Oracle® Database

Messages Guide

10g Release 2 (10.2.0.5) for IBM z/OS on System z

B25397-02

October 2012

Oracle Database Messages Guide, 10g Release 2 (10.2.0.5) for IBM z/OS on System z

B25397-02

Copyright © 2003, 2012, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

List of Tables

Preface

- Intended Audience

- Documentation Accessibility

- Structure

- Product Name

- Command Syntax

- Accessing Documentation

- Related Documentation

- Typographic Conventions

1 Oracle Access Manager for IMS TM Messages

- 1.1 Messages AMI-0001 to AMI-0057

- 1.2 Messages AMI-0107 to AMI-0198

2 Oracle Access Manager for CICS Messages

- 2.1 Messages CIC-00001 to CIC-99999

- 2.2 Abends Under Oracle Access Manager for CICS

3 CFUTIL Messages

- 3.1 Messages CFU-0001 to CFU-0013

4 Oracle Database for z/OS Installation Messages

- 4.1 Messages OFT101I to OFT107I

- 4.2 Messages OFT101E to OFT999E

5 z/OS-Specific Oracle Database Messages

- 5.1 Messages ORA-04100 to ORA-04166

6 Server Infrastructure Error Codes

- 6.1 ORA-04101 Error Codes 1060 to 1349

7 Client Infrastructure Messages

- 7.1 Messages MIC011E to MIC022E

- 7.2 Messages MIC0208E to MIC0377E

8 Network Messages

- 8.1 Messages MIN0001I to MIN1105E

9 Database Region Messages

- 9.1 Messages MIR0001I to MIR0622I

10 Oracle Subsystem Messages

- 10.1 Messages MIS0001E to MIS0454E

11 User Abend Codes

- 11.1 User Abend Codes U1010 to U1378

- 11.2 User Abend Codes U2010 to U2011

- 11.3 User Abend Codes U3975 to U3986 (Oracle Access Manager for IMS TM)

Index

List of Tables

- 4-1 Oracle Database Installation Message Letter Codes

- 7-1 Client Infrastructure Message Letter Codes

- 8-1 Network Message Letter Codes

- 9-1 Database Region Message Letter Codes

- 10-1 Oracle Subsystem Messages Letter Codes

Preface

This guide explains how to understand messages encountered when using Oracle Database 10g Release 2 (10.2) for IBM z/OS.

Intended Audience

This guide is intended for anyone who uses, installs, or administers Oracle Database 10g Release 2 (10.2.0.5) for IBM z/OS on System z. It provides information about Oracle products and their interactions with z/OS. A thorough understanding of the fundamentals of z/OS is necessary before attempting to use this software.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Structure

This guide contains z/OS-specific messages issued by Oracle Database 10g Release 2 (10.2) for IBM z/OS on System z products. Messages that are independent of the operating system environment are documented in the relevant product-specific documentation.

Each message description includes the message, a probable cause, and a suggested action. The messages are listed in order by reference number, and are organized into the following chapters:

To find these messages:

Go to this chapter:

Messages AMI-0001 to AMI-0057
Messages AMI-0107 to AMI-0198

Chapter 1, " Oracle Access Manager for IMS TM Messages"

Messages CIC-00001 to CIC-99999

Chapter 2, " Oracle Access Manager for CICS Messages"

Messages CFU-0001 to CFU-0013

Chapter 3, "CFUTIL Messages"

Messages OFT101I to OFT107I
Messages OFT101E to OFT999E

Chapter 4, "Oracle Database for z/OS Installation Messages"

Messages ORA-04100 to ORA-04166

Chapter 5, "z/OS-Specific Oracle Database Messages"

ORA-04101 Error Codes 1060 to 1349

Chapter 6, "Server Infrastructure Error Codes"

Messages MIC011E to MIC022E
Messages MIC0208E to MIC0377E

Chapter 7, "Client Infrastructure Messages"

Messages MIN0001I to MIN1105E

Chapter 8, "Network Messages"

Messages MIR0001I to MIR0622I

Chapter 9, "Database Region Messages"

Messages MIS0001E to MIS0454E

Chapter 10, "Oracle Subsystem Messages"

User Abend Codes U1010 to U1378
User Abend Codes U2010 to U2011

User Abend Codes U3975 to U3986 (Oracle Access Manager for IMS TM)

Chapter 11, "User Abend Codes"

Product Name

The complete name for the product described in this book is Oracle Database 10g release 2 (10.2.0.5) for IBM z/OS on System z. To maintain readability and conciseness in this document, the product is also referred to as Oracle Database for z/OS and the platform as z/OS.

Command Syntax

UNIX command syntax appears in monospace font. The dollar character ($), number sign (#), or percent character (%) are UNIX command prompts. Do not enter them as part of the command. The following command syntax conventions are used in this guide:

Convention

Description

backslash \

A backslash is the UNIX command continuation character. It is used in command examples that are too long to fit on a single line. Enter the command as displayed (with a backslash) or enter it on a single line without a backslash:

dd if=/dev/rdsk/c0t1d0s6 of=/dev/rst0 bs=10b count=10000

braces { }

Braces indicate required items:

.DEFINE {macro1}

brackets [ ]

Brackets indicate optional items:

cvtcrt termname [outfile]

ellipses ...

Ellipses indicate an arbitrary number of similar items:

CHKVAL fieldname value1 value2 ... valueN

italics

Italic type indicates a variable. Substitute a value for the variable:

library_name

vertical line |

A vertical line indicates a choice within braces or brackets:

FILE filesize [K|M]

Accessing Documentation

The documentation for this release includes platform-specific documentation and generic product documentation.

Platform-Specific Documentation

Platform-specific documentation includes information about installing and using Oracle products on particular platforms. The platform-specific documentation for this product is available in both Adobe portable document format (PDF) and HTML format on the product disc. To access the platform-specific documentation on disc:

1. Use a Web browser to open the welcome.htm file in the top-level directory of the disc.

2. For DVD only, select the appropriate product link.

3. Select the Documentation tab.

If you prefer paper documentation, then open and print the PDF files.

Product Documentation

Product documentation includes information about configuring, using, or administering Oracle products on any platform. The product documentation for Oracle Database 10g products is available in both HTML and PDF formats in the following locations:

- In the doc subdirectory on the Oracle Database 10g DVD
To access the documentation from the DVD, use a Web browser to view the welcome.htm file in the top-level directory on the disc, then select the Oracle Database 10g Documentation Library link.

- Online on the Oracle Technology Network (OTN) Web site:
http://www.oracle.com/technetwork/indexes/documentation/index.html

Related Documentation

The platform-specific documentation for Oracle Database 10g products includes the following manuals:

- Oracle Database

- Oracle Database Release Notes for IBM z/OS on System z

- Oracle Database Installation Guide for IBM z/OS on System z

- Oracle Database User's Guide for IBM z/OS on System z

- Oracle Database Messages Guide for IBM z/OS on System z

- Oracle Database System Administration Guide for IBM z/OS on System z

For information about upgrading from a previous release of Oracle Database, refer to the Oracle Database Upgrade Guide and the Oracle Database System Administration Guide for IBM z/OS on System z.

- Oracle Books

- Oracle Database Error Messages

- IBM Books

- z/OS V1R10.0 Communications Server IP and SNA Codes (SC31-8791)

- z/OS V1R10.0 Communications Server IP Sockets Application Programming Interface Guide and Reference (SC31-8788)

- z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566)

- z/OS V1R10.0 MVS Programming Authorized Assembler Services Reference Vol 1 (SA22-7609)

- z/OS V1R10.0 MVS Programming Authorized Assembler Services Reference Vol 2 (SA22-7610)

- z/OS V1R10.0 MVS Programming Sysplex Services Reference (SA22-7618)

IBM documents are referenced in a shorter form throughout this document. For example, z/OS V1R10.0 Language Environment Run-Time Messages (SA22-7566) is referred to as Language Environment Run-Time Messages.

Refer to Oracle Database Release Notes for IBM z/OS on System z for important information that was not available when this book was released. The release notes for Oracle Database 10g are updated regularly. You can get the most recent version from Oracle Technology Network at

http://www.oracle.com/technetwork/indexes/documentation/index.html

Typographic Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Oracle Access Manager for IMS TM Messages

This chapter describes the messages issued by Oracle Access Manager for IMS TM while running under z/OS.

Oracle Access Manager for IMS TM messages begin with the prefix "AMI-"

The following messages are described in this chapter:

- Messages AMI-0001 to AMI-0057

- Messages AMI-0107 to AMI-0198

1.1 Messages AMI-0001 to AMI-0057

Messages AMI-0001 to AMI-0055 are issued in American English only. They cannot be translated.

AMI-0001 THE RTT FOR THIS REGION AND SUBSYSTEM IS NOT AN AMI RTT

Cause: During Oracle Access Manager for IMS TM initialization processing, the RTT loaded into the region (specified in the SSM entry for the subsystem) was not generated with AMIRT and other macros, or has been damaged.

Action: Initialization processing for the region fails. If the failure occurs in the control region, then the subsystem is placed in a stopped state. When the RTT is replaced or repaired, the region can retry initialization. If the subsystem was stopped, then it can be restarted with the START SUBSYS command.

AMI-0002 AMI/RTT VERSIONS INCOMPATIBLE (RTT=version.version AT date_time, AMI=version.version)

Cause: During Oracle Access Manager for IMS TM initialization processing, the RTT loaded into the region (specified in the SSM entry for the subsystem) contained an Oracle Access Manager for IMS TM version or release number higher than that of the Oracle Access Manager for IMS TM code.

Action: Initialization processing for the region fails. If the failure occurs in the control region, then the subsystem is placed in a stopped state. When the RTT is replaced or repaired, the region can retry initialization. If the subsystem was stopped, then it can be restarted with the START SUBSYS command.

AMI-0003 NO AMI RTT HAS BEEN SUPPLIED FOR THE CONTROL REGION

Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, no RTT name had been specified in the SSM entry for the subsystem or the specified RTT could not be loaded.

Action: Initialization processing for the subsystem fails. If the SSM entry does not specify an RTT name, then one must be added. If a name is specified, then ensure the name is correct and that the load module is located in an authorized library that is part of the DFSESL DD statement concatenation.

AMI-0004 UNABLE TO ALLOCATE AMI GLOBAL STRUCTURE (number BYTES)

Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, an attempt to allocate the specified amount of memory in the z/OS extended common storage area (ECSA) failed.

Action: Initialization processing for the subsystem fails. The indicated amount of ECSA must be available in order for Oracle Access Manager for IMS TM to initialize. If ECSA can be made available, then the subsystem can be restarted with the START SUBSYS command.

AMI-0005 DEPENDENT REGION UNABLE TO LOCATE AMI GLOBAL STRUCTURE

Cause: During Oracle Access Manager for IMS TM initialization processing for a dependent region, the Oracle Access Manager for IMS TM global data area could not be located.

Action: Initialization processing for the region fails. You can report this error to Oracle Support Services for additional assistance.

AMI-0006 UNABLE TO ALLOCATE AMI LOCAL STRUCTURE (number BYTES)

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate the specified amount of memory in the extended private area of the region failed.

Action: Initialization processing for the region fails. If the error occurs in the control region, then subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for a discussion of region memory requirements.

AMI-0007 AMI MESSAGE FACILITY INITIALIZATION FAILED

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the product failed. This message normally is preceded by one or more instances of message AMI-0010.

Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Ensure the required message modules are installed in an authorized library that is part of the region DFSESL DD statement concatenation.

AMI-0008 (AMI MESSAGE FETCH FAILURE FOR MSGNO msgid)

Cause: An attempt to fetch the indicated Oracle Access Manager for IMS TM message has failed.

Action: You can report this message to Oracle Support Services for additional assistance. The original message can be looked up in this section by its number. If the message contains fill in items, however, then they cannot be determined.

AMI-0009 UNABLE TO ALLOCATE GVV STRUCTURE (number BYTES)

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate the specified amount of memory in the extended private area of the region failed.

Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for a discussion of region memory requirements.

AMI-0010 AMI MESSAGE INITIALIZATION FOR LANGUAGE lang_id FAILED WITH ERROR number

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the indicated language string failed.

Action: Initialization retries message initialization using other language strings, if available. If all such attempts fail, then message AMI-0007 is issued and initialization of the region fails. Ensure the required message module has been placed in an authorized library that is part of the DFSESL DD statement concatenation for the region, and that the NLS_LANG environment variable has not been specified incorrectly in an AMIENV macro in the region's RTT.

AMI-0011 AMI LANGUAGE INITIALIZATION FOR LANGUAGE lang_id UNSUCCESSFUL

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to initialize message localization facilities for the indicated language string failed.

Action: Initialization retries message initialization using other language strings if available. If all such attempts fail, then message AMI-0007 is issued and initialization of the region fails. Ensure the required message module has been placed in an authorized library that is part of the DFSESL DD statement concatenation for the region, and that the NLS_LANG environment variable has not been specified incorrectly in an AMIENV macro in the region's RTT.

AMI-0012 UNABLE TO ALLOCATE MEMORY FOR MESSAGE/MESSAGE PROCESSING

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an attempt to allocate virtual memory in the extended private area of the region failed.

Action: Initialization processing for the region fails. If the error occurs in the control region, then the subsystem initialization fails. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for a discussion of region memory requirements.

AMI-0013 UNABLE TO LOCATE AMI LOCAL DATA AREA

Cause: During Oracle Access Manager for IMS TM processing for a region, an attempt to locate a required data structure in the region failed.

Action: Application request processing, if any, fails with a U3044 ABEND. You can report this message to Oracle Support Services for additional assistance.

AMI-0014 UNABLE TO SET AMI GLOBAL STRUCTURE POINTER IN SSCT

Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, an attempt to dynamically add a z/OS subsystem entry for the Oracle Access Manager for IMS TM has failed.

Action: Initialization processing for the subsystem fails. You can report this message to Oracle Support Services for additional assistance. A possible workaround for this problem is to add the subsystem entry to z/OS using the formal mechanism and re-IPL z/OS.

AMI-0015 ssn IMS MESSAGE SERVICE ROUTINE RETURNED ERROR CODE number

Cause: An attempt to issue an Oracle Access Manager for IMS TM message through the IMS message service routine has returned the indicated error.

Action: This message and the original message are displayed at the z/OS system console. You can report this to Oracle Support Services for additional assistance.

AMI-0016 LOADED CONTROL REGION RTT name AT ADDRESS address

Cause: During Oracle Access Manager for IMS TM initialization processing for the control region, Oracle Access Manager for IMS TM has loaded the RTT because IMS failed to do so.

Action: Processing continues; no action is required. This message is an expected occurrence in IMS TM release 4.1.

AMI-0050 AMI ANCHOR BLOCK NOT FOUND - ESMT ERROR

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, an Oracle Access Manager for IMS TM data structure was not found as expected.

Action: Initialization processing for the region fails. This data area is allocated by IMS through controls in the ESMT module ORAESMT. Ensure you are using the correct ESMT and it has not been altered.

AMI-0051 AMI UNABLE TO LOCATE IMS SCD

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, the IMS SCD data area could not be located.

Action: Initialization processing for the region fails. Ensure the version and release level of your IMS TM are supported by the Oracle Access Manager for IMS TM release. If so, then you can report this message to Oracle Support Services for additional assistance.

AMI-0052 AMI DOES NOT SUPPORT THIS VERSION OF IMS

Cause: During Oracle Access Manager for IMS TM initialization processing for a region, the IMS SCD data area indicated an IMS TM version and release not supported by this release of Oracle Access Manager for IMS TM.

Action: Initialization processing for the region fails. Ensure the version and release level of your IMS TM are supported by the Oracle Access Manager for IMS TM release. If so, then you can report this message to Oracle Support Services for additional assistance.

AMI-0053 AMI UNABLE TO ALLOCATE SECONDARY STACK

Cause: During Oracle Access Manager for IMS TM deferred connection processing for a region, a request for region virtual storage could not be satisfied.

Action: Connection processing for the region fails. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for a discussion of region memory requirements.

AMI-0054 AMI UNABLE TO ALLOCATE REQUIRED REGION MEMORY

Cause: During Oracle Access Manager for IMS TM deferred initialization processing for a region, a request for region virtual storage could not be satisfied.

Action: Initialization processing for the region fails. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for a discussion of region memory requirements.

AMI-0055 AMILS UNABLE TO LOCATE IMS ECP

Cause: The Oracle Access Manager for IMS TM linking stub, AMILS, issues this message when the IMS ECP data area associated with the task cannot be found.

Action: Ensure the transaction is running in a valid IMSMPP, IFP, or BMP environment.

AMI-0056E LOAD REQUEST FOR (module) FAILED. ABEND CODE (abend-reason)

Cause: Access Manager initialization was unable to load a required module.

Action: Ensure that AMIMAIN, AMIDMYC, and LIBCLNTS are in an APF authorized library that is available to IMS through the standard MVS search sequence, for example, STEPLIB, or the ORAAMIDD DD name.

AMI-0057E CEEPIPI FUNCTION (function) RETURN CODE (rc)

Cause: The IBM Language Environment pre-initialized environment routine completed with a non-zero return code.

Action: The Access Manager ESAF initialization exit returns error code 8 to IMS. For the control region, the external subsystem is marked as unstartable. If an application request is involved, the program will be terminated with user ABEND 3044. This message should be reported to Oracle.

1.2 Messages AMI-0107 to AMI-0198

AMI-0107 ROLLBACK NON-EXISTING TRANSACTION (xxxx) IGNORED

Cause: During Oracle Access Manager for IMS TM resolve in-doubt processing, where IMS requested a rollback of the transaction, the transaction was not found in the Oracle system. This is a normal message after a certain type of application failure.

Action: None. Processing continues.

AMI-0108 INITIALIZATION SUCCESSFUL WITH RTT ASSEMBLED AT date_time

Cause: Oracle Access Manager for IMS TM initialization processing for the region has completed successfully. The RTT in effect for the region was assembled on the indicated date. This is the RTT specified in the region SSM entry for the subsystem, if any; otherwise it is the RTT loaded by the control region.

Action: Processing continues; this message is informational. Oracle Access Manager for IMS TM initialization consists primarily of allocation and setup of internal data areas. It does not include making a connection to the target Oracle database server, which might follow immediately or be deferred until an application request is issued.

AMI-0109 UNABLE TO LOCATE AMI GLOBAL DATA AREA

Cause: On entry to one of the Oracle Access Manager for IMS TM ESAF exit routines, the global data area for Oracle Access Manager for IMS TM was not found.

Action: The exit routine returns error code 32 (decimal) to IMS; the effect depends on which exit encountered the problem. If an application request is involved, then the program ends with user ABEND U3044. You can report this message to Oracle Support Services for additional assistance.

AMI-0110 CONNECT TO ORACLE FAILED WITH ERROR ORA-number

Cause: During Oracle Access Manager for IMS TM connection processing, the attempt to connect to the target Oracle database server failed with the indicated error.

Action: ESAF identify processing fails for the region; if this is the control region or a subsequent access of the Oracle database server from the control region fails, then the subsystem is placed in the stopped state. It can be restarted with the START SUBSYS command after the cause of the error is corrected.

AMI-0111 ORACLE VERSION QUERY FAILED WITH ERROR ORA-number

Cause: During initial connection (ESAF identify) or following an application ABEND, a test inquiry sent to the Oracle database server failed with the indicated error.

Action: In the identify case, identify processing ends with an error and the subsystem is placed in a logical stopped state. In the latter case, IMS assumes that the target Oracle database server is unavailable and stops the subsystem in the region in question. This is a normal occurrence if communications with the Oracle database server ended unexpectedly by hardware or software failure.

AMI-0112 TARGET ORACLE7 IS AN UNSUPPORTED VERSION (version)

Cause: During connection processing, the version number returned by the target Oracle database server was one not supported by Oracle Access Manager for IMS TM.

Action: Connection processing fails and the subsystem is placed in the stopped state. Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for information about supported versions and releases of the Oracle database server.

AMI-0113 SUBSYSTEM ssn CONNECTED TO ORACLE VERSION version

Cause: Oracle Access Manager for IMS TM identify (connection) processing for the indicated subsystem id has completed in the region.

Action: Processing continues; this message is informational.

AMI-0114 UNABLE TO ALLOCATE HSTDEF EXTENSION OF SIZE number

Cause: During Oracle Access Manager for IMS TM identify (connection) processing, a request for the indicated amount of virtual memory failed.

Action: Connection processing ends and IMS ESAF identify ends with an error. The subsystem can be restarted with the IMS START SUBSYS command when more virtual storage is available in the affected region.

