Oracle® GoldenGate

Upgrading Oracle GoldenGate Veridata

12c (12.2.1)

E60966-01

October 2015

Oracle GoldenGate Upgrading Oracle GoldenGate Veridata, 12c (12.2.1)

E60966-01

Copyright © 2014, 2015,  Oracle and/or its affiliates. All rights reserved.

Primary Author:  Savija Vijayaraghavan

Contributing Author: Lorna Vallad

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate failsafe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

List of Tables

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Preparing for the Oracle GoldenGate Veridata Upgrade

- 1.1 Overview of the Oracle GoldenGate Veridata Upgrade Process

- 1.2 Oracle GoldenGate Veridata Server Upgrade Roadmap

- 1.3 Pre-Upgrade Requirements for Oracle GoldenGate Veridata Upgrade

- 1.4 Understanding the Upgrade Prerequisites

2 Upgrading Oracle GoldenGate Veridata

- 2.1 Choosing an Upgrade Path and Upgrading

- 2.1.1 Upgrading Veridata 11g to Veridata 12.2.1

- 2.1.2 Upgrading a Veridata 12.1.3 Compact Domain to 12.2.1

- 2.1.3 Upgrading a Veridata 12.1.3 Expanded Domain to Veridata 12.2.1

- 2.1.4 Migrating a MySQL Repository Configuration to Veridata 12.2.1

- 2.2 Upgrade Utilities

- 2.2.1 Creating Repository Schemas using Repository Creation Utility

- 2.2.2 Creating the Veridata Domain using the Upgraded Schema

- 2.2.3 Upgrading Veridata Schemas

- 2.2.4 Upgrading Your Veridata Configuration

- 2.2.5 Upgrading the Veridata Agent

3 Performing Post-Upgrade Tasks

- 3.1 Verifying the Schema Upgrade

- 3.2 Verifying the Veridata Configuration Upgrade

- 3.3 Managing Veridata Users

- 3.4 Verifying Veridata Report Files

- 3.5 Troubleshooting your Upgrade

List of Tables

- 1-1 Directories in an Oracle GoldenGate Veridata Installation

Preface

This document describes how to upgrade an existing Oracle GoldenGate Veridata 11g or 12c (12.1.3) environment to 12c (12.2.1).

Audience

This document is intended for system administrators who are responsible for installing, maintaining, and upgrading Oracle GoldenGate Veridata.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see the following documentation set:

- Installing and Configuring Oracle GoldenGate Veridata

- Administering Oracle GoldenGate Veridata

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Preparing for the Oracle GoldenGate Veridata Upgrade

This chapter provides a summary of points you should understand before you upgrade Oracle GoldenGate Veridata from the 11g and 12c (12.1.3) releases to the 12c (12.2.1) release.

This chapter includes the following sections:

- Section 1.1, "Overview of the Oracle GoldenGate Veridata Upgrade Process"

- Section 1.2, "Oracle GoldenGate Veridata Server Upgrade Roadmap"

- Section 1.3, "Pre-Upgrade Requirements for Oracle GoldenGate Veridata Upgrade"

- Section 1.4, "Understanding the Upgrade Prerequisites"

1.1 Overview of the Oracle GoldenGate Veridata Upgrade Process

The upgrade process described in this document applies to upgrades from Oracle GoldenGate Veridata Release 11g (11.2.1.0.0) and greater and 12c (12.1.3) to Oracle GoldenGate Veridata Release 12c (12.2.1).

The following table describes the directories and the variables that are used when referring to those directories in this book.

Table 1-1 Directories in an Oracle GoldenGate Veridata Installation

Directory Variable

Directory Path

ORACLE_HOME

/install_location/Oracle_Home. This is the home directory for the Oracle Fusion Middleware products.

VERIDATA_PRODUCT_HOME

/ORACLE_HOME/veridata

OLD_AGENT_ORACLE_HOME

/VERIDATA_PRODUCT_HOME/agent for your existing 11g or 12c (12.1.3) Veridata Agent.

NEW_AGENT_ORACLE_HOME

