Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 214 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
BIEE 12.2.1.4.0 JDBC (jndi) error when execute Scripts on Connection

Dear Specialists
I will describe the case:
Current scenario
Datasource's; Oracle with VPD and Vertica with VPD.
BIEE 12 with Connection Pool using OCI.
Script on connect defines sessions that are the parameter for data security / governance.
The two blocks of code currently look like this:
call dbms_session.set_identifier ('VALUEOF (NQ_SESSION.USER)')
call dbms_application_info.set_module ('OBIEE', NULL);
Problem with the current scenario;
OCI is limited to result set at 2 gb (Due to the huge amount of data required by several users (dozens daily), I get the error fseekfails).
So I want to switch to JDBC (jndi) - (like oac cloud product.).
Desired Scenario
Datasource's; Oracle with VPD and Vertica with VPD.
BIEE 12 with Connection Pool using OCI.
Script on connect defines sessions that are the parameter for data security / governance.
The two code blocks look like this:
call dbms_session.set_identifier ('VALUEOF (NQ_SESSION.USER)')
call dbms_application_info.set_module ('OBIEE', NULL);
The problem:
These scripts are not supported on the jdbc (jndi) connection type.
I suspect the implementation is of the jdbc type on_execute_query method and not on_execute_command.
Therefore, JDBC requires a return of the type resulting from a query.
The error generated is as follows:
[JDSError: 77] SQL string is not Query - Cause: SQLException is thrown from the datasource Action.
Orcl support suggest I using this note solution;
"
SOLUTION
Enclosing commands in BEGIN ... ... ... END;
Change the syntax as below and the report query executes with out any issues.
BEGIN fnd_global.apps_initialize (1034, 50469,800); END;
"
But this solution does not work for my two databases.
Thank You for any sugestions.
Michel.