Linux/UNIX:
If '-a' (apply on staging flag) is passed, it connects to the database as staging schema admin and performs the conversion setup, in addition to creation of the above files, by running the same SQLs present in the create* SQL files.
On-premises:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d ${JDBC_CONN_STRING} -p ${CIS_ADMIN_USR},${CIS_ADMIN_PSWD} -a -s ${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
ADB:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -p ${CIS_ADMIN_USR},${CIS_ADMIN_PSWD} -a -s
${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
If '-r' (revert staging flag) is passed, it connects to the database as staging schema admin and reverts the staging to a state prior to conversion setup, running the same SQLs present in drop_* or restore_* SQL files.
On-premises:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d ${JDBC_CONN_STRING} -p ${CIS_ADMIN_USR},${CIS_ADMIN_PSWD} -r -s ${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
ADB:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -r -s
${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
To generate ONLY the scripts, the program should be invoked with '-s' parameter with no other flags (no '-a' or '-r' ):
On-premises:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d ${JDBC_CONN_STRING} -p ${CIS_ADMIN_USR},${CIS_ADMIN_PSWD} -s ${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
ADB:
java com.oracle.ouaf.oem.conversion.ConversionSetup -d
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -s
${STG_ADMIN_USR},${STG_ADMIN_PSWD},${STG_RW_USER}
 
Windows:
If '-a' (apply on staging flag) is passed, it connects to the database as staging schema admin and performs the conversion setup, in addition to creation of the above files, by running the same SQLs present in the create* SQL files.
On-premises:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d %{JDBC_CONN_STRING}% -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -a -s %{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
ADB:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -a -s
%{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
If '-r' (revert staging flag) is passed, it connects to the database as staging schema admin and reverts the staging to a state prior to conversion setup, running the same SQLs present in drop_* or restore_* SQL files.
On-premises:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d %{JDBC_CONN_STRING}% -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -r -s %{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
ADB:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -r -s
%{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
To generate ONLY the scripts, the program should be invoked with '-s' parameter with no other flags (no '-a' or '-r' ):
On-premises:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d %{JDBC_CONN_STRING}% -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -s %{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
ADB:
"%JAVA_HOME%"\bin\java com.oracle.ouaf.oem.conversion.ConversionSetup -d
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -p %{CIS_ADMIN_USR}%,%{CIS_ADMIN_PSWD}% -s
%{STG_ADMIN_USR}%,%{STG_ADMIN_PSWD}%,%{STG_RW_USER}%
 
It creates the following files in current directory (or output directory if passed as '-o') if '-r' (revert staging flag) is not passed.
Filename
Description
mainFile.sql
Contains instructions on the order and how to run the files
create_schgrants.sql
Grant read permissions on production schema objects to staging admin user
create_cxviews.sql
Creates Conversion X views on staging schema
create_ctlviews.sql
Create Production Control views on staging schema
createck_tbls.sql
Creates Conversion Key tables on staging schema
createck_pkix.sql
Creates primary indexes on Conversion key tables
createck_secix.sql
Creates secondary indexes on Conversion key tables
createcr_tbls.sql
Creates XML/CLOB Resolution tables on staging schema
create_stggrants.sql
Grants select, insert permissions on above created staging objects to staging read/write user
restore_ctltbls.sql
Restores Control tables
drop_cxviews.sql
Restored Conversion X views
drop_tables.sql
Restores CK & CR tables
 
After the staging schema has been set up, generate the security for the staging user following the steps in the Configuring Security section.
Linux/UNIX:
• On-premises:
java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec-d
<STAGING_DBUSER>,< STAGING_DBPASS>, jdbc:oracle:thin:@<DB_SERVER>:<PORT>/
<SID> -u <STAGING_RW_USER> -r <STAGING_RW_USER_ROLE>,< STAGING_R_USER_ROLE> -a A -p
<RW_USERPASS>
 
• ADB:
java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec-d
<STAGING_DBUSER>,< STAGING_DBPASS>,
jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -u <STAGING_RW_USER> -r <STAGING_RW_USER_ROLE>,< STAGING_R_USER_ROLE> -a A -p <RW_USERPASS>
 
Windows:
• On-premises:
"%JAVA_HOME%"\bin\java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec -d < STAGING_DBUSER>,< STAGING DBPASS>, jdbc:oracle:thin:@<DB_SERVER>:<PORT>/
<SID> -u < STAGING RW_USER> -r <STAGING RW_USER_ROLE>,<STAGING R_USER_ROLE> -a A -p
<STAGING_RW_USERPASS>
 
• ADB:
"%JAVA_HOME%"\bin\java -Xmx1500M com.oracle.ouaf.oem.install.OraGenSec -d < STAGING_DBUSER>,< STAGING DBPASS>, jdbc:oracle:thin:@<tnsname>?TNS_ADMIN=<wallet location> -u < STAGING RW_USER> -r <STAGING RW_USER_ROLE>,<STAGING R_USER_ROLE> -a A -p <STAGING_RW_USERPASS>