ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Oracle Default schema cannot be specified with Analytics


Article ID: 84427


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :

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.



Cause type:
Root Cause: Enhancement - Added a new configuration property to the analytics backend to specify an initial SQL script.


OS Version: N/A


Update to a fix version listed below or a newer version if available.

A new configuration property was added to the analytics backend 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: 
    This will set the schema to "uc4" while still using the configured db username and password. 

    Enable the following setting in the