http://gavinsoorma.com/2012/05/12c-management-agent-silent-installation/

We will see here how we can install as well as deployment the management agent on single or multiple target hosts from within 12c Cloud Control itself.

 From the Cloud Control Setup menu, click Add Target and then Add Targets Manually

Select Add Host Targets and click Add Host

We can provide a name for the agent deployment session activity or leave it at the default value.

 Click Add and enter the host name as well as select the appropriate platform from the dropdown list. It is recommended to use a fully qualified host name which includes the domain name as well.

 Note – to deploy on multiple host targets, do not enter multiple hosts on the same line separated by commas. Instead each host must be entered on a separate row

On the Installation Details page,  we have entered the following:

 For Installation Base Directory we have entered the absolute path to the agent base directory under which the 12c management agent software will be installed. Ensure that this directory is empty.

 The Instance Directory is where all the management agent configuration files will be stored.

 For Named Credential, either use an existing profile or create a new one. These credentials are used for setting up SSH connectivity between the OMS and the managed hosts as well as installing the Management Agent on the target hosts.

 If we leave the Privileged Delegation Setting blank, then the root scripts will not be run and we have to manually run the same after the agent installation

 We can review the agent deployment details and then click on the Deploy Agent button

We can review the progress made on each of the phases of the agent deployment operation — Initialization, Remote Prerequisite Check, and Agent Deployment.

After the agent deployment has been completed we need to do the following

1. Run the agent root.sh script as root which is located in the Management Agent home.
2. Discover and Add Targets for monitoring via Cloud Control

From the Setup menu, select Configure Auto Discovery

Select Multiple Target-Type Discovery on Single Host and then click on Configure

Select the relevant Agent Host Name and click on Configure

Under the Discovery Module, we are checking the Enabled box for Oracle Database,Listener …. and Oracle Home Discovery

Click on the Run Discovery Now button

We see that for the host where we have just run the target discovery, out of the 5 Discovered Targets, so far 3 are Managed Targets. We still need to discover the Database Instance and the Listener.

In this case the 12c  OMS host server is called linux-oem-prod and the target host where we are deploying the agent is .linux-orasql-001-dev.

In the next post we will see how we can deploy or push the 12c management agents to target hosts from 12c Cloud Control itself.

On the OMS host launch the EMCLI client

[oracle@linux-oem-prod Middleware]$ cd oms

 [oracle@linux-oem-prod oms]$ cd bin

 [oracle@linux-oem-prod bin]$ ./emcli login -username=sysman -password=xxx

Login successful

Synchronize EMCLI

[oracle@linux-oem-prod bin]$ ./emcli sync

Synchronized successfully

Check the platforms for which the Management Agent software is available on the OMS host

[oracle@linux-oem-prod bin]$ ./emcli get_supported_platforms

Getting list of platforms …

Check the logs at /u01/app/oracle/Middleware/oms/bin/agent.log

About to access self-update code path to retrieve the platforms list..

Getting Platforms list  …

———————————————–

Version = 12.1.0.1.0

 Platform = Linux x86-64

———————————————–

Platforms list displayed successfully.

Download the Management Agent software from Oracle Software Library to a temporary directory on the OMS host

[oracle@linux-oem-prod bin]$ ./emcli get_agentimage -destination=/u01/app/oracle/agent_software -platform=”Linux x86-64″ -version=”12.1.0.1.0″

Platform:Linux x86-64

Destination:/u01/app/oracle/agent_software

 === Partition Detail ===

Space free : 14 GB

Space required : 1 GB

Check the logs at /u01/app/oracle/agent_software/get_agentimage_2012-04-15_22-50-00-PM.log

Setting property ORACLE_HOME to:/u01/app/oracle/Middleware/oms

calling pulloneoffs with arguments:/u01/app/oracle/Middleware/oms/u01/app/oracle/Middleware/oms/sysman/agent/12.1.0.1.0_AgentCore_226.zip12.1.0.1.0linux_x64

Check this logs for more information: /u01/app/oracle/Middleware/oms/sysman/prov/agentpush/logs

[oracle@linux-oem-prod bin]$ cd /u01/app/oracle/agent_software

[oracle@linux-oem-prod agent_software]$ ls -l

total 230400

-rw-r—– 1 oracle oinstall 235679029 Apr 15 22:50 12.1.0.1.0_AgentCore_226.zip

-rw-r–r– 1 oracle oinstall      1805 Apr 15 22:50 get_agentimage_2012-04-15_22-50-00-PM.log

Transfer the downloaded zip file to the host where we would like to install the 12c management agent

[oracle@linux-oem-prod agent_software]$ scp -rp 12.1.0.1.0_AgentCore_226.zip oracle@linux-orasql-001-dev.dev.domain:/u01/app/oracle/agent_software

Unzip the file on the target host

Check the directory contents

[oracle@linux-orasql-001-dev agent_software]$ ls -l

total 460420

-rw-r—– 1 oracle oinstall 235679029 Apr 16 10:50 12.1.0.1.0_AgentCore_226.zip

-rwxr-xr-x 1 oracle oinstall   4979329 Apr 16 10:50 12.1.0.1.0_PluginsOneoffs_226.zip

-rw-rw-r– 1 oracle oinstall 230621327 Sep 23  2011 agentcoreimage.zip

-rwxrwxr-x 1 oracle oinstall     17150 Sep 23  2011 agentDeploy.sh

-rw-rw-r– 1 oracle oinstall        91 Sep 23  2011 agentimage.properties

-rw-rw-r– 1 oracle oinstall      3856 Sep 23  2011 agent.rsp

drwxr-xr-x 7 oracle oinstall      4096 Apr 16 10:50 plugins

-rwxr-xr-x 1 oracle oinstall       223 Apr 16 10:50 plugins.txt

-rwxr-xr-x 1 oracle oinstall    145976 Sep 23  2011 unzip

Edit the response file agent.rsp

OMS_HOST=”linux-oem-prod.dev.domain”

EM_UPLOAD_PORT=”4902″

AGENT_REGISTRATION_PASSWORD=”xxx”

AGENT_INSTANCE_HOME=”/u01/app/oracle/agent12g/agent_inst”

AGENT_PORT=”3872″

ORACLE_HOSTNAME=”linux-orasql-001-dev.dev.domain”

Run the agent deployment script

[oracle@linux-orasql-001-dev agent_software]$ ./agentDeploy.sh AGENT_BASE_DIR=/u01/app/oracle/agent12g RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp 

 Validating the OMS_HOST & EM_UPLOAD_PORT

Executing command : /u01/app/oracle/agent12g/core/12.1.0.1.0/jdk/bin/java -classpath /u01/app/oracle/agent12g/core/12.1.0.1.0/jlib/agentInstaller.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /u01/app/oracle/agent12g/core/12.1.0.1.0 /u01/app/oracle/agent_software /u01/app/oracle/agent12g -prereq

 Validating oms host & port with url: http://linux-oem-prod.dev.domain:4902/empbs/genwallet

Validating oms host & port with url: https://linux-oem-prod.dev.domain:4902/empbs/genwallet

Return status:3

Unzipping the agentcoreimage.zip to /u01/app/oracle/agent12g ….

12.1.0.1.0_PluginsOneoffs_226.zip

Executing command : /u01/app/oracle/agent_software/unzip -o /u01/app/oracle/agent_software/12.1.0.1.0_PluginsOneoffs_226.zip -d /u01/app/oracle/agent12g

 Checking the ownership of agent base directory:/u01/app/oracle/agent12g

Checking for proper ownership on the agent base directory.

Checks whether the agent base directory is owned by the agent user oracle  and that its parent directory is owned by either the agent user or root.

….

Login name is : oracle & file owner is : oracle

…………

Agent Base directory verification completed Successfully.

 Ownership check completed.

Executing command : /u01/app/oracle/agent12g/core/12.1.0.1.0/jdk/bin/java -classpath /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/OraInstaller.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/xmlparserv2.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/srvm.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/emCfg.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/jlib/agentInstaller.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /u01/app/oracle/agent12g/core/12.1.0.1.0 /u01/app/oracle/agent_software /u01/app/oracle/agent12g AGENT_BASE_DIR=/u01/app/oracle/agent12g AGENT_BASE_DIR=/u01/app/oracle/agent12g RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp

 Executing agent install prereqs…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runInstaller -ignoreSysPrereqs -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy -entryPoint oracle.sysman.top.agent_Complete -detailedExitCodes PREREQ_CONFIG_LOCATION=/u01/app/oracle/agent12g/core/12.1.0.1.0/prereqs  -J-DORACLE_HOSTNAME=linux-orasql-001-dev.dev.domain

Prereq Logs Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/prereq<timestamp>.log

Agent install prereqs completed successfully

Cloning the agent home…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runInstaller -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/u01/app/oracle/agent12g/core/12.1.0.1.0 -responseFile /u01/app/oracle/agent_software/agent.rsp  AGENT_BASE_DIR=/u01/app/oracle/agent12g AGENT_BASE_DIR=/u01/app/oracle/agent12g RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp -noconfig  ORACLE_HOME_NAME=agent12g1 -force

Clone Action Logs Location:/u01/app/oraInventory/logs/cloneActions<timestamp>.log

Cloning of agent home completed successfully

Attaching sbin home…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runInstaller -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/u01/app/oracle/agent12g/sbin ORACLE_HOME_NAME=sbin12g1 -force

Attach Home Logs Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.log

Attach home for sbin home completed successfully.

Updating home dependencies…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runInstaller -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST=”/u01/app/oracle/agent12g/sbin:/u01/app/oracle/agent12g/core/12.1.0.1.0″ -invPtrLoc /u01/app/oracle/agent12g/core/12.1.0.1.0/oraInst.loc -force

Update Home Dependencies Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestamp>.log

Update home dependency completed successfully.

Performing the agent configuration…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runConfig.sh ORACLE_HOME=/u01/app/oracle/agent12g/core/12.1.0.1.0 RESPONSE_FILE=/u01/app/oracle/agent12g/core/12.1.0.1.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

Configuration Log Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log

Agent Configuration completed successfully

The following configuration scripts need to be executed as the “root” user.

#!/bin/sh

#Root script to run

 /u01/app/oracle/agent12g/core/12.1.0.1.0/root.sh

To execute the configuration scripts:

1. Open a terminal window

2. Log in as “root”

3. Run the scripts

Agent Deployment Successful.

Agent deployment log location:

/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/agentDeploy_<timestamp>.log

Agent deployment completed successfully.

Run the root.sh script

[root@linux-orasql-001-dev ~]#  /u01/app/oracle/agent12g/core/12.1.0.1.0/root.sh

Finished product-specific root actions.

/etc exist

Finished product-specific root actions.

Check the status of the agent on the target host where it has been deployed

[oracle@linux-orasql-001-dev oracle]$ pwd

/u01/app/oracle

[oracle@linux-orasql-001-dev oracle]$ cd agent12g/

[oracle@linux-orasql-001-dev agent12g]$ cd core

[oracle@linux-orasql-001-dev core]$ cd 12.1.0.1.0/bin

[oracle@linux-orasql-001-dev bin]$ ./emctl status agent

Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0

Copyright (c) 1996, 2011 Oracle Corporation.  All rights reserved.

—————————————————————

Agent Version     : 12.1.0.1.0

OMS Version       : 12.1.0.1.0

Protocol Version  : 12.1.0.1.0

Agent Home        : /u01/app/oracle/agent12g/agent_inst

Agent Binaries    : /u01/app/oracle/agent12g/core/12.1.0.1.0

Agent Process ID  : 2678

Parent Process ID : 2631

Agent URL         : https://linux-orasql-001-dev.dev.domain:3872/emd/main/

Repository URL    : https://linux-oem-prod.dev.domain:4902/empbs/upload

Started at        : 2012-04-16 11:20:59

Started by user   : oracle

Last Reload       : (none)

Last successful upload                       : 2012-04-16 11:31:33

Last attempted upload                        : 2012-04-16 11:31:33

Total Megabytes of XML files uploaded so far : 0.02

Number of XML files pending upload           : 0

Size of XML files pending upload(MB)         : 0

Available disk space on upload filesystem    : 45.31%

Collection Status                            : Collections enabled

Last attempted heartbeat to OMS              : 2012-04-16 11:32:06

Last successful heartbeat to OMS             : 2012-04-16 11:32:06

—————————————————————

Agent is Running and Ready

In a previous note I described the process of  upgrading 10.2.0.5 Grid Control to 12c Cloud Control.

If you have installed 11g Grid Contro;l, then the process is quite similar. The real difference is the screen related to selecting Plug-ins which is something new in 12c. Plug-ins and Connectors are extensions to Grid Control to enable management of non-Oracle products and the complete ‘cloud’ stack which includes databases, middleware and even virtual servers.

We have plug-ins for Oracle like Oracle Database, Oracle Exadata, My Oracle Support, Oracle Fusion Middleware, Oracle Virtualisation and also a number of no-Oracle plug-ins like IBM DB2, Sybase etc

Packages required:

• make-3.81
• binutils-2.17.50.0.6
• gcc -4.1.1
• libaio-0.3.106
• glibc-common-2.3.4
• libstdc++ -4.1.1
• setarch-1.6
• sysstat-5.0.5
• rng-utils-2.0
• libXtst-1.0.1-3.1(x86_64)
• glibc-2.5.12

In addition, install the 32-bit version as well as the 64-bit version of glibc-devel-2.5-49

Port Requirements

•Admin Server HTTP SSL Port = 7101 – 7200

•Enterprise Manager Upload HTTP Port = 4889 – 4898

•Enterprise Manager Upload HTTP SSL Port = 1159, 4899 – 4908

•Enterprise Manager Central Console HTTP Port = 7788 – 7798

•Enterprise Manager Central Console HTTP SSL Port = 7799 – 7809

•Oracle Management Agent Port = 3872, 1830 – 1849

Repository Database requirements

10.2.0.5 database can be used as repository for cloud control

If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure that you apply the patches for bugs 10014178 and 8799099

For fresh installs, database should not have SYSMAN schema. If Database Control exists in the dtaabase chosen for the OMS repository, then we need to use the emca -deconfig dbcontrol db -repos drop command to deconfigure Database Control first.

open_cursors  needs  to be 300 to 400

processes  should be greater than  300

session_cached_cursors between 200 and 500

job_queue_interval needs to be at least 20

shared pool size minimum 600 MB

Redo log file sizes minimum 300 MB

UNDO tablespace has a minimum space of 200 MB

 stop the Gather Statistics job

For 10g use :

execute dbms_scheduler.disable(‘GATHER_STATS_JOB’,TRUE);

execute dbms_scheduler.stop_job(‘GATHER_STATS_JOB’,TRUE);

For 11g use :

execute dbms_auto_task_admin.disable(‘auto optimizer stats collection’,null,null);

Use the Enterprise Manager Prerequisite Kit utility (emprereqkit)

The emprereqkit utlity is available  in the 12c software under the directory location install/requisites/bin/emprereqkit. After installation also, it can be run if say we want to upgrade to the next higher version and now need to check if the repository meets the minimum requirements.

It will be located under the OMS_HOME at /install/requisites/bin

It is a command line utility which we can run to test if our repoitory database for the 12c OMS meets all the requirements before we start the installation.

An example of running this is shown here:

$ ./emprereqkit -executionType install -prerequisiteXMLLoc $ORACLE_HOME/install/requisites/list -dbHost oem-prod -dbPort 1521 -dbSid oem12c -dbUser SYS -dbPassword syspwd -dbRole sysdba -showPrereqs

Also …

Ensure the directory selected for the Middleware Home Location does not contain any files or subdirectories

If not already present, Oracle WebLogic Server 11g Release 1 (10.3.5) and JDK 1.6 v24 are installed in the Middleware home

A WebLogic domain called GCDomain is created

We can not only create new database objects, but also verify if the objects currently stored in the database have the right definition which is being expected by the particular patch which we were running.

The object defintions are stored in the odf and xdf files which are located under the patch sub-directory $PRODUCT_TOP/patch/115/odf and $PRODUCT_TOP/patch/115/xdf.

The Java Utility FndXdfCmp is located under the $JAVA_TOP/oracle/apps/fnd/odf2 to verify and create Database Objects, defined in a xdf-File.

To verify and create Database Objects, defined in a odf-File adodfcmp utility is used and it is located under the $AD_TOP/bin.

Using adodfcmp

This is an example of the adodfcmp command:

adodfcmp odffile=arcceh.odf mode=tables changedb=YES userid=AR/ar touser=APPS/appspwd priv_schema=SYSTEM/systempwd

odffile: name of the Object definition odf file

Mode: type of the objects to be compared or created. Valid values include tables, views, sequences

Changedb: toggle between YES and NO

userid: this is the ORACLE database user account who owns the base object

touser: this will typically be the APPS user account

priv_schema: database user account with DBA privileges – we are using SYSTEM in this case

Initially we run it with changedb=NO which will not make any changes in the database but willl just write the actions to the odf log file which we can review.

If we are satisfied with the object creation commands which will be executed, we can use changedb=YES which will cause the objects to be created or modified as the case may be in the database.

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
ODF (Object Description File) Comparison Utility
Version 11.5.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
************* Start of ODF Comparison Utility session *************
ODF Comparison Utility version: 11.5.0
ODF Comparison Utility started at: Mon Apr 23 2012 17:44:59
Reading objects from ODF file
Reading table AR_CC_ERROR_MAPPINGS …
Reading table AR_CC_ERROR_HISTORY …
*** Reading objects from AR schema

*******************************************************
The database is missing the table AR_CC_ERROR_MAPPINGS.
Create it with the statement(s):
CREATE TABLE AR.AR_CC_ERROR_MAPPINGS (CC_ERROR_CODE VARCHAR2(80) NOT NULL,
CC_ERROR_TEXT VARCHAR2(255), RECEIPT_METHOD_ID NUMBER(15) NOT NULL,
CC_TRX_CATEGORY VARCHAR2(15) NOT NULL, CC_ACTION_CODE VARCHAR2(30) NOT
NULL, NO_DAYS NUMBER, SUBSEQUENT_ACTION_CODE VARCHAR2(30), ERROR_NOTES
VARCHAR2(255), LAST_UPDATE_DATE DATE NOT NULL, LAST_UPDATED_BY NUMBER(15)
NOT NULL, LAST_UPDATE_LOGIN NUMBER(15), CREATION_DATE DATE NOT NULL,
CREATED_BY NUMBER(15) NOT NULL, OBJECT_VERSION_NUMBER NUMBER(15))
STORAGE(INITIAL 4K NEXT 128K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE
0 FREELIST GROUPS 4 FREELISTS 4 ) PCTFREE 10 PCTUSED 60 INITRANS 10
MAXTRANS 255
CREATE UNIQUE INDEX AR.AR_CC_ERROR_MAPPINGS_U1 ON AR.AR_CC_ERROR_MAPPINGS
(CC_ERROR_CODE, CC_TRX_CATEGORY, RECEIPT_METHOD_ID) LOGGING STORAGE
(INITIAL 4K NEXT 32K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0
FREELIST GROUPS 4 FREELISTS 4 ) PCTFREE 10 INITRANS 11 MAXTRANS 255
COMPUTE STATISTICS
*******************************************************
Schema is “AR”, SQL statement is:
GRANT ALL ON AR.AR_CC_ERROR_MAPPINGS TO APPS_APPLFND WITH GRANT OPTION
[did not execute above statement -- Mode changedb = NO]

CREATE OR REPLACE SYNONYM APPS_APPLFND.AR_CC_ERROR_MAPPINGS FOR
AR.AR_CC_ERROR_MAPPINGS
Schema is “AR”, SQL statement is:
GRANT ALL ON AR.AR_CC_ERROR_HISTORY TO APPS_APPLFND WITH GRANT OPTION
[did not execute above statement -- Mode changedb = NO]

CREATE OR REPLACE SYNONYM APPS_APPLFND.AR_CC_ERROR_HISTORY FOR
AR.AR_CC_ERROR_HISTORY

ODF Comparison Utility is complete.
You should check the file
/u01/home/applprod/patch/3653484/ar/patch/115/odf/adodfcmp.log
for errors.

If we now set changedb=YES, we can see that the statements are executed in the database.

The database is missing the table AR_CC_ERROR_MAPPINGS.
Create it with the statement(s):
CREATE TABLE AR.AR_CC_ERROR_MAPPINGS (CC_ERROR_CODE VARCHAR2(80) NOT NULL,
CC_ERROR_TEXT VARCHAR2(255), RECEIPT_METHOD_ID NUMBER(15) NOT NULL,
CC_TRX_CATEGORY VARCHAR2(15) NOT NULL, CC_ACTION_CODE VARCHAR2(30) NOT
NULL, NO_DAYS NUMBER, SUBSEQUENT_ACTION_CODE VARCHAR2(30), ERROR_NOTES
VARCHAR2(255), LAST_UPDATE_DATE DATE NOT NULL, LAST_UPDATED_BY NUMBER(15)
NOT NULL, LAST_UPDATE_LOGIN NUMBER(15), CREATION_DATE DATE NOT NULL,
CREATED_BY NUMBER(15) NOT NULL, OBJECT_VERSION_NUMBER NUMBER(15))
STORAGE(INITIAL 4K NEXT 128K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE
0 FREELIST GROUPS 4 FREELISTS 4 ) PCTFREE 10 PCTUSED 60 INITRANS 10
MAXTRANS 255
Statement executed.
CREATE UNIQUE INDEX AR.AR_CC_ERROR_MAPPINGS_U1 ON AR.AR_CC_ERROR_MAPPINGS
(CC_ERROR_CODE, CC_TRX_CATEGORY, RECEIPT_METHOD_ID) LOGGING STORAGE
(INITIAL 4K NEXT 32K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0
FREELIST GROUPS 4 FREELISTS 4 ) PCTFREE 10 INITRANS 11 MAXTRANS 255
COMPUTE STATISTICS
Statement executed.

Using FndXdfCmp

This is the usage:

adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp [Oracle_Schema] [Oracle_Password] \
[apps_schema] [apps_password] [jdbc protocol] [JDBC_Connect_String] [Object Type] \
[full path to xdf file] [full path of $FND_TOP/patch/115/xdf/xsl

Note: ChangeDb can also be specified as ChangeDb=y/n. The default is y so objects will be created in the database.

For example:

applprod@/u01/home/applprod $ adjava -mx512m -nojit oracle.apps.fnd.odf2.FndXdfCmp fa fa apps appspwd thin \
test-4:1523:CLMTS10G all fa_inquiry_trx_gt.xdf $FND_TOP/patch/115/xdf/xsl

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Java
Version 11.5.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Reading product information from file…
Reading language and territory information from file…
Reading language information from applUS.txt …
Temporarily resetting CLASSPATH to:
“/u02/prod/clmfinpr/clmfinprappl/ad/11.5.0/java/adjri.zip:/u01/home/applprod/patch/jdk16/jdk1.6.0_20/jre/lib/rt.jar:/u01/home/applprod/patch/jdk16/jdk1.6.0_20/lib/dt.jar:/u01/home/applprod/patch/jdk16/jdk1.6.0_20/lib/tools.jar:/u01/home/applprod/patch/jdk16/jdk1.6.0_20/jre/lib/charsets.jar:/u02/prod/clmfinpr/clmfinprcomn/java/appsborg2.zip:/u02/prod/clmfinpr/clmfinprora/8.0.6/forms60/java:/u02/prod/clmfinpr/clmfinprcomn/java”
Calling /u01/home/applprod/patch/jdk16/jdk1.6.0_20/bin/java …
================================================================================
Applying XDF file : fa_inquiry_trx_gt.xdf
================================================================================
Copyright (c) 2003 Oracle Corporation
Redwood Shores, California, USA
XDF(XML Object Description File) Comparison Utility
Version 1
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.

Creating Table in the XDF file
Table Name is FA_INQUIRY_TRX_GT
Table does not exist in the target database
Executing create Statement
Create Statement is

CREATE GLOBAL TEMPORARY TABLE “FA”.”FA_INQUIRY_TRX_GT”
( “TRANSACTION_HEADER_ID” NUMBER(15,0),
“ASSET_ID” NUMBER(15,0),
“BOOK_TYPE_CODE” VARCHAR2(15)
) ON COMMIT PRESERVE ROWS
Start time for statement above is Tue Apr 24 10:49:10 WST 2012
End time for statement above is Tue Apr 24 10:49:10 WST 2012
Executing grants on FA_INQUIRY_TRX_GT to APPS_APPLFND
GRANT ALL ON FA.FA_INQUIRY_TRX_GT TO APPS_APPLFND WITH GRANT OPTION
Creating synonym FA_INQUIRY_TRX_GT for FA.FA_INQUIRY_TRX_GT
Synonym created
Index hashcode(s) extracted from the XDF.
Hashcodes generated for DB indexes.
Index FA_INQUIRY_TRX_GT_N2 does not exist in FA.
CREATE INDEX “FA”.”FA_INQUIRY_TRX_GT_N2″ ON “FA”.”FA_INQUIRY_TRX_GT” (“ASSET_ID”, “BOOK_TYPE_CODE”)
Start time for statement above is Tue Apr 24 10:49:11 WST 2012
End time for statement above is Tue Apr 24 10:49:11 WST 2012
Index FA_INQUIRY_TRX_GT_N2 Created
Index FA_INQUIRY_TRX_GT_N1 does not exist in FA.
CREATE INDEX “FA”.”FA_INQUIRY_TRX_GT_N1″ ON “FA”.”FA_INQUIRY_TRX_GT” (“TRANSACTION_HEADER_ID”)
Start time for statement above is Tue Apr 24 10:49:11 WST 2012
End time for statement above is Tue Apr 24 10:49:11 WST 2012
Index FA_INQUIRY_TRX_GT_N1 Created

If we are having a physical standby Data Guard environment, then we can easily offload the potentially I/O and CPU intensive backup process required for creating these clone or duplicate databases to the standby site.

Here are a few examples of using the physical Standby database in a Data Guard environment to create a clone of the primary production database.

In the first example we use RMAN to perform the backup and restore and in the second example we are using OS commands to just copy files ONLINE from Standby host to the target host.

Note that in 11g, we can take the backup of the control file from the Standby database. In 10g, we have to take the backup of the controlfile from the primary database.

Metalink states that:

From 11G onwards controlfile backups are interchangible. This is applicable for Physical standby only.

For example the controlfile backup taken on standby(the control file type is STANDBY) can be restored directly on primary and the controlfile type automatically converted as CURRENT.

Method 1) Using RMAN to take a backup from Standby Database (same DB_NAME)

