E
Troubleshooting

This appendix describes how to troubleshoot problems with Oracle8 Client.

Specific topics discussed are:

• Database Connection Issues

• Operating System Permission Issues

• Operating System Permission Issues

• Using Oracle Trace

Database Connection Issues

This table lists and provides answers to common Oracle8 database connection issues:

If You Receive This Error...	Ensure Your...
TNS-12203 TNS: unable to connect to destination	OracleServiceSID and OracleTNSListener80 services are started. See Net8 Administrator's Guide.
ORA-12547 TNS: lost contact	OracleServiceSID, OracleStartSID, and OracleTNSListener801 services are started. You receive this error if you attempt to use any of the Oracle8 Utilities, such as Server Manager. Note: This error is analogous to the following Oracle7 error: ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task
ORA-28575: unable to open RPC connection to external procedure agent ORA-06512: at "APPLICATIONS.OSEXEC", line 0 ORA-06512: at "APPLICATIONS.TEST", line 4 ORA-06512: at line 2	TNSNAMES.ORA and LISTENER.ORA files have been correctly configured to use external procedures. See "Configuring External Procedure Calls" in Chapter 8 of Net8 Getting Started for Windows NT and Windows 95.

1 Ensure that OracleHOME_NAMETNSListener is started if you are using an Oracle8 database that has a home name.

Operating System Permission Issues

The permission problem (OS 5 or 3) is typically caused by inadequate configuration of the NTFS permissions. By default, the Oracle8 database service runs using the SYSTEM account instead of a named Windows NT user such as Administrator. In File Manager or Windows NT Explorer, you must grant Full Control on the ORACLE_HOME directory and all of its subdirectories to the SYSTEM user. The SYSTEM user has the full name The operating system and has an icon of a computer chip. For this and other Windows NT problems, consult your Windows NT documentation or contact your Windows NT System Administrator.

After correcting the problem, you must delete any files created as a result of partial completion of the CREATE DATABASE command. The files to delete are the:

• Data files: SYS1SID.ORA, USR1SID.ORA, RBS1SID.ORA, TMP1SID.ORA

• Redo log files: LOG1SID.ORA, LOG2SID.ORA, LOG3SID.ORA, LOG4SID.ORA

• Control files: CTL1SID.ORA and CTL2SID.ORA

Then, run the BUILD_DB.SQL script again in Server Manager.

Using Oracle Trace

Oracle Trace is a general-purpose data collection tool that is part of the Oracle Enterprise Manager Performance Pack (not contained on this CD-ROM disc). Oracle Trace collects data from Oracle applications and databases. This data can include:

• performance statistics

• diagnostics data

• system resource usage

• business transaction details

This data can be:

• formatted into a report for your review

• input to the Oracle Expert tool of Oracle Enterprise Manager, an expert system that applies rules to this data and provides suggestions for optimizing your application or database.

See Oracle Enterprise Manager Oracle Trace User's Guide for information on starting and using Oracle Trace.

Contacting Oracle Worldwide Customer Support

If after reading this appendix, you still cannot resolve your problems, call Oracle Worldwide Customer Support to report the error (or see the Oracle Worldwide Customer Support page at: http://www.oracle.com/support/. Please have the following information at hand:

• The hardware and operating system release number on which your application(s) is running.

• The release numbers (up to five digits in release) of all Oracle networking products involved in the current problem.

• The third-party vendor and version you are using.

• The kind of links that are between the client and server.

• A description of what does work.

• The exact error message.

• A Net8 trace if possible. If not, the log file is sufficient.

---