Advanced Queuing - Oracle

Messaging Gateway Questions
What transformation exceptions might I see in a Messaging Gateway log
file?
The exception messages logged to the MGW log file often include a linked
exception that provides additional information. If the linked exception is a
java.sql.SQLException, it may include an Oracle error message and possibly
a PL/SQL stack trace.
ORA-25229 is typically thrown by AQ when the transformation function raises a
PL/SQL exception or some other Oracle error occurs when attempting to use the
transformation.
Example 1
Errors occured during processing of subscriber SUB_MQ2AQ_2
oracle.mgw.common.GatewayException: [722] Message transformation failed; queue:
MGWUSER.DESTQ_SIMPLEADT, transform:
MGWUSER.MGW_BASIC_MSG_TO_SIMPLEADT
[…Java stack trace here…]
[Linked-exception]
oracle.mgw.common.MessageException: [722] Message transformation failed; queue:
MGWUSER.DESTQ_SIMPLEADT, transform:
MGWUSER.MGW_BASIC_MSG_TO_SIMPLEADT
[…Java stack trace here…]
[Linked-exception]
java.sql.SQLException: ORA-25229: error on transformation of message msgid:
9749DB80C85B0BD4E03408002086745E
ORA-00604: error occurred at recursive SQL level 1
ORA-00904: invalid column name
[…Java stack trace here…]
Possible causes of transformation exceptions include:
1. The MGW agent user may not have EXECUTE privilege on the transformation
function. It is not sufficient to grant EXECUTE to MGW_AGENT_ROLE and then
grant MGW_AGENT_ROLE to the agent user. EXECUTE privilege on the
transformation function must be granted directly to the agent user or to
PUBLIC.
2. The transformation function may not exist, even though the registered
transformation does. If the transformation function does not exist, it must be
re-created.
3. The MGW agent user may not have EXECUTE privilege on the payload object
type for the queue indicated in the exception. It is not sufficient to grant
EXECUTE to MGW_AGENT_ROLE and then grant MGW_AGENT_ROLE to the agent
6-14 Oracle9i Application Developer’s Guide - Advanced Queuing