Guenadi N Jilevski's Oracle BLOG

Oracle RAC, DG, EBS, DR and HA DBA BLOG

Upgrade Oracle Enterprise Manager Grid Control from 10.2.0.2 to 10.2.0.5 on windows

Upgrade Oracle Enterprise Manager Grid Control from 10.2.0.2 to 10.2.0.5 on windows

In this article we will look at the upgrade of Oracle Enterprise from version 10.2.0.2 to version 10.2.0.5 on windows. The paper covers upgrade of all OEM Grid Control components.

  1. Upgrade OMS
  2. Upgrade agent

Upgrade OMS

Start OUI. Press Next to continue.

Select OMS Oracle Home and press Next to continue.

Enter the details as per your case and press Next to continue.

Wait for the product prerequisite checks to finish. Make sure that there are no errors. If there are errors fix them before proceed with the installation. If there are no errors press Next to continue.

Enter the sys password and make sure than the OMS and opmn processes are shutdown cleanly. The installation will proceed if all of the above is met. Press Next to continue.

Enter ias_admin password when prompted and press Next to continue.

Acknowledge the OUI action to shut down the middle tier by pressing OK. Press Next to continue.

The summary screen appears. Examine it and press Install to continue to start installation of the upgrades.

Wait for the installation to complete. The screen shows the progress of the installation.

Wait for the configuration to complete. The screen shows the progress of the configuration assistants.

If assistant fails, check the log files and try to fix the problem. Rerun the assistant after fixing the problem.

When all assistants compete you will see a confirmation for the successful installation of the upgrades. Press Exit to exit the installer.

Upgrade the agent

Start the OUI and press Next to continue.

Select the agent Oracle Home and press Next to continue.

Enter your credentials and press Next to continue.

Wait until OUI completes the prerequisite checks for the installation. Examine the OUI findings. Fix any error before proceed with the installation of the upgrade. If the prerequisite checks are successful press Next to continue.

Examine the summary screen and press Install to start the installation of the upgrades.

Wait for the installation to complete. You will be shown the progress of the installation.

After the completion of the installation the configuration phase kicks off. Wait for all of the configuration assistants to complete successfully.

You will be notified that the installation of the upgrades have successfully completed. The information is provided for the user to login to the upgraded Oracle Enterprise Manager Grid control. Press Exit to exit from the OUI.

This information is also available at:

E:\OracleHomes\agent10g\sysman\setupinfo.txt

See below for information pertaining to your Enterprise Manager installation:

1. Use the following URL to access the Enterprise Manager Grid Control:

https://userpc.gj.com:1159/em

2. The Enterprise Manager installation includes an Oracle Application Server instance, which is administered using a special “ias_admin” user account. The following information was defaulted for the embedded Application Server instance:

Instance Name: EnterpriseManager0.userpc.gj.com

ias_admin password: This password is the same the SYSMAN account.

3. The connection details for the Enterprise Manager Repository are:

Host: userpc.gj.com

Port: 1521

SID: DB10g

4. The Enterprise Manager Release Notes are located at:

E:\OracleHomes\agent10g\relnotes\README_EM.htm

This confirms that Oracle Enterprise Manager Grid Control was successfully upgraded to version 10.2.0.5 on windows.

February 27, 2010 Posted by | oracle | Leave a comment

Installing Oracle Enterprise Manager Grid Control 10.2.0.2 on Windows

Installing Oracle Enterprise Manager Grid Control 10.2.0.2 on Windows

Here in the article we will look at install Oracle EM GC using an existing database.

  1. Make sure that the database selected does not have EM DB console installed. If it is installed drop the setup.
  2. Run the following script in a script against the new OMR database prior to the running OUI for installing Oracle EM GC.

    drop user sysman cascade;

    drop public synonym MGMT_ADMIN;

    drop public synonym MGMT_AS_ECM_UTIL;

    drop public synonym MGMT_AVAILABILITY;

    drop public synonym MGMT_COLLECTION_PROPERTIES;

    drop public synonym MGMT_CREDENTIAL;

    drop public synonym MGMT_CURRENT_AVAILABILITY;

    drop public synonym MGMT_CURRENT_METRICS;

    drop public synonym MGMT_CURRENT_METRIC_ERRORS;

    drop public synonym MGMT_CURRENT_SEVERITY;

    drop public synonym MGMT_DELTA;

    drop public synonym MGMT_DELTA_ENTRY;

    drop public synonym MGMT_DELTA_ENTRY_VALUES;

    drop public synonym MGMT_DELTA_IDS;

    drop public synonym MGMT_DELTA_ID_VALUES;

    drop public synonym MGMT_DELTA_VALUE;

    drop public synonym MGMT_DELTA_VALUES;

    drop public synonym MGMT_GLOBAL;

    drop public synonym MGMT_GUID_ARRAY;

    drop public synonym MGMT_GUID_OBJ;

    drop public synonym MGMT_IP_TGT_GUID_ARRAY;

    drop public synonym MGMT_JOB;

    drop public synonym MGMT_JOBS;

    drop public synonym MGMT_JOB_EXECPLAN;

    drop public synonym MGMT_JOB_EXECUTION;

    drop public synonym MGMT_JOB_EXEC_SUMMARY;

    drop public synonym MGMT_JOB_OUTPUT;

    drop public synonym MGMT_JOB_PARAMETER;

    drop public synonym MGMT_JOB_SCHEDULE;

    drop public synonym MGMT_JOB_TARGET;

    drop public synonym MGMT_LOG;

    drop public synonym MGMT_LONG_TEXT;

    drop public synonym MGMT_MESSAGES;

    drop public synonym MGMT_METRICS;

    drop public synonym MGMT_METRICS_1DAY;

    drop public synonym MGMT_METRICS_1HOUR;

    drop public synonym MGMT_METRICS_COMPOSITE_KEYS;

    drop public synonym MGMT_METRICS_RAW;

    drop public synonym MGMT_METRIC_COLLECTIONS;

    drop public synonym MGMT_METRIC_ERRORS;

    drop public synonym MGMT_METRIC_THRESHOLDS;

    drop public synonym MGMT_NAME_VALUE;

    drop public synonym MGMT_NAME_VALUES;

    drop public synonym MGMT_PREFERENCES;

    drop public synonym MGMT_SEVERITY;

    drop public synonym MGMT_SEVERITY_ARRAY;

    drop public synonym MGMT_SEVERITY_OBJ;

    drop public synonym MGMT_STRING_METRIC_HISTORY;

    drop public synonym MGMT_TARGET;

    drop public synonym MGMT_TARGETS;

    drop public synonym MGMT_TARGET_BLACKOUTS;

    drop public synonym MGMT_TARGET_MEMBERSHIPS;

    drop public synonym MGMT_TARGET_PROPERTIES;

    drop public synonym MGMT_TYPE_PROPERTIES;

    drop public synonym MGMT_USER;

    drop public synonym MGMT_VIEW_UTIL;

    drop public synonym MGMT$DELTA_ORACLE_HOME;

    drop public synonym MGMT$DELTA_OS_COMPONENTS;

    drop public synonym MGMT$DELTA_OS_COMP_DETAILS;

    drop public synonym MGMT$DELTA_OS_KERNEL_PARAMS;

    drop public synonym MGMT$DELTA_PATCHSETS;

    drop public synonym MGMT$DELTA_PATCHSET_DETAILS;

    drop public synonym MGMT$DELTA_TABLESPACES;

    drop public synonym MGMT$DELTA_VENDOR_SW;

    drop public synonym MGMT$DELTA_VIEW;

    drop public synonym MGMT$DELTA_VIEW_DETAILS;

    drop public synonym MGMT$ECM_CURRENT_SNAPSHOTS;

    drop public synonym MGMT$ECM_VISIBLE_SNAPSHOTS;

    drop public synonym MGMT$GROUP_DERIVED_MEMBERSHIPS;

    drop public synonym MGMT$GROUP_FLAT_MEMBERSHIPS;

    drop public synonym MGMT$GROUP_MEMBERS;

    drop public synonym MGMT$HA_BACKUP;

    drop public synonym MGMT$HA_FILES;

    drop public synonym MGMT$HA_INFO;

    drop public synonym MGMT$HA_INIT_PARAMS;

    drop public synonym MGMT$HA_MTTR;

    drop public synonym MGMT$HA_RMAN_CONFIG;

    drop public synonym MGMT$HW_NIC;

    drop public synonym MGMT$METRIC_COLLECTION;

    drop public synonym MGMT$METRIC_CURRENT;

    drop public synonym MGMT$METRIC_DAILY;

    drop public synonym MGMT$METRIC_DETAILS;

    drop public synonym MGMT$METRIC_HOURLY;

    drop public synonym MGMT$MISSING_TARGETS;

    drop public synonym MGMT$MISSING_TARGETS_IN_GROUPS;

    drop public synonym MGMT$OS_COMPONENTS;

    drop public synonym MGMT$OS_FS_MOUNT;

    drop public synonym MGMT$OS_HW_SUMMARY;

    drop public synonym MGMT$OS_KERNEL_PARAMS;

    drop public synonym MGMT$OS_PATCHES;

    drop public synonym MGMT$OS_SUMMARY;

    drop public synonym MGMT$SOFTWARE_COMPONENTS;

    drop public synonym MGMT$SOFTWARE_COMPONENT_ONEOFF;

    drop public synonym MGMT$SOFTWARE_COMP_PATCHSET;

    drop public synonym MGMT$SOFTWARE_DEPENDENCIES;

    drop public synonym MGMT$SOFTWARE_HOMES;

    drop public synonym MGMT$SOFTWARE_ONEOFF_PATCHES;

    drop public synonym MGMT$SOFTWARE_OTHERS;

    drop public synonym MGMT$SOFTWARE_PATCHES_IN_HOMES;

    drop public synonym MGMT$SOFTWARE_PATCHSETS;

    drop public synonym MGMT$TARGET;

    drop public synonym MGMT$TARGET_COMPONENTS;

    drop public synonym MGMT$TARGET_COMPOSITE;

    drop public synonym MGMT$TARGET_PROPERTIES;

    drop public synonym MGMT$TARGET_TYPE;

    drop PUBLIC SYNONYM SMP_EMD_AVAIL_OBJ;

    drop public synonym EMD_MNTR;

    drop public synonym SMP_EMD_AVAIL_OBJ;

    drop public synonym SMP_EMD_DELETE_REC_ARRAY;

    drop public synonym SMP_EMD_INTEGER_ARRAY;

    drop public synonym SMP_EMD_INTEGER_ARRAY_ARRAY;

    drop public synonym SMP_EMD_NVPAIR;

    drop public synonym SMP_EMD_NVPAIR_ARRAY;

    drop public synonym SMP_EMD_STRING_ARRAY;

    drop public synonym SMP_EMD_STRING_ARRAY_ARRAY;

    drop public synonym SMP_EMD_TARGET_OBJ;

    drop public synonym SMP_EMD_TARGET_OBJ_ARRAY;

    drop public synonym ECM_UTIL;

    drop role mgmt_user;

    drop public synonym SETEMVIEWUSERCONTEXT;

Run OUI and specify installation type as follows. Select Enterprise Manager 10g Grid Control Using an Existing Database. Press Next to continue.

Specify the location e:\OracleHomes and press Next to continue.

The windows appear for a while to inform you that a preparation for install takes place.

Wait until the OUI completes all the of the prerequisites checks. Make sure that there are no errors. After you make sure that there are no errors press Next to continue.

The Screen ‘Specify Repository Database Configuration appears’ after entering the details for the target OMR database I was prompted to:

  1. /rdbms/admin/dbmspool.sql
  2. Session_cached_cursors=300

After successfully implementation of the suggested OMR database reconfiguration press Next to continue.

Enter the details for connection to Metalink as in the case. For the rest specify details that fit for purpose in your case. Press Next to continue.

Specify the password and press Next to continue.

The summary screen appears. Examine the components and make sure that resources on disk are sufficient. Press Install to start the installation.

The next screen shows the progress of the installation. Wait for until completion.

After completion of the installation the Configuration Assistants screen appears. Monitor the progress of the Oracle EM configuration.

The next screen will show a failure. This is known windows bug related to the DST in different time zones. Leave the window and apply patch 5872134 as per Note
419700.1 from a separate session.

In order to continue with successful completion of the Agent Configuration Assistant apply patch 5872134 as per Note
419700.1

Leaving the installer with the “Retry” option available, download the DST agent patch 5872134 for the Windows platform affected and agent version 10.2.0.2.0 and apply to the …\agent10g\ Oracle Home.

When patch application has completed, click the “Retry” button on the primary installer to complete the installation and observe successful agent startup.

Note that the …\oms10g\ and …\db10g\ Oracle Homes will still need be patched for DST according to 409225.1.

NOTE:<<409225.1>> – Impact of 2007 DST changes on Grid Control Release 2 – Preparation and Patching guidelines

Get the information for logging in to the Oracle Enterprise Manager Grid Control and press exit to finish the installation.

See below for information pertaining to your Enterprise Manager Installation:

1. Use the following URL to access the Enterprise Manager Grid Control:

https://userpc.gj.com:1159/em

2. The Enterprise Manager installation includes an Oracle Application Server instance, which is administered using a special “ias_admin” user account. The following information was defaulted for the embedded Application Server instance:

Instance Name: EnterpriseManager0.userpc.gj.com

ias_admin password: This password is the same the SYSMAN account.

3. The connection details for the Enterprise Manager Repository are:

Host: userpc.gj.com

Port: 1521

SID: DB10g

4. The Enterprise Manager Release Notes are located at:

E:\OracleHomes\agent10g\relnotes\README_EM.htm

After login to the Oracle Enterprise Manager Grid Control site we have as below.

This we have successfully installed Oracle Enterprise Manager 10.2.0.2 on windows. Stay tuned for the upgrade to 10.2.0.5.

February 24, 2010 Posted by | oracle | 7 Comments

Patching Oracle Enterprise Manager Grid Control to 10.2.0.5 on OEL 5.4 from Oracle EM Grid Control 10.2.0.2

Patching Oracle Enterprise Manager Grid Control to 10.2.0.5 on OEL 5.4 from Oracle EM Grid Control 10.2.0.2

The article will look at patching Oracle EM Grid Control to version 10.2.0.5. There are two components that we will cover.

  1. Patching OMS
  2. Patching the agent

Patching OMS

From the patch stage directory we start runInstaller. Select the OMS Oracle Home and press Next to continue.

Enter your details and press Next to continue.

Wait for the pre-installation checkups to finish. If there are errors that will prevent you from the installation fix the errors. If you are sure that is safe to continue press Next to continues.

Stop the Oracle EM Grid Control issuing the command below.

./emctl stop oms

Wait for 5 minutes. Press Next to continue.

Enter the password when prompted and press Next to continue.

You are prompted that the Oracle Applications middle-tier will be shutdown. Acknowledge it by pressing OK. Wait for a while and press Next for the upgrade to continue.

Examine the summary. Take a note of the availability of resources and actions that are about to take place. Press Install to continue.

Installation starts and the progress of the update can be monitored. Wait for the installation/upgrade to complete.

Once the upgrade completes you are prompted to run as a root the specified script. Open a new terminal session and execute the scripts.

After executing the scripts as root acknowledge their execution by pressing OK and press Next to continue. The screen snows all configuration assistants that need to be run. Please be patient for the configuration to complete.

After the successful completion of the configuration you will be informed for the final status. If you require the steps do as it advised. Press Exit to exit the upgrade.

Patching the Agent

In this section we will look at agent patching. Run the runInstaller from the staging area that accommodating the 10.2.0.5 patch. Enter the agent Oracle Home.

After entering the agent Oracle Home press Next to continue the upgrade the Oracle EM agent. Enter the details specific for your configuration or leave it for configuring it later.

Wait until OUI completes pre-installations verifications and check up. Fix the errors prior to moving further on. Press Next to continue.

After all the pre-install verifications and checkups are successful press Next to continue. The Summary screen will show you the products to be installed and the resource status. If resources are available and this is what you need press Install to start the upgrade process.

The installation starts to perform the upgrade. Once upgrade is completed you will be asked to execute a shell scripts as a root. Execute the scripts from another terminal session while logged as a root and acknowledge it by pressing OK. Press Next to continue.

This will show you that the agent upgrade has complete successfully. Press Exit button to exit the upgrade process.

Summary

We looked at upgrading the Oracle EM Grid Control from 10.2.0.2 to 10.2.0.5. We step-by-step walked through the upgrade process for both OMS and EM GC agent.

February 19, 2010 Posted by | oracle | Leave a comment

Installing Oracle Grid Control 10.2.0.2 on OEL 5.4

Installing Oracle Grid Control 10.2.0.2 on OEL 5.4

Here we will look at the steps to install Oracle Enterprise Manager Grid Control 10.2.0.2 on OEL 5.4.

Kernel Parameters

Make Sure the Linux kernel parameters are set as specified as below in /etc/systcl.conf

fs.aio-max-nr = 1048576

fs.file-max = 6815744

kernel.shmall = 2097152

kernel.shmax = 536870912

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

net.ipv4.ip_local_port_range = 1024 65500

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 1048586

Activate the parameters with

sysctl -p

Modify /etc/security/limits.conf to include the following.

oracle soft nofile 131072

oracle hard nofile 131072

oracle soft nproc 131072

oracle hard nproc 131072

oracle soft core unlimited

oracle hard core unlimited

oracle soft memlock 3500000

oracle hard memlock 3500000

# Recommended stack hard limit 32MB for oracle installations

# oracle hard stack 32768

Append the following entry to the “/etc/pam.d/login” file.

session required pam_limits.so

Disable secure linux by editing the “/etc/selinux/config” file, making sure the SELINUX flag is set as follows.

SELINUX=disabled

Alternatively, this alteration can be done using the GUI tool (Applications > System Settings > Security Level). Click on the SELinux tab and disable the feature.

Setup

Install the required packages, some of which may already be present.

# From OEL 5.4

cd /media/cdrom/Enterprise/RPMS

rpm -Uvh glibc-2*

rpm -Uvh make-3*

rpm -Uvh binutils-2*

rpm -Uvh gcc-3*

rpm -Uvh libaio-0*

rpm -Uvh glibc-common-2*

rpm -Uvh setarch-1*

rpm -Uvh pdksh-5*

rpm -Uvh openmotif21*

rpm -Uvh sysstat-5*

rpm -Uvh gnome-libs-1*

rpm -Uvh compat-db-4*

rpm -Uvh compat-db-4.1.25-9.i386.rpm

rpm -Uvh control-center-2*

rpm -Uvh xscreensaver-4*

rpm -Uvh glibc-devel-2*

rpm -Uvh glibc-devel-2.3.4-2.43.i386.rpm

rpm -Uvh libgcc-3*

rpm -Uvh compat-gcc*

rpm -Uvh compat-glibc*

rpm -Uvh compat-libgcc-296*

rpm -Uvh libstdc++-devel-3*

rpm -Uvh libgcc-3.4.6-11.0.1.i386.rpm

rpm -Uvh compat-libstdc++-296*

rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm

rpm -Uvh libstdc++-3*

rpm -Uvh openmotif2*

rpm -Uvh freetype-devel*

rpm -Uvh fontconfig-devel*

rpm -Uvh xorg-x11-devel*

rpm -Uvh –force xorg-x11-deprecated-libs*

Create the new groups and users.

groupadd oinstall

groupadd dba

groupadd oper

useradd -g oinstall -G dba oracle

passwd oracle

Create the directories in which the Oracle software will be installed.

mkdir -p /u01/app/oracle/OracleHomes

chown -R oracle.oinstall /u01

Login as root and issue the following command.

xhost +

Login as the oracle user and add the following lines at the end of the “.bash_profile” file:

# Oracle Settings

TMP=/tmp; export TMP

TMPDIR=$TMP; export TMPDIR

ORACLE_BASE=/u01/app/oracle; export ORACLE_BASE

ORACLE_HOME=$ORACLE_BASE/OracleHomes/db10g; export ORACLE_HOME

AGENT_HOME=$ORACLE_BASE/OracleHomes/agent10g; export AGENT_HOME

OMS_HOME=$ORACLE_BASE/OracleHomes/oms10g; export OMS_HOME

ORACLE_HOSTNAME=raclinux2.gj.com; export ORACLE_HOSTNAME

ORACLE_SID=emrep; export ORACLE_SID

ORACLE_TERM=xterm; export ORACLE_TERM

PATH=/usr/sbin:$PATH; export PATH

PATH=$ORACLE_HOME/bin:$PATH; export PATH

LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib; export LD_LIBRARY_PATH

CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib; export CLASSPATH

if [ $USER = “oracle” ]; then

if [ $SHELL = “/bin/ksh” ]; then

ulimit -p 16384

ulimit -n 65536

else

ulimit -u 16384 -n 65536

fi

fi

Pre-install Patching

Download from Metalink patch 6078836 and apply it as per the instructions below.

# To apply the patch, unzip the PSE container file:

#

# % unzip p6078836_101330_Linuxx86.zip

#

# Set your current directory to the directory where the patch

# is located:

#

# % cd 6078836

# As the super-user, copy libdb.so.2 to /usr/lib

#

# % mv /usr/lib/libdb.so.2 /usr/lib/libdb.so.2.6078836 (if libdb.so.2 exist already in /usr/lib)

# % cp libdb.so.2 /usr/lib/libdb.so.2

#

#

# Restart the OHS instances of the iAS instance under repair.

Installation

Launch runInstaller after loggin as oracle user

We will select Enterprise Manager 10 Grid Control Using a New Database. Then press Next.

In the Parent Directory we specify the $ORACLE_BASE/OracleHomes. Press Next to continue.

Wait for the OUI to complete the prerequisite checks. If the result is fine press Next to continue.

Accept the OUI suggested values or change accordingly and press Next to continue.

Here we accept to perform the configurations later. Press Next to Continue.

Specify the passwords and press Next to continue.

Review the Summary and press Install to start the installation process.

Wait while OUI is performing the install. We are notified for the progress of the installation.

Execute as root from a separate terminal session the specified scripts. Press OK to continue.

Wait while OUI is performing the configuration. We are notified for the progress of the installation. Make sure that all configuration assistants complete successfully.

After successful completion of the configuration we are notified for details how to connect to Oracle Enterprise Manager Grid Control using a browser.

After that we launch a browser and login into the Oracle EM Grid Control and look at the repository database.

In this article we looked at the prerequisites for Oracle EM 10.2.0.2 install on OEL. We set the kernel parameters, created the user account and groups. We patched the OEL for Oracle EM Grid Control Installation and installed the Oracle EM Grid Control.

February 12, 2010 Posted by | oracle | Leave a comment

How to discover disk name when LUN number is known (OEL5)

How to discover disk name when LUN number is known (OEL5)

I am creating 11gR2 RAC setup for one of my client. Following Oracle documentation for storage, I opted for Oracle ASM and asked storage team for new physical devices.
Storage admin thus provided me with a set of LUNs instead of actual physical device names like /dev/sdcxxx.

Now the major task is to get the actual device name associated with LUNs.
In OEL4 this is easy to get by issuing

# iscsi-ls -l
This command will give output like:

DEVICE DETAILS:

—————

LUN ID : 0

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

page83 type3: 6001e4f0003fa9970000083c48573c94

page80: 383438303045500a

Device: /dev/sdh

LUN ID : 1

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

page83 type3: 6001e4f0003fbc5b000008dd486dae67

page80: 383438303045500a

Device: /dev/sdl

LUN ID : 2

Vendor: DELL Model: MD3000i Rev: 0670

Type: Direct-Access ANSI SCSI revision: 05

page83 type3: 6001e4f0003fbc5b0000082048574033

page80: 383438303045500a

Device: /dev/sdp

But this command is obsolete in OEL5. The replacement for iscsi-ls in OEL5 is iscsiadm.

In OEL5, there are two ways to get the device name associated with LUN:

1. Use iscsiadm -m host -P 4

# iscsiadm -m host -P 4

It will show the output as:

************************

Attached SCSI devices:

************************

scsi6 Channel 00 Id 0 Lun: 0

Attached scsi disk sdk State: running

scsi6 Channel 00 Id 0 Lun: 1

Attached scsi disk sdm State: running

scsi6 Channel 00 Id 0 Lun: 10

Attached scsi disk sdah State: running

scsi6 Channel 00 Id 0 Lun: 11

Attached scsi disk sdai State: running

scsi6 Channel 00 Id 0 Lun: 13

Attached scsi disk sdap State: running

scsi6 Channel 00 Id 0 Lun: 14

Attached scsi disk sdaq State: running

2. Install the OEL5 package: lsscsi-0.17-3.el5 (or similar version).

# lsscsi -l

It will show the output as:

[6:0:0:22] disk DELL MD3000i 0670 /dev/sdbp

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=60

[6:0:0:24] disk DELL MD3000i 0670 /dev/sdbq

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30

[6:0:0:31] disk DELL Universal Xport 0670 /dev/sdbx

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=60

[6:0:0:32] disk DELL MD3000i 0670 /dev/sdby

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30

[6:0:0:33] disk DELL MD3000i 0670 /dev/sdcg

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=60

[6:0:0:71] disk DELL MD3000i 0670 /dev/sdch

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=60

[6:0:0:72] disk DELL MD3000i 0670 /dev/sdci

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30

[6:0:0:73] disk DELL MD3000i 0670 /dev/sdck

state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=60

Here we can see the LUN numbers in begning:

[6:0:0:73] i.e 73 is the LUN number here.

[6:0:0:72] i.e 72 is the LUN number here.

Finally I created the disks with correct device names.

February 9, 2010 Posted by | oracle | Leave a comment

Installing Oracle GoldenGate for (Oracle 11g on Linux)

Installing Oracle GoldenGate for (Oracle 11g on Linux)

This example will illustrate the installation of Oracle GoldenGate on an RH 5 platform. GoldenGate software is also available on OTN but for our platform we need to download the required software from the Oracle E-Delivery web site.

Select the Product Pack “Oracle Fusion Middleware” and the platform Linux X86-64.

Then select “Oracle GoldenGate on Oracle Media Pack for Linux x86-64″ and since we are installing this for an Oracle 11g database, we download “Oracle GoldenGate V10.4.0.x for Oracle 11g 64bit on RedHat 5.0″

$ unzip V18159-01.zip
Archive: V18159-01.zip
inflating: ggs_redhatAS50_x64_ora11g_64bit_v10.4.0.19_002.tar

$tar -xvof ggs_redhatAS50_x64_ora11g_64bit_v10.4.0.19_002.tar

$ export PATH=$PATH:/u01/oracle/ggs

$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/u01/oracle/ggs

$ ggsci

GGSCI (linuxoel54.gj.com) 1>

GGSCI (linuxoel54.gj.com) 1> CREATE SUBDIRS

Creating subdirectories under current directory /u01/app/oracle/product/11.2.0/db_1

Parameter files /u01/oracle/ggs/dirprm: created

Report files /u01/oracle/ggs/dirrpt: created

Checkpoint files /u01/oracle/ggs/dirchk: created

Process status files /u01/oracle/ggs/dirpcs: created

SQL script files /u01/oracle/ggs/dirsql: created

Database definitions files /u01/oracle/ggs/dirdef: created

Extract data files /u01/oracle/ggs/dirdat: created

Temporary files /u01/oracle/ggs/dirtmp: created

Veridata files /u01/oracle/ggs/dirver: created
Veridata Lock files /u01/oracle/ggs/dirver/lock: created

Veridata Out-Of-Sync files /u01/oracle/ggs/dirver/oos: created

Veridata Out-Of-Sync XML files /u01/oracle/ggs/dirver/oosxml: created

Veridata Parameter files /u01/oracle/ggs/dirver/params: created
Veridata Report files /u01/oracle/ggs/dirver/report: created
Veridata Status files /u01/oracle/ggs/dirver/status: created
Veridata Trace files /u01/oracle/ggs/dirver/trace: created

Stdout files /u01/oracle/ggs/dirout: created

We then need to create a database user which will be used by the GoldenGate Manager, Extract and Replicat processes. We can create individual users for each process or configure just a common user – in our case we will create the one user GGS and grant it the required privileges.

SQL> create tablespace ggs_data
2 datafile ‘/u01/oradata/gavin/ggs_data01.dbf’ size 200m;

SQL> create user ggs identified by ggs
2 default tablespace ggs_data
3 temporary tablespace temp;

User created.

SQL> grant connect,resource to ggs;

Grant succeeded.

SQL> grant select any dictionary, select any table to ggs;

Grant succeeded.

SQL> grant create table to ggs;

Grant succeeded.

SQL> grant flashback any table to ggs;

Grant succeeded.

SQL> grant execute on dbms_flashback to ggs;

Grant succeeded.

