Skip Headers
Oracle® Database Error Messages
11g Release 1 (11.1)

B28278-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
Mobi · ePub

81 PGA-20900 to PGA-22014

PGA-20900: unable to obtain number bytes of storage for string
Cause: Memory shortage in the gateway server process.
Action: Ensure your system has enough available memory to support the number of concurrent users you are running.
PGA-20901: internal gateway error: string
Cause: Internal error in the gateway server process.
Action: Reproduce the error with debugging enabled to produce a log file. Supported customers should contact Oracle Worldwide Support for assistance.
PGA-20905: invalid conversation id: no active conversations were found
Cause: There were no APPC conversations active for the user.
Action: Check that the application is not calling the PL/SQL TIP routines out of sequence.
PGA-20906: invalid conversation id: no matching conversation was found
Cause: The conversation id received from the caller is not a valid active conversation id.
Action: Check that the application is not calling the PL/SQL TIP routines out of sequence.
PGA-20907: preceding error occurred during gateway string processing
Cause: An error occurred processing the Oracle function <func>. This message is preceded by additional messages providing more detailed information about the error.
Action: Refer to the messages preceding this one to determine the course of action to take.
PGA-20910: communication error: CPI-C string failed, rc = number, errno = number
Cause: An unexpected communication error occurred while executing the specified CPI-C function <func>. The CPI-C function return code <rc> and system error number <errno> are provided in the message text. The CPI-C function return codes and system error numbers are described in the vendor documentation.
Action: Determine the cause of the communications error, correct it, and rerun the transaction.
PGA-20911: update transaction is already active with TP string at LU string
Cause: Transaction <tpname> has already been started at LU <luname> by a PGAINIT call with synclevel set to 1 or 2. Only one transaction at synclevel 1 or 2 is allowed at any given time.
Action: The new transaction is not started. Change your application to start the second update transaction after the first one has completed, or to use a different gateway database link for the second update transaction.
PGA-20912: send and receive buffer lengths cannot both be zero
Cause: Both the send and receive buffer lengths passed to PGAXFER were zero. This is invalid.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20914: send buffer length of number exceeds actual send buffer size of number
Cause: The send buffer length <len> passed to PGAXFER was larger than the actual size <size> of the send buffer passed to PGAXFER.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20915: receive buffer length of number exceeds the maximum of number
Cause: The receive buffer length <len> passed to PGAXFER was larger than the maximum allowed length <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20916: send count is number but only number send lengths were specified
Cause: The first value <count> in the send lengths array passed to PGAXFER specified more elements than the send lengths array contained. Only <num> elements were found in the array.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20917: receive count is number but only number receive lengths were specified
Cause: The first value <count> in the receive lengths array passed to PGAXFER specified more elements than the receive lengths array contained. Only <num> elements were found in the array.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20918: send length number number is number but only number bytes are left in the buffer
Cause: The length <len> specified in send lengths array element number <num> exceeded the number of bytes <bytes> of data remaining in the send buffer.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20919: receive length number number is number but only number bytes are left in the buffer
Cause: The length <len> specified in receive lengths array element number <num> exceeded the number of bytes <bytes> of space remaining in the receive buffer.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20920: unexpected request-to-send received
Cause: The remote transaction program requested to send data when the gateway was still sending data.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20921: buffer overflow on receive: requested number bytes, received number bytes
Cause: The remote transaction program sent <len> bytes of data when the gateway was expecting to receive only <num> bytes.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20922: no data available to receive: number bytes were requested
Cause: The remote transaction program has either requested to receive or deallocated the conversation, but the gateway is still expecting to receive more data.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.
PGA-20923: unexpected status, number (string), received after string
Cause: An unexpected status code <stat> was received from the remote transaction program following the CPI-C <func> call. The descriptive name of the status code is <desc>. <func> is the CPI-C function receiving the status.
Action: This is usually a problem with the remote transaction program or a network problem. The status codes for each CPI-C function call are documented in the platform-specific SNA software documentation for your system. Refer to the "System Requirements" chapter of the Oracle Database Gateway for APPC Installation and Configuration Guide for your platform for titles of SNA software documentation.
PGA-20924: unable to enter send state for deallocate, state = number (string)
Cause: The gateway was unable to enter send state to perform a normal deallocation. The conversation state is <state>, and its descriptive name is <desc>. The conversation states are documented in the /usr/include/cmc.h header file.
Action: This is usually a problem with the remote transaction program or a problem with the network. Check the remote system for diagnostic information. The gateway will perform an abnormal deallocation after this error has been encountered.
PGA-20925: missing LU/TP/MODE name parameter and no side info profile specified
Cause: PGAINIT was called with no Side Information profile name specified but the LU name, TP name, and MODE name parameters were not all filled in with non-blank values.
Action: Check the PGDL used to define the transaction program to PGAU to ensure that either a valid Side Information profile name is specified (SIDEPROFILE keyword), or that the LU name, TP name, and Mode name (LUNAME, TPNAME, LOGMODE keywords) are all specified with valid values. If no Side Information profile is specified, the LU name, TP name, and Mode name parameters are all required.
PGA-20926: userid string length of number is invalid; maximum length is number
Cause: The userid <uid> is too long (<len>) to be used with APPC conversation security. The maximum allowable length for the userid is <max> characters. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to either SAME or PROGRAM.
Action: The userid must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. This restriction is imposed by SNA and APPC, not by the gateway.
PGA-20927: password length of number is invalid; maximum length is number
Cause: The password is too long (<len>) to be used with APPC conversation security. The maximum allowable length for the password is <max> characters. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to PROGRAM.
Action: The password must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. This restriction is imposed by SNA and APPC, not by the gateway.
PGA-20928: cannot open parameter file string
Cause: The gateway cannot locate or open the file specified.
Action: Make sure that the file exists in a location expected by the gateway and can be opened.
PGA-20930: invalid SYNCLEVEL, number, specified; valid range is number:number
Cause: The synclevel, <sync>, passed to PGAINIT is not a valid value. This value is specified by the SYNCLEVEL keyword in the DEFINE TRANSACTION statement used to define the transaction to PGAU.
Action: The value for SYNCLEVEL must fall within the range <min>:<max>. Correct the value specified in the DEFINE TRANSACTION statement for the SYNCLEVEL keyword, and regenerate the PL/SQL TIP using PGAU.
PGA-20931: send buffer length of number exceeds the maximum of number
Cause: The send buffer length, <len>, passed to PGAXFER was larger than the maximum allowed, <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU do not define any data items larger than the maximum size allowed by APPC. Correct the data item(s) in error and regenerate the PL/SQL TIP using PGAU.
PGA-20932: invalid function code, string, passed to pgatctl
Cause: The function code, <func>, passed to the PGATCTL function was invalid.
Action: Correct the function code in the PL/SQL procedure, recompile it, and retry the operation.
PGA-20933: invalid value specified by initialization parameter string=string
Cause: The keyword parameter <keyword>=<value> specifies an invalid value.
Action: Refer to the Oracle Database Gateway for APPC, Installation and Configuration Guide, documenting gateway initilization parameters for the keyword and correct the error.
PGA-20934: side information profile string not defined; cannot establish conversation
Cause: The Side Information profile <profile> is not defined to the SNA software. Either the profile name was misspelled, or no profile has been defined.
Action: Correct the profile name if it was misspelled, or have the profile defined to the SNA software if it was not already defined.
PGA-20935: synclevel number is not allowed when PGA_CAPABILITY=string
Cause: The synclevel parameter <sync> passed to PGAINIT was incompatible with the setting of the PGA_CAPABILITY gateway initialization parameter, <cap>.
Action: If the synclevel passed to PGAINIT is correct, then the gateway initialization parameter PGA_CAPABILITY must be changed to allow the desired synclevel to be supported. If the synclevel is not correct, the TIP should be changed to specify the correct sync- level in the call to PGAINIT. If the TIP was generated by PGAU, the SYNCLEVEL keyword of the DEFINE TRANSACTION statement should be changed to specify the correct synclevel and the TIP should be regenerated. The table below shows which synclevels are valid with each PGA_CAPABILITY setting. PGA_CAPABILITY Value SYNCLEVELs Allowed ---------------------- ------------------ READ_ONLY 0 SINGLE_SITE 0, 1 COMMIT_CONFIRM 0, 1
PGA-20936: send buffer length is number but no send lengths were specified
Cause: The send buffer length passed to PGAXFER was <len>, but the send lengths array was either null or contained a send count of zero.
Action: Check that the PGDL or COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions.
PGA-20937: receive buffer length is number but no receive lengths were specified
Cause: The receive buffer length passed to PGAXFER was <len>, but the receive lengths array was either null or contained a receive count of zero.
Action: Check that the PGDL or COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions.
PGA-20938: send lengths array too small (number) to contain a valid send count
Cause: The send lengths array passed to PGAXFER was too small to contain a valid send item count. The actual length of the send lengths array was <len>. The minimum length of the send lengths array is 4 bytes.
Action: If the TIP was generated by PGAU, ensure that it was not modified incorrectly. If the TIP was not modified, supported customers should contact Oracle Worldwide Support for assistance. If the TIP was modified or was not generated by PGAU, correct the send lengths array passed to PGAXFER.
PGA-20939: receive lengths array too small (number) to contain a valid receive count
Cause: The receive lengths array passed to PGAXFER was too small to contain a valid receive item count. The actual length of the receive lengths array was <len>. The minimum length of the receive lengths array is 4 bytes.
Action: If the TIP was generated by PGAU, ensure that it was not modified incorrectly. If the TIP was not modified, supported customers should contact Oracle Worldwide Support for assistance. If the TIP was modified or was not generated by PGAU, correct the receive lengths array passed to PGAXFER.
PGA-20945: unable to log on to Oracle for transaction logging
Cause: The gateway server was unable to connect to the Oracle server where the transaction log table is stored. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. If the protocol is SNA: also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. If the protocol is TCP/IP: also check the PGA_TCP_DB, PGA_TCP_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. Refer to the Oracle Server Messages and Codes Manual for information on the Oracle server message.
PGA-20947: unable to bind variable string for transaction logging
Cause: The gateway server was unable to bind variable <var> for use in performing transaction logging functions. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. Refer to the Oracle Server Messages and Codes Manual for information on the Oracle server message.
PGA-20948: unable to prepare the statement for transaction logging
Cause: The gateway server was unable to prepare the statement to be used to call the transaction logging PL/SQL stored procedure. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. Verify that the transaction logging PL/SQL procedure has been properly installed into the Oracle server under the userid and password specified by PGA_LOG_USER and PGA_LOG_PASS and that it is executable. Refer to the Oracle Server Messages and Codes Manual for information on the Oracle server message.
PGA-20949: unable to define variable string for transaction recovery
Cause: The gateway server was unable to define variable <var> to be used in accessing the transaction log table during recovery processing. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. Refer to the Oracle Server Messages and Codes Manual for information on the Oracle server message.
PGA-20950: unable to perform string on transaction log
Cause: The gateway server was unable to insert, update, or delete a pending transaction row in the transaction log table. An Oracle server message will follow this message.
Action: Ensure that the Oracle server and its TNS listener are both operational. Also check the PGA_LOG_DB, PGA_LOG_USER, and PGA_LOG_PASS parameters in the gateway init file and ensure that they specify the correct database string, userid, and password, respectively. Verify that the transaction logging PL/SQL stored procedure and the transaction log table have been properly installed into the Oracle server under the userid and password specified by PGA_LOG_USER and PGA_LOG_PASS. Refer to the Oracle Server Message and Codes Manual for information on the Oracle server message.
PGA-20960: missing string parameter, required when PGA_CAPABILITY=string
Cause: The PGA_CAPABILITY parameter specified <cap>, but another required parameter, <parm>, was omitted.
Action: Add the missing parameter to the gateway initialization file. Refer to Appendix A, 'Gateway Initialization Parameters', in the Oracle Database Gateway for APPC Installation and Configuration Guide for information on required parameters.
PGA-20961: synclevel 1 conversations not allowed when PGA_CAPABILITY=2_PHASE
Cause: A conversation was requested at synclevel 1. The gateway init file specified PGA_CAPABILITY=2_PHASE. When 2-phase commit is enabled, synclevel 1 conversations are not supported, since they are not protected by 2-phase processing.
Action: Either use synclevel 2 for the conversation (if the remote transaction program supports it) or use a different gateway SID for this conversation.
PGA-20962: synclevel 2 conversations not currently allowed
Cause: A conversation was requested at synclevel 2, but the SNA software allocated the conversation at synclevel 0 or 1. This means that the SNA software is not configured to support synclevel 2, or has no RRM enabled.
Action: Correct the SNA software configuration to support synclevel 2 and to enable RRN processing.
PGA-20963: side profile string specifies the wrong local LU name (string)
Cause: The Side Information profile <profile> specified for this conversation has a local LU name <lu> that is different from the local LU name specified by the PGA_LOCAL_LU gateway initialization parameter.
Action: This message will be accompanied by message PGA-20984, which provides the local LU name that was specified by the PGA_LOCAL_LU gateway initialization parameter. The Side Information profile must be changed to use the same local LU name.
PGA-20964: local LU name specified by PGA_LOCAL_LU is string
Cause: Message PGA-20963 was issued. This message always follows.
Action: See message PGA-20963.
PGA-20965: syncpoint error: expecting string PS header, received string
Cause: During the processing of a 2-phase commit, an incorrect response was received from the remote transaction program following a syncpoint control command. The response received was <rcv> and not a <pstype> PS header as expected.
Action: This is an error in the remote transaction program or the remote OLTP. Check the remote system for error messages from the OLTP. Contact the system administrator for the remote system to assist in problem determination.
PGA-20966: syncpoint error: sent string, expecting string, received string
Cause: During the processing of a 2-phase commit, an incorrect response <resp> was received from the remote transaction program following a syncpoint control command <psh>. The expected response was <exp>.
Action: This is an error in the remote transaction program or the remote OLTP. Check the remote system for error messages from the OLTP. Contact the system administrator for the remote system to assist in problem determination.
PGA-20967: 2-phase commit recovery attempted, DBA action required
Cause: The recovery process of the Oracle integrating server has connected to the gateway to perform recovery. However, the gateway cannot perform automatic recovery for this transaction due to unknown heuristic action taken by the target OLTP.
Action: The DBA must attempt to manually resolve the in-doubt transaction. Detailed information on how to proceed is contained in Chapter 8 of the Oracle Database Gateway for APPC Installation and Configuration Guide, in the section titled "Manual Recovery of In-Doubt Transactions".
PGA-20995: communication error: 'string' failed, rc = number, errno = number
Cause: An unexpected communications error occurred while executing the AIX SNA Server API <func> function. The function return code is <rc> and the system error number is <errno>. The AIX SNA Server LU6.2 API function return codes and system error numbers are described in the vendor documentation. The SNA system error numbers can also be found in the /usr/include/luxsna.h header file on AIX systems.
Action: Determine the cause of the communications error, correct it, and rerun the transaction. If you need assistance, contact your system adminstrator.
PGA-20999: SIGDANGER received from system - all conversations deallocated
Cause: The system sent a SIGDANGER signal to the server, indicating that there is a shortage of paging space. All currently active conversations are deallocated abnormally.
Action: Contact your system administrator.
PGA-21001: internal error: string
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 Worldwide Support for assistance.
PGA-21002: unable to obtain number bytes of memory for string
Cause: Memory shortage in the gateway RRM process. A request failed to allocate <bytes> of memory for the <usage> area.
Action: Ensure 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 your system has enough available memory to support the RRM.
PGA-21004: invalid string 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 'string'
Cause: There was no message file available for the language <lang> specified by the NLS_LANG environment variable.
Action: Refer to Appendix J, National Language Support, for a list of message file languages supported by the RRM. If the language required is supported, 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 (number), valid range is number:number
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 (number), valid range is number:number
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 'string'
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 upper-case alphabetic character or one of the national characters $, #, or @. Subsequent characters can be upper-case 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 'string'
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 upper-case alphabetic character or one of the national characters $, #, or @. Subsequent characters can be upper-case 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 string
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 string
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 may have terminated without cleaning up. On AIX systems, the /tmp/o/e<luname> file may still exist. This will prevent a new RRM from being started. If you have verified that the original RRM is no longer running, 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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support for assistance.
PGA-21023: error opening init file string
Cause: An error occurred opening the init file <ifn>.
Action: This message will be 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 string
Cause: An error occurred reading the init file <ifn>.
Action: This message will be 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 string
Cause: An error occurred opening the init file <ifn>.
Action: This message will be 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 number
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 string value (number) not within valid range (number:number)
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 stringstring
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 will then be processed. This error is received only when the init file contains a very large number of invalid lines.
PGA-21035: value of string (number) not within valid range (number:number)
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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support for assistance.
PGA-21043: error opening log file string
Cause: An error occurred opening the log file <lfn>.
Action: This message will be 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 string
Cause: An error occurred writing to the log file <lfn>.
Action: This message will be 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 string
Cause: An error occurred closing the log file <lfn>.
Action: This message will be 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 cause d the error on the log file, so that the next restart of the RRM will be 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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support 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, supported customers should contact Oracle Worldwide Support for assistance.
PGA-21053: error opening trace file string
Cause: An error occurred opening the trace file <tfn>.
Action: This message will be 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 string
Cause: An error occurred writing to the trace file <tfn>.
Action: This message will be 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 string
Cause: An error occurred closing the trace file <tfn>.
Action: This message will be 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 cause d the error on the trace file, so that the next restart of the RRM will be able to write to the trace file. A common cause for this message is unavailable disk space for the file.
PGA-21060: system errno = number
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 file error and correct it.
PGA-21100: RRM initializing for local LU string
Cause: The RRM is initializing for the local LU <llu>.
Action: Informational message.
PGA-21101: initialization parameters read from string
Cause: Init parameters were read from the file <ifn>.
Action: Informational message.
PGA-21102: log messages written to string
Cause: Log messages will be written to the file <lfn>.
Action: Informational message.
PGA-21103: trace information written to string
Cause: Trace information will be written to the file <tfn>.
Action: Informational message.
PGA-21104: trace level currently set to number
Cause: The trace level specified by the TRACE_LEVEL parameter is <trc>.
Action: Informational message.
PGA-21105: startup for local LU string is warm
Cause: The RRM is warm-starting for the local LU <llu>. The RRM will attempt 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 string
Cause: The RRM has warm-started 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 string is cold
Cause: The RRM is cold-starting for the local LU <llu>. The RRM will not retain any LU6.2 log states from the previous execution.
Action: Informational message.
PGA-21108: cold start complete for local LU string
Cause: The RRM has cold-started 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'string'
Cause: The local LU's LU6.2 log name is <llog>. Since 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 string
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 since either the local RRM or the partner RRM was last started.
Action: Informational message.
PGA-21111: partner log name is x'string'
Cause: The partner LU's LU6.2 log name is <plog>. Since 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 string
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 since the last cold start of the local RRM.
Action: Informational message.
PGA-21113: warm starting for partner LU string
Cause: The RRM is warm starting for the partner LU <plu>. This happens when the partner LU's RRM is warm starting and is contacting the local RRM for the first time since the local RRM was started.
Action: Informational message.
PGA-21114: cold starting for partner LU string
Cause: The RRM is cold starting for the partner LU <plu>. This happens when the partner LU's RRM is cold starting and is contacting the local RRM for the first time since 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 string
Cause: The RRM has terminated for the local LU <llu>.
Action: Informational message.
PGA-21200: connect to Oracle Server as string 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 will follow 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, userid, and password, respectively.
PGA-21201: error selecting PGA_2PC_LUS row for local LU string
Cause: The RRM was unable to read its local LU6.2 log entry. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21202: error updating PGA_2PC_LUS row for local LU string
Cause: The RRM was unable to update its local LU6.2 log entry during warm start processing. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21203: error inserting PGA_2PC_LUS rows for local LU string
Cause: The RRM was unable to create its local LU6.2 log entry during cold start processing. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started again.
PGA-21204: error deleting PGA_2PC_PENDING rows for local LU string
Cause: The RRM was unable to delete the pending transaction entries from its local LU6.2 log during cold start processing. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started 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 cold start processing. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started again.
PGA-21206: error selecting PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to read its local LU6.2 log entry for the partner LU. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21207: error inserting PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to create a local LU6.2 log entry for the partner LU. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21208: error updating PGA_2PC_LUS row for partner LU string
Cause: The RRM was unable to update its local LU6.2 log entry for the partner LU. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21209: error selecting PGA_2PC_PENDING rows for partner LU string
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 will follow 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, it may need to be reinitialized and the RRM cold started.
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. Once 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. Once the problem has been corrected, restart the RRM.
PGA-21212: incorrect data received from partner LU string
Cause: A partner LU has sent incorrect data in its initial communication with the local RRM. The first data received should be 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'string'
Cause: This message follows message PGA-00208, 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, 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 cold started and later warm started, all between the times the local LU's RRM was last shut down and warm started. The local LU's RRM is not aware that the partner LU was cold started, 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 so, 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 12, "2-Phase Commit".
PGA-21216: last stored log name x'string'
Cause: This message always follows message PGA-00213, and lists the last partner LU LU6.2 log name <plog> saved by the local LU's RRM.
Action: The log name in the message may 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'string'
Cause: This message always follows message PGA-00214, and lists the LU6.2 log name <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 may 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 string rejected, number pending transactions exist
Cause: A cold start 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 cold start request will be 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 cold start request will be accepted.
PGA-21219: recovery action by DBA required for local LU string
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 should 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 in this appendix provide the DBA with a course of action. For further information on recovery, refer to "RRM Recovery" in Chapter 8, "Implementing Two-Phase Commit", of the Oracle Database Gateway for APPC Installation and Configuration Guide.
PGA-21220: logging error limit (number) exceeded, RRM shutting down for LU string
Cause: The limit of <lim> Oracle errors while accessing the RRM's local LU6.2 log tables has exceeded. The RRM for the local LU <llu> is shutting down.
Action: The DBA should examine the RRM log file to determine what action to take. The messages in the log file will show what Oracle errors have occurred, and the DBA should take whatever corrective action is required.
PGA-21221: commit failed during cold start of local LU string
Cause: The RRM was unable to commit updates to its local log during a cold start of local LU <llu>. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21222: commit failed during warm start of local LU string
Cause: The RRM was unable to commit updates to its local log during a warm start of local LU <llu>. An Oracle server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21223: commit failed during first-time processing for partner LU string
Cause: The RRM was unable to commit updates to its local log during a first-time processing for partner LU <plu>. An Oracle Server message will follow 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, it may need to be reinitialized and the RRM cold started.
PGA-21224: commit failed during cold start of partner LU string
Cause: The RRM was unable to commit updates to its local log during a cold start of partner LU <plu>. An Oracle Server message will follow 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, it may need to be reinitialized and the RRM cold started.
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 may 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: string
Cause: The RRM received an invalid control flag <control> from a partner RRM.
Action: This error indicates that there may 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 string, fopen errno = number
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 string, fputs errno = number
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 string, fclose errno = number
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 string, remove errno = number
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: 'string' failed, errno = number
Cause: The AIX SNA function <func> failed with a system error number of <errno>.
Action: The AIX SNA error codes are documented in the IBM manual AIX SNA Server: Diagnosis Guide and Messages. Use this manual to determine the cause of the problem and correct it. AIX SNA system error numbers are also documented in the /usr/include/luxsna.h header file on AIX systems.
PGA-21451: SNA Server is shutting down
Cause: SNA Server is being shut down and sent a SIGUSR1 to the RRM.
Action: The RRM must terminate when this occurs. Contact the system administrator to determine the cause of the SNA Server shutdown. Restart the RRM after SNA Server has been restarted.
PGA-22001: remote host name is null.
Cause: TCP/IP protocol has returned "null" for the remote host name.
Action: Verify the remote host name via the pg4tcpmap tool and re-execute your PL/SQL statement. If the problem cannot be resolved, supported customers should contact Oracle Support Services.
PGA-22002: communication error: TCP/IP string failed, rc = number
Cause: The function <func> has failed with the return code of <rc>.
Action: If the problem cannot be resolved, the supported customers should contant Oracle Support Servics for assistance.
PGA-22003: communication error: TCP/IP string failed, rc = number, for, string
Cause: An unexpected communications error occurred while executing the specified TCP/IP function <func>. The TCP/IP function return code is <rc> and the function <func> parameter is <parm>.
Action: If the problem cannot be resolved, the supported customers should contant Oracle Support Servics for assistance.
PGA-22004: length of the total message value (number) not within valid range (number:number)
Cause: The length <len> for the value is not within the valid range <min>:<max>.
Action: If the problem cannot be resolved, the supported customers should contant Oracle Support Servics for assistance.
PGA-22005: invalid socket file descriptor: no active conversations were found
Cause: There were no TCP/IP conversations active for the user.
Action: Check that the application is not calling the PL/SQL TIP routines out of sequence.
PGA-22006: Parameter string is not specified.
Cause: Parameter <parm> is missing from the gateway initialization file.
Action: Add the missing parameter to the gateway initialization file. Refer to the Oracle Database Gateway Installation and Configuration Guide for the required initialization parameters for gateways using TCP/IP.
PGA-22007: user ID string length of number is invalid; maximum length is number
Cause: The user id <uid> is too long <len> to be used. The maximum allowable length for the user ID is <max> characters.
Action: The user id must be changed to a shorter value for OCI logon to the table PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.
PGA-22008: password length of number is invalid; maximum length is number
Cause: The password is too long <len> to be used. The maximum allowable length for the password is <max> characters.
Action: The password must be changed to a shorter value for OCI logon to the table PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.
PGA-22009: database name string length of number is invalid; maximum length is number
Cause: The database name <db name> is too long <len> to be used. The maximum allowable length for the database name is <max> characters.
Action: The database name must be changed to a shorter value for OCI logon to the table PGA_TCP_IMSC. Refer to the Oracle Database Gateway Installation and Configuration Guide for the required gateway initialization parameters for gateways using TCP/IP.
PGA-22010: userid string length of number is invalid; maximum length is number
Cause: The userid <uid> is too long (<len>) to be used with TCP/IP RACF conversation security. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to either SAME or PROGRAM.
Action: The userid must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. The maximum allowable length for the userid is <max> characters. This restriction is imposed by RACF, not by the gateway.
PGA-22011: password length of number is invalid; maximum length is number
Cause: The password is too long (<len>) to be used with TCP/IP RACF conversation security. This can occur only when the gateway initialization parameter PGA_SECURITY_TYPE is set to PROGRAM.
Action: The password must be changed to a shorter value on both the client system and the system where the remote transaction program is being executed. The maximum allowable length for the password is <max> characters. This restriction is imposed by RACF, not by the gateway.
PGA-22012: IMS Connect error: return code = string, reason code = string
Cause: An unexpected IMS Connect error occurred while executing the 'recv' function. The return code <rc> and reason code <rsc> are provided in the message text. For more information, look at the OLTP SDSF log and IMS Connect error message which starts with HWS. The messages are documented in the IBM IMS Connect Guide and Refrence manual.
Action: Determine the cause of the error, correct it, and rerun the transaction.
PGA-22014: Transaction code length of number exceeds the maximum of number
Cause: The transaction code length <len> passed to PGAINIT or PGAINIT_SEC was larger than the maximum allowed length <max>.
Action: Check that the PGDL and COBOL record descriptions used to define the transaction to PGAU are in sync with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions. If modifications have been made to the generated PL/SQL code, check that they are correct.