F
Troubleshooting

This appendix describes how to troubleshoot problems with Oracle8 Client.

Specific topics discussed are:

• Database Connection Issues

• DOS Compatibility Mode on Windows 95 or Windows 98 Computers

• Oracle Web Publishing Assistant

• Oracle Assistants

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 OracleTNSListener801 services are started. See Chapter 10 "Troubleshooting Net8" in 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/98.

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:

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

DOS Compatibility Mode on Windows 95 or Windows 98 Computers

If a Windows 95 or Windows 98 computer is in DOS COMPATIBILITY MODE, then it is unable to read the long file name of TRACESVR80 (and directory so named) from the CD-ROM. You can determine if a computer is running in compatible mode by right-clicking on MY COMPUTER, choosing PROPERTIES, and then selecting the PERFORMANCE tab. This will open a window that tells you which drives, if any, are running in compatible mode, or if your computer is running a complete 32-bit FILE System.

DOS compatible mode may be enabled by the operating system for several reasons:

• A boot sector virus exists on the computer

• A realmode device driver exists in the CONFIG.SYS and Windows NT has no protectmode driver that can take over for it

• Too many INT 13 hooks exist

• An old VxD exists for a controller in the SYSTEM.INI file that has no counterpart in Windows 95.

A list of all ProtectMode drivers, and some bad ones, exists on a Windows 95 computer in a file called IOS.INI. If a computer is running in compatible mode, then a log file should be created called IOS.LOG. This will list the devices that are running in compat/realmode and the reason why.

Additionally, if the Windows 95 or Windows 98 computer is on a LAN and can connect to a Windows NT computer (or a Windows 95 or Windows 98 computer whose CD-ROM drivers can deal with the long file name), place the CD-ROM in the Windows NT computer's CD-ROM drive and install the software on the Windows 95 or Windows 98 computer over the network.

Oracle Web Publishing Assistant

Due to French government regulations on encryption, you cannot set your system default locale to French (Standard) in the Regional Settings Control Panel of Windows NT.

Oracle Assistants

This section includes known problems, restrictions, and workarounds to the Oracle Assistants:

• The Help button of some Assistants is sometimes enabled even though online help is not available.

• Oracle Net8 Assistant, Oracle Net8 Easy Config, and Oracle INTYPE File Assistant require monitors displaying at least 256 colors.

• Oracle Assistants have an online help facility that includes the feature to search for a text string in the help text. This feature is activated by the Search button. When you click the Search button, a dialog box appears. You can then enter a text string such as a word or phrase into a text box and press the Find button to search for the string in the help text.

• Currently, the Find feature cannot find a Japanese text string of more than one character. That is, if you enter one Japanese character to search, the search feature will work normally; it will find the character, provided it exists in the help text. If you enter more than one Japanese character, or one Japanese character mixed with other characters such as English characters, the search facility will fail to find the string even if it does exist in the help text. Searching for English and other European languages text strings does not have this limitation.

Oracle Database Assistant

• The Oracle Database Assistant in this release is certified against an Oracle8 database only. Version 7 databases are not supported.

• During installation, if you choose to install the starter database or use the Oracle Database Assistant, a dialog box appears asking if you want to view the documentation. If you choose Yes, a browser appears over the Assistant. To see the Assistant, dismiss the browser.

• In order to enable the Image Demo for an existing instance (in the Modify route of the assistant), the SCOTT/TIGER account must have been created in that instance and CONNECT and RESOURCE roles must have been granted; the Oracle Database Assistant assumes the account is already created.

Registering CTXV236.OCX on Windows 95 Clients

When executing Start > Programs > ConText Cartridge Workbench > Viewer Example on a Windows 95 client, you can receive an error message stating that registration of CTXV236.OCX failed. If you receive this error message:

1. Register CTXV236.OCX at the MS-DOS command prompt:

   C:\> REGSVR32 CTXV236.OCX
   

2. Shut down and restart your Windows 95 client.