AMI-0117 SESSION POOL FULL BEFORE ALL POOLED SESSIONS WERE STARTED

Cause: During connection processing for a dependent region, the maximum number of session pool entries (RTT MAXSESS parameter) was reached before all pooled sessions (those having AMISESS START=YES) could be started.

Action: Processing continues; sessions beyond the MAXSESS number are not pooled. You might want to increase MAXSESS to allow for all START=YES sessions or reduce the number of START=YES sessions defined.

AMI-0118 RESOLVE IN-DOUBT PROCESSING COMPLETED

Cause: Following Oracle Access Manager for IMS TM identify (connection) processing in the control region or following an application ABEND, IMS resolve in-doubt processing has completed normally.

Action: Processing continues; this message is informational.

AMI-0119 RECOVERY SESSION CREATION FAILED WITH ERROR ORA-number

Cause: During connection (identify) processing in the control region, the attempt to create an Oracle session for recovery (using the RTT RECOID user id) failed with the indicated error.

Action: Connection processing fails and the subsystem is placed in the stopped state. Ensure RECOID is correctly specified in the RTT AMIRT macro and a suitable AMISESS entry is provided for that user id.

AMI-0120 UNABLE TO FIND RTT SESSION ENTRY FOR RECOVERY USERID

Cause: During connection (identify) processing in the control region, no RTT AMISESS entry could be found for the recovery user id (AMIRT RECOID) and no default session entry is provided.

Action: Connection processing fails and the subsystem is placed in the stopped state. Ensure RECOID is correctly specified in the RTT AMIRT macro and a suitable AMISESS entry is provided for that user id.

AMI-0121 RETRIEVE PENDING TRANSACTION COUNT FAILED WITH ERROR ORA-number

Cause: IMS has been cold-started and an attempt by the Oracle database server to obtain information about possible inconsistencies has failed with the indicated error.

Action: Resolve in-doubt processing fails and the subsystem is placed in the stopped state. The cause of the error must be corrected to restart the subsystem.

AMI-0122 IMS COLD-STARTED AND THERE ARE number PENDING TRANSACTIONS IN ORACLE

Cause: IMS has been cold-started and the target Oracle database server has the indicated number of in-doubt transaction entries. These create an inconsistency between IMS and the Oracle database server.

Action: Resolve in-doubt processing fails and the subsystem is placed in the stopped state. Manual (forced) commit or rollback of the Oracle transactions must be performed by an Oracle database administrator (DBA).

AMI-0123 UNKNOWN RECOVERY ACTION string FOR RECOVERY TOKEN token, IGNORED

Cause: During resolve in-doubt processing, IMS has called the RID exit for Oracle Access Manager for IMS TM with an action code other than CO (commit) or AB (abort).

Action: Resolve in-doubt processing fails. You can report this message to Oracle Support Services for additional assistance.

AMI-0124 RECOVERY action FOR TOKEN token FAILED WITH ERROR ORA-number

Cause: During resolve in-doubt processing, an attempt to take the indicated action (COMMIT or ROLLBACK) in the Oracle database server has failed with the indicated error.

Action: Resolve in-doubt processing fails. If the error is ORA-2058, indicating an unknown Oracle transaction id, then an inconsistency might exist between IMS and the Oracle database server.

AMI-0125 RECOVERY COMMITS=number, ABORTS=number, DEFERS=number

Cause: Resolve in-doubt processing has completed. The indicated number of transactions have been committed, ended (rolled back), or deferred for later recovery action.

Action: Processing continues; this message is informational.

AMI-0126 RETRIEVE PENDING TRANSACTION COUNT FAILED WITH ERROR ORA-number

Cause: Following resolve in-doubt processing, an attempt to check for irrecoverable Oracle transactions (which constitute an inconsistency between IMS and the Oracle database server) has failed with the indicated error.

Action: Resolve in-doubt processing fails. Manual recovery of in-doubt Oracle transactions might be required.

AMI-0127 ORACLE STILL HAS number PENDING TRANSACTIONS AFTER RECOVERY

Cause: IMS has signalled recovery has ended, but the Oracle database server still has in-doubt transactions associated with this IMS.

Action: Resolve in-doubt processing fails. Manual recovery of in-doubt Oracle transactions might be required.

AMI-0128 CLOSE OF RECOVERY CURSOR GOT ERROR ORA-number

Cause: The call to close a cursor using resolve in-doubt processing received the indicated error.

Action: Processing continues. Unless this message is associated with an obvious cause (such as an outage of the target database or Oracle Net), you can report this message to Oracle Support Services for additional assistance.

AMI-0129 ESAF CALL OCCURRED IN ILLOGICAL STATE OR UNEXPECTED SEQUENCE

Cause: A call to one of the Oracle Access Manager for IMS TM ESAF exits has occurred at an unexpected time.

Action: The exit routine returns error code 32 (decimal) to IMS; the effect depends on which exit encountered the problem. If an application request is involved, then the program ends with user ABEND U3044. You can report this message to Oracle Support Services for additional assistance.

AMI-0130 ORACLE DISCONNECT FAILED WITH ERROR ORA-number

Cause: Disconnect (end identify) processing encountered an error on the call to disconnect from the Oracle database server.

Action: Processing continues. Unless this message is associated with an obvious cause (such as an outage of the target database or Oracle Net), you can report this message to Oracle Support Services for additional assistance.

AMI-0131 action ACTION FOR RECOVERY TOKEN token SUCCESSFUL

Cause: During resolve in-doubt processing, the transaction associated with the indicated IMS recovery token was successfully forced through COMMIT or ROLLBACK processing in the Oracle database server.

Action: Processing continues; this message is informational.

AMI-0132 action ACTION FOR RECOVERY TOKEN token FAILED DUE TO INCONSISTENCY

Cause: During resolve in-doubt processing, an attempt to force a COMMIT or ROLLBACK of the transaction associated with the indicated IMS recovery token has failed because the transaction is not known to the Oracle database server. This indicates that an inconsistency exists between IMS and the Oracle database server.

Action: Resolve in-doubt processing fails. Manual commit or end of the transaction might be required in other resource managers.

AMI-0133 action ACTION FOR RECOVERY TOKEN token DEFERRED DUE TO ERROR

Cause: During resolve in-doubt processing, an attempt to force a COMMIT or ROLLBACK of the transaction associated with the indicated IMS recovery token has failed. A return code is passed to IMS indicating recovery for this transaction is to be deferred.

Action: The specific error should be displayed in another message; investigate the cause of the error.

AMI-0134 RECOVERY TOKEN CHANGED DURING MULTIPLE-MODE TRANSACTION

Cause: In ESAF signon processing for the second or later input message for a multiple-mode transaction, IMS indicated a change of recovery token.

Action: Oracle Access Manager for IMS TM causes the application to end with ABEND U3047.

AMI-0135 ILLEGAL ATTEMPT TO CHANGE USERID IN MULTIPLE-MODE TRANSACTION

Cause: In processing a multiple-mode transaction whose RTT AMITRANS macro specifies AUTH=IMSID, a new input message has a different MVS/IMS user id than the one under which the transaction was started.

Action: Oracle Access Manager for IMS TM causes the application to end with ABEND U3047.

AMI-0136 ESAF SIGNON CALL IN IMPROPER STATE number

Cause: IMS invoked the signon ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: This indicates an internal IMS or Oracle Access Manager for IMS TM problem and you can report this message to Oracle Support Services for additional assistance.

AMI-0137 ESAF CREATE THREAD CALLED IN IMPROPER STATE number

Cause: IMS invoked the create thread ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: This indicates an internal IMS or Oracle Access Manager for IMS TM problem and you can report this message to Oracle Support Services for additional assistance.

AMI-0139 UNABLE TO FIND RTT TRANSACTION ENTRY FOR PSB psb_name

Cause: At thread creation time, Oracle Access Manager for IMS TM was unable to locate an RTT transaction entry (AMITRANS macro) for the indicated PSB name and no default transaction entry is provided.

Action: Thread creation fails and the application is ended by IMS with ABEND U3047. To run this application, the region RTT must be changed to include an AMITRANS entry for the PSB name or a default AMITRANS (with a PSB name of *). Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for more details.

AMI-0140 UNABLE TO FIND RTT SESSION ENTRY FOR USERID id, PSB psb_name

Cause: At transaction start time, Oracle Access Manager for IMS TM was unable to locate an RTT session entry (AMISESS macro) for the indicated Oracle user id, and no default session entry is provided. The applicable PSB name, whose RTT AMITRANS entry determined the user id, is also indicated.

Action: Transaction start fails, and the application is ended by IMS with ABEND U3047. To run this application with the indicated user id, the region RTT must be changed to include an AMISESS entry for the user id or a default AMISESS (with a user id of *). Refer to the Oracle Database System Administration Guide for IBM z/OS on System z for more details.

AMI-0143 DELETE SESSION sess_id FAILED (number); MAY STILL BE ACTIVE IN ORACLE

Cause: An Oracle Access Manager for IMS TM request to delete an Oracle session received an error.

Action: The session is logically discarded by Oracle Access Manager for IMS TM. If this message occurs with a failure of the Oracle connection, then it is normal and can be ignored. Otherwise, investigate the specific error to determine why the session was not deleted. Repeated occurrences of this message over time might signal a resource problem in the target Oracle instance.

AMI-0145 UNABLE TO MAKE ORACLE SESSION FOR USERID id (function ERROR number)

Cause: An attempt to create or clone an Oracle session for the indicated Oracle user id failed; the internal interface routine and Oracle error code are shown in parentheses.

Action: If this occurs in the control region (with the recovery user id), then Oracle Access Manager for IMS TM identify processing ends; the problem indicated by the error code must be corrected and the Oracle Access Manager for IMS TM instance restarted. In a dependent region this message might indicate a problem with a specific Oracle user id (such as incorrect authentication information in the RTT session descriptor) or a more general problem that affects all sessions; accompanying messages tell you the problem. In the former case, only transactions running with the specific user id are affected and behavior depends on the region error option (REO) in effect for the transaction. In the latter case, IMS attempts to restart the Oracle Access Manager for IMS TM instance in the region before placing the instance in a stopped state.

AMI-0149 UNEXPECTED RESPONSE CODE (number) TO ORACLE COMMIT

Cause: During the last phase of two-phase commit processing for a transaction, the COMMIT command sent to the Oracle database server received an unexpected response code as shown.

Action: The transaction ends with ABEND U3044. This message indicates an Oracle Access Manager for IMS TM or the Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0150 UNEXPECTED RESPONSE (number) TO ORACLE COMMIT PREPARE

Cause: During the first phase of two-phase commit processing for a transaction, the commit prepare command sent to the Oracle database server received an unexpected response code as shown.

Action: The transaction ends with ABEND U3044. This message indicates an Oracle Access Manager for IMS TM or an Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0151 ESAF COMMIT PREPARE CALLED IN IMPROPER STATE number

Cause: IMS invoked the commit prepare ESAF processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: The application ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0157 ESAF PREPARE CALLED WITH UNEXPECTED RECOVERY TOKEN

Cause: The ESAF commit prepare exit was invoked with an IMS recovery token different from the one supplied when the transaction started.

Action: The transaction ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0159 SETUP OF RECOVERY CURSOR(S) FAILED WITH ERROR ORA-number

Cause: During resolve in-doubt processing, parse, bind, or define processing for recovery SQL received the indicated error.

Action: Resolve in-doubt processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0160 ESAF START SUBSYSTEM REQUEST FAILED WITH RC number (DECIMAL)

Cause: An attempt to start Oracle Access Manager for IMS TM in response to an application request has failed. The IMS ESAF subsystem startup service routine returned the indicated error code.

Action: Deferred connect processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0162 IDENTIFY FAILED - ORACLE CONNECTION LOST

Cause: During connection (identify) processing, an error was received indicating the connection has been lost.

Action: Connection processing fails. Unless the error is associated with an obvious cause, such as an outage of the target database or Oracle Net, you can report this message to Oracle Support Services for additional assistance.

AMI-0165 IMBEDDED SIGNON ATTEMPTED WITH MODE=SNGL PSB psb_name

Cause: An IMS transaction defined as MODE=SNGL caused a second ESAF signon call within a single transaction. This behavior is limited to MODE=MULTI transactions.

Action: Oracle Access Manager for IMS TM causes the transaction program to end with ABEND code U3045.

AMI-0169 INCORRECT STATE (number) AT TRANSACTION COMPLETION

Cause: IMS invoked the commit prepare or end thread processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: The application ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0170 ESAF COMMIT CALLED WITH UNEXPECTED RECOVERY TOKEN

Cause: The ESAF commit prepare or end thread exit was invoked with an IMS recovery token different from the one supplied when the transaction started.

Action: The transaction ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0174 INCORRECT STATE (number) AT TRANSACTION ABORT

Cause: IMS invoked the abort continue or end thread processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: The application ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0175 ESAF ABORT CALLED WITH UNEXPECTED RECOVERY TOKEN

Cause: The ESAF abort continue or end thread exit was invoked with an IMS recovery token different from the one supplied when the transaction started.

Action: The transaction ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0178 UNEXPECTED RESPONSE CODE (number) TO ORACLE ABORT

Cause: During ABORT processing for a transaction, the ABORT command sent to the Oracle database server received an unexpected response code as shown.

Action: The transaction ended with ABEND U3044. This message indicates an Oracle Access Manager for IMS TM or Oracle database server problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0179 ESAF TERMINATE THREAD 'DEALLOCATE' WITH IN-PROGRESS TRANSACTION

Cause: IMS has invoked the ESAF end thread exit with a deallocate request code while a transaction is still in progress.

Action: This message indicates an IMS or Oracle Access Manager for IMS TM logic problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0180 UNKNOWN ESAF TERMINATE THREAD COMMIT OPTION <opt>

Cause: IMS has invoked the ESAF end thread exit with an option code other than COMM, ABRT, or DEAL.

Action: The current transaction, if any, ends with an ABEND U3044. You can call Oracle Support Services for additional assistance.

AMI-0181 INCORRECT STATE (number) AT TERMINATE IDENTIFY

Cause: IMS invoked the end identify processing exit for Oracle Access Manager for IMS TM at an unexpected time.

Action: The application ends with ABEND U3044. This message indicates an internal IMS or Oracle Access Manager for IMS TM problem. You can report this message to Oracle Support Services for additional assistance.

AMI-0183 AMI REGION TERMINATION COMPLETED NORMALLY

Cause: End identify (disconnect) processing completed normally in the region.

Action: Processing continues; this message is informational.

AMI-0186 RECOVERY ACTION ON TRANSACTION token DEFERRED DUE TO DISCONNECT

Cause: During resolve in-doubt processing, a previous error caused connection to the Oracle database server to be lost.

Action: Processing continues; IMS retains the recovery token for later resolution. This message is normal for each recovery token processed after a disconnect.

AMI-0187 ABORT TRANSACTION FAILED AT TERMINATE IDENTIFY

Cause: An identify end has been called while there is still a transaction in progress, and the attempt to end the transaction in the Oracle database server has failed.

Action: You can report this message to Oracle Support Services for additional assistance.

AMI-0188 FAILED TO ALLOCATE MESSAGE BUFFER OF SIZE number

Cause: Initialize or identify was unable to allocate an Oracle error message buffer of the indicated size.

Action: Initialize or identify processing fails. Refer to the product documentation for a discussion of memory requirements.

AMI-0189 CONTROL REGION DBADDR DIFFERS FROM THIS DR DBADDR; net_type addr_string

Cause: The dependent region RTT contains a database address (DBADDR parameter of the AMIRT macro) or NET specification that differs from that specified in the control region RTT.

Action: Oracle Access Manager for IMS TM initialization for the region ends. The dependent region RTT must be regenerated or a different RTT used.

AMI-0190 function FOR SSN ssn FAILED, SUBSYSTEM UNAVAILABLE UNTIL RESTARTED

Cause: A failure in the indicated Oracle Access Manager for IMS TM function for the indicated subsystem has failed, causing IMS to place the subsystem in a logical stopped state. Details on the failure appeared in prior messages.

Action: Access to the affected target Oracle database server remains unavailable until the problem is corrected and the subsystem restarted using the IMS START SUBSYS command.

AMI-0191 UNABLE TO ALLOCATE SESSION ARRAY OF SIZE number

Cause: During Oracle Access Manager for IMS TM identify processing for the region, a request for session array memory of the indicated size failed.

Action: If this occurs in the control region, then Oracle Access Manager for IMS TM identify processing fails and the Oracle Access Manager for IMS TM instance is placed in a stopped state. Steps must be taken to ensure sufficient virtual memory is available in the region before Oracle Access Manager for IMS TM can be restarted. In a dependent region, Oracle Access Manager for IMS TM might attempt to allocate a smaller session array. If this is not possible or also fails, then identify processing for the region fails.

AMI-0193 TRACE COMMAND HAS SYNTAX ERROR - descr

Cause: A syntax error was found in the TRACE command.

Action: The tracing state is not changed. Change the command and reenter it.

AMI-0192 TRACE COMMAND PROCESSED SUCCESSFULLY

Cause: Trace command was processed successfully.

Action: Processing continues; this is a normal response to the Oracle Access Manager for IMS TM TRACE command.

AMI-0194 INVALID ACCESS MANAGER COMMAND - string

Cause: A command unknown to Oracle Access Manager for IMS TM has been entered through SSR.

Action: Issue the command correctly.

AMI-0195 ORACLE ERROR - INFORMATION FOLLOWS

userid=xxxx, PGM=xxxx, PSB=xxxx,Oracle userid=xxxx, lterm=xxxx, tran name=xxxx, REO option is x, oercid=xxxx, typ=xxx, fatal=xx, flg=xx, oerrcd=xx,opt=xx, par=xx, wflg=xx

Cause: This is an Oracle system error.

Action: Review the error information. You can contact Oracle Support Services for additional assistance. The following is a list of definitions of terms in the message:

- userid: The IMS TM user id

- PGM: The name of the IMS TM program

- PSB: The PSB name

- Oracle userid: The Oracle user ID

- lterm: The IMS logical terminal name

- tran name: The IMS TM transaction name

- REO option is: The IMS TM region error option

- oercid: The current cursor id (oercid)

- typ: The SQL command type (oertyp)

- fatal: The error action information (oeropt)

- flg: The flags (oerflg)

- oerrcd: The return code (oerrcd)

- opt: The user-specified cursor options (oeropt)

- par: The UPI parameter that generates the error (oerpar)

- wflg: The warning flag (oerwflg)

AMI-0196 SESSION CACHE OVERFLOWED

Cause: The session cache has no vacant entries and all occupied cache session is defined as protected.

Action:

- Increase the number of session cache entries (MAXSESS parm in AMIRT)

- Specify PROTECT=NO in AMITRANS macro

- Apply both the above actions

AMI-0197 ORACLE NOT RESPONDING. MANUAL INTERVENTION MIGHT BE REQUIRED.

Cause: Oracle Access Manager for IMS TM has determined that the target Oracle instance is not responding. The instance might have failed. If Oracle Net is being used, then the network connection to the target instance might not be operating normally.

Action: Check the status of the target Oracle instance. If Oracle Net is being used, then ensure it is operating properly and that the underlying network protocol is functioning normally

AMI-0198 ORACLE ERROR - (oci_error) - INFORMATION FOLLOWS

userid=xxxx, PGM=xxxx, PSB=xxxx, Oracle userid=xxxx, lterm=xxxx, tran name=xxxx

Cause: This is an Oracle system error.

Action: Review the error information. You can contact Oracle Support Services for additional assistance. The following is a list of definitions of terms in the message:

- oci_error: OCI error description or code.

- userid: The IMS user ID

- PGM: The name of the IMS program

- PSB: The PSB name

- Oracle userid: The Oracle user ID

- lterm: The IMS logical terminal name

- tran name: The IMS transaction name

2 Oracle Access Manager for CICS Messages

This chapter describes the messages issued by Oracle Access Manager for CICS while running under z/OS.

Oracle Access Manager for CICS messages begin with the prefix "CIC-."

The following messages are described in this chapter:

- Messages CIC-00001 to CIC-99999 (UNKNOWN STEP NUMBER)

- Abends Under Oracle Access Manager for CICS

2.1 Messages CIC-00001 to CIC-99999

CIC-00001E UNKNOWN COMMAND

Cause: The command, as entered, is unknown.

Action: Correct the command input and reenter the command.

CIC-00002E INVALID PARAMETER

Cause: The command specifies an invalid parameter.

Action: Check the command syntax, correct the parameters, and reenter the command.

CIC-00003E INVALID SYNTAX

Cause: The command, as entered, is incorrect.

