My Oracle Support Banner

OBIEE 11g: After Changing Call Interface to ODBC 3.5, Records with Japanese Characters Can Not Be Inserted into S_NQ_ACCT Completely (Doc ID 2229168.1)

Last updated on NOVEMBER 04, 2019

Applies to:

Business Intelligence Server Enterprise Edition - Version and later
Information in this document applies to any platform.


You face the issue that in queries with large text are not getting captured in the S_NQ_ACCT table.

According to the development team suggestion, you changed Call interface from [OCI 10g/11g] to [ODBC 3.5].
However after that, SAW_DASHBOARD, SAW_DASHBOARD_PG value in S_NQ_ACCT is not fully inserted (at the end of the path some texts are cut off) when the dashboard/page path includes Japanese.

And when you run the Answer with column SAW_DASHBOARD, SAW_DASHBOARD_PG, the result is GARBLED.


You changed call interface of Connection Pool from [OCI 10g/11g] to [ODBC 3.5]. 


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.