3
Resource Recovery Manager Messages

This chapter lists the messages issued by the Oracle Procedural Gateway for APPC Resource Recovery Manager (RRM) and provides a possible cause and recommended action for each message.

This chapter contains the following sections:

• Messages PGA-21001 to PGA-21211

• Messages PGA-21212 to PGA-21450

Messages PGA-21001 to PGA-21211

PGA-21001 internal error: args

Cause: Internal error in the gateway RRM process.

Action: Reproduce the error with tracing enabled to produce a trace file. Supported customers should contact Oracle Support Services for assistance.

PGA-21002 unable to obtain bytes bytes of memory for usage

Cause: Memory shortage in the gateway RRM process. A request failed to allocate bytes of memory for the usage area.

Action: Ensure that your system has enough available memory to support the RRM.

PGA-21003 memory allocation error in lxlinit

Cause: Memory shortage in the gateway RRM process.

Action: Ensure that your system has enough available memory to support the RRM.

PGA-21004 invalid comp specified by NLS_LANG

Cause: The comp component of the NLS_LANG environment variable was not valid. The component can be the language, territory, or character set.

Action: Correct the invalid component and restart the RRM process.

PGA-21005 no message file found for language 'lang'

Cause: There was no message file available for the language lang specified by the NLS_LANG environment variable.

Action: Refer to Appendix H, "National Language Support," in the Oracle Procedural Gateway for APPC User's Guide for a list of message file languages supported by the RRM. If the language required is supported, then ensure that the ORACLE_HOME environment variable specifies the gateway's home directory and that the message files are properly installed.

PGA-21006 RRM initialization failed

Cause: The initialization of the gateway RRM process failed.

Action: This message is sent to the system log as an ALERT message when the initialization of the RRM failed before it could initialize the message facility or before it could determine the local LU name for which it was started.

PGA-21010 missing fully-qualified local LU name argument

Cause: The fully-qualified local LU name was not passed as the first argument to the pg4arrm program on the command line.

Action: The fully-qualified local LU name must be specified as the first argument to the pg4arrm program. Reenter the command line with the fully-qualified local LU name specified.

PGA-21011 invalid network name length (len), valid range is min:max

Cause: The network name portion of the fully-qualified local LU name specified as the first argument to the pg4arrm program is the wrong length (len).

Action: The valid range of lengths for the network name is given in the message text by min:max. Reenter the command line with a valid network name specified in the fully-qualified local LU name.

PGA-21012 invalid LU name length (len), valid range is min:max

Cause: The LU name portion of the fully-qualified local LU name specified as the first argument to the pg4arrm program is the wrong length (len).

Action: The valid range of lengths for the LU name is given in the message text by min:max. Reenter the command line with a valid LU name specified in the fully-qualified local LU name.

PGA-21013 missing period(.) in fully-qualified local LU name

Cause: There is no period (.) in the fully-qualified local LU name specified as the first argument to the pg4arrm program.

Action: A fully-qualified local LU name must contain a network name and an LU name, separated by a period (.). Reenter the command line with a valid fully-qualified local LU name specified.

PGA-21014 invalid character(s) found in network name 'net'

Cause: One or more invalid characters were found in the network name portion net of the fully-qualified local LU name.

Action: The network name must begin with an uppercase alphabetic character or one of the national characters $, #, or @. Subsequent characters can be uppercase alphabetic, national, or numeric. Reenter the command line with a valid network name specified in the fully-qualified local LU name.

PGA-21015 invalid character(s) found in LU name 'lu'

Cause: One or more invalid characters were found in the LU name portion lu of the fully-qualified local LU name.

Action: The LU name must begin with an uppercase alphabetic character or one of the national characters $, #, or @. Subsequent characters can be uppercase alphabetic, national, or numeric. Reenter the command line with a valid network name specified in the fully-qualified local LU name.

PGA-21016 RRM initialization failed for LU lu

Cause: The initialization of the gateway RRM process for local LU lu failed.

Action: This message is sent to the system log as an ALERT message when the initialization of the RRM failed for the local LU.

PGA-21017 RRM already active for LU lu

Cause: The RRM has already been started for the local LU lu. A second RRM cannot be started for the same local LU.