Action: Check the command syntax for missing values or parentheses and reenter the command.

CIC-00004E INVALID VALUE

Cause: A keyword parameter specifies an invalid value.

Action: Correct the keyword parameter value and reenter the command.

CIC-00005E INVALID NUMBER

Cause: The command specifies an invalid value. The value must contain only numeric characters.

Action: Check the command syntax and reenter the command.

CIC-00007I CICS ATTACH xxxx SUCCESSFULLY INITIALIZED FOR ssn

Cause: Oracle Access Manager for CICS has initialized.

Action: None. This is an informational message.

CIC-00009E INVALID SSN

Cause: The specified SSN value is not valid or does not point to an active Oracle subsystem.

Action: Bring up the Oracle subsystem first; or contact your Oracle system administrator.

CIC-00010E INVALID NAME

Cause: The specified NAME parameter is not the name of an active Oracle Access Manager for CICS adapter.

Action: If the name is correct, then ensure the adapter is active. If the name is incorrect, then specify the correct name in the NAME parameter and reenter the command.

CIC-00011I SHUTDOWN IN PROGRESS FOR xxxx

Cause: Oracle Access Manager for CICS is shutting down.

Action: None. This is an informational message.

CIC-00012I SHUTDOWN COMPLETE FOR xxxx

Cause: Oracle Access Manager for CICS has ended.

Action: None. This is an informational message.

CIC-00013I ADAPTER NOT ACTIVE

Cause: The referenced Oracle Access Manager for CICS adapter is not active.

Action: None. This is an informational message.

CIC-00015E EXITS=YES REQUIRED IN SIT

Cause: Oracle Access Manager for CICS requires EXITS=YES.

Action: Contact your CICS system administrator for assistance.

CIC-00016E ADAPTER ALREADY ACTIVE

Cause: The Oracle Access Manager for CICS adapter being started is already active.

Action: None. This is an informational message.

CIC-00018E PROGRAM xxxx NOT FOUND

Cause: The module xxxx is not in a CICS library or the PPT; or, the version of the thread table is outdated.

Action: Ensure the module is in the correct library, is defined to CICS by RDO (CEDA) or PPT, and that the thread table has been compiled using the current distribution libraries. If so, then contact your CICS system administrator.

CIC-00017E UNABLE TO LOAD xxxx DUE TO AUTHORIZATION FAILURE

Cause: An attempt to load the module failed due to a NOTAUTH exception condition.

Action: Contact your CICS system administrator for assistance.

CIC-00023I CICS ATTACH xxxx INITIALIZED FOR ssn, SOME ERRORS OCCURRED

Cause: An error occurred while trying to initialize one or more threads.

Action: To determine the status of the threads, enter the DISPLAY THREADS command. The Oracle subsystem startup parameters might need to be adjusted.

CIC-00024E INITIALIZATION FOR xxxx FAILED. ORACLE ERROR CODE nnnn

Cause: An Oracle database server error occurred, preventing the completion of Oracle Access Manager for CICS initialization.

Action: Refer to the book Oracle Database Error Messages for information about the error code. The error probably occurred when you logged on to the Oracle server.

CIC-00025E EITHER MODNAME OR SSN, NAME, AND MAXTHREADS IS REQUIRED

Cause: To initialize the interface, Oracle Access Manager for CICS requires the name of a definition module assembled with the ORACICS macro or the SSN, NAME, and MAXTHREADS parameters.

Action: Enter the required parameters.

CIC-00026I EMERGENCY SHUTDOWN INVOKED FOR xxxx DUE TO ssn FAILURE

Cause: The Oracle server is no longer available.

Action: Restart Oracle Access Manager for CICS after restarting the corresponding Oracle server.

CIC-99999 MANUAL RESTART REQUIRED

Cause: The retry limit for the maximum number of consecutive occurrences of an OSDI loss of service condition has occurred. This message will immediately precede a CIC-00026 emergency shutdown message.

Action: For more information about CICS, refer to the Oracle Database System Administration Guide for IBM z/OS on System z.

2.2 Abends Under Oracle Access Manager for CICS

Oracle Access Manager for CICS will issue a CICS transaction ABEND "ORAP" under the following circumstances:

- A PURGE is issued from the active transaction display

- A SQL COMMIT/ROLLBACK statement is issued and AM4CICS has been started with COMMIT(CICS).

- A STOP IMMEDIATE FORCE statement is issued and there are active transactions. In this instance, AM4CICS will "ORAP" transactions which are connected to Oracle at the next call to the database. Shutdown will take effect when all the existing transactions have exited.

- AM4CICS has determined the database is no longer available and is in the process of performing an emergency shutdown. For more information about CICS, refer to Oracle Database System Administration Guide for IBM z/OS on System z.

- An application has not been linked with the ORACSTUB.

3 CFUTIL Messages

This chapter describes messages that are issued by CFUTIL, the Oracle Database 10g for z/OS convert file utility. The CFUTIL messages begin with the prefix "CFU-." The following messages are described in this chapter:

- Messages CFU-0001 to CFU-0013

3.1 Messages CFU-0001 to CFU-0013

CFU-0001 Command Syntax: cfutil CONVERTFOROSDI/CONVERTFORMPM <dsn> ...

Cause: This message indicates that insufficient parameters were supplied to the command.

Action: Correct the command and run it again.

CFU-0002 Invalid function: %s

Cause: This message indicates that the command was not CONVERTFOROSDI or CONVERTFORMPM.

Action: Correct the command and run it again.

CFU-0003 Memory allocation failed (__4kmalc)

Cause: This message indicates that insufficient memory is available. The "(__4kmalc)" indicates that a memory allocation of 4k failed.

Action: Increase the region size and run it again.

CFU-0004 Memory allocation failed (__4kmalc) for %d bytes

Cause: This message indicates that insufficient memory is available. The size attribute indicates that a memory allocation of the specified number of bytes failed.

Action: Increase the region size and run it again.

CFU-0005 Invalid data set name: %s

Cause: This message indicates that the supplied data set name is invalid. The data set name is too long, the data set does not exist, or the user running the control file utility does not have read/write access to the data set.

Action: Correct the problem, and run the job again.

CFU-0006 Starting commit to control file: %s

Cause: This message indicates normal progress of the utility. This message is for information only.

Action: No action is required.

CFU-0007 Committed changes to control file: %s

Cause: This message indicates normal progress of the utility. This message is for information only.

Action: When this message is received, all changes have been successfully committed to the control file.

CFU-0008 Close failed for data set name: %s

Cause: The close of the data set failed.

Action: Check for accompanying operating system errors that explain what happened. Running the job again will normally clear any problems that might occur at close time.

CFU-0009 %s (%s) failed, rc: %d, reason code: %d

Cause: This message indicates that an internal error occurred.

Action: Contact Oracle Support Services. The function that failed, and the return and reason codes, must be provided to Oracle Support Services for problem resolution.

CFU-0010 Processing data set name: %s

Cause: This message indicates normal progress of the utility. This message is for information only.

Action: No action is required.

CFU-0011 Command Syntax: cfutil CVTMIG/CVTARCLOG <dsn> <dsn>

Cause: For these two commands, two data set names must be supplied.

Action: Correct this situation by supplying the names of the source and target data sets.

CFU-0012 Error reading input data set

Cause: An error occurred while reading the input data set.

Action: No action is required.

CFU-0013 The data set is not a linear data set

Cause: The data set currently being processed is not a VSAM Linear Data Set (LDS). It must be converted to a linear data set by running the IBM IDCAMS utility. Refer to the installation documentation for details and sample JCL for doing this.

Action: No action is required.

4 Oracle Database for z/OS Installation Messages

This chapter describes the z/OS-specific messages that can appear during the installation of Oracle Database products on z/OS.

The installation messages all begin with the prefix "OFT-" followed by a 3-digit decimal number followed by a letter that indicates one of the following:

Table 4-1 Oracle Database Installation Message Letter Codes

Letter

Definition

E

Error. Action is required.

I

Information. Action is not required.

The following messages are described in this chapter:

- Messages OFT101I to OFT107I

- Messages OFT101E to OFT999E

4.1 Messages OFT101I to OFT107I

While installing the primary Oracle products, a TSO user selected panel option 2 to generate an INSTLIB member. This selection was based on the options chosen from the customization panels available through option 1. The following messages are received as a result.

OFT101I PHASE-I - VERIFY ORACLE INSTALLATION OPTION PARAMETERS

Cause: Validation of panel options occurs.

Action: None. This is an informational message.

OFT102I ORACLE INSTALLATION LIBRARY ALLOCATED, LIBRARY = 'instlib'

Cause: Allocation of the Oracle installation library instlib completed successfully.

Action: None. This is an informational message.

OFT104I PHASE-II - GENERATE ORACLE INSTALLATION JOB STREAM MEMBER. LIBRARY = 'instlib'. MEMBER = 'ispfile_member'

Cause: Validation phase I completed successfully. The Oracle tailoring process continues.

Action: None. This is an informational message. The ISPFILE member ispfile_member is created in Oracle installation library instlib.
The skeleton tailoring process tailors a member of ISPSLIB (an ISPF library) to an output library (the Oracle product set installation library). The created member is an IEBUPDTE job containing all the necessary JCL jobs, Oracle PARMLIB members, and procedures to install the Oracle product set.

OFT105I ISPSLIB FTINCL MEMBER (ispslib_member) PROCESSING COMPLETED. COMPLETION CODE xxxx

Cause: The ISPSLIB skeleton member tailoring process completed.

Action: Check for a successful completion code of 0. This is an informational message.

OFT106I ORACLE INSTALLATION JOB STREAM MEMBER CREATED. LIBRARY = 'instlib'. MEMBER = 'ispfile_member'. COMPLETION CODE xxxx

Cause: Creation of the ISPFILE member is complete.

Action: Check for a successful completion code of 0. This is an informational message.

OFT107I GENERATION PROCESS COMPLETED. COMPLETION CODE xxxx

Cause: Option 2 of the Oracle Primary Option Menu (OR@INST) completed.

Action: Check for a successful completion code of 0. For a completion code other than 0, refer to the additional message (OFTnnnE), which you also received, for resolution information.

4.2 Messages OFT101E to OFT999E

OFT101E ORACLE INSTALLATION LIBRARY NOT DEFINED. EXECUTION TERMINATED

Cause: An attempt to select panel option 2 on the Primary Option Menu occurred without specifying the Oracle installation library definition panel entry (ORPTIP15). This might be a user error.

Action: The tailoring process ends. Select option 1 and then option 5 (INSTLIB/ISPLIB file tailoring information) to access panel ORPTIP15. Check the entries on panel ORPTIP15, define all panel definition fields, and retry option 2.

OFT102E ORACLE INSTLIB LIBRARY DISPOSITION FIELD SPECIFIES INVALID PARAMETER. EXECUTION TERMINATED

Cause: The Oracle installation library disposition panel entry (ORPTIP15) specifies an invalid value. This might be a user error.

Action: The tailoring process ends. Select option 1 and then option 5 (INSTLIB/ISPLIB file tailoring information) to access panel ORPTIP15. Define an appropriate disposition of NEW or SHR for the INSTLIB library and retry option 2.

OFT103E ORACLE INSTLIB DATASET SPECIFIES INCORRECT VOLSER NAME. EXECUTION TERMINATED

Cause: The Oracle installation library VOLSER panel entry (ORPTIP15) specifies an invalid value. This might be a user error.

Action: The tailoring process ends. Select option 1 and then option 5 (INSTLIB/ISPLIB file tailoring information) to access panel ORPTIP15. Define the volume serial number of the DASD (direct access storage device) where the Oracle INSTLIB library resides and retry option 2.

OFT104E ORACLE INSTLIB UNIT FIELD SPECIFIES INCORRECT DEVICE NAME. EXECUTION TERMINATED

Cause: The Oracle INSTLIB library DEVICE TYPE panel entry (ORPTIP15) specifies an invalid value. This might be a user error.

Action: The tailoring process ends. Select option 1 and then option 5 (INSTLIB/ISPLIB file tailoring information) to access panel ORPTIP15. Define the device type name of the DASD device where the Oracle INSTLIB library resides and retry option 2.

OFT105E ALLOCATION FAILURE FOR ORACLE INSTLIB DDNAME "ISPFILE" DSN=instlib [VOLUME=volser UNIT=device_name] DISP=disp COMPLETION CODE xxxx. EXECUTION TERMINATED

Cause: The Oracle INSTLIB library allocation process received a nonzero completion code. This might be a user error.

Action: The tailoring process ends. The completion code xxxx is a TSO ALLOC command return code. Check the TSO allocation return codes to find out why the allocation request failed. Possible reasons for the failure are:

- The volume serial name volser is unknown to the system.

- A duplicate data set existed during allocation and the disposition field specified NEW.

- A DATASET NOT FOUND condition occurred because the panel definition for the INSTLIB disposition field specified SHR or the data set name was incorrect.

- An error occurred while defining the Oracle Database for z/OS panel entries (ORPTIP15) for the Oracle INSTLIB library.

Correct the reason for the failure and retry option 2.

OFT106E ORACLE INSTALLATION PROC/TSO CLIST LIBRARY dataset_name NOT DEFINED. EXECUTION TERMINATED

Cause: The procedure library has not been defined in the system. The installation customization process ends.

Action: Define the library, or select option 1 and then option 7 (define data sets for PROC, CLISTs, and temporary disk unit) to access panel ORPTIP25. Specify a library that already exists in the system and retry option 2.

OFT108E DUPLICATE INSTLIB MEMBER. "ispfile_member" MEMBER NOT REPLACED. EXECUTION TERMINATED

Cause: The REPLACE LIKE-NAMED INSTLIB MEMBER panel entry (ORPTIP15) specifies a NO value, protecting the member.

Action: You specified the member is not to be overwritten and the tailoring process ends. Before proceeding, you must rename the old member, delete the old member, or select a different option.
You also receive message OPT107I when this error occurs.

OFT109E ISPSLIB FTOPEN ERROR OCCURRED PROCESSING MEMBER(ispslib_member). COMPLETION CODE xxxx. EXECUTION TERMINATED

Cause: The ISPSLIB data set could not be opened for input processing. An ISPEXEC FTOPEN process caused the error.

Action: The tailoring process ended. This might be a user error. Check for the following possible errors:

- The ISPSLIB member does not exist. Member not found.

- The ISPSLIB library is enqueued because another user or the TSO user performing the Oracle installation is processing the data set.

The possible return codes are described as follows:

8 – File tailoring already in progress.

12 – Output file in use; ENQ failed.

16 – Skeleton library or output file not allocated.

20 – Severe error.

Correct the reason for the error and retry option 2.

OFT110E ISPSLIB ERROR DURING FTINCL MEMBER(ispslib_member) PROCESSING. COMPLETION CODE xxxx. EXECUTION TERMINATED

Cause: Processing of the ISPSLIB data set member could not occur because an ISPEXEC FTINCL process found an error, which was probably a B37 ABEND. This error usually occurs because the temporary ISPF data set used for file tailoring requires secondary extents and the allocated volume does not have free space for secondary space allocations. For a B37 ABEND, an IECnnnI message appears on the z/OS console and supplies the data set name.

Action: The tailoring process ended. This might be a user error. Possible errors are:

- The ISPSLIB member was not found or does not exist.

- The ISPSLIB skeleton member is in use.

The possible return codes are described as follows:

- 8 – Skeleton member (default name NEWSKEL) does not exist.

- 12 – Output file in use; ENQ failed.

- 16 – Data truncation occurred; or skeleton library or output file was not allocated.

- 20 – Severe error. Probably a B37 ABEND occurred. Ensure there is sufficient space on the allocated volume.

Correct the reason for the error and retry option 2.

OFT111E ISPFILE CLOSE ERROR DURING FTCLOSE NAME(ispfile_member) PROCESSING. COMPLETION CODE xxxx. EXECUTION TERMINATED

Cause: A library full condition prevented the copying of the ISPFILE member to the INSTLIB data set.

Action: The tailoring process ends. The possible return code is described as follows:

20 – Severe error. A B37, D37, or E37 ABEND has probably occurred.

Ensure sufficient space on the allocated volume for the temporary ISPF data set, compress the INSTLIB data set, and retry option 2.

OFT112E SERVICE NOT INVOKED. A VALID ISPF ENVIRONMENT DOES NOT EXIST

Cause: While installing the Oracle database server, a TSO user tried to use the Oracle CLIST ORIPO10 command in a non-ISPF environment.

Action: The CLIST ended without running.

OFT119E NO PRODUCTS OR LANGUAGES WERE SELECTED. PLEASE SELECT SOMETHING FROM EITHER OR BOTH

Cause: An attempt was made to move to panel ORDSN without selecting at least one product or language.

Action: Panel ORPRODS is displayed again. Select the appropriate products or languages and continue through the panels.

OFT919E type LIBRARY name NOT FOUND

Cause: An ISPF library of type type was not found while trying to allocate that library using data set name name.

Action: Check the high-level index specified for the ISPF data sets and check the name under which those data sets are installed.

OFT999E s (variable text)

Cause: This diagnostic message indicates a serious error with the installation process.

Action: Possible reasons for the problem are:

- Table ORADB is already open; try again later

- Table LANG is locked by another user; try again later

- Table table_name is locked by another user; try again later

- You entered the same data set name for different products; rename and try again

- No products or languages were selected; select products or languages and try again

If the error persists, then you can contact Oracle Support Services for additional assistance.

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 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, ensure 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 ensure 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 file name 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.

6 Server Infrastructure Error Codes

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:

6.1 ORA-04101 Error Codes 1060 to 1349

1060

Latch state error on latch free. Report this error to Oracle Support Services.

1061

Latch state error on latch free. Report this error to Oracle Support Services.

1062

Latch state error on latch get. Report this error to Oracle Support Services.

1063

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.

1064

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.

1065

Invalid state to create SGA. Report this error to Oracle Support Services.

1066

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.

1067

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).

1068

An MMGRSRV CONNECT request failed during database file extend processing. Report this error to Oracle Support Services.

1069

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1070

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1071

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.

1072

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.

1073

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.

1074

An invalid user ID length was passed to Oracle SAF-based logon authorization checking. This can occur if an Oracle user ID longer than 8 characters is submitted to the SAF check.

1075

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.

1076

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.

1077

An invalid I/O request was attempted during RMAN backup or restore processing; report to Oracle Support Services.

1078

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1079

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1080

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1081

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1082

A file parameter string longer than 256 bytes was passed to an RMAN backup/restore function.

1083

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.

1084

An unexpected error occurred during POST processing; report to Oracle Support Services.

1085

An invalid parameter was passed to the POST function; report to Oracle Support Services.

1086

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1087

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1088

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1089

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1090

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1091

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1092

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.

1093

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.

1094

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1095

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1096

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.

1097

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.

1098

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.

1099

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.

1100

Internal RMAN proxy backup/restore error; report to Oracle Support Services.

1101

A call to a z/OS UNIX System Services function has abended; report to Oracle Support Services.

1102

An invalid argument list was supplied for a z/OS UNIX System Services call; report to Oracle Support Services.

1103

Internal error in processing a z/OS UNIX System Services function call; report to Oracle Support Services.

1104

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.

1105

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.

1106

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 user ID under which the Oracle server address space runs. It can also occur if no z/OS user ID is associated with the server address space.

1107

File name buffer length error; report this error to Oracle Support Services.

1108

Invalid file handle; report this error to Oracle Support Services.

1109

Invalid resource string passed to RACROUTE check for CONNECT AS SYSOPER/SYSDBA; report this error to Oracle Support Services.

1110

The RACROUTE check for CONNECT AS SYSOPER/SYSDBA failed. This is a normal condition if the z/OS user ID that is attempting to connect is not authorized to connect as either SYSOPER or SYSDBA.

1111

An invalid database name was passed to the instance lock routine; report this error to Oracle Support Services.

1112

An unexpected error occurred on the ENQ used to serialize database mount; report this error to Oracle Support Services.

1113

An attempt to allocate memory for an IDCAMS request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).

1114

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).

1115

Invalid length in alert log message; report this error to Oracle Support Services.

1116

Oracle is attempting to delete a file that is still open to one or more processes; report this error to Oracle Support Services.

1117

An invalid security profile suffix was supplied for a RACROUTE request; report this error to Oracle Support Services.

1118

A LOAD macro for IDCAMS failed; report this error to Oracle Support Services.

1119

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.

1120

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).

1121

Internal error in database file request; report this error to Oracle Support Services.

1122

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).

1123

Internal error in database file request; report this error to Oracle Support Services.

1124

An attempt to extend a database file failed because I/O to the file has not quiesced. Report this error to Oracle Support Services.

