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

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 on compiling and linking customer applications, refer to the Oracle Database User's Guide for IBM z/OS.

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 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 via 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