/VERIDATA_PRODUCT_HOME/agent for your new 12c (12.2.1) Veridata Agent.

AGENT_DEPLOY_LOCATION

This is the location where the Veridata Agent is deployed in the WebLogic Server domain.

Note: that this location should be outside the ORACLE_HOME.

1.2 Oracle GoldenGate Veridata Server Upgrade Roadmap

Follow the steps below to upgrade Oracle GoldenGate Veridata:

1. Before you upgrade, back up your existing environment then ensure that all pre-upgrade requirements are met. See "Pre-Upgrade Requirements for Oracle GoldenGate Veridata Upgrade".

2. Ensure that all upgrade prerequisites are met. See Section 1.4, "Understanding the Upgrade Prerequisites".

3. Install Oracle GoldenGate Veridata 12c (12.2.1). See Installing and Configuring Oracle GoldenGate Veridata.

4. Install Oracle GoldenGate Veridata Agent 12c (12.2.1). See Oracle GoldenGate Installing, Configuring, and Upgrading Oracle GoldenGate Monitor Agent.

5. Perform a readiness check then upgrade your existing environment to Oracle GoldenGate Veridata 12c (12.2.1). See Chapter 2, "Upgrading Oracle GoldenGate Veridata".

6. Perform the necessary post-installation tasks. See Chapter 3, "Performing Post-Upgrade Tasks".

1.3 Pre-Upgrade Requirements for Oracle GoldenGate Veridata Upgrade

Before you upgrade, you must do the following:

1. Ensure that no jobs are running in your existing Veridata instance.

2. Stop your existing Veridata Server.

3. Stop all of your existing Veridata Agents.

4. Back up the Veridata Agent configuration files.

5. Back up the Veridata repository.

6. Back up old report files. Do not delete the existing report location if you want to retain old reports.

1.4 Understanding the Upgrade Prerequisites

Following are the prerequisites for upgrading your existing Oracle GoldenGate Veridata Server to 12c (12.2.1):

- JDK 8 must be installed on the target machine. For more information about the JDK 8 installation, see the Java Platform, Standard Edition Installation Guide at
https://docs.oracle.com/javase/8/docs/technotes/guides/install/install_overview.html

- Oracle WebLogic Server 12c (12.2.1) with JRF installed on the target machine. For more information, see Installing and Configuring the Oracle Fusion Middleware Infrastructure.

- If required, upgrade the Veridata repository database. For more details about the supported databases, see the system requirements document at
https://support.oracle.com/

2 Upgrading Oracle GoldenGate Veridata

This chapter describes the tasks you perform to upgrade Oracle GoldenGate Veridata.

This chapter includes the following sections:

- Section 2.1, "Choosing an Upgrade Path and Upgrading"

- Section 2.2, "Upgrade Utilities"

2.1 Choosing an Upgrade Path and Upgrading

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

- Section 2.1.1, "Upgrading Veridata 11g to Veridata 12.2.1"

- Section 2.1.2, "Upgrading a Veridata 12.1.3 Compact Domain to 12.2.1"

- Section 2.1.3, "Upgrading a Veridata 12.1.3 Expanded Domain to Veridata 12.2.1"

- Section 2.1.4, "Migrating a MySQL Repository Configuration to Veridata 12.2.1"

2.1.1 Upgrading Veridata 11g to Veridata 12.2.1

The Oracle GoldenGate Veridata 11g release was based on the use of the Apache Tomcat Application Server. Oracle GoldenGate Veridata 12.2.1 uses Oracle WebLogic Servers 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, use these steps:

1. Run RCU to create OPSS schemas and Service Table (STB) with Section 2.2.1, "Creating Repository Schemas using Repository Creation Utility".

2. Run the Upgrade Assistant to upgrade your Veridata schema to 12.2.1 with Section 2.2.3, "Upgrading Veridata Schemas".

3. 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 Section 2.2.2, "Creating the Veridata Domain using the Upgraded Schema".

4. Run Upgrade Assistant to perform the Veridata configuration upgrade to 12.2.1, which includes wallet and veridata.cfg migration with Section 2.2.4, "Upgrading Your Veridata Configuration"

5. Start your Veridata WebLogic Server and domain. See "Starting the Servers" in Installing and Configuring Oracle GoldenGate Veridata.

6. Run the agent.config utility to upgrade your Veridata configuration with Section 2.2.4, "Upgrading Your Veridata Configuration".

7. Run the Upgrade Assistant to upgrade your Veridata Agent with Section 2.2.5, "Upgrading the Veridata Agent".

8. Go to Chapter 3 and perform the post-installation tasks.

2.1.2 Upgrading a Veridata 12.1.3 Compact Domain to 12.2.1

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 release and only Expanded domain is supported.

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

1. Run RCU to create OPSS schemas using the same prefix that you used in 12.1.3 with Section 2.2.1, "Creating Repository Schemas using Repository Creation Utility".

2. Run the Upgrade Assistant to upgrade your Veridata schema and STB to 12.2.1 with Section 2.2.3, "Upgrading Veridata Schemas".

3. 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 Section 2.2.2, "Creating the Veridata Domain using the Upgraded Schema".

4. Run Upgrade Assistant to perform the Veridata configuration upgrade to 12.2.1 including wallet migration and veridata.cfg migration with Section 2.2.4, "Upgrading Your Veridata Configuration"

5. Start your Veridata WebLogic Server and domain. See "Starting the Servers" in Installing and Configuring Oracle GoldenGate Veridata.

6. Run the agent.config utility to upgrade your Veridata configuration with Section 2.2.4, "Upgrading Your Veridata Configuration".

7. Run the Upgrade Assistant to upgrade your Veridata Agent with Section 2.2.5, "Upgrading the Veridata Agent".

8. Go to Chapter 3 and perform the post-installation tasks.

2.1.3 Upgrading a Veridata 12.1.3 Expanded Domain to Veridata 12.2.1

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

1. Run the Upgrade Assistant to upgrade your Veridata and OPSS schemas to 12.2.1 with Section 2.2.3, "Upgrading Veridata Schemas" or using the Domain Assisted Schema Upgrade (DASU), which is the recommended way to upgrade.

2. Run the Oracle WebLogic Server Reconfiguration Wizard to reconfigure your existing 12.1.3 expanded domain to a 12.2.1 domain with this command.

ORACLE_HOME/oracle_common/common/bin/reconfig.sh -log=logFileName.log -log_priority=FINE"

3. Run the Upgrade Assistant to upgrade your Veridata schema to 12.2.1 with Section 2.2.4, "Upgrading Your Veridata Configuration".

4. Start your Veridata WebLogic Server and domain. See "Starting the Servers" in Installing and Configuring Oracle GoldenGate Veridata.

5. Run the agent.config utility to upgrade your Veridata configuration with Section 2.2.4, "Upgrading Your Veridata Configuration".

6. Run the Upgrade Assistant to upgrade your Veridata Agent with Section 2.2.5, "Upgrading the Veridata Agent".

7. Go to Chapter 3 and perform the post-installation tasks.

2.1.4 Migrating a MySQL Repository Configuration to Veridata 12.2.1

Support for MySQL was removed in Oracle GoldenGate Veridata 12.2.1 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.

1. Go to the DOMAIN_HOME/veridata/bin directory.

2. 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">

3. 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

2.2 Upgrade Utilities

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

- Section 2.2.1, "Creating Repository Schemas using Repository Creation Utility"

- Section 2.2.2, "Creating the Veridata Domain using the Upgraded Schema"

- Section 2.2.3, "Upgrading Veridata Schemas"

- Section 2.2.4, "Upgrading Your Veridata Configuration"

- Section 2.2.5, "Upgrading the Veridata Agent"

2.2.1 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) 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.

- Section 2.2.1.1, "Creating Schema for an 11g to 12.2.1 Upgrade"

- Section 2.2.1.2, "Creating Schema for a 12.1.3 Compact Domain SQL Server to 12.2.1 Upgrade"

2.2.1.1 Creating Schema for an 11g to 12.2.1 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 Upgrade

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

