This chapter describes the post-upgrade tasks that are required for some upgrade scenarios.
This chapter includes the following sections:
After upgrading to 12c (12.1.3), you must deploy and configure the Oracle GoldenGate Veridata Agent at a non-Oracle Home location. For more information, see "Deploying and Configuring Oracle GoldenGate Veridata Agent" in Installing and Configuring Oracle GoldenGate Veridata.
To configure SSL communication between the Veridata Agent and the Server, set the SSL properties for the agent and follow the procedure as described in "Configuring Oracle GoldenGate Veridata Security" chapter in Administering Oracle GoldenGate Veridata.
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:
SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM schema_version_registry where MRC_NAME='Prefix Specified in RCU';
Example 3-1 Sample output of the query on Oracle database
SQL> SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM schema_version_registry where MRC_NAME='DEV100';
| COMP_ID | COMP_NAME | MRC_NAME | OWNER | VERSION | STATUS | UPGRADED |
|---|---|---|---|---|---|---|
|
IAU |
Audit Service |
DEV100 |
DEV100_IAU |
12.1.3.0.0 |
VALID |
N |
|
IAU_APPEND |
Audit Service Append |
DEV100 |
DEV100_IAU_APPEND |
12.1.3.0.0 |
VALID |
N |
|
IAU_VIEWER |
Audit Service Viewer |
DEV100 |
DEV100_IAU_VIEWER |
12.1.3.0.0 |
VALID |
N |
|
OPSS |
Oracle Platform Security Services |
DEV100 |
DEV100_OPSS |
12.1.3.0.0 |
VALID |
N |
|
STB |
Service Table |
DEV100 |
DEV100_STB |
12.1.3.0.0 |
VALID |
N |
|
VERIDATA |
Veridata Repository |
DEV100 |
VERIDATAONE |
12.1.3.0.0 |
VALID |
Y |
SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM DB_NAME.schema_version_registry where MRC_NAME='Prefix Specified in RCU';
DB_NAME is the name of the database you specified while running the RCU.
Example 3-2 Sample output of the query on MySQL database
SELECT COMP_ID,COMP_NAME,MRC_NAME,OWNER,VERSION,STATUS,UPGRADED FROM veridata_test.schema_version_registry where MRC_NAME='DEV';
| COMP_ID | COMP_NAME | MRC_NAME | OWNER | VERSION | STATUS | UPGRADED |
|---|---|---|---|---|---|---|
|
STB |
Service Table |
DEV |
DEV_STB |
12.1.3.0.0 |
VALID |
N |
|
VERIDATA |
Veridata Repository |
DEV100 |
VERIDATAONE |
12.1.3.0.0 |
VALID |
Y |
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.
Example 3-3 Sample output of the query on SQL Server database
SELECT COMP_ID, comp_name, mrc_name, owner, version, status, upgraded FROM veridata12.dbo.schema_version_registry where mrc_name='DEV';
| COMP_ID | COMP_NAME | MRC_NAME | OWNER | VERSION | STATUS | UPGRADED |
|---|---|---|---|---|---|---|
|
STB |
Service Table |
DEV |
DEV_STB |
12.1.3.0.0 |
VALID |
N |
|
VERIDATA |
Veridata Repository |
DEV100 |
VERIDATAONE |
12.1.3.0.0 |
VALID |
Y |
After upgrading to Oracle GoldenGate Veridata 12c (12.1.3), 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/veridata directory. If any of the default values were changed in the 11g 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.
After upgrading to Oracle GoldenGate Veridata 12c (12.1.3), the Veridata 11g users cannot login to the Veridata application. You must create Veridata users and assign privileges by using the Oracle WebLogic Administration Console.
For more information, see "Securing Access to Oracle GoldenGate Veridata by Defining User Roles" in Administering Oracle GoldenGate Veridata.
The Veridata report file location is defined by the server.veridata_data property in the veridata.cfg file. In 12c (12.1.3), the default location is VERIDATA_DOMAIN_HOME/veridata/reports. For more information about the server.veridata_data property see "Server Parameters" section in Administering Oracle GoldenGate Veridata.
Before upgrading to 12c, if the report files were stored in the default report file location of the Veridata 11g installation (shared/data directory), the default location will be updated as VERIDATA_DOMAIN_HOME/veridata/reports after upgrade.
If you have specified another location for the report files in the Veridata 11g installation then the same location will be used in Veridata 12c after upgrade. To access the old report files after upgrade, you should retain the directory structure of the report files.
Note that the report location of 11g reports are not updated after upgrade.
If the upgrade process fails, you must close the Upgrade Assistant, correct the issue, and then restart the Upgrade Assistant.
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 Upgrading with the Upgrade Assistant.