Oracle Procedural Gateway® for APPC Messages Guide 10g Release 2 (10.2) for UNIX and Microsoft Windows Part Number B16213-01 |
|
|
View PDF |
This chapter lists the TIP
exceptions issued by the PGAU
-generated TIP
s and provides a possible cause and the recommended action for you to take for each message.
This chapter contains the following section:
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.TIP
data lengths for the, cname pname
, send parameter did not correspond. One of the indicated lengths, elen
or clen
, is incorrect.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.cname pname
, did not correspond. One of the indicated lengths, elen
, rlen
, or clen
, is incorrect.rc
, occurred on a DBMS_PIPE
send call. The call was made because TIP tracing was enabled. If the value of rc
equals to 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.rtrace.sql
procedure is run often enough to keep the TIP trace pipe from filling and that the server output size is sufficient to hold the trace stream between rtrace calls.
See Also:
For more information, refer to Chapter 6, "Problem Determination," in Oracle Procedural Gateway for APPC User's Guide. Supported customers can contact Oracle Support Services for assistance.tranuse
value passed to a TIP
function was of the type that is used for unshared TIP
conversations that are associated with TIP
s generated prior to release 3.4.0. This happens when a pre-3.4.0 version of a TIP is used to initiate a conversation, and its tranuse value is subsequently passed to a post-3.4.0 TIP
to use both TIP
s in a shared conversation.TIP
to cause it to pick up a new function that supports the TIP conversation sharing feature. Do not initiate the conversation with (or otherwise use) the old TIP
with the new TIP
. Do not call the new TIP
for the active conversation. Pre-3.4.0 TIP
s cannot be used with post-3.4.0 TIP
s for shared conversations.