5 z/OS-Specific Oracle Database Messages

This chapter documents the Oracle database server error codes unique to Oracle Database for z/OS. These errors are returned to applications and to Oracle tools and utilities that are accessing an Oracle server running on z/OS. The manner in which these error codes are displayed depends on the application, the tool, or the utility and where and how it is run. These errors are displayed with the prefix "ORA-."

The following messages are described in this chapter:

5.1 Messages ORA-04100 to ORA-04166

ORA-04100 system name buffer too small: Cause: The buffer that was supplied on a call to retrieve the system name was not large enough for the name.; Action: Report this error to Oracle Support Services.

ORA-04101 OS/390 implementation layer error: Cause: The OS/390-specific Oracle implementation layer reported an error. This message should be accompanied by additional messages, including a numeric error ID and possible system function name, return or abend code, and so forth. The error ID can be found in Chapter 6, "Server Infrastructure Error Codes".; Action: Respond as indicated for the specific error ID.

ORA-04103 database file access method I/O error: Cause: An I/O request to a database file was unsuccessful. The file types that can receive this error include tablespace, control, online log, archive log, disk backups, and other files that use VSAM linear organization and are accessed with Media Manager. This message should be accompanied by additional messages identifying the file name and/or type and numeric return and reason codes identifying the specific error.; Action: This error can result from pre allocating a file and then specifying the file to an Oracle function with an explicit file size that is greater than the actual (pre allocated) size. If this is the case, the size specified to Oracle must not exceed the actual space allocated to the file: either re-allocate the file with more space, specify a smaller size to Oracle, or omit the explicit size completely when specifying the file to Oracle. If the problem does not appear to be related to file size discrepancies, then it probably stems from an internal (software) error or hardware failure. If you have received no other indication of hardware problem (such as system log messages or errors recorded in SYS1.LOGREC), then this error should be reported to Oracle Support Services.

ORA-04104 process terminating with open database file(s): Cause: An Oracle session attempted to terminate database file activity with one or more files still open.; Action: Report this error to Oracle Support Services.

ORA-04105 invalid database file logical block size: Cause: An attempt was made to create or initialize a file with a logical block size other than 4096, 8192, 16384, or 32768 bytes.; Action: If a value other than those listed was specified, then remove the parameter or change it to one of the listed values. Otherwise, report this error to Oracle Support Services.

ORA-04107 database file close attempted with active I/O: Cause: Oracle attempted to logically close a database file while I/O requests for the file were still active.; Action: Report this error to Oracle Support Services.

ORA-04108 database file access structure error: Cause: An internal consistency check of the memory structures that are used to access a database file failed. This generally indicates a software problem, not a problem in the database file itself.; Action: Report this error to Oracle Support Services.

ORA-04109 file name buffer too small: Cause: An internal memory area that is used to hold the name of a file is too small for a particular file name.; Action: Report this error to Oracle Support Services.

ORA-04110 archive log name buffer too small: Cause: An internal memory area that is used to hold the name of an archive log is too small for a particular file name.; Action: Report this error to Oracle Support Services.

ORA-04111 unable to allocate memory for process global area: Cause: During Oracle session initialization, a request for virtual memory in the server address space for the process global area (PGA) failed.; Action: Either increase the region size available to the Oracle server (REGION parameter on the JCL EXEC statement of the server JCL procedure) or increase the number of server address spaces (MAXAS parameter of the Oracle subsystem DEFINE SERVICE command).

ORA-04112 server executable name could not be determined: Cause: During Oracle session initialization, an attempt to retrieve the database server program (load module) name failed.; Action: Report this error to Oracle Support Services.

ORA-04113 client executable name could not be determined: Cause: During Oracle session initialization, an attempt to retrieve the client's program name failed.; Action: Report this error to Oracle Support Services.

ORA-04114 database file opened for input was found to be empty: Cause: Oracle attempted to open a database file for input, but the file was found to be empty (the high-used RBA stored in the ICF catalog structure is zero).; Action: If this error does not appear to result from a user error (such as accidentally deleting and redefining a database file), then it should be reported to Oracle Support Services.

ORA-04115 database file identification block is invalid or unreadable: Cause: When opening a database file, the self-identifying block (CI 0) in the file did not contain the correct information, or the block could not be read due to an I/O error or other failure.; Action: If this occurs when adding a file to the database, make sure that the file name is not that of an existing (non-Oracle) VSAM object. Otherwise, report this error to Oracle Support Services.

ORA-04116 unable to allocate memory for database file validation buffer: Cause: When opening a database file, an attempt to allocate server region memory for a buffer for the file's self-identifying block failed.; Action: Either increase the region size available to the Oracle server (REGION parameter on the JCL EXEC statement of the server JCL procedure) or increase the number of serve address spaces (MAXAS parameter of the Oracle subsystem DEFINE SERVICE command).

ORA-04117 improper database file I/O request: Cause: An improper request (such as a write to a file that was opened for read only) was issued for a database file.; Action: Report this error to Oracle Support Services.

ORA-04118 invalid database file type code: Cause: A request to create, access, or delete a database file passed an unknown internal file type code.; Action: Report this error to Oracle Support Services.

ORA-04119 message file read request error: Cause: A request to read a product message file specified an incorrect file offset or length.; Action: Report this error to Oracle Support Services.

ORA-04120 message file name buffer too small: Cause: An internal memory area that is used to hold a message file name was too small for a particular name.; Action: Report this error to Oracle Support Services.

ORA-04121 message file name invalid: Cause: An internally-generated message file name was invalid.; Action: Report this error to Oracle Support Services.

ORA-04122 invalid connect authorization type: Cause: During database logon processing, a call was made to the connection authority checking routine with an unknown connection type code.; Action: Report this error to Oracle Support Services.

ORA-04123 invalid parameter to sltln: Cause: The SLTLN name translation routine was called with invalid arguments. The input or output strings were either NULL or 0 length.; Action: Report this error to Oracle Support Services.

ORA-04124 sltln output buffer overflow: Cause: The SLTLN name translation routine was called with an output buffer that was too short for the input name.; Action: Report this error to Oracle Support Services.

ORA-04125 skgm out of memory: Cause: Out of memory.; Action: Consult the trace file for details.

ORA-04126 skgm shared memory realm does not exist: Cause: Unable to locate shared memory realm.; Action: This error is expected if you try to perform a SHUTDOWN of an oracle instance that is not started. Otherwise, report this error to Oracle Support Services.

ORA-04127 slkhst could not perform host operation: Cause: Operating system call failed.; Action: Report this error to Oracle Support Services.

ORA-04128 sllfop open error; could not open file: Cause: Open call returned an error.; Action: Ensure that the file exists.

ORA-04129 sllfop invalid processing option, incorrect format: Cause: Processing option passed is of incorrect format.; Action: Report this error to Oracle Support Services.

ORA-04130 sllfop filestat error: Cause: Possible bad data passed to filestat.; Action: Report this error to Oracle Support Services.

ORA-04131 sllfop invalid recordsize: Cause: Input record size was larger than user specified record size.; Action: Report this error to Oracle Support Services.

ORA-04132 sllfop no memory for read buffer: Cause: Allocation of read buffer failed.; Action: Report this error to Oracle Support Services.

ORA-04133 sllfrb no memory for internal structure: Cause: Allocation of memory for internal structure failed.; Action: Report this error to Oracle Support Services.

ORA-04134 sllfsk skip option not supported: Cause: Skip option not supported with linked-in loader.; Action: Report this error to Oracle Support Services.

ORA-04135 sllfsk end of logical record: Cause: While attempting to read the length portion of a varying length field, the end of the logical record was reached.; Action: Report this error to Oracle Support Services.

ORA-04136 sllfcf bad close: Cause: Close call returned an error.; Action: Report this error to Oracle Support Services.

ORA-04137 sllfrd bad read: Cause: Read call returned an error.; Action: Report this error to Oracle Support Services.

ORA-04138 soamon connection error: Cause: Connection error.; Action: Report this error to Oracle Support Services.

ORA-04139 internal name translation length error: Cause: The length of a name to be translated is invalid.; Action: Report this error to Oracle Support Services.

ORA-04140 internal name translation buffer too small: Cause: An internal buffer for translating logical names was too small for the result.; Action: Report this error to Oracle Support Services.

ORA-04141 invalid backup device internal structure: Cause: The internal data structure which describes an RMAN channel failed a validity test.; Action: Report this error to Oracle Support Services.

ORA-04142 backup file still open on device being released: Cause: RMAN attempted to release or start a new operation on a channel that still has a file open or a proxy operation in progress.; Action: Report this error to Oracle Support Services.

ORA-04143 channel not allocated for I/O: Cause: RMAN attempted to open a backup file or start a proxy operation on a channel that was allocated for maintenance activity only.; Action: Report this error to Oracle Support Services.

