Skip Headers

Oracle8i Server User's Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD

Part Number A95463-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

A
Oracle Messages

This appendix lists the Oracle8i Release 3 for Fujitsu Siemens Computers BS2000/OSD messages together with possible causes and suggested actions. The messages shown in this chapter may be accompanied by additional text when displayed on screen. This text identifies the function that detected the problem, and can include internal status codes and/or BS2000 system macro return codes. These codes can be helpful to your Oracle Customer Support Representative in determining the cause of a problem.

Sometimes, for example in the early stages of initialization when the message components are not yet available, the Oracle Server cannot issue a regular Oracle message. If this occurs, the Oracle Server calls the ILCS task termination routine, or it issues a TERM macro directly, giving the message number as the user termination code. You can use this message number to find the explanation in this appendix.

ORA-5000: ORACLE termination routine called

Cause: The termination routine of the Oracle Server runtime system has been called due to a fatal error.

Action: If you do not know why the Oracle Server program terminated, or how to resolve this problem, contact your Oracle Customer Support Representative.

ORA-5001: Unsupported BS2000 Version

Cause: The active version of the BS2000/OSD operating system is not supported by Oracle8i Release 3.

Action: Upgrade to a more recent BS2000/OSD version.

ORA-5002: Fatal error: called from non-ILCS program

Cause: In a precompiler or OCI application, the Oracle Server is called from a program that does not run in an ILCS environment. The Oracle Server does not support non-ILCS programs.

Action: Make sure that your application program runs in ILCS mode. Some programming languages (for example, FOR1, PL/I) require specific options for ILCS. See your Fujitsu Siemens Computers documentation for further information.

ORA-5003: Fatal error: ILCS PCD cannot be verified

Cause: In a precompiler or OCI application, the Oracle Server is called with a save area that is marked as an ILCS save area but does not point to a proper PCD (ILCS global area). The problem is either that memory has been overwritten, or that. the Oracle Server is called from a program that does not run in an ILCS environment. The Oracle Server does not support non-ILCS programs.

Action: Make sure that your application program runs in ILCS mode. Some programming languages (for example, FOR1, PL/I) require specific options for ILCS. See your Fujitsu Siemens Computers documentation for further information.

ORA-5004: Fatal error: stack overflow, extension failed

Cause: A call to a function required an extension of the current call stack segment. This extension failed (the corresponding ILCS routine returned the error).

Action: Make sure that the user address space is large enough (in the JOIN entry) and that there is no temporary memory saturation. Then re-run the program. If you need further help, contact your Oracle Customer Support Representative.

ORA-5005: Error: IT0INITS called in PROLOD

Cause: This is an internal error and should not occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5007: failed to load OSNTAB

Cause: This message will normally be preceded by a BS2000 BLS-nnnn message. The most likely reason is that the ORALOAD library cannot be found.

Action: Contact your Database Administrator about the ORALOAD library. If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5008: failed to load requested network driver

Cause: This message will be normally preceded by a BS2000 BLS-nnnn message. The most likely reason is that the ORALOAD library cannot be found.

Action: Contact your Database Administrator about the ORALOAD library. If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5009: osnsgl: user connects invalid in kernel

Cause: A database link was set up using the single-task driver (S:). This is invalid, as the single-task driver can only be used for call connections on the user side.

Action: Select a different network driver for the database link.

ORA-5010: bad filename length

Cause: Buffer overflow while building/translating a filename. This could be caused by specifying an excessively long file name in the ORAENV file.

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5011: bad file size

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5012: bad block size

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5013: bad filename parse

Cause: A filename being analysed is not well-formed for Oracle Server purposes.

Action: Correct the filename and re-run the program.

ORA-5014: sfcopy: non-matching block size

Cause: In a partial database file copy, source and target file have different blocksizes. This may indicate an internal error and should not normally occur.

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5015: text file open failed

Cause: An Oracle Server text or command file cannot be opened. Either the filename is wrong, the file has not been properly initialized, or the file is not accessible.

Action: Correct the problem and restart the Oracle Server. If this occurred when you issued the STARTUP command, check your initialization file for the correct specification of the database files.

ORA-5016: text file close failed

Cause: Attempt to close an Oracle Server file has failed. This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5017: file open failed

Cause: An Oracle Server database file cannot be opened. Either the filename is wrong, the file has not been properly initialized, or the file is not accessible (for example a file may not be accessible for a cross-userid single-task client).

Action: Correct the problem and restart the Oracle Server. If this occurred when you issued the STARTUP command, check your initialization file for the correct specification of the database files.

ORA-5018: file seek failed

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5019: file write failed

Cause: An I/O error occurred while writing to an Oracle Server file.

Action: If the error cannot be identified as one caused by a disk malfunction, either contact the System Administrator, or contact your Oracle Customer Support Representative.

ORA-5020: write block outside of file

Cause: An attempt was made to write a block of an Oracle Server file that does not exist (block number < 1 or > file size). This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5021: file read failed

Cause: An I/O occurred while reading an Oracle Server file.

Action: If the error cannot be identified as one caused by a disk malfunction, either contact the System Administrator, or contact your Oracle Customer Support Representative.

ORA-5022: read block outside of file

Cause: An attempt was made to read a block of an Oracle Server file that does not exist (block number < 1 or > file size). This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5023: file close failed

Cause: The attempt to close an Oracle Server file failed. This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5025: sfccf:file mismatch. Trying to reuse a file with different size

Cause: When trying to reuse a database file, the filesize specified differs from the actual size of the existing file.

Action: Specify the correct filesize (remember to subtract one logical block for the implicit header block), or leave the size unspecified, or use a different filename if you want to create a larger or smaller database file.

ORA-5026: file does not exist

Cause: An attempt was made to access a database file which no longer exists.

Action: Contact your Database Administrator who may know why this error has occurred. If your Database Administrator cannot find the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5027: file does exist

Cause: When attempting to create a new file, the file is found to exist and not be empty.

Action: If the error occurred in a "create database", retry with the "reuse" option. Otherwise use a different file name or check whether the file can be erased.

ORA-5028: file is not a dbfile

Cause: The database (or log, or control) file to be opened does not contain the proper identification for such a file.

Action: Check for wrong file specification.

ORA-5029: illegal use-option

Cause: Internal error. Function sfccf was called with an illegal option.

Action: Contact your Oracle Customer Support Representative.

ORA-5030: SID not defined

Cause: When the system id was required (typically, to substitute the "?" in names, for example, in filenames set by the initialization file), it was not yet defined. This could be caused by a missing ORAENV file or a missing ORASID in that file.

Action: Ensure that the ORAENV file definition is correct and re-run the program.

ORA-5031: SID translation failure

Cause: The system id is syntactically incorrect.

Action: Ensure that the ORASID definition is correct and re-run the program.

ORA-5032: bad name parse

Cause: The translation of a file name, or other name containing variable parts, failed. The error may be caused by a wrong specification in the ORAENV file.

Action: Ensure that the ORAENV variable assignments are correct. If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5033: bad environment values

Cause: One or more of the values specified in the ORAENV file are invalid.