1125

Invalid file handle for file sync request; report this error to Oracle Support Services.

1126

Invalid file handle for file sync request; report this error to Oracle Support Services.

1127

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.

1128

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.

1129

Invalid parameter for timer wait; report this error to Oracle Support Services.

1130

An attempt to allocate memory for a timer request failed. This indicates that virtual memory is nearly exhausted in server address space 1 (AS1).

1131

Invalid parameter for timer wait; report this error to Oracle Support Services.

1132

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).

1133

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).

1134

Invalid database file handle for close; report this error to Oracle Support Services.

1135

Invalid database file handle for extend; report this error to Oracle Support Services.

1136

Invalid database file handle for extend; report this error to Oracle Support Services.

1137

An MMGRSRV CATUPDT failed during database file sync processing. Report this error to Oracle Support Services.

1138

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.

1139

An MMGRSRV CONNECT request failed during database file open processing. Report this error to Oracle Support Services.

1140

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.

1141

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).

1142

Invalid file handle passed to database file open; report this error to Oracle Support Services.

1143

Invalid file handle passed to database file open; report this error to Oracle Support Services.

1144

Invalid file handle passed to database file close; report this error to Oracle Support Services.

1145

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.

1146

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.

1147

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).

1148

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).

1149

Invalid file handle passed to database file open; report this error to Oracle Support Services.

1150

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.

1151

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).

1152

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.

1153

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.

1154

Invalid database file function code. Report this error to Oracle Support Services. An SDUMP will be generated.

1155

Internal error detected during database file state processing. Report this error to Oracle Support Services. An SDUMP will be generated.

1156

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).

1157

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.

1158

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.

1160

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.

1161

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.

1162

Invalid data module load parameter. Report this error to Oracle Support Services.

1163

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.

1164

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.

1166

I/O or other error on a BSAM WRITE macro. Report this error to Oracle Support Services.

1167

Invalid record length for a BSAM WRITE. Report this error to Oracle Support Services.

1168

Invalid file handle for BSAM or BPAM file write. Report this error to Oracle Support Services.

1169

I/O error during buffer flush of a BSAM data set that is being closed. Report this error to Oracle Support Services.

1170

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.

1171

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).

1172

Invalid file handle for BSAM or BPAM file read. Report this error to Oracle Support Services.

1173

Invalid file handle for BSAM or BPAM file close. Report this error to Oracle Support Services.

1174

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.

1175

Invalid parameter on BSAM/BPAM file close request. Report this error to Oracle Support Services.

1176

Invalid file handle for BSAM or BPAM file close. Report this error to Oracle Support Services.

1177

ABEND in file task 3 services function. An SDUMP is generated for this. Report this error to Oracle Support Services.

1178

Invalid parameter in a file services task 3 request. An SDUMP is generated for this. Report this error to Oracle Support Services.

1179

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.

1180

An unexpected ABEND occurred while processing an OPEN for a BSAM or BPAM data set. Report this error to Oracle Support Services.

1181

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.

1182

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.

1183

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.

1184

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.

1185

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.

1186

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.

1187

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.

1188

Invalid parameter or option combination on a request to open a BSAM or BPAM data set. Report this error to Oracle Support Services.

1189

An invalid BSAM or BPAM file task request was issued. An SDUMP is generated for this. Report this error to Oracle Support Services.

1190

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.

1191

Unexpected result from file name normalization. Report this error to Oracle Support Services.

1192

Invalid file name length for BSAM or BPAM data set processing. Report this error to Oracle Support Services.

1193

Invalid parameter or option combination on a request to open a BSAM or BPAM data set. Report this error to Oracle Support Services.

1194

Inadequate buffer length for normalized file name. Report this error to Oracle Support Services.

1195

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.

1196

File name syntax error. This is an expected error when a file name string supplied to an Oracle server contains invalid characters or syntax.

1197

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.

1198

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.

1199

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.

1200

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.

1201

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.

1202

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.

1203

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.

1204

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.

1205

An IDCAMS function requested by EDM has returned an error. Refer to the EDM job log or SYSPRINT for details on the error.

1206

Buffer state error during EDM processing. Report this error to Oracle Support Services.

1207

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.

1208

An invalid request was made to EDM. Report this error to Oracle Support Services.

1209

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.

1210

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.

1211

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.

1212

An error occurred during EDM dynamic unallocation processing. Report this error to Oracle Support Services.

1213

An IDCAMS function requested by EDM has returned an error. Refer to the EDM job log or SYSPRINT for details on the error.

1214

A RDJFCB macro for an EDM backup data set failed. Report this error to Oracle Support Services.

1215

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.

1216

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.

1217

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.

1218

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.

1219

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.

1220

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.

1221

An attempt to catalog an EDM-created backup piece has failed. Refer to the EDM job log for additional details on the error.

1222

An error occurred during EDM dynamic unallocation processing. Report this error to Oracle Support Services.

1301

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.

1302

IXCQUERY answer area too small. IXCQUERY return code x'04', reason code x'04'. Report this error to Oracle Support Services.

1303

STORAGE OBTAIN failed for MIRXCFRQ storage. Report this error to Oracle Support Services.

1304

IXCJOIN with return code 4, but not reason code x'04'. Report this error to Oracle Support Services.

1305

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.

1306

STORAGE OBTAIN failed for history table XNGHT. (MIRXNJG) Report this error to Oracle Support Services.

1307

Bitmap of group memberships is full. No more Oracle instances can be added to the cluster. (MIRXNJG) Report this error to Oracle Support Services.

1308

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.

1309

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.

1310

The history table XNGHT contains no unproccessed entries therefore no new entries can be added. (MIRXNPS) Report this error to Oracle Support Services.

1311

An MIRXCFRQ did not contain the correct information to perform the request. Report this error to Oracle Support Services.

1312

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.

1313

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.

1314

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.

1315

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.

1316

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.

1317

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

1318

STORAGE OBTAIN failed for MIRXCFRQ storage. (MIRXNCM) Report this error to Oracle Support Services.

1319

STORAGE OBTAIN failed for answer area storage. (MIRXNCM) Report this error to Oracle Support Services.

1320

ECB posting error. (MIRXNPS) Report this error to Oracle Support Services.

1321

IXCQUERY answer area too small. IXCQUERY return code 4, reason code 4. (MIRXNCM) Report this error to Oracle Support Services.

1322

An MIRXCFRQ was formatted incorrectly. (MIRXCFT) Report this error to Oracle Support Services.

1323

STORAGE OBTAIN failed for background task. (MIRXCFT) Report this error to Oracle Support Services.

1324

STORAGE RELEASE failed for background task. (MIRXCFT) Report this error to Oracle Support Services.

1325

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.

1326

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.

1327

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.

1328

Background task abended and recovered while processing a MIRXCFRQ request. (MIRXCFT) Report this error to Oracle Support Services.

1329

Invalid exit name was passed on a MIRXCFRQ connect request. (MIRXCFT) Report this error to Oracle Support Services.

1330

Invalid user state data was passed to the IPC open routine. (MIRXCFO) Report this error to Oracle Support Services.

1331

Invalid member data was passed to the IPC open routine. (MIRXCFO) Report this error to Oracle Support Services.

1332

STORAGE OBTAIN failed for MIRXCFRQ storage. (MIRXCFS) Report this error to Oracle Support Services.1

1333

STORAGE OBTAIN failed while processing an IPC request. (MIRXCFS) Report this error to Oracle Support Services.

1334

STORAGE RELEASE failed while processing an IPC request. (MIRXCFS) Report this error to Oracle Support Services.

1335

An invalid parameter was passed to an IPC routine. Report this error to Oracle Support Services.

1336

An unknown internal error occurred while processing and IPC request. Report this error to Oracle Support Services.

1337

An invalid storage address was passed to an IPC routine. Report this error to Oracle Support Services.

1338

An invalid parameter was passed to a node monitor routine. (MIRXCFPM) Report this error to Oracle Support Services.

1339

There is no more room in the node monitor member data table. (MIRXCFPM) Report this error to Oracle Support Services.

1340

STORAGE RELEASE failed in a node monitor routine. (MIRXCFGM) Report this error to Oracle Support Services.

1341

STORAGE OBTAIN failed in a node monitor routine. (MIRXCFPM) Report this error to Oracle Support Services.

1342

A get member data request failed on target instance. (MIRXCFGM) Report this error to Oracle Support Services.

1343

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.

1344

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.

1345

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.

1346

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.

1347

The request by the node monitor to set a timer failed. Report this error to Oracle Support Services.

1348

ENQ request issued by a node monitor routine failed. Report this error to Oracle Support Services.

1349

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.

7 Client Infrastructure Messages

This chapter documents the messages that are issued by z/OS-specific components of the Oracle client software on z/OS. The messages may appear in SYSLOG, at the user's terminal when running an Oracle tool or utility, or in a customer-written application in TSO, batch, or a z/OS UNIX System Services shell environment.

The messages begin with the prefix "MIC" followed by a 3- or 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:

Table 7-1 Client Infrastructure Message Letter Codes

Letter

Definition

E

Error. Action is required.

I

Information. Action is not required.

W

Warning. Action may be required.

The following messages are described in this chapter:

- Messages MIC011E to MIC022E

- Messages MIC0208E to MIC0377E

7.1 Messages MIC011E to MIC022E

MIC011E Oracle API processing error, reason code n

Cause: During Oracle API call processing, an error was detected in the Oracle linking stub. This message is followed by an ABEND with user completion code 2010 (U2010) and the reason code in general register 15.

Action: Refer to the description of ABEND U2010 in Chapter 11, "User Abend Codes" for an explanation of the possible reason codes.

MIC012E LE condition raised during Oracle API op, condition token = xxx xxx xxx

Cause: During Oracle API call processing, a Language Environment (LE) condition was raised. The "op" text indicates the API activity during which the error occurred:

- Initialization – API initial loading and setup

- Argument dereference – accessing arguments (parameters) of the function call

- Call – Oracle API code in control

- Termination – termination and cleanup of the interface

- [Unknown state] – indeterminate activity

The LE condition token associated with the error is displayed in hexadecimal on the following line.

Action: This error may be accompanied by other messages related to the error in the system log or the LE message destination. Check these places for additional data describing the error. Errors during argument dereference and certain initialization errors (such as inability to load the Oracle program interface module) can be caused by problems in the application or the environment (for example, STEPLIB). If the error does not seem to be caused by the application or the environment, report this message to Oracle Support Services. Refer to IBM Language Environment documentation for a description of LE condition tokens and their meanings.

MIC013E Oracle API call from a non-LE environment.

Cause: This message is written to SYSLOG during Oracle API call processing when a non-LE environment is detected and is accompanied by User Abend 2010 with reason code 3.

Action: For information about compiling and linking customer applications, refer to the Oracle Database User's Guide for IBM z/OS on System z.

MIC021E Failed to find function fff in Oracle API mmm - errno nnn, <errno-string>

Cause: During Oracle API call processing, an attempt to resolve the DLL function "fff" failed. The API module in use is "mmm" and the Language Environment error number (errno) is "nnn". The string text associated with this error appears on the following line.

Action: Contact Oracle Support Services for assistance.

MIC022E Failed to load Oracle API module mmm - errno nnn, <errno-string>

Cause: During Oracle API call processing, an attempt to load the Oracle program interface failed. The API module in use is "mmm" and the Language Environment error number (errno) is "nnn". The string text associated with this error appears on the following line.

Action: Check to see whether the required Oracle library (typically the "CMDLOAD" data set) has been specified in STEPLIB or JOBLIB or made available through the system link list. In the z/OS UNIX System Services environment, a STEPLIB environment variable may be needed.

7.2 Messages MIC0208E to MIC0377E

MIC0208E Insufficient memory for FNA data; type t not stored

Cause: During FNA initialization, a request for memory to store FSA data for FTYPE t failed. FNA initialization processing is terminated, so subsequent entries in the ORA$FNA file are not processed.

Action: Provide a larger maximum region for the application. If this does not resolve the problem, report this error to Oracle Support Services.

MIC0209E Duplicate FNA entry for type t ignored

Cause: During FNA initialization, more than one FSA entry for FTYPE t was found. Only the first FSA entry in the ORA$FNA file is honored; the duplicates are discarded.

Action: Remove the duplicate entries from the file.

MIC0210E Insufficient storage for FNA initialization

Cause: During FNA initialization, a memory request for the FNA context area failed.

Action: Provide a larger maximum region for the application. If this does not resolve the problem, report this error to Oracle Support Services.

MIC0211E Invalid FNA input at line l position p

Cause: During FNA initialization, a syntax error was encountered in the ORA$FNA file. The line number l equates to a logical record number if ORA$FNA specifies a data set, or to a line number if ORA$FNA specifies an HFS file. The position p is the approximate character on the line or record where the error was detected. Both l and p are 1-origin numbers. Processing continues without the affected FSA data.

Action: Correct the syntax error and rerun the application.

MIC0212E Duplicate FNA keyword (n) at line l position p

Cause: During FNA initialization, the same keyword was specified twice in one FSA entry. The decimal number n identifies the keyword, as follows:

9 – FSA

10 – FTYPE

11 – FNAME

12 – FATTR

The line number l equates to a logical record number if ORA$FNA specifies a data set, or to a line number if ORA$FNA specifies an HFS file. The position p is the approximate character on the line or record where the duplicate was detected. Both l and p are 1-origin numbers. The entire FSA entry is ignored and processing continues without it.

Action: Correct the duplication and rerun the application.

MIC0213E Invalid FNA FTYPE at line l position p

Cause: During FNA initialization, an illegal FTYPE was encountered in the ORA$FNA file. The line number l equates to a logical record number if ORA$FNA specifies a data set, or to a line number if ORA$FNA specifies an HFS file. The position p is the approximate character on the line or record where the error was detected. Both l and p are 1-origin numbers. Processing continues without the affected FSA data.

Action: Correct the duplication and rerun the application.

MIC0214E Missing FTYPE in FNA entry - FSA entry ignored

Cause: During FNA initialization, an FSA with no FTYPE keyword was found in the ORA$FNA file. Processing continues without the affected FSA data.

Action: Correct the error and rerun the application.

MIC0215E No FNAME or FATTR in FNA entry - FSA entry ignored

Cause: During FNA initialization, an FSA with no FNAME or FATTR keyword was found in the ORA$FNA file. Processing continues without the affected FSA data.

Action: Specify FNAME, FATTR, or both in the entry.

MIC0216W Skipping input until next FSA keyword

Cause: Due to an error, FNA initialization is skipping all input until the next FSA keyword is found. This message always follows a specific input error message.

Action: Correct the error described by the accompanying message.

MIC0217W No further FNA input processed

Cause: This message appears after another more specific error message. It indicates that no further FNA input will be processed.

Action: Correct the error described by the accompanying message.

MIC0218E FNA input string or name too long at line l position p

Cause: During FNA initialization, an input keyword or string was too long to process. The line number l equates to a logical record number if ORA$FNA specifies a data set, or to a line number if ORA$FNA specifies an HFS file. The position p is the approximate character on the line or record where the error was detected. Both l and p are 1-origin numbers. Processing continues without the affected FSA data.

Action: Correct the error and rerun the application.

MIC0219E LE error (errno) reading FNA input; treating as EOF LE-message

Cause: During FNA initialization, a read request to the ORA$FNA input file returned an error. The errno value is the LE error number in decimal and LE-message is the text description of the error returned by LE. FNA initialization terminates but processing proceeds.

Action: Correct the problem with the ORA$FNA input file and rerun the application. If there appear to be no problems with the file, report this error to Oracle Support Services.

MIC0220W Warning: FNA string input terminated by EOF

Cause: During FNA initialization, an input keyword or string was not properly terminated and the end of the ORA$FNA file was reached. FNA initialization continues using the possibly truncated data.

Action: Correct the syntax error in the ORA$FNA file.

MIC0221W FNA entry ended by abrupt EOF

Cause: During FNA initialization, an FSA entry was ended by EOF rather than a closing parenthesis. FNA initialization continues using the possibly truncated entry.

Action: Correct the syntax error in the ORA$FNA file.

MIC0222I Found FSA at line l position p

Cause: After message MIC017W, this message indicates the point in the FNA input file where the next FSA was found. The line number l equates to a logical record number if ORA$FNA specifies a data set, or to a line number if ORA$FNA specifies an HFS file. The position p is the approximate character on the line or record where the keyword was detected. Both l and p are 1-origin numbers.

Action: Correct the error that led to message MIC017W.

MIC0223W EOF reached inside FNA comment text

Cause: During FNA initialization, EOF occurred while inside comment

Cause: text in the ORA$FNA file. This may indicate a syntax error in the file.

Action: Terminate any comments in the ORA$FNA file with "*/" (asterisk and forward slash).

MIC0224E LE error (errno) opening FNA input file f LE-message/

Cause: During FNA initialization, the request to open the FNA input file failed. The errno value is the LE error number in decimal, f is the input filespec, and LE-message is the text description of the error returned by LE. FNA initialization terminates but processing proceeds.

Action: Correct the problem with the ORA$FNA input file and rerun the application. If there appear to be no problems with the file, report this error to Oracle Support Services.

MIC0225W Unable to schedule FNA cleanup routine

Cause: During FNA initialization, an attempt to schedule an enclave cleanup routine using the atexit() service failed. Processing continues, but it is possible for the enclave to leak memory due to the absence of cleanup processing at enclave termination.

Action: Try to rerun the application with a larger maximum region. If the problem persists, report it to Oracle Support Services.

MIC0330E Insufficient storage for utility initialization

Cause: During Oracle tool or utility initialization, memory for command line argument or parameter processing could not be obtained. Tool or utility initialization fails.

Action: Provide a larger maximum region for the application. If the problem persists, report it to Oracle Support Services.

MIC0331E Invalid argument count (c) for utility initialization

Cause: During Oracle tool or utility initialization, an invalid command line argument or parameter count was detected.

Action: Report this error to Oracle Support Services.

MIC0350E Env file f open failed with LE error errno, LE-message

Cause: During Oracle environment variable initialization, an environment variable file could not be opened. The f value is the filespec, errno is the LE error number in decimal, and LE-message is the text string associated with the error number. Tool, utility, or application initialization fails after this error.

Action: Correct the problem with the environment file and rerun the application. If the problem persists, report this error to Oracle Support Services.

MIC0351W Env file f line l too long, ignored

Cause: During Oracle environment variable initialization, a line of an input environment variable file was too long to process. In the message text, f is the filespec and l is the logical record or line number (1-origin). Processing continues, but any environment variable specified on the line is ignored.

Action: Lines or records in an environment variable file are limited to 1023 data bytes. Shorten the line (HFS) or record (data set) that caused the error.

MIC0352E Env file f misquoted value on line l ignored

Cause: During Oracle environment variable initialization, a variable assignment value was not quoted properly. In the message text, f is the filespec and l is the logical record or line number (1-origin). Processing continues, but any environment variable specified on the line is ignored.

Action: Environment variables that begin with a quote must end with one on the same record or line. Correct the error and rerun the application.

MIC0353E Env file f LE putenv error errno on: setting LE-message

Cause: During Oracle environment variable initialization, setting of a variable through the LE putenv() function returned an error. In the message text, f is the filespec, errno is the LE error number in decimal, setting is the variable assignment statement that was passed to putenv(), and LE-message is the text associated with the LE error. Processing continues without the associated environment variable setting.

Action: If the problem does not seem to be associated with something like the region being too small, report this error to Oracle Support Services.

MIC0354E Env file f syntax error, line l ignored

Cause: During Oracle environment variable initialization, a syntax error was detected in an environment variable file. In the message text, f is the filespec and l is the logical record or line number (1-origin). Processing continues, but any environment variable specified on the line is ignored.

Action: Correct the error and rerun the application.

MIC0355E Env file f I/O error errno, LE-message

Cause: During Oracle environment variable initialization, an I/O error occurred on a read request to an environment variable file. In the message text, f is the filespec, errno is the LE error number in decimal, and LE-message is the text associated with the error. Tool, utility, or application initialization fails.

Action: Correct the problem with the environment variable file and rerun the application. If the problem persists, report this error to Oracle Support Services.

MIC0356W LE error errno closing env file f, LE-message

Cause: During Oracle environment variable initialization, a request to close an environment variable file returned an error. In the message text errno is the error number in decimal, f is the filespec, and LE-message is the text associated with the error. Processing continues normally.

Action: Report this error to Oracle Support Services.

MIC0357E Insufficient memory to set env var varname

Cause: During Oracle environment variable initialization, a request for memory for an environment variable failed. In the message text varname is the name of the variable whose request failed. Processing continues with the variable being set.

