1 TIP Exceptions
This chapter lists the TIP exceptions issued by the PGAU-generated TIPs and provides a possible cause and recommended action for each message.
This chapter contains the following section:
1.1 Messages ORA-20700 to ORA-20704
- ORA-20700 PGA_TIP: repeating group limits exceeded
-
Cause: The repetition count in a repeating group is outside its limits as defined in the PG DD for the group. The actual data being converted and exchanged through the TIP contains a count field with an invalid number.
-
Action: Generate the TIP with data conversion and data exchange tracing as required or rerun the application with tracing enabled. Analyze the resulting TIP and gateway server traces. Supported customers can contact Oracle Support Services for assistance.
- ORA-20701 PGA_TIP: sent data length invalid cname pname, expected elen, converted clen
-
Cause: TIP data lengths for the send parameter cname pname did not correspond. One of the indicated lengths, elen or clen, is incorrect.
-
Action: Generate the TIP with data conversion and data exchange tracing as required or rerun the application with tracing enabled. Analyze the resulting TIP and gateway server traces. Supported customers can contact Oracle Support Services for assistance.
- ORA-20702 PGA_TIP: received data length invalid cname pname, expected elen, received rlen, converted clen
-
Cause: TIP data lengths for the received parameter cname pname did not correspond. One of the indicated lengths, elen, rlen, or clen, is incorrect.
-
Action: Generate the TIP with data conversion and data exchange tracing as required or rerun the application with tracing enabled. Analyze the resulting TIP and gateway server traces. Supported customers can contact Oracle Support Services for assistance.
- ORA-20703 PGA_TIP: pipe send error, rc = rc
-
Cause: The indicated error, rc, occurred on a DBMS_PIPE send call. The call was done because TIP tracing was enabled. If rc=1, then the 60 second pipe wait time elapsed. This is usually because the TIP trace pipe has overflowed at the inlet due to the trace message inflow exceeding 16K.
-
Action: Ensure that the rtrace.sql procedure is run often enough to keep the pipe from filling and that the server output size is sufficient to hold the trace stream between rtrace calls. For more information, refer to Chapter 6, "Problem Determination," in your Oracle Procedural Gateway for APPC User's Guide. Supported customers can contact Oracle Support Services for assistance.
- ORA-20704 PGA_TIP: tranuse value can not be shared
-
Cause: The tranuse value passed to a TIP function is of the type used for unshared TIP conversations associated with TIPs generated prior to release 3.4.0. This can happen when a pre-3.4.0 version of a TIP was used to initiate a conversation and its tranuse value was subsequently passed to a post-3.4.0 TIP in an attempt to use both TIPs in a shared conversation.
-
Action: Regenerate the pre-3.4.0 TIP to cause it to pick up a new function that supports the TIP conversation sharing feature, or do not initiate the conversation with (or otherwise use) the old TIP with the new TIP, or do not call the new TIP for the active conversation. Pre-3.4.0 TIPs cannot be used with post-3.4.0 TIPs for shared conversations.
