Performing Post-Upgrade Tasks

3 Performing Post-Upgrade Tasks

Perform these tasks to verify your upgrade was successful. This chapter includes the following sections:

3.1 Verifying the Schema Upgrade

To verify that the schema has been upgraded, run the following SQL query on the schema_version_registry table from the database host by an admin or root user:

Oracle:

SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM schema_version_registry where MRC_NAME='Prefix Specified in RCU';

For example:

SQL> SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM schema_version_registry where MRC_NAME='DEV100';

SQL Server:

SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM DB_NAME.dbo.schema_version_registry where MRC_NAME='Prefix Specified in RCU';

DB_NAME is the name of the database you specified while running the RCU.

For example:

SELECT COMP_ID, comp_name, mrc_name, owner, version, status, upgraded FROM veridata12.dbo.schema_version_registry where mrc_name='DEV';

Example 3-1 Sample Output of the Query on All Databases

COMP_ID	COMP_NAME	MRC_NAME	OWNER	VERSION	STATUS	UPGRADED
IAU	Audit Service	DEV100	DEV100_IAU	12.2.1.2.0	VALID	N
IAU_APPEND	Audit Service Append	DEV100	DEV100_IAU_APPEND	12.2.1.2.0	VALID	N
IAU_VIEWER	Audit Service Viewer	DEV100	DEV100_IAU_VIEWER	12.2.1.2.0	VALID	N
OPSS	Oracle Platform Security Services	DEV100	DEV100_OPSS	12.2.1.0.0	VALID	N
STB	Service Table	DEV100	DEV100_STB	12.2.1.3.0	VALID	Y
VERIDATA	Veridata Repository	DEV100	VERIDATAONE	12.2.1.4.0	VALID	Y

3.2 Verifying the Oracle GoldenGate Veridata Configuration Upgrade

After upgrading to Oracle GoldenGate Veridata 12c (12.2.1.4.0), you can verify the following and confirm whether the upgrade was successful:

Verify the configuration properties: After upgrade, the configuration properties are copied to the veridata.cfg file located in the VERIDATA_DOMAIN_HOME/config/veridatadirectory. If any of the default values were changed in the 12.2.1.2.0 installation before upgrade, verify the values are copied to the veridata.cfg file after upgrade.

Note:

The veridata.cfg file contains only the properties which are valid in 12c. Deprecated properties are not copied after upgrade.
Verify the connections: After upgrade, Veridata users can login to the Veridata application and verify the existing connections. If the password fields are not empty and if the Test Connection succeeds, then the upgrade is successful.

3.3 Managing Oracle GoldenGate Veridata Users

After upgrading to Oracle GoldenGate Veridata 12c (12.2.1.4.0), users are managed as follows:

Oracle GoldenGate Veridata 12.2.1.2.0 users for Oracle and SQL Server can be used in Veridata 12.2.1.4.0.

For more information about creating and managing users using the Oracle WebLogic Administration Console, see "Securing Access to Oracle GoldenGate Veridata by Defining User Roles" in Adminstering Oracle GoldenGate Veridata Guide.

3.4 Verifying Veridata Report Files

The Veridata report file location is defined by the server.veridata_data property in the veridata.cfg file. In 12c (12.2.1.4.0), the default location is VERIDATA_DOMAIN_HOME/veridata/reports. For more information about the server.veridata_data property see "Server Parameters" section in Adminstering Oracle GoldenGate Veridata Guide.

If you have specified another location for the report files in the Oracle GoldenGate Veridata 12.2.1.2.0 installation then the same location will be used in the Oracle GoldenGate Veridata 12c (12.2.1.4.0) after upgrade. To access the old report files after upgrade, you should retain the directory structure of the report files.

3.5 Clearing your Browser Cookies

After the Oracle GoldenGate Veridata upgrade to 12.2.1.4.0 is successfully completed, ensure to clear browser cookies before you launch the Oracle GoldenGate Veridata user interface.

3.6 Troubleshooting your Upgrade

If the upgrade process fails, you must close the Upgrade Assistant, correct the issue, and then restart the Upgrade Assistant.

Reviewing Log Files

By default, upgrade log files are created and saved in the ORACLE_HOME/oracle_common/upgrade/logs/ directory. You can review these log files to diagnose problems that might have occurred during the upgrade process.

The log file location is displayed on the console where you run the Upgrade Assistant.

For Veridata schema upgrade, only one log file is created, but when you upgrade Veridata configuration, two log files are created. One is the default log file and the other is an output log file. The output log file is created at the same location but with an .out extension. The file name remains the same

For more troubleshooting information, see "Troubleshooting Your Upgrade" in the Oracle FusionMiddleware Upgrading with the Upgrade Assistant Guide.