Showing posts with label Installation. Show all posts
Showing posts with label Installation. Show all posts
Thursday, December 5, 2013
GoldenGate 12.1.2.0 Install/Upgrade on OEL 6.4 x86-64
It was about time that I started working with the new release. I’ve had to upgrade my current 11g install, and since I’m on a documentation high these days, I put something together to help anyone else who wants to go through the install.
My current install is OGG 11.2.1.0.13 on Linux 64bit running against an 11.2.0.3 databases.
My current install is OGG 11.2.1.0.13 on Linux 64bit running against an 11.2.0.3 databases.
Vamanos!
Installation
1. Make a copy of your existing GoldenGate install folder after stopping all processes.
[oracle@blue gg12c]$ ls -lhtr total 578M -rwxrwx--- 1 root vboxsf 326M Dec 5 15:03 121200_fbo_ggs_Linux_x64_shiphome.zip -rwxrwx--- 1 root vboxsf 253M Dec 5 18:13 ggate.1121013.tgz [oracle@blue gg12c]$ unzip 121200_fbo_ggs_Linux_x64_shiphome.zip [oracle@blue gg12c]$ ls -lhtr total 579M drwxrwx--- 1 root vboxsf 102 Sep 25 05:59 fbo_ggs_Linux_x64_shiphome -rwxrwx--- 1 root vboxsf 276K Oct 6 18:04 OGG_WinUnix_Rel_Notes_12.1.2.0.0.pdf -rwxrwx--- 1 root vboxsf 92K Oct 6 18:04 Oracle-GoldenGate-12.1.2.0-README.doc -rwxrwx--- 1 root vboxsf 141K Oct 6 18:04 OGG_WinUnix_Rel_Notes_12.1.2.0.0.doc -rwxrwx--- 1 root vboxsf 23K Oct 6 18:04 Oracle-GoldenGate-12.1.2.0-README.txt -rwxrwx--- 1 root vboxsf 326M Dec 5 15:03 121200_fbo_ggs_Linux_x64_shiphome.zip -rwxrwx--- 1 root vboxsf 253M Dec 5 18:13 ggate.1121013.tgz [oracle@blue gg12c]$ cd fbo_ggs_Linux_x64_shiphome/ [oracle@blue fbo_ggs_Linux_x64_shiphome]$ ls -lhtr total 0 drwxrwx--- 1 root vboxsf 204 Sep 25 05:59 Disk1 [oracle@blue fbo_ggs_Linux_x64_shiphome]$ cd Disk1/ [oracle@blue Disk1]$ ls -lhtr total 4.0K drwxrwx--- 1 root vboxsf 374 Sep 25 05:59 install drwxrwx--- 1 root vboxsf 714 Sep 25 05:59 stage -rwxrwx--- 1 root vboxsf 918 Sep 25 05:59 runInstaller drwxrwx--- 1 root vboxsf 102 Sep 25 05:59 response
2. Invoke the installer, and lets get started!
[oracle@blue Disk1]$ ./runInstaller Starting Oracle Universal Installer... Checking Temp space: must be greater than 120 MB. Actual 74181 MB Passed Checking swap space: must be greater than 150 MB. Actual 8015 MB Passed Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-12-05_06-14-19PM. Please wait ...
To start, I’ll only install the GoldenGate with DB11g since thats the only instance I have installed on this server at the moment.
3. Pick your installation directories. I’ve entered the same location for the software install as my existing GG11g directory to perform an upgrade.
4. Click “yes” on this prompt. I think I know what I am doing!
4. Click “yes” on this prompt. I think I know what I am doing!
5. Review changes and click “Install”.
6. Progress is good! If you are prompted whether the directory is not empty, simply select “yes” and proceed.
7. Awesome!
Upgrade
Upgrade
8. Review the installation, and validate the binaries startup successfully.
[oracle@blue]$ pwd /u01/app/ggate [oracle@blue ggate]$ ./ggsci Oracle GoldenGate Command Interpreter for Oracle Version 12.1.2.0.0 17185003 OGGCORE_12.1.2.0.0_PLATFORMS_130924.1316_FBO Linux, x64, 64bit (optimized), Oracle 11g on Sep 25 2013 00:31:13 Operating system character set identified as UTF-8. Copyright (C) 1995, 2013, Oracle and/or its affiliates. All rights reserved. GGSCI (blue.color) 1> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT STOPPED E_GG 00:00:00 00:37:10 REPLICAT STOPPED R_GG 00:00:00 00:37:10
9. Upgrade the Checkpointtable. This needs to be done on both source and target databases!
GGSCI (blue.color) 2> dblogin userid ggate, password ggate Successfully logged into database. GGSCI (blue.color) 5> upgrade checkpointtable No checkpoint table specified. Using GLOBALS specification (ggate.checkpoint)... Successfully upgraded checkpoint table ggate.checkpoint.
10. Start the Extract
GGSCI (blue.color) 2> start e_gg Sending START request to MANAGER ... EXTRACT E_GG starting GGSCI (blue.color) 3> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT ABENDED E_GG 00:00:00 00:38:40 REPLICAT STOPPED R_GG 00:00:00 00:38:40
2013-12-05 21:40:13 ERROR OGG-01416 File ./dirdat/lt000005, with format RELEASE 11.2, does not match current format specification of RELEASE 12.1. Modify the parameter file to specify format RELEASE 11.2 or issue ETROLLOVER prior to restart.
12. Ok, my mistake :)
Modify the parameter file to specify format RELEASE 11.2 or issue ETROLLOVER prior to restart.
12.1. Option #1: Let’s make the correct parameter change and try again. Add the following to the EXTTRAIL ./dirdat/lt in the extracts parameter file.
Modify the parameter file to specify format RELEASE 11.2 or issue ETROLLOVER prior to restart.
12.1. Option #1: Let’s make the correct parameter change and try again. Add the following to the EXTTRAIL ./dirdat/lt in the extracts parameter file.
EXTTRAIL ./dirdat/lt, FORMAT RELEASE 11.2
12.2. Option #2: Start a new trail sequence by issuing a roll-over command.
GGSCI> alter extract e_gg etrollover12.2.1. Starting it again!
GGSCI (blue.color) 6> start e_gg Sending START request to MANAGER ... EXTRACT E_GG starting GGSCI (blue.color) 7> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT RUNNING E_GG 00:00:00 00:00:04 REPLICAT STOPPED R_GG 00:00:00 00:54:46
12.3. Great, now we can make the same change to the replicat’s parameter file and start it.
GGSCI (blue.color) 13> start r_gg Sending START request to MANAGER ... REPLICAT R_GG starting GGSCI (blue.color) 14> info all Program Status Group Lag at Chkpt Time Since Chkpt MANAGER RUNNING EXTRACT RUNNING E_GG 00:00:00 00:00:04 REPLICAT RUNNING R_GG 00:00:00 00:00:01
13. Excellent!! Now we are done with the installation of 12c and upgrade of 11g to 12c!
Hopefully this has been educational for you. I hope to dive further into some of the new features in 12c.
Cheers!
Cheers!
GoldenGate Veridata 11.2.1 Agent Installation
With my previous post, I completed the Server component install and moving ahead I’d like to proceed with the agent installs. The Veridata server communicates with the hosts (that are running on each target and source servers) via the Veridata Agents. There are basically two types of agents; Java based and the C-Agent. The latter is designed for NonStop SQL/MP and Enscribe databases running on the NonStop platform.
Components:
For this example, I will install the Java based agent.
Installation
1. Create the Tablespace, User, and Grant Privileges.
SQL> create tablespace ggate_data datafile '/u003/oradata/gvddvs01/ggate_ata.dbf' size 500m autoextend on;
Tablespace created.
SQL> create role veridata_role;
Role created.
SQL> grant create session to veridata_role;
Grant succeeded.
SQL> grant create table to veridata_role;
Grant succeeded.
SQL> grant create view to veridata_role;
Grant succeeded.
SQL> grant create procedure to veridata_Role;
SQL> grant create synonym to veridata_role;
Grant succeeded.
SQL> create user ggate identified by ggate default tablespace ggate_data;
User created.
SQL> grant veridata_role to ggate;
Grant succeeded.
SQL> grant unlimited tablespace to veridata_role;
Grant succeeded.
2. Create directories
greed101:(oracle) [green] $ echo $ORACLE_HOME
/u001/app/oracle/product/11.2.0
greed101:(oracle) [green] $ mkdir /u001/app/oracle/product/veridata_agent
greed101:(oracle) [green] $ mv V35569-01.zip /u001/app/oracle/product/veridata_agent
greed101:(oracle) [green] $ cd /u001/app/oracle/product/veridata_agent/
3. Unzip Binaries
greed101:(oracle) [green] $ ls -ltr
total 15664
-rw-rw-r-- 1 oracle dba 8018466 Oct 30 16:04 V35569-01.zip
drwxr-xr-x 6 oracle dba 256 Nov 7 11:16 ../
drwxr-xr-x 2 oracle dba 256 Nov 7 11:16 ./
greed101:(oracle) [green] $ unzip V35569-01.zip
Archive: V35569-01.zip
creating: agent/
creating: agent/classes/
creating: agent/drivers/
creating: agent/lib/
creating: agent/licenses/
inflating: agent/JavaAgent.jar
inflating: agent/agent.bat
inflating: agent/agent.properties.sample
inflating: agent/classes/log4j.properties
inflating: agent/drivers/gvdb2.jar
inflating: agent/drivers/gvsybase.jar
inflating: agent/drivers/ojdbc6.jar
inflating: agent/drivers/sqljdbc.jar
inflating: agent/lib/commons-dbcp-1.2.2.jar
inflating: agent/lib/commons-pool-1.3.jar
inflating: agent/lib/log4j-1.2.12.jar
inflating: agent/lib/ucp.jar
inflating: agent/licenses/Apache-LICENSE-2.0.txt
inflating: agent/licenses/notices.txt
inflating: agent/agent.sh
inflating: ogg-veridata-readme-11.2.1.0.0.doc
inflating: ogg-veridata-readme-11.2.1.0.0.txt
inflating: ogg_veridata_relnotes_11.2.1.0.0.doc
inflating: ogg_veridata_relnotes_11.2.1.0.0.pdf
greed101:(oracle) [green] $ ls -ltr
total 16416
drwxr-xr-x 6 oracle dba 4096 Nov 8 2012 agent/
-rw-r--r-- 1 oracle dba 220968 Dec 4 2012 ogg_veridata_relnotes_11.2.1.0.0.pdf
-rw-r--r-- 1 oracle dba 97280 Dec 4 2012 ogg_veridata_relnotes_11.2.1.0.0.doc
-rw-r--r-- 1 oracle dba 39424 Dec 4 2012 ogg-veridata-readme-11.2.1.0.0.doc
-rw-r--r-- 1 oracle dba 14661 Dec 4 2012 ogg-veridata-readme-11.2.1.0.0.txt
-rw-rw-r-- 1 oracle dba 8018466 Oct 30 16:04 V35569-01.zip
drwxr-xr-x 6 oracle dba 256 Nov 7 11:16 ../
drwxr-xr-x 3 oracle dba 4096 Nov 7 11:17 ./
4. Create a copy of the agent.properties.sample file as agent.properties and edit the files highlighted.
# Copyright (c) 2011, 2012, Oracle and/or its affiliates. All rights reserved.
# The server.port property is the port where the Veridata agent listens
# for connection requests.
server.port=8500
# The database.url specifies the JDBC connection URL for the database.
# Samples for all supported databases are shown below.
database.url=jdbc:oracle:thin:@greed101:1521:green
# DB2 z/OS sample database connection URL
#database.url=jdbc:veridata:db2://localhost:447;LocationName=DB2
# DB2 LUW sample database connection URL
#database.url=jdbc:veridata:db2://localhost:50000;DatabaseName=sample
# Oracle sample database connection URL
#database.url=jdbc:oracle:thin:@localhost:1521:orcl
# Uncomment the following line to change the timeout for idle connections
# in the Oracle connection pool. The value is in seconds. The default
# value in the Veridata Agent is 600 seconds.
#oracle.connection.cache.InactivityTimeout=600
# Uncomment the following line to change the time between checks for
# timeout outs in the Oracle connection pool. The value is is seconds.
# The default value in the Veridata agent is 300 seconds.
#oracle.connection.cache.PropertyCheckInterval=300
# Oracle OCI bequeath database connection URL
# The OCI libraries must available and the JDBC
# driver must match the OCI libraries.
#database.url=jdbc:oracle:oci:@
# SQL Server database connection URL
#database.url=jdbc:sqlserver://localhost:1433
# Teradata database connection URL
#database.url=jdbc:teradata://localhost/DBS_PORT=1025,CHARSET=UTF8
# Sybase database connection URL
#database.url=jdbc:veridata:sybase://localhost:5000;ApplicationName=VeriAgent;MaxPooledStatements=20
# The server.driversLocation property is the directory
# containing the JDBC driver jar file(s).
# The path is relative to the Veridata agent
# installation directory.
server.driversLocation = drivers
# The server.jdbcDriver property specifies the list of
# JDBC driver jar files. Sample lists for the
# supported databases are shown below.
#server.jdbcDriver=<server.jdbcDriver>
#For DB2 uncomment the following line:
#server.jdbcDriver=gvdb2.jar
# For Oracle uncomment the following line:
server.jdbcDriver=ojdbc6.jar
# For SQL Server uncomment the following line:
#server.jdbcDriver=sqljdbc.jar
# For Teradata uncomment the following line:
#server.jdbcDriver=terajdbc4.jar tdgssconfig.jar
#For Sybase uncomment the following line:
#server.jdbcDriver=gvsybase.jar
# The database.transaction.isolation property controls the
# transaction isolation level used during initial compare.
# The default value for Sybase, DB2, SQL Server and Teradata is
# READ_UNCOMMITTED. The only value supported for Oracle
# is READ_COMMITTED. SQL Server versions 2005 above also support
# the value SNAPSHOT which requires that ALLOW_SNAPSHOT_ISOLATION is
# enabled in the database.
#
# Confirm out of sync always uses the READ_COMMITTED
# transaction isolation level.
#database.transaction.isolation=READ_UNCOMMITTED
5. Set the JRE_HOME or JAVA_HOME parameter, and start the agent.
greed101:(oracle) [green] $ ./agent.sh start
6. Check the agent run log
greed101:(oracle) [green] $ ./agent.sh run
[VERIAGT-BOOT] INFO Looking for home directory.
[VERIAGT-BOOT] INFO Found bootstrap class in file:/u001/app/oracle/product/veridata/agent/JavaAgent.jar!/com/goldengate/veridata/agent/Bootstrap.class.
[VERIAGT-BOOT] INFO Home directory: /u001/app/oracle/product/veridata/agent
[VERIAGT-BOOT] INFO Preparing classpath.
[VERIAGT-BOOT] INFO Searching library directory /u001/app/oracle/product/veridata/agent/lib.
[VERIAGT-BOOT] INFO Driver location: /u001/app/oracle/product/veridata/agent/drivers
[VERIAGT-BOOT] INFO Drivers to load: ojdbc6.jar
[VERIAGT-BOOT] INFO Classpath:
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/JavaAgent.jar
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/lib/commons-dbcp-1.2.2.jar
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/lib/commons-pool-1.3.jar
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/lib/log4j-1.2.12.jar
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/lib/ucp.jar
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/classes
[VERIAGT-BOOT] INFO /u001/app/oracle/product/veridata/agent/drivers/ojdbc6.jar
[VERIAGT-BOOT] INFO Initializing.
[VERIAGT-BOOT] INFO Invoking startup method: public static void com.goldengate.veridata.agent.VeridataAgent.main(java.lang.String[])
Setting up agent log
Agent log redirected to /u001/app/oracle/product/veridata/agent/veridata-agent.log
7. Check the log for messages
greed101:(oracle) [green] $ cat /u001/app/oracle/product/veridata/agent/veridata-agent.log
INFO:2013-11-07 11:31:35,727 (main) - Veridata Agent Version 11.2.1.0 OGGVDT_11.2.1.0.0_PLATFORMS_121108.1625 built on Thu, 8 Nov 2012 21:21:26 -0800 [VeriAgentVersion:logVersion, line 33]
WARN:2013-11-07 11:31:35,734 (main) - The specified transaction isolation level, 'READ_UNCOMMITTED', is not support for Oracle databases [Context:init, line 222]
INFO:2013-11-07 11:31:35,881 (main) - Veridata Agent starting on greed101 port 16000 [VeridataAgent:serve, line 141]
INFO:2013-11-07 11:31:40,913 (main) - Veridata Agent Version 11.2.1.0 OGGVDT_11.2.1.0.0_PLATFORMS_121108.1625 built on Thu, 8 Nov 2012 21:21:26 -0800 [VeriAgentVersion:logVersion, line 33]
WARN:2013-11-07 11:31:40,921 (main) - The specified transaction isolation level, 'READ_UNCOMMITTED', is not support for Oracle databases [Context:init, line 222]
ERROR:2013-11-07 11:31:40,950 (main) - Veridata Agent shutting down on port 16000 due to error: Address already in use [VeridataAgent:serve, line 169]
INFO:2013-11-07 11:31:40,951 (main) - Veridata Agent stopped on port -1 [VeridataAgent:serve, line 175]
INFO:2013-11-07 11:33:23,132 (main) - Veridata Agent Version 11.2.1.0 OGGVDT_11.2.1.0.0_PLATFORMS_121108.1625 built on Thu, 8 Nov 2012 21:21:26 -0800 [VeriAgentVersion:logVersion, line 33]
INFO:2013-11-07 11:33:23,176 (main) - Veridata Agent starting on greed101 port 8500 [VeridataAgent:serve, line 141]
Tuesday, November 26, 2013
GoldenGate Veridata 11.2.1 Server Installation
Today, I’d like to share my experience with a tool that I’ve used infrequently with GoldenGate.
Veridata is Oracle’s answer to Data Validation for environments where a replication technology is utilized. In other words, the tool is agnostic (but partial) to a set Database vendors. You can install it on a variety of platforms, and a few database types.
Components:
Installation
1. Download and unzip the media from eDelivery.
2. Invoke the bash script to start the installer.
3. Click “Next”.
4. Pick your installation directory and click “Next”.
5. On the ports section, click “Next”.
6. Leave the defaults and click “Next”.
7. Enter at the account username and password. This will be used to install the tables in the repository database.
8. Of course we will chose “Oracle” :)
9. Confirm the Oracle Home (Veridata Home) location.
10. Select and Instance and click Continue. This article assumes that the Veridata installation is on the same server as its intended repository.
11. I will let the installer create a new user for me.
12. Enter the DBA
13. On the next screen, enter the oracle database user where the Veridata objects will be installed.
14. Enter the default, and temp tablespace for the above user.
15. Check the box if you want it to start Veridata after the installation.
16. Review the settings and click “Next”.
17. Progress is always good.
18. Awesome! All done.
At this point, we can log into the Veridata Server successfully!
In subsequent posts, I will discuss the other aspects such as the Veridata Agent install, Configuration, etc.
Cheers!
Veridata is Oracle’s answer to Data Validation for environments where a replication technology is utilized. In other words, the tool is agnostic (but partial) to a set Database vendors. You can install it on a variety of platforms, and a few database types.
Components:
Installation
1. Download and unzip the media from eDelivery.
[oracle@as-sandbox-n1 installs]$ cd veridata/
[oracle@as-sandbox-n1 veridata]$ ls -lhtr
total 147M
-rwxr-xr-x 1 oracle oinstall 145M Nov 8 2012 GoldenGate_Veridata_redhatAS40_x64.sh
-rw-r--r-- 1 oracle oinstall 216K Dec 4 2012 ogg_veridata_relnotes_11.2.1.0.0.pdf
-rw-r--r-- 1 oracle oinstall 95K Dec 4 2012 ogg_veridata_relnotes_11.2.1.0.0.doc
-rw-r--r-- 1 oracle oinstall 39K Dec 4 2012 ogg-veridata-readme-11.2.1.0.0.doc
-rw-r--r-- 1 oracle oinstall 15K Dec 4 2012 ogg-veridata-readme-11.2.1.0.0.txt
-rw-r--r-- 1 oracle oinstall 1.3M Oct 24 14:26 veridata-install.log
2. Invoke the bash script to start the installer.
[oracle@as-sandbox-n1 veridata]$ ./GoldenGate_Veridata_redhatAS40_x64.sh
Unpacking JRE ...
Starting Installer ...
3. Click “Next”.
4. Pick your installation directory and click “Next”.
5. On the ports section, click “Next”.
6. Leave the defaults and click “Next”.
7. Enter at the account username and password. This will be used to install the tables in the repository database.
8. Of course we will chose “Oracle” :)
9. Confirm the Oracle Home (Veridata Home) location.
10. Select and Instance and click Continue. This article assumes that the Veridata installation is on the same server as its intended repository.
11. I will let the installer create a new user for me.
12. Enter the DBA
13. On the next screen, enter the oracle database user where the Veridata objects will be installed.
14. Enter the default, and temp tablespace for the above user.
15. Check the box if you want it to start Veridata after the installation.
16. Review the settings and click “Next”.
17. Progress is always good.
18. Awesome! All done.
At this point, we can log into the Veridata Server successfully!
In subsequent posts, I will discuss the other aspects such as the Veridata Agent install, Configuration, etc.
Cheers!
Subscribe to:
Posts
(
Atom
)