Oracle9i Enterprise Edition Messages Guide
Release 2 (9.2.0.1.0) for OS/390

Part Number A97314_01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

8
Client Infrastructure Messages

This chapter documents the messages that are issued by OS/390-specific components of the Oracle client software on OS/390. 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 USS.

The messages begin with the prefix "MIC" followed by a 3-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:

E

Error. Action is required.

I

Information. Action is not required.

W

Warning. Action might be required.

The following messages are described in this chapter:

Messages MIC011 to MIC022

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 12, "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 (e.g. 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.

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 via the system link list. In the USS environment, a STEPLIB environment variable may be needed.


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

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