Troubleshooting the Transaction Manager
Listener Cannot Be Started or is not defined Error
1. Confirm that the listener.ora file contains no syntax errors that were introduced by manually editing the file. The most common errors are missing or extra parentheses. Using Oracle Network Manager 3.1.4 prevents such problems. Oracle does not support manipulation of network configuration files by any method other than the Oracle Network Manager.
2. Confirm that the listener.ora file that you have modified is indeed the file that SQL*Net is reading. To do so, define a SQL*Net UNIX environment variable TNS_ADMIN to the name of the directory where your listener.ora file is located. Restart the listener. If the listener starts up without a problem, then SQL*Net is reading a different listener file. Make sure that you're placing the listener.ora file in the appropriate directory. Contact your Database Administrator if you are not certain where the network configuration files belong.
3. Confirm that you are running lsnrctl on the machine for which this listener was defined (host field in the listener.ora). You must run the listener on the machine defined as the host.
4. Confirm that no other process is using the same network address. It is possible that another listener, a Transaction Manager running in the STANDALONE mode, or another network program may already be occupying that network address. Set the listener to another network address. Contact your Database Administrator to find the appropriate network addresses that you can assign to the listener.
Oracle Network Layer Error Occurs When the Sales Order Form Is Opened
1. Has the OE: Transaction Manager profile been defined properly?
The OE: Transaction Manager profile determines the Oracle Order Entry Transaction Manager to which the client should connect. Network layer messages will specify the name of the Oracle Order Entry Transaction Manager. If the name specified in the message does not match the name you expect to see, confirm that this profile has the correct Transaction Manager name. If not, open the System Profile Values window using the System Administrator responsibility and set the correct name at the site level. If the correct value is already set at the site level, this value is being overridden at either the application, responsibility, or user level. You must make appropriate changes to enable the client to read the correct Transaction Manager name. See: Oracle Order Entry/Shipping Profile Options.
2. Can the TNSPING utility connect to the OE Transaction Manager?
Oracle TNSPING is a utility that is packaged with SQL*Net 2.3 or higher. To quickly confirm whether your PC can connect to a server residing across the network:
1. On the client PC, start TNSPING. Typically, choose Programs from the Start menu, then choose Oracle for Windows, then choose TNSPING.
2. At the Address prompt, enter the name of your Order Entry Transaction Manager as defined in the OE: Transaction Manager profile option and in the tnsnames.ora configuration file.
3. At the Number of Pings prompt, enter 1.
If successful, TNSPING will report a message "OK" followed by the roundtrip time. If TNSPING successfully connects to the Transaction Manager, but you still see Oracle Network Layer errors when you open the Sales Order form, contact your system administrator.
If TNSPING cannot connect to the Order Entry Transaction Manager, it will issue an error message. Follow the steps below to identify the problem.
3. Has the Transaction Manager been defined in the tnsnames.ora file?
Confirm that an entry for the Transaction Manager has been defined in the tnsnames.ora file on the client. If not, you must add an appropriate entry to the file. Review the Oracle Order Entry section in Chapter 5 of the Oracle Applications Installation Manual for Windows Clients.
4. Are the configuration files located in the appropriate directories?
1. Confirm that the tnsnames.ora and sqlnet.ora files you modified are indeed the files that SQL*Net is reading. On the client, tnsnames.ora and sqlnet.ora files are placed in the ORACLE_HOME/network/admin directory. To identify where ORACLE_HOME is on your PC, review Configuration Files in Chapter 2 of the Oracle Applications Installation Manual for Windows Clients.
You can also use SQL*Net trace files to confirm which tnsnames.ora file SQL*Net is reading. To turn on SQL*Net trace, update the sqlnet.ora file on the client PC. Modify these three parameters:
trace_level_client = ADMIN
trace_file_client = sqlnet
trace_directory_client=C:\ORAP15\network\trace
Make sure that trace_level_client is set to ADMIN. Modify trace_file_client and trace_directory_client as desired to define the location of the trace file.
2. Try to connect to the Order Entry Transaction Manager through TNSPING (described above), through SQL*Plus, or by opening the Sales Order form. After the SQL*Net connection fails, review the trace file generated by SQL*Net. Using an editor or word processor, search the trace file for the phrase "tnsnames.ora". This line will indicate which tnsnames.ora file SQL*Net is reading.
5. Is the listener up and running?
1. Confirm that the listener is up and running. Run the command "lsnrctl status [listener name]" on the server.
If the listener is not up and running, lsnrctl displays a message similar to the following: (In this example, the listener name is "LISTENER_OEORPC_testsun".)
LSNRCTL for SVR4: Version 2.1.6.1.0 - Production on 04-SEP-96 00:15:36
TNS-01101: Could not find service name LISTENER_OEORPC_testsun NNC-00406: name "LISTENER_OEORPC_testsun" does not exist
2. If the listener is not running, start the listener. If the listener is running, lsnrctl displays a message similar to the following:
LSNRCTL for SVR4: Version 2.1.6.1.0 - Production on 04-SEP-96 00:14:19
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=testsun)(PORT=1527))
STATUS of the LISTENER
------------------------
Alias LISTENER_OEORPC_testsun
Version TNSLSNR for SVR4: Version 2.1.6.1.0 - Production
Start Date 04-SEP-96 00:12:44
Uptime 0 days 0 hr. 1 min. 35 sec
Trace Level off
Security OFF
Listener Parameter File /u6/oracle/prod/7.1.6.2/netword/admin/listener.ora
Listener Log File /tmp/log/oeorpc_testsun.log
Services Summary...
OEORPC_testsun has 1 service handlers
The command completed successfully
3. Confirm that the network address indicated by the lsnrctl utility's output is identical to the network address defined in the client's tnsnames.ora file for the Transaction Manager. Also, examine the Listener Parameter File value of the output to validate that the lsnrctl is reading the desired listener.ora file.
4. Confirm that the SID value defined for the Transaction Manager in the client's tnsnames.ora file matches the server listener.ora's SID Name value. If not, you must update the tnsnames.ora files of the client or stop the listener, modify the server's listener.ora file, and restart the listener for the Transaction Manager so that these two values match.
6. Has the listener.ora file been generated properly?
1. A common problem with the listener.ora file is that the user parameter, "ENVS", has not been defined properly. Run the Transaction Manager in STANDALONE mode from the Application Manager's environment. (See: Standalone Mode.) If the client is able to connect to the standalone Transaction Manager, then it is likely that the user parameter, "ENVS", is defined improperly.
2. Confirm that the ENVS parameter is defined in one line, without any extra characters such as tabs or spaces. Also, confirm that the FND_TOP, OE_TOP, TNS_ADMIN and other environment variables are defined correctly.
3. Run the diagnostics using the STANDALONE mode with the environment variables, OERPCDBG and OEDBGFILE, set. (See Generating a Diagnostics File.) Search for any errors in the diagnostics output. One potential error could be that the Transaction Manager fails to connect to the database.
4. Confirm that the server's tnsnames.ora file also has the entry for the database to which that client connects. Also, validate that the TNS_ADMIN variable is set to the correct directory in the listener.ora file.
7. Still not running?
Other installation or configuration problems could adversely affect the Transaction Managers.
Name Servers: Some Name Servers cause incompatibility problems with the Transaction Manager configuration. Oracle Order Entry currently does not support the network configuration that uses Name Servers. You can confirm the existence of the Name Servers in your network environment by searching in your sqlnet.ora file for an entry similar to the following:
names.name_servers = (ADDRESS_LIST =
(ADDRESS = (COMMUNITY = tcp) (PROTOCOL = TCP) (Host = name_server) (Port = 1521)))
SQL*Net V2: It is possible that SQL*Net V2 has not been properly installed or configured on your client PC. Some known problems include incompatible TCP/IP adapter or TPC/IP stack problems. To confirm that your SQL*Net V2 is working, connect to a database in SQL*Plus 3.1 using the SQL*Net V2 connect string. For example, you would use the connect string "t:testsun:A106CD" for SQL*Net V1, whereas for SQL*Net V2, you would use the connect string "A106CD". An entry for the database "A106CD" should be defined in the client's tnsnames.ora file. If you cannot connect to the database using the SQL*Net V2 connect string, and you have confirmed that the database entry exists in the tnsnames.ora file in the client's $ORACLE_HOME/network/admin directory, then there is a problem with your client's SQL*Net V2 installation. Contact your System Administrator.