On Standby

SQL> recover managed standby database cancel;
Media recovery complete.

[oracle@kens-orasql-001-dev oracle]$ rman target /

Recovery Manager: Release 11.2.0.1.0 – Production on Wed Apr 18 11:15:00 2012

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

connected to target database: HDESK11G (DBID=1866661199, not open)

RMAN> backup as compressed backupset database plus archivelog format ‘/u01/app/oracle/bkp_db.%U’;

Starting backup at 18-APR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=1300 RECID=376 STAMP=780913484
input archived log thread=1 sequence=1301 RECID=377 STAMP=780913486
input archived log thread=1 sequence=1302 RECID=379 STAMP=780913792
input archived log thread=1 sequence=1303 RECID=378 STAMP=780913792
input archived log thread=1 sequence=1304 RECID=380 STAMP=780913805
input archived log thread=1 sequence=1305 RECID=381 STAMP=780913812
input archived log thread=1 sequence=1306 RECID=382 STAMP=780913822
input archived log thread=1 sequence=1307 RECID=383 STAMP=780914242
input archived log thread=1 sequence=1308 RECID=384 STAMP=780914245
input archived log thread=1 sequence=1309 RECID=386 STAMP=780914858
input archived log thread=1 sequence=1310 RECID=385 STAMP=780914858
input archived log thread=1 sequence=1311 RECID=387 STAMP=780914870
input archived log thread=1 sequence=1312 RECID=388 STAMP=780914872
channel ORA_DISK_1: starting piece 1 at 18-APR-12
channel ORA_DISK_1: finished piece 1 at 18-APR-12
piece handle=/u01/app/oracle/bkp_db.0pn8nrhf_1_1 tag=TAG20120418T105335 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07
Finished backup at 18-APR-12

Starting backup at 18-APR-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting compressed full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=/u01/oradata/HDESK11G/hdesk_data01.dbf
input datafile file number=00001 name=/u01/oradata/HDESK11G/system01.dbf
input datafile file number=00002 name=/u01/oradata/HDESK11G/sysaux01.dbf
input datafile file number=00003 name=/u01/oradata/HDESK11G/undotbs101.dbf
input datafile file number=00007 name=/u01/oradata/HDESK11G/common_data01.dbf
input datafile file number=00004 name=/u01/oradata/HDESK11G/users01.dbf
input datafile file number=00008 name=/u01/oradata/HDESK11G/testme01.dbf
input datafile file number=00005 name=/u01/oradata/HDESK11G/example01.dbf
channel ORA_DISK_1: starting piece 1 at 18-APR-12
channel ORA_DISK_1: finished piece 1 at 18-APR-12
piece handle=/u01/oradata/HDESK11G/FRA/HDESK11G2/backupset/2012_04_18/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp tag=TAG20120418T105342 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:05:15
Finished backup at 18-APR-12

Starting backup at 18-APR-12
using channel ORA_DISK_1
specification does not match any archived log in the repository
backup cancelled because there are no files to backup
Finished backup at 18-APR-12

Starting Control File and SPFILE Autobackup at 18-APR-12
piece handle=/u01/oradata/HDESK11G/FRA/HDESK11G2/autobackup/2012_04_18/o1_mf_s_780922291_7rwchkow_.bkp comment=NONE
Finished Control File and SPFILE Autobackup at 18-APR-12

Now copy the RMAN backup pieces from the Standby site to the Target site. Note that if the directory structure where we have taken the backup on standby differs on the target server where we are performing the restore, then we have to use the CATALOG command to register those backups in the controlfile.

On Target

RMAN> restore controlfile from ‘/u01/app/oracle/ o1_mf_s_780922291_7rwchkow_.bkp’;

Starting restore at 18-APR-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=134 device type=DISK

channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/u01/app/oracle/oradata/HDESK11G/control01.ctl
output file name=/u01/app/oracle/oradata/HDESK11G/control02.ctl
Finished restore at 18-APR-12

RMAN> alter database mount;

RMAN> catalog backuppiece ‘/u01/app/oracle/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp’;

using target database control file instead of recovery catalog
cataloged backup piece
backup piece handle=/u01/app/oracle/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp RECID=9 STAMP=780923733

RMAN> restore database;

Starting restore at 18-APR-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=125 device type=DISK

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to /u01/app/oracle/oradata/HDESK11G/system01.dbf
channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/HDESK11G/sysaux01.dbf
channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/HDESK11G/undotbs101.dbf
channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/HDESK11G/users01.dbf
channel ORA_DISK_1: restoring datafile 00005 to /u01/app/oracle/oradata/HDESK11G/example01.dbf
channel ORA_DISK_1: restoring datafile 00006 to /u01/app/oracle/oradata/HDESK11G/hdesk_data01.dbf
channel ORA_DISK_1: restoring datafile 00007 to /u01/app/oracle/oradata/HDESK11G/common_data01.dbf
channel ORA_DISK_1: restoring datafile 00008 to /u01/app/oracle/oradata/HDESK11G/testme01.dbf
channel ORA_DISK_1: reading from backup piece /u01/oradata/HDESK11G/FRA/HDESK11G2/backupset/2012_04_18/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp
channel ORA_DISK_1: errors found reading piece handle=/u01/oradata/HDESK11G/FRA/HDESK11G2/backupset/2012_04_18/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp
channel ORA_DISK_1: failover to piece handle=/u01/app/oracle/o1_mf_nnndf_TAG20120418T105342_7rwc5pf4_.bkp tag=TAG20120418T105342
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:04:35
Finished restore at 18-APR-12

RMAN> recover database noredo;

Starting recover at 18-APR-12
using channel ORA_DISK_1

Finished recover at 18-APR-12

RMAN> alter database open resetlogs;

FAILED HERE !!

Alert log showed:

LGWR: Primary database is in MAXIMUM AVAILABILITY mode
LGWR: Destination LOG_ARCHIVE_DEST_1 is not serviced by LGWR
LGWR: Minimum of 1 LGWR standby database required
Errors in file /u01/app/oracle/diag/rdbms/hdesk11g/HDESK11G/trace/HDESK11G_lgwr_7926.trc:
ORA-16072: a minimum of one standby database destination is required
Errors in file /u01/app/oracle/diag/rdbms/hdesk11g/HDESK11G/trace/HDESK11G_lgwr_7926.trc:
ORA-16072: a minimum of one standby database destination is required
LGWR (ospid: 7926): terminating the instance due to error 16072
Wed Apr 18 11:40:30 2012
ARC1 started with pid=19, OS id=8008
Instance terminated by LGWR, pid = 7926

This error was because in the original environment Standby Database was running in MAXIMUM AVAILABILITY mode and it needs a valid destination for LOG_ARCHIVE_DEST_2. Changed it to maximum performance even though there is no Data Guard involved in the restored database. But control file which was restored belonged to a Data Guard Primary database (even though we took it from Standby) – this is the difference in 11g.

SQL> startup mount;
ORACLE instance started.

Total System Global Area 2137886720 bytes
Fixed Size 2215064 bytes
Variable Size 553649000 bytes
Database Buffers 1577058304 bytes
Redo Buffers 4964352 bytes
Database mounted.

SQL> alter database set standby database to maximize performance;

Database altered.

SQL> alter database open;

Database altered.

SQL> select name from v$database;

NAME
———
HDESK11G

Method 2) Using Online ‘Hot’ Operating System level copy of database files of the standby database (Changing DB_NAME)

On Primary

SQL> alter database backup controlfile to trace;

Copy trace file to target site and edit as required

SQL> alter database begin backup;

Database altered.

Create a test table as SYSTEM (just to test the process)

SQL> conn system/
Connected.

SQL> create table test_me
2 as select * from all_objects;

Table created.

SQL> alter system switch logfile; >>> doing this because we are using MAXIMUM PERFORMANCE mode

System altered.

ON STANDBY

scp all the data files to the target server

[oracle@kens-orasql-002 HDESK11G]$ scp -rp *.dbf oracle@kens-orasql-001-dev:/u01/app/oracle/oradata/CLONEDB

ON PRIMARY

SQL> alter database end backup;

Database altered.

SQL> alter system switch logfile;

System altered.

ON STANDBY

scp all the archivelog files generated while copy in progress. Ensure last archive log file is present after the alter database end backup command is issues on primary

[oracle@kens-orasql-002 2012_04_19]$ scp -rp *.arch oracle@kens-orasql-001-dev:/u01/app/oracle/oradata/CLONEDB/arch
oracle@kens-orasql-001-dev’s password:
o1_mf_1_1313_7rywxhl0_.arc 100% 108MB 27.0MB/s 00:04
o1_mf_1_1314_7ryx9660_.arc 100% 387KB 387.0KB/s 00:00
o1_mf_1_1315_7ryy5322_.arc 100% 9807KB 9.6MB/s 00:00
o1_mf_1_1316_7ryyjztx_.arc 100% 359KB 358.5KB/s 00:00

ON TARGET

Create the controlfile

Startup nomount – note init.ora file is having new database name

[oracle@kens-orasql-001-dev dbs]$ export ORACLE_SID=CLONEDB
[oracle@kens-orasql-001-dev dbs]$ sqlplus sys as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Thu Apr 19 10:48:47 2012

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Enter password:
Connected to an idle instance.

SQL> startup nomount
ORACLE instance started.

Total System Global Area 2137886720 bytes
Fixed Size 2215064 bytes
Variable Size 553649000 bytes
Database Buffers 1577058304 bytes
Redo Buffers 4964352 bytes

SQL> @crectl

Control file created.

Apply the archive log files and recover the database

SQL> !ls -lrt /u01/app/oracle/oradata/CLONEDB/arch/
total 843700
-rw-r—– 1 oracle oinstall 113127424 Apr 19 10:08 o1_mf_1_1313_7rywxhl0_.arc
-rw-r—– 1 oracle oinstall 396288 Apr 19 10:15 o1_mf_1_1314_7ryx9660_.arc
-rw-r—– 1 oracle oinstall 10042368 Apr 19 10:29 o1_mf_1_1315_7ryy5322_.arc
-rw-r—– 1 oracle oinstall 367104 Apr 19 10:36 o1_mf_1_1316_7ryyjztx_.arc

SQL> recover database until cancel using backup controlfile;

ORA-00279: change 23286334 generated at 04/18/2012 10:51:31 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/CLONEDB/arch/1_1313_764155537.arch
ORA-00280: change 23286334 for thread 1 is in sequence #1313

Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1313_7rywxhl0_.arc
ORA-00279: change 23395781 generated at 04/19/2012 10:08:47 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/CLONEDB/arch/1_1314_764155537.arch
ORA-00280: change 23395781 for thread 1 is in sequence #1314
ORA-00278: log file
‘/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1313_7rywxhl0_.arc’ no longer
needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1314_7ryx9660_.arc
ORA-00279: change 23396254 generated at 04/19/2012 10:15:02 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/CLONEDB/arch/1_1315_764155537.arch
ORA-00280: change 23396254 for thread 1 is in sequence #1315
ORA-00278: log file
‘/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1314_7ryx9660_.arc’ no longer
needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1315_7ryy5322_.arc
ORA-00279: change 23397491 generated at 04/19/2012 10:29:55 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/CLONEDB/arch/1_1316_764155537.arch
ORA-00280: change 23397491 for thread 1 is in sequence #1316
ORA-00278: log file
‘/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1315_7ryy5322_.arc’ no longer
needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}
/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1316_7ryyjztx_.arc
ORA-00279: change 23397950 generated at 04/19/2012 10:36:15 needed for thread 1
ORA-00289: suggestion :
/u01/app/oracle/oradata/CLONEDB/arch/1_1317_764155537.arch
ORA-00280: change 23397950 for thread 1 is in sequence #1317
ORA-00278: log file
‘/u01/app/oracle/oradata/CLONEDB/arch/o1_mf_1_1316_7ryyjztx_.arc’ no longer
needed for this recovery

Specify log: {=suggested | filename | AUTO | CANCEL}
cancel
Media recovery cancelled.

SQL> alter database open resetlogs;

Database altered.

SQL> select name from v$database;

NAME
———
CLONEDB

SQL> select name from v$datafile;

NAME
——————————————————————————–
/u01/app/oracle/oradata/CLONEDB/system01.dbf
/u01/app/oracle/oradata/CLONEDB/sysaux01.dbf
/u01/app/oracle/oradata/CLONEDB/undotbs101.dbf
/u01/app/oracle/oradata/CLONEDB/users01.dbf
/u01/app/oracle/oradata/CLONEDB/example01.dbf
/u01/app/oracle/oradata/CLONEDB/hdesk_data01.dbf
/u01/app/oracle/oradata/CLONEDB/common_data01.dbf
/u01/app/oracle/oradata/CLONEDB/testme01.dbf

8 rows selected.

SQL> select member from v$logfile;

MEMBER
——————————————————————————–
/u01/app/oracle/oradata/CLONEDB/redo03.log
/u01/app/oracle/oradata/CLONEDB/redo02.log
/u01/app/oracle/oradata/CLONEDB/redo01.log

Check the table we created on primary is also present on clone database

SQL> conn system
Enter password:
Connected.

SQL> select count(*) from test_me;

COUNT(*)
———-
74864

Broadly speaking at a high level, these are the main steps involved in the 12c upgrade.

• Decide on what upgrade you are going to follow. I have used the 2-System Upgrade approach which although requires an additional server for the 12g OMS, is non-intrusive and does not affect the existing 10g OEM environment.
• Apply the pre-upgrade console patch on existing 10g OEM – this will provide us the interface in the existing 10g OEM Grid Control for performing many of the upgrade tasks. Note the 10g OMS needs to down for this.
• Provide information about the host where the 12c upgrade is going to take place.
• Download the 12c Grid Control software and plug-ins and stage them on the server which is going to host the 12c OMS
• Register the software and plug-ins with Grid Control
• Analyze the existing management agents and determine which agents are having an upgradeable status – note that currently there are no Windows 12c Management Agents available. On Metalink it is mentioned that Windows 12c agents will be available by June 2012.
• Backup the existing 10g Repository Database and restore it on the same host or another host. In our case, I have restored the 10.2.0.5 OEM repository database on the server which will host the 12c OMS. So both repository database and OMS are on the same host. We can perform an upgrade of the database here if we so desire, but 10.2.0.5 repository database is supported with the 12c Grid Control.
• Install 12c Enterprise Manager Cloud Control and upgrade the Management Repository in the database you backed up and restored.
• Link the earlier release of the Management Repository with the upgraded Management Repository.
• Upgrade the management agents by deploying the 12c agent software on the hosts where we are upgrading the existing 10g agent. All these tasks are done from the Upgrade Console in the 10g OEM Grid Control. We can do this in a piecemeal manner and do not have to upgrade all the agents to 12c in one go. So we will have both the 10g and 12c Grid Control environments running side by side until we have migrated all the 10g agents to 12c. Note that the 12c OMS can only communicate with the 12c agent and not any other agent version.
• Generate a health report and check the readiness of the redeployed Management Agents. Verify and sign off the health report.
• Switch over the old Management Agent to the newly deployed 12c agent
• Note – Ensure that you have the Enterprise Manager Cloud Control software released in February 2012 – Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) (With Bundle Patch 1).

Read the note: Upgrading Grid Control 10.2.0.5 to OEM 12c Cloud Control

In case of a RAC to RAC clone, with RMAN Duplicate we first create a target or duplicate single instance database and then convert the single instance database to a RAC database.

While the note deals with an Oracle 10.2.0.4 database, the same procedure can be used for an 11g database. However, note that in 11g we now have the Duplicate From Active enhanced feature as well.

Read the document …..

The templates are available from the Oracle E-Delivery web site and are available in both OEL 32bit Linux as well as 64bit Linux.

While we are demonstrating a test or development RAC setup where a single Oracle VM server is hosting both the guest nodes, a ‘Production’ type envrionment is also supported using the Oracle VM Templates where we have multiple OVM Servers and the shared disks are configured as ‘phy’ devices which are then passed on to the guest Oracle VM’s. So there are a number of Oracle VM Servers in this case.

In this test environment, however, the shared disk is configured as ‘file’ devices and both guests can run on the same Oracle VM Server.

In other words we have one single DOM-0 and we use files located in the DOM-0 to emulate the shared disks for the Oracle RAC ‘cluster’ nodes running in DOM-U.

The template requires about 40 Gb of disk space and assumes that we have at least 4 Gb of RAM available. In our test case, we have allocated 4 Gb of RAM to each Virtual Machine.

The template assumes the following are already in place.

a) We have already installed Oracle VM Server (we have used OVM 2.2)
b) We have already installed and configured Oracle VM Manager (OVM 2.2)
c) allocated 7 unused IP addresses and registered in our DNS

Assuming a two node RAC cluster, that is

2 IP’s for the public host names
2 IP’s for the VIP
3 IP’s for the SCAN

The high level steps involved would be:

• Download the zip files from Oracle E-Delivery site
  
• Import the Virtual Machine template into OVM
  
• Create the ASM shared storage

• Create the VM’s from the 11gR2 RAC template
• Add the shared disks to the VM’s
• Complete the first boot interview
• run the script buildcluster.sh which will install the 11g R2 Grid Infrastructure and database software and also create the ORCL RAC database
• Customize as required
  

Some resources

• Installing OVM Manager 2.2

• Installing OVM Server 2.2

• RAC OVM Templates Overview

• RAC 11g Release 2 (11.2.0.2.0) Oracle VM templates Test and Development Configuration”
  

We need to unzip the 3 files we have downloaded fron the E-Delivery web site and then also extract the 11gR2 RAC template.

This is all done in the /OVS/seed_pool/ directory on the OVM Server

[root@kens-ovm-002 OVS]# mv p10113572*.zip ./tmp

[root@kens-ovm-002 OVS]# cd tmp

[root@kens-ovm-002 tmp]# ls
p10113572_10_Linux-x86-64_1of3.zip  p10113572_10_Linux-x86-64_2of3.zip  p10113572_10_Linux-x86-64_3of3.zip

[root@kens-ovm-002 tmp]# unzip -q p10113572_10_Linux-x86-64_1of3.zip
[root@kens-ovm-002 tmp]# unzip -q p10113572_10_Linux-x86-64_2of3.zip
[root@kens-ovm-002 tmp]# unzip -q p10113572_10_Linux-x86-64_3of3.zip

[root@kens-ovm-002 tmp]# cd /OVS/seed_pool/

[root@kens-ovm-002 seed_pool]# tar xzf /OVS/tmp/OVM_EL5U4_X86_64_11202RAC_PVM-1of2.tgz

[root@kens-ovm-002 seed_pool]# cat /OVS/tmp/OVM_EL5U4_X86_64_11202RAC_PVM-2of2-parta.tgz /OVS/tmp/OVM_EL5U4_X86_64_11202RAC_PVM-2of2-partb.tgz | tar xzf -

Importing the Virtual Machine Template

We will now import this template using OVM Manager.

Resources >> Virtual Machine Templates and click on Import button

Our template is stored in the /OVS/seed_pool on our OVM Server machine. So we select the option “Select from Server Pool (Discover and Register)”

From the Virtual Machine Template Name drop down list select the 11gR2 RAC PVM.

In the Virtual Machine System Password field, we need to enter the root password. The template assumes the root password to be ‘ovsroot’ and if we set it to anything else as in our case, we got an error.

But there is a configuration file we can edit to change the default root password to whatever we desire and I will show you how that’s done in a bit.

Click on the Confirm button

We will see that the status of the Virtual Machine Template is now changed to “Importing”

We will see that the status of the Virtual Machine Template is now changed to “Pending”

We need to click on the Approve button

We see that the template status has now changed to “Active” and we can now use this template to set up our 11g R2 RAC environment.

Create the shared ASM disks

Resources >> Shared Virtual Disks >> Create

Select the appropriate Server Pool Name and Group Name.

We will be creating 5 shared virtual disks – ASM1,ASM2,ASM3, ASM4 and ASM5 each of size 2048 Mb or 2 Gb

Click on Confirm

After the first disk ASM1 has been created, click on the Create button and similarly create the other ASM disks in the same manner

We should now see all the five Shared Virtual Disks with status Active

Create the Virtual Machines from the imported 11gR2 RAC template

Click on the Create Virtual Machine button

Select the option Create virtual machine based on virtual machine template

Select the template OVM_EL5U4_X86_64_11202RAC_PVM

Important

Do not forget to add a SECOND Virtual Network Interface – in this case the name is VIF1 and Bridge name is xenbr1

Keep a note of the console password as we will need to enter this at a later stage

Note the status of the Virtual Machine is now ‘Creating’

After the Virtual Machine is created, it is in a Powered Off state

Click on the Configure tab as we would like to change the Memory Size of this VM from 2 Gb to 4 Gb

Change the Maximum Memory Size and Memory Size to 4096

Change the Memory Size of the second VM as well to 4096 MB and now we will see that both the VM’s have been created and are in the Powered Off state

Attach the Shared Disks to both the VM’s

Select one of the Virtual Machines and click on the Configure tab

Select the Storage tab and then the Attach/Detach Shared Virtual Disk

We see the 5 Shared Virtual Disks which we had earlier created – Click on Move All

We can now see that the 5 ASM Shared Disks have been attached to the VM and the disk status is Active

Repeat the same process for the second VM and attach the same 5 ASM disks to that Virtual Machine as well

Complete the First Boot Interview

Power On both the VM’s

Once the machines are powered on, click on the Console tab and launch both the consoles

This is called the First Boot Interview stage.

On the first screen we enter YES and on the second screen we enter NO.

Only after we have entered NO on the second console does the install continue.

We need to now provide the IP’s for the Public, Private and Virtual hostnames

We need to enter the SCAN name for this cluster. Note – we should have registered the SCAN in our DNS already and have assigned 3 unused IP addresses to the SCAN

Install Grid Infrastructure and Oracle 11g R2 RAC

We now need to run the buildcluster.sh script. This needs to be on only ONE of the VM’s – the one we have designated to be the first node of the cluster.

Note – because we had not used the standad root password ovsroot, we find that the script has failed becuase it tries to establish a passwordless ssh session which fails.

We needed to edit the /u01/racovm/params.ini file and change the entry for ROOTUSERPASSWORD to the one we want.

Have a read through of the params.ini file as it is through this file that we can add a lot of customisation to the RAC cluster build.

While the RAC installation is in progress, we can monitor the same by doing a tail -f of the progress-racovm.out file located on /tmp

]]> http://gavinsoorma.com/2011/11/3366/feed/ 0 http://gavinsoorma.com/2011/11/oracle-11g-fusion-middleware-installation-on-linux/ http://gavinsoorma.com/2011/11/oracle-11g-fusion-middleware-installation-on-linux/#comments Fri, 25 Nov 2011 00:31:59 +0000 Gavin Soorma http://gavinsoorma.com/?p=3310 This note describes the (long) process of installing an 11g Fusion Middleware environment with Forms, Reports, Discoverer and Portal on an Oracle Enterprise Linux 5.6 64 Bit platform.

If you are not using Oracle Portal , then you do not need to configure Identity Management and Single Sign On which is a real big pain as there is no 11g SSO as yet and we have to install, upgrade and configure 10g SSO/DAS as well with a number of patches.

These are the top level steps:

• Run inspre11.pls (with -op1)
• Install SSO MRCA 10.1.4.3.1 on Windows – not available for 64 bit Linux – change compatibility to Windows XP since we have installed on Windows 7 client PC (ofm_sso_rcu_win_10.1.4.3.1_disk1_1of1.zip)
• Reset the ODS Password
• Run inspre11.pls (with -op2)
• Install SSO/DAS 10.1.4.0.1 (into a NEW Oracle Home – this must be a different Oracle Home from OID/DIP 11gR1)
• Apply patch 688088 (p6880880_101000_Linux-x86-64.zip)
• Apply Patch 5649850 for release 10.1.0.5 (p5649850_10105_GENERIC.zip)
• Apply patch 6265268 (p6265268_101430_GENERIC.zip)
• Upgrade SSO/DAS to 10.1.4.3 (p7215628_101430_LINUX.zip)
• Run inspre11.pls (with -op3)

Read the note:

11g-Fusion-Middleware-Installation-Part-1.doc

11g-Fusion-Middleware-Installation-Part-2.doc

A number of Metalink support notes discuss this topic like:

Database Tablespace Full Metric Alerts not Generated In Grid Control [ID 357049.1]
Troubleshooting a Database Tablespace Used(%) Alert problem [ID 403264.1]
Oracle Recommended Patches For Tablespace Monitoring using the Tablespace Space Used % metric [ID 849498.1]

What happens if autoextend is turned on but in some cases we have specified an upper limit for the MAXSIZE parameter or have just left it to UNLIMITED? How will OEM handle those cases?

To clarify things, OEM alert notification mechanism will query the DBA_TABLESPACE_USAGE_METRICS view to determine the Used % in a tablespace in relation to the Warning and Critical thresholds which have been set. This is true for Oracle 10g and above and if we are using Locally Managed tablespaces.

It does not look at DBA_FREE_SPACE or DBA_TABLESPACES for that matter to determine how much of free space is there in a tablespace. In fact many of us had these custom scripts which query these two views and in case of databases which had many tablespaces like an Oracle Applications environment, this query could take a long time to return the results and was quite a ‘costly’ query.

It is important to note that this metric takes into consideration the available disk space into which the tablespace’s datafile can extend if autoextend is turned on.

With a 8k block size, on most Unix systems the maximum a datafile can extend upto with autoextend turned on is 32 Gb. In that case the DBA_TABLESPACE_USAGE_METRICS view will use 32 Gb as the basis for calculating the available free space in the tablespace because if a tablespace consists of one datafile, that is the maximum size the tablespace can grow to.

In the figure below of the OEM Tablespaces screen (Database Instance Home Page –> Administration –> Tablespaces), we see some tablespaces which have used space greater 95%, but we have not received any alert from OEM even though the Critical threshold has been crossed.

Why is that the case?

This is because of the AUTOEXTEND setting. In the figure above, some tablespaces have datafiles which have autoextend turned on and some do not have autoextend enabled.

In this case, the datafile of the SYSTEM tablespace does have autoextend turned on, and even though the SYSTEM tablespace is 99% full, OEM does not consider it a candidate for an alert notification because the DBA_TABLESPACE_USAGE_METRICS view shows it only as 15.71% used.

SQL>  SELECT TABLESPACE_NAME TBSP_NAME
  2  , USED_SPACE
  3  , TABLESPACE_SIZE TBSP_SIZE
  4  , USED_PERCENT
  5  FROM SYS.DBA_TABLESPACE_USAGE_METRICS
  6  order by 4;

TBSP_NAME                      USED_SPACE  TBSP_SIZE USED_PERCENT
—————————— ———- ———- ————
…
…

SYSTEM                              91512     582427   15.7121837

So how did Oracle compute this 15.71% used figure? (91512/582427*100)

Note the USED_SPACE and TBSP_SIZE columns are in blocks - in this case the DB_BLOCK_SIZE of the database is 8k or 8192 bytes.

The maximum size which the file can extend upto via autoextend is 582427 blocks or 4450 Mb

582427 (blocks) *8192 (each block size) / 1048576 (to convert to MB) = 4450 MB

The SYSTEM tablespace is made up of one datafile and that datafile is about 714 MB used. (91512* 8192/1048576)

Let us create a tablespace TESTME of size 50 Mb.

SQL>  create tablespace testme
  2  datafile '/u01/oradata/HDESK11G/testme01.dbf' size 50m;

We now create a table and use the TESTME tablespace to store the table data

SQL> create table sh.test
  2   tablespace testme
  3   as select * from sh.sales;

Table created.

Since we have not specified any AUTOEXTEND for the datafile of the TESTME tablespace, the TBSP_SIZE column for this tablespace shows 6400 blocks which is equal to 50 MB and the tablespace is about 74% full after we have created and populated the TEST table.

TBSP_NAME                      USED_SPACE  TBSP_SIZE USED_PERCENT
------------------------------ ---------- ---------- ------------
...
...
SYSTEM                              91512     552558   16.5615193
TESTME                               4736       6400           74

Let us now force a space used alert to be fired from OEM

SQL> insert into  sh.test
  2  select * from sh.sales;
insert into  sh.test
                *
ERROR at line 1:
ORA-01653: unable to extend table SH.TEST by 128 in tablespace TESTME

We can see that the tablespace TESTME is now 100% full and an alert has been raised as well.

TBSP_NAME                      USED_SPACE  TBSP_SIZE USED_PERCENT
------------------------------ ---------- ---------- ------------
...
...
TESTME                               6400       6400          100

SELECT REASON
, METRIC_VALUE
, MESSAGE_TYPE
, TO_CHAR(CREATION_TIME,'DD-MON-YYYY HH24:MI:SS')
, HOST_ID
FROM SYS.DBA_OUTSTANDING_ALERTS;

SQL> /

REASON
----------------------------------------------
METRIC_VALUE MESSAGE_TYPE TO_CHAR(CREATION_TIM
------------ ------------ --------------------
HOST_ID
----------------------------------------------
Tablespace [TESTME] is [100 percent] full
         100 Warning      15-NOV-2011 08:38:39
kens-orasql-001.corporateict.domain

Now we turn on AUTOEXTEND for the datafile of the TESTME tablespace - note in this case we specify the MAXIZE as UNLIMITED

SQL> alter database datafile '/u01/oradata/HDESK11G/testme01.dbf' autoextend on next 100M maxsize unlimited;

Database altered.

Now we see that the DBA_TABLESPACE_USAGE_METRICS view shows the tablespace as only 1.37% used.

Currently 50 MB is being used (the file size initially was 50 Mb and all the space in the datafile was used when we inserted rows into the table), but the TBSP_SIZE is showing 466770 (blocks) which is about 3646 Mb ( 466770*8192/1048576).

So why has Oracle chosen this figure?

If we run a df -k command, we see that the /u01 file system where this datafile of the TESTME tablespace is located has about 3.7 GB of free space and with AUTOEXTEND turned on, Oracle estimates that this is the maximum that the datafile can extend upto.

TBSP_NAME                      USED_SPACE  TBSP_SIZE USED_PERCENT
------------------------------ ---------- ---------- ------------
...
....
TESTME                               6400     466770   1.37112497

SQL> !df -k |grep u01

Filesystem           1K-blocks      Used Available Use% Mounted on

/dev/xvdb1            20635700  16007140   3780324  82% /u01

Now what happens if we instead specify an upper file size limit to which the datafile can extend upto with autoextend turned on.

SQL> alter database datafile '/u01/oradata/HDESK11G/testme01.dbf' autoextend on next 100M maxsize 500M;

Database altered.

We now see that the TESTME tablespace is 10% full because the maximum size that this tablespace can now grow to is 64000 blocks or 500 Mb and currently it has 50 Mb of used space.

The tablespaces screen from OEM however shows the tablepace as 33% full because it has grown the datafile to 150 MB from 50 Mb as we had specified the NEXT increment as 100 MB when we had enabled autoextend for the datafile of the TESTME tablesapace.

TBSP_NAME                      USED_SPACE  TBSP_SIZE USED_PERCENT
------------------------------ ---------- ---------- ------------
...
...
TESTME                               6400      64000           10

But what we see from OEM Tablespaces screen (Database Instance Home Page --> Administration --> Tablespaces), the tablespace is 33% full and not 10%.

Remember, this is not what OEM will use to determine the tablespace free space available and when it needs to raise an alert if the space usage threshold is crossed.

The Metalink note Data Guard Support for Heterogeneous Primary and Physical Standbys in Same Data Guard Configuration [ID 413484.1] describes the supported cross platform combinations between a primary and standby database.

In Oracle 10g, we could have a 32 bit and 64 bit Primary/Standby combination on some supported platforms and in 11g this has been extended to cover heterogenous platforms for the Primary and Standby database.

The environment used is as follows:

Primary

Windows 7 64 bit
11g Release 2
DB_UNIQUE_NAME=orcl

Active Standby

Oracle Enterprise Linux 5.7 64 bit
11g Release 2
DB_UNIUE_NAME=orcl_dr

Read the rest of the note Oracle 11g Cross platform Active Standby – Windows Primary database and Linux Active Standby

I tried out the procedure listed by the author and thought I’d share this with those who may not be aware of this note and must say thanks to the author Ginny Henningsen.

When I have tried to install Oracle 11g on Linux, in most cases I have found that the OUI either reports that some packages are missing (typically unixODBC or libaio) or some kernel parameters are not appropriately set. In this case however, we download and install an RPM package called oracle-validated and the oracle-validated RPM does a number of things for us.

Note that the oracle-validated RPM package is accessible through the Oracle Unbreakable Linux Network (ULN) which requires a support contract or from the Oracle public yum repository.

First we needed to configure the Linux machine to be able to connect to the internet using the corporate proxy and we did this by editing the /etc/profile.d/proxy.sh file with some environment variables like FTP_PROXY and HTTP_PROXY

export http_proxy=http://test-apache-001-dev.corporateict.domain:8123/
export ftp_proxy=http://test-apache-001-dev.corporateict.domain:8123/
export no_proxy=.corporateict.domain
export HTTP_PROXY=http://test-apache-001-dev.corporateict.domain:8123/
export FTP_PROXY=http://test-apache-001-dev.corporateict.domain:8123/

Login once again as root to invoke the changes made to the environment.

We then use wget to download the file which has the repository locations

[root@kens-orasql-001 yum.repos.d]# wget http://public-yum.oracle.com/public-yum-el5.repo

We have to update this file and change the line enabled=0 to enabled=1 for the tag which is appropriate to our Linux version – in our case we were using OEL 5.7 so we have to update these lines:

Change

[ol5_u7_base]
name=Oracle Linux $releasever – U7 – $basearch – base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/7/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=0

to

[ol5_u7_base]
name=Oracle Linux $releasever – U7 – $basearch – base
baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL5/7/base/$basearch/
gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
gpgcheck=1
enabled=1

We then ran a yum update followed by the yum install oracle-validated

[root@kens-orasql-002 yum.repos.d]# yum update
Loaded plugins: rhnplugin, security
This system is not registered with ULN.
ULN support will be disabled.
ol5_u7_base                                                                                                                                    | 1.1 kB     00:00
ol5_u7_base/primary                                                                                                                            | 1.5 MB     00:07
ol5_u7_base                                                                                                                                                 4605/4605
Skipping security plugin, no data
Setting up Update Process
No Packages marked for Update

[root@kens-orasql-002 yum.repos.d]# yum install oracle-validated
Loaded plugins: rhnplugin, security
This system is not registered with ULN.
ULN support will be disabled.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package oracle-validated.x86_64 0:1.1.0-14.el5 set to be updated
--> Processing Dependency: kernel-uek >= 2.6.32 for package: oracle-validated
--> Processing Dependency: libXp.so.6 for package: oracle-validated
--> Processing Dependency: /usr/lib/libodbccr.so for package: oracle-validated
--> Processing Dependency: /usr/lib64/libodbccr.so for package: oracle-validated
--> Processing Dependency: unixODBC-devel for package: oracle-validated
--> Processing Dependency: libaio-devel for package: oracle-validated
--> Processing Dependency: sysstat for package: oracle-validated
--> Processing Dependency: /usr/lib64/libaio.so for package: oracle-validated
--> Processing Dependency: /usr/lib/libodbc.so.1 for package: oracle-validated
--> Processing Dependency: /usr/lib/libaio.so for package: oracle-validated
--> Processing Dependency: compat-gcc-34-c++ for package: oracle-validated
--> Processing Dependency: compat-gcc-34 for package: oracle-validated
--> Processing Dependency: libdb-4.2.so()(64bit) for package: oracle-validated
--> Processing Dependency: libodbc.so.1()(64bit) for package: oracle-validated
--> Running transaction check
---> Package compat-db.x86_64 0:4.2.52-5.1 set to be updated
---> Package compat-gcc-34.x86_64 0:3.4.6-4.1 set to be updated
---> Package compat-gcc-34-c++.x86_64 0:3.4.6-4.1 set to be updated
---> Package kernel-uek.x86_64 0:2.6.32-200.13.1.el5uek set to be installed
--> Processing Dependency: kernel-firmware >= 2.6.32-200.13.1.el5uek for package: kernel-uek
---> Package libXp.i386 0:1.0.0-8.1.el5 set to be updated
---> Package libaio-devel.i386 0:0.3.106-5 set to be updated
---> Package libaio-devel.x86_64 0:0.3.106-5 set to be updated
---> Package sysstat.x86_64 0:7.0.2-11.el5 set to be updated
---> Package unixODBC.i386 0:2.2.11-7.1 set to be updated
---> Package unixODBC.x86_64 0:2.2.11-7.1 set to be updated
---> Package unixODBC-devel.i386 0:2.2.11-7.1 set to be updated
---> Package unixODBC-devel.x86_64 0:2.2.11-7.1 set to be updated
--> Running transaction check
---> Package kernel-uek-firmware.noarch 0:2.6.32-200.13.1.el5uek set to be updated
--> Finished Dependency Resolution

Dependencies Resolved

======================================================================================================================================================================
Package                                     Arch                           Version                                         Repository                           Size
======================================================================================================================================================================
Installing:
oracle-validated                            x86_64                         1.1.0-14.el5                                    ol5_u7_base                          24 k
Installing for dependencies:
compat-db                                   x86_64                         4.2.52-5.1                                      ol5_u7_base                         1.6 M
compat-gcc-34                               x86_64                         3.4.6-4.1                                       ol5_u7_base                         4.3 M
compat-gcc-34-c++                           x86_64                         3.4.6-4.1                                       ol5_u7_base                          13 M
kernel-uek                                  x86_64                         2.6.32-200.13.1.el5uek                          ol5_u7_base                          25 M
kernel-uek-firmware                         noarch                         2.6.32-200.13.1.el5uek                          ol5_u7_base                         2.5 M
libXp                                       i386                           1.0.0-8.1.el5                                   ol5_u7_base                          22 k
libaio-devel                                i386                           0.3.106-5                                       ol5_u7_base                          12 k
libaio-devel                                x86_64                         0.3.106-5                                       ol5_u7_base                          11 k
sysstat                                     x86_64                         7.0.2-11.el5                                    ol5_u7_base                         187 k
unixODBC                                    i386                           2.2.11-7.1                                      ol5_u7_base                         830 k
unixODBC                                    x86_64                         2.2.11-7.1                                      ol5_u7_base                         835 k
unixODBC-devel                              i386                           2.2.11-7.1                                      ol5_u7_base                         743 k
unixODBC-devel                              x86_64                         2.2.11-7.1                                      ol5_u7_base                         799 k

Transaction Summary
======================================================================================================================================================================
Install      14 Package(s)
Upgrade       0 Package(s)

Total size: 50 M
Is this ok [y/N]: y
Downloading Packages:
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID 1e5e0159
ol5_u7_base/gpgkey                                                                                                                             | 1.4 kB     00:00
Importing GPG key 0x1E5E0159 "Oracle OSS group (Open Source Software group) " from http://public-yum.oracle.com/RPM-GPG-KEY-oracle-el5
Is this ok [y/N]: y
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing     : unixODBC                                                                                                                                      1/14
  Installing     : compat-gcc-34                                                                                                                                 2/14
  Installing     : sysstat                                                                                                                                       3/14
  Installing     : compat-db                                                                                                                                     4/14
  Installing     : unixODBC                                                                                                                                      5/14
  Installing     : unixODBC-devel                                                                                                                                6/14
  Installing     : unixODBC-devel                                                                                                                                7/14
  Installing     : libaio-devel                                                                                                                                  8/14
  Installing     : libaio-devel                                                                                                                                  9/14
  Installing     : kernel-uek-firmware                                                                                                                          10/14
  Installing     : libXp                                                                                                                                        11/14
  Installing     : compat-gcc-34-c++                                                                                                                            12/14
Change references of /dev/hd in /etc/fstab to disk label
  Installing     : kernel-uek                                                                                                                                   13/14
WARNING: No module ehci-hcd found for kernel 2.6.32-200.13.1.el5uek, continuing anyway
WARNING: No module ohci-hcd found for kernel 2.6.32-200.13.1.el5uek, continuing anyway
WARNING: No module uhci-hcd found for kernel 2.6.32-200.13.1.el5uek, continuing anyway
  Installing     : oracle-validated                                                                                                                             14/14

Installed:
  oracle-validated.x86_64 0:1.1.0-14.el5

Dependency Installed:
  compat-db.x86_64 0:4.2.52-5.1                         compat-gcc-34.x86_64 0:3.4.6-4.1                               compat-gcc-34-c++.x86_64 0:3.4.6-4.1
  kernel-uek.x86_64 0:2.6.32-200.13.1.el5uek            kernel-uek-firmware.noarch 0:2.6.32-200.13.1.el5uek            libXp.i386 0:1.0.0-8.1.el5
  libaio-devel.i386 0:0.3.106-5                         libaio-devel.x86_64 0:0.3.106-5                                sysstat.x86_64 0:7.0.2-11.el5
  unixODBC.i386 0:2.2.11-7.1                            unixODBC.x86_64 0:2.2.11-7.1                                   unixODBC-devel.i386 0:2.2.11-7.1
  unixODBC-devel.x86_64 0:2.2.11-7.1

Complete!
[root@kens-orasql-002 yum.repos.d]#

We can see that the oracle-validated RPM has been installed.

[root@kens-orasql-001 yum.repos.d]# rpm -qa |grep oracle-valid
oracle-validated-1.1.0-14.el5

We can also check and see that the user and groups have been created as well.

[root@kens-orasql-001 yum.repos.d]# cat /etc/passwd |grep oracle

oracle:x:54321:54321::/home/oracle:/bin/bash

[root@kens-orasql-001 yum.repos.d]# cat /etc/group |grep dba 
dba:x:54322:oracle

It has also updated the /etc/security/limits.conf file

[root@kens-orasql-001 yum.repos.d]# cat /etc/security/limits.conf

# Oracle-Validated setting for nofile soft limit is 131072
oracle   soft   nofile    131072

# Oracle-Validated setting for nofile hard limit is 131072
oracle   hard   nofile    131072

# Oracle-Validated setting for nproc soft limit is 131072
oracle   soft   nproc    131072

# Oracle-Validated setting for nproc hard limit is 131072
oracle   hard   nproc    131072

# Oracle-Validated setting for core soft limit is unlimited
oracle   soft   core    unlimited

# Oracle-Validated setting for core hard limit is unlimited
oracle   hard   core    unlimited

# Oracle-Validated setting for memlock soft limit is 50000000
oracle   soft   memlock    50000000

# Oracle-Validated setting for memlock hard limit is 50000000
oracle   hard   memlock    50000000

Finally, we can see that the /etc/sysctl.conf has been updated as well with some “Oracle-Validated” settings.

# For 11g, Oracle-Validated setting for fs.file-max is 6815744
# For 10g, uncomment 'fs.file-max = 327679', and comment 'fs.file-max = 6553600' entry and re-run sysctl -p
# fs.file-max = 327679
fs.file-max = 6815744

# Oracle-Validated setting for kernel.msgmni is 2878
kernel.msgmni = 2878

# Oracle-Validated setting for kernel.msgmax is 8192
kernel.msgmax = 8192

# Oracle-Validated setting for kernel.msgmnb is 65536
kernel.msgmnb = 65536

# Oracle-Validated setting for kernel.sem is '250 32000 100 142'
kernel.sem = 250 32000 100 142

# Oracle-Validated setting for kernel.shmmni is 4096
kernel.shmmni = 4096

# Oracle-Validated setting for kernel.shmall is 1073741824
kernel.shmall = 1073741824

# Oracle-Validated setting for kernel.shmmax is 4398046511104 on x86_64 and 4294967295 on i386 architecture. Refer Note id 567506.1
kernel.shmmax = 4398046511104

# Oracle-Validated setting for kernel.sysrq is 1
kernel.sysrq = 1

# Oracle-Validated setting for net.core.rmem_default is 262144
net.core.rmem_default = 262144

# For 11g, Oracle-Validated setting for net.core.rmem_max is 4194304
# For 10g, uncomment 'net.core.rmem_max = 2097152', comment 'net.core.rmem_max = 4194304' entry and re-run sysctl -p
# net.core.rmem_max = 2097152
net.core.rmem_max = 4194304

# Oracle-Validated setting for net.core.wmem_default is 262144
net.core.wmem_default = 262144

# For 11g, Oracle-Validated setting for net.core.wmem_max is 1048576
# For 10g, uncomment 'net.core.wmem_max = 262144', comment 'net.core.wmem_max = 1048576' entry for this parameter and re-run sysctl -p
# net.core.wmem_max = 262144
net.core.wmem_max = 1048576

# Oracle-Validated setting for fs.aio-max-nr is 3145728
fs.aio-max-nr = 3145728

# For 11g, Oracle-Validated setting for net.ipv4.ip_local_port_range is 9000 65500
# For 10g, uncomment 'net.ipv4.ip_local_port_range = 1024 65000', comment 'net.ipv4.ip_local_port_range = 9000 65500' entry and re-run sysctl -p
# net.ipv4.ip_local_port_range = 1024 65000
net.ipv4.ip_local_port_range = 9000 65500

# Oracle-Validated setting for vm.min_free_kbytes is 51200 to avoid OOM killer
vm.min_free_kbytes = 51200

Let us today take a look at two other functions STRCAT and STREXT.

STRCAT basically enables us to concatenate two strings or two character columns.

The STREXT function on the other hand is used to extract a portion of a string.

For example in our source database we have a table MYPHONE with the following structure:

SQL> desc myphone
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 AREA_CODE                                          NUMBER
 PHONE_NO                                           NUMBER

In the target we have the same table MYPHONE with a different structure:

SQL> desc myphone
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 PHONE_NO                                           VARCHAR2(30)

So in the target database, the PHONE_NO column includes both the area code as well as the phone number with a ‘-‘ character as well between both the values, while in the source database the table has two columns – one for the area code and one for the phone number.

We will use SRTCAT function in this case.

Remember that since the source and target tables differ in structure, we need to run the DEFGEN utility in the source GoldenGate environment to generate the definitions file and then copy this across to the target GoldenGate environment..

These are the contents of the extract parameter file:

extract ext
userid ggs_owner, password ggs_owner
rmthost venom , mgrport 7809
rmttrail ./dirdat/gg
table ggs_owner.myphone;

These are the contents of the replicat parameter file – note how the STRCAT function is being used here.

REPLICAT rep
sourcedefs /export/home/oracle/gg/dirsql/myphone.sql
USERID ggs_owner, PASSWORD ggs_owner
MAP ggs_owner.myphone, TARGET ggs_owner.myphone,
COLMAP (phone_no=@STRCAT("0",area_code,"-",phone_no));

We now start the extract and replicat processes and insert some records in the source table.

The source table now has the following rows:

SQL> select * from myphone;

 AREA_CODE   PHONE_NO
---------- ----------
         8   92471136
         4   17213124
         2     818188

Let us see how these rows have been transformed on the target database.

SQL> select * from myphone;

PHONE_NO
------------------------------
08-92471136
04-17213124
02-818188

We can extend this example and use both STRCAT and STREXT together to achieve the data transformation that we desire.

For example in our source MYSSID table, we have data like this:

SQL> select * from myssid;

      SSID
----------
 123456787
 123456788
 123456789

But on the target database, in the same table the data has been displayed like this:

SQL> select * from myssid;

SSID
--------------------
123-456-787
123-456-788
123-456-789

So how did we achieve this?

Have a look at the replicat parameter file and note how we have used first the STREXT function to extract 3 characters at a time – the first 3, then the next 3 and finally the last 3 and then used STRCAT to concatenate the result of the STREXT functions together with a ‘-‘ character acting as the string separator.

REPLICAT rep
sourcedefs /export/home/oracle/gg/dirsql/myssid.sql
USERID ggs_owner, PASSWORD ggs_owner
MAP ggs_owner.myssid, TARGET ggs_owner.myssid,
COLMAP (ssid=@STRCAT(@STREXT(ssid,1,3),"-",@STREXT(ssid,4,6),"-",@STREXT(ssid,7,9) ));

To illustrate this example, we have a source and target table called EMPSAL and the structure of the tables in both databases is slightly different.

In the source table we have the JOB column and in the target database we have a TAX_BRACKET column.

In the first example, we will use CASE function to populate the target database TAX_BRACKET column based on the value for the JOB column in the source database.

In the second example, we will use the EVAL function to populate the target database TAX_BRACKET column based on a particular range of values for the SAL column in the source table.

Remember that since the table structure in source and target are different, we need to run the DEFGEN utility to generate a definitions file which we will then copy to the target GoldenGate environment and instead of using the ASSUMEDEFS parameter in the replicate parameter file, we use the SOURCEDEFS parameter instead to indicate the location of the definitions file which we have generated and copied over from the source GoldenGate environment.

Source

SQL> desc empsal
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ENAME                                              VARCHAR2(20)
 SAL                                                NUMBER
 JOB                                                VARCHAR2(12)

Target

SQL> desc empsal
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 ENAME                                              VARCHAR2(20)
 SAL                                                NUMBER
 TAX_BRACKET                                        VARCHAR2(10)

We now create the definitions file for the EMPSAL table and copy the generated definitions file to the target GoldenGate environment.

GGSCI (sunos1) 4> edit params defgen

"/export/home/oracle/gg/dirprm/defgen.prm" 3 lines, 97 characters
defsfile ./dirsql/empsal.sql
userid ggs_owner password ggs_owner
table ggs_owner.empsal;

sunos1:/export/home/oracle/gg $ ./defgen paramfile /export/home/oracle/gg/dirprm/defgen.prm

sunos1:/export/home/oracle/gg/dirsql $ scp -rp empsal.sql oracle@sunos2:/export/home/oracle/gg/dirsql

Let us have a look at the Extract parameter file – quite normal and straight forward here.

extract ext
userid ggs_owner, password ggs_owner
rmthost sunos2 , mgrport 7809
rmttrail ./dirdat/gg
table ggs_owner.empsal;

On the target, these are the contents of the replicat parameter file. Note the COLPMAP clause. Since both the tables have common columns ENAME and SAL, we do not have to explicitly map them and we can just specify USEDEFAULTS.

The TAX_BRACKET column on the target table is being populated using the CASE function which evaluates the values for the JOB column in the source table.

If the value for JOB is ‘OPERATOR’, then the TAX_BRACKET column is assigned the value ‘LOW’. If it is ‘DBA’ then the TAX_BRACKET column is assigned the value ‘MID’ and if the value is ‘MANAGER’, then the TAX_BRACKET column is assigned the value ‘HIGH’. If the value for JOB is none of the values, then a default value of ‘UNKNOWN’ is assigned.

REPLICAT rep
sourcedefs /export/home/oracle/gg/dirsql/empsal.sql
USERID ggs_owner, PASSWORD ggs_owner
MAP ggs_owner.empsal, TARGET ggs_owner.empsal,
COLMAP (
usedefaults, tax_bracket=@case(JOB, "OPERATOR","LOW","DBA", "MID","MANAGER","HIGH", "UNKNOWN"));

Let us now insert some values into the source table.

SQL> insert into empsal values
  2  ('JOHN',10000, 'DBA');

1 row created.

SQL> insert into empsal values
  2  ('JACK',5000, 'OPERATOR');

1 row created.

SQL> insert into empsal values
  2  ('TOM',20000, 'MANAGER');

1 row created.

SQL>  insert into empsal values
  2  ('MARY', 6000, 'ANALYST');

1 row created.

SQL> commit;

Commit complete.

SQL> select * from empsal;

ENAME                       SAL JOB
-------------------- ---------- ------------
JOHN                      10000 DBA
JACK                       5000 OPERATOR
TOM                       20000 MANAGER
MARY                       6000 ANALYST

Let us now see how the data has been replicated and how the transformation has taken place on the target.

SQL> select * from empsal;

ENAME                       SAL TAX_BRACKE
-------------------- ---------- ----------
JOHN                      10000 MID
JACK                       5000 LOW
TOM                       20000 HIGH
MARY                       6000 UNKNOWN

Let us now truncate both the tables and see the next example using EVAL instead of CASE.
We stop both the extract and replicat processes and will now change the replicat parameter file on the target to include the EVAL function.
So this is how our replicat parameter file will look like.
REPLICAT rep
sourcedefs /export/home/oracle/gg/dirsql/empsal.sql
USERID ggs_owner, PASSWORD ggs_owner
MAP ggs_owner.empsal, TARGET ggs_owner.empsal,
COLMAP (
usedefaults, &
tax_bracket=@eval(sal < 10000,"LOW", sal >= 20000 , "HIGH",sal >= 10000, "MID"));

Start the extract and replicat processes again and let us now insert the same set of values in the source table as we did before and see how they are now replicated and transformed on the target.
SQL> select * from empsal;

ENAME                       SAL TAX_BRACKE
-------------------- ---------- ----------
JOHN                      10000 MID
JACK                       5000 LOW
TOM                       20000 HIGH
MARY                       6000 LOW

For those rows where the SAL value was less than 10000, a value of 'LOW' was assigned to the TAX_BRACKET column and if the value was equal to or greater than 10000 (but less than 20000), a value of 'MID' is assigned and all SAL values above 20000 are assigned 'HIGH'.
Have a read of the all the diferent column conversion functions mentioned in the GoldenGate reference guide and there are quite a few. Let me know if you found any others which are useful and kindly share your experience with the community!
]]>
			http://gavinsoorma.com/2011/08/using-the-goldengate-column-conversion-functions-case-and-eval/feed/
		0
		
		
		
		http://gavinsoorma.com/2011/08/passed-the-1z0-539-exam-am-now-an-oracle-certified-goldengate-implementation-specialist/
		http://gavinsoorma.com/2011/08/passed-the-1z0-539-exam-am-now-an-oracle-certified-goldengate-implementation-specialist/#comments
		Thu, 18 Aug 2011 02:44:21 +0000
		Gavin Soorma
				

		http://gavinsoorma.com/?p=3239
		
			 I have recently passed the Oracle GoldenGate 10 Essentials exam which recognizes you as a Oracle GoldenGate 10 Certified Implementation Specialist.

