OBIEE 11g: After Changing Call Interface to ODBC 3.5, Records with Japanese Characters Can Not Be Inserted into S_NQ_ACCT Completely
Last updated on APRIL 20, 2017
Applies to:Business Intelligence Server Enterprise Edition - Version 188.8.131.52.0 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, which described in <Note 1595783.1>.
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].
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms