My Oracle Support Banner

Reporting Schema Is Incorrect in setup_reporting_user.sql Downloaded From "Download Reporting Schema Setup Sql" in Instantis EnterpriseTrack (Doc ID 2328632.1)

Last updated on MARCH 22, 2019

Applies to:

Instantis EnterpriseTrack - Version and later
Instantis EnterpriseTrack Cloud Service - Version 17.2 and later
Information in this document applies to any platform.


The reporting schema is incorrect in the setup_reporting_user.sql file downloaded when clicking "Download Reporting Schema Setup SQL" from Administration>Data Import & Export. The reporting schema name is being derived from the schema used by the etrack application rather than by the name of SiteWand account.

For example: SiteWand using account name "etrack" deployed using database schema "etrack2". When downloading setup_reporting_user.sql, the reporting schema is ET_etrack2_REP instead of ET_etrack_REP.

Example of downloaded SQL:

prompt Enter the password for the reporting schema called 'ET_etrack2_REP'
prompt prompted.  You must remember this password; it will be required
prompt to access the reporting schema.
accept reppassword prompt 'Password for reporting schema: '
create user ET_etrack2_REP identified by "&reppassword" default tablespace
users temporary tablespace temp ;
grant connect, resource to ET_etrack2_REP ;
grant unlimited tablespace to ET_etrack2_REP ;
grant execute on dbms_lob to ET_etrack2_REP ;
alter user ET_etrack2_REP grant connect through etrack2 ;


  1. Install SiteWand using non-default schema user, such as etrack2
  2. SiteWand account name should be "etrack"
  3. Deploy EnterpriseTrack application
  4. Login as sys_admin
  5. Enable "Manage reporting data model" in Feature Settings>Global
  6. Move account to UAT mode
  7. Go to Administration>Data Import & Export
  8. Click "Download Reporting Schema Setup SQL"
  9. Open setup_reporting_user.sql in a text editor
  10. Notice reporting schema is ET_etrack2_REP instead of ET_etrack_REP


The reporting schema user downloaded in setup_reporting_user.sql should match the SiteWand account name, not the db schema name for the application.

See: What Is the Naming Convention for the User Schema Name When Configuring Instantis EnterpriseTrack for BI Publisher Integration? (Doc ID 2275395.1)


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.