Action: Determine whether the RRM is still active and functioning. If it is not, then it might have terminated without cleaning up. On UNIX systems, the /var/tmp/rrmluname file might still exist. This prevents a new RRM from being started. If you have verified that the original RRM is no longer running, then you can delete the file to allow a new copy of the RRM to be started.

PGA-21020 error creating path object for init file

Cause: A memory shortage occurred while creating an internal control block for accessing the init file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21021 error creating name object for init file

Cause: A memory shortage occurred while creating an internal control block for accessing the init file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21022 error creating file object for init file

Cause: A memory shortage occurred while creating an internal control block for accessing the init file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21023 error opening init file ifn

Cause: An error occurred opening the init file ifn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21024 error reading init file ifn

Cause: An error occurred reading the init file ifn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21025 error closing init file ifn

Cause: An error occurred closing the init file ifn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21030 invalid keyword in line line

Cause: An invalid keyword was encountered in the init file in line number line.

Action: Correct the invalid line in the init file and restart the RRM process.

PGA-21031 length of key value (len) not within valid range (min:max)

Cause: The length len of the value specified in the init file by the keyword key is not within the valid range min:max.

Action: Correct the invalid keyword value in the init file and restart the RRM process.

PGA-21032 invalid value specified by key=val

Cause: The value val specified in the init file by the keyword key is invalid.

Action: Correct the invalid keyword value in the init file and restart the RRM process.

PGA-21033 error(s) found in init file

Cause: One or more errors were found in the init file during RRM initialization. The RRM process has terminated.

Action: Correct all init file errors and restart the RRM process.

PGA-21034 too many errors in init file, cannot continue

Cause: The init file contained more errors than the RRM initialization code could process.

Action: Correct all errors that have been processed so far and restart the RRM process. Any additional errors are then processed. This error is received only when the init file contains many invalid lines.

PGA-21035 value of key (val) not within valid range (min:max)

Cause: The value val specified in the init file by the keyword key is not within the valid range min:max.

Action: Correct the invalid keyword value in the init file and restart the RRM process.

PGA-21040 error creating path object for log file

Cause: A memory shortage occurred while creating an internal control block for accessing the log file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21041 error creating name object for log file

Cause: A memory shortage occurred while creating an internal control block for accessing the log file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21042 error creating file object for log file

Cause: A memory shortage occurred while creating an internal control block for accessing the log file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21043 error opening log file lfn

Cause: An error occurred opening the log file lfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21044 error writing to log file lfn

Cause: An error occurred writing to the log file lfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21045 error closing log file lfn

Cause: An error occurred closing the log file lfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21046 logging switched to system log due to error on log file

Cause: An error occurred writing to the log file, and logging as been switched to the system log facility for the remainder of this RRM execution.

Action: Correct the problem that caused the error on the log file, so that the next restart of the RRM is able to write to the log file. A common cause for this message is unavailable disk space for the file.

PGA-21050 error creating path object for trace file

Cause: A memory shortage occurred while creating an internal control block for accessing the trace file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21051 error creating name object for trace file

Cause: A memory shortage occurred while creating an internal control block for accessing the trace file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21052 error creating file object for trace file

Cause: A memory shortage occurred while creating an internal control block for accessing the trace file.

Action: Ensure that sufficient memory is available to the RRM process. If the problem persists, then supported customers should contact Oracle Support Services for assistance.

PGA-21053 error opening trace file tfn

Cause: An error occurred opening the trace file tfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21054 error writing to trace file tfn

Cause: An error occurred writing to the trace file tfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21055 error closing trace file tfn

Cause: An error occurred closing the trace file tfn.

Action: This message is followed by an OS-specific message displaying the error information. Use that information to determine the cause of the error and correct it. Then restart the RRM process.

PGA-21056 tracing suspended due to error on trace file

Cause: An error occurred writing to the trace file and tracing has been suspended for the remainder of this RRM execution.

Action: Correct the problem that caused the error on the trace file, so that the next restart of the RRM is able to write to the trace file. A common cause for this message is unavailable disk space for the file.

PGA-21060 system errno = errno

Cause: The system error number was errno following a failure in a file operation.

