User`s guide

A-14 Oracle Database User's Guide
ORA-05153: xa_switch definition not found for specified Resource-Manager: s
Cause: System error.
Action: Contact your Oracle Support Services Representative.
ORA-05154: Syntax error in start parameters for Resource-Manager: s
Cause: In the start parameters for the Oracle Database there is a syntax error.
Action: Refer to the chapter "UTM Product Set" in your Oracle Database Installation
and Administration Guide for Fujitsu BS2000/OSD and correct the start parameters.
ORA-05155: Internal Error: malloc in dbstpa
Cause: System error (one possible reason: out of memory)
Action: Contact your Oracle Support Services Representative.
ORA-05156: Internal Error: realloc in dbstpa
Cause: System error (one possible reason: out of memory)
Action: Contact your Oracle Support Services Representative.
ORA-05157: Internal Error: malloc in up_recovery
Cause: This error message indicates a system error. One of the possible reasons
for this issue is that the system does not have sufficient memory.
Action: Contact your Oracle Support Services Representative.
ORA-05158: IUTMDB-Function not supported
Cause: openUTM system error.
Action: Contact your Oracle Support Services Representative.
ORA-05159: 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-05161: 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, then contact your Oracle Support Services Representative.
ORA-05165: function not supported
Cause: Either Oracle Database 11g Release 2 (11.2) or BS2000/OSD does not
support this function.
Action: None.
ORA-05167: Defect in data buffer
Cause: This is an internal error and should not normally occur.
Action: Contact your Oracle Support Services Representative.
ORA-05170: SID not defined (ORAENV file missing?)
Cause: The system identifier, data base name, is not defined when needed during
Oracle Database 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-05173: bad kernel size