Oracle Net8 Configuration and Troubleshooting
| | |
| Team-Fly | |
| | Oracle Net8 Configuration and Troubleshooting By Jonathan Gennick, Hugo Toledo
|
| Table of Contents | |
| [SYMBOL] [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X]
tables (repository) TAF [See Transparent Application Failover] TCP/IP access control and choosing port numbers client connectivity, testing configuring listeners Connection Manager Addresses and dispatcher processes and adding host naming and initiating discovery installing Net8 under Windows JDBC drivers and Microsoft protocols, installing multi-protocol support and prespawned dedicated server processes, creating testing network connectivity TIMEOUT parameter creating prespawned dedicated server processes returning prespawned dedicated server processes to pool timestamp (listener log entry field) TNS (Transparent Network Substrate) in protocol stacks TNS Ping trace file parameters and TNS_ADMIN environment variable configuration files, locating listener.ora file, locating overriding default location of configuration files TNSNAME keyword, choosing naming method TNSNAMES entries, syntax for tnsnames.ora file adding Net8 service names Bequeath connections and centralized naming and changing Net8 settings connect-time failover creating Oracle instances in dedicated server configurations default domains and 2nd defining net service names 2nd 3rd directory naming and editing profiles external procedure calls, supporting forcing a dedicated server connection IPC connections and keeping a standard file LDAP directory, configuring local naming and names resolution options and naming method LDAP naming methods and 2nd Net8 Easy Config and Oracle Names, using parameters for SID_LIST parameter and Transparent Application Failover and verifying names tnsping utilities connectivity between machines Net8 connectivity testing verifying options testing client connectivity tnsping utility TNSPING.TRACE_DIRECTORY parameter generating trace files TNSPING.TRACE_LEVEL parameter generating trace files TOTALQ column, in the V$QUEUE view TRACE command, changing listener parameters trace files choosing locations contents of locations of names parameters of problems generating using trace levels TRACE_DIRECTORY parameter generating trace files modifying a listener TRACE_DIRECTORY_CLIENT parameter generating trace files specifying trace file locations TRACE_DIRECTORY_listener_name parameter generating trace files TRACE_DIRECTORY_SERVER parameter generating trace files specifying trace file locations TRACE_FILE parameter, modifying a listener TRACE_FILE_CLIENT parameter generating trace files specifying location of trace files TRACE_FILE_listener_name parameter generating trace files TRACE_FILE_SERVER parameter generating trace files specifying trace file locations TRACE_FILELEN parameter generating trace files TRACE_FILELEN_listener_name parameter generating trace files TRACE_FILENO parameter generating trace files TRACE_FILENO_listener_name parameter generating trace files TRACE_LEVEL parameter, modifying a listener 2nd TRACE_LEVEL_CLIENT parameter generating trace files TRACE_LEVEL_listener_name parameter generating trace files TRACE_LEVEL_SERVER parameter generating trace files TRACE_TIMESTAMP parameter generating trace files TRACE_TIMESTAMP_listener_name parameter generating trace files TRACE_UNIQUE_CLIENT parameter generating trace files TRACING parameter generating trace files transparency location protocol Transparent Application Failover (TAF) 2nd client load balancing and connect-time failover connecting to a backup instance limitations of methods retries and delays types of V$SESSION view, status from Transparent Network Substrate (TNS) in protocol stacks troubleshooting techniques (Net8) testing connectivity Two-Task Common (TTC) presentation layer, in default protocol stacks TWO_TASK environment variable
|
| | |
| Team-Fly | |
| Top |