Action: The system error codes are documented in the header file /usr/include/errno.h. Determine the cause of the error and correct it.

PGA-21100 RRM initializing for local LU llu

Cause: The RRM is initializing for the local LU llu.

Action: Informational message.

PGA-21101 initialization parameters read from ifn

Cause: Init parameters were read from the file ifn.

Action: Informational message.

PGA-21102 log messages written to lfn

Cause: Log messages are written to the file lfn.

Action: Informational message.

PGA-21103 trace information written to tfn

Cause: Trace information is written to the file tfn.

Action: Informational message.

PGA-21104 trace level currently set to trc

Cause: The trace level specified by the TRACE_LEVEL parameter is trc.

Action: Informational message.

PGA-21105 startup for local LU llu is warm

Cause: The RRM is warmstarting for the local LU llu. The RRM attempts to restore all LU6.2 log states from the RRM LU6.2 log as it existed at the last RRM shutdown.

Action: Informational message.

PGA-21106 warm start complete for local LU llu

Cause: The RRM has warmstarted for the local LU llu. This means that all state information, for the local LU and partner LUs with which the RRM has previously communicated, was restored from the RRM LU6.2 log as it existed at the last RRM shutdown.

Action: Informational message.

PGA-21107 startup for local LU llu is cold

Cause: The RRM is coldstarting for the local LU llu. The RRM does not retain any LU6.2 log states from the previous execution.

Action: Informational message.

PGA-21108 cold start complete for local LU llu

Cause: The RRM has coldstarted for the local LU llu. The RRM has a new local LU6.2 log name and all LU6.2 log names for partner LUs have been erased.

Action: Informational message.

PGA-21109 local log name is x'llog'

Cause: The local LU's LU6.2 log name is llog. Because the log name is not necessarily a printable string, it is listed as a hexadecimal string.

Action: Informational message.

PGA-21110 XLN received from partner LU

Cause: An Exchange Log Names (XLN) GDS variable has been received from the RRM at the partner LU plu. This is the first thing that occurs when communication is established with a partner LU for the first time after either the local RRM or the partner RRM was last started.

Action: Informational message.

PGA-21111 partner log name is x'plog'

Cause: The partner LU's LU6.2 log name is plog. Because the log name is not necessarily a printable string, it is listed as a hexadecimal string.

Action: Informational message.

PGA-21112 creating new log entry for partner LU plu

Cause: The RRM is creating an entry in its LU6.2 log for the partner LU plu. This happens only the first time that the partner LU's RRM contacts the local RRM after the last coldstart of the local RRM.

Action: Informational message.

PGA-21113 warm starting for partner LU plu

Cause: The RRM is warmstarting for the partner LU plu. This happens when the partner LU's RRM is warmstarting and is contacting the local RRM for the first time after the local RRM was started.

Action: Informational message.

PGA-21114 cold starting for partner LU plu

Cause: The RRM is coldstarting for the partner LU plu. This happens when the partner LU's RRM is coldstarting and is contacting the local RRM for the first time after the local RRM was started.

Action: Informational message.

PGA-21115 shutdown request received

Cause: A shutdown request has been received by the RRM.

Action: Informational message.

PGA-21116 RRM termination complete for local LU llu

Cause: The RRM has terminated for the local LU llu.

Action: Informational message. PGA-21200 connect to Oracle server as user failed.

Cause: The RRM was unable to connect as user user to the Oracle server where its LU6.2 log information is stored. An Oracle server message follows this message.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the LOG_DB, LOG_USER and LOG_PASS parameters in the RRM init file and ensure that they specify the correct database string, user ID and password, respectively.

PGA-21201 error selecting PGA_2PC_LUS row for local LU llu

Cause: The RRM was unable to read its local LU6.2 log entry. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM cold started.

PGA-21202 error updating PGA_2PC_LUS row for local LU llu

Cause: The RRM was unable to update its local LU6.2 log entry during warmstart processing. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21203 error inserting PGA_2PC_LUS row for local LU llu

Cause: The RRM was unable to create its local LU6.2 log entry during coldstart processing. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted again.

PGA-21204 error deleting PGA_2PC_PENDING rows for local LU llu