2.2.1.2 Creating Schema for a 12.1.3 Compact Domain SQL Server to 12.2.1 Upgrade

For upgrading to version 12.2.1, 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 Service Table in the Select Components page:

Figure 2-2 Service Table selection for Non-Oracle database

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

2.2.2 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

2.2.3 Upgrading Veridata Schemas

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

To upgrade the Veridata repository schema follow the instructions below:

1. To start Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:
On UNIX: ./ua

On Windows: ua.bat

The Welcome screen of the Upgrade Assistant appears. Click Next.

2. Select Individually Selected Schemas as the upgrade type. Click Next.

3. The Upgrade Assistant lists all schemas available for upgrade. Select only Oracle GoldenGate Veridata. Ensure that no other schemas are selected for upgrade.

4. You must select all three checkboxes to continue. The Upgrade Assistant will not verify that the prerequisites have been met.

5. On the VERIDATA Schema page, enter the connection credentials for the database containing the schema you want to upgrade.

6. On the Veridata Schema Prefix page, enter the prefix that was entered while creating the schema using RCU. See Section 2.2.1, "Creating Repository Schemas using Repository Creation Utility".

7. 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.

8. 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 Section 3.1, "Verifying the Schema Upgrade".

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

2.2.4 Upgrading Your Veridata Configuration

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

1. To start the Upgrade Assistant, go to the ORACLE_HOME/oracle_common/upgrade/bin directory, and enter the following command:
On UNIX: ./ua

On Windows: ua.bat

2. Select All Configurations Used by a Domain on the All Configurations page and enter the domain directory path, then click Next.

3. Select the Veridata domain to be upgraded. See Section 2.2.2, "Creating the Veridata Domain using the Upgraded Schema".

4. The Component List page displays a list of components that will be upgraded. Review the list and click Next to start the upgrade process.

5. 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.

6. On the Veridata 12c Home Directory page, specify the location of the Veridata 12.2.1 installation.

7. 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.

8. 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.

2.2.5 Upgrading the Veridata Agent

1. Upgrade your existing Veridata Agent the new 12c (12.2.1) 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)

Deploy the Veridata Agent to the same location used in 12.1.3 setup.

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

Either command replaces the following files with the new 12.2.1 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.batservice/Stop_Veridata_Agent.batservice/Uninstall_Veridata_Agent.batservice/agent_service.properties

2. (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.

3. (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.

4. Start your Veridata Agent.

3 Performing Post-Upgrade Tasks

This chapter describes the post-upgrade tasks that are required for some upgrade scenarios.

This chapter includes the following sections:

- Section 3.1, "Verifying the Schema Upgrade"

- Section 3.2, "Verifying the Veridata Configuration Upgrade"

- Section 3.3, "Managing Veridata Users"

- Section 3.4, "Verifying Veridata Report Files"

- Section 3.5, "Troubleshooting your Upgrade"

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.0.0

VALID

N

IAU_APPEND

Audit Service Append

DEV100

DEV100_IAU_APPEND

12.2.1.0.0

VALID

N

IAU_VIEWER

Audit Service Viewer

DEV100

DEV100_IAU_VIEWER

12.2.1.0.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.0.0

VALID

N

VERIDATA

Veridata Repository

DEV100

VERIDATAONE

12.2.1.0.0

VALID

Y

3.2 Verifying the Veridata Configuration Upgrade

After upgrading to Oracle GoldenGate Veridata 12c (12.2.1), 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.

3.3 Managing Veridata Users

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

- Veridata 12.1.3 users for Oracle can be used in Veridata 12.2.1.

- Veridata 12.1.3 users for SQL Server cannot be used in Veridata 12.2.1. You must create Veridata users and assign privileges.

- Veridata 11g users cannot be used in Veridata 12.2.1. You must create Veridata users and assign privileges.

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 Administering Oracle GoldenGate Veridata.

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), 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.

If you have specified another location for the report files in the Veridata 12.1.3 installation then the same location will be used in Veridata 12c (12.2.1) 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 12.1.3 reports are not updated after upgrade.

3.5 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 Upgrading with the Upgrade Assistant.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.