Cant unpack BLOB data

Hello All,

We are getting error cant unpack BLOB data. When Interaction server is sending eventRouteRequest to URS. In order to solve this, We are looking for option of using ODBC connection between IXN server and Interaction DB. Below is the steps we had followed for creating ODBC connection.

Created a System DSN through ODBC manager 64 bit. Test connection is succefull.
created a DAP without any DB server. Option [settings] dbprotcol=odbc. Server info holds DBhost and port 1525.
DAp is added into inetraction server connection.

We are able to connect to inetraction DB using ODBC connection when interaction server starts. And log starts with no error.
But while we are testing ODBC connection. When Interaction server sends EventROuteRequest to URS. Email Header is never passed to URS. We do not see any BLOB data issue. But WHole Email Header details are missing in URS, Below is the example of header data which is never sent to URS. We have opened a case with Genesys, But if somebody has already faced issue of Email Header not passing to URS while ODBC connection Please help!! or how Can’t unpack BLOB data issue was resolved for interaction server.

AttributeTimeinSecs 1495812994 (11:36:34)
AttributeExtensions [38] 00 01 00 00..
‘STRATEGY_ID’ ‘tfs_email_preprocess’
AttributeUserData [2400] 00 38 00 00..
‘FromPersonal’ ‘Roy, Rajnish K.’
‘_AttachmentsInfo’(list) ‘[email removed]9B4F0’(list) ‘documentId’ ‘00058aCJGDMD001H’
‘LastCalledAgent_EmployeeID’ ‘107422’
‘_AutoReplyCount’ 0
‘Header_MIME-Version’ ‘1.0’
‘Header_Date’ ‘Fri, 26 May 2017 08:35:56 -0700’
‘Header_X-MS-Exchange-Organization-Network-Message-Id’ ‘a201cb60-b478-432f-862f-08d4a44ce6e9’
‘Header_X-Microsoft-Exchange-Diagnostics’ ‘1;BY1PR0701MB1335;27:w/hp3js5yGsG6hU5ZaIaT/xrODCx8wDRodvJp51AFUq76YMbBirMU3ERXUBEgQ8P29/pr77QE+N4lPBcv8B2knC+NuGNoTEtA+Tcz2YDD4HJGC68Q2vjzmXVEwGD7TXIaFEO9bT6koBDRsXrhAdMtQ==’
‘ContactId’ ‘0004TaBW5MP3001E’
‘Header_Thread-Index’ ‘AdLWNcITcZXx0YRUQSSO74dEG+HedQ==’
‘FromAddress’ ‘[email removed]’
‘_AttachmentsSize’ ‘36326’
‘Header_Content-Language’ ‘en-US’
‘Mailbox’ ‘[email removed]’
‘LCA_EmplID_email’ ‘107422’
‘LCA_TimeStamp_chat’ ‘2017-03-21T10:15:55Z’
‘Header_X-MS-Exchange-Organization-AuthMechanism’ ‘04’
‘Header_X-MS-Has-Attach’ ‘yes’
‘Header_X-MS-Exchange-Organization-AuthSource’ ‘MWHPR07MB2862.namprd07.prod.outlook.com’
‘To’ ‘USCBD DefaultQueue <[email removed]>’
‘Header_Accept-Language’ ‘en-US’
‘Header_Message-ID’ ‘<[email removed]>’
‘Header_X-MS-Exchange-Organization-SCL’ ‘-1’
‘_AttachmentFileNames’ ‘image001.jpg’
‘FirstName’ ‘Rajnish K.’
‘Origination_Source’ ‘Email’
‘Header_x-ms-publictraffictype’ ‘Email’
‘_ContainsAttachment’ ‘true’
‘Header_X-MS-TNEF-Correlator’ ‘’
‘LastCalledAgent_TimeStamp’ ‘2017-05-26T14:21:24Z’
‘LCA_TimeStamp_email’ ‘2017-05-26T14:21:24Z’
‘EmailAddress’ ‘[email removed]’
‘Subject’ ‘9513276470 test’
‘LCA_EmplID_chat’ ‘107422’
‘Header_X-MS-Exchange-Organization-AuthAs’ ‘Internal’
‘Header_Thread-Topic’ ‘9513276470 test’
‘Header_Content-Type’ ‘multipart/related; boundary=“002_MWHPR07MB2862DE68E989C3762034FB4390FC0MWHPR07MB2862namp”; type=“text/html”’

Thanks,
Rajnish

From where did you get that ODBC is supported? Why you decided for this configuration?

Genesys recomended to use ODBC connection, As this is known issue with DBServer 8.1.XX and Oracle 10g (Cant Unpack BLOB data).

Now What i think is Column (Flexible properties) is type long raw, in oracle 10g. and ODBC connection does not support type=Long RAW, That is why we are facing this issue(It is my thinking and i might be 100% wrong )

Please suggest what should we do.

Thanks,
Rajnish

Request your suggestion, If you have faced such kind of issue.

Thanks,
Rajnish

Hi,

Got exactly that error some time agao.

You need to add LOB=T in the connection strin on the ODBC source as below:

Driver={Oracle in instantclient_11_2};Dbq=ORACLENAME.world;LOB=T

Unfortunately, the data truncation occurs when BLOB is being written to the database (when LOB=T is not specified). If some “broken” records were written to the database, the server can’t read them back even if LOB=T is specified.

So interactions written to InteractionServer database before the LOB=T addition will generate this error. But new ones will work.

Good Luck!

Hello Catanirex,

Was you DB 10g or 11g or later?

Our DB is 10g, And i think that is creating issue. I have given a try using LOB=T in connection string.. But It does not help.

Thanks,
Rajnish

We used 11G.

I have no idea if LOB=T can be used on 10.

But as I wrote - all records written into db WITHOUT LOB=T will fail even when LOB=T, so those records must be handled other way. Only records written when LOB=T will work.

I hope you find a solution! Good Luck!