Dm_aq Is Failing To Enqueue With Error ORA-06502 When The Payload Has Unicode Characters
(Doc ID 2104624.1)
Last updated on OCTOBER 24, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 7.5.0]
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Webservices Mgr & JCA Adaptor
When implementing DM_AQ to push the collections payload to Oracle AQ, if the payload is having the unicode characters, sometimes the enqueue is failing with error ORA-06502.
After investigating/debugging the PORTAL_SYNC package code, the following are the findings:
- DM is calling the procedure enq_event with the flist length > 4000
- Internally the procedure is calculating the length again and getting the value as < 4000
So, it is trying to add the payload as VARCHAR2 and failing with the error below:
The issue can be reproduced with the following steps:
1. Take a sample unicode message of such a length where,
length in bytes > 4000 chars and
length in char < 4000 chars
2. Insert such a message in AQ using pin_ifw_sync utility
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document