Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
The error messages in this section are Oracle operating system-dependent (OSD) messages that are issued in response to an error condition in Windows NT. Each message in this section triggers an Oracle8 Enterprise Edition database error message, listed in the previous Section , "Oracle8 Enterprise Edition Database Error Messages".
Logical block size mismatch
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.
Invalid logical block size
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.
Unable to open file
Cause: The specified path or filename is invalid, or the destination device is full. This error can also be caused by insufficient Windows NT file handles.
Action: Make sure that the path and file exist, and that 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.
Invalid file header
Cause: The file is corrupted.
Action: Recover the file.
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.
Truncated read
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.
Truncated write
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 that 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.
File size mismatch
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.
Unable to read line from 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.
Unable to close file
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 filename 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.
Unable to set file pointer
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.
Unable to set eof file marker
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.
Unable to read 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.
Unable to write 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.
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.
Unable to delete 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.
Invalid question asked
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Worldwide Customer Support.
Invalid parameter passed
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.
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 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 thread died holding the semaphore.
Action: Restart Oracle8 instance.
Thread information not found
Cause: An Oracle8 thread died without deleting its information.
Action: Restart Oracle8 instance.
Maximum number of Oracle threads reached
Cause: The maximum number of Oracle8 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.
Cannot post thread
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Worldwide Customer Support.
Bad thread list semaphore
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Worldwide Customer Support.
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.
Record size too large
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 Server 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.
Illegal option specified
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Worldwide Customer Support.
Internal buffer overflow
Cause: This is an internal error, not normally expected to occur.
Action: Contact Oracle Worldwide Customer Support.Support.
Translations nested too deep
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.
Stdin not responding
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.
No password given
Cause: An attempt was made to connect as 'internal' without a password.
Action: Enter a valid password when connecting as internal.
No password found
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 logins 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.
