Release 2 (9.2) for Windows
Part Number A95490-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Getting Started Release 2 (9.2) for Windows Part Number A95490-01 |
|
This appendix lists error messages, causes, and corrective actions that are specific to operation of Oracle9i for Windows. This appendix also includes database connection issues.
This appendix contains these topics:
|
Note: The |
Keep a log of error messages you receive by redirecting messages to a file. You can record the contents of normal utility messages by using the LOGFILE parameter discussed in Oracle9i Database Utilities. You can separately record the error message portion by using standard Windows NT file redirection. For example, use the following syntax to redirect the output from Export utility:
C:\> exp USERNAME/PASSWORD parfile=FILENAME >file1.log 2>file2.err
With this command line, file1.log receives standard output from Export utility, while file2.err receives standard error messages.
Connect internal is no longer supported
Cause: CONNECT INTERNAL is no longer supported.
Action: Connect to the database as CONNECT / AS SYSDBA or an existing user with appropriate password.
Error messages in this section are Oracle operating system-dependent (OSD) messages displayed in response to an error condition in Windows NT. Each message in this section triggers an Oracle9i database error message.
Error messages appear first in summary tables consisting of error numbers and the corresponding error message. Following the tables is a more detailed discussion of errors, including causes and corrective actions.
| Loader Errors: | OSD-04300 to OSD-04399 |
|---|---|
|
4300 |
Unable to read complete record from datafile |
|
4301 |
Record size too large |
|
4302 |
Invalid record type, load options, or both |
| Semaphore Errors: | OSD-04400 to OSD-04499 |
|---|---|
|
4400 |
Unable to acquire internal semaphore for process |
|
4401 |
WaitForSingleObject() failure, unable to obtain semaphore |
Logical block size mismatch
Cause: Database block size specified in initialization parameter file (init.ora) does not match block size of actual database files.
Action: Use matching logical block sizes.
Invalid logical block size
Cause: Logical block size is not a multiple of 512 bytes, or it is too large.
Action: Change the value of DB_BLOCK_SIZE in the initialization parameter file.
Unable to open file
Cause: Specified path or filename is invalid, or destination device is full. This error can also be caused by insufficient Windows NT file handles.
Action: Make sure path and file exist, and device has free space. If this fails, then increase number of Windows NT file handles.
Unable to read file header block
Cause: Media has been damaged.
Action: Recover file, if necessary, and verify that Windows NT is functioning correctly.
Invalid file header
Cause: File is damaged.
Action: Recover file.
SetFilePointer() failure, unable to read from file
Cause: There was an unexpected return from Windows NT system service SetFilePointer().
Action: Check operating system error code and consult Windows NT documentation.
ReadFile() failure, unable to read from file
Cause: There was an unexpected return from Windows NT system service ReadFile().
Action: Check operating system error code and consult Windows NT documentation.
Truncated read
Cause: System encountered an unexpected end-of-file, which is due to damaged media.
Action: Verify that file is not damaged.
WriteFile() failure, unable to write to file
Cause: There was an unexpected return from Windows NT system service WriteFile().
Action: Check operating system error code and consult Windows NT documentation.
Truncated write
Cause: Destination device is full, or media is damaged.
Action: Verify that device has free space and that file is not damaged.
<create> option specified, file already exists
Cause: File you attempted to create already exists.
Action: Delete existing file or use REUSE option in SQL statement.
GetFileInformationByHandle() failure, unable to obtain file info
Cause: There was an unexpected return from Windows NT system service GetFileInformationByHandle().
Action: Check operating system error code and consult Windows NT documentation.
File size mismatch
Cause: File to be re-used is either too large or too small.
Action: Specify correct file size or delete existing file.
Unable to read line from file
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
Unable to close file
Cause: Media has been damaged.
Action: Recover file, if necessary, and verify that Windows NT is functioning correctly.
Asynchronous I/O request returned an error
Cause: There was an unexpected return from Windows NT system service.
Action: Check operating system error code and consult Windows NT documentation.
Error queuing an asynchronous I/O request
Cause: There was an unexpected return from Windows NT system service.
Action: Check operating system error code and consult Windows NT documentation.
Unable to open the specified RAW device
Cause: An invalid path or filename was specified, or device is full.
Action: Make sure file exists and device is not full; verify that operating system is functioning correctly.
Unable to access the specified directory or device
Cause: An invalid path name was specified.
Action: Make sure directory or device exists and is accessible.
Unable to set file pointer
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
Unable to set eof file marker
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
Unable to read file
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
Unable to write file
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
SleepEx() failure, unable to Sleep
Cause: There was an unexpected return from Windows NT system service.
Action: Check operating system error code and consult Windows NT documentation.
Unable to delete file
Cause: This error is caused by an operating system error or by damaged media.
Action: Check operating system error code (if available) and consult Windows NT documentation. If no operating system error code is presented, then verify that media is not damaged.
Invalid question asked
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Invalid parameter passed
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Malloc() failure, unable to allocate memory
Cause: Program is out of memory.
Action: Shut down all unnecessary processes or install more memory in the computer.
Invalid SGA: SGA not initialized
Cause: System Global Area (SGA) has been allocated but not initialized.
Action: Wait until STARTUP has completed before attempting to connect.
Unable to open/create file for shared memory object
Cause: There was an unexpected return from Windows NT system service CreateFile().
Action: Check operating system error code and consult Windows NT documentation.
Unable to attach to SGA: SGA does not exist
Cause: SGA does not exist.
Action: Start up an Oracle instance.
Unable to map shared memory (SGA) into the address space
Cause: There was an unexpected return from Windows NT system service MapViewOfFileEx().
Action: Check operating system error code and consult Windows NT documentation.
Shared memory (SGA) mapped to wrong address
Cause: There was an unexpected return from Windows NT system service MapViewOfFileEx().
Action: Check operating system error code and consult Windows NT documentation.
Unable to allocate memory with VirtualAlloc
Cause: Program is out of memory.
Action: Shut down all unnecessary processes or install more memory in the computer.
Unable to deallocate memory with VirtualFree
Cause: There was an unexpected return from Windows NT system service VirtualFree().
Action: Check operating system error code and consult Windows NT documentation.
Unable to protect memory with VirtualProtect
Cause: There was an unexpected return from Windows NT system service VirtualProtect().
Action: Check operating system error code and consult Windows NT documentation.
Unable to begin another thread
Cause: Program has run out of system resources.
Action: Shut down all unnecessary processes; install more memory in the computer.
No pid structure supplied to spdcr()
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
DosSetPriority() failure, unable to set process priority
Cause: There was an unexpected return from Windows NT system service DosSetPriority().
Action: Check operating system error code and consult Windows NT documentation.
DosKillProcess() failure, unable to kill process
Cause: There was an unexpected return from Windows NT system service DosKillProcess().
Action: Check operating system error code and consult Windows NT documentation.
Invalid pid
Cause: Process ID not recognized by system; process previously terminated.
Action: Verify that process ID is correct and that process is active.
CreateProcess() failure, unable to spawn process
Cause: There was an unexpected return from Windows NT system service CreateProcess().
Action: Check operating system error code and consult Windows NT documentation.
Invalid priority specified in CONFIG parameter ORACLE_PRIORITY
Cause: Priority specified is invalid or out of range.
Action: Specify a valid setting for ORACLE_PRIORITY.
OpenProcess() failure, unable to open process handle
Cause: There was an unexpected return from Windows NT system service OpenProcess().
Action: Check operating system error code and consult Windows NT documentation.
Incorrect or unknown background image name given to spdcr()
Cause: There was an unexpected background name given to spdcr().
Action: Contact Oracle Support Services.
Timeout waiting for thread semaphore
Cause: An Oracle database thread died holding the semaphore.
Action: Restart Oracle database instance.
Thread information not found
Cause: An Oracle database thread died without deleting its information.
Action: Restart Oracle database instance.
Maximum number of Oracle threads reached
Cause: Maximum number of Oracle database threads for the instance is reached.
Action: Wait until some connections exit before trying again.
Oracle thread unable to DuplicateHandle()
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Oracle thread unable to CreateEvent()
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Bad function code supplied to ssthreadop
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Unable to find file handle for that thread
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Unable to retrieve system username for current user
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Cannot post thread
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Bad thread list semaphore
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Target thread is currently busy
Cause: Target thread is processing an oradebug command.
Action: Wait and resend command.
Unable to get the threads context
Cause: Check operating system error code.
Action: Remedy operating system error.
Unable to set the threads context
Cause: Check operating system error code.
Action: Remedy operating system error.
Unable to suspend the target thread
Cause: Check operating system error code.
Action: Remedy operating system error.
Unable to resume the target thread
Cause: Check operating system error code.
Action: Remedy operating system error.
Unable to read complete record from datafile
Cause: Datafile ended in the middle of a record. This error occurs when loading files with a fixed record length.
Action: Verify that datafile is of correct length and contains complete records.
Record size too large
Cause: Specified record size is too large to load.
Action: Reduce record size and reload data.
Invalid record type, load options, or both
Cause: Control file's Windows NT file processing options string contains an invalid option or keyword.
Action: Set Windows NT file processing options string to an acceptable value.
Unable to acquire internal semaphore for process
Cause: Oracle database has exceeded the maximum number of connections.
Action: Delete any unused connections and try again.
WaitForSingleObject() failure, unable to obtain semaphore
Cause: There was an unexpected return from Windows NT system service WaitForSingleObject().
Action: Check operating system error code and consult Windows NT documentation.
Illegal option specified
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Internal buffer overflow
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Support Services.
Translations nested too deep
Cause: Program encountered too many intermediate translations while attempting to translate a configuration variable.
Action: Simplify values of configuration parameters to include fewer intermediate translations.
Text contains no translatable elements
Cause: Program cannot recognize variables in text to be translated.
Action: Check and, if necessary, correct text to be translated.
stdin not responding
Cause: System is unable to receive input from standard input stream.
Action: Verify that process has access to an input device.
Unable to spawn process via system()
Cause: System is out of memory or executable is invalid.
Action: Shut down unnecessary processes; install more memory in the computer. Verify name of executable.
Operating system roles are not supported
Cause: An attempt was made to use an operating system role.
Action: Only use roles that were created 'IDENTIFIED BY PASSWORD' as opposed to 'IDENTIFIED EXTERNALLY'.
Unable to get date and time from the operating system
Cause: There was an unexpected return from GetLocalTime() call.
Action: Verify that system time is correct on the computer.
Unable to translate the 'USERNAME' config.ora variable on server
Cause: 'USERNAME' configuration parameter variable on host is not properly set.
Action: Verify 'USERNAME' variable is set.
'remote_os_authent' init.ora variable not set to TRUE
Cause: For remote operating system logon to function, 'REMOTE_OS_AUTHENT' parameter must be set to TRUE.
Action: Shut down and start up instance with 'REMOTE_OS_AUTHENT = TRUE' in initialization parameter file.
The Windows NT Group name is too long for internal buffer
Cause: Windows NT Group name is too long.
Action: Use a shorter Windows NT group name.
ORADIM is a command-line utility for starting and stopping database instances that is only available on Oracle for Windows. It is not available on any other platform.
| Oradim Errors | DIM-0000 to DIM-0039 |
|---|---|
|
00000 |
ORADIM completed with no errors |
|
00001 |
ORADIM: <command> [options]. Please refer to the manual. |
|
00002 |
Valid commands are: -DELETE, -EDIT, -NEW, -STARTUP, and -SHUTDOWN |
|
00003 |
An argument is missing for the parameter |
|
00004 |
Either a SID or service name is mandatory. Please enter a valid SID or service name |
|
00005 |
You have entered a SID with more than 64 characters |
|
00006 |
You have entered an empty SID |
|
00007 |
Missing or invalid -STARTMODE parameter. Valid -STARTMODE parameter is AUTO or MANUAL |
|
00008 |
A valid service name is OracleService appended with a SID |
|
00009 |
SID name is mandatory. Please enter a valid SID name |
|
00010 |
SYSTEM\CurrentControlSet\Services\OracleService key does not exist |
|
00011 |
The service does not exist |
|
00012 |
You did not enter a pfile for autostart capability |
|
00013 |
The service start mode could not be set in the registry |
|
00014 |
Cannot open the Windows NT Service Control Manager |
|
00015 |
Cannot start already-running ORACLE - shut it down first |
|
00016 |
Missing or invalid -SHUTTYPE parameter. A valid -SHUTTYPE parameter is SRVC or INST |
|
00017 |
Instance shutdown mode must be one of the following: a for abort, i for immediate or n for normal |
|
00018 |
Failed to stop Oracle Service |
|
00019 |
Create Service Error |
|
00020 |
A service for this SID is already created. Please enter a different SID name. No action has been taken |
|
00021 |
RegOpenkeyEx failed |
|
00022 |
Please enter one of the following commands |
|
00023 |
Create an instance by specifying the following parameters: |
|
00024 |
-NEW -SID sid | -SRVC service [-INTPWD password] [-MAXUSERS number] [-STARTMODE a|m] [-PFILE file] [-TIMEOUT secs] |
|
00025 |
Edit an instance by specifying the following parameters: |
|
00026 |
-EDIT -SID sid [-NEWSID sid] [-INTPWD passwd] [-STARTMODE a|m] [-PFILE file] [-SHUTMODE a|i|n] [-SHUTTYPE srvc|inst] |
|
00027 |
Delete instances by specifying the following: |
|
00028 |
-DELETE -SID sid | -SRVC service name |
|
00029 |
Startup services and instance by specifying the following parameters: |
|
00030 |
-STARTUP -SID sid [-USRPWD password] [-STARTTYPE srvc|inst|srvc,inst] [-PFILE filename] |
|
00031 |
Shutdown services and instance by specifying the following parameters: |
|
00032 |
-SHUTDOWN -SID sid [-USRPWD password] [-SHUTTYPE srvc|inst|srvc,inst] [-SHUTMODE a | i | n] |
|
00033 |
Query for help by specifying the following parameters: -? | -h | -help |
|
00034 |
You have entered an invalid option for the -NEW command |
|
00035 |
You have entered an invalid option for the |
|
00036 |
You have entered an invalid option for the |
|
00037 |
You have entered an invalid option for the |
|
00038 |
You have entered an invalid option for the |
|
00039 |
Internal logic error in ORADIM |
ORADIM completed with no errors
Cause: ORADIM has completed without any errors.
Action: None.
ORADIM: <command> [options]. Please refer to the manual.
Cause: Command-line arguments could not be recognized.
Action: Usage: ORADIM <command> [options]
Use the following commands:
To create an instance:
-NEW -SID sid | -SRVC service name [-INTPWD password][-MAXUSERS number] [-STARTMODE auto [-PFILE filename]| manual]
To edit an instance:
-EDIT -SID sid [-NEWSID sid][-INTPWD password][-STARTMODE auto [-PFILE filename]| manual]
To delete an instance:
-DELETE -SID sid | -SRVC service name
To startup a service and instance:
-STARTUP -SID sid [-USRPWD password][-STARTTYPE srvc | inst | srvc,inst] [-PFILE filename]
To shutdown a service and instance:
-SHUTDOWN -SID sid [-USRPWD password][-SHUTTYPE srvc | inst | srvc,inst] [-SHUTMODE a | i | n]
To query for help
-? | -h | -help
Valid commands are: -DELETE, -EDIT, -NEW, -STARTUP, and -SHUTDOWN
Cause: You have not entered one of the referenced commands.
Action: Use valid commands.
An argument is missing for the parameter
Cause: You have entered an invalid argument.
Action: Use a valid argument and start program again.
Either a SID or service name is mandatory. Please enter a valid SID or service name
Cause: You have not entered the SID following -SID.
Action: Enter a valid SID of 64 characters and try again.
You have entered SID with more than 64 characters
Cause: You have entered a SID with more than 64 characters.
Action: Change it to 64 or fewer characters and make sure that there is no other service with this name.
You have entered an empty SID
Cause: Enter a SID with 64 characters and make sure that there is no service with this SID on your system.
Action: Fill in the SID and rerun program.
Missing or invalid -STARTMODE parameter. Valid -STARTMODE parameter is AUTO or MANUAL
Cause: You have not entered valid start mode (AUTO or MANUAL).
Action: Enter valid start mode and try again.
A valid service name is OracleService appended with a SID
Cause: You have entered a service name other than OracleService(SID).
Action: Correct name of service and try again.
SID name is mandatory. Please enter a valid SID name
Cause: You did not enter a SID.
Action: Enter the SID and try again.
SYSTEM\CurrentControlSet\Services\OracleService key does not exist
Cause: Referenced key is not in the registry.
Action: Try reinstalling. If problem persists, then contact Oracle Support Services.
The service does not exist
Cause: You have tried to edit a service which does not exist, or there is an error trying to access the registry.
Action: Verify service/SID name used and try again. Restart if necessary or contact Oracle Support Services.
You did not enter a pfile for autostart capability
Cause: You did not provide the parameter file for starting the database.
Action: Enter the parameter file used to start the database and retry.
The service start mode could not be set in the registry
Cause: Start mode entry in the registry for the service could not be set.
Action: Try again later, restart, or call Oracle Support Services.
Cannot open the Windows NT Service Control Manager
Cause: Service Control Manager could not be opened.
Action: Restart or call Oracle Support Services.
Cannot start already-running ORACLE - shut it down first
Cause: Instance is already started; shut it down first.
Action: Stop database before restarting.
Missing or invalid -SHUTTYPE parameter. A valid -SHUTTYPE parameter is SRVC or INST
Cause: You did not enter a valid shuttype parameter (Service or Instance).
Action: Enter parameter to shut down instance or service and try again.
Instance shutdown mode must be one of the following: a for abort, i for immediate or n for normal
Cause: You did not enter the correct mode for shutting down the database.
Action: Enter correct mode and try again.
Failed to stop Oracle Service
Cause: Failed to stop Oracle Service.
Action: Retry. If error persists, then look at system error or call Oracle Support Services.
Create Service Error
Cause: Service could not be created.
Action: Look at detail error.
A service for this SID is already created. Please enter a different SID name. No action has been taken
Cause: Service with this name already exists.
Action: Retry with a different SID.
RegOpenkeyEx failed
Cause: This is a system error due to service not existing or Windows error.
Action: Retry, restart, or call Oracle Support Services.
Please enter one of the following commands:
Create an instance by specifying the following parameters:
-NEW -SID sid | -SRVC service [-INTPWD password] [-MAXUSERS number] [-STARTMODE a|m] [-PFILE file] [-TIMEOUT secs]
Edit an instance by specifying the following parameters:
-EDIT -SID sid [-NEWSID sid] [-INTPWD passwd] [-STARTMODE a|m] [-PFILE file] [-SHUTMODE a|i|n] [-SHUTTYPE srvc|inst]
Delete instances by specifying the following:
-DELETE -SID sid | -SRVC service name
Startup services and instance by specifying the following parameters:
-STARTUP -SID sid [-USRPWD password] [-STARTTYPE srvc|inst|srvc,inst] [-PFILE filename]
Shutdown services and instance by specifying the following parameters:
-SHUTDOWN -SID sid [-USRPWD password] [-SHUTTYPE srvc|inst|srvc,inst] [-SHUTMODE a | i | n]
Query for help by specifying the following parameters: -? | -h |-help
You have entered an invalid option for the -NEW command
You have entered an invalid option for the -EDIT command
You have entered an invalid option for the -DELETE command
You have entered an invalid option for the -STARTUP command
You have entered an invalid option for the -SHUTDOWN command
Internal logic error in ORADIM
The following are common Oracle9i database connection error codes, their causes, and suggested remedies.
TNS: unable to connect to destination
Cause: OracleServiceSID service, OracleHome_NameTNSListener service, or both are not running.
Action: Ensure that both services are started.
TNS: lost contact
Cause: OracleServiceSID service, OracleHome_NameTNSListener service, or both are not running. You receive this error if you attempt to use any Oracle9i Utilities, such as SQL*Plus. This error is analogous to the following Oracle7 error: ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task.
Action: Ensure that both services are started.
unable to open RPC connection to external procedure agent
Cause: tnsnames.ora and listener.ora files have not been correctly configured to use external procedures.
Action: Reconfigure services.
at "APPLICATIONS.OSEXEC", line 0
Cause: tnsnames.ora and listener.ora files have not been correctly configured to use external procedures.
Action: Reconfigure services.
at "APPLICATIONS.TEST", line 4
Cause: tnsnames.ora and listener.ora files have not been correctly configured to use external procedures.
Action: Reconfigure services.
at line 2
Cause: tnsnames.ora and listener.ora files have not been correctly configured to use external procedures.
Action: Reconfigure services.
Both codes appear at startup
Cause: Parameter file (init.ora) or Windows services are damaged. These errors usually appear when the parameter file cannot be read by Oracle at database startup.
Action: Delete and re-create the SID and services. Make sure you are logged on as the user Administrator, or a user within the Windows Administrator's Group with full administrative rights. At the command prompt, enter: oradim -delete -sid sid where: sid is the name of your database (for example, orcl). Re-create the sid and services by entering: oradim -new -sid sid -intpwd password -startmode auto -pfile full path to init.ora
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