Cause: The RRM was unable to delete the pending transaction entries from its local LU6.2 log during coldstart processing. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_PENDING table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted again.

PGA-21205 error deleting PGA_2PC_LUS rows for partner LUs

Cause: The RRM was unable to delete the partner LU entries from its local LU6.2 log during coldstart processing. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted again.

PGA-21206 error selecting PGA_2PC_LUS row for partner LU plu

Cause: The RRM was unable to read its local LU6.2 log entry for the partner LU. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21207 error inserting PGA_2PC_LUS row for partner LU plu

Cause: The RRM was unable to create a local LU6.2 log entry for the partner LU. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21208 error updating PGA_2PC_LUS row for partner LU plu

Cause: The RRM was unable to update its local LU6.2 log entry for the partner LU. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21209 error selecting PGA_2PC_PENDING rows for partner LU plu

Cause: The RRM was unable to read the pending transaction entries from its LU6.2 log for the partner LU plu. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_PENDING table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21210 unable to open connection with SNA services

Cause: The RRM was unable to initialize its connection with the SNA software for LU6.2 communications. An OS-specific error message precedes this message.

Action: Check the error information in the OS-specific error message to determine the cause of the problem and take corrective action. After the problem has been corrected, restart the RRM.

PGA-21211 unable to allocate LU6.2 listen for RRM TP

Cause: The RRM was unable to allocate an LU6.2 listen with the SNA software for LU6.2 communications. An OS-specific error message precedes this message.

Action: Check the error information in the OS-specific error message to determine the cause of the problem and take corrective action. After the problem has been corrected, restart the RRM.

Messages PGA-21212 to PGA-21450

PGA-21212 incorrect data received from partner LU plu

Cause: A partner LU has sent incorrect data in its initial communication with the local RRM. The first data received should have been an Exchange Log Names (XLN) GDS variable, but was not.

Action: This error indicates that there is a problem on the partner LU side of the connection. Corrective action must be taken by the system administrator for that LU.

PGA-21213 received x'data'

Cause: This message follows message PGA-21212 and dumps out the first 32 bytes of the data received from the partner LU.

Action: If the data in this message is not sufficient for determination of the problem at the partner LU, then use SNA traces on either side of the connection to gather more detailed information, or use the TRACE_LEVEL parameter in the RRM init file to enable SNA data tracing to the trace file.

PGA-21214 incorrect service flag in XLN

Cause: The service flag in the Exchange Log Names (XLN) GDS variable received from the partner LU's RRM is not correct. The XLN is expected to have the REQUEST flag set.

Action: This error indicates that there is a problem on the partner LU side of the connection. Corrective action must be taken by the system administrator for that LU.

PGA-21215 partner log name mismatch on warm start

Cause: The Exchange Log Names (XLN) GDS variable received from the partner LU's RRM contains an LU6.2 log name that is different from that known by the local LU's RRM.

Action: This can happen if the partner LU was coldstarted and later warmstarted, all between the times the local LU's RRM was last shut down and warmstarted. The local LU's RRM is not aware that the partner LU was coldstarted and therefore assumes that the partner LU's RRM is using the wrong LU6.2 log name. Verify that this is what happened and if this is so, then the local LU's RRM can be forced to accept the new LU6.2 log name from the partner LU's RRM--by deleting the local RRM's LU6.2 log entry for the partner LU and then forcing the partner LU to reinitiate the connection to the local LU. For further information on recovery from this error, refer to "RRM Recovery" in Chapter 7, "Implementing Two-phase Commit," of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your platform.

PGA-21216 last stored log name x'plog'

Cause: This message always follows message PGA-21215, and lists the last partner LU LU6.2 log name that plog saved by the local LU's RRM.

Action: The log name in the message might be of use to the system administrator for the partner LU in determining the cause for the log name mismatch.

PGA-21217 partner sent log name x'plog'

Cause: This message always follows message PGA-21215, and lists the LU6.2 log name that plog sent by the partner LU's RRM in the warm start Exchange Log Names (XLN) GDS variable.

Action: The log name in the message might be of use to the system administrator for the partner LU in determining the cause for the log name mismatch.

PGA-21218 cold start for partner LU plu rejected, count pending transactions exist