Action: Increase the maximum available region and rerun the application. If the problem persists, report this error to Oracle Support Services.

MIC0370E Argument file f line/record too long

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, an input record or line was too long to process. Tool or utility initialization fails.

Action: Record or lines in a ++ parameter file are limited to 1023 data bytes. Correct the file contents and rerun the application.

MIC0371E Mismatched quote in argument file f

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, an argument was begun with a quote but no ending quote was found. Tool or utility initialization fails.

Action: Quoted arguments in a ++ parameter file must have a closing quote. Correct the problem and rerun the application.

MIC0372E Insufficient storage for utility argument processing

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, a request for memory to store argument values failed. Tool or utility initialization fails.

Action: Increase the maximum available region and rerun the application.

Action: If the problem persists, report this error to Oracle Support Services.

MIC0373E LE error errno opening argument file f LE-message

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, the request to open the file failed. In the message text, errno is the LE error number in decimal, f is the filespec, and LE-message is the text associated with the error. Tool or utility initialization fails.

Action: Correct the problem with the ++ argument file and rerun the application. If the problem persists, report this error to Oracle Support Services.

MIC0374E Error processing argument filespec f, err-data

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, examination of the filespec produced an error. In the message text, f is the filespec and err-data is additional details about the error. Tool or utility initialization fails.

Action: This error usually results from invalid syntax in the ++ filespec or from attempting to use an Oracle runtime filespec (such as DD or DSN) when Oracle runtime compatibility is disabled. If neither of those is the cause, report this error to Oracle Support Services.

MIC0375W Error errno closing argument file f LE-message

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, a request to close the file failed. In the message text errno is the error number in decimal, f is the filespec, and LE-message is the text associated with the error. Processing continues normally.

Action: Report this error to Oracle Support Services.

MIC0376E Argument file f I/O error errno LE-message

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, a request to read the file failed. In the message text errno is the error number in decimal, f is the filespec, and LE-message is the text associated with the error. Tool or utility initialization fails.

Action: Correct the problem with the file and rerun the application. If the problem persists, report it to Oracle Support Services.

MIC0377E Error (rc) opening argument filef , err-data

Cause: During Oracle tool or utility initialization processing for a parameter (++) file, a request to open the file failed. In the message text rc is an internal return code in decimal, f is the filespec, and err-data is additional details describing the error. Tool or utility initialization fails.

Action: This error should be accompanied by another providing more details on the open problem. Correct the problem with the file and rerun the application. If the problem persists, report it to Oracle Support Services

8 Network Messages

This chapter describes the messages that are issued by the Oracle Network Service on z/OS. Error and warning messages are written to the system console. Informational messages are generally only written to the Oracle NETLOG DD.

The messages all begin with the prefix "MIN" followed by a 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:

Table 8-1 Network Message Letter Codes

Letter

Definition

E

Error. Action is required.

I

Information. Action is not required.

S

Severe error. Action is required. Oracle Net probably will terminate.

W

Warning. Action may be required.

The network messages are often created with character substitutions. In the messages below,%x represents some hexadecimal value, %d a decimal value, and %c a character value. The number of x's, d's, and c's after the % represent the precision of the expected value with the % counting as 1. For example %cccc means that a character value substitution with a length of five is expected.

To find the return code values for TCP/IP failures, refer to the IBM manual Communications Server IP and SNA Codes or its equivalent for the level of z/OS.

The following messages are described in this chapter:

- Messages MIN0001I to MIN1105E

8.1 Messages MIN0001I to MIN1105E

MIN0001I networking service initializing

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0002I networking service %ccccccc initialization complete

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0003E module MINMAIN is not in an APF-authorized library

Cause: Oracle Net must be executed from an APF authorized library.

Action: Authorize the library and restart Oracle Net.

MIN0004E unable to obtain storage for global vector

Cause: Not enough virtual storage is available to Oracle Net.

Action: Increase the Oracle Net region and restart.

MIN0005I global vector is at %xxxxxxx

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0006E failure executing ASEXT, R15 = %d, R0 = %d

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0008E unable to obtain %dddd bytes of storage for %ccccccc

Cause: Insufficient storage space is available.

Action: Increase the Oracle Net region and restart.

MIN0009E unable to obtain %dddd bytes of %ccc for %ccccccc, rc = %d

Cause: Insufficient storage space is available.

Action: Increase the Oracle Net region and restart.

MIN0010E unable to attach subtask %ccccccc, ATTACH RC = %ddd

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0011E subtask %ccccccc abended with S%xx/U%ddd during initialization.

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0012E Invalid reply area on %ccccccc to subsystem %ccc

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0013E signon to subsystem %ccc rejected, RC = %ddd

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0014E signon to subsystem %ccc failed, RC = %ddd, RSN = %ddd, INFO = %ddd

Cause: This message is a critical error. Oracle Net will not function properly.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0016I command service subtask initialized

Cause: This message is a normal Oracle Net start up message

Action: No action is required.

MIN0017I message service subtask initialized

Cause: This message is a normal Oracle Net start up message

Action: No action is required.

MIN0018I bind/unbind service subtask initialized

Cause: This message is a normal Oracle Net start up message

Action: No action is required.

MIN0019W multiple TCP/IP tasks requested, none will be started

Cause: Only one TCP/IP protocol task may be active within Oracle Net.

Action: Correct the OSDI Oracle Net start parms.

MIN0020W Internal tracing will not be performed

Cause: There was not enough storage available for the internal trace table.

Action: This message is not a fatal error, but the Oracle Net region should be increased and Oracle Net restarted.

MIN0021E unable to start networking task, storage unavailable

Cause: Storage is unavailable.

Action: Increase the Oracle Net region and restart.

MIN0022W Invalid service parameter %ccccccc ignored

Cause: The parameter shown from the service definition or alter is not recognized.

Action: This message may indicate that Oracle Net was started with a JES start command rather than an OSDI subsystem start command. The latter must be used.

MIN0023W Invalid service parameter beginning with %ccccccc, ignored

Cause: The parameter shown from the service definition or alter is not recognized.

Action: This message may indicate that Oracle Net was started with a JES start command rather than an OSDI subsystem start command. The latter must be used.

MIN0024I connected to WLM subsystem %cccc

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0025W WLM not active, connect failed RC=%xxxx RSN=%xxxxxxxx

Cause: Oracle Net will continue, but work will be scheduled into the Oracle server on preemptable SRB's instead of enclave SRB's and the work will not be managed by WLM.

Action: Activate WLM if you want to have it manage the work scheduled for the Oracle server.

MIN0026I timer service subtask initialized

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0027I session/transaction enclave duration

Cause: This message indicates the enclave duration for WLM services.

Action: No action is required.

MIN0091I timer service subtask terminated

Cause: This message is a normal Oracle Net start up message.

Action: No action is required.

MIN0092W WLM disconnect failed RC=%xxxx RSN=%xxxxxxxx

Cause: Oracle Net will continue to terminate, but a graceful termination of WLM services was not possible.

Action: None, Oracle Net will continue shutdown.

MIN0093I command service subtask terminated

Cause: This message is a normal Oracle Net termination message.

Action: No action is required.

MIN0094I message service subtask terminated

Cause: This message is a normal Oracle Net termination message.

Action: No action is required.

MIN0095I bind/unbind service subtask terminated

Cause: This message is a normal Oracle Net termination message.

Action: No action is required.

MIN0096E signoff from subsystem %ccc rejected, RC = %ddd

Cause: Oracle Net has been stopped but cannot properly remove itself from the OSDI subsystem.

Action: This message should be reported to Oracle Support Services.

MIN0097E signoff from subsystem %ccc failed, RC = %ddd, RSN = %ddd, INFO = %ddd

Cause: Oracle Net has been stopped but cannot properly remove itself from the OSDI subsystem.

Action: This message should be reported to Oracle Support Services.

MIN0098I networking service %ccccccc termination in progress

Cause: This message is a normal Oracle Net termination message.

Action: No action is required.

MIN0099I networking service termination complete

Cause: This message is a normal Oracle Net termination message.

Action: No action is required.

MIN0100W command ignored, shutdown in progress

Cause: Modify commands cannot be processed once Oracle Net receives a stop command. It may take several minutes for Oracle Net to shut down after the stop command has been received.

Action: Allow Oracle Net to continue its shutdown. Do not try to enter more commands.

MIN0101I task %ccccccc already active, START command ignored

Cause: A modify command is trying to start a protocol that is already active.

Action: No action is required.

MIN0102I task %ccccccc not active, STOP command ignored

Cause: A modify command is trying to stop a protocol that is not yet active.

Action: No action is required.

MIN0103E unrecognized command verb

Cause: A modify command has been entered, but it does not specify one of the support action verbs.

Action: Enter a corrected command.

MIN0104E unrecognized keyword in command

Cause: A modify command has been entered, but it does not specify a supported keyword for the provided verb.

Action: Enter a corrected command.

MIN0105E unrecognized OSDI command %d

Cause: An OSDI command has been entered, but it does not specify an action verb supported by Oracle Net.

Action: Enter a corrected command.

MIN0106E error retrieving OSDI command, RC = %d

Cause: An OSDI command has been entered for Oracle Net, but Oracle Net was unable to retrieve the actual command.

Action: Report this error to Oracle Support Services.

MIN0107E TCP/IP subtask %ccccccc already active, START command ignored

Cause: An attempt was made to start a second TCP/IP protocol task. This is not allowed.

Action: Stop the active protocol task before attempting another start.

MIN0108E Resource error while attempting display command.

Cause: A request was made to display the current active protocol connections, but resources are not available to do so without interfering with activity on those connections.

Action: Attempt the command again. If the error persists, contact Oracle Support Services.

MIN0200I CID Owner Protocol Address

Cause: This message is used to respond to a Oracle Net 'modify dis' (display) command to show active connections.

Action: No action is required.

MIN0201I %xxxxxxx %ccccccc TCP %cccccccccccccc/%dddd

Cause: This message is used to respond to a Oracle Net 'modify dis' (display) command to show active connections

Action: No action is required.

MIN0203I %ccccccc has %d Sub-tasks active, %d are protocol tasks , GV is at %xxxxxxx.

Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status.

Action: No action is required.

MIN0204I SubTask Protocol @TCB Terminated?

Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status of an OSDI Net service.

Action: No action is required.

MIN0205I %ccccccc %ccc %xxxxxxx %cc

Cause: This message is used to respond to an OSDI 'DISPLAY name,L' command to show status.

Action: No action is required.

MIN0206I Pool SP Size Free Total Reuses

Cause: This message is used to respond to a Oracle Net 'modify dis pool' command to show storage use.

Action: No action is required.

MIN0207I %CCC %dd %dddd %ddddddddd %ddddddddd %ddddddddd

Cause: This message is used to respond to a Oracle Net 'modify dis pool' command to show storage use.

Action: No action is required.

MIN0300E memory unavailable for new %ccc pool element

Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.

Action: Increase the Oracle Net region and restart.

MIN0303E unable to locate CBX for CID %xxxxxxx

Cause: Oracle Net has probably suffered corruption of control structures.

Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.

MIN0304S Internal error, CB and CBX specify different CIDs

Cause: Oracle Net has probably suffered corruption of control structures.

Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.

MIN0305E unable to obtain buffer of size %dddd

Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.

Action: Increase the Oracle Net region an restart.

MIN0306E bind request to subsystem %ccc rejected with RC = %d

Cause: A server to which a remote client is trying to connect is not available.

Action: Check the system log for 'MIS' messages to help determine why. If the reason for failure is not apparent, contact Oracle Support Services with the information for all MIN and MIS messages.

MIN0307E bind to service %ccccccc failed, RC = %d, RSN = %ddd, I NFO = %ddd

Cause: A server to which a remote client is trying to connect is not available.

Action: Check the system log for 'MIS' messages to help determine way. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages.

MIN0308E unbind request to subsystem %ccc rejected with RC = %d

Cause: A server from which a remote client is trying to disconnect is not responding correctly.

Action: Check the system log for 'MIS' messages to help determine way. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages. The protocol side of the connection will be terminated.

MIN0309E unbind to service %ccccccc failed, RC = %d, RSN = %ddd, INFO = %ddd

Cause: A server from which a remote client is trying to disconnect is not responding correctly.

Action: Check the system log for 'MIS' messages to help determine why. If the reason for failure is not apparent, contact Oracle Support Services with the information from all MIN and MIS messages. The protocol side of the connection will be terminated.

MIN0310W WLM enclave create failed RC=%xxxx RSN=%xxxxxxxx protocol %ccc.

Cause: This message may be due to IBM imposed restrictions on the number of enclaves that may be created by a single address space.

Action: Oracle Net will continue, but work will be scheduled into the Oracle server for this connection on a preemptable SRB instead of an enclave SRB and the work will not be managed by WLM.

MIN0311W WLM enclave delete failed RC=%xxxx RSN=%xxxxxxxx protocol %ccc.

Cause: Oracle Net was not able to delete an enclave, probably because a SRB was active when a client tried to force a disconnection.

Action: Processing will continue and the connection will be dropped.

MIN0700I HPNS INITAPI call performed. RC=%ddd, EC=%dddd

Cause: If the RC and EC are anything other than 0, then Oracle Net TCP/IP protocol will not function correctly. The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.

Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error and the error number gives some indication of what that error is.

MIN0701E getclientid failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot initialize correctly and will not function correctly. The RC and EC are return code and error number from an EZASMI TYPE=GETCLIENTID macro call.

Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error. It should be reported to Oracle Support Services for assistance in determining the cause.

MIN0702E getclientid call failed. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot initialize correctly and will not function correctly. The RC and EC are return code and error number from the completion of an EZASMI TYPE=GETCLIENTID macro call.

Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. Generally this message indicates that there is a configuration error. It should be reported to Oracle Support Services for assistance in determining the cause.

MIN0703E gethostid failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot obtain the default home internet address and will terminate. The RC and EC are return code and error number from an EZASMI TYPE=GETHOSTID macro call.

Action: Refer to the IBM manual Communications Server IP and SNA Codes for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0704E gethostid failed invoke. RC=%ddd

Cause: The Oracle Net TCP/IP protocol cannot obtain the default home internet address and will terminate. The RC and EC are return code and error number from the completion of an EZASMI TYPE=GETHOSTID macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0705E gethostbyname attach failed. RC=%ddd

Cause: The Oracle Net TCP/IP protocol cannot attach the gethostbyname task and will terminate. The return code is the return code from an ATTACHX macro call.

Action: This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0706E Attach of HPNS kid task failed. RC=%ddd

Cause: The Oracle Net TCP/IP protocol cannot attach a kid task and will terminate. The return code is the return code from an ATTACHX macro call.

Action: This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0707E listen-socket failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot obtain a socket descriptor from TCPIP and will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SOCKET macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0708E listen-socket call failed. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot obtain a socket descriptor from TCPIP and will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=SOCKET macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0709E bind socket failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot bind to a port in TCPIP and will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=BIND macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0710E bind socket call failed. RC=%ddd, EC=%dddd

Cause: The TCP/IP protocol cannot initialize correctly.

Action: Report this message to Oracle Support Services

MIN0711E listen failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The TCP/IP protocol cannot initialize correctly.

Action: Report this message to Oracle Support Services

MIN0712E listen call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot listen on a port in TCPIP and will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=LISTEN macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0713I I am listening on port %dddd socket %dddd

Cause: This message is normal and indicates that Oracle Net is listening on port nnnn and will accept connection request on this port.

Action: None.

MIN0714E accept failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an accept connection request which failed and Oracle Net will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=ACCEPT macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0715W accept call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an accept connection request which failed to complete. Oracle Net attempts to correct this and will continue as far as it can. If it cannot correct the error then Oracle Net will terminate. The RC and EC are return code and error number from the completion from an EZASMI TYPE=ACCEPT macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network error. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0716E givesocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued a givesocket to hand off a connection to a Oracle Net kid. Oracle Net will continue; however, probably with reduced functionality. The RC and EC are return code and error number from the call to an EZASMI TYPE=GIVESOCKET macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network or a configuration error (for example; not enough sockets defined). This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0717E givesocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an givesocket to hand off a connection to an Oracle Net kid which failed to complete. Oracle Net will continue; however, with reduced functionality. The RC and EC are return code and error number from the completion from an EZASMI TYPE=GIVESOCKET macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is possibly a network or a configuration error (for example; not enough sockets defined). This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0718E close for given failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an close socket to close a connection which failed. Oracle Net will continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=CLOSE macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message can be reported to Oracle Support Services for assistance in determining the cause.

MIN0719W close for given call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an close socket to close a connection which failed to complete. Oracle Net will continue. The RC and EC are return code and error number from the completion from an EZASMI TYPE=CLOSE macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message should be reported to Oracle Support Services for assistance in determining the cause.

MIN0721I HPNS shut down, GoodBye.

Cause: This message is normal and indicates that the Oracle Net TCP/IP protocol has shutdown.

Action: None

MIN0722I HPNS Kid #%dd shut down.

Cause: This message is normal and indicates that one of the kid slaves has shutdown.

Action: None

MIN0723I HPNS Gethostbyname subtask ended.

Cause: This message is normal and indicates that the Oracle Net gethostbyname subtask has shutdown.

Action: None

MIN0724I HPNS GHBY INITAPI call performed. RC=%ddd, EC=%dddd

Cause: If the RC and EC are anything other than 0 then Oracle Net TCP/IP protocol will not function correctly. This subtask performs all the name resolution for IP addresses (DNS). The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance if the return code and error number is anything other than 0.

MIN0725E gethostname failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot obtain the default host name and will terminate. The RC and EC are return code and error number from a call to an EZASMI TYPE=GETHOSTNAME macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause.

MIN0726E gethostname failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol cannot obtain the default host name and will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETHOSTNAME macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause.

MIN0727E gethostbyname call failed. RC=%ddd

Cause: The Oracle Net TCP/IP protocol cannot obtain the resolve the default host name obtained from the gethostname call and thus fails to initialize and will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETHOSTBYNAME macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This message indicates that there is a configuration error. It can be reported to Oracle Support Services for assistance in determining the cause. This may also indicate that IBM Language Environment is not available.

MIN0728I HPNS KID INITAPI call performed. RC=%ddd, EC=%dddd

Cause: If the RC and EC are anything other than 0 then Oracle Net TCP/IP protocol will not function correctly. This subtask performs all the work for IP connections and multiple subtasks (kids) are started. The RC and EC are return code and error number from an EZASMI TYPE=INITAPI macro call.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance if the return code and error number is anything other than 0.

MIN0729E KID getclientid failed invoke. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an getclientid to initialize a Oracle Net kid which failed. Oracle Net will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=GETCLIENTID macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0730E KID getclientid call failed. RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP protocol issued an getclientid to initialize a Oracle Net kid which failed to complete. Oracle Net will terminate. The RC and EC are return code and error number from the completion of the call to an EZASMI TYPE=GETCLIENTID macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0731E takesocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The setup of a TCP/IP connection has failed. The kid is trying to take connection request and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=TAKESOCKET macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0732E takesocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The setup of a TCP/IP connection has failed. The kid is trying to take connection request and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=TAKESOCKET macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0733I Socket %ddd connected Subtask %ccc, IP %cccccccccccccc, Port %dddd.

Cause: This message is a normal TCP/IP connection message for an inbound connection request to a z/OS server from some remove TCP/IP client.

Action: None.

MIN0734E setsocket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The setup of a TCP/IP connection has failed. The kid is trying to set up the connection and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the call to an EZASMI TYPE=SETSOCKOPT macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0735E setsocket call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The setup of a TCP/IP connection has failed. The kid is trying to set up the connection and has failed. Oracle Net will try to continue. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SETSOCKOPT macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0736E receive failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to receive some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=RECV macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.

MIN0737E receive call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to receive some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=RECV macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.

MIN0738E send failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to send some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SEND macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance however, any error is most likely to be due to a network error.

MIN0739E send call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to send some data and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SEND macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.

MIN0740E close failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to close a connection and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CLOSE macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.

MIN0741E close call failed. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: A TCP/IP connection has failed. The kid is trying to close a connection and has failed. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CLOSE macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to a network error.

MIN0742I Socket %ddd closed Subtask %ccc, IP %cccccccccccccc, Port %dddd.

Cause: This message is normal and indicates that a remote TCP/IP connection has closed.

Action: None

MIN0743E socket failed invoke. Sckt=%dddd RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP connection cannot obtain a socket descriptor from TCPIP. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=SOCKET macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0744E socket call failed. Subtask %ccc RC=%ddd, EC=%dddd

Cause: The Oracle Net TCP/IP connection cannot obtain a socket descriptor from TCPIP. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=SOCKET macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0745E connect failed invoke. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CONNECT macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0746E connect call failed. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CONNECT macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0747E getsockname failed invoke. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=GETSOCKNAME macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0748E getsockname call failed. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot establish a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=GETSOCKNAME macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance; however, any error is most likely to be due to either a network or configuration error.

MIN0749I Socket %ddd connected Subtask %ccc, IP %cccccccccccccc, Port %dddd.

Cause: This message is a normal message issued when an outbound z/OS client connects to a remote server through TCP/IP.

Action: None.

MIN0750E cancel recv failed invoke. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CANCEL macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0751E cancel recv call failed. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local client cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion of a call to an EZASMI TYPE=CANCEL macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0752E cancel accept failed invoke. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local socket cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the call to an EZASMI TYPE=CANCEL macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0753E cancel accept call failed. Subtask %ccc Sckt=%ddd, RC=%ddd, EC=%dddd

Cause: The local socket cannot close a connection between a local TCP/IP socket and a remote socket. Oracle Net will try to continue though this connection will terminate. The RC and EC are return code and error number from the completion to a call to an EZASMI TYPE=CANCEL macro.

Action: Refer to the IBM manual Communications Server IP Application Programming Interface Guide in the return codes section (Appendix B) for an explanation of what the error number is from this EZASMI macro call. This should be reported to Oracle Support Services for assistance.

MIN0901S diagnostic dump failed for abend Ssss/Uuuuu, SDUMPX RC = rc, RSN = rs

Cause: The SDUMPX macro has failed to complete for the system ABEND sss or the user ABEND uuuu.

Action: Refer to the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2 for further information about macro SDUMPX, return code rc, reason code rs, and appropriate actions.

MIN0900W diagnostic dump suppressed for abend S%xx/U%ddd

Cause: The dump was suppressed for system ABEND sss or the user ABEND uuuu.

Action: Refer to Chapter 11, "User Abend Codes" for further information.

MIN0901S diagnostic dump failed for abend Ssss/Uuuuu, SDUMPX RC = rc, RSN = rs

Cause: The SDUMPX macro has failed to complete for the system ABEND sss or the user ABEND uuuu.

Action: Refer to the macro SDUMPX in the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 2 for further information about return code rc and reason code rs and appropriate actions.

MIN0902S loop in %ccc freepool element %xxxxxxx, some memory now unusable

Cause: A loop was detected in the free memory chain.

Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.

MIN0903S overlay in %ccc freepool element %xxxxxxx, some memory now unusable

Cause: An overlay was detected in the free memory chain.

Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.

MIN0904S message %dddd not found in message table'

Cause: The message is not in the message table.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0905E internal error in %ccccccc, unrecognized AR type %d received

Cause: The net AR type is not recognized.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0906E internal error in %ccccccc, unrecognized request option %d in AR type %d

Cause: The option for the net AR type is not recognized.

Action: The information displayed in the message should be reported to Oracle Support Services.

MIN0907E internal error in %ccccccc, no matching task block found

Cause: The TB control block cannot be found.

Action: A console dump of the address space should be taken, and Oracle Net restarted as soon as practical.

MIN0908I SRB abend PSW=%xxxxxxxx %xxxxxxxx CODE=%xxxxxxxx REAS=%xxxxxxxx

Cause: The SRB has abended

Action: Refer to the MVS System Codes or the User Abend Codes section of this manual for further information.

MIN1100E request rejected, shutdown in progress

Cause: The Net address space is terminating the request is rejected

Action: Restart the net address space.

MIN1101E unable to obtain %dd bytes of memory for API request

Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.

Action: Increase the Oracle Net region and restart.

MIN1102E unable to obtain %dddd bytes of memory for data buffer

Cause: Oracle Net is short on storage. It will continue to operate, but may be unable to handle new work.

Action: Increase the Oracle Net region and restart.

MIN1103E request rejected, CID is no longer valid

Cause: The connection id cannot be located.

Action: If the problem persists, a console dump of the address space should be taken and the problem reported to Oracle Support Services.

MIN1104E request rejected, unable to locate connection block

Cause: The connection is marked idle.

Action: If the problem persists, a console dump of the address space should be taken and the problem reported to Oracle Support Services.

MIN1105E request rejected, invalid AR type %d

Cause: The net AR type is not recognized.

Action: The information displayed in the message should be reported to Oracle Support Services.

9 Database Region Messages

This chapter documents the messages that are issued by the database instance management component of Oracle Database for z/OS. These messages are generally written to the system console.

The messages begin with the prefix "MIR" followed by a 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:

Table 9-1 Database Region Message Letter Codes

Letter

Definition

E

Error. Action is required

I

Information. Action is not required

W

Warning. Action may be required

D

Debug. Action is not required.

The following messages are described in this chapter:

9.1 Messages MIR0001I to MIR0622I

MIR0001I Starting control region for ssssssss service in subsystem ssss

Cause: Region initialization for the first address space of the indicated service is beginning. This is normally the first message issued by the database service after it is started.

Action: No action is required.

MIR0002I ssssssss service address space ready

Cause: Region initialization for the indicated database service address space has completed successfully. Connection to the service to perform an Oracle startup is now possible.

Action: No action is required.

MIR0003I Quiescing ssssssss service address spaces

Cause: A z/OS or OSDI STOP (P) command has been issued to the indicated database service, and termination of its address space (or spaces) and tasks is beginning.

Action: No action is required.

MIR0004I ssssssss service terminated

Cause: Termination processing for the indicated service has completed. All address spaces of the service should end execution shortly after this message is received.

Action: No action is required.

MIR0005E ssssssss service failed to signon to ssss subsystem

Cause: During database service initialization, an attempt to register the service as "active" in the subsystem failed. The service address space terminates. This message should be accompanied by one or more subsystem (MIS) messages describing the error.

Action: This message and the accompanying MIS messages should be reported to Oracle Support Services.

MIR0006E nnnn macro error. Comp code = cccc; reason code rrrr

Cause: During database service initialization, one of the macros that was issued to set up cross-memory access has failed. The service address space terminates.

Action: This message and the included macro name and error codes should be reported to Oracle Support Services.

MIR0007E Environment check failed: reason

Cause: Database service address space initialization cannot proceed due to one of the following environmental conditions [reason]:
Reason: APF-authorization: The database service program is not executing APF-authorized.

Action: Ensure that ORARASC is being fetched from an APF-authorized library and that no non-authorized libraries are concatenated in the service JCL STEPLIB DD statement.
Reason: Protection key 7: The database service program is not running in protection key 7.

Action: Ensure that ORARASC has been added to the z/OS Program Properties Table (PPT) with an entry that specifies KEY(7), and ensure that the PPT has been refreshed or that the system has been IPLed.
Reason: Non-swappable: The database service address space is not marked non-swappable.

Action: Ensure that ORARASC has been added to the z/OS Program Properties Table (PPT) with an entry that specifies NOSWAP, and ensure that the PPT has been refreshed or that the system has been IPLed.

Action: The database service address space is terminated. Correct the indicated condition and restart the service.

MIR0009I Starting system subtasks

Cause: Database service initialization has reached the point at which internal service tasks are attached. This is a normal progress message during service address space initialization.

Action: No action is required.

MIR0010I Stopping system subtasks

Cause: Database service termination has reached the point at which internal service tasks are detached. This is a normal progress message during service STOP (P) processing.

Action: No action is required.

MIR0011I Stop command received

Cause: The database service acknowledges receiving a z/OS or OSDI STOP (or P) command.

Action: No action is required.

MIR0012I Starting auxiliary region nnn for ssssssss in subsystem ssss

Cause: During database service initialization, the region INIT_ADR_SPACES parameter specified a number greater than one. The first server address space has therefore starting an auxiliary address space. One message of this type is issued from each auxiliary address space that is started.

Action: No action is required.

MIR0013E Failed to allocate parameter data set dsname

Cause: During database service initialization, the region parameters data set (supplied through the service PARM string on DEFINE or ALTER SERVICE) could not be dynamically allocated. Service initialization fails, and the address space terminates. The usual cause of this is a misspelled data set name in the service PARM.

Action: This can be corrected with an OSDI ALTER command.

MIR0014E Failed to open parameter data set dsname

Cause: During database service initialization, the region parameters data set (supplied through the service PARM string on DEFINE or ALTER SERVICE) could not be opened. Service initialization fails, and the address space terminates.

Action: This message is normally accompanied by messages from open/close/EOV (IECxxx messages) indicating the nature of the error. Refer to the appropriate message.

MIR0016W Syntax error in option; ignored

Cause: During service initialization, an invalid or unknown parameter was specified in the server region parameter file.

Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0017W Invalid option value; option ignored

Cause: During service initialization, an unacceptable parameter value was specified in the server region parameter file.

Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0018W Unrecognized option; ignored

Cause: During service initialization, an invalid or unknown parameter was specified in the server region parameter file.

Action: The parameter is ignored, and service initialization continues. The parameter file should be examined and corrected.

MIR0020W I/O error reading option file

Cause: During service initialization, an I/O error occurred while reading the server region parameter file.

Action: Region parameter processing stops, and service initialization continues. The parameter file should be examined and corrected.

MIR0021E Unable to load nnnnnnnn - cccc-rr

Cause: During service initialization, a required module could not be loaded. The module name and the LOAD macro completion and return codes are given in the message. Service initialization fails, and the service address space terminates.

Action: Two likely causes of this error are a misspelled Oracle kernel module name in the region initialization parameters or a missing data set in the region JCL STEPLIB concatenation. If the module name begins with "CEE", then it is an IBM LE/370 module. Ensure that you have included the LE/370 runtime library in STEPLIB.

MIR0022E Fatal error - terminating

Cause: An error has caused database service address space initialization to fail. The error is described in earlier MIR messages. The service address space terminates.

Action: Correct the error(s) indicated in prior message(s) and then restart the service.

MIR0023I Starting nnn auxiliary address spaces

Cause: During database service initialization, the region INIT_ADR_SPACES parameter specified a number greater than one.

Action: The first server address space is therefore starting auxiliary address spaces.

MIR0024I Terminating all auxiliary address spaces

Cause: During database service STOP (P) processing, the auxiliary address spaces that have been started are about to be terminated.

Action: This is a normal progress message during service termination.

MIR0025W Unable to open file management input file - SMS assumed

Cause: During database region initialization processing of the file management parameters, the ORA$FPS file could not be opened. The usual cause of this is that the DD is not included in the region JCL. Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations.

Action: No action is required.

MIR0027E Unable to retrieve OSDI command

Cause: An OSDI subsystem command that was forwarded to the database service could not be retrieved.

Action: This error should be reported to Oracle Support Services.

MIR0029E nnnnn lines not displayed

Cause: A DISPLAY command that was issued through the z/OS MODIFY (F) interface produced more lines of output than would fit in the response buffer.

Action: Reissue the command with finer criteria to get a complete display.

MIR0030E Fatal error - terminating

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a severe error has halted processing of the parameters.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Report this error to Oracle Support Services.

MIR0036W dump_title - SDUMPX RC=return_code, RSN=reason_code

Cause: The service attempted to perform an SVC dump, but was unsuccessful. The return code and reason code from the SDUMPX macro are displayed in hexadecimal. This message commonly appears if dumps are suppressed by DAE, SLIP or other system configuration options.

Action: If the dump was suppressed by DAE, a previous dump should exist. If the previous dump was lost, it may be necessary to disable DAE or to modify it so the suppressed dump can be generated. Consult your system programmer for assistance. Refer to the IBM manual MVS Authorized Assembler Services Reference, LLA-SDU for further information about macro SDUMPX.

MIR0075E FT2 dddddddd unallocation error eeeeeeee

Cause: During close/free processing for a non VSAM file (such as a trace or parameter file), a dynamic unallocation request received an unexpected error.

Action: This message and the accompanying error code should be reported to Oracle Support Services.

MIR0110W Service ssssssss UNIX services unavailable

Cause: During database service initialization, an attempt to dub the service address space as a z/OS UNIX System Services process has failed. Service initialization continues, and the database can be started up as usual. However, database functions that interact with z/OS UNIX System Services will not be available.

Action: Usually this message results from not having a default OE segment defined for the z/OS user ID associated with the service address space.

MIR0111W Service ssssssss gethostbyname service unavilable

Cause: During database service initialization, an attempt to initialize the sockets macro interface has failed.

Action: Service initialization continues, and the database can be started up as usual. However, database functions that depend on z/OS UNIX System Services sockets will not be available.

MIR0112E Service ssssssss UNIX resource cleanup failed, Session=sess, func=fn, resource=resid, errno=e, reason=r

Cause: During resource cleanup processing for a terminating database session, an attempt to release a z/OS UNIX System Services resource allocated by the session has failed.

Action: The service continues execution normally. This message should be reported to Oracle Support Services.

MIR0113E Service ssssssss async request (xxxxxxxx) post error

Cause: Internal error.

Action: Service continues execution normally, but some sessions may hang. This message should be reported to Oracle Support Services.

MIR0130I FPS refresh completed successfully

Cause: The FPS refresh completed successfully.

Action: None required.

MIR0131W FPS syntax error; record nnnnnn

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a syntax error (such as missing punctuation) was encountered.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Correct the syntax error. For more information about file management parameter syntax, refer to the Oracle Database System Administration Guide for IBM z/OS on System z.

MIR0132W FPS value error; keyword: text; record nnnnnn

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), the value that was specified for a file management parameter keyword was not valid.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Specify a valid value for the keyword. For more information, refer to the list of file management parameter keywords in the Oracle Database System Administration Guide for IBM z/OS on System z.

MIR0133W FPS invalid GROUP: group; record nnnnnn

Cause: The group name specified in the FILE_GROUP parameter is not a valid group.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Choose a valid group name. For more information, refer to the list of valid file management parameter file group names in Oracle Database System Administration Guide for IBM z/OS on System z.

FPS unknown keyword: text; record nnnnnn

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), an invalid or misspelled keyword was encountered.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. Specify a valid keyword. For more information, refer to the list of file management parameter keywords in Oracle Database System Administration Guide for IBM z/OS on System z.

MIR0135W FPS I/O error reading file

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), an I/O error occurred on a request to read the parameter file. The file is closed, and no further parameters are processed.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. This message should be reported to Oracle Support Services.

MIR0136E Unable to open ORA$FPS DD, refresh cancelled

Cause: During execution of the REFRESH FPS command, the ORA$FPS file could not be opened. The usual cause of this is that the DD is not included in the region JCL.

Action: The refresh operation is terminated and the previous configuration, if any, remains in place. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Verify that the ORA$FPS DD is included in the region JCL. If it is and the problem persists, report this error to Oracle Support Services.

MIR0137E Errors encountered reading FPS input, refresh cancelled

Cause: During execution of the REFRESH FPS command, one or more errors prevented completion of FPS processing.

Action: The refresh operation is terminated, and the previous configuration, if any, remains in place. Correct the problem with ORA$FPS and rerun the REFRESH FPS command. If the problem persists, report this error to Oracle Support Services.

MIR0138W No FPS input found, refresh cancelled

Cause: During execution of the REFRESH FPS command, the ORA$FPS was found to have no definitions.

Action: The refresh operation is terminated and the previous configuration, if any, remains in place. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Add FPS definitions and rerun the REFRESH FPS command. If the problem persists, report this error to Oracle Support Services.

MIR0139E FPS fatal error, terminating

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), a severe error has halted processing of the parameters.

Action: Server initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Report this error to Oracle Support Services.

MIR0140E FPS fatal error, insufficient memory

Cause: FPS was unable to obtain storage for the FPS definitions.

Action: FPS processing is terminated. Ensure adequate storage is available for the FPS definitions.

MIR0141E FPS fatal error, file inconsistency

Cause: New errors appeared during the second pass over the ORA$FPS data set.

Action: FPS processing is terminated. File processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. File creation in the server will not succeed without ORA$FPS parameters unless your installation's ACS routines provide defaults for new VSAM LDS allocations. Report this error to Oracle Support Services.

MIR0142E FPS fatal error, ABEND Snnn-rrrrrrrr, during oooo

Cause: The processing of the ORA$FPS DD has resulted in a z/OS ABEND. The variable nnn is the system ABEND code (hex) and rrrrrrrr is the associated reason code (hex). The ABEND occurred while performing operation oooo - the name of a system service or macro. This error can be preceded by system messages with IEC prefixes. These IEC messages will have additional detail about the problem.

Action: FPS processing is terminated. If the error occurred during server initialization, initialization continues, but file processing in the server (especially file creation) may not behave as expected due to parameters that were not processed. If the error occurred during a REFRESH FPS command, then the refresh operation is terminated and the previous configuration, if any, remains in place. Using the ABEND code, reason code, and z/OS system-issued messages, correct the condition that resulted in the ABEND. If the problem persists, report this error to Oracle Support Services. If an SVC dump is generated, save it for problem diagnosis.

MIR0380E Failed to load ORADIE module

Cause: During database service initialization, a LOAD macro (for the timer-disabled interrupt exit) failed. Service initialization fails, and the service terminates. This message will usually be accompanied by one or more CSVxxx messages from Contents Management indicating the nature of the error.

Action: Ensure that ORADIE is in one of the server region STEPLIB data sets and that sufficient ECSA memory is available to load it. If sufficient ECSA memory is available, then report this message to Oracle Support Services.

MIR0381E Failed to obtain SQA for timer structure

Cause: During database service initialization, approximately 500 bytes of ESQA memory could not be obtained for a time interval control structure. Service initialization fails, and the service terminates.

Action: If your system does not have 500 bytes of available ESQA, you can expect other problems to be reported. If problems other than Oracle database server problems are not reported, then report this error to Oracle Support Services.

MIR0382E Initial timer request enqueue failed

Cause: During database service initialization, an attempt to enqueue a timer request (TQE) failed.

Action: Service initialization fails, and the service terminates. This error should be reported to Oracle Support Services.

MIR0400I Oracle for OS/390 External Data Mover ready

Cause: EDM startup has completed. This is normally the first message issued by the EDM after it has successfully started.

Action: No action is required.

The EDM will write high-level debug messages to the log file (SYSPRINT DD).MIR0401E ESTAEX macro failed: R15=r15,R0=r0

Cause: During EDM startup, a macro that was issued to set up a recovery environment has failed. The EDM address space terminates.

Action: This message and the register values should be reported to Oracle Support Services.

MIR0402E Environment check failed: APF-authorization

Cause: During startup, the EDM detected that it was not executing APF-authorized. The EDM address space terminates.

Action: Ensure that ORAEDM is being fetched from an APF-authorized library and that no non-authorized libraries are concatenated in the EDM JCL STEPLIB DD statement.

MIR0403E ASTX macro failed: R15=r15,R0=r0

Cause: During EDM startup, a macro that was issued to retrieve startup parameters has failed. The EDM address space terminates.

Action: This message and the register values should be reported to Oracle Support Services.

MIR0404E ASPARM length invalid: actual=x, expected=y

Cause: During EDM startup, the startup parameters length was not as expected. The EDM address space terminates.

Action: This message and the error values should be reported to Oracle Support Services.

MIR0405E Client post failed: R15=r15,R0=r0,R1=r1

Cause: An attempt by the EDM to post function completion information back to the client has failed. This could happen if the client unexpectedly terminates, as well as for other reasons. The EDM address space terminates.

Action: If the client did not unexpectedly terminate, this message and the register values should be reported to Oracle Support Services.

MIR0406D Debug mode enabled

Cause: The EDM will write high-level debug messages to the log file (SYSPRINT DD).

Action: None required.

MIR0407D Ultra debug mode enabled

Cause: The EDM will write high-level and low-level debug messages to the log file (SYSPRINT DD).

Action: None required.

MIR0408E Unable to initialize File Management Parameters handler

Cause: During startup, the EDM was unable to initialize File Management Parameters processing. The EDM address space terminates.

Action: This message should be reported to Oracle Support Services.

MIR0409E Unsupported request received; function code=fc

Cause: The EDM received a request containing an unexpected function code. This could happen if the EDM program is down-level. The request is failed.

Action: If the EDM program is not down-level, this message and the function code should be reported to Oracle Support Services.

MIR04010E SYNAD entered; message text . : text

Cause: An attempt by the EDM to write a message to the log file (SYSPRINT DD) resulted in an I/O error. The text value is the error information passed to the SYNAD exit. The EDM suspends logging.

Action: Interpret text to diagnose and correct the error. If the error persists, contact Oracle Support Services.

