| 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 |
This chapter documents the Oracle database server infrastructure error codes for Oracle error ORA-04101. When this error occurs, the displayed messages include an additional 4-digit numeric error code that identifies the particular error condition. The following error codes are described in this chapter:
Latch state error on latch free. Report this error to Oracle Support Services.
Latch state error on latch free. Report this error to Oracle Support Services.
Latch state error on latch get. Report this error to Oracle Support Services.
Requested SGA size cannot be allocated in the server address space. To resolve this you must do one of the following:
Reduce the SGA size by changing one or more of the init.ora parameters that determine the size.
Increase the REGION in which the server runs. You can do this only if you are not running with REGION=0M.
Requested SGA size exceeds the reserve limit imposed by the REGION_MEM_RESERVE server region parameter. To resolve this you must do one of the following:
Reduce the SGA size by changing one or more of the init.ora parameters that determine the size.
Reduce the amount specified for REGION_MEM_RESERVE.
Increase the REGION in which the server runs. You can do this only if you are not running with REGION=0M.
Invalid state to create SGA. Report this error to Oracle Support Services.
An attempt was made to create the Oracle SGA in other than server address space 1 (AS1). To issue STARTUP (which creates the SGA) you must be connected to AS1.
Database file extend request failed due to share options conflict in the associated VSAM LDS cluster. To be able to be extended, the cluster must be defined with share options (3,3). To enable extend processing for an existing cluster, use IDCAMS ALTER to modify the share options to (3,3).
An MMGRSRV CONNECT request failed during database file extend processing. Report this error to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
The installation-supplied Oracle logon exit returned a nonzero return code when called during logon validation. This is a normal occurrence when the user fails whatever authorization checking is performed by the exit. It could also occur due to problems in the exit code.
A RACROUTE macro issued during Oracle logon authorization checking received an unexpected nonzero return code. The logon attempt is denied. Report this error to Oracle Support Services.
A RACROUTE macro issued during Oracle logon authorization checking received a nonzero return code indicating that the user is not authorized to connect to that Oracle instance.
An invalid userid length was passed to Oracle SAF-based logon authorization checking. This can occur if an Oracle userid longer than 8 characters is submitted to the SAF check.
An invalid password length was passed to Oracle SAF-based logon authorization checking. This can occur if a password longer than 8 characters is submitted to the SAF check.
A BSAM I/O error occurred while writing or reading a backup data set during RMAN backup or restore processing. Refer to the EDM job log for additional error details.
An invalid I/O request was attempted during RMAN backup or restore processing; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
A file parameter string longer than 256 bytes was passed to an RMAN backup/restore function.
An attempt to allocate memory for an RMAN EDM request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the RMAN session.
An unexpected error occurred during POST processing; report to Oracle Support Services.
An invalid parameter was passed to the POST function; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
An invalid filename was passed to an RMAN EDM backup or restore function. This can arise if an incorrect backup piece name is supplied in an RMAN request.
A RMAN request was issued for an EDM but the EDM was found to be in not-ready state. This error is expected if the EDM address space has terminated for any reason, including any unrecovered ABEND or an operator cancel.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
An attempt to allocate memory for an RMAN EDM request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the RMAN session.
CHANNEL TYPE "EDM0" request was either zero or greater than 124 bytes. Refer to the Oracle Database System Administration Guide for IBM z/OS for details on how to specify PARMS for an EDM channel.
An ASCRE macro request to start an EDM address space failed. This could be caused by an incorrect PARMS specification on the RMAN ALLOCATE CHANNEL command. It can also be caused by z/OS system resource problems.
An attempt to allocate memory for an RMAN EDM request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the RMAN session.
Internal RMAN proxy backup/restore error; report to Oracle Support Services.
A call to a z/OS UNIX System Services function has abended; report to Oracle Support Services.
An invalid argument list was supplied for a z/OS UNIX System Services call; report to Oracle Support Services.
Internal error in processing a z/OS UNIX System Services function call; report to Oracle Support Services.
An attempt to allocate memory for a z/OS UNIX System Services function request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
Internal error in processing a z/OS UNIX System Services function call. This error can arise when running a newer release of the Oracle RDBMS kernel with an older release of the OSDI server region program (ORARASC). If that is not the case, report this error to Oracle Support Services.
z/OS UNIX System Services are not available. This is a normal condition if an RDBMS request requires a z/OS UNIX System Services function call but the Oracle server address space fails z/OS UNIX System Services "dubbing". The usual cause of dubbing failure is that no default OMVS segment is associated with the z/OS userid under which the Oracle server address space runs. It can also occur if no z/OS userid is associated with the server address space.
File name buffer length error; report this error to Oracle Support Services.
Invalid file handle; report this error to Oracle Support Services.
Invalid resource string passed to RACROUTE check for CONNECT AS SYSOPER/SYSDBA; report this error to Oracle Support Services.
The RACROUTE check for CONNECT AS SYSOPER/SYSDBA failed. This is a normal condition if the z/OS userid that is attempting to connect is not authorized to connect as either SYSOPER or SYSDBA.
An invalid database name was passed to the instance lock routine; report this error to Oracle Support Services.
An unexpected error occurred on the ENQ used to serialize database mount; report this error to Oracle Support Services.
An attempt to allocate memory for an IDCAMS request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
An attempt to allocate memory for an alert log request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Invalid length in alert log message; report this error to Oracle Support Services.
Oracle is attempting to delete a file that is still open to one or more processes; report this error to Oracle Support Services.
An invalid security profile suffix was supplied for a RACROUTE request; report this error to Oracle Support Services.
A LOAD macro for IDCAMS failed; report this error to Oracle Support Services.
IDCAMS DEFINE or DELETE returned an error. The return code is stored with the error message. The IDCAMS output was written to the instance alert log and can be examined for details on the error.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Internal error in database file request; report this error to Oracle Support Services.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Internal error in database file request; report this error to Oracle Support Services.
An attempt to extend a database file failed because I/O to the file has not quiesced. Report this error to Oracle Support Services.
Invalid file handle for file sync request; report this error to Oracle Support Services.
Invalid file handle for file sync request; report this error to Oracle Support Services.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
A non-VSAM file was specified using DD name notation (such as "//DD:") but the specified DD is not allocated in the server address space.
Invalid parameter for timer wait; report this error to Oracle Support Services.
An attempt to allocate memory for a timer request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Invalid parameter for timer wait; report this error to Oracle Support Services.
An attempt to extend a database file has failed; this error is expected if the VSAM Linear Data Set is not defined with share options (3,3). To enable extend processing for such a data set, use IDCAMS ALTER to change the share options to (3,3).
An attempt to allocate memory for a database file extend request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Invalid database file handle for close; report this error to Oracle Support Services.
Invalid database file handle for extend; report this error to Oracle Support Services.
Invalid database file handle for extend; report this error to Oracle Support Services.
An MMGRSRV CATUPDT failed during database file sync processing. Report this error to Oracle Support Services.
An MMGRSRV EXTEND request failed during database file extend processing. This is expected if:
the data set is already at maximum extents
the requested amount of space was not available
an installation exit (such as a DADSM exit) denied the request for space
Otherwise, report this error to Oracle Support Services.
An MMGRSRV CONNECT request failed during database file open processing. Report this error to Oracle Support Services.
Dynamic allocation failed for a database file that was to be opened. The DYNALLOC macro return, reason and information codes are in the error message. If this does not appear to be due to external causes (such as an incorrect data set name) report this error to Oracle Support Services.
An attempt to allocate memory for a database file open request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1) or, for a multi-AS server, in z/OS common (CSA).
Invalid file handle passed to database file open; report this error to Oracle Support Services.
Invalid file handle passed to database file open; report this error to Oracle Support Services.
Invalid file handle passed to database file close; report this error to Oracle Support Services.
A Media Manager I/O request (MMGRCALL macro) returned an error. This error is expected if an existing VSAM LDS is supplied to Oracle with both REUSE and SIZE specified and the supplied SIZE exceeds the current high-used RBA of the data set. The Media Manager error code will indicate an incorrect RBA (disk extent violation) in this case. Do not include SIZE when reusing an Oracle database file as the correct size is determined automatically. For all other circumstances, report this error to Oracle Support Services.
An attempt to allocate LSQA for a database file I/O request failed. This indicates that LSQA is nearly exhausted in the server address space that hosts the requesting session.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
Invalid file handle passed to database file open; report this error to Oracle Support Services.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
An invalid data set name was passed to a database file function. This is expected if a SQL request such as CREATE or ALTER supplies a file name with incorrect syntax.
A retriable abend occurred in database file processing. The abend code is in the error message and a system dump (SDUMP) should be generated. Report this error to Oracle Support Services.
Invalid database file function code. Report this error to Oracle Support Services. An SDUMP will be generated.
Internal error detected during database file state processing. Report this error to Oracle Support Services. An SDUMP will be generated.
An attempt to allocate memory for a database file request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).
The catalog entry for a database file indicates that it is not a VSAM Linear Data Set (LDS) cluster. This can occur if an Oracle database file is migrated by a product such as DFSMShsm; the data set must be reloaded for Oracle to use it. This error can also arise if a data set that is not a VSAM LDS cluster is supplied to Oracle with REUSE.
Catalog LOCATE for an Oracle database file failed. The LOCATE return and information codes accompany this error. If the return code is 8, it indicates that the data set is not cataloged. Other return codes may indicate problems with your system's catalog structure.
A BLDL macro for a non-executable (data) module load failed. This can occur if the required Oracle NLS objects and message modules are not available in the ORA$LIB data set(s) specified in the region JCL. If that is not the case, report this error to Oracle Support Services.
An attempt to allocate memory for a data module LOAD request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
Invalid data module load parameter. Report this error to Oracle Support Services.
A LOAD macro for a non-executable (data) module load failed. This can occur if the required Oracle NLS objects and message modules are not available in the ORA$LIB or STEPLIB data set(s) specified in the region JCL. If that is not the case, report this error to Oracle Support Services.
An attempt to allocate memory for a data module LOAD request failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
I/O or other error on a BSAM WRITE macro. Report this error to Oracle Support Services.
Invalid record length for a BSAM WRITE. Report this error to Oracle Support Services.
Invalid file handle for BSAM or BPAM file write. Report this error to Oracle Support Services.
I/O error during buffer flush of a BSAM data set that is being closed. Report this error to Oracle Support Services.
Invalid logical record length for a BSAM or BPAM READ. This error is expected if a corrupted RECFM=VB data set is supplied as an input file (such as a parameter file). The error is the equivalent of a z/OS S002 ABEND.
I/O or other error on a BSAM or BPAM READ macro. This is expected if a corrupted or damaged data set is supplied as an input file (such as a parameter file).
Invalid file handle for BSAM or BPAM file read. Report this error to Oracle Support Services.
Invalid file handle for BSAM or BPAM file close. Report this error to Oracle Support Services.
An error or ABEND occurred on a BSAM or BPAM CLOSE macro. If the error is not an environment-caused problem (such as an Sx37 ABEND due to insufficient disk space), report this error to Oracle Support Services.
Invalid parameter on BSAM/BPAM file close request. Report this error to Oracle Support Services.
Invalid file handle for BSAM or BPAM file close. Report this error to Oracle Support Services.
ABEND in file task 3 services function. An SDUMP is generated for this. Report this error to Oracle Support Services.
Invalid parameter in a file services task 3 request. An SDUMP is generated for this. Report this error to Oracle Support Services.
An unexpected ABEND occurred while processing a request for a BSAM or BPAM data set. An SDUMP is generated. Report this error to Oracle Support Services.
An unexpected ABEND occurred while processing an OPEN for a BSAM or BPAM data set. Report this error to Oracle Support Services.
An attempt to allocate memory for BSAM/BPAM buffer memory failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
An error occurred when a FIND macro was issued for a member of an input PDS. This is an expected condition when an incorrect member name is supplied in an input file specification.
An OPEN macro for a BSAM or BPAM DCB failed. This is an expected condition if an input data set is cataloged but does not exist on the disk volume indicated in the catalog entry. It can also happen when the hosting server address space is running out of virtual memory.
An attempt to allocate memory for BSAM/BPAM data structures failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
An error occurred during dynamic allocation for a BSAM or BPAM data set. The DYNALLOC return, reason, and information codes accompany this error. There are a number of normal causes for this error including specifying an incorrect data set name (for an input data set) or failing to allocate required disk space (for an output data set). If the dynalloc error data does not indicate such a condition, report this error to Oracle Support Services.
An attempt to allocate memory for BSAM/BPAM data structures failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
An attempt was made to open a BSAM or BPAM data set in an incompatible use mode. Either the open was for output and the data set is already open for another Oracle session or the open was for input and the data set is open for output in another Oracle session.
Invalid parameter or option combination on a request to open a BSAM or BPAM data set. Report this error to Oracle Support Services.
An invalid BSAM or BPAM file task request was issued. An SDUMP is generated for this. Report this error to Oracle Support Services.
An attempt to allocate memory for BSAM/BPAM data structures failed. This indicates that virtual memory is nearly exhausted in the server address space that hosts the requesting session.
Unexpected result from file name normalization. Report this error to Oracle Support Services.
Invalid file name length for BSAM or BPAM data set processing. Report this error to Oracle Support Services.
Invalid parameter or option combination on a request to open a BSAM or BPAM data set. Report this error to Oracle Support Services.
Inadequate buffer length for normalized file name. Report this error to Oracle Support Services.
File name normalization was passed a file name type that cannot be normalized. This is an expected result when certain types of file specifications (particularly //SYSOUT:) are supplied in a function that does not support the use of that type of file. If that is not the case, report this error to Oracle Support Services.
File name syntax error. This is an expected error when a file name string supplied to an Oracle server contains invalid characters or syntax.
Invalid input length for file name normalize. This is an expected result when a very long file name string (>255 characters) is supplied to Oracle. If that is not the case, report this error to Oracle Support Services.
A RDJFCB macro for a DD name failed. This is an expected result when a file is specified as a DD name and a corresponding DD statement is not included in the server region JCL.
A call to the z/OS Symbol Substitution Service returned an error. This is an expected error when the result of the substitution is too long for the supplied output area. Check any strings that you have supplied with imbedded system symbols to make sure the total length of the string after substitution does not exceed the documented length limit for the associated parameter or option.
An error was detected on the interface between an EDM address space and the Oracle server. This could arise if the Oracle server region program (ORARASC) and the EDM jobstep program (ORAEDM) are from different releases of the product. Otherwise report this error to Oracle Support Services.
During RMAN processing an EDM address space was terminated by a fatal error condition. Refer to the EDM job log for details of the error.
An EDM dynamic allocation request during RMAN backup or restore processing returned an error. This is an expected error if invalid information is supplied in the ORA$FPS parameter file using with EDM. It can also occur for environmental reasons such as insufficient disk space when performing and EDM backup to disk. Refer to the EDM job log for additional details on the error.
A BSAM OPEN macro during RMAN backup or restore processing returned an error. This is an expected error for certain conditions such as a backup data set that is cataloged but not actually present on disk or tape. Refer to the EDM job log for additional details on the error.
A request for BSAM buffer memory failed in the EDM address space. This is an expected result if the EDM JCL procedure specifies a very small REGION but requests a large number of buffers.
An IDCAMS function requested by EDM has returned an error. Refer to the EDM job log or SYSPRINT for details on the error.
Buffer state error during EDM processing. Report this error to Oracle Support Services.
An error occurred during EDM CLOSE processing. This is an expected result if the final buffer flush during close encounters something like an Sx37 ABEND. Otherwise, report this error to Oracle Support Services.
An invalid request was made to EDM. Report this error to Oracle Support Services.
A request for file control block memory failed in the EDM address space. This is an expected result if the EDM JCL procedure specifies a very small REGION but requests a large number of buffers.
An attempt to allocate memory for an EDM request structure failed. This can occur of the EDM JCL procedure specifies or defaults to a very small REGION. Otherwise, report this error to Oracle Support Services.
An error occurred during EDM CLOSE processing. This is an expected result if the final buffer flush during close encounters something like an Sx37 ABEND. Otherwise, report this error to Oracle Support Services.
An error occurred during EDM dynamic unallocation processing. Report this error to Oracle Support Services.
An IDCAMS function requested by EDM has returned an error. Refer to the EDM job log or SYSPRINT for details on the error.
A RDJFCB macro for an EDM backup data set failed. Report this error to Oracle Support Services.
A catalog LOCATE request by EDM has failed. This is an expected result if the catalog entry for an RMAN-created backup piece has been deleted. Otherwise, report this error to Oracle Support Services.
An ATTACH macro to start the proxy data mover (normally IBM DFSMSdss) has failed. Make sure the IBM module ADRDSSU is available to the EDM address space and that the EDM REGION is large enough to run it.
An invocation of ADRDSSU (IBM DFSMSdss) for EDM proxy backup or restore processing returned an error. Refer to the EDM job log for details on the error.
A catalog LOCATE request by EDM has failed. This is an expected result if the catalog entry for an RMAN-created backup piece has been deleted. Otherwise, report this error to Oracle Support Services.
An EDM dynamic allocation request during RMAN backup or restore processing returned an error. This is an expected error if invalid information is supplied in the ORA$FPS parameter file using with EDM. It can also occur for environmental reasons such as insufficient disk space when performing and EDM backup to disk. Refer to the EDM job log for additional details on the error.
The device that was specified for an EDM proxy backup request is not a tape-class device. Proxy backup to disk devices is not supported. The device may have come from a UNIT parameter in the EDM ORA$FPS file or it may have been defaulted by installation exit or ACS processing.
An attempt to catalog an EDM-created backup piece has failed. Refer to the EDM job log for additional details on the error.
An error occurred during EDM dynamic unallocation processing. Report this error to Oracle Support Services.
IXCQUERY for a specific member returned data for multiple member. (MIRXNQF) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCQUERY answer area too small. IXCQUERY return code x'04', reason code x'04'. Report this error to Oracle Support Services.
STORAGE OBTAIN failed for MIRXCFRQ storage. Report this error to Oracle Support Services.
IXCJOIN with return code 4, but not reason code x'04'. Report this error to Oracle Support Services.
IXCJOIN with a return code greater than x'04'. Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
STORAGE OBTAIN failed for history table XNGHT. (MIRXNJG) Report this error to Oracle Support Services.
Bitmap of group memberships is full. No more Oracle instances can be added to the cluster. (MIRXNJG) Report this error to Oracle Support Services.
IXCLEAVE completed with an unexpected return or reason code. (MIRXNLG) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCLEAVE failed with return code 8, reason code 4, indicating that the XCF member token was not for an active member. (MIRXNLG) Report this error to Oracle Support Services.
The history table XNGHT contains no unproccessed entries therefore no new entries can be added. (MIRXNPS) Report this error to Oracle Support Services.
An MIRXCFRQ did not contain the correct information to perform the request. Report this error to Oracle Support Services.
IXCSETUS request failed for master member. (MIRXNJG) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCSETUS request failed for update of member bit map. (MIRXNJG) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCQUERY Defer requested failed. Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCSETUS request failed for reset of member bit map. (MIRXNLG) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCSETUS request failed leaving member bit on in member bit map. (MIRXNLG) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCSETUS request failed for reset of own bit in member bit map. (MIRXNLG) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference
STORAGE OBTAIN failed for MIRXCFRQ storage. (MIRXNCM) Report this error to Oracle Support Services.
STORAGE OBTAIN failed for answer area storage. (MIRXNCM) Report this error to Oracle Support Services.
ECB posting error. (MIRXNPS) Report this error to Oracle Support Services.
IXCQUERY answer area too small. IXCQUERY return code 4, reason code 4. (MIRXNCM) Report this error to Oracle Support Services.
An MIRXCFRQ was formatted incorrectly. (MIRXCFT) Report this error to Oracle Support Services.
STORAGE OBTAIN failed for background task. (MIRXCFT) Report this error to Oracle Support Services.
STORAGE RELEASE failed for background task. (MIRXCFT) Report this error to Oracle Support Services.
IXCJOIN failed with a return code greater than 4. (MIRXCFT) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCLEAVE completed with an unexpected return or reason code. (MIRXCFT) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCLEAVE failed with return code 8, reason code 4, indicating that the XCF member token was not for an active member. (MIRXCFT) Report this error to Oracle Support Services.
Background task abended and recovered while processing a MIRXCFRQ request. (MIRXCFT) Report this error to Oracle Support Services.
Invalid exit name was passed on a MIRXCFRQ connect request. (MIRXCFT) Report this error to Oracle Support Services.
Invalid user state data was passed to the IPC open routine. (MIRXCFO) Report this error to Oracle Support Services.
Invalid member data was passed to the IPC open routine. (MIRXCFO) Report this error to Oracle Support Services.
STORAGE OBTAIN failed for MIRXCFRQ storage. (MIRXCFS) Report this error to Oracle Support Services.1
STORAGE OBTAIN failed while processing an IPC request. (MIRXCFS) Report this error to Oracle Support Services.
STORAGE RELEASE failed while processing an IPC request. (MIRXCFS) Report this error to Oracle Support Services.
An invalid parameter was passed to an IPC routine. Report this error to Oracle Support Services.
An unknown internal error occurred while processing and IPC request. Report this error to Oracle Support Services.
An invalid storage address was passed to an IPC routine. Report this error to Oracle Support Services.
An invalid parameter was passed to a node monitor routine. (MIRXCFPM) Report this error to Oracle Support Services.
There is no more room in the node monitor member data table. (MIRXCFPM) Report this error to Oracle Support Services.
STORAGE RELEASE failed in a node monitor routine. (MIRXCFGM) Report this error to Oracle Support Services.
STORAGE OBTAIN failed in a node monitor routine. (MIRXCFPM) Report this error to Oracle Support Services.
A get member data request failed on target instance. (MIRXCFGM) Report this error to Oracle Support Services.
IXCSETUS request failed for master member. (MIRXNCM) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
The table of XCF groups established by the Oracle instance is full. (MIRXCFT). No new instances can be added to the cluster. Report this error to Oracle Support Services.
An IXCQUERY request failed to return the requested information. (MIRXCFT) Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Sysplex Services Reference.
IXCMSGO send request failed. (MIRXCFSN) Report this error to Oracle Support Services. For return codes x'0C' or greater, refer to the IBM manual MVS Programming: Sysplex Services Reference.
The request by the node monitor to set a timer failed. Report this error to Oracle Support Services.
ENQ request issued by a node monitor routine failed. Report this error to Oracle Support Services.
GQSCAN request issued by a node monitor routine failed. Report this error to Oracle Support Services. For return codes x'0C' or greater refer to the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2.
|
 Copyright © 2003, 2006, Oracle. All rights reserved. Legal Notices |
|
