Enterprise Edition Getting Started
Release 8.0.5 for Windows NT
Specific topics discussed are:
|If You Receive This Error...||Ensure Your...|
TNS-12203 TNS: unable to connect to destination
OracleServiceSID and OracleTNSListener801 services are started. See section , "Managing Oracle Services" in Chapter 10, "Administering a Database" and Chapter 10 "Troubleshooting Net8" in Net8 Administrator's Guide.
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. See section , "Managing Oracle Services" in Chapter 10, "Administering a Database" for instructions.
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.|
See "Oracle8 Performance Monitor
Troubleshooting Information" in Chapter
12, "Monitoring a Database", for information on Oracle8 Performance
Monitor troubleshooting issues.
This section includes the following topics:
If you are migrating from Oracle7 to Oracle8 Enterprise Edition with your own customized batch migration script, and the system seems to be taking unusually long to complete the migration, you may be experiencing an ORA-54 error. Follow these steps to complete migration:
Uses the default INITSID.ORA file located in your ORACLE_HOME\DATABASE directory to start the Oracle8 database.
SVRMGR> STARTUP PFILE=PATH\FILENAME
Uses an initialization file other than the default to start your database. PATH\FILENAME specifies an initialization parameter file other than the default, INITSID.ORA. The following example starts the database using a file named INIT2.ORA.
SVRMGR> STARTUP PFILE=%ORACLE_HOME%\RDBMS80\INIT2.ORA
You must add additional space in order to extend rollback segments if you receive the following errors when using either Oracle Data Migration Assistant or the Migration Utility (MIG80) to migrate your database to release 8.0.5:
To add space to the rollback segments:
The data file size you specify depends upon the size of the database you want to migrate. See Oracle8 Administrator's Guide, Oracle8 SQL Reference, and Oracle8 Error Messages for more information.
You must add additional space to the SYSTEM tablespace if you receive the following errors:
To add space to the SYSTEM tablespace:
Re-install Required Support Files release 8.0.5 if:
These problems occur if after installing release 8.0 products,
you subsequently install a product that installs Required Support Files
release 7.3.2 or release 7.2. Oracle Web Server release 2.1 is an example
of such a product.
To re-install Required Support Files release 8.0.5:
The Software Asset Manager window appears.
A window appears showing the progress of the installation. After installation is complete, a message appears confirming the installation.
When trying to start your database with Server Manager after migrating from a 220.127.116.11.6 database, ensure that you use the PFILE option to identify the correct INITSID.ORA file. For example:
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:
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 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
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.
When using Replication Manager to configure a snapshot replication site, this error message may appear when trying to create a snapshot group:
If this error does occur, remove the replication object,
delete the snapshot group just created, and re-create the snapshot group.
On the Snapshot Group Wizard - Individual Snapshot Settings dialog
box, clear the check box for Minimum Communication. This error is logged
as bug number 601075.
This section includes known problems, restrictions, and workarounds to the Oracle Assistants:
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: