Upgrading Oracle GoldenGate Veridata

2 Upgrading Oracle GoldenGate Veridata

Follow step by step procedures to upgrade your system and also upgrade your utilities such as schemas and Veridata agent.

This chapter includes the following sections:

Choosing an Upgrade Path and Upgrading

To upgrade your existing Oracle GoldenGate Veridata release to the Veridata 12c (12.2.1.2.0) release, choose the appropriate upgrade path for your environment and use the steps in that section to proceed with your upgrade:

Upgrading Veridata 11g to Veridata 12.2.1.2.0

The Oracle GoldenGate Veridata 11g release was based on the use of the Apache Tomcat Application Server. Oracle GoldenGate Veridata 12.2.1.2.0 uses Oracle WebLogic Server and is dependent on other Oracle Fusion Middleware products.

Note:

All of your User Preferences will be lost as a result of the upgrade because of the product changes in the Oracle GoldenGate Veridata 12c release.

To upgrade from 11.2.1.0.0 and greater to 12.2.1.2.0, use these steps:

Run the Upgrade Assistant to upgrade your Veridata schema to 12.2.1.2.0 with Upgrading Veridata Schemas.
Run RCU to create OPSS schemas and Service Table (STB) with Creating Repository Schemas using Repository Creation Utility.
Run the Oracle WebLogic Server Configuration Wizard to create a new Veridata domain using the previously upgraded Veridata database and newly created OPSS and STB schemas with Creating the Veridata Domain using the Upgraded Schema.
Run Upgrade Assistant to perform the Veridata configuration upgrade to 12.2.1.2.0, which includes wallet and veridata.cfg migration with Upgrading Your Oracle GoldenGate Veridata Configuration
Start your Veridata WebLogic Server and domain. See Starting the Servers in Installing and Configuring Oracle GoldenGate Veridata.
Run the agent_config utility to upgrade your Veridata Agent with Upgrading the Veridata Agent.
Go to Performing Post-Upgrade Tasks and perform the post-installation tasks.

Upgrading Veridata 12.1.3 Compact Domain to 12.2.1.2.0

The Oracle GoldenGate Veridata 12.1.3 domain with a SQL Server database as repository was a compact domain, which does not use an OPSS schema. The compact domain support was removed in the Oracle GoldenGate Veridata 12.2.1.2.0 release and only Expanded domain is supported.

To upgrade from a compact domain 12.1.3 to Veridata 12.2.1.2.0, use these steps:

Run the Upgrade Assistant to upgrade your Veridata schema and STB to 12.2.1.2.0 with Upgrading Veridata Schemas.
Run RCU to create OPSS schemas using the same prefix that you used in 12.1.3 with Creating Repository Schemas using Repository Creation Utility.
Run the Oracle WebLogic Server Configuration Wizard to create a new Veridata domain using the previously upgraded Veridata and STB databases and newly created OPSS with Creating the Veridata Domain using the Upgraded Schema.
Run Upgrade Assistant to perform the Veridata configuration upgrade to 12.2.1.2.0 including wallet migration and veridata.cfg migration with Upgrading Your Oracle GoldenGate Veridata Configuration
Start your Veridata WebLogic Server and domain. See Starting the Servers in Installing and Configuring Oracle GoldenGate Veridata.
Run the agent_config utility to upgrade your Veridata Agent with Upgrading the Veridata Agent.
Go to Performing Post-Upgrade Tasks perform the post-installation tasks.

Upgrading Veridata 12.1.3 Expanded Domain to Veridata 12.2.1.2.0

To upgrade from a 12.1.3 expanded domain to Veridata 12.2.1.2.0, use these steps:

Run the Upgrade Assistant to upgrade your Veridata, OPSS schema and AUDIT schemas to 12.2.1.2.0 with Upgrading Veridata Schemas or using the Domain Assisted Schema Upgrade (DASU), which is the recommended way to upgrade as mentioned in All Schemas Used by Domain
Run the Oracle WebLogic Server Reconfiguration Wizard to reconfigure your existing 12.1.3 expanded domain to a 12.2.1.2.0 domain with this command.
```
ORACLE_HOME/oracle_common/common/bin/reconfig.sh -log=logFileName.log -log_priority=FINE
```
Run the Upgrade Assistant to upgrade your Veridata configuration to 12.2.1.2.0 with Upgrading Your Oracle GoldenGate Veridata Configuration.
Start your Veridata WebLogic Server and domain. See Starting the Servers in Installing and Configuring Oracle GoldenGate Veridata.
Run the agent_config utility to upgrade your Veridata Agent with Upgrading the Veridata Agent.
Go to Performing Post-Upgrade Tasks.

Upgrading Veridata 12.2.1 Domain to Veridata 12.2.1.2.0

To upgrade from a 12.2.1 domain to Veridata 12.2.1.2.0, use these steps:

Run the Upgrade Assistant to upgrade your Veridata, OPSS schema and AUDIT schemas to 12.2.1.2.0 with Upgrading Veridata Schemas or using the Domain Assisted Schema Upgrade (DASU), which is the recommended way to upgrade as mentioned in All Schemas Used by Domain
Run the Oracle WebLogic Server Reconfiguration Wizard to reconfigure your existing 12.2.1 domain to a 12.2.1.2.0 domain with this command.
```
ORACLE_HOME/oracle_common/common/bin/reconfig.sh -log=logFileName.log -log_priority=FINE
```
Run the Upgrade Assistant to upgrade your Veridata configuration to 12.2.1.2.0 with Upgrading Your Oracle GoldenGate Veridata Configuration.
Start your Veridata WebLogic Server and domain. See Starting the Servers in Installing and Configuring Oracle GoldenGate Veridata.
Run the agent_config utility to upgrade your Veridata Agent with Upgrading the Veridata Agent.
Go to Performing Post-Upgrade Tasks.

Migrating a MySQL Repository Configuration to Veridata 12.2.1.2.0

Support for MySQL was removed in Oracle GoldenGate Veridata 12.2.1.2.0 so you must migrate to any of the supported databases for this release using the following steps:

To migrate existing configuration like connections, groups, jobs and profiles, use the Veridata export and import utilities. For more information, see Administering Oracle GoldenGate Veridata.

Go to the DOMAIN_HOME/veridata/bin directory.
Use the export utility to export all the configured objects from MySQL repository to a XML file. This utility exports Connections (including passwords), Groups, Jobs, and Profiles. It does not export the User Preferences or Job Run history. If your new Veridata Agents use different host or port, update this connection information in the exported XML file.

The syntax for running the export script is:
```
veridata_export[.sh | .bat] -export filePath -wluser commandlineUusername   [-wlport portNo] [–jobs jobName | - groups groupName | -connections connName | -profiles profileName | -all | -exportPassword] [[-repoUrl jdbc_url] [-u username>][-schema schema_name][-vdtPath VERIDATA_PRODUCT_HOME]]
```
For example:
```
./veridata_export.sh -wluser vdtUser -wlport 8830 -export /scratch/mysqlRepo.xml -all -exportPassword -repoUrl jdbc:mysql://localhost:3306/DEV_VERIDATA -username DEV_VERIDATA -schema DEV_VERIDATA -vdtPath /scratch/fmwHome/user_projects/domains/mysqlDomain/ 
```
where: -repoUrl, -username, -schema, -vdtPath corresponds to your MySQL configuration.

The wluser must have Veridata Command Line privilege and Veridata Admin/ Veridata Power User privilege.
Note:

(Optional) The export operation exports all of the data in the repository to XML file without validation. If your environment has some compare pairs for which the Validation Status is not successful, then the import operation will fail with the XML file generated by the export operation. To prevent failure of the import operation, you have the option to disable the compare pair validation. You can do this by updating the generated XML with these steps:
1. Open the generated XML file.
2. Search for the configuration tag. This tag has the validation attribute, which is set to required, by default.
3. Set the validation attribute to one of the following values:
  
  omit-failures — Indicates that all successfully validated compare pairs will be added to the repository and other specified compare pairs will be ignored.
  
  none — Indicates that no compare pair validation is done before adding the compare pairs to the repository. You and then use the Veridata GUI to review and fix the validation problems. For example:
  
  Old tag: <configuration operation="update" validation="required">
  
  Updated tag: <configuration operation="update" validation="omit-failures">

Use the import utility to import all the configured objects you just exported.

The syntax for running the import utility is:

veridata_import[.sh | .bat] [-wlport portNo] -wluser commandlineUusername [-create | -update | -delete | -replace] configuration.xml

For example:

veridatadomain/veridata/bin/veridata_import.sh -wluser vdtUser -wlport 8830 -update /scratch/mysqlRepo.xml

Upgrade Utilities

This section contains explanations of how to use each of the upgrade utilities for the various upgrade paths that are identified in Choosing an Upgrade Path and Upgrading. You are directed to use these utilities with the steps in your chosen upgrade path:

For more information about the Upgrade Utilities, see About Using the Upgrade Assistant.

Creating Repository Schemas using Repository Creation Utility

Oracle GoldenGate Veridata Server requires a database to serve as a repository for objects that store the information and environment preferences that users create when using Oracle GoldenGate Veridata Web User Interface. You can use the following databases as a repository:

Oracle
Microsoft SQL Server

After installing Oracle GoldenGate Veridata 12c (12.2.1.2.0) and configuring your database, create the necessary schema for your repository database by using RCU. Navigate to the ORACLE_HOME/oracle_common/bin directory and start RCU.

RCU creates the schema_version_registry table in the database and it is used by Veridata and Upgrade Assistant. Following sections explain how to create schema for various databases:

Note:

In the RCU pages, when you create the Service Table (STB), specify a unique prefix for the schema for all databases. You need to provide this prefix while running the Upgrade Assistant for upgrading Veridata schema.

To drop the Veridata repository, you should use the same prefix.

Creating Schema for an 11g to 12.2.1.2.0 Upgrade

For all supported databases, create the Oracle Platform Security Services (OPSS) schema using RCU. Select Create new prefix then provide unique prefix. In the Select Components page, select Oracle Platform Security Services; the Common Infrastructure Services (STB) is selected by default as in the following:

Figure 2-1 OPSS schema selection for an 11g to 12.2.1.2.0 Upgrade

See Creating Schemas with the Repository Creation Utility for more information.

Creating Schema for a 12.1.3 Compact Domain SQL Server to 12.2.1.2.0 Upgrade

For upgrading to version 12.2.1.2.0, SQL Server you should run RCU to create the Oracle Platform Security Services (OPSS) schema using the same prefix which was used for 12.1.3. Select only OPSS in the Select Components page:

Figure 2-2 OPSS Schema selection for Non-Oracle database

selecting only OPS schema for SQL Server

See Creating Schemas with the Repository Creation Utility for more information.

Creating the Veridata Domain using the Upgraded Schema

To create a WebLogic Server domain for Veridata, follow the procedure described in "Configure a Domain for Oracle GoldenGate Veridata" in Installing and Configuring Oracle GoldenGate Veridata.

Note:

Provide the upgraded Veridata schema details on the JDBC Component Schema page of the Configuration Wizard as shown in Figure 2-3.

Figure 2-3 Schema Selection in the Configuration Wizard

Provide the upgraded schema details in the configuration wizard

Upgrading Veridata Schemas

The Oracle Fusion Middleware Upgrade Assistant upgrades your Oracle GoldenGate Veridata schema to 12c (12.2.1.2.0). For more information about the features of Upgrade Assistant, see About Using the Upgrade Assistant.

This topic contains the following:

Upgrading Veridata Schema from 11g to 12.2.1.2.0

The Oracle Fusion Middleware Upgrade Assistant upgrades your Oracle GoldenGate Veridata schema to 12c (12.2.1.2.0).

To upgrade the Veridata repository schema from 11g to 12.2.1.2.0 follow the instructions below:

To start Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:

On UNIX: ./ua

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

On Windows: ua.bat

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

The Welcome screen of the Upgrade Assistant appears. Click Next.
Select Individually Selected Schemas as the upgrade type. Click Next.
The Upgrade Assistant lists all schemas available for upgrade. Select only Oracle GoldenGate Veridata. Ensure that no other schemas are selected for upgrade.
You must select all the checkboxes to continue. The Upgrade Assistant will not verify that the prerequisites have been met.
On the VERIDATA Schema page, enter the connection credentials for the database containing the schema you want to upgrade.
On the Veridata Schema Prefix page, enter the prefix that was entered while creating the schema using RCU. See Creating Repository Schemas using Repository Creation Utility.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded. Click Next.
Click Upgrade on the Upgrade Summary screen to begin the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.

To verify the schema upgrade, follow the procedure as described in Verifying the Schema Upgrade.

To troubleshoot issues that might occur during schema upgrade, review the logs as described in Troubleshooting your Upgrade.

Upgrading Oracle GoldenGate Veridata Schema from 12.1.3 Compact Domain to 12.2.1.2.0

The Oracle Fusion Middleware Upgrade Assistant upgrades your Oracle GoldenGate Oracle GoldenGate Veridata schema to 12c (12.2.1.2.0).

To upgrade the Oracle GoldenGate Veridata repository schema from 12.1.3 Compact Domain to 12.2.1.2.0 follow the instructions below:

To start Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:

On UNIX: ./ua

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

On Windows: ua.bat

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

The Welcome screen of the Upgrade Assistant appears. Click Next.
Select Individually Selected Schemas as the upgrade type. Click Next.
The Upgrade Assistant lists all schemas available for upgrade. Select only Common Infrastructure Services and Oracle GoldenGate Veridata. Ensure that no other schemas are selected for upgrade.
You must select all the checkboxes to continue. The Upgrade Assistant will not verify that the prerequisites have been met.
On the VERIDATA Schema page, enter the connection credentials for the database containing the schema you want to upgrade.
On the Veridata Schema Prefix page, enter the prefix that was entered while creating the schema using RCU. See Creating Repository Schemas using Repository Creation Utility.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded. Click Next.
Click Upgrade on the Upgrade Summary screen to begin the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.

To verify the schema upgrade, follow the procedure as described in Verifying the Schema Upgrade.

To troubleshoot issues that might occur during schema upgrade, review the logs as described in Troubleshooting your Upgrade.

Upgrading Veridata Schemas from 12.1.3 Expanded Domain to 12.2.1.2.0

The Oracle Fusion Middleware Upgrade Assistant upgrades your Oracle GoldenGate Veridata schema to 12c (12.2.1.2.0).

To upgrade the Veridata repository schema from 12.1.3 Expanded Domain to 12.2.1.2.0 follow the instructions below:

To start Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:

On UNIX: ./ua

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

On Windows: ua.bat

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

The Welcome screen of the Upgrade Assistant appears. Click Next.
Select All Schemas Used By a Domain as the upgrade type. Click Next.

After selecting Next, the screen displays the auto-selected schemas as shown in the following figure:
You must select all the checkboxes to continue. The Upgrade Assistant will not verify that the prerequisites have been met.
On the VERIDATA Schema page, enter the connection credentials for the database containing the schema you want to upgrade.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded. Click Next.
Click Upgrade on the Upgrade Summary screen to begin the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.

To verify the schema upgrade, follow the procedure as described in Verifying the Schema Upgrade.

To troubleshoot issues that might occur during schema upgrade, review the logs as described in Troubleshooting your Upgrade.

Upgrading Veridata Schemas from 12.2.1 Domain to 12.2.1.2.0

The Oracle Fusion Middleware Upgrade Assistant upgrades your Oracle GoldenGate Veridata schema to 12c (12.2.1.2.0).

To upgrade the Veridata repository schema from 12.2.1 Domain to 12.2.1.2.0 follow the instructions below:

To start Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:

On UNIX: ./ua

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

On Windows: ua.bat

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.

The Welcome screen of the Upgrade Assistant appears. Click Next.
Select All Schemas Used By a Domain as the upgrade type. Click Next.