MIR0500I Command processed

Cause: A command that was issued using the z/OS MODIFY (F) interface has been processed.

Action: No action is required.

MIR0501E Command not processed

Cause: A command that was issued using the z/OS MODIFY (F) interface could not be processed.

Action: This message should be preceded by other messages indicating the specific error.

MIR0502I No matching sessions found

Cause: A DISPLAY SESSION command that was issued through the z/OS MODIFY (F) interface could not find any server sessions matching the criteria specified in the command.

Action: No action is required.

MIR0503I Server session display

Cause: Information is displayed in response to the server DISPLAY SESSION command when it finds one or more sessions matching the criteria, as described below:

- Session ID – OSDI session identifier in hexadecimal.

- AS# – Server address space number to which the session is assigned.

- Jobname – Jobname for the address space that bound the session, or internal identifier for Oracle background processes

- TCB-Addr – z/OS TCB address currently associated with the session (may be blank)

- UserID – Oracle user ID for the session, if one is known

Action: None required.

MIR0504W Results may be inaccurate; enter command again

Cause: A DISPLAY SESSION command that was issued through the z/OS MODIFY (F) interface encountered a change in server session state structures while the structures were being examined.

Action: The result of the command may not be complete. The command should be reissued to get a current display.

MIR0505W Results have been truncated

Cause: A DISPLAY SESSION command that was issued through the z/OS MODIFY (F) interface produced more lines of output than would fit in the response buffer.

Action: Reissue the command with finer criteria to get a complete display.

MIR0506E Error encountered during command processing

Cause: An error occurred during processing of an IEATDUMP request for a DUMP SESSION command that was issued through the z/OS MODIFY (F) interface.

Action: Report this problem to Oracle Support Services.

MIR0507I Session not found

Cause: The session that was specified in a DUMP SESSION command that was issued through the z/OS MODIFY (F) interface could not be found.

Action: Either the session process ID was entered incorrectly, or the session has ended in the server.

MIR0611I Service ssssssss alert log closed

Cause: The instance alert log for the indicated service has been closed due to an error condition. An attempt will be made to allocate and open a SYSOUT data set for the alert log.

Action: If that attempt fails, then the alert log will be written to the system log.

MIR0612I Alert log for service ssssssss allocated to dddddddd

Cause: The instance alert log for the indicated service has been dynamically allocated as a SYSOUT data set to the DD name shown.

Action: This message is normally received during service startup when no SYSPRINT DD statement is supplied in the service procedure.

MIR0613E Service ssssssss alert log I/O error: synad-message

Cause: An I/O error occurred when the indicated service wrote to the alert log. The error description is in the form of message text that is generated by a SYNADAF macro.

Action: The alert log is closed, and an attempt is made to dynamically allocate a SYSOUT data set for the log. This message is usually followed, therefore, by messages MIR0611I and MIR0612I.

MIR0614E Service ssssssss alert log open failed, reason code n

Cause: An attempt to create a new alert log failed. The cause of the failure is indicated by the following reason codes:

1 – Data set or spool allocation failed

2 – OPEN failed

3 – Storage for BSAM buffers not available

4 – Storage for internal structures not available

With reason codes 1 and 2, additional messages will have appeared in the system log immediately before this message. For reason code 1, look for message MIR0619E containing the return and reason codes from a z/OS DYNALLOC request. For reason code 2, look for z/OS OPEN messages beginning with IEC, in your IBM message documentation.

Action: Some instances of reason code 1 or 2 can be corrected by changing things in the environment (such as available disk space) or by changing and refreshing ORA$FPS parameters in the DBAT group, which influence alert log dynamic allocation. Reason codes 3 and 4 are unlikely unless memory is nearly exhausted in the service address space, in which case this error is the least of your worries. If the error does not seem to be due to an environment or ORA$FPS problem, report this error to Oracle Support Services.

MIR0615W Service ssssssss alert log default SYSOUT=* assumed

Cause: No non-default alert log specification was provided, or an attempt to use a non-default alert log specification (from the ALERT_DSNAME region parameter) has failed, so an attempt will be made to allocate a default alert log.

Action: Normal operation continues with the default alert log or, if that fails, using the z/OS system log for alert messages. If you can correct the cause of the original failure (for example, by increasing available disk space or by changing and refreshing ORA$FPS), issue a LOGSWITCH database service command to cause the corrected alert log to be retried.

MIR0616E Service ssssssss ALERT_DSNAME syntax or content error

Cause: During service initialization or during processing of a LOGSWITCH command, the value specified for the ALERT_DSNAME parameter was not a usable filespec.

Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0617E Service ssssssss ALERT_DSNAME symbol substitution error (nnn)

Cause: During service initialization, an attempt to resolve system symbols in a data set filespec supplied for ALERT_DSNAME failed. The nnn value is the return code from the z/OS ASASYMBM service in decimal. These are described in the IBM manual Assembler Services Reference, under "ASASYMBM".

Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0618I DSN=dsn

Cause: This message accompanies message MIR0612I when the alert log is allocated as a disk data set. It provides the data set name used for the new log after symbol substitutions have been done.

Action: None required.

MIR0619E Service ssssssss alert log dynalloc error, RC=nnn, Reason=xrrrr, Info=xiiii

Cause: During service initialization or during processing of a LOGSWITCH command, dynamic allocation of a new alert log failed. The nnn is the return code from DYNALLOC in decimal and rrrr and iiii are the reason and information codes, respectively, in hexadecimal. These are described in the IBM manual MVS Programming: Authorized Assembler Services Reference, Vol. 1.

Action: Processing continues with a default (SYSOUT=*) alert log. If the dynamic allocation error results from an external cause such as lack of disk space, correct the problem as necessary. If it is caused by an error in the ORA$FPS parameters used for the alert log, correct the ORA$FPS data and refresh it using the REFRESH FPS database service command. In these cases you can issue a LOGSWITCH command to cause a new attempt at alert log allocation. If the problem is caused by the value in ALERT_DSNAME, such as a syntax error, you must stop and restart the service to effect a correction.

MIR0620E Service SSSSSSSS alert log dsname symbol error, RC=nnn

Cause: During LOGSWITCH command processing, an attempt to resolve system symbols in a data set filespec supplied for ALERT_DSNAME failed. The nnn value is the return code from the z/OS ASASYMBM in decimal. These are described in the IBM manual Assembler Services Reference, under "ASASYMBM".

Action: Processing continues with a default (SYSOUT=*) alert log. Correct the problem with the ALERT_DSNAME value and stop and restart the service to use a non-default alert log.

MIR0621I Alert log switch for service ssssssss ignored, not over ALERT_MIN

Cause: A LOGSWITCH command was issued without the FORCE option, but the accumulated size of the current alert log is less than the value specified for the ALERT_MIN region parameter.

Action: The LOGSWITCH command is ignored and processing continues with the current alert log. If you want to force the log switch without regard for ALERT_MIN, reissue LOGSWITCH with the FORCE option.

MIR0622I Service ssssssss alert log switching due to ALERT_MAX

Cause: The alert log has reached the threshold size specified by the ALERT_MAX region parameter, causing an automatic alert log switch.

Action: The current alert log is closed and deallocated and a new one allocated and opened. Processing continues normally with the new alert log.

MIR0623I alert log text

Cause: Information from the alert log. These messages are only issued when the ALERT_ROUTCDE parameter is specified.

Action: None required, but may be useful for automated operations products.

10 Oracle Subsystem Messages

This chapter documents the messages that are issued by the Oracle subsystem component. These messages are generally written to the system console.

These messages begin with the prefix "MIS" followed by a 4-digit decimal number followed by a letter to identify the action and severity associated with each message. The final letter indicates one of the following:

Table 10-1 Oracle Subsystem Messages Letter Codes

Letter

Definition

E

Error. Action is required.

I

Information. Action is not required.

W

Warning. Action may be required.

The following messages are described in this chapter:

10.1 Messages MIS0001E to MIS0454E

MIS0001E Failed to allocate parameter data set

Cause: The subsystem initialization program (ORASSINI) was unable to allocate the parameter data set.

Action: Check the system log for more details.

MIS0002E Failed to open parameter data set

Cause: The subsystem initialization program (ORASSINI) was unable to open the parameter data set.

Action: Check the system log for more details.

MIS0003E Failed to load subsystem code: loadmod - rc-rsn

Cause: The subsystem initialization program (ORASSINI) was unable to load the subsystem code (ORASSI) into common storage.

Action: The subsystem code load module must be in a LNKLST library.

MIS0004E Syntax error in or missing INITialize statement

Cause: An error exists in the boot-strap record.

Action: Correct the record and retry.

MIS0005E I/O error reading initialization file

Cause: An error occurred while reading the file.

Action: Check the system log and the error log to determine the cause of the error.

MIS0006E Unexpected EOF in initialization file

Cause: The subsystem initialization program reached the end of the initialization parameter file when it was expecting additional data. This usually means that the last record in the file indicated continuation.

Action: Correct the file and rerun.

MIS0010E LXRES failure. Reason Code - rsncd

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0011E Error creating/modifying SSVT - RC rc, RSNCD rsncd

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0012E Error activating subsystem - RC rc, RSNCD rsncd

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0013W Unknown RACF class for classname class - using default

Cause: The CLASS that is specified in the subsystem bootstrap record is unknown to the security system.

Action: The default class (FACILITY) is used instead.

MIS0014W Trace Initialization Failed: RC=rc, RS=rsncd, INFO=info

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0015E Failed to allocate storage in subpool subpool, RC = rc

Cause: The subsystem was unable to allocate storage in CSA/ECSA subpool subpool.

Action: You might need to increase the size of the CSA.

MIS0016E Subsystem command prefix conflict - prefix

Cause: The command prefix that is specified in the subsystem bootstrap record is already in use.

Action: Choose a command prefix that is not in use by any other subsystem.

MIS0017E Invalid character in command prefix - prefix

Cause: The command prefix that is specified in the subsystem bootstrap record contains characters that are not valid for command prefixes.

Action: Choose a command prefix containing only characters from the set allowed by z/OS.

MIS0018E System error in CPF macro

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0019E Unable to allocate a system LX

Cause: A system linkage index (LX) was not available for the subsystem to use.

Action: You might need to increase the number of system LXes.

MIS0020I Initialization of Oracle subsystem subsys complete

Cause: Subsystem was successfully initialized.

Action: No action is required.

MIS0080W Oracle AS init skipped--reason code 0

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0081E Oracle AS init subsystem request returned nnn

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0082E Oracle AS init signon RC=rc, reason=rsncd, info=infocd

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0100E Command parser failed to allocate nnnnnnn bytes

Cause: A STORAGE OBTAIN for subpool 229 failed.

Action: If this persists, contact Oracle Support Services for instructions

MIS0101E Data beginning "ssssss" too long for parser

Cause: A command token was too long for an internal buffer.

Action: Correct the command and resubmit. This error cannot occur with any valid command parameters or data.

MIS0102E Scan halted by illegal character X'nn'

Cause: The command contains a character that is not in the allowed character set.

Action: Reissue the command without the offending character.

MIS0103E Quoted string not terminated

Cause: A quoted string was not terminated.

Action: Correct error and resubmit command.

MIS0104E Invalid number data

Cause: An invalid number was included in a date.

Action: Correct error and resubmit command.

MIS0105E Number out of allowed range

Cause: A number that was out of the allowed range was entered.

Action: Check command description for valid values.

MIS0106E Invalid character data

Cause: An invalid character was entered.

Action: Correct the data and resubmit.

MIS0107E Too few or too many values for parameter

Cause: An entry for a parameter contains too few or too many values.

Action: Correct the command and resubmit.

MIS0108E Command terminated prematurely

Cause: A command was terminated prematurely.

Action: Correct the command and resubmit.

MIS0109E Command syntax error

Cause: A command contains invalid syntax.

Action: Correct the command and resubmit.

MIS0110E Unknown command verb: verb

Cause: The command verb: verb is unknown.

Action: Correct the command and resubmit.

MIS0111E Unable to allocate required virtual memory

Cause: A STORAGE OBTAIN for subpool 229 failed.

Action: If this persists, contact Oracle Support Services for instructions.

MIS0112E Unknown or invalid command modifier

Cause: The command contains an unknown or invalid modifier.

Action: Correct the command and resubmit.

MIS0113E Syntax error in positional parameter

Cause: The positional parameter contains a syntax error.

Action: Correct the command and resubmit.

MIS0114E Data error in positional parameter

Cause: The positional parameter contains a data error.

Action: Correct the command and resubmit.

MIS0115E Unexpected data in command

Cause: The command contains unexpected data.

Action: Correct the command and resubmit.

MIS0116E Unknown parameter keyword:

Cause: The parameter contains a keyword that is unknown in this context.

Action: Correct the command and resubmit.

MIS0117E Improperly terminated parameter: parameter

Cause: The parameter: parameter was improperly terminated.

Action: Correct the command and resubmit.

MIS0118E Syntax error in parameter: parameter

Cause: The parameter: parameter contains a syntax error.

Action: Correct the command and resubmit.

MIS0119E Data error in parameter: parameter

Cause: The parameter: parameter contains a data error.

Action: Correct the command and resubmit.

MIS0120E Parameter specified multiple times:

Cause: A parameter was specified multiple times.

Action: Correct the command and resubmit.

MIS0121E Character value too short for parameter

Cause: A character value is too short for the parameter.

Action: Correct the command and resubmit.

MIS0122E Character value too long for parameter

Cause: A character value is too long for the parameter.

Action: Correct the command and resubmit.

MIS0152E An invalid structure was passed to the function processor

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0153E An invalid parameter ID (000) was specified in the function request

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0154E Error encountered processing request parameter:

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0155E A required request parameter was omitted:

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0156E An error occurred setting a default for:

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0157E Service group for subsystem subsys already defined

Cause: A DEFINE SERVICEGROUP was already successfully processed for the subsystem.

Action: None. The command is ignored.

MIS0158E Service group ECSA allocation failed for subsysystem subsys

Cause: The subsystem was unable to allocate storage in CSA/ECSA subpool 231.

Action: You might need to increase the size of the CSA.

MIS0159E Service group for subsystem subsys has not been defined

Cause: An ALTER SERVICEGROUP was attempted before the service group was defined.

Action: Define the service group.

MIS0160E Invalid MISSVG structure detected for subsystem subsys

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0161E Service definition prohibited before service group definition for subsystem subsys

Cause: A DEFINE SERVICE command was encountered before a DEFINE SERVICEGROUP.

Action: Define a service group and try again.

MIS0162E Service name parameter missing in request to subsystem subsys

Cause: The request to subsystem subsys is missing a service name parameter.

Action: Correct the command and resubmit.

MIS0163E Invalid service name parameter in request to subsystem subsys

Cause: The request to subsystem subsys contains an invalid service name parameter.

Action: Correct the command and resubmit.

MIS0164E Service service_name already defined in subsystem subsys

Cause: A DEFINE SERVICE is defining a service that is already defined.

Action: Make sure that you spelled the service name correctly. Issue a SHOW SERVICE command to display an existing service definition.

MIS0165E Invalid structure for service service_name in subsystem subsys

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0166E Service service_name is not defined in subsystem subsys

Cause: The service is not defined.

Action: Make sure that you spelled the service name correctly. Issue a SHOW SERVICEGROUP LONG command to list all of the services defined in the service group.

MIS0167E Service service_name ECSA allocation failed in subsystem subsys

Cause: The subsystem was unable to allocate storage in CSA/ECSA subpool 231.

Action: You might need to increase the size of the CSA.

MIS0168E Conflicting define/alter service group for subsystem subsys

Cause: The command submitted to subsystem subsys contains conflicting define/alter service group data.

Action: Correct the command and resubmit.

MIS0169E Conflicting define/alter service service_name for subsystem subsys

Cause: The command submitted to subsystem subsys contains conflicting define/alter service service_name data.

Action: Correct the command and resubmit.

MIS0170E Invalid length or structure for parameter:

Cause: The parameter has invalid length or invalid structure.

Action: Correct the command and resubmit.

MIS0171E Parameter too long after symbol substitution:

Cause: After symbol substitution, the parameter is too long.

Action: Correct the command and resubmit.

MIS0172E Symbol substitution error (ASASYMBM return code rc) in parameter:

Cause: Symbol substitution failed with return code rc.

Action: This is probably an internal error. Contact Oracle Support Services.

MIS0173E Illegal value specified for parameter:

Cause: An illegal value was specified for a parameter.

Action: Correct the command and resubmit.

MIS0174E Invalid mode parameter

Cause: An invalid mode parameter has been used.

Action: Correct the command and resubmit.

MIS0175E Invalid system list parameter

Cause: An invalid system list parameter has been used.

Action: Correct the command and resubmit.

MIS0176E System list contains illegal or inconsistent values

Cause: Illegal or inconsistent values are contained in the system list.

Action: Correct the command and resubmit.

MIS0177E Invalid option parameter:

Cause: The option parameter is invalid.

Action: Correct the command and resubmit.

MIS0178E Invalid service type parameter

Cause: The service type parameter is invalid.

Action: Correct the command and resubmit.

MIS0179E Unknown service type type

Cause: Service type type is unknown.

Action: Correct the command and resubmit.

MIS0180E An invalid service type structure was loaded for type type

Cause: The type definition load module does not contain a valid type structure. This is probably an installation problem.

Action: Contact Oracle Support Services.

MIS0181E Duplicate parameter specified:

Cause: A duplicate parameter was specified.

Action: Correct the command and resubmit.

MIS0182E Input SSID does not match subsystem name subsys

Cause: The SSID value in a DEFINE SERVICEGROUP command does not match the subsystem name.

Action: If specified, the SSID must match the subsystem name. Correct the command by changing the SSID value or by omitting the SID parameter.

MIS0183E Service service_name can't start, currently service_state

Cause: The named service cannot be started because it is not in the ACTIVE or INACTIVE state.

Action: If the service is in one of the transient states (STARTING or STOPPING), wait until the start or stop operation is completed, and then reissue the START command. If the service is drained, you must resume it before you can issue a START.

MIS0184E Service service_name start error, ASCRE RC=rc, RS=rsn

Cause: The ASCRE macro that was used to start a service address space failed.

Action: This may be due to environmental problems (not enough storage or maximum address spaces already running) or to an internal error. Check with your system programmer or contact Oracle Support Services.

MIS0185E Service service_name can't start, at maximum address spaces

Cause: The service cannot be started without exceeding the maximum number of address spaces.

Action: If more service address spaces are needed, then increase the MAXAS value for the service.

MIS0186E Unable to allocate address space table for service

Cause: The subsystem was unable to allocate storage in CSA/ECSA subpool 231.

Action: You might need to increase the size of the CSA.

MIS0187E Maximum address space value nnnn illegal for service type

Cause: The MAXAS value nnnn exceeds that allowed for the service type. This is probably a user or an installation error.

Action: For a NET service, MAXAS must be 1 (default). For an ORA service, the MAXAS can be 1 through 8.

MIS0188E Service service_name can't start, internal structure damaged

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0189E Service service_name can't stop, currently service_state

Cause: The named service cannot be stopped because it is not in the ACTIVE or STOPPING state.

Action: If the service is in the STARTING state, then you must wait for it to reach the ACTIVE state before you can issue a stop command.

MIS0190E Service service_name unable to schedule stop notification

Cause: The service address space could not be contacted. This might be due to a transient condition.

Action: Try to use the MVS STOP (P) system command to stop the service. If the problem persists, call Oracle Support Services.

MIS0191I Service service_name forced stop requested

Cause: This is the normal response to the OSDI STOP FORCE command

Action: No action is required.

MIS0192I Service service_name stopping

Cause: This is the normal response to the OSDI STOP command.

Action: No action is required.

MIS0193I Service service_name starting

Cause: This is the normal response to the OSDI START command.

Action: No action is required.

MIS0194I Service service_name Type service_type (service_description) SID=service_identifier MaxAS=max_address_spaces Proc=procedure_name Jobname=job_nameJobAcct=accounting_informationJCLParm=JCL_override_parametersParm=service_parameters

Cause: This is the normal response to the OSDI SHOW SERVICE command.

Action: No action is required.

MIS0195I Service group servicegroup Mode=mode, Systems=

Cause: This is the normal response to the OSDI SHOW SERVICEGROUP command.

Action: No action is required.

MIS0196I Service group servicegroup defined

Cause: This is the normal response to the OSDI DEFINE SERVICEGROUP command.

Action: No action is required.

MIS0197I Service group servicegroup altered

Cause: This is the normal response to the OSDI ALTER SERVICEGROUP command.

Action: No action is required.