Cause: A coldstart was requested by the partner LU's RRM, but the local RRM determined that there are still unresolved pending transactions for that LU in the local RRM's LU6.2 log.

Action: If the pending transactions have been resolved, then they must be manually deleted from the local RRM's LU6.2 log before the partner LU's coldstart request is accepted. If the pending transactions have not been resolved, then they must be resolved and then manually deleted from the local RRM's LU6.2 log before the partner LU's coldstart request is accepted.

PGA-21219 recovery action by DBA required for local LU llu

Cause: A condition has occurred which requires action by the DBA. This message is also sent to the system log as an alert message.

Action: The DBA must examine the RRM log file to determine what action to take. The messages in the log file show what event has occurred that makes DBA action necessary, and their descriptions provide the DBA with a course of action. For further information on recovery, refer to "RRM Recovery" in Chapter 7, "Implementing Two-Phase Commit," of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your platform.

PGA-21220 logging error limit (lim) exceeded, RRM shutting down for LU llu

Cause: The limit of lim Oracle errors while accessing the RRM's local LU6.2 log tables has been exceeded. The RRM for the local LU llu is shutting down.

Action: The DBA examines the RRM log file to determine what action to take. The messages in the log file show what Oracle errors have occurred and the DBA takes whatever corrective action is required.

PGA-21221 commit failed during cold start of local LU llu

Cause: The RRM was unable to commit updates to its local log during a coldstart of local LU llu. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21222 commit failed during warm start of local LU llu

Cause: The RRM was unable to commit updates to its local log during a warmstart of local LU llu. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21223 commit failed during first-time processing for partner LU plu

Cause: The RRM was unable to commit updates to its local log during first-time processing for partner LU plu. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21224 commit failed during cold start of partner LU plu

Cause: The RRM was unable to commit updates to its local log during a coldstart of partner LU plu. An Oracle server message follows this message and contains information on the Oracle error.

Action: Ensure that the Oracle server and its TNS listener are both operational. Also ensure that the PGA_2PC_LUS table exists and has not been altered or updated manually. If the table has been tampered with, then it might need to be re-initialized and the RRM coldstarted.

PGA-21300 received no data when expecting data

Cause: The RRM was expecting to receive data from a partner RRM, but received none.

Action: This error indicates that there might be a problem on the partner LU side of the connection. Corrective action must be taken by the system administrator for that LU.

PGA-21301 invalid control received: control

Cause: The RRM received an invalid control flag control from a partner RRM.

Action: This error indicates that there might be a problem on the partner LU side of the connection. Corrective action must be taken by the system administrator for that LU.

PGA-21400 ORACLE_HOME environment variable not set

Cause: The ORACLE_HOME environment variable was not set before the RRM was started.

Action: The ORACLE_HOME environment variable must be set to the gateway's ORACLE_HOME directory before the RRM is started.

PGA-21401 ORACLE_HOME environment variable set to null string

Cause: The ORACLE_HOME environment variable was set to a null value.

Action: The ORACLE_HOME environment variable must be set to the gateway's ORACLE_HOME directory before the RRM is started.

PGA-21402 error opening file fn, fopen errno = errno

Cause: An error occurred opening the RRM enqueue file fn for writing. The error number from fopen is errno.

Action: Use the errno value to determine the cause of the problem and correct it before restarting the RRM.

PGA-21403 error writing to file fn, fputs errno = errno

Cause: An error occurred writing to the RRM enqueue file fn. The error number from fputs is errno.

Action: Use the errno value to determine the cause of the problem and correct it before restarting the RRM.

PGA-21404 error closing file fn, fclose errno = errno

Cause: An error occurred closing the RRM enqueue file fn. The error number from fclose is errno.

Action: Use the errno value to determine the cause of the problem and correct it before restarting the RRM.

PGA-21405 error deleting file fn, remove errno = errno

Cause: An error occurred deleting the RRM enqueue file fn during shutdown. The error number from remove is errno.

Action: Use the errno value to determine the cause of the problem and correct it before restarting the RRM. The file fn must be manually deleted before attempting to start the RRM.

PGA-21450 communication error: 'func' failed, errno = errno

Refer to Appendix B of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your platform for information on this message.