SQL> grant execute on utl_file to ggs;

Grant succeeded.

We can then confirm that the GoldenGate user we have just created is able to connect to the Oracle database

$ ggsci

Oracle GoldenGate Command Interpreter for Oracle
Version 10.4.0.19 Build 002

Linux, x64, 64bit (optimized), Oracle 11 on Sep 17 2009 23:51:28

Copyright (C) 1995, 2009, Oracle and/or its affiliates. All rights reserved.

GGSCI (linuxoel54.gj.com) 1> DBLOGIN USERID ggs, PASSWORD ggs
Successfully logged into database.

We also need to enable supplemental logging at the database level otherwise we will get this error when we try to start the Extract process –

2010-02-08 13:51:21 GGS ERROR 190 No minimum supplemental logging is enabled. This may cause extract process to handle key update incorrectly if key
column is not in first row piece.

2010-02-08 13:51:21 GGS ERROR 190 PROCESS ABENDING.

SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

Database altered

February 8, 2010 Posted by | oracle | 4 Comments

Oracle GoldenGate Concepts and Architecture

Oracle GoldenGate Concepts and Architecture

GoldenGate enables us to extract and replicate data across a variety of topologies as shown the diagram below as well as the exchange and manipulation of data at the transactional level between a variety of database platforms like Oracle, DB2, SQL Server, Ingres, MySQL etc.

It can support a number of different business requirements like:

Business Continuity and High Availability

Data migrations and upgrades

Decision Support Systems and Data Warehousing

Data integration and consolidation


Let us know look at the different components and processes that make up a typical GoldenGate configuration on Oracle.


(source: Oracle GoldenGate Administration Guide)

Manager

The Manager process must be running on both the source as well as target systems before the Extract or Replicat process can be started and performs a number of functions including monitoring and starting other GoldenGate processes, managing the trail files and also reporting.

Extract

The Extract process runs on the source system and is the data capture mechanism of GoldenGate. It can be configured both for initial loading of the source data as well as to synchronize the changed data on the source with the target. This can be configured to also propagate any DDL changes on those databases where DDL change support is available.

Replicat

The Replicat process runs on the target system and reads transactional data changes as well as DDL changes and replicates then to the target database. Like the Extract process, the Replicat process can also be configured for Initial Load as well as Change Synchronization.

Collector

The Collector is a background process which runs on the target system and is started automatically by the Manager (Dynamic Collector) or it can be configured to start manually (Static Collector). It receives extracted data changes that are sent via TCP/IP and writes then to the trail files from where they are processed by the Replicat process.

Trails

Trails are series of files that GoldenGate temporarily stores on disks and these files are written to and read from by the Extract and Replicat processes as the case may be. Depending on the configuration chosen, these trail files can exist on the source as well as on the target systems. If it exists on the local system, it will be known an Extract Trail or as a Remote Trail if it exists on the target system.

Data Pumps

Data Pumps are secondary extract mechanisms which exist in the source configuration. This is optional component and if Data Pump is not used then Extract sends data via TCP/IP to the remote trail on the target. When Data Pump is configured, the Primary Extract process will write to the Local Trail and then this trail is read by the Data Pump and data is sent over the network to Remote Trails on the target system.

In the absence of Data Pump, the data that the Extract process extracts resides in memory alone and there is no storage of this data anywhere on the source system. In case of network of target failures, there could be cases where the primary extract process can abort or abend. Data Pump can also be useful in those cases where we are doing complex filtering and transformation of data as well as when we are consolidating data from many sources to a central target.

Data source

When processing transactional data changes, the Extract process can obtain data directly from the database transaction logs (Oracle, DB2, SQL Server, MySQL etc) or from a GoldenGate Vendor Access Module (VAM) where the database vendor (for example Teradata) will provide the required components that will be used by Extract to extract the data changes.

Groups

To differentiate between the number of different Extract and Replicat groups which can potentially co-exist on a system, we can define processing groups. For instance, if we want to replicate different sets of data in parallel, we can create two Replicat groups.

A processing group consists of a process which could be an Extract or Replicat process, a corresponding parameter file, checkpoint file or checkpoint table (for Replicat) and other files which could be associated with the process.

February 7, 2010 Posted by | oracle | 1 Comment