Skip Headers

Oracle® Procedural Gateway for APPC Messages Guide
Release 9.2.0.1.0

Part Number A97320-01
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

2
Procedural Gateway Server Messages

This chapter lists the messages issued by the Oracle Procedural Gateway for APPC server and provides a possible cause and recommended action for each message. In addition to these messages, there are gateway messages, prefixed with GTW, documented in the Oracle Open Gateways Guide for SQL-Based and Procedural Gateways.

This chapter contains the following sections:

Messages PGA-20900 to PGA-20927

PGA-20900 unable to obtain n bytes of storage for description

Cause: Memory shortage in the gateway server process.

Action: Ensure that your system has enough available memory to support the number of concurrent users you are running.

PGA-20901 internal gateway error: [arg1] [,arg2] [,arg3] [,arg4] [,arg5]

Cause: Internal error in the gateway server process.

Action: Reproduce the error with debugging enabled in order to produce a log file. Supported customers should contact Oracle Support Services 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 func processing

Cause: An error occurred processing the specified Oracle function func. This message is preceded by additional messages providing more information about the error.

Action: Refer to the messages preceding this one to determine the course of action.

PGA-20910 communication error: CPI-C func failed, rc = rc, 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.

PGA-20911 update transaction is already active with TP tpname at LU luname

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.

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, then check that they are correct.

PGA-20914 send buffer length of len exceeds actual send buffer size of size

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, then check that they are correct.

PGA-20915 receive buffer length of len exceeds the maximum of max

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, then check that they are correct.

PGA-20916 send count is count but only num 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 you have modified the generated PL/SQL code, check that the modifications are correct.

PGA-20917 receive count is count but only num 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 you have modified the generated PL/SQL code, check that the modifications are correct.

PGA-20918 send length number num is len but only bytes 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, then check that they are correct.

PGA-20919 receive length number num is len but only bytes 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, then 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, then check that they are correct.

PGA-20921 buffer overflow on receive: requested num bytes, received len 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, then check that they are correct.

PGA-20922 no data available to receive: num 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, then check that they are correct.

PGA-20923 unexpected status, stat (desc), received after func

Cause: An unexpected status stat was received from the remote transaction program following the CPI-C func call. The descriptive name of the status code is desc.

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 Procedural Gateway for APPC Installation and Configuration Guide for your platform for titles of SNA software documentation.

PGA-20924 unable to enter send state for normal deallocate, state = state (desc)

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.

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 performs 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 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, then the LU name, TP name and Mode name parameters are all required.

PGA-20926 userid uid length of len is invalid; maximum length is max

Cause: The user id uid is too long (len) to be used with APPC conversation security. This can occur only when the gateway initialization parameter APPC_SECURITY_TYPE is set to either SAME or PROGRAM.

Action: The user id 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 user ID is max characters. This restriction is imposed by SNA and APPC, not by the gateway.

PGA-20927 password length of len is invalid; maximum length is max

Cause: The password is too long (len) to be used with APPC conversation security. This can occur only when the gateway initialization parameter APPC_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 SNA and APPC, not by the gateway.

Messages PGA-20930 to PGA-20999

PGA-20930 invalid SYNCLEVEL, sync, specified; valid range is min:max

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 the 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 len exceeds the maximum of max

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, func, 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 keyword=value

Cause: The keyword parameter keyword=value specifies an invalid value.

Action: Refer to the documentation for the keyword and correct the error.

PGA-20934 side information profile profile 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 sync level sync is not allowed when PGA_CAPABILITY=cap

Cause: The sync level parameter sync passed to PGAINIT was incompatible with the setting of the PGA_CAPABILITY gateway initialization parameter, cap.

Action: If the sync level passed to PGAINIT is correct, then the gateway initialization parameter PGA_CAPABILITY must be changed to allow the desired sync level to be supported. If the sync level is not correct, then the TIP should be changed to specify the correct sync level in the call to PGAINIT. If the TIP was generated by PGAU, then the SYNCLEVEL keyword of the DEFINE TRANSACTION statement should be changed to specify the correct sync level and the TIP should be regenerated. In the following list, each PGA_CAPABILITY value setting is followed by the number of the sync level(s) that are valid for that setting:

  • READ_ONLY or RO: 0

  • SINGLE_SITE or SS: 0, 1

  • COMMIT_CONFIRM or CC: 0,1

  • 2_PHASE or 2P: 0,2

PGA-20936 send buffer length is len 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 synchronized with the transaction program and that the PL/SQL TIP was generated by PGAU using the correct definitions.

PGA-20937 receive buffer length len 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 synchronized 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 (len) 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, then ensure that it was not modified incorrectly. If the TIP was not modified, then supported customers should contact Oracle Support Services for assistance. If the TIP was modified or was not generated by PGAU, then correct the send lengths array passed to PGAXFER.

PGA-20939 receive lengths array too small (len) 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, then ensure that it was not modified incorrectly. If the TIP was not modified, then supported customers should contact Oracle Support Services for assistance. If the TIP was modified or was not generated by PGAU, then 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.

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, user ID and password, respectively. Refer to Oracle9i Server Messages for information on this Oracle server message.

PGA-20947 unable to bind variable var for transaction logging

Cause: The gateway server was unable to bind variable var for use in performing transaction logging functions. An Oracle server message follows 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, user ID and password, respectively. Refer to Oracle9i Server Messages for information on this 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.

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, user ID and password, respectively. Verify that the transaction logging PL/SQL procedure has been properly installed into the Oracle server under the user ID and password specified by PGA_LOG_USER and PGA_LOG_PASS and that it is executable. Refer to Oracle9i Server Messages for information on this Oracle server message.

PGA-20949 unable to define variable var 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.

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, user id and password, respectively. Refer to Oracle9i Server Messages for information on this Oracle server message.

PGA-20950 unable to perform oper on transaction log

Cause: The gateway server was unable to insert, update, or delete a pending transaction row in the transaction log table.

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, user ID 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 user ID and password specified by PGA_LOG_USER and PGA_LOG_PASS. Refer to Oracle9i Server Messages for information on this Oracle server message.

PGA-20960 missing parm parameter, required when PGA_CAPABILITY=cap

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 of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for your platform 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 two-phase commit is enabled, synclevel 1 conversations are not supported, since they are not protected by two-phase processing.

Action: Either use synclevel 2 for the conversation (if the remote transaction program supports it) or use a different gateway SID configured with PGA_CAPABILITY=SINGLE_SITE 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 RRM processing.

PGA-20963 side profile profile specifies the wrong local LU name (lu)

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-20964, 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 lu

Cause: Message PGA-20963 was issued. This message always follows message PGA-20963.

Action: See message PGA-20963.

PGA-20965 syncpoint error: expecting pstype PS header, received rcv

Cause: During the processing of a two-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 psh, expecting exp, received resp

Cause: During the processing of a two-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 integrating Oracle 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 7 of the Oracle Procedural Gateway for APPC Installation and Configuration Guide for AIX, in the section titled "Manual Recovery of In-Doubt Transactions."

PGA-20995 communication error: func failed, rc = rc, 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.

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 de-allocated normally.

Action: Contact your system administrator.


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

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