| Oracle® Database Messages Guide 10g Release 2 (10.2) for IBM z/OS (OS/390) Part Number B25397-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Database Messages Guide 10g Release 2 (10.2) for IBM z/OS (OS/390) Part Number B25397-01 |
|
|
PDF · Mobi · ePub |
Under certain circumstances, an Oracle component will issue an ABEND macro with a user completion code (normally formatted in decimal). This chapter describes the user abend codes issued by Oracle products while running under z/OS. Unless otherwise specified, all user abends should be reported to Oracle Support Services. User abend codes begin with the prefix "U".
User abend codes in the range U4034 to U4095 are issued by the IBM Language Environment (LE) runtime component. These are documented in the IBM manual Language Environment Run-Time Messages. The occurrence of a Language Environment abend can indicate a problem in your own Pro* or OCI application, in an Oracle product, or in Language Environment itself. If you receive a Language Environment abend and it does not appear to be associated with your application, report the problem to Oracle Support Services.
The following messages are described in this chapter:
During server address space initialization, an ATTACH macro for an internal service subtask failed. The return code from ATTACH is in R15 at the time of the abend.
While accepting a bind from a client address space, an ALESERV macro to gain addressability to the client's address space failed unexpectedly. The return code from ALESERV is in R15 at the time of the abend.
During server address space initialization, an IDENTIFY macro for an internal service subtask failed. The return code from IDENTIFY is in R15 at the time of the abend. This abend is an expected condition if the ORARASC load module has been placed in the z/OS Link Pack Area (LPA).
During server address space initialization, an IEFSSREQ macro to issue a request to the OSDI subsystem failed unexpectedly. The return code from IEFSSREQ is in R15 at the time of the abend.
An invalid state condition was detected in the EDM address space.
An unexpected failure occurred when an EDM address space tried to post status back to the invoking server address space.
An invalid request structure was submitted to an EDM address space.
An invalid BSAM buffer state was detected in an EDM address space.
An invalid request structure was submitted to an EDM address space.
During server address space initialization, an ASEXT macro to fetch server address space parameters from the subsystem failed. The return code from ASEXT is in R15 at the time of the abend.
During server address space initialization, the parameter structure obtained via an ASEXT macro was corrupted or incorrect.
During server address space initialization an attempt to initialize the timer function in AS1 failed.
An invalid proxy commit request was passed to an EDM address space.
An Oracle Net internal error caused a loop in the free element chain.
In the Oracle kernel, a call was made to a function that is not implemented. This abend also occurs as an expected condition when certain internal "events" are set in the Oracle kernel. This abend is always abnormal in a customer system and should be reported to Oracle Support Services.
The Oracle kernel attempted to invoke an OSDI infrastructure function that is not provided. This abend is expected to occur when a newer Oracle kernel release is used with an older release of the server region control program, ORARASC.
An Oracle Net internal error caused an invalid self reference pointer.
An Oracle Net internal error occurred because the sanity value was not present on allocate; the element was already in use.
An Oracle Net internal error occurred because a large element was not on the page boundary.
An Oracle Net internal error occurred because the element being freed was already on the free element chain.
These abends are issued by internal Oracle runtime components associated with Oracle precompiler and OCI applications running in TSO, batch, and z/OS UNIX System Services shell environments. They indicate problems with the execution environment or with the calling application. Each abend is accompanied by a reason code in general register 15 (R15) at the time of the abend. Unless otherwise indicated by the reason code, these abends should be reported to Oracle Support Services.
The abend occurred on an application call to an Oracle precompiler or OCI interface function. The specific error is indicated by the reason code in general register 15:
The application context could not be located.
Oracle API DLL initialization failed. This may be accompanied by Language Environment messages indicating the nature of the error.
The caller is not a Language Environment-enabled language. This abend is expected when you link any non-LE application with the Oracle LE linking stub.
An invalid or corrupted application context was found.
An invalid API function descriptor was found.
An invalid function index was found.
Stub function and API function mismatch.
The application is calling a missing, obsolete, or disabled API function.
An API function supported only for C language callers has been called from a non-C language.
Attempt to set an LE condition handler failed. This can be caused by certain environmental conditions such as insufficient private area region.
Insufficient LE environment to support COBOL DYNAM application. This is usually due to an incorrectly linked COBOL application. For more information, refer to the Oracle Database User's Guide for IBM z/OS (OS/390).
The abend occurred in internal application context management. The specific error is indicated by the reason code in general register 15:
An attempt to obtain memory for the internal application context failed. This generally indicates that insufficient private area region is provided.
An unexpected error occurred using Name Token services.
There are several points where failure of critical Oracle Access Manager for IMS TM logic leads to a z/OS user abend. These abend codes are described as follows:
This abend is displayed on entry to an Oracle Access Manager for IMS TM ESAF exit when message AMI-0053 is issued as a z/OS WTO message. This indicates the region private area memory (both above and below 16M) is nearly exhausted. Refer to the Oracle Database System Administration Guide for IBM z/OS (OS/390) for a discussion of Oracle Access Manager for IMS TM memory requirements.
If no message is displayed, report the situation to Oracle Support Services.
The Oracle Access Manager for IMS TM linking stub issues this abend and message AMI-0055 when the IMS ECP data area associated with the task could not be found. This probably indicates the program is running in an environment other than an IMS MPP, IFP, or BMP region. If not, report the abend to Oracle Support Services.
This abend indicates an invalid memory allocation request was issued within Oracle Access Manager for IMS TM code. General register 15 contains a subcode that further describes the error. Report this abend to Oracle Support Services.
This abend indicates an invalid memory release request was issued within Oracle Access Manager for IMS TM code. General register 15 contains a subcode that further describes the error. Report this abend to Oracle Support Services.
This abend indicates Oracle Access Manager for IMS TM memory management control information has been damaged. General register 15 contains a subcode that further describes the error.
It is possible for this error to be caused by the user's application program by erroneously overwriting data areas that Oracle Access Manager for IMS TM maintains in key 8 region memory. This possibility should be considered if the abend occurs in a dependent region during or near the time new or modified application software is running. The errant software need not be a program that uses Oracle Access Manager for IMS TM.
If this possibility seems unlikely, report the abend to Oracle Support Services.
An error occurred in an internal memory management function. General register 15 contains a subcode describing the error. Report this abend to Oracle Support Services.
An error occurred during memory cleanup processing. General register 15 contains a subcode that describes the error. Report this abend to Oracle Support Services.
An error occurred when an application issued a request that Oracle Access Manager for IMS TM does not support.
SQL DDL statements, SQL DCL statements, and COMMIT/ROLLBACK entered as parsed statements are excluded since these errors are detected by the server and result in generic ORA-xxxx errors.
Your program attempted to use a cursor before it had been opened. Before the cursor can be used, the OOPEN OCI call must be used.
|
 Copyright © 2003, 2006, Oracle. All rights reserved. Legal Notices |
|
