Oracle B12255-01 - Manual (Page 105)

mod_plsql
Oracle HTTP Server Modules 7-35
Notes:
■
If the database is running in the same Oracle home, or the environment
variable “TWO_TASK” is set (called “LOCAL” on Windows NT), this parameter
need not be specified.
■
If the database is running in a separate Oracle home, then this parameter is
mandatory.
■
If you have problems connecting to the database:
■
Check the username and password information in the DAD.
■
Make sure that you run “tnsping <string>” and execute commands
such as:
sqlplus DADUsername/DADPassword@<string>
■
Ensure that TNS_ADMIN is configured properly.
■
Verify that the HOST:PORT:SERVICE_NAME format makes the connection
go through.
■
Ensure that the TNS listener and database are up and running.
■
Ensure that you can ping the host from this machine.
■
From a mod_plsql perspective, TNSFormat and NetServiceNameFormat
are synonymous and denote connect descriptors that are resolved by Net. The
TNSFormat
is provided as a convenience so that end-users use this to signify
that the name resolution happens through the local tnsnames.ora. For
situations where the resolution is through an LDAP lookup as configured in
sqlnet.ora
, it is recommended that the format specifier of
NetServiceNameFormat be used.
If your database supports high availability, for example, RAC database, it is
highly recommended that you use the NetServiceNameFormat such that the
resolution for the net service name is through LDAP. This enables you to add or
remove RAC nodes accessible through mod_plsql by just changing Oracle
Internet Directory with the new/deleted node information. In such situations,
hard-coding database listener HOST:PORT information in dads.conf or in the
local tnsnames.ora is not recommended.
■
In older versions of the product, this configuration parameter was called
connect_string
.