Action: Ensure that you specified legal values in the ORAENV file (see the appendix "ORAENV Variables" in your Installation and Database Administration Guide or your User's Guide for further information).

ORA-5034: bad seal

Cause: Internal error. An internal file control structure is found to be corrupt.

Action: Contact your Oracle Customer Support Representative.

ORA-5035: host command not executed

Cause: A BS2000 command, argument of a HOST or #HOST command, is invalid or too long.

Action: Enter a valid HOST command.

ORA-5036: bad user id (length)

Cause: Internal buffer overflow while building a filename from variable components.

Action: Ensure that the ORAUID value specified in the ORAENV file is correct. If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5037: /CANCEL command not executed

Cause: A background job could not be cancelled. The background task may have already been terminated.

Action: If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5038: SID has illegal length

Cause: The system identifier specified in either the ORAENV file or as part of a connect string exceeds 4 characters in length.

Action: Specify a correct value.

ORA-5039: Recursive entry to ssodrv

Cause: The Oracle Server kernel has been re-entered at the top. This should not happen.

Action: Make sure that your user program does not incorrectly call Oracle Server functions from within an interrupt handling routine (signal routine, contingency). If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5040: no more dynamic memory

Cause: Request memory failed in file-management components. This is probably caused by a user address space that is too small.

Action: Make sure that the user address space is large enough (in the JOIN entry) and that there is no temporary memory saturation. Then re-run the program. If you need further help, contact your Oracle Customer Support Representative.

ORA-5041: Interrupt in soarch

Cause: The archiver process was unexpectedly interrupted.

Action: If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5042: soarch: Buffer overflow

Cause: The archiver process detected an internal buffer overflow.

Action: If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5043: Archive control string too long

Cause: The archive control string is too long.

Action: Shorten this parameter and restart the database.

ORA-5044: Archive generated filename too long

Cause: The filename is generated from the values of the initialization parameters log_archive_format and log_archive_dest. This has resulted in a filename that is too long.

Action: Issue the command ALTER SYSTEM ARCHIVE LOG START TO VALID_DEST where VALID_DEST is a valid BS2000 filename.

ORA-5045: Archive file creation/open error

Cause: The archive file is normally allocated dynamically. Either this or the subsequent open failed. Possible causes are either insufficient space left on disk, or a bad archive file allocation parameter in ORAENV.

Action: Make sure that the optional ORAENV parameter is correct and that sufficient disk space is available.

ORA-5046: Archive control string error

Cause: The archive filename or control parameters are incorrect.

Action: Correct the parameters.

ORA-5050: PGA (fixed part) could not be allocated

Cause: Probable operating system error or internal error.

Action: Contact your Oracle Customer Support Representative.

ORA-5051: cannot allocate var. PGA

Cause: During creation of the PGA, required dynamic memory could not be allocated.

Action: Verify that the user address space is large enough and that if an application program produced the error, the program is not consuming excessive memory. Otherwise contact your Oracle Customer Support Representative.

ORA-5052: error deleting var. PGA

Cause: During deletion of the PGA, dynamic memory could not be released. This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5053: invalid or missing PGA_BASE

Cause: An invalid value for the PGA_BASE parameter has been specified in the DBA ORAENV file.

Action: Specify a correct value.

ORA-5054: invalid or missing PGA_SIZE

Cause: An invalid value for the PGA_SIZE environment variable has been specified in the DBA ORAENV file. You should never need to change the default value for the PGA_SIZE environment variable.

Action: Use the default value for the PGA_SIZE environment variable. If this does not solve the problem, contact your Oracle Customer Support Representative.

ORA-5055: address range for PGA (fixed part) is not free

Cause: The address range described by the PGA_BASE and PGA_SIZE ORAENV variables is not available for allocation. This may be due to overlapping PGA, SGA, and KERNEL areas, or to an application program which has occupied memory in this area. If you did not specify a value for PGA_BASE, the default may be inappropriate for your case.

Action: See the section "Address Space Planning" in the "Oracle Server System Architecture and Implementation" chapter of your Installation and Database Administration Guide for further information.

ORA-5056: no more context space

Cause: During processing of a SQL request, dynamic memory could not be allocated. This could happen when very complex requests are being processed and there is not enough memory available.

Action: Verify that the user address space is large enough and that your application program (if the error occurred when you were using an application program) is not using excessive memory. Otherwise, contact your Oracle Customer Support Representative.

ORA-5058: assert failed: SGA not mapped

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5059: assert failed: not in kernel

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5060: SGA not created

Cause: After you issued the STARTUP command, the SGA shared memory pool could not be created.

Action: Verify that you are not trying to start the database while it is running and that the database system id is not being used for two different databases. Otherwise, contact your Oracle Customer Support Representative.

ORA-5061: SGA attach failed

Cause: Connection to the SGA shared memory pool could not be established. This may have happened if you used the wrong system id, or if the database you expected to be running is not running.

Action: Verify that it is is not one of the above causes (check with your Database Administrator). Otherwise, contact your Oracle Customer Support Representative.

ORA-5063: SGA base invalid

Cause: An invalid value has been specified for the SGA_BASE parameter in the ORAENV file.

Action: This value is not normally needed. If specified, it must be a hexadecimal value giving the full virtual address for the SGA memory pool. Correct the value and re-issue the STARTUP command.

ORA-5064: cannot allocate SGA

Cause: After creating the memory pool, the REQMP to allocate the space failed. Probable operating system error.

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5065: SGA not deleted

Cause: When attempting to detach from the SGA, the DISMP system macro returned an error.

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5066: SGA address space conflict

Cause: The SGA cannot be placed at the requested address range, because the range is already partly used. The SGA start address is defined by the ORAENV variable, SGA_BASE; its size is determined by various initialization file parameters such as processes, buffers, and so on.

Action: See the section on "Address Space Planning" in the chapter "Oracle Server System Architecture and Implementation" of the Installation and Database Administration Guide, and adjust the relevant initialization file and ORAENV variables. Inspect the JOIN entry for your address space limit. Contact your System Administrator to find out about shared subsystems and their placement in the address space. Make sure that you do not overlap with the Oracle Server kernel.

ORA-5067: SGA: address space saturation

Cause: When the SGA is being allocated, the operating system reported that the virtual address space is saturated.

Action: Contact your System Administrator about paging area size and current overall system load.

ORA-5068 SGA still active, should not be

Cause: When the SGA is being created during startup, it is found that the SGA memory pool is still in use (although the databases should be shut down). This may be caused by a hanging single-task, user task or a network server task.

Action: Check for such hanging tasks. Cancel these tasks, then restart the database.

ORA-5069: Unexpected SGA memory pool problem

Cause: The ENAMP macro returned an unexpected error code.

Action: Contact your Oracle Customer Support Representative.

ORA-5070: cannot enable TPA ser.item

Cause: Probable operating system error.

Action: Contact your Oracle Customer Support Representative.

ORA-5071: cannot ENQ on TPA ser.item

Cause: Probable operating system error.

Action: Contact your Oracle Customer Support Representative.

ORA-5072: cannot enable post/wait item

Cause: Probable operating system error.

Action: Contact your Oracle Customer Support Representative.

ORA-5073: error in post

Cause: An interprocess communication operation failed.

Action: Check that the database is running correctly (all required background tasks have to be up). If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5074: error in wait

Cause: An interprocess communication operation failed.

Action: Check that the database is running correctly (all required background tasks have to be up). If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5075: error in task table manager

Cause: Internal error.

Action: Contact your Oracle Customer Support Representative.

ORA-5076: error setting spid

Cause: Probable operating system error.

Action: Contact your Oracle Customer Support Representative.

ORA-5077: cannot enable HIA event

Cause: Probable operating system error. The HIA (Here I Am) event item is used during startup to communicate between a started background task and the invoking SQL*DBA program.

Action: Contact your Oracle Customer Support Representative.

ORA-5078: create process failure

Cause: When you issued the STARTUP command, a background job could not be started successfully.

Action: Check for any job scheduling problems and that any BGJPAR entry in the ORAENV file is correct. If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5079: internal asynchronous IO error

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5101: bind-error xxxxxxxx for module/library

Cause: The Oracle Server/UTM attach module could not be loaded. One possible reason is that the Oracle Server has been installed under a userid different from $ORACL817 and that the installation procedure has not executed correctly.

Action: Ensure that the ORAUID definition in the ORAENV file is correct. Otherwise, contact your Oracle Customer Support Representative.

ORA-5102: module verification failure: ORADBCN@

Cause: The UTM application has probably been link-edited with an Oracle Server version different from the Oracle Server version used at execution.

Action: Re-link the UTM application. If the error persists, contact your Oracle Customer Support Representative.

ORA-5103: generated TSKM too short

Cause: The TSKM area was overwritten by the Oracle Server.

Action: Change the parameter LTHTSKM in the KDCDB / KDCDBO macro.

ORA-5104: generated TAM too short

Cause: The TAM area was overwritten by the Oracle Server.

Action: Change the parameter LTHTAM in the KDCDB / KDCDBO macro.

ORA-5110: cannot attach to memory pool

Cause: Invalid pool ID parameter xxx_MPID or operating system error.

Action: Check the ORAENV parameter xxx_MPID (at most 4 characters of the set [A...Z],[0...9]) or contact your Oracle Customer Support Representative.

ORA-5111: error attaching to memory pool

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5112: error creating memory pool

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5114: bad pool base

Cause: An invalid value for the base address parameter of the shared pool (i.e. COM_BASE, JVM_BASE, etc ...) has been specified in the ORAENV file.

Action: If this value is specified, it must be a hexadecimal value giving the full virtual address for the base address of a memory pool. Correct the value and restart the database.

ORA-5116: cannot load shared code into pool

Cause: Shared code could not be loaded into the specified memory pool. Generally, this message will be preceded by a BLS-nnnn message from the operating system.

Action: Make sure that the ORALOAD linkname identifies the correct ORALOAD library. Then restart the program. If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5117: cannot attach to socket subsystem

Cause: An application could not be bound to the sockets subsystem. Generally this message will be preceeded by a BLS-nnnn message from the operating system.

Action: Contact your Oracle Customer Support Representative.

ORA-5118: ORACLE PCD slot not accessible

Cause: The current task is trying to attach to the ORACLE PCD slot but cannot find this slot.
This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5119: module verification failed

Cause: The version of the shared loaded module does not match the version of the connection module on the user side.

Action: Contact your Oracle Customer Support Representative.

ORA-5120: waiting for shared module to be loaded timed out

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5121: waiting for initialization of shared module timed out

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5126: Missing IT0PCD address

Cause: The ILCS runtime link-library is probably missing.

Action: Contact your System Administrator.

ORA-5127: PARAM-LIST AT CALL ORACLE NOT OK

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5128: COMMIT/ROLLBACK/CONNECT NOT ALLOWED IN UTM-PROGRAM

Cause: Illegal SQL COMMIT/ROLLBACK/CONNECT found in UTM program.

Action: Correct your UTM program accordingly.

ORA-5131: ORADBCO-Call not allowed

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5132: TA for User x is committed by the Resource-Manager

Cause: Transaction has been committed before crash.

Action: None.

ORA-5133: No Connect-String in Startparams found

Cause: In the start parameters there must be at least one open string for the Oracle Server.

Action: See the chapter "UTM Product Set" in your Installation and Database Administration Guide and correct the start parameters.

ORA-5134: DBSTAT secondary opcode inconsistent

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5135: Error x Recover PTC-list, Instance y

Cause: System error.

Action: Check if UTM is correctly installed and select privileges are granted to XA-tables (see chapter on openUTM) otherwise contact your Oracle Customer Support Representative.

ORA-5136: Maximum number of instances exceeded

Cause: The maximum number of open strings in the start parameters has been exceeded.

Action: See the chapter "UTM Product Set" in your Installation and Database Administration Guide and correct the start parameters.

ORA-5137: Error x at Open Instance y

Cause: The connection to instance y is not possible.

Action: Start the Instance with all the required servers. If the error persists, contact your Oracle Customer Support Representative.

ORA-5138: Error x at Close Instance y

Cause: Error occurred when disconnecting from instance y.

Action: Because the disconnection has just been done, there is no action.

ORA-5139: Error x at Start Transaction for User z, Instance y

Cause: The start of transaction in instance y is invalid.

Action: Restart the UTM transaction. If the error persists, close the UTM application and do a restart.

ORA-5140: Error x at Continue Transaction for User z, Instance y

Cause: The continuation of transaction in instance y is invalid.

Action: Restart the UTM transaction. If the error persists, and the error is not 'XAER_PROTO' (this means, that the transaction is rolled back because of longlock), shut down the UTM application and restart.

ORA-5141: Error x at Break Transaction for User z, Instance y

Cause: The break of transaction in instance y is invalid.

Action: Restart the UTM transaction. If the error persists, and there are no cursor operations in the preceded dialog step, shut down the UTM application and do a restart.

ORA-5142: Error x at End Transaction for User z, Instance y

Cause: The end of a transaction in instance y is invalid.

Action: Restart the UTM transaction. If the error persists, shut down the UTM application and do a restart.

ORA-5143: Mismatch in TA for User(s) z

Cause: In the UTM warmstart there is a mismatch between openUTM and/or between the Oracle Server instance(s).

Action: Clear the Oracle Server instance(s), create new KDCDEF for UTM and restart the UTM application.

ORA-5143: Mismatch in TA for User(s) z

Cause: In the UTM warmstart there is a mismatch between openUTM and/or between the Oracle Server instance(s).

Action: Clear the Oracle instance(s), create new KDCDEF for UTM and restart the UTM application.

ORA-5144: Error x at Prepare Transaction for User z, Instance y

Cause: The preparation for committing a transaction in instance y is invalid.

Action: Restart the UTM transaction. If the error persists, shutdown the UTM application and do a restart.

ORA-5145: Error x at Commit Transaction for User z, Instance y

Cause: Attempt to commit transaction in instance y unsuccessful.

Action: Restart the UTM transaction. If the error persists, shutdown the UTM application and restart.

ORA-5146: Error x at Rollback Transaction for User z, Instance y

Cause: The rollback of transaction in instance y is invalid.

Action: No action, but if the error persists, shutdown the UTM application and restart.

ORA-5147: TA for User z committed; Reason: Recovery

Cause: In a openUTM warmstart an interrupted transaction has been committed.

Action: None.

ORA-5148: TA for User z heuristic rolled back in Instance y

Cause: In a UTM warmstart an interrupted transaction has just been rolled back from the Oracle Server.

Action: Restart the UTM transaction.

ORA-5149: TA for User z rolled back; Reason: Internal Event

Cause: The end- or prepare-call was invalid. Therefore the transaction must be rolled back.

Action: Restart the UTM transaction.

ORA-5150: KDCS-PEND before DBFITA missing

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5151: KDCS-PEND before DBPETA missing

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5152: Linked Resource-Manager is not CAE-compatible

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5153: xa_switch definition not found for specified Resource-Manager: s

Cause: System error.

Action: Contact your Oracle Customer Support Representative.

ORA-5154: Syntax error in start parameters for Resource-Manager: s

Cause: In the start parameters for the Oracle Server there is a syntax error.

Action: See the chapter "UTM Product Set" in your Installation and Database Administration Guide and correct the start parameters.

ORA-5155: Internal Error: malloc in dbstpa

Cause: System error (one possible reason: out of memory)

Action: Contact your Oracle Customer Support Representative.

ORA-5156: Internal Error: realloc in dbstpa

Cause: System error (one possible reason: out of memory)

Action: Contact your Oracle Customer Support Representative.

ORA-5157: Internal Error: malloc in up_recovery

Cause: System error (One possible reason: out of memory)

Action: Contact your Oracle Customer Support Representative.

ORA-5158: IUTMDB-Function not supported

Cause: openUTM system error.

Action: Contact your Oracle Customer Support Representative.

ORA-5159: TA for User(s) z rolled back; Reason: Recovery

Cause: In a openUTM warmstart one or more interrupted transactions have been rolled back.

Action: None.

ORA-5161: TCP/IP can't perform asynchronous test on break socket.

Cause: Select on break socket failed.

Action: Contact your System Administrator about TCP/IP networking problems. If the error persists, contact your Oracle Customer Support Representative.

ORA-5165: function not supported

Cause: Either Oracle8i Release 3 Server or BS2000/OSD does not support this function.

Action: None.

ORA-5167: Defect in data buffer

Cause: This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5170: SID not defined (ORAENV file missing?)

Cause: The system identifier (data base name) is not defined when needed during Oracle Server program initialization. This could be caused by a missing ORAENV file or a missing ORASID entry in that file.

Action: Ensure that the ORAENV file definition is correct and re-run the program.

ORA-5173: bad kernel size

Cause: An invalid value for the KNL_SIZE parameter has been specified in the ORAENV file.

Action: You should not normally need to specify this variable, as the default value will be correct. Contact your Oracle Customer Support Representative.

ORA-5174: bad kernel base

Cause: An invalid value for the KNL_BASE parameter has been specified in the ORAENV file.

Action: If this value is specified, it must be a hexadecimal value giving the full virtual address for the kernel memory pool. Correct the value and restart the database.

ORA-5175: Kernel address space conflict

Cause: The Oracle Server kernel cannot be placed at the requested address range, because the range is already used. The kernel start address is defined by the ORAENV parameter, KNL_BASE.

Cause: See the section on "Address Space Planning" in the chapter "Oracle Server System Architecture and Implementation" of the Installation and Database Administration Guide, and adjust the relevant initialization file and ORAENV parameters. Inspect the JOIN entry for your address space limit. Contact your System Administrator to learn about shared subsystems and their placement in the address space.

ORA-5176: Kernel: address space saturation

Cause: When the Oracle Server kernel memory pool was being allocated, the operating system signalled that the virtual address space is currently saturated.

Action: Contact your System Administrator about paging area size and current overall system load.

ORA-5177: Unexpected Kernel memory pool problem

Cause: The ENAMP macro returned an unexpected error code.

Action: This problem can be caused when you run a program in 24-bit mode and try to connect single-task to a kernel residing above the 16MB line (because the database itself is running in 31-bit mode). If this is the cause ot the error, you must access the database in two-task mode (via SQL*Net). See the ENAMP macro description in your BS2000 documentation for other possible reasons. If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5178: Kernel module not yet initialized

Cause: The current task is trying to attach to an Oracle Server kernel which is not yet completely initialized. This can only happen if you try to connect to a database which is just being started.

Action: Retry after a while (remember that it may take a few minutes until a database is fully running and ready for the users). If the error persists, see your Database Administrator.

ORA-5180: Cannot load character set table

Cause: One of the modules containing character set tables cannot be loaded.

Action: Verify that the ORALOAD library is accessible via "LINK=ORALOAD". For further information on linknames and the ORALOAD library, see the chapter "Getting Started" in the User's Guide. If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5181: load/init problem with PRO*C interface

Cause: The user-side stub module could not load the Pro*C module (in this case, the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module.

Action: Make sure the ORALOAD linkname exists and points to the current ORALOAD library. Re-link your application with the current link libraries.

ORA-5182: load/init problem with PRO*COBOL interface

Cause: The user-side stub module could not load the Pro*COBOL module (in this case the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module.

Action: Make sure the ORALOAD linkname exists and points to the current ORALOAD library. Re-link your application with the current link libraries.

ORA-5188: load/init problem with OCI C interface

Cause: The user-side stub module could not load the OCI C module (in this case the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module.

Action: Make sure the ORALOAD linkname exists and points to the current ORALOAD library. Re-link your application with the current link libraries.

ORA-5189: load/init problem with OCI COBOL interface

Cause: The user-side stub module could not load the OCI COBOL module (in this case the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module.

Action: Make sure the ORALOAD linkname exists and points to the current ORALOAD library. Re-link your application with the current link libraries.

ORA-5190: load/init problem with UPI interface

Cause: The user-side stub module could not load the UPI module (in this case the message will normally be preceded by a BS2000 BLS-nnnn message), or the loaded module is incompatible with the version of the stub module.

Action: Make sure the ORALOAD linkname exists and points to the current ORALOAD library. Re-link your application with the current link libraries.

ORA-5191: symbol translation error for kernel memory pool

Cause: The logical name translation for the kernel memory pool failed. Normally, this indicates an invalid system id (ORASID in the ORAENV file).

Action: Ensure that the ORAENV file definition is correct. Otherwise contact your Oracle Customer Support Representative.

ORA-5192: cannot create/attach kernel memory pool

Cause: The memory pool for the Oracle Server kernel code could not be enabled. In a user program (single-task Oracle Server), a possible cause is that part of the address range needed for the memory pool is already allocated by the user program.

Action: Ensure that the user program does not request storage excessively, and that any SGA_BASE and KNL_BASE parameters in the ORAENV file are consistent. If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5193: Symbol translation error for kernel module or load library

Cause: The logical-name translation for the kernel module or load library failed. This is an internal error and should not normally occur.

Action: Contact your Oracle Customer Support Representative.

ORA-5194: cannot load kernel

Cause: The kernel could not be loaded into the kernel memory pool. In most cases, this message is preceded by a BLS-nnn message from the operating system.

Action: Make sure that the ORALOAD linkname identifies the correct ORALOAD library, and that the ORAENV variable, KNL_MODULE, names one of the possible kernels. Then re-issue the STARTUP command. If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5195: bad or missing kernel connector

Cause: The loaded kernel could not verify its user-side connector module. This can occur if you use an incorrect kernel version in single-task mode. If the program is a Pro* program, it may be caused by using an ORALOAD.LIB different from the one that was used to startup the instance.

Action: If you cannot identify the cause of the problem contact your Oracle Customer Support Representative.

ORA-5196: Single Task Mode not allowed

Cause: The current task cannot run in single-task mode.

Action: Use two-task mode for the current task.

ORA-5197: Kernel can only be loaded by Oracle Server Manager

Cause: The shared kernel does not exist, however, the current task is not executing Server Manager and is not permitted to create the shared kernel. A user task will only need the Oracle Server kernel if it is connecting in single-task mode. The error normally indicates that the identified database is not running or does not allow single-task usage.

Action: Ensure the identified database is not running or does not allow single-task usage.

ORA-5198: associated internal OSD error code %d

Cause: This message precedes ORA-5199 if there is more information available. The first 4 hexadecimal digits can often identify the module; the last 4 hexadecimal digits are usually a condensed version of an associated system macro code. This code can be helpful in diagnosing the problem.

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.

ORA-5199: ORACLE ABNORMAL EXIT

Cause: A fatal error occurred which prevents continuation of execution. In many cases, a preceding message will explain the error. The system will cause the program execution to stop (TERM ABNORMAL with DUMP will be shown).

Action: If you cannot identify the cause of the problem, contact your Oracle Customer Support Representative.


Go to previous page Go to next page
Oracle
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Contents
Go To Index
Index