Oracle8
Enterprise Edition Getting Started
Release 8.0.4 for Windows NT A55928-01 |
|
This appendix lists the error messages, causes, and corrective
actions that are specific to the installation and operation of Oracle8
Enterprise Edition for Windows NT.
Specific topics discussed are:
Keep a log of error messages you receive from the Oracle8 Utilities by redirecting the messages to a file. You can record the contents of normal utility messages by using the LOGFILE parameter discussed in Oracle8 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 the Export utility:
C:\> EXP80 USERNAME/PASSWORD PARFILE=FILENAME >FILE1.LOG 2>FILE2.ERR
In this command line, FILE1.LOG receives the standard output
from Export, while FILE2.ERR receives the standard error messages.
This section lists error messages that can occur while using Oracle Installer. Most Oracle Installer error messages are accompanied with corrective information on the screen; therefore, they are not listed in this appendix. This appendix lists error messages in alphabetical order and provides the probable cause and corrective action.
This section lists error messages issued by the Oracle8 database. Each one is triggered by an operating system-dependent (OSD) message specific to Windows NT that specifies the error condition signalled. The OSD messages appear in the next section. When you receive one of these messages, look up the accompanying OSD message number listed in the section, "Codes 04000-04999: Windows NT-Specific Oracle Messages" for an explanation of the error.
The error messages in this section are Oracle operating system-dependent (OSD) messages issued in response to an error condition in Windows NT. Each message in this section triggers an Oracle8 database error message, listed in the previous section, "Codes 09200-09499: Oracle8 Database Messages".
Cause: The database block size specified in the initialization
parameter file does not match the block size of the actual database files.
Action: Use matching logical block sizes.
Cause: The 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.
Cause: The specified path or file name is invalid,
or the destination device is full. This error can also be caused by insufficient
Windows NT file handles.
Action: Make sure the path and file exist, and the
device has free space. If this fails, increase the number of Windows NT
file handles.
Unable to read file header block
Cause: The media has been damaged.
Action: Recover the file if necessary, and verify
that Windows NT is functioning correctly.
SetFilePointer() failure, unable to read from file
Cause: There was an unexpected return from the Windows
NT system service, SetFilePointer().
Action: Check the operating system error code and
consult the Windows NT documentation.
ReadFile() failure, unable to read from file
Cause: There was an unexpected return from the Windows
NT system service, ReadFile().
Action: Check the operating system error code and
consult the Windows NT documentation.
Cause: The system encountered an unexpected end-of-file,
which is due to damaged media.
Action: Verify that the file is not damaged.
WriteFile() failure, unable to write to file
Cause: There was an unexpected return from the Windows
NT system service, WriteFile().
Action: Check the operating system error code and
consult the Windows NT documentation.
Cause: The destination device is full or the media
is damaged.
Action: Verify that the device has free space and
the file is not damaged.
<create> option specified, file already exists
Cause: The file you attempted to create already exists.
Action: Delete the existing file or use the REUSE
option in the SQL statement.
GetFileInformationByHandle() failure, unable to obtain
file info
Cause: There was an unexpected return from the Windows
NT system service, GetFileInformationByHandle().
Action: Check the operating system error code and
consult the Windows NT documentation.
Cause: The file to be re-used is either too large
or too small.
Action: Specify the correct file size or delete the
existing file.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
Cause: The media has been damaged.
Action: Recover the 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 the Windows
NT system service.
Action: Check the operating system error code and
consult the Windows NT documentation.
Error queuing an asynchronous I/O request
Cause: There was an unexpected return from the Windows
NT system service.
Action: Check the operating system error code and
consult the Windows NT documentation.
Unable to open the specified RAW device
Cause: An invalid path or file name was specified
or the device is full.
Action: Make sure the file exists and/or device is
not full; verify that the operating system is functioning correctly.
Unable to access the specified directory or device
Cause: An invalid path name was specified.
Action: Make sure the directory or device exists
and is accessible.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
SleepEx() failure, unable to Sleep
Cause: There was an unexpected return from the Windows
NT system service.
Action: Check the operating system error code and
consult the Windows NT documentation.
Cause: This error is caused by an operating system
error or by damaged media.
Action: Check the operating system error code (if
available) and consult the Windows NT documentation. If no operating system
error code is presented, verify that the media is not damaged.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Malloc() failure, unable to allocate memory
Cause: The program is out of memory.
Action: Shut down all unnecessary processes or install
more memory in the computer.
Invalid SGA: SGA not initialized
Cause: The System Global Area (SGA) has been allocated
but not initialized.
Action: Wait until the STARTUP has completed before
attempting to connect.
Unable to open/create file for shared memory object
Cause: There was an unexpected return from the Windows
NT system service, CreateFile().
Action: Check the operating system error code and
consult the Windows NT documentation.
Unable to attach to SGA: SGA does not exist
Cause: The 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 the Windows
NT system service, MapViewOfFileEx().
Action: Check the operating system error code and
consult the Windows NT documentation.
Shared memory (SGA) mapped to wrong address
Cause: There was an unexpected return from the Windows
NT system service, MapViewOfFileEx().
Action: Check the operating system error code and
consult the Windows NT documentation.
Unable to allocate memory with VirtualAlloc
Cause: The 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 the Windows
NT system service, VirtualFree().
Action: Check the operating system error code and
consult the Windows NT documentation.
Unable to protect memory with VirtualProtect
Cause: There was an unexpected return from the Windows
NT system service, VirtualProtect().
Action: Check the operating system error code and
consult the Windows NT documentation.
Unable to begin another thread
Cause: The 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 Worldwide Customer Support.
DosSetPriority() failure, unable to set process priority
Cause: There was an unexpected return from the Windows
NT system service, DosSetPriority().
Action: Check the operating system error code and
consult the Windows NT documentation.
DosKillProcess() failure, unable to kill process
Cause: There was an unexpected return from the Windows
NT system service, DosKillProcess().
Action: Check the operating system error code and
consult the Windows NT documentation.
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 the Windows
NT system service, CreateProcess().
Action: Check the operating system error code and
consult the Windows NT documentation.
Invalid priority specified in CONFIG parameter ORACLE_PRIORITY
Cause: The 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 the Windows
NT system service, OpenProcess().
Action: Check the operating system error code and
consult the 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 Worldwide Customer Support.
Timeout waiting for thread semaphore
Cause: An Oracle8 database thread died holding the
semaphore.
Action: Restart Oracle8 database instance.
Cause: An Oracle8 database thread died without deleting
its information.
Action: Restart Oracle8 database instance.
Maximum number of Oracle threads reached
Cause: The maximum number of Oracle8 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 Worldwide Customer Support.
Oracle thread unable to CreateEvent()
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Bad function code supplied to ssthreadop
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Unable to find file handle for that thread
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Unable to retrieve system username for current user
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Target thread is currently busy
Cause: The target thread is processing an oradebug
command.
Action: Wait and re-issue command.
Unable to get the threads context
Unable to set the threads context
Unable to suspend the target thread
Unable to resume the target thread
Unable to read complete record from data file
Cause: The data file ended in the middle of a record.
This error occurs when loading files with a fixed record length.
Action: Verify that the data file is of the correct
length and contains complete records.
Cause: The specified record size is too large to
load.
Action: Reduce record size and reload the data.
Invalid record type and/or load options
Cause: The control file's Windows NT file processing
options string contains an invalid option or keyword.
Action: Set the Windows NT file processing options
string to an acceptable value.
Unable to acquire internal semaphore for process
Cause: Oracle8 database has exceeded the maximum
number of connections.
Action: Delete any unused connections and try again.
WaitForSingleObject() failure, unable to obtain semaphorex
Cause: There was an unexpected return from the Windows
NT system service, WaitForSingleObject().
Action: Check the operating system error code and
consult the Windows NT documentation.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Cause: This is an internal error, not normally expected
to occur.
Action: Contact Oracle Worldwide Customer Support.
Cause: The program encountered too many intermediate
translations while attempting to translate a configuration variable.
Action: Simplify the values of configuration parameters
to include fewer intermediate translations.
Text contains no translatable elementsx
Cause: The program cannot recognize variables in
the text to be translated.
Action: Check and, if necessary, correct the text
to be translated.
Cause: The system is unable to receive input from
the standard input stream.
Action: Verify that the process has access to an
input device.
Unable to spawn process via system()
Cause: The system is out of memory or the executable
is invalid.
Action: Shut down unnecessary processes; install
more memory in the computer. Verify the name of the executable.
Password for 'internal' is incorrect
Cause: An attempt was made to connect as 'internal'
with an invalid password.
Action: Verify that the password is correct and try
again.
Cause: An attempt was made to connect as 'internal'
without a password.
Action: Enter a valid password when connecting as
internal.
Cause: Oracle was unable to locate and retrieve the
password for 'internal'.
Action: Verify that Oracle is installed and configured
correctly.
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 the system time is correct on
the computer.
Unable to translate the 'USERNAME' configuration variable
on server
Cause: The 'USERNAME' configuration parameter variable
on the host is not properly set.
Action: Verify the 'USERNAME' variable is set.
'REMOTE_OS_AUTHENT' variable not set to TRUE'
Cause: For remote operating system log on to function,
the 'REMOTE_OS_AUTHENT' parameter must be set to TRUE.
Action: Shut down and start up the instance with
'REMOTE_OS_AUTHENT = TRUE' in the initialization parameter file.
The Windows NT Group name is too long for internal buffer
Cause: The Windows NT Group name is too long.
Action: Use a shorter Windows NT group name.