Note that the exam is currently based on GoldenGate 10.4 and not the 11g version of GoldenGate which has been out now for quite some time.
I must point out that while there are a number of ‘brain dumps’ like Pass4Sure and Test King to ‘help’ you pass the exam, I have seen the questions and answers that are provided by them and in most cases I found the answers to be provided to be grossly incorrect and wrong. So beware!
The best preparation for the exam is to go through the following sets of documentation:
Oracle Installation and Setup Guide

Reference Guide

Administration Guide
These and other 10.4 GoldenGate documentation can be obtained online  here …
I am now available to provide my services in any GoldenGate implementation project around the world as well as for consultancy on any GoldenGate related subjects.
You can contact me at +61417713124 or via email to gavin.soorma@oncalldba.com.au to discuss anything further.
Happy GoldenGating!
]]>
			http://gavinsoorma.com/2011/08/passed-the-1z0-539-exam-am-now-an-oracle-certified-goldengate-implementation-specialist/feed/
		0
		
		
		
		http://gavinsoorma.com/2011/08/does-goldengate-support-oracle-flashback/
		http://gavinsoorma.com/2011/08/does-goldengate-support-oracle-flashback/#comments
		Wed, 17 Aug 2011 03:16:21 +0000
		Gavin Soorma
				

		http://gavinsoorma.com/?p=3235
		
			There is an Oracle Metalink Note (Does Goldengate Support The New Oracle 10g Flashback Feature? [ID 966212.1]) which discusses this aspect, but I thought that I would like to see for myself how does the Extract and Replicat processes behave if we issue any FLASHBACK command on the source database.

The Metalink note states that GoldenGate supports the following Flashback operations:
Flashback Table to SCN

Flashback Table to timestamp

Flashback Table to restore point
and does not support operations like:
Flashback Table to before drop

Flashback database
I have tested both the Flashback Table To Timestamp as well as the Flashback Table To Before Drop operations and find that both seem to be supported by GoldenGate and replication continues inspite of these commands being issued on the source database.
Let us see the examples of the same.
I have an Oracle 11g Goldengate (11.1.1) environment configured with the source and target databases of version 11.2.0.2.
Extract and Replicat processes are running and I am not using Data Pump in this case. The table configured for replication is called MYOBJECTS.
To test the Flashback, I am deleting all the rows from the table and then check on the target database if this delete operation has been propagated. 
We will then flashback to a point in time when all the rows were present in the table and then check both the source and target database to verify if the delete operation has been flashed back on both databases.
Source
SQL> select count(*) from myobjects;
  COUNT(*)

———-

     56687
SQL> select to_char(sysdate,’dd-mon-yyyy hh24:mi:ss’) from dual;
TO_CHAR(SYSDATE,’DD-

——————–

17-aug-2011 10:23:07
SQL> delete myobjects;
56687 rows deleted.
SQL> commit;
Commit complete.
Target 
SQL> select count(*) from myobjects;
  COUNT(*)

———-

         0
Source
SQL> conn / as sysdba

Connected.

SQL> alter table ggs_owner.myobjects enable row movement;
Table altered.
SQL>   flashback table ggs_owner.myobjects to timestamp to_timestamp (’17-aug-2011 10:23:07′,’dd-mon-yyyy hh24:mi:ss’);
Flashback complete.
SQL> select count(*) from ggs_owner.myobjects;
  COUNT(*)

———-

     56687
Target 
SQL> select count(*) from myobjects;
  COUNT(*)

———-

     56687
If we check the Extract and Replicat process reports, we can see that around the time we have performed the database flashback operation, there has been both extract and replicat activity 
Source
2011-08-17 10:23:58  INFO    OGG-01026  Rolling over remote file ./dirdat/yy000004.

2011-08-17 10:25:53  INFO    OGG-01026  Rolling over remote file ./dirdat/yy000005.

2011-08-17 10:25:58  INFO    OGG-01026  Rolling over remote file ./dirdat/yy000006.
Target
Switching to next trail file ./dirdat/yy000004 at 2011-08-17 10:23:59 due to EOF, with current RBA 9999940

Opened trail file ./dirdat/yy000004 at 2011-08-17 10:23:59
Switching to next trail file ./dirdat/yy000005 at 2011-08-17 10:25:54 due to EOF, with current RBA 9999930

Opened trail file ./dirdat/yy000005 at 2011-08-17 10:25:54
Switching to next trail file ./dirdat/yy000006 at 2011-08-17 10:25:58 due to EOF, with current RBA 9999882

Opened trail file ./dirdat/yy000006 at 2011-08-17 10:25:58
Let us now look at the Flashback Table To Before Drop operation. 
The Metalink note states that  this operation is NOT supported, but I found that in my case, GoldenGate was still peforming the online change synchronization even after we dropped the table and flashed it back.
Would like others in the community to try this out themselves and provide some feedback to me on how it went for them.
Here is the example.
We will use the same MYOBJECTS table and drop it and then flash it back from the recycle bin. Note – if you are using DDL replication as well, then recycle bin has to be turned off and in that case you will not be able to flashback the table from the recycle bin using the Flashback Table To Before Drop command.
Source
SQL> drop table myobjects;
Table dropped.
SQL> flashback table myobjects to before drop;
Flashback complete.
SQL> update myobjects set owner=’GAVIN’;
56687 rows updated.
SQL> commit;
Commit complete.
SQL> select distinct owner from myobjects;
OWNER

——————————

GAVIN
Target
SQL> select distinct owner from myobjects;
OWNER

——————————

GAVIN
Changes have been replicated!
]]>
			http://gavinsoorma.com/2011/08/does-goldengate-support-oracle-flashback/feed/
		0
		
		
		
		http://gavinsoorma.com/2011/08/goldengate-replication-with-source-and-target-on-the-same-physical-host/
		http://gavinsoorma.com/2011/08/goldengate-replication-with-source-and-target-on-the-same-physical-host/#comments
		Mon, 15 Aug 2011 06:47:39 +0000
		Gavin Soorma
				

		http://gavinsoorma.com/?p=3229
		
			I have been asked this question several times about using GoldenGate to replicate between source and target Oracle databases located on the same physical server. Do we need two manager processes, or do we need two separate Goldengate environments or what happens if one database is a version 11g database and the other is 10g – do we need to install two versions of GoldenGate and so on and so forth.

To answer these common questions:
1)	You do not need two manager processes configured. In fact, I am not sure if we can have multiple manager processes on the same GoldenGate environment.

2)	You do not need to install two GoldenGate environments in this particular case– one for source and one for target

3)	You can replicate data from 11g to 10g and vice versa as well.

4)	Both extract and replicat processes can run on the same host with one manager process for both 
Let us test this with a simple example. 
We have a table called MYOBJECTS existing in both source database (11.2.0.2) and target database (10.2.0.4). At present, both the tables have no rows. We will insert rows into the 11g database and see them propagated to the 10g target database on the same host.
SQL> desc  myobjects;
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER                                              VARCHAR2(30)
 OBJECT_NAME                                        VARCHAR2(128)
 OBJECT_ID                                 NOT NULL NUMBER

SQL> select count(*) from myobjects;

  COUNT(*)
----------
         0

We create an extract called extlocal and a remote trail file (even though there is actually no ‘remote’ machine) – note the directory path pertains to a location on the source database machine. We are dealing with just one server here which acts as both a local as well as remote server as far as GoldenGate is concerned.
GGSCI (sunos01) 25> add extract extlocal tranlog begin now

2011-08-12 09:03:50  INFO    OGG-01749  Successfully registered EXTRACT EXTLOCAL to start managing log retention at SCN 10185228.
EXTRACT added.

GGSCI (sunos01) 26> add rmttrail ./dirdat/aa extract extlocal

RMTTRAIL added.

These are the contents of the extract parameter file – note rmthost points to the ‘local’ machine.
However, since we have both the source and target database on the same host, we need to define the source database which GoldenGate will connect to using the setenv keyword.

extract extlocal
userid ggs_owner, password ggs_owner
setenv (ORACLE_HOME="/u01/app/oracle/product/11.2.0/dbhome_2")
setenv (ORACLE_SID="eleven")
rmthost sunos01 , mgrport 7809
rmttrail ./dirdat/aa
table ggs_owner.myobjects;

We then add a replicat group replocal, which will read from the trail file located on the same server where the extract process is running. So in essence, we are running the extract and replicat processes on the same host!
GGSCI (sunos01) 1> add replicat replocal exttrail ./dirdat/aa
REPLICAT added.

These are the contents of the replicat parameter file – we now are setting the environment for the Oracle 10g database which will be the target.
REPLICAT replocal
SETENV (ORACLE_HOME="/u01/app/oracle/product/10.2.0/dbhome_1")
SETENV (ORACLE_SID="tentwo")
ASSUMETARGETDEFS
USERID ggs_owner, PASSWORD ggs_owner
MAP ggs_owner.myobjects, TARGET ggs_owner.myobjects;

We now start the extract process.
GGSCI (sunos01) 27> start extract extlocal

Sending START request to MANAGER ...
EXTRACT EXTLOCAL starting

Also, start the replicat process.
GGSCI (sunos01) 2> start replicat replocal

Sending START request to MANAGER ...
REPLICAT REPLOCAL starting

Check the status and we see both are running now (on the same server)
GGSCI (sunos01) 6> info all

Program     Status      Group       Lag           Time Since Chkpt

MANAGER     RUNNING
EXTRACT     RUNNING     EXTLOCAL    00:00:00      00:00:13
REPLICAT    RUNNING     REPLOCAL    00:00:31      00:00:03

Now make some changes in the 11g source database ….
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> insert into myobjects
  2  select owner,object_name,object_id from dba_objects where object_id is not null;

56656 rows created.

SQL> commit;

Commit complete.

Connect to the target 10g database and we see that the rows have been inserted into the table 
devastator:/export/home/oracle/gg $ sqlplus ggs_owner/ggs_owner

SQL*Plus: Release 10.2.0.4.0 - Production on Mon Aug 15 14:28:47 2011

Copyright (c) 1982, 2007, Oracle.  All Rights Reserved.

Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select count(*) from myobjects;

  COUNT(*)
----------
     56656

Let us use the STATS command to verify that the replicat process has actually done the inserts.
GGSCI (devastator) 4> stats replicat replocal latest

Sending STATS request to REPLICAT REPLOCAL ...

Start of Statistics at 2011-08-15 14:30:11.

Replicating from GGS_OWNER.MYOBJECTS to GGS_OWNER.MYOBJECTS:

*** Latest statistics since 2011-08-15 14:28:20 ***
        Total inserts                            56656.00
        Total updates                                0.00
        Total deletes                                0.00
        Total discards                               0.00
        Total operations                         56656.00

]]>
			http://gavinsoorma.com/2011/08/goldengate-replication-with-source-and-target-on-the-same-physical-host/feed/
		0
		
		
		
		http://gavinsoorma.com/2011/08/goldengate-replication-using-a-data-definition-file-and-defgen-utility/
		http://gavinsoorma.com/2011/08/goldengate-replication-using-a-data-definition-file-and-defgen-utility/#comments
		Mon, 01 Aug 2011 02:17:04 +0000
		Gavin Soorma
				

		http://gavinsoorma.com/?p=3224
		
			Some time back I had written a post on GoldenGate column mapping and transformations.

I have been asked the question several times regarding how can we replicate data between tables which are not similar in structure or where the target table has columns which are just a subset of the columns present in the source table.
Let us look at a simple example to see how this can be done using the DEFGEN utility of GoldenGate.
In this example we have a source table MYOBJECTS2 (based on DBA_TABLES) and the target table structure is different as it has only three columns – OWNER, OBJECT_NAME and OBJECT_TYPE as shown below.
The table has 113238 rows which we need to replicate to the target database.
Source table 
SQL> desc myobjects2
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER                                              VARCHAR2(30)
 OBJECT_NAME                                        VARCHAR2(128)
 SUBOBJECT_NAME                                     VARCHAR2(30)
 OBJECT_ID                                          NUMBER
 DATA_OBJECT_ID                                     NUMBER
 OBJECT_TYPE                                        VARCHAR2(19)
 CREATED                                            DATE
 LAST_DDL_TIME                                      DATE
 TIMESTAMP                                          VARCHAR2(19)
 STATUS                                             VARCHAR2(7)
 TEMPORARY                                          VARCHAR2(1)
 GENERATED                                          VARCHAR2(1)
 SECONDARY                                          VARCHAR2(1)
 NAMESPACE                                          NUMBER
 EDITION_NAME                                       VARCHAR2(30)

Target table 
SQL> desc  myobjects2
 Name                                      Null?    Type
 ----------------------------------------- -------- ----------------------------
 OWNER                                              VARCHAR2(30)
 OBJECT_NAME                                        VARCHAR2(128)
 OBJECT_TYPE                                        VARCHAR2(19)

Since the source and target table definitions are different, we first need to create what is called a data definition file which contains the definition of the source table. 
This is done using the DEFGEN utility and after the file is created, we transfer the same to the target server.
We first create a DEFGEN parameter file as shown below:
GGSCI (dev1) 1> edit params defgen

defsfile ./dirsql/myobjects2.sql
userid ggs_owner password ggs_owner
table ggs_owner.myobjects2;

We then run DEFGEN and specify the parameter file to be used which is the one we have just created.
$ ./defgen paramfile /export/home/oracle/gg/dirprm/defgen.prm
This will create a file called myobjects2.sql in the /dirsql subdirectory with the following contents:

* Definitions created/modified  2011-08-01 08:16
*
*  Field descriptions for each column entry:
*
*     1    Name
*     2    Data Type
*     3    External Length
*     4    Fetch Offset
*     5    Scale
*     6    Level
*     7    Null
*     8    Bump if Odd
*     9    Internal Length
*    10    Binary Length
*    11    Table Length
*    12    Most Significant DT
*    13    Least Significant DT
*    14    High Precision
*    15    Low Precision
*    16    Elementary Item
*    17    Occurs
*    18    Key Column
*    19    Sub Data Type
*
*
Definition for table GGS_OWNER.MYOBJECTS2
Record length: 532
Syskey: 0
Columns: 15
OWNER            64     30        0  0  0 1 0     30     30      0 0 0 0 0 1    0 1 0
OBJECT_NAME      64    128       36  0  0 1 0    128    128      0 0 0 0 0 1    0 1 0
SUBOBJECT_NAME   64     30      170  0  0 1 0     30     30      0 0 0 0 0 1    0 1 0
OBJECT_ID        64     50      206  0  0 1 0     50     50     50 0 0 0 0 1    0 1 2
DATA_OBJECT_ID   64     50      262  0  0 1 0     50     50     50 0 0 0 0 1    0 1 2
OBJECT_TYPE      64     19      318  0  0 1 0     19     19      0 0 0 0 0 1    0 1 0
CREATED         192     19      342  0  0 1 0     19     19     19 0 5 0 0 1    0 1 0
LAST_DDL_TIME   192     19      364  0  0 1 0     19     19     19 0 5 0 0 1    0 1 0
TIMESTAMP        64     19      386  0  0 1 0     19     19      0 0 0 0 0 1    0 1 0
STATUS           64      7      410  0  0 1 0      7      7      0 0 0 0 0 1    0 1 0
TEMPORARY        64      1      422  0  0 1 0      1      1      0 0 0 0 0 1    0 1 0
GENERATED        64      1      428  0  0 1 0      1      1      0 0 0 0 0 1    0 1 0
SECONDARY        64      1      434  0  0 1 0      1      1      0 0 0 0 0 1    0 1 0
NAMESPACE        64     50      440  0  0 1 0     50     50     50 0 0 0 0 1    0 1 2
EDITION_NAME     64     30      496  0  0 1 0     30     30      0 0 0 0 0 1    0 1 0
End of definition

We then will ftp or copy this data definitions file which we have just generated to the target machine. In this case we are copying the file to the same ./dirsql subdirectory under the GoldenGate root directory on the target machine.
In our example, we are running an initial data load and not online change synchronization. But the same example can be extended to cover online change replication as well.
Since this is an initial data load remember for the Extract process, we need to use the SOURCEISTABLE keyword and for the Replicat process we need to use the SPECIALRUN keyword.
GGSCI (dev1) 1>  add extract ext1, sourceistable 
These are the contents of the parameter file for extract process ext1
extract ext1
userid ggs_owner, password ggs_owner
rmthost dev2 , mgrport 7809
rmttask replicat, group rep1
table ggs_owner.myobjects2;

On the target we create a replicat process and replicat parameter file.
GGSCI (dev2) 1> add replicat rep1 specialrun

The replicat rep1 parameter file has the following contents:
REPLICAT rep1
USERID ggs_owner, PASSWORD ggs_owner
SOURCEDEFS ./dirsql/myobjects2.sql
MAP ggs_owner.myobjects2, TARGET ggs_owner.myobjects2,
colmap (
owner=owner, object_name=object_name,object_type=object_type)
;

Note the column mapping using the COLMAP clause and how we have only mapped the three columns which we require. The SOURCEDEFS keyword will specify the location of the data definitions file which we have copied from the source machine and which was generated via the DEFGEN utility.
On the source GoldenGate environment, we start the extract ext1 using the START EXTRACT EXT1 command. Note that we do not have to start the replicat process REP1 on the target as this is done automatically by the initial load extract process.
We can see that after a while the extract process has stopped because it has extracted and loaded all the 113238 rows into the source table and if we see the report via the VIEW REPORT EXT1 command, we can see the insert operations which have taken place.
Processing table GGS_OWNER.MYOBJECTS2
***********************************************************************
*                   ** Run Time Statistics **                         *
***********************************************************************

Report at 2011-08-01 08:42:40 (activity since 2011-08-01 08:42:13)
Output to rep1:
From Table GGS_OWNER.MYOBJECTS2:
       #                   inserts:    113238
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         0

On the target, we can see via the VIEW REPORT REP1 command, the column mapping which has taken place.
MAP resolved (entry GGS_OWNER.MYOBJECTS2):
  MAP GGS_OWNER.MYOBJECTS2, TARGET ggs_owner.myobjects2, colmap ( owner=owner, object_name=object_name,object_type=object_type) ;
2011-08-01 08:42:23  WARNING OGG-00869  No unique key is defined for table MYOBJECTS2. All viable columns will be used to represent the key, but may not guar
antee uniqueness.  KEYCOLS may be used to define the key.
Using the following key columns for target table GGS_OWNER.MYOBJECTS2: OWNER, OBJECT_NAME, OBJECT_TYPE.

***********************************************************************
*                   ** Run Time Statistics **                         *
***********************************************************************

Report at 2011-08-01 08:42:45 (activity since 2011-08-01 08:42:23)
From Table GGS_OWNER.MYOBJECTS2 to GGS_OWNER.MYOBJECTS2:
       #                   inserts:    113238
       #                   updates:         0
       #                   deletes:         0
       #                  discards:         0

]]>
			http://gavinsoorma.com/2011/08/goldengate-replication-using-a-data-definition-file-and-defgen-utility/feed/
		0
		
		
		
		http://gavinsoorma.com/2011/07/installing-oracle-10-2-0-5-enterprise-manager-grid-control-on-linux-and-upgrading-the-repository-database-to-10-2-0-5/
		http://gavinsoorma.com/2011/07/installing-oracle-10-2-0-5-enterprise-manager-grid-control-on-linux-and-upgrading-the-repository-database-to-10-2-0-5/#comments
		Fri, 29 Jul 2011 02:51:06 +0000
		Gavin Soorma
				
		

		http://gavinsoorma.com/?p=3218
		
			This note explains the procedure used to install 10.2.0.5 Grid Control on a Linux operating system (64 bit Red Hat Enterprise Linux Server release 5.6) as well as the steps taken to upgrade the repository database from the default 10.1.0.4 version to 10.2.0.5.

We will be using the silent installation method and not doing the installation using the OUI in interactive mode.
The steps can be broadly outlined as follows:
•	Install any missing RPM’s especially the 32 bit RPM’s needed for OEM

•	Create the users and groups

•	Configure kernel parameters and hosts file

•	Edit the response files needed for the silent installation

•	Install Grid Control 10.2.0.3 (OMS and Agent) using response files

•	Upgrade Grid Control to 10.2.0.5 using response files

•	Configure database repository (10.1.0.4) and OMS using response files

•	Upgrade repository database to 10g Release 2 (10.2.0.1) using DBUA

•	Apply 10.2.0.5 patch to database software and upgrade repository database to 10.2.0.5
Download the software 
Download the Grid Control software from the following link:
http://www.oracle.com/technetwork/oem/grid-control/downloads/linuxx8664soft-085949.html
We need the 10.2.0.3 OEM Grid Control base release and the 10.2.0.5 patch release.
•	Linux_x86_64_Grid_Control_full_102030_disk1.zip

•	Linux_x86_64_Grid_Control_full_102030_disk2.zip

•	gc_x86_64_10205_part1of2.zip

•	gc_x86_64_10205_part2of2.zip 
Create a staging directory and unzip all the downloaded software there.
Download  and read the rest of this note.
]]>
			http://gavinsoorma.com/2011/07/installing-oracle-10-2-0-5-enterprise-manager-grid-control-on-linux-and-upgrading-the-repository-database-to-10-2-0-5/feed/
		0