Oracle9i Enterprise Edition Messages Guide
Release 1 (9.0.1) for OS/390

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

Go to previous page Go to next page

9
Database Region Messages

This chapter documents the messages that are issued by the database instance management component of Oracle9i. 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:

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 MIR0001 to MIR0613

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.

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.

MIR0003I Quiescing ssssssss service address spaces

Cause: An OS/390 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.

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.

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 OS/390 Program Properties Table (PPT) with an entry that specifies KEY(7), and make sure 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 OS/390 Program Properties Table (PPT) with an entry that specifies NOSWAP, and make sure 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.

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.

MIR0011I Stop command received

Cause: The database service acknowledges receiving an OS/390 or OSDI STOP (or P) command.

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.

MIR0013E Failed to allocate parameter data set dsname

Cause: During database service initialization, the region parameters data set (supplied via 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 via 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. Make sure 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.

MIR0026W Errors encountered reading file management input -
Continuing with some defaults

Cause: During database region initialization processing of the file management parameters (ORA$FPS DD statement in server JCL), one or more errors were encountered. (These are described by other messages issued earlier.)

Action: The service will continue initialization with whatever file parameters it was able to recognize.

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.

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.

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

MIR0032W Syntax error; skipping keyword: text

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.

MIR0033W Invalid keyword value; keyword ignored: text

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 keyword was unacceptable.

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.

MIR0034W Unrecognized keyword; ignored: text

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.

MIR0035W I/O error reading file management parameters

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.

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 an OS/390 Unix System Services (USS) process has failed. Service initialization continues, and the database can be started up as usual. However, database functions that interact with OS/390 USS will not be available.

Action: Usually this message results from not having a default OE segment defined for the OS/390 userid 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 USS 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 an OS/390 USS resource allocated by the session has failed.

Action: The service continues execution normally. This message should be reported to Oracle Support Services.

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: Make sure 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.

MIR0500I Command processed

Cause: A command that was issued using the OS/390 MODIFY (F) interface has been processed.

MIR0501E Command not processed

Cause: A command that was issued using the OS/390 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 via the OS/390 MODIFY (F) interface could not find any server sessions matching the criteria specified in the command.

MIR0503I Sess=pid, job=jobname, TCB=tcbaddr, AS=asix

Cause: A DISPLAY SESSION command that was issued via the OS/390 MODIFY (F) interface found a server session matching the selection criteria. The session originated in the OS/390 address space whose jobname is jobname, from the task whose TCB address is tcbaddr. The session has an Oracle process ID of pid, and it is assigned to server address space number asix.

MIR0504W Results may be inaccurate; enter command again

Cause: A DISPLAY SESSION command that was issued via the OS/390 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 via the OS/390 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 via the OS/390 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 via the OS/390 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.


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