Oracle Default schema cannot be specified with Analytics

Document ID : KB000084427
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
N/A

There is currently no way to specify a default schema when using Analytics with an Oracle database. Analytics and Oracle is currently only possible with a read only user.
 


 
Environment:
OS Version: N/A
Cause:
Cause type:
Other
Root Cause: Enhancement - Added a new configuration property to the analytics backend application.properties to specify an initial SQL script.
Resolution:
Update to a fix version listed below or a newer version if available.

A new configuration property was added to the analytics backend application.properties to specify an initial SQL script. 

This enhancement was added with the following releases:
Analytics.On.Premise 1.0.1 is the equivalent to AWA release 12.0.2
Analytics.On.Premise 1.1.0 is the equivalent to AWA release 12.1.0
 
Please note that this package is part of the complete image of the AWA download which can be found on our download center.
 


Fix Status: Released

Fix Version(s):
Analytics On Premise 1.1.0 – Available
Analytics On Premise 1.0.1 - Available
Additional Information:
Workaround :
The following steps are recommended to alleviate the issue.

    When using a read-only user for Oracle, the schema must be specified. 
    Create a text file in the analytics backend folder (next to the analytics-backend.jar) 

 
    Example: ae_schema.sql with the following content: 
    ALTER SESSION SET CURRENT_SCHEMA=uc4 
 
    This will set the schema to "uc4" while still using the configured db username and password. 

    Enable the following setting in the application.properties: datasource.ae.schema=file:ae_schema.sql.