After selecting Next, the screen displays the auto-selected schemas as shown in the following figure:
You must select all the checkboxes to continue. The Upgrade Assistant will not verify that the prerequisites have been met.
On the VERIDATA Schema page, enter the connection credentials for the database containing the schema you want to upgrade.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded. Click Next.
Click Upgrade on the Upgrade Summary screen to begin the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.

To verify the schema upgrade, follow the procedure as described in Verifying the Schema Upgrade.

To troubleshoot issues that might occur during schema upgrade, review the logs as described in Troubleshooting your Upgrade.

Upgrading Your Oracle GoldenGate Veridata Configuration

The Oracle Fusion Middleware Upgrade Assistant is also used to upgrade your Oracle GoldenGate Veridata repository schema using the following steps:

To start the Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:

On UNIX: ./ua

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if-logLevel TRACE is used.

On Windows: ua.bat

Note:
A default logging level is NOTIFICATION. In general -logLevel TRACE is recommended for Veridata.
When setting the -logLevel to TRACE, more information is logged and that is used to troubleshoot a failed upgrade. The Oracle Fusion Middleware Upgrade Assistant's log files may become very large if -logLevel TRACE is used.
Select All Configurations Used by a Domain on the All Configurations page and enter the domain directory path, then click Next.
Select the Veridata domain to be upgraded. See Creating the Veridata Domain using the Upgraded Schema.
The Component List page displays a list of components that will be upgraded. Review the list and click Next to start the upgrade process.
The Prerequisites screen lists items that you must check and verify before you can proceed.

You must check the boxes before you can continue. The Upgrade Assistant will not verify that the prerequisites have been met.
Depending on the upgrade path, perform one of the below mentioned actions:

On the Veridata 11g Home Directory page, specify the location of the Veridata 11g installation:

When SQL Server was used as Veridata repository for 11g and 12.1.3, the following figure will be applicable:

When you upgrade from 12.1.3 expanded domain and 12.2.1.0.0, Veridata Home Directory page is not displayed.
On the Examine screen, the Upgrade Assistant performs a series of validations before upgrading the selected components. Ensure that all validations have succeeded. Click Next to start the upgrade process.
Click Upgrade on the Upgrade Summary screen to begin the upgrade. The Upgrade Progress screens shows information about the progress of the upgrade, and the Upgrade Success screen summarizes the upgrade.

Upgrading the Veridata Agent

Upgrade your existing Veridata Agent the new 12c (12.2.1.2.0) agent using one of the following commands:
Upgrading from 11g

Deploy the Oracle GoldenGate Veridata Agent to a directory outside ORACLE_HOME.

ORACLE_HOME/veridata/agent/bin/agent_config.sh NEW_AGENT_ORACLE_HOME

Upgrading from 12c (12.1.3 or 12.2.1)

Deploy the Veridata Agent to the same location used in 12c(12.1.3 or 12.2.1) setup.

ORACLE_HOME/veridata/agent/agent_config.sh OLD_AGENT_ORACLE_HOME

Either command replaces the following files with the new 12.2.1.2.0 files:

On Unix:
```
agent.properties.sample
config/agent-jps-config.xml
config/certs/serverIdentity.jks
config/certs/serverTrust.jks
config/odl.xml;
agent.sh
configure_agent_ssl.sh
```
On Windows:
```
agent.bat
agent.properties.sample
config/agent-jps-config.xml
config/certs/serverIdentity.jks
config/certs/serverTrust.jks
config/odl.xml
configure_agent_ssl.bat
service/Install_Veridata_Agent.bat
service/README.txtservice/Start_Veridata_Agent.bat
service/Stop_Veridata_Agent.bat
service/Uninstall_Veridata_Agent.bat
service/agent_service.properties
```
(Optional) If you have changed any of the files listed in step 1in the previous release, then use your backup files to replace these changed files.If your Veridata Agent is installed as a service in Windows machine, then update the service/agent_service.properties property with the same service name that you used in the previous release.
(Optional) 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.
Start your Veridata Agent.