Oracle 12c Golden Gate Veridata 1610472497

1
CONTENTS
0: Veridata introduction ............................................................................................................................. 3

1: Deploy and configure Veridata 12.2.1.0.0 ........................................................................................... 9
2: Deploy and configure Veridata 12.2.1.4.0 ......................................................................................... 42
3: Install and configure Veridata 12.2.1.4.0 with backing pluggable database ................................ 73
4: Deploy and Configure Oracle Golden Gate veridata agent .......................................................... 107
5: Deploy and Configure Oracle Golden Gate veridata agent for pluggable database ................ 114
6: Deploy and Configure Oracle Golden Gate veridata agent on target database server ............ 122
7: Job Configuration in oracle GG veridata ......................................................................................... 135
8: Vericom utility ....................................................................................................................................... 152
9: Uninstall OGG Veridata ......................................................................................................................... 156
2
0: Veridata introduction
Oracle providing oracle veridata tool for data comparison and repair, using veridata you can compare data
from two target database. Veridata compare the data from two data set (source and target database) and
shows out of Sync records. Veridata tool especially considerable in high volume data set(environment)
where you can verify the data integrity and repair if any inconsistent data without any downtime.
Mostly people use this tool where oracle Golden Gate configured, you can use it to data comparison and
sync operation between two data set (source and target database). Using this tool, you can easily sync the
Mitch match record between two data. Best thing of this tool is you can sync the data without stop the
replication operation also you will get accurate report without stop GG operation.
Fig 0.1: veridata architecture
Components Details:
Veridata repository database: backing database to store the veridata repository
Veridata Server: veridata server where stored veridata binaries
Veridata command line: veridata command line tool through you can configure veridata job using
command line
Veridata Application: veridata web base GUI interface
Veridata AGENT: veridata agent to get data from source and target database (target Machin)
Source and target database: dataset to compare the data
3
Agent Deployment
In veridata to get the data from target database for comparison you need to deploy
agent for specific database. You can deploy the veridata agent in two way, one is to deploy agent for
target database on veridata server itself, another way is to deploy agent on target database servers.
Below two figure showing both deployment diagram.
Fig 0.2: Deploy Agent on veridata server for target database
Fig 0.3: deploy veridata agent on target database servers
4
Veridata web GUI explanation:
In veridata web GUI you will get below main option
✓ Running Job
✓ Finished job
✓ Repair job
✓ Configuration
✓ Run/Execute job
✓ Report
✓ Option and settings
Option explanation:
Running Jobs:
You can see the running job details sort by job name, group, compare pair. Below screen shot
showing currently no jobs are running.
5
Finished Jobs:
Dashboard will show details about the finished job, you can filter it by job, group, compare
pair. Let’s see finished job filter with job
Repair job:
Dash board will show all jobs details on repair operation performed
6
Report:
If you want to see the report of each jobs, got to report and click on particular job report
Configuration:
You can create connection, group, job and profile.in next section we will see how to create it.
Run/Execute Job:
You can select job name and profile and execute particular job
Options/Setting:
If you want to change the values of user preferences and purge data
User preference dashboard
7
Purge Data
8
1: Deploy and configure Veridata 12.2.1.0.0
Fig 1.1: veridata configuration
Info: In this veridata configuration we are going to configure veridata repository database and web logic
application on same node veridata.example.com, if you want to configure oracle veridata repository
database and web logic Application on different node you can configure it.
Table 1.1: Software Details
Name Version
Oracle Database 12.1.0.2.0
Java jdk1.8.0_241-amd64
Oracle Fusion Middleware 12.2.1.0.0
Oracle Golden Gate veridata 12.2.1.0.0
9
In this QuickStart, we learn how to:
Prerequisite:
• Oracle 12c R1 database

• Create oracle user and grant it appropriate privilege to run RCU
• Set JAVA_HOME
Installation and configuration:
• Install Oracle Fusion Middleware (FMW) infrastructure

• Install oracle veridata
• Execute Repository Creation utility (RCU)
• Create New domain
• Start Web logic Server
• Check web logic URL
• Start Veridata Server
• Create New user for veridata operation
• Validate the veridata URL
Prerequisite:
Step-1 oracle 12c R1 database details
Step-2 Create oracle user and grant it appropriate privilege to run RCU
SQL> create user veridata_admin

identified by admin112233;
/
User created.
SQL> GRANT CONNECT, RESOURCE, DBA TO veridata_admin;
Grant succeeded.
10
Step-3 set JAVA_HOME
Step-1 Install Oracle Fusion Middleware (FMW) infrastructure
[oracle@veridata tmp]$ unzip -q V78156-01_12.2.1.0.0.zip
Click on next
11
Select skip auto update and select on next on
Select ORACLE HOME for Oracle Fusion Middleware 12c
12
Select Fusion Middleware infrastructure and click on next button
Click on next button after 100% completion
Note: Ignore the alert or yo
13
Unclick on I wish to receive security update via my Oracle Support and click on next button
Click on yes
14
Click on install button
Progress screen
15
After 100% completion click on next
Click on Finish
16
Step-2 Install oracle veridata
Click on next
17
Select Skip Auto Updates and click button
Select ORACLE_HOME and click on next button
18
Select Oracle GoldenGate Veridata Server and Agent and Click on Next
Note: If you want to Install Veridata Server, select option Oracle Golden Gate Veridata Server. For
Veridata Agent select Golden Gate Veridata Agent.
19
Note: Ignore alert, or you can use 7.8 or higher version of OS and use java certified version.
Click on Install Button
20
After 100% completion Click on next button
Click on Finish
21
Step-3 Execute Repository Creation utility (RCU)
Click on next button
Select System Load and Product Load and click on next button
22
Specify the oracle database details:
Note: To Configure the Oracle Fusion Middleware need oracle database with AL32UTF8 character Set
Click on ok button
23
Specify the DEV to Create new prefix and select Veridata Repository and click next
Click on next
24
Select Use same password for all schema and click on next
Note: If you want to Deferent Password for each schema, select Specify Different passwords for all
schemas
Click on next It will create respective tablespace for repository schema
25
Click on next
Click on OK button
26
Click on ok
Click on Create button
27
If you want check log for each operation click on respective option or click on close
Step-4 Create New domain
To create new domain for veridata execute config.sh script
[oracle@veridata u02]$ cd /u02/app/oracle/oracle_common/common/bin/
[oracle@veridata bin]$ pwd
28
Click on Create a new domain and specify the Domain location where you want to store domain binaries
Select the veridata Standard WebLogic Server Domain option
29
Specify the web logic password
Select the development option and JDK HOME, it will select default JDK HOME
Note: If you want configure veridata for production then select production option, in this example we
are configuring veridata for testing environment.
30
Specify the below details for RCU data
Vender: ORACLE (database vender)

Database service: orcl (Database Service Name)
Hostname: Database Server Hostname
Schema owner: it will show default DEV_STB
Schema password: Enter the password (we create for all schema in step-2)
After specify all details click on Get RCU Configuration it will check all details which you mentioned and
click Next
31
If you want to mentioned different password for each schema you can Enter it on specific user password
text box
It will validate all details about the user, click on next
32
Click on next button
Select Administrator Server option and click on Next
33
If you want Enable SSL select it and If you want to change default port you can specify it.
In below screen shot I choose default setting and click on next button
Click Create button
34
After 100% completion Click next
Note details about the link and click on Finish
35
Step-5 Start Web logic Server
Go to /u02/app/oracle/user_projects/domains/base_domain/bin
Step-6 Check web logic URL
http://<hostname/ip address>:7001/console
Enter web logic user and its password
Step-7 Start Veridata Server
Execute veridataServer.sh and Enter web logic user and password
36
Step-8 Create New user for veridata operation
Connect to weblogic portal and create user for Veridata operation

Go to home page and click on Security Realms
37
Click on myrealm
Click on User and Group
38
Click on new
Specify user details and click on ok
Name: Veridata_1 (user name)
Description: veridata admin user (user description)
Password: ******(user password)
39
Click on Created user -> click on Group
Assign all veridata related group to user and click on save button
40
Step-9 Validate the veridata URL
http://<hostname/ip address>:8830/veridata/login.jsf
Enter veridata user and its password which we created in step-7 (veridata-1 and its password)
41
2: Deploy and configure Veridata 12.2.1.4.0
Info: In this veridata configuration we are going to configure database and web logic application on
same node veridata.example.com, if you want to configure oracle database and web logic Application
on different node you can do it.
Name Version
Oracle Database 12.1.0.2
Note: In this example we used the non-container database 12c R1 as backing up database for veridata
and oracle middleware application
42
Prerequisite:
• Oracle Fusion Middleware (FMW) backing up database (12c R1)

• Create oracle user and grant it appropriate privilege to run RCU
• Set JAVA_HOME

Prerequisite:
Step-1 Oracle Fusion Middleware (FWM) backing up database (12c R1)
Step-2 Create oracle user and grant it appropriate privilege to run RCU
43
Step-3 Set JAVA_HOME
[root@veridata tmp]# export JAVA_HOME=/usr/java/jdk1.8.0_141/jre
[root@veridata tmp]# echo $JAVA_HOME
/usr/java/jdk1.8.0_141/jre
[root@veridata tmp]#
44
Select Skip Auto Updates and click on next button
Note: create directory for ORACLE_HOME of oracle fusion middleware /u02/app/oracle
Specify the ORACLE_HOME where oracle FMW binaries
45
46
Click on install
After 100% completion Click on Next
47
Click on Finish
After Oracle Fusion middleware installation, install oracle veridata
48
Click on next
Select the Skip Auto Updates and click on next button
49
Select ORACLE_HOME of oracle Fusion middleware and click on next
Select complete Install and click on next
50
After 100% completion click on next button
Click on Finish
51
Read the Details and click Finish
52
Click on next
53
Specify the Database details to store the RCU repository
Hostname: veridata.example.com
Port: 1521
Service name: orcl
User Name: veridata_admin
Password: *******
Role: Normal
54
Note: You can install RCU repository using sys/system user, if you use sys/system user then select role
as as sysdba
Click on next
select oracle Golden Gate option and click on next
55
Click on Next
Select Use same password for all schemas
Note: If you want different password for each schema then select Specify different password for all
schemas, good practice is use same password for all schema.
56
Screen will show details about the schema, default table space of schema and its temp tablespace.
Click on next
Read the details and click on OK
57
Click on OK
Click on create
58
Click on Close
Note: If you want see log of each component, click on specific log
59
60
Specify the web logic user and its password
61

Database service: orcl (Database Service Name)
Hostname: veridata.example.com (Database Server Hostname)
click Next
62
If each schema password is different than enter password front box of each schema
It will check connectivity of each schema, click on next button
63
Click on next
Select administration Server and click on Next
64
Click on Next
65
After 100% completion click on Next
Click on next
66
[oracle@veridata bin]$ nohup sh startWebLogic.sh 2>&1 &
http://192.168.94.154:7001/console
Login with weblogic user its password
67

68
Click on myrealm
Click on Users and Groups
69
Click on New
Specify user details and click on ok button
70
Assign veridata related Group to created user (veridata_1) and click on save
71
72
3: Install and configure Veridata 12.2.1.4.0 with backing pluggable database
Info: In this veridata configuration we are going to configure database and web logic application on
same node veridata.example.com, if you want to configure oracle database and web logic Application
on different node you can do it.
Name Version
Oracle Database 12.2.0.1
Container Database cdb1
Pluggable Database veridata
Note: In this example we used the non-container database 12c R1 as backing up database for veridata
and oracle middleware application
73
Prerequisite:
• Oracle Fusion Middleware (FMW) backing up database (12c R2)

• Create pluggable database for veridata
• Set JAVA_HOME

Prerequisite:
Step-1 Oracle Fusion Middleware (FMW) backing database (12c R2)
Step-2 Create pluggable database for veridata
SQL> select name from v$database;
NAME
---------
74
CDB1
SQL>CREATE PLUGGABLE DATABASE veridata ADMIN USER admin identified by

"Password12345"
DEFAULT TABLESPACE USERS
DATAFILE '/u01/app/oracle/oradata/CDB1/veridata/users01.dbf'
SIZE 250M AUTOEXTEND ON
FILE_NAME_CONVERT=(
'/u01/app/oracle/oradata/cdb1/pdbseed/',
'/u01/app/oracle/oradata/CDB1/veridata/');
SQL> alter session set container=veridata;
Session altered.
SQL> select name from v$database;
NAME
---------
CDB1
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED

---------- ------------------------------ ---------- ----------
4 VERIDATA READ WRITE NO
Step-3 Set JAVA_HOME
Get JAVA_HOME details

[root@veridata ~]# update-alternatives --config java
There is 1 program that provides 'java'.
Selection Command
-----------------------------------------------
*+ 1 /usr/java/jdk1.8.0_141/jre/bin/java
Enter to keep the current selection[+], or type selection number: 1
[oracle@veridata ~]$ export JAVA_HOME=/usr/java/jdk1.8.0_141/jre
75
76
Select Skip Auto Updates and click on next button
Note: create directory for ORACLE_HOME of oracle fusion middleware /u02/app/oracle
Specify the ORACLE_HOME where oracle FMW binaries
77
78
Click on install
79
Click on Finish
After Oracle Fusion middleware installation, install oracle veridata
80
Click on next
Select the Skip Auto Updates and click on next button
81
Select ORACLE_HOME of oracle Fusion middleware and click on next
Select complete Install and click on next
82
After 100% completion click on next button
Click on Finish
83
Read the Details and click Finish
84
Click on next
85
Specify the Database details to store the RCU repository
Hostname: veridata.example.com
Port: 1521
Service name: veridata {pluggable database name}
User Name: admin {pluggable database admin user}
Password: *******
Role: Normal
86
Note: You can install RCU repository using sys/system user, if you use sys/system user then select role
as as sysdba
Click on next
87
select oracle Golden Gate option and click on next
Click on Next
88
Select Use same password for all schemas
Note: If you want different password for each schema then select Specify different password for all
schemas, good practice is use same password for all schema.
Screen will show details about the schema, default table space of schema and its temp tablespace.
Click on next
89
Read the details and click on OK
Click on OK
90
Click on create
Click on Close
Note: If you want see log of each component, click on specific log
91
Info: You can validate created user details in pluggable database veridata with DEV prefix schema name
Connect pluggable database and check user details
[oracle@veridata bin]$ ls -ltr config.sh
-rwxr-x---. 1 oracle oinstall 234 Aug 14 2019 config.sh
[oracle@veridata bin]$
92
93
Specify the web logic user and its password
94

Database service: veridata (pluggable Database Service Name)
Hostname: veridata.example.com (Database Server Hostname)
click Next
95
If each schema password is different than enter password front box of each schema
It will check connectivity of each schema, click on next button
96
Click on next
Select administration Server and click on Next
97
Click on Next
98
After 100% completion click on Next
Click on next
99
[oracle@veridata bin]$ nohup sh startWebLogic.sh 2>&1 &
http://192.168.94.158:7001/console
Login with weblogic user its password
100
[oracle@veridata bin]$ sh veridataServer.sh start
101

Click on myrealm
102
Click on Users and Groups
Click on New
Specify user details and click on ok button
103
104
Assign veridata related Group to created user (veridata_1) and click on save
105
106
4: Deploy and Configure Oracle Golden Gate veridata agent
Fig 4.5: Deployment Figure
Table 4.1: Software Details:
Name Version
Table 4.2: Directories in an Oracle GoldenGate Veridata Installation
Directories Variable Directories Location

ORACLE_HOME /u02/app/oracle
VERIDATA_HOME $ORACLE_HOME/veridata
AGENT_ORACLE_HOME $VERIDATA_HOME/agent
AGENT1_HOME $ORACLE_HOME/agent1
AGENT2_HOME $ORACLE_HOME/agent2
Note: In this example we are not set ORACLE_HOME variable, because we have database on same
server where veridata application installed.
Info: In this example we are deploying agent on same server where we installed veridata application, but
as per oracle document you have to deploy agent on target database server. If you want stay production
server safe, you can deploy agent on veridata server but it will take more I/O of application server.
107
• Create Directory for AGENT_HOME

• Create AGENT_HOME for Target database
• Configure target database details in Agent property files and start Agent
• Validate
Step-1 Create Directory for AGENT_HOME

[oracle@veridata ~]$ mkdir -p /u02/app/oracle/agent1
Set variable
Step-2 Create AGENT_HOME for Target database
Set JAVA_HOME first
Note: Set JAVA_HOME before configure veridata agent and start the agent
108
Step-3 Configure target database details in Agent property files
Got AGENT1_HOME
[oracle@veridata agent]$ cd $AGENT1_HOME
[oracle@veridata agent_1]$ ls -ltr
total 24
-rw-r-----. 1 oracle oinstall 74 Oct 11 22:22 VAOH.sh
drwxr-x---. 2 oracle oinstall 6 Oct 11 22:22 drivers
-rw-r-----. 1 oracle oinstall 9638 Oct 11 22:22
agent.properties.sample
-rwxr-----. 1 oracle oinstall 261 Oct 11 22:22 configure_agent_ssl.sh
drwxr-x---. 3 oracle oinstall 62 Oct 11 22:22 config
-rwxr-----. 1 oracle oinstall 303 Oct 11 22:22 agent.sh
[oracle@veridata agent_1]$
[oracle@veridata agent_1]$ cp agent.properties.sample agent.properties
Edit agent.properties enter the target database connection string and port number details in it
database.url=jdbc:oracle:thin:@node1.example.com:1521:orcl
server.port=7850
comment line server.jdbcDriver=<server.jdbcDriver>
uncomment line server.jdbcDriver=ojdbc7.jar oracle.xdb.jar
Start Agent
total 36
-rw-r-----. 1 oracle oinstall 9671 Oct 11 22:33 agent.properties
[oracle@veridata agent_1]$ ./agent.sh start agent.properties
Got AGENT1_HOME
total 24
109
database.url=jdbc:oracle:thin:@node2.example.com:1521:orcl
server.port=7851
Start Agent
total 36
Step-4 Validation
Agent1
Got veridata portal home -> connection configuration -> new
Specify details and click on next
Connection name: Node1_connection

Description: Node1 database connection
110
Specify the veridata agent details and click on verify once verification done click on next
Hostname or IP address: veridata.example.com {host where agent deployed}

Port:7788 {port number of AGENT}
Data source type: oracle {database type to connect}
Specify the target database schema and password and click on test connection
111
Once connection verified click on Finish
Agent2

Description: Node2 database connection

112
Specify the target database schema name and password and click on test connection
Once connection verified click on Finish
Note: If you deployed agent on same server where veridata installed then need to mention host name of
same node in connection, in our example we have installed agent in veridata server veridata.example.com
(port agent1 7850 and agent2 7850
113
5: Deploy and Configure Oracle Golden Gate veridata agent for pluggable database
Fig 5.1: Deployment Figure
Name Version
Table 5.2: Directories in an Oracle GoldenGate Veridata Installation
Directories Variable Directories Location Description of directory

ORACLE_HOME /u02/app/oracle Home of oracle FMW
VERIDATA_HOME $ORACLE_HOME/veridata Home directory of Veridata
AGENT_ORACLE_HOME $VERIDATA_HOME/agent Home of AGENT config binaries
AGENT1_HOME $ORACLE_HOME/agent1 Home of target database agent (Node1)
AGENT2_HOME $ORACLE_HOME/agent2 Home of target database agent (Node2)
Note: In this example we are not setting ORACLE_HOME variable, because we have database on same
server where veridata application installed.
Info: In this example we are deploying agent on same server where we installed veridata application, but
as per oracle document you have to deploy agent on target database server. If you want stay production
server safe, you can deploy agent on veridata server but it will take more I/O of application server.
114
• Set JAVA_HOME
• Create Directory for AGENT_HOME
• Create AGENT_HOME for Target database
• Specify target database details in Agent property files and start Agent
• Validate
Step-1 set JAVA_HOME

[oracle@veridata agent1]$ export JAVA_HOME=/usr/java/jdk1.8.0_141/jre
[oracle@veridata agent1]$ echo $JAVA_HOME
/usr/java/jdk1.8.0_141/jre
Step-2 Create Directory for AGENT_HOME

Set variable
Step-3 Configure AGENT for Target database
Go to AGENT_ORACLE_HOME
115
Set JAVA_HOME and create AGENT for target database.
Note: Set JAVA_HOME before configure veridata agent and start the agent
Step-4 Specify target database details in Agent property files and start Agent
Got AGENT1_HOME
total 24
database.url=jdbc:oracle:thin:@node1.example.com:1521/finance
server.port=7850
Start Agent
total 36
116
Got AGENT2_HOME
total 24
server.port=7851
Info: To connect the pluggable data as target database you need veridata version which support it. Only
one changes in agent property file change the database connecting string :<database_name> as
/<database_name>
Step-4 Validation
Agent1
117
Description: connecting node1.example.com server finance pluggable database
Specify the veridata agent details and click on verify, once verification done click on next

Specify the target database schema name and its password and click on test connection,
user: HR
password: ****
118
Once connection verified, click on Finish and click on OK
Agent1
Connection name: Node2

Description: connecting node1.example.com server finance pluggable database
119

Specify the target database schema and password and click on test connection,
user: HR
password: ****
120
Once connection verified, click on Finish and click on OK
Once connection configured successfully, all connection will appear in existing connection list.
Note: If you deployed agent on same server where veridata installed then need to mention host name of
same node in connection, in our example we have installed agent in veridata server veridata.example.com
(port agent1 7850 and agent2 7851)
121
6: Deploy and Configure Oracle Golden Gate veridata agent on target database server
6.1: Deployment Figure
Name Version
JAVA build 1.8.0_241-b07
Table 6.2: Node Details:
Node Details Node Directories

veridata.example.com Veridata application node
node1.example.com Source database node
node2.example.com Target database node
122
• Create Directory for veridata AGENT

• Install veridata AGENT
• Configure AGENT on target database Node
• Specify target database details in Agent property files and start Agent
• Validate
Step-1 Create Directory for AGENT_HOME (Node1 and Node2)

[root@node2 ~]# mkdir /u02
[root@node2 ~]# chown oracle:oinstall /u02
[root@node2 ~]# chmod 775 /u02
[root@node2 ~]# su - oracle
Last login: Mon Oct 19 23:28:31 EDT 2020 from 192.168.94.1 on pts/0
[oracle@node2 ~]$
[oracle@node2 ~]$ mkdir -p /u02/app/oracle
[oracle@node2 ~]$
Step-2 Install veridata AGENT (node1 and node2)
Set JAVA_HOME
[oracle@node2 ~]$ export JAVA_HOME=/usr/java/jdk1.8.0_241-amd64/jre
[oracle@node2 tmp]$ unzip -q fmw_12.2.1.4.0_ogg_Disk1_1of1.zip
123
Select Skip Auto Updates and click next
124
Specify the oracle home and click on next
Select Oracle Golden Gate Veridata Agent and click on next
125
After 100% completion click next
Read the details and click on install
126
Read the details and click on Finish
Step-3 Configure AGENT on target database Node (Node1 and Node2)
Create directory structure for AGENT binaries

[oracle@node2 ~]$ mkdir -p /u02/app/oracle/agent
Set java home

[oracle@node2 agent]$ export JAVA_HOME=/usr/java/jdk1.8.0_241-
amd64/jre
[oracle@node2 agent]$ echo $JAVA_HOME
/usr/java/jdk1.8.0_241-amd64/jre
[oracle@node2 agent]$
Configure agent
127
Configure the AGENT
[oracle@node2 agent]$ sh agent_config.sh /u02/app/oracle/agent

Successfully deployed the agent.
[oracle@node2 agent]$
Set AGENT_HOME
[oracle@node2 agent]$ export AGENT_HOME=/u02/app/oracle/agent
[oracle@node2 agent]$ echo $AGENT_HOME
/u02/app/oracle/agent
Step-4 Configure target database details in Agent property files and start Agent
Source Database(node1.example.com)
[oracle@node1 agent]$ cd $AGENT1_HOME
[oracle@node1 agent_1]$ ls -ltr
total 24
[oracle@node1 agent_1]$
[oracle@node1 agent_1]$ cp agent.properties.sample agent.properties
server.port=7850
128
Start Agent
total 36
[oracle@node1 agent_1]$ ./agent.sh start agent.properties
[oracle@node1 agent_1]$
Source Database(node2.example.com)
server.port=7852
Start Agent
total 36
[oracle@node2 agent_1]$ ./agent.sh start agent.properties
129
Note: Before start Agent check JDBC driver present in drivers’ folder <$AGENT_HOME/dirvers>
Step-5 Validate
Agent1

Description: Node1 pluggable database finance connection
Hostname or IP address: node1.example.com {host where agent deployed}

130
Specify the target database schema and password and click on test connection, Click Finish
User: HR
Password: *******
131
Click on OK
Agent2

Description: Node2 pluggable database finance connection
Hostname or IP address: node2.example.com {host where agent deployed}

132
Specify the target database schema and password and click on test connection, Click Finish
User: HR
Password: *******
Click on OK
133
After connection configuration done successfully connect details will appear Existing connection list.
134
7: Job Configuration in oracle GG veridata
• Create connection configuration for both target database

• Create Group Configuration
• Create compare pair for created Group
• Configure job
• Schema Validation before job execution
• Execute job
• Schema validation before job execution
Step-1 Create connection configuration for both target database
Node1 connection configuration (first target database)
Click on NEW button
135
Specify the connection Name and its description and click on next button
Specify the target agent details and click on Verify Button, once verification success then click on next
button.
Host Name: veridata.example.com {Host name where agent installed}

Port: 7788
Database Type: Oracle
Specify the target database schema name who used to compare the objects and test connectivity, once
connectivity looks good click on Finish button
User: HR
Password: ****
136
Once you click on Finish button new connection come into connection list
Node2 connection Configuration (Second Database)
Click on NEW button
Specify the connection Name and its description and click on next button
Specify the target agent details and click on Verify Button, once verification success then click on next
button.
Host Name: veridata.example.com {Host name where agent installed}

Port: 7850
Database Type: Oracle
137
Specify the target database schema name who used to compare the objects and test connectivity, once
connectivity looks good click on Finish button
User: HR
Password: ****
Once you click on Finish button new connection come into connection list
138
Step-2 Group configuration
Go to Home click on group configuration
Click on New
Specify the Name and Description and click on Next
Name: node1_vs_node2
Description: Group for node1 and node2 HR schema compare
Specify the Source connection and target connection
Source connection: Node1 database

Target connection: Node2 Database
Note: Source database means database which data compare with another database (target database)
139
Click on Finish and click on OK
Group name will display on Existing Group list
140
Step-3 Create compare pair for created Group
Click on group configuration -> Click on group Node1_vs_node2
Click on Go to Compare pair Configuration
Click on Manual Mapping
141
Select source database and target database schema and its tables, which you want to compare and click
Generate Compare pair
In below example we are going to compare HR schema Department table.
Click on Preview tab and click on Save
142
Compare pair Details will appear on dash board
Step-4 Configure the Job
Click on Job Configuration and click on NEW
Specify the Job name and Description and click on Next
Job Name: node1_vs_node2

Description: Node1 HR and Node2 schema compare
143
Select the group details which we created on step-3 and click on Finish
144
Click on OK Button
After job successfully create, job name will appear on existing job list
Step-5 Schema Validation before job execution
Node1 Table Status:
145
Node2 Table Status:
Step-6 Run the job
Go to Job configuration -> select Job -> Run
Before run the job, if you want to review the compare pair of job click on Retrieve Compare pair list
146
After click on Retrieve Compare pair list, it will display the list of all table under the compare pair
Click on RUN job
147
It will show the job execution status
Once Job execution Done, Click on View by Compare pair.

Job showing one record out-of-sync
148
Click on the out-of-sync button, it will display the out-of-sync rows details.
It showing infra records which are mismatch or missing in target database schema tables
Note: If you want to see the output report of Job click on report and get the job report
149
Let’s click on run repair
After run repair all status will in green color
Step-7 Schema Validation After job execution
From Node1 (Source node)
150
From Node2(Target Node)
151
8: Vericom utility
Vericom utility is a veridata command line utility. Using vericom command line interface you can
configure some automation task. It presents in veridata binaries location.
How to execute?
$ sh vericom.sh mandatory_input_parameters option_output_parameter
Let’s execute some task using vericom utility
▪ Check version
[oracle@veridata bin]$ sh vericom.sh -version
Oracle GoldenGate Veridata Command Line Interface - Version 12.2.1.4.0
190913 release build 19
[oracle@veridata bin]$
▪ Vericom help
▪ Create credential Store
Specify
wluser: veridata user created in WebLogic
wlport: veridata port number
152
[oracle@veridata bin]$vericom.sh -wluser veridata_1 -wlport 8830 -
addCredentialStore
▪ Create alias for credential

[oracle@veridata bin]$ sh vericom.sh -wluser veridata_1 -wlport 8830 -
createAlias veridata_user
▪ Display the created credential alias

[oracle@veridata bin]$ sh vericom.sh -wluser veridata_1 -wlPort 8830 -
displayAlias
▪ Update credential alias
Use the -updateAlias argument to update the password for the valid user
[oracle@veridata bin]$ sh vericom.sh -wluser veridata_1 -wlport 8830 -
updateAlias veridata_user
▪ Execute the job
Specify details:
-Wluser: veridata user create in WebLogic
-Wlport: veridata url port
- j: Job name
153
[oracle@veridata bin]$ sh vericom.sh -wluser veridata_1 -wlport 8830
-j node1_vs_node2_job
Output Showing
0 means job executed successfully
Errors:0 zero errors after job execution
Out-Of-Sync:1 it showing one record mismatch
▪ Execute job using credential alias

[oracle@veridata bin]$ sh vericom.sh -wluserAlias veridata_user -
wlport 8830 -j node1_vs_node2_job
0 means job executed successfully

Errors:0 zero errors after job execution
Out-Of-Sync:0 it showing one record mismatch
No Out-Of-Sync:1
154
▪ Delete credential alias
Table: Vericom execution Exit Status
Exit Status Description

0 The command executed successfully. If a job was run, then all rows are insync.
1 Invalid syntax
3 Provides more granularity for input errors that involve comparison flags.
For example, the following mistakes cause this error:
vericom.sh –j job1 –c address=address
In the preceding example, the-g group input is missing. It is required with -
j if -c is used.
vericom.sh –j job1 –g group1 –rd0
In the preceding example, the -rd0 flag requires –c because delta
processing applies at the compare pair level
4 The job ran successfully, but the comparison of some rows are not in sync.
5 There was a communication error with the server.
155
9: Uninstall OGG Veridata
• Stop veridata agent on target database servers

• Stop the Oracle Fusion Middleware server and process
• Using RCU remove the schema of veridata repository
• Deinstall oracle veridata
• Deinstall oracle fusion middleware
• Remove the Oracle Home Directory Manually
• Removing domain directory
Step-1 Stop veridata agent on target database servers
Go veridata portal -> connection configuration -> click on connection and get veridata agent host name
156
Go to target host name and stop veridata agent
node1.example.com
node2.example.com
157
Step-2 Stop the Oracle Fusion Middleware server and process
Stop veridata process:
Stop web logic server
158
Stop-3 Using RCU remove the schema of veridata repository
Repository schema details before drop
159
Click on next
Select drop Repository
160
Specify the details and click Next
Host Name: veridata.example.com

Port: 1521
Service Name: veridata
User Name: sys
Password: sys password
Role: sysdba
161
Check repository details and click on next
Click on OK
162
Click on OK
Click on Drop
163
Click on close
If you want see the component log you can click on log
After drop repository using RCU
Step-4 Deinstall oracle veridata
Got location /u02/app/oracle/oui/bin
164
Select the veridata need to uninstall and click Uninstall
165
Click on next
Read the veridata details and click Deinstall
166
After 100% completion click Next
Read the details and click Finish
167
Step-5 Deinstall oracle Fusion Middleware
168
Read the Oracle FMW and click Deinstall
169
Read the details and click finish
Step-6 Remove the Oracle Home Directory Manually
Go to Oracle Fusion middleware ORACLE_HOME
170

Oracle 12c Golden Gate Veridata 1610472497

Uploaded by

Copyright:

Available Formats

Oracle 12c Golden Gate Veridata 1610472497

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle 12c Golden Gate Veridata 1610472497

Uploaded by

Copyright:

Available Formats

1

0: Veridata introduction ............................................................................................................................. 3

Fig 0.1: veridata architecture

Veridata repository database: backing database to store the veridata repository

Veridata Server: veridata server where stored veridata binaries

Veridata Application: veridata web base GUI interface

Source and target database: dataset to compare the data

Fig 0.2: Deploy Agent on veridata server for target database

Fig 0.3: deploy veridata agent on target database servers

In veridata web GUI you will get below main option

User preference dashboard

Fig 1.1: veridata configuration

Table 1.1: Software Details

• Oracle 12c R1 database

Installation and configuration:

• Install Oracle Fusion Middleware (FMW) infrastructure

Step-1 oracle 12c R1 database details

SQL> create user veridata_admin

Installation and configuration:

Step-1 Install Oracle Fusion Middleware (FMW) infrastructure

[oracle@veridata tmp]$ unzip -q V78156-01_12.2.1.0.0.zip

Select ORACLE HOME for Oracle Fusion Middleware 12c

Click on next button after 100% completion

Note: Ignore the alert or yo

Select ORACLE_HOME and click on next button

Click on Install Button

Click on next button

Click on next It will create respective tablespace for repository schema

Click on Create button

Step-4 Create New domain

To create new domain for veridata execute config.sh script

[oracle@veridata u02]$ cd /u02/app/oracle/oracle_common/common/bin/

[oracle@veridata bin]$ pwd

Select the veridata Standard WebLogic Server Domain option

Vender: ORACLE (database vender)

It will validate all details about the user, click on next

Select Administrator Server option and click on Next

Click Create button

Note details about the link and click on Finish

Step-6 Check web logic URL

Step-7 Start Veridata Server

Execute veridataServer.sh and Enter web logic user and password

Connect to weblogic portal and create user for Veridata operation

Click on User and Group

Specify user details and click on ok

Name: Veridata_1 (user name)

Description: veridata admin user (user description)

Password: ******(user password)

Fig 2.1: veridata configuration

Table 2.1: Software Details

• Oracle Fusion Middleware (FMW) backing up database (12c R1)

Installation and configuration:

• Install Oracle Fusion Middleware (FMW) infrastructure

Step-1 Oracle Fusion Middleware (FWM) backing up database (12c R1)

[root@veridata tmp]# export JAVA_HOME=/usr/java/jdk1.8.0_141/jre

[root@veridata tmp]# echo $JAVA_HOME

Installation and configuration:

Step-1 Install Oracle Fusion Middleware (FMW) infrastructure

Note: create directory for ORACLE_HOME of oracle fusion middleware /u02/app/oracle

Specify the ORACLE_HOME where oracle FMW binaries