ORA-04144 invalid data block length for backup file: Cause: Oracle supplied an invalid data block length on a request to create a backup.; Action: Report this error to Oracle Support Services.

ORA-04145 invalid request for asynchronous I/O: Cause: A backup I/O request specified an unsupported mode of operation.; Action: Report this error to Oracle Support Services.

ORA-04146 invalid backup file internal structure: Cause: The internal data structure which describes a backup file failed a validity test.; Action: Report this error to Oracle Support Services.

ORA-04147 proxy backup/restore operation sequence error: Cause: Internal function calls related to RMAN proxy backup or restore were made in the wrong sequence.; Action: Report this error to Oracle Support Services.

ORA-04148 insufficient server virtual memory for proxy operation: Cause: Virtual memory for an internal data structure related to RMAN proxy backup or restore could not be allocated. This can happen if the target server address space is very low on virtual memory.; Action: Start a new RMAN session in the target server and retry the proxy operation. If the problem persists, report the error to Oracle Support Services.

ORA-04149 invalid backup channel device type: Cause: An invalid TYPE was specified on an RMAN ALLOCATE CHANNEL command.; Action: For a z/OS OSDI server, TYPE must be either DISK or "EDM0".

ORA-04150 invalid backup channel device name: Cause: An invalid NAME was specified on an RMAN ALLOCATE CHANNEL command.; Action: No device names are supported for z/OS servers. Remove the name from the ALLOCATE CHANNEL command and make sure that you have specified a valid TYPE.

ORA-04151 invalid destination for Oracle-Managed File: Cause: One of the parameters DB_CREATE_FILE_DEST or DB_CREATE_ONLINE_LOG_DEST_n has been specified with a value that is unacceptable on z/OS.; Action: Correct the parameter value and retry the STARTUP or ALTER SYSTEM request that received the error.

ORA-04152 invalid characters in file path name: Cause: The characters '..' were found in a file path name. This is not allowed.; Action: Correct the file path name and retry.

ORA-04153 invalid normalized file name length: Cause: The length of a normalized file name either exceeds the length of the caller's buffer or the allowed maximum.; Action: Report this error to Oracle Support Services.

ORA-04154 invalid generated file name length: Cause: The length of a generated file name exceeds the length of the caller's buffer.; Action: Report this error to Oracle Support Services.

ORA-04155 invalid tablespace name for OMF name generation: Cause: The tablespace name that would be used as part of name generation for an Oracle-managed tablespace file is invalid.; Action: Report this error to Oracle Support Services.

ORA-04156 invalid Oracle-managed filename template: Cause: A filename template used for generating an Oracle- managed file name does not contain the expected substitution marker.; Action: Report this error to Oracle Support Services.

ORA-04157 alert log access is not available: Cause: This error arises normally when a function attempts to access (read) the instance alert log, which is not supported on z/OS.; Action: None.

ORA-04158 error encountered during HOST command: Cause: An error was encountered during the execution of a HOST command; Action: Report this error to Oracle Support Services.

ORA-04159 HOST command unable to reserve storage: Cause: An attempt to reserve storage during the processing of a HOST command was unsuccessful.; Action: Ensure adequate storage is available to your process and try the command again.

ORA-04160 get thread ID encountered an internal error: Cause: An error was encountered while processing an internal get thread ID request.; Action: Report this error to Oracle Support Services.

ORA-04161 get process ID encountered an internal error: Cause: An error was encountered while processing an internal get process ID request.; Action: Report this error to Oracle Support Services.

ORA-04162 get program name encountered an internal error: Cause: An error was encountered while processing an internal get program name request.; Action: Report this error to Oracle Support Services.

ORA-04163 get user name encountered an internal error: Cause: An error was encountered while processing an internal get user name request.; Action: Report this error to Oracle Support Services.

ORA-04164 get terminal name encountered an internal error: Cause: An error was encountered while processing an internal get terminal name request.; Action: Report this error to Oracle Support Services.

ORA-04165 Unable to determine file logical block size: Cause: An attempt was made to determine the logical block size of an Oracle database file, but the file was found to be newly-created (its high-used RBA is zero). The logical block size could not be determined.; Action: Unless you have created this situation by manually deleting and redefining an Oracle database file, this is an unexpected error and should be reported to Oracle Support Services.

ORA-04166 incorrect SGA_MAX_SIZE value: Cause: SGA_MAX_SIZE value is too large.; Action: Remove SGA_MAX_SIZE parameter.