MIS0198I Service service_name defined

Cause: This is the normal response to the OSDI DEFINE SERVICE command.

Action: No action is required.

MIS0199I Service service_name altered

Cause: This is the normal response to the OSDI ALTER SERVICE command.

Action: No action is required.

MIS0200I Address space for service servicename terminated

Cause: This message is issued when a service address space terminates abnormally.

Action: No action is required.

MIS0201E Invalid service bind/unbind parameter

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0202E Invalid bind option or target class

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0203E Invalid or corrupted bind structure

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0204E Requested service not found

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0205E Bind request failed authorization check

Cause: The bind failed because the address space was not authorized to bind to the service.

Action: Check the security package configuration.

MIS0206E Bind request not in task mode

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0207E Unable to allocate private storage for bind

Cause: Unable to allocate storage in subpool 229 in the caller's address space.

Action: Increase the region size and rerun the job.

MIS0208E Requested service unavailable

Cause: The service is not active.

Action: Start the service and retry the operation.

MIS0209E Service structure corrupted

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0210E Connect to service failed

Cause: The service rejected the bind request. This normally should not occur.

Action: Shutdown and restart the service. Contact Oracle Support Services for instructions for collecting diagnostic information.

MIS0211E RESMGR request failed

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0212E Error(s) during unbind processing

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0213E Invalid unbind option

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0214E Invalid or corrupted unbind structure

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0217E No jobstep TCB for bind

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0218E AS unbind with dependent binds active

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0300E Service service_name forced stop CALLRTM RC=rc for ASID X'nnnn'

Cause: The subsystem attempted to use CALLRTM to terminate the service address spaces in order to effect a forced stop, but the attempt failed. This may or may not indicate a problem because the address space may have terminated.

Action: If necessary, use the MVS FORCE command to terminate the address spaces.

MIS0301E Unable to allocate command notification structure

Cause: The subsystem was unable to allocate storage in CSA/ECSA subpool 231.

Action: You might need to increase the size of the CSA.

MIS0302I Service service_name drained

Cause: This is the normal response to the OSDI DRAIN command.

Action: No action is required.

MIS0303E Service service_name can't drain, currently service_state

Cause: The named service cannot be drained because it is not in the ACTIVE state.

Action: If the service is in STARTING state, then you must wait for it to reach the ACTIVE state before you can drain it.

MIS0304E Service service_name unable to schedule drain notification

Cause: The service address space could not be contacted. This might be due to a transient condition.

Action: If the problem persists call Oracle support.

MIS0305I Service service_name resumed

Cause: This is the normal response to the OSDI RESUME command.

Action: No action is required.

MIS0306E Service service_name can't resume, currently service_state

Cause: The named service cannot be stopped because it is not in the DRAINED state.

Action: None. The command is ignored. Only a service that is in DRAINED state can be resumed.

MIS0307E Service service_name unable to schedule resume notification

Cause: The service address space could not be contacted. This might be due to a transient condition.

Action: If the problem persists, call Oracle Support Services.

MIS0308I Service service_name is service_state, [ nnn address spaces ] [ ASID asid: AS_state, bbbbb binds, HHHHHHHH metric ]

Cause: This is the normal response to the OSDI DISPLAY SERVICE command. When the LONG option is specified, the second line is repeated for every address that is running for the service.

Action: No action is required.

MIS0309E Service service_name unable to schedule display request

Cause: The service address space could not be contacted. This might be due to a transient condition.

Action: If the problem persists, call Oracle Support Services.

MIS0310E Service service_name ID SID duplicates an existing service ID

Cause: The SID that is specified in a DEFINE SERVICE command is already in use.

Action: The DEFINE SERVICE command fails. The SID specified in DEFINE SERVICE must be unique throughout the z/OS system.

MIS0311E Service service_name ID SID IEANTCR call returned rc

Cause: This is probably an internal error.

Action: Contact Oracle Support Services.

MIS0312E Service service_name - invalid jobname pattern

Cause: The value supplied on the JOBNAME parameter of the DEFINE SERVICE command is invalid.

Action: Correct the jobname and reissue the command.

MIS0313E Service service_name can't alter MAXAS--not inactive

Cause: The MAXAS parameter cannot be altered while a service is active.

Action: Stop the service and retry the command.

MIS0314I Subsystem service version:version_number

Cause: This is the normal response to the OSDI SHOW VERSION command.

Action: No action is required.

MIS0315I Link Date:mm/dd/yy Time:hh.mm

Cause: This is the normal response to the OSDI SHOW VERSION command.

Action: No action is required.

MIS0316I Fixes Applied:bug_number

Cause: This is the normal response to the OSDI SHOW VERSION command.

Action: No action is required.

MIS0317I :bug_number

Cause: This is the normal response to the OSDI SHOW VERSION command.

Action: No action is required.

MIS0400E Service service_name lost one or more queued command elements

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0450E Access denied to profile: profile

Cause: The user or job has not been granted access to the profile.

Action: If appropriate, grant access to the profile.

MIS0451E Invalid subsystem ID passed to MISSAUTH

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0452E Invalid request passed to MISSAUTH

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0453E Invalid command name passed to MISSAUTH

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

MIS0454E Invalid service name passed to MISSAUTH

Cause: This message indicates an internal error.

Action: Contact Oracle Support Services for instructions.

11 User Abend Codes

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 ABEND codes 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:

- User Abend Codes U1010 to U1378

- User Abend Codes U2010 to U2011

- User Abend Codes U3975 to U3986 (Oracle Access Manager for IMS TM)

11.1 User Abend Codes U1010 to U1378

U1010

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.

U1011

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.

U1012

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).

U1013

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.

U1014

An invalid state condition was detected in the EDM address space.

U1015

An unexpected failure occurred when an EDM address space tried to post status back to the invoking server address space.

U1016

An invalid request structure was submitted to an EDM address space.

U1017

An invalid BSAM buffer state was detected in an EDM address space.

U1018

An invalid request structure was submitted to an EDM address space.

U1019

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.

U1020

During server address space initialization, the parameter structure obtained through an ASEXT macro was corrupted or incorrect.

U1021

During server address space initialization an attempt to initialize the timer function in AS1 failed.

U1022

An invalid proxy commit request was passed to an EDM address space.

U1078

An Oracle Net internal error caused a loop in the free element chain.

U1111

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.

U1112

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.

U1178

An Oracle Net internal error caused an invalid self reference pointer.

U1179

An Oracle Net internal error occurred because the sanity value was not present on allocate; the element was already in use.

U1278

An Oracle Net internal error occurred because a large element was not on the page boundary.

U1378

An Oracle Net internal error occurred because the element being freed was already on the free element chain.

11.2 User Abend Codes U2010 to U2011

These ABEND codes 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 ABEND codes should be reported to Oracle Support Services.

U2010

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:

00000001

The application context could not be located.

00000002

Oracle API DLL initialization failed. This may be accompanied by Language Environment messages indicating the nature of the error.

00000003

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.

00000005

An invalid or corrupted application context was found.

00000006

An invalid API function descriptor was found.

00000007

An invalid function index was found.

00000008

Stub function and API function mismatch.

00000009

The application is calling a missing, obsolete, or disabled API function.

0000000A

An API function supported only for C language callers has been called from a non-C language.

0000000B

Attempt to set an LE condition handler failed. This can be caused by certain environmental conditions such as insufficient private area region.

0000000E

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 on System z.

U2011

The ABEND occurred in internal application context management. The specific error is indicated by the reason code in general register 15:

00000001

An attempt to obtain memory for the internal application context failed. This generally indicates that insufficient private area region is provided.

00000002

An unexpected error occurred using Name Token services.

11.3 User Abend Codes U3975 to U3986 (Oracle Access Manager for IMS TM)

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:

U3975

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 on System z for a discussion of Oracle Access Manager for IMS TM memory requirements.

If no message is displayed, report the situation to Oracle Support Services.

U3976

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.

U3977

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.

U3978

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.

U3979

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.

U3980

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.

U3981

An error occurred during memory cleanup processing. General register 15 contains a subcode that describes the error. Report this ABEND to Oracle Support Services.

U3982

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.

U3984

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.

U3985

This ABEND is issued by the Oracle Access Manager for IMS (TM) ESAF initialization exit following messages AMI-0050, AMI-0051, or AMI-0053. It usually indicates that Oracle Access Manager for IMS (TM) does not support this version of IMS (TM.) Report this ABEND to Oracle Support.

U3986

An invalid API function descriptor was found. Report this ABEND to Oracle.

Index
A  C  D  M  O  R  S  U  Z

Numerics

1060, 6.1

1061, 6.1

1062, 6.1

1063, 6.1

1064, 6.1

1065, 6.1

1066, 6.1

1067, 6.1

1068, 6.1

1069, 6.1

1070, 6.1

1071, 6.1

1072, 6.1

1073, 6.1

1074, 6.1

1075, 6.1

1076, 6.1

1077, 6.1

1078, 6.1

1079, 6.1

1080, 6.1

1081, 6.1

1082, 6.1

1083, 6.1

1084, 6.1

1085, 6.1

1086, 6.1

1087, 6.1

1088, 6.1

1089, 6.1

1090, 6.1

1091, 6.1

1092, 6.1

1093, 6.1

1094, 6.1

1095, 6.1

1096, 6.1

1097, 6.1

1098, 6.1

1099, 6.1

1100, 6.1

1101, 6.1

1102, 6.1

1103, 6.1

1104, 6.1

1105, 6.1

1106, 6.1

1107, 6.1

1108, 6.1

1109, 6.1

1110, 6.1

1111, 6.1

1112, 6.1

1113, 6.1

1114, 6.1

1115, 6.1

1116, 6.1

1117, 6.1

1118, 6.1

1119, 6.1

1120, 6.1

1121, 6.1

1122, 6.1

1123, 6.1

1124, 6.1

1125, 6.1

1126, 6.1

1127, 6.1

1128, 6.1

1129, 6.1

1130, 6.1

1131, 6.1

1132, 6.1

1133, 6.1

1134, 6.1

1135, 6.1

1136, 6.1

1137, 6.1

1138, 6.1

1139, 6.1

1140, 6.1

1141, 6.1

1142, 6.1

1143, 6.1

1144, 6.1

1145, 6.1

1146, 6.1

1147, 6.1

1148, 6.1

1149, 6.1

1150, 6.1

1151, 6.1

1152, 6.1

1153, 6.1

1154, 6.1

1155, 6.1

1156, 6.1

1157, 6.1

1158, 6.1

1160, 6.1

1161, 6.1

1162, 6.1

1163, 6.1

1164, 6.1

1166, 6.1

1167, 6.1

1168, 6.1

1169, 6.1

1170, 6.1

1171, 6.1

1172, 6.1

1173, 6.1

1174, 6.1

1175, 6.1

1176, 6.1

1177, 6.1

1178, 6.1

1179, 6.1

1180, 6.1

1181, 6.1

1182, 6.1

1183, 6.1

1184, 6.1

1185, 6.1

1186, 6.1

1187, 6.1

1188, 6.1

1189, 6.1

1190, 6.1

1191, 6.1

1192, 6.1

1193, 6.1

1194, 6.1

1195, 6.1

1196, 6.1

1197, 6.1

1198, 6.1

1199, 6.1

1200, 6.1

1201, 6.1

1202, 6.1

1203, 6.1

1204, 6.1

1205, 6.1

1206, 6.1

1207, 6.1

1208, 6.1

1209, 6.1

1210, 6.1

1211, 6.1

1212, 6.1

1213, 6.1

1214, 6.1

1215, 6.1

1216, 6.1

1217, 6.1

1218, 6.1

1219, 6.1

1220, 6.1

1221, 6.1

1222, 6.1

1301, 6.1

1302, 6.1

1303, 6.1

1304, 6.1

1305, 6.1

1306, 6.1

1307, 6.1

1308, 6.1

1309, 6.1

1310, 6.1

1311, 6.1

1312, 6.1

1313, 6.1

1314, 6.1

1315, 6.1

1316, 6.1

1317, 6.1

1318, 6.1

1319, 6.1

1320, 6.1, 6.1

1321, 6.1

1322, 6.1

1323, 6.1

1324, 6.1

1325, 6.1

1326, 6.1

1327, 6.1

1328, 6.1

1329, 6.1

1330, 6.1

1331, 6.1

1332, 6.1

1333, 6.1

1334, 6.1

1335, 6.1

1336, 6.1

1337, 6.1

1338, 6.1

1339, 6.1

1340, 6.1

1341, 6.1

1342, 6.1

1343, 6.1

1344, 6.1

1345, 6.1

1346, 6.1

1347, 6.1

1348, 6.1

1349, 6.1

A

abend

network error message MIN0011E, 8.1

Oracle Access Manager for CICS, 2.2

user abend codes, 11

z/OS-specific Oracle error 04101, 5.1

alert log

error message MIR0611I, 9.1

error message MIR0612I, 9.1

error message MIR0613I, 9.1

AMI-0001, 1.1 AMI-0002, 1.1 AMI-0003, 1.1 AMI-0004, 1.1 AMI-0005, 1.1 AMI-0006, 1.1 AMI-0007, 1.1 AMI-0008, 1.1 AMI-0009, 1.1 AMI-0010, 1.1 AMI-0011, 1.1 AMI-0012, 1.1 AMI-0013, 1.1 AMI-0014, 1.1 AMI-0015, 1.1 AMI-0016, 1.1 AMI-0050, 1.1 AMI-0051, 1.1 AMI-0052, 1.1 AMI-0053, 1.1 AMI-0054, 1.1 AMI-0055, 1.1 AMI-0107, 1.2 AMI-0108, 1.2 AMI-0109, 1.2 AMI-0110, 1.2 AMI-0111, 1.2 AMI-0112, 1.2 AMI-0113, 1.2 AMI-0114, 1.2 AMI-0117, 1.2 AMI-0118, 1.2 AMI-0119, 1.2 AMI-0120, 1.2 AMI-0121, 1.2 AMI-0122, 1.2 AMI-0123, 1.2 AMI-0124, 1.2 AMI-0125, 1.2 AMI-0126, 1.2 AMI-0127, 1.2 AMI-0128, 1.2 AMI-0129, 1.2 AMI-0130, 1.2 AMI-0131, 1.2 AMI-0132, 1.2 AMI-0133, 1.2 AMI-0134, 1.2 AMI-0135, 1.2 AMI-0136, 1.2 AMI-0137, 1.2 AMI-0139, 1.2 AMI-0140, 1.2 AMI-0143, 1.2 AMI-0145, 1.2 AMI-0149, 1.2 AMI-0150, 1.2 AMI-0151, 1.2 AMI-0157, 1.2 AMI-0159, 1.2 AMI-0160, 1.2 AMI-0162, 1.2 AMI-0165, 1.2 AMI-0169, 1.2 AMI-0170, 1.2 AMI-0174, 1.2 AMI-0175, 1.2 AMI-0178, 1.2 AMI-0179, 1.2 AMI-0180, 1.2 AMI-0181, 1.2 AMI-0183, 1.2 AMI-0186, 1.2 AMI-0187, 1.2 AMI-0188, 1.2 AMI-0189, 1.2 AMI-0190, 1.2 AMI-0191, 1.2 AMI-0192, 1.2 AMI-0193, 1.2 AMI-0194, 1.2 AMI-0195, 1.2 AMI-0197, 1.2

C

catalog structure

ICF, OS/390-Specific Oracle Error 04114, 5.1

CFU-0001, 3.1 CFU-0002, 3.1 CFU-0003, 3.1 CFU-0004, 3.1 CFU-0005, 3.1 CFU-0006, 3.1 CFU-0007, 3.1 CFU-0008, 3.1 CFU-0009, 3.1 CFU-0010, 3.1 CFU-0011, 3.1 CFU-0012, 3.1 CFU-0013, 3.1 CFUTIL (convert file utility)

messages, 3

CIC-00001E, 2.1 CIC-00002E, 2.1 CIC-00003E, 2.1 CIC-00004E, 2.1 CIC-00005E, 2.1 CIC-00007I, 2.1 CIC-00009E, 2.1 CIC-00010E, 2.1 CIC-00011I, 2.1 CIC-00012I, 2.1 CIC-00013I, 2.1 CIC-00015E, 2.1 CIC-00016E, 2.1 CIC-00017E, 2.1 CIC-00018E, 2.1 CIC-00023I, 2.1 CIC-00024E, 2.1 CIC-00025E, 2.1 CIC-00026I, 2.1 CIC-99999, 2.1

D

dsname

database region message MIR0013E, 9.1

database region message MIR0014E, 9.1

M

MAXAS parameter

platform-specific error 0411, 5.1

platform-specific error 04111, 5.1

MIC011E to MIC022E messages, 7.1 MIC0208E to MIC0377E messages, 7.2 MIN0001I to MIN1105E messages, 8.1 MIR0001I to MIR0622I messages, 9.1 MIS0001E to MIS0454E messages, 10.1

O

OFT101E, 4.2

OFT101I, 4.1

OFT102E, 4.2

OFT102I, 4.1

OFT103E, 4.2

OFT104E, 4.2

OFT104I, 4.1

OFT105E, 4.2

OFT105I, 4.1

OFT106E, 4.2

OFT106I, 4.1

OFT107I, 4.1

OFT108E, 4.2

OFT109E, 4.2

OFT110E, 4.2

OFT111E, 4.2

OFT112E, 4.2

OFT119E, 4.2

OFT919E, 4.2

OFT999E, 4.2

ORA-04100, 5.1

ORA-04100 to ORA-04166 messages, 5.1

ORA-04101, 5.1

ORA-04103, 5.1

ORA-04104, 5.1

ORA-04105, 5.1

ORA-04107, 5.1

ORA-04108, 5.1

ORA-04109, 5.1

ORA-04110, 5.1

ORA-04111, 5.1

ORA-04112, 5.1

ORA-04113, 5.1

ORA-04114, 5.1

ORA-04115, 5.1

ORA-04116, 5.1

ORA-04117, 5.1

ORA-04118, 5.1

ORA-04119, 5.1

ORA-04120, 5.1

ORA-04121, 5.1

ORA-04122, 5.1

ORA-04123, 5.1

ORA-04124, 5.1

ORA-04125, 5.1

ORA-04126, 5.1

ORA-04127, 5.1

ORA-04128, 5.1

ORA-04129, 5.1

ORA-04130, 5.1

ORA-04131, 5.1

ORA-04132, 5.1

ORA-04133, 5.1

ORA-04134, 5.1

ORA-04135, 5.1

ORA-04136, 5.1

ORA-04137, 5.1

ORA-04138, 5.1

ORA-04139, 5.1

ORA-04140, 5.1

ORA-04141, 5.1

ORA-04142, 5.1

ORA-04143, 5.1

ORA-04144, 5.1

ORA-04145, 5.1

ORA-04146, 5.1

ORA-04147, 5.1

ORA-04148, 5.1

ORA-04149, 5.1

ORA-04150, 5.1

ORA-04151, 5.1

ORA-04152, 5.1

ORA-04153, 5.1

ORA-04154, 5.1

ORA-04155, 5.1

ORA-04156, 5.1

ORA-04157, 5.1

ORA-04158, 5.1

ORA-04159, 5.1

ORA-04160, 5.1

ORA-04161, 5.1

ORA-04162, 5.1

ORA-04163, 5.1

ORA-04164, 5.1

ORA-04166, 5.1

ORAP abends, 2.2

R

REGION parameter

platform-specific error 04111, 5.1

platform-specific error 04116, 5.1

S

SID parameter

error message MIS0182E, 10.1

U

U1010, 11.1

U1011, 11.1

U1012, 11.1

U1013, 11.1

U1014, 11.1

U1015, 11.1

U1016, 11.1

U1017, 11.1

U1018, 11.1

U1019, 11.1

U1020, 11.1

U1021, 11.1

U1022, 11.1

U1078, 11.1

U1111, 11.1

U1112, 11.1

U1178, 11.1

U1179, 11.1

U1278, 11.1

U1378, 11.1

U2010, 11.2

U2011, 11.2

U3975, 11.3

U3976, 11.3

U3977, 11.3

U3978, 11.3

U3979, 11.3

U3980, 11.3

U3981, 11.3

U3982, 11.3

U3984, 11.3

U4034 to U4095, 11

UNIX System Services, z/OS

error message MIR0110W, 9.1

error message MIR0111W, 9.1

error message MIR0112E, 9.1

Z

z/OS UNIX System Services

error message MIR0110W, 9.1

error message MIR0111W, 9.1

error message MIR0112E, 9.1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2016, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Alpha and Beta Draft Documentation Notice

If this document is in private preproduction status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your beta trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.