Guenadi N Jilevski's Oracle BLOG

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

Managing Data Guard 11g R2 with OEM 11g

Managing Data Guard 11g R2 with OEM 11g

In this article we will look at what OEM offers to manage Data Guard. We will see how Flashback database and Data guard can be managed with OEM to build a DR solution. OEM Gird Control is an enterprise tool offering a centralized console for management and monitoring enterprise systems. The post look at how OEM can be used to manage and monitor Data Guard configurations. There are wizards automating most important Data Guard activities in OEM and the paper covers in details the OEM wizards related to Data Guard. Data guard features combined with Flashback database feature allow to achieve an ultimate DR strategy for the business allowing a flexibility in deploying different Data Guard configurations that is, different Data Guard modes, attributes, Active Data Guard, Snapshot Data guard, Fast start Failover and fast and reliable standby database reinstate after failover to name a few. OEM enables us to perform the following tasks related to Data Guard.

  • Creating a new physical standby database
  • Creating a new logical standby database
  • Adding an existing standby database for management with Data Guard broker
  • Monitoring performance of a Data Guard configuration
  • Monitoring archiving and applying of redo log
  • Verifying structure of Data Guard Configuration
  • Performing switchover and failover
  • Setting Active Data Guard
  • Setting Snapshot Data Guard
  • Manage Data Guard Configuration modes and properties. Setting fast start failover.
  • There are various backup options to choose from when creating a standby database.

 

We assume that the database that we will designate as a primary database is configured as follows:

  • Running in archive log mode
  • The primary database has flashback database turned ON.
  • Parameter LOCAL_LISTENER is set even if listening on default port 1521. It is a must to set the LOCAL_LISTENER for ports different from the default.

 

We are using Oracle 11g R2 Grid Infrastructure and RDBMS software and OEM 11g. Below we are going to look at few of the OEM Data Guard automation features.

  1. Let’s create a physical standby database.

     

    Select a primary database.

    Navigate to Availability tab and select Add Standby Database link.

    Click on the Add Standby Database Link. Note that the link will appear only if there is no Data Guard configuration created for the primary database.

    Select create a new physical standby database link. Here the options are to create a physical or logical database, register an existing standby database for management with a data guard broker or creating a backup that later will be used for creating standby databases.

    Select Online Backup. This will create and run a job backing up the primary database and creating the standby database. The option of using an existing backup will create and run a job creating the standby database using already existing database backup.

    Specify the requested backup options and credentials.

    Specify the details for the standby database.

    Specify the standby database file location and FRA details. Select Listener configuration.

    Specify the standby database details as specified below. Configure Oracle restart and Data guard broker.

    Review details prior submission and press Finish. If at any time a change is necessary press the Back button. Press Next to move forward.

    The display explains what is happening.

    We will let it finish, once done a job is submitted to create the standby database. Pressing Cancel will terminate the process. Click Creation in progress link in the Data Guard Status.

    Here we can monitor the details and status of the standby database creation job.

    Pressing Job activity will show the job status presently is in progress.

    Wait until the job succeeds.

    Upon successful job completion we have the following configuration.

    We also have a set of links to manage the Data Guard configuration.

  2. Verify Data Guard configuration

     

    Click on the Verify configuration link.

    Upon successful completion the status will be as displayed on the screenshot below. We confirmed that the physical standby database is created successfully.

  3. Data Guard Performance

     

    Click on the Performance link and start a test application to generate a load on the primary database. What we are interested in are the redo generation rate, redo apply rate and the transport and apply lag.

    After running for a while the application generating a load on the primary database we will have more meaningful data gathered as displayed on the screenshot below.

    We can further drill down and look at details of the Transport Lag.

    We can further drill down and look at details of the redo generation rate.

    We can further drill down and look at details of the redo apply rate.

  4. Managing Data Guard Properties

     

    Click Edit properties link.

    In the general properties tab we can toggle on and off redo apply. This translates into having Managed Recovery Process (MRP) process running or stopped on the standby database. Enable real time query check box activates/deactivates the Active Data Guard.

    Selecting Enable Real-time query check box will activate the Active Data Guard.

    Standby Role properties tab enables us to specify series of properties such as redo transport mode SYNC/ASYNC, redo compression to name a few.

    Common properties tab enables us to set the listed properties.

    Once the properties are set press Apply.

  5. Managing Data Guard Mode

     

    Here we can specify the Data Guard mode. Let’s choose maximum protection and press Continue.

    Press Continue.

    Confirm to continue.

    Now we have a Data Guard configuration in maximum protection mode.

  6. Managing Switchover

     

    Select a standby database (from the list of standby databases) that will become a primary and press Switchover.

    Specify whether to swap the monitoring settings and confirm the switchover.

    Upon successful completion of the switchover we get a confirmation and a role reversal.

  7. Managing & Setting fast start failover

     

    Click on the link specifying the status of the fast start failover.

    In the Configure Observer page specify the details for the observer.

    Clicking the Observer button show a list of discovered target hosts and Oracle home for the observer.

    After selecting the host and Oracle home press OK. We are prompted to enable flashback database feature as indicated. Enter the specifics and press Continue.

    Confirm to continue.

    Wait for the processing to complete.

    We are back to the Data Guard page with a confirmation of success in enabling FSFO.

  8. Managing Failover & reinstate former primary as a new standby database

     

    Select a database from the list of standby databases to become a new primary and press Convert button. Page appears asking to select a failover option and whether to swap monitoring settings and jobs. Confirm to continue.

    Wait for the failover to complete.

    When until the failover completes. We have a role reversal the former standby database is a primary and the old primary must be reinstated to become a standby database. Click on the link related to the Data Guard status (Database must be reinstated link).

    In the properties page is indicated that the former primary needs to be reinstated to become a standby database. Press Reinstate button.

    Confirm to continue.

    Wait for the process to continue.

    If the reinstate is successful we will have a valid Data Guard with a new standby database.

    If the reinstate fails create a new standby database.

  9. Managing creation of a logical standby

     

    Select create a new logical standby database. Press Continue.

    Select the type of the backup for the standby database creation. Note that currently there are no tables unsupported by SQL Apply.

    Select the type of the backup for the standby database creation. Note that currently there are table unsupported by SQL Apply. Address unsupported tables and continue with the standby database creation pressing Next. Select Online backup (Use RMAN to copy database files)

    Next pages are similar to the pages for physical database creation. Select the backup options and press Next.

    Select standby database attributes, standby database location and standby host credentials. Press Next to continue.

    Specify the standby database locations, FRA and listener configuration. Press Next to continue.

    Specify the configuration parameters requested and press Next to continue.

    After reviewing the configuration press submit. Again as in the case of a physical standby creation a job is submitted.

    Wait for the job to complete. After completion we will have the new Data Guard configuration. Available databases are shown below.

    The Data Guard configuration managed and monitored by OEM is as follows.

    Performance page will show now all standby databases as show below.

  10. Monitor Archived and Applied redo logs

     

    Log File Details link will show the status of the redo transfer and apply.

    Note the progress of redo apply.

  11. Manage Active Data Guard

     

    Enable Real-time Query property enables Active Data Guard. Check the box Enable Real-time Query and press Apply.

    After completion we will have an Active Data Guard as show below.

  12. Manage Snapshot Data Guard

     

    Make sure that the databases have flashback database turned on. Select a database from the list of standby databases and press Convert.

    Confirm the conversion.

    Wait for the conversion to complete.

    Upon completion we will have a snapshot standby database.

    Select the snapshot database and press Convert. Confirm the conversion.

    We have a physical standby database

    Once the standby database is with flashback database feature turned on we can toggle on and off between a physical standby database and snapshot standby database.

  13. Manage standby database create process – options for create standby database

     

    We have multiple options to backup a database for standby creation. So far we used to make a backup and create a standby database in one job. This is if we choose an Online Backup option.

    1. Backup to stage

       

    Select Create a Primary Database backup only. Press Continue.

    Specify the staging area and primary host credentials.

    Schedule the primary database backup.

    Select Backup from a previous standby database creation

    Enter the primary host credentials.

    Specify the standby database attributes, standby host credentials and staging area holding the backup.

    Enter the standby database files location. Press Next to continue.

    In the configuration page specify Standby Database Parameters, enable Oracle Restart and specify standby database monitoring credentials.

    Review and press Finish. Note that Backup Type has changed from Online Backup to Existing Backup.

    1. Regular level 0 database backup.

       

     

  14. Remove a standby database from Data Guard configuration and Remove a Data Guard configuration. Remove button removes a database from the Data Guard configuration. The Remove a Data Guard Configuration link removes the whole data guard configuration.

    Summary

    We looked at how to create a standby database, how to set the Data Guard modes and properties. We performed a switchover and failover and the respective ex-primary reinstatement to a new standby database. We looked at converting a physical standby to snapshot standby or active data guard. We covered log file monitoring, and Data Guard performance monitoring. We explained how to use OEM 11g to manage standby database in Data Guard Broker configuration.

July 24, 2010 Posted by | oracle | 2 Comments

Installing OEM 11g on OEL 5.5

Installing OEM 11g on OEL 5.5

In this article we will looks at installing OEM Grid Control11 g. The OEM Grid Control 11g install requires an existing Oracle 11g database (11R1 or 11gR2) and Oracle WebLogic server 11g 10.3.2 both patched as specified here in Oracle installation documentation. Oracle OEM Grid Control 10g used to come bundled with Oracle Application server 10g (traditional Apache and OC4J) and an option to install database for OMR or use an already existing database for OMR. OEM Grid Control versions 11g instead contrary to previous versions requires that Oracle WebLogic server be installed and OEM OMR database be created prior to the install. The install in this post uses OEL 5.5, Oracle Web server 11g 10.3.2 and existing Oracle database 11gR2. Some patches need to be installed to the existing oracle RDBMS and Grid Infrastructure homes and to Oracle WebLogic Server. The documentation requires that patches for database bugs 9002336 and 9067282 be applied. Patch 9002336 has a prerequisite of patch 9352237, which includes patch 9067282, so only patches 9352237 and 9002336 will be applied.

Download the following software components using the following links

  1. OEL 5.5
  2. Oracle 11gR2 for linux.
  3. OPatch latest version
  4. Oracle WebLogic Server 10.3.2.
  5. Java SE Development Kit 6u18
  6. OEM GC 11gR1
  7. Patch 9002336 and patch 9352237

Install OEL 5.5 as show in the post related to installing OEL 5.5, click here for further information.

Make sure packages required to install Oracle 11g R2 are present.

  • binutils-2.*
  • compat-libstdc++-33*
  • elfutils-libelf-0.*
  • elfutils-libelf-devel-*
  • gcc-4.*
  • gcc-c++-4.*
  • glibc-2.*
  • glibc-common-2.*
  • glibc-devel-2.*
  • glibc-headers-2.*
  • ksh-2*
  • libaio-0.*
  • libaio-devel-0.*
  • libgcc-4.*
  • libstdc++-4.*
  • libstdc++-devel-4.*
  • make-3.*
  • sysstat-7.*
  • unixODBC-2.*
  • unixODBC-devel-2.*

 

For example if packages are not installed install them as specified below:

[root@raclinux1 Server]# rpm -Uvh unixODBC-2.*

warning: unixODBC-2.2.11-7.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 1e5e0159

Preparing… ########################################### [100%]

……………………………………………………………………………………………………

 

For OEM11g make sure the following packages are installed.

  • compat-db-4*
  • compat-libstdc++-296*
  • rng-utils-2*
  • setarch-2*

 

Install Oracle 11g R2 Grid Infrastructure and RDBMS and create database to serve as OMR.

Staging area will look as follow.

Change the permissions for JDK:

chmod +x jdk -6u18-linux-i586-rpm.bin

Start the JDK by issuing the below command to install jdk

[oracle@raclinux1 u01]$ ./jdk-6u18-linux-i586-rpm.bin

Sun Microsystems, Inc. Binary Code License Agreement

 

for the JAVA SE DEVELOPMENT KIT (JDK), VERSION 6

 

SUN MICROSYSTEMS, INC. (“SUN”) IS WILLING TO LICENSE THE

SOFTWARE IDENTIFIED BELOW TO YOU ONLY UPON THE CONDITION

THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS BINARY

…………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………

Network Circle, Santa Clara, California 95054, U.S.A.

 

 

Do you agree to the above license terms? [yes or no]

yes

Unpacking…

Checksumming…

Extracting…

UnZipSFX 5.50 of 17 February 2002, by Info-ZIP (Zip-Bugs@lists.wku.edu).

replace jdk-6u18-linux-i586.rpm? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

inflating: jdk-6u18-linux-i586.rpm

inflating: sun-javadb-common-10.5.3-0.2.i386.rpm

inflating: sun-javadb-core-10.5.3-0.2.i386.rpm

inflating: sun-javadb-client-10.5.3-0.2.i386.rpm

inflating: sun-javadb-demo-10.5.3-0.2.i386.rpm

inflating: sun-javadb-docs-10.5.3-0.2.i386.rpm

inflating: sun-javadb-javadoc-10.5.3-0.2.i386.rpm

error: can’t create transaction lock on /var/lib/rpm/__db.000

 

Java(TM) SE Development Kit 6 successfully installed.

 

Product Registration is FREE and includes many benefits:

* Notification of new versions, patches, and updates

* Special offers on Sun products, services and training

* Access to early releases and documentation

 

Product and system data will be collected. If your configuration

supports a browser, the Sun Product Registration form for

the JDK will be presented. If you do not register, none of

this information will be saved. You may also register your

JDK later by opening the register.html file (located in

the JDK installation directory) in a browser.

 

For more information on what data Registration collects and

how it is managed and used, see:

http://java.sun.com/javase/registration/JDKRegistrationPrivacy.html

 

Press Enter to continue…..

 

Done.

[oracle@raclinux1 u01]$

 

Install OWLS 11g 10.3.2 typing ./ oepe111130_wls1032_linux32.bin as oracle at the prompt in /u01/app/oracle/Middleware.

Install Oracle WebLogic Server 10.3.2 as shown here. Note OWLS 10.3.3 cause OEM 11g installation to fail.

Prepare the repository database. If you have performed a default installation you will need to de-configure Enterprise Manager Database Control. Run the following command as the “oracle” user.

$ emca -deconfig dbcontrol db -repos drop -SYS_PWD -SYSMAN_PWD

The output of the command is as follow:

[oracle@raclinux1 ~]$ emca -deconfig dbcontrol db -repos drop -SYS_PWD sys1 -SYSMAN_PWD sysman

[oracle@raclinux1 ~]$ env | grep REP11gR2

[oracle@raclinux1 ~]$ env | grep ORA

ORACLE_UNQNAME=RACDB

ORACLE_SID=REP11GR2

ORACLE_BASE=/u01/app/oracle

ORACLE_HOSTNAME=raclinux1.gj.com

ORACLE_TERM=xterm

ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1

[oracle@raclinux1 ~]$ emca -deconfig dbcontrol db -repos drop -SYS_PWD sys1 -SYSMAN_PWD sysman

 

STARTED EMCA at Jul 9, 2010 10:37:18 AM

EM Configuration Assistant, Version 11.2.0.0.2 Production

Copyright (c) 2003, 2005, Oracle. All rights reserved.

 

Enter the following information:

Database SID: REP11GR2

Listener port number: 1521

 

Do you wish to continue? [yes(Y)/no(N)]: Y

Jul 9, 2010 10:37:50 AM oracle.sysman.emcp.EMConfig perform

INFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/REP11/emca_2010_07_09_10_37_17.log.

Jul 9, 2010 10:37:52 AM oracle.sysman.emcp.util.DBControlUtil stopOMS

INFO: Stopping Database Control (this may take a while) …

Jul 9, 2010 10:43:17 AM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl

WARNING: Error initializing SQL connection. SQL operations cannot be performed

Jul 9, 2010 10:43:17 AM oracle.sysman.emcp.EMReposConfig invoke

INFO: Dropping the EM repository (this may take a while) …

Jul 9, 2010 10:58:51 AM oracle.sysman.emcp.EMReposConfig invoke

INFO: Repository successfully dropped

Enterprise Manager configuration completed successfully

FINISHED EMCA at Jul 9, 2010 10:59:20 AM

[oracle@raclinux1 ~]$

 

Make the following initialization parameter changes.

ALTER SYSTEM SET log_buffer=10485760 SCOPE=SPFILE;

ALTER SYSTEM SET processes=500 SCOPE=SPFILE;

ALTER SYSTEM SET session_cached_cursors=200 SCOPE=SPFILE;

 

Now bounce the instance for changes to take effect. Make sure that UNDO tablespace is at least 300MB.

The documentation states that patches for database bugs 9002336 and 9067282 must be applied. Those patches need to be applied to BOTH RDBMS and Grid Infrastructure homes. Next we must install the latest version of the “opatch” utility and unzip the patches.

 

 

$ unzip -o p6880880_112000_Linux.zip

$unzip –o p9002336_112000_Linux.zip

$unzip –o p9067282_112000_Linux.zip

 

The screenshot confirms that the Opatch and the requested patches are unzipped.

Make sure that

  1. in RDBMS home listener and databases are down
  2. in grid infrastructure home listener and ASM database are down

Patching RDBMS and Grid Infrastructure details:

  1. Applying patch 9352237

[oracle@raclinux1 9352237]$ export PATH=$PATH:/u01/OPatch

[oracle@raclinux1 9352237]$ opatch apply

Invoking OPatch 11.2.0.1.2

 

Oracle Interim Patch Installer version 11.2.0.1.2

Copyright (c) 2010, Oracle Corporation. All rights reserved.

 

 

Oracle Home : /u01/app/oracle/product/11.2.0/db_1

Central Inventory : /u01/app/oraInventory

from : /etc/oraInst.loc

OPatch version : 11.2.0.1.2

OUI version : 11.2.0.1.0

OUI location : /u01/app/oracle/product/11.2.0/db_1/oui

Log file location : /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch2010-07-09_18-54-32PM.log

 

Patch history file: /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

 

ApplySession applying interim patch ‘9352237’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

 

Running prerequisite checks…

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

 

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]:

Email address/User Name: gjilevski@gmail.com

Provide your My Oracle Support password to receive security updates via your My Oracle Support account.

Password (optional):

 

Unable to establish a network connection to Oracle. If your systems require a

proxy server for outbound Internet connections, enter the proxy server details

in this format:

[<proxy-user>@]<proxy-host>[:<proxy-port>]

If you want to remain uninformed of critical security issues in your

configuration, enter NONE

Proxy specification:

An invalid proxy specification was given. Please re-enter the proxy information.

 

Unable to establish a network connection to Oracle. If your systems require a

proxy server for outbound Internet connections, enter the proxy server details

in this format:

[<proxy-user>@]<proxy-host>[:<proxy-port>]

If you want to remain uninformed of critical security issues in your

configuration, enter NONE

Proxy specification:

An invalid proxy specification was given. Please re-enter the proxy information.

 

Unable to establish a network connection to Oracle. If your systems require a

proxy server for outbound Internet connections, enter the proxy server details

in this format:

[<proxy-user>@]<proxy-host>[:<proxy-port>]

If you want to remain uninformed of critical security issues in your

configuration, enter NONE

Proxy specification: NONE

 

 

 

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

 

 

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’)

 

 

Is the local system ready for patching? [y|n]

Could not recognize input. Please re-enter.

y

User Responded with: Y

Backing up files and inventory (not for auto-rollback) for the Oracle Home

Backing up files affected by the patch ‘9352237’ for restore. This might take a while…

Backing up files affected by the patch ‘9352237’ for rollback. This might take a while…

Execution of ‘sh /u01/9352237/custom/scripts/pre -apply 9352237 ‘:

 

 

Return Code = 0

 

Patching component oracle.rdbms.rsf, 11.2.0.1.0…

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libpls11.a” with “lib/libpls11.a/phd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libpls11.a” with “lib/libpls11.a/ph2drv.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libpls11.a” with “lib/libpls11.a/ph2oa.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/kot.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/kgh.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/kgl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/kgl2.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/kgl4.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libgeneric11.a” with “lib/libgeneric11.a/qct.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libcommon11.a” with “lib/libcommon11.a/kdzt.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libcommon11.a” with “lib/libcommon11.a/sagedata.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libcommon11.a” with “lib/libcommon11.a/kdzilcs.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libcommon11.a” with “lib/libcommon11.a/kdzc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/libdbtools11.a” with “rdbms/lib/libdbtools11.a/krmq.o”

 

Patching component oracle.rdbms.dbscripts, 11.2.0.1.0…

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/admin/prvtamgt.plb”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/admin/utlu112i.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/admin/utlu112x.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/admin/catexp.sql”

 

Patching component oracle.rdbms, 11.2.0.1.0…

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdt.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kspt.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kxtt.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktcnq.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktu.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktur.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjbr.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/k2g.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfafo.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfcfg.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfmboot.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfmedd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfmrole.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/rfsicd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdo.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktcn.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktg.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktfa.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktud.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/aud.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kzam.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kxs.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kks.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kks1.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kksc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfda.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfdp.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfds.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kff.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfio.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfio0.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfn.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfnb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfnc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfns.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kfnm.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ksfd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kkopq.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kxfp.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kxfr.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kxfxq.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjbl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ksucln.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ksk.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ksu.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdlw.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdst00.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdst01.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdst11.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdstrr.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcfis.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbz.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktsla.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktslm.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/koks3.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdu.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kqf.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kwqa.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kwqm.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kko.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjxgf.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjxgg.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjxgm.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjxgr.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/qesrc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/qkna.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/qksrc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kkqtutl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kkqs.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/knlb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbk.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kzu.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktt.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kjbm.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/qksvc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ksmg.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdbl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdzh.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdblc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdst.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktein.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbs.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbz.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktsp.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdblc.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdo.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktsf.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/atb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kwqid.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdlrci.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdlxdup.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kmgs.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kmgsb.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kzvdve.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/qks3t.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kcbi.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdli.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/skptch.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/ktslj.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kdza.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/libknlopt.a” with “rdbms/lib/libknlopt.a/ktd.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/libknlopt.a” with “rdbms/lib/libknlopt.a/jox.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.a” with “lib/libasmclnt11.a/kgf.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.a” with “lib/libasmclnt11.a/kgfdp.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.a” with “lib/libasmclnt11.a/kgfdputl.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.a” with “lib/libasmclnt11.a/kgfn.o”

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.a” with “lib/libasmclnt11.a/kgfo.o”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/ktd.o”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/jox.o”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/kfod.o”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/mkpatch.o”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/ins_rdbms.mk”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/lib/env_rdbms.mk”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/xml/xsl/kulob.xsl”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/xml/xsl/kustorag.xsl”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/cpu/scripts/bug9371993.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/cpu/scripts/bug9016295.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/psu/scripts/bug8820324.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/psu/11.2.0.1.1/catpsu.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/psu/11.2.0.1.1/catpsu_rollback.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/rdbms/admin/bundledata_PSU.xml”

 

Patching component oracle.oraolap, 11.2.0.1.0…

Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/liboraolap11.a” with “lib/liboraolap11.a/xscarrot.o”

 

Patching component oracle.rdbms.deconfig, 11.2.0.1.0…

Copying file to “/u01/app/oracle/product/11.2.0/db_1/lib/libasmclnt11.so”

 

Patching component oracle.javavm.server, 11.2.0.1.0…

Copying file to “/u01/app/oracle/product/11.2.0/db_1/javavm/install/jvm_exp.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/javavm/install/initjvm.sql”

Copying file to “/u01/app/oracle/product/11.2.0/db_1/javavm/install/jvmursc.sql”

Running make for target client_sharedlib

Running make for target irman

Running make for target ikfod

Running make for target irenamedg

Running make for target idgmgrl

Running make for target imkpatch

Running make for target client_sharedlib

Running make for target ioracle

ApplySession adding interim patch ‘9352237’ to inventory

 

Verifying the update…

Inventory check OK: Patch ID 9352237 is registered in Oracle Home inventory with proper meta-data.

Files check OK: Files from Patch ID 9352237 are present in Oracle Home.

 

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

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

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

** ATTENTION **

** **

** Please note that the Patch Set Update Installation (PSU Deinstallation) **

** is not complete until all the Post Installation (Post Deinstallation) **

** instructions noted in the Readme accompanying this PSU, have been **

** successfully completed. **

** **

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

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

 

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

 

Execution of ‘sh /u01/9352237/custom/scripts/post -apply 9352237 ‘:

 

 

Return Code = 0

 

The local system has been patched and can be restarted.

 

  • Applying patch 9002336

     

    [oracle@raclinux1 u01]$ cd 9002336

    [oracle@raclinux1 9002336]$ opatch apply

    Invoking OPatch 11.2.0.1.2

     

    Oracle Interim Patch Installer version 11.2.0.1.2

    Copyright (c) 2010, Oracle Corporation. All rights reserved.

     

     

    Oracle Home : /u01/app/oracle/product/11.2.0/db_1

    Central Inventory : /u01/app/oraInventory

    from : /etc/oraInst.loc

    OPatch version : 11.2.0.1.2

    OUI version : 11.2.0.1.0

    OUI location : /u01/app/oracle/product/11.2.0/db_1/oui

    Log file location : /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch2010-07-09_20-20-32PM.log

     

    Patch history file: /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

     

    ApplySession applying interim patch ‘9002336’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

     

    Running prerequisite checks…

     

    OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

     

     

    Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

    (Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’)

     

     

    Is the local system ready for patching? [y|n]

    y

    User Responded with: Y

    Backing up files and inventory (not for auto-rollback) for the Oracle Home

    Backing up files affected by the patch ‘9002336’ for restore. This might take a while…

    Backing up files affected by the patch ‘9002336’ for rollback. This might take a while…

     

    Patching component oracle.rdbms, 11.2.0.1.0…

    Updating archive file “/u01/app/oracle/product/11.2.0/db_1/lib/libserver11.a” with “lib/libserver11.a/kkqtutl.o”

    Running make for target ioracle

    ApplySession adding interim patch ‘9002336’ to inventory

     

    Verifying the update…

    Inventory check OK: Patch ID 9002336 is registered in Oracle Home inventory with proper meta-data.

    Files check OK: Files from Patch ID 9002336 are present in Oracle Home.

     

    The local system has been patched and can be restarted.

     

     

    OPatch succeeded.

    [oracle@raclinux1 9002336]$

    OPatch succeeded.

    [oracle@raclinux1 9352237]$

     

    1. Applying patch 9004119

    [oracle@raclinux1 u01]$ cd 9004119

    [oracle@raclinux1 9004119]$ ls

    etc files README.txt

    [oracle@raclinux1 9004119]$ opatch apply

    Invoking OPatch 11.2.0.1.2

     

    Oracle Interim Patch Installer version 11.2.0.1.2

    Copyright (c) 2010, Oracle Corporation. All rights reserved.

     

     

    Oracle Home : /u01/app/oracle/product/11.2.0/db_1

    Central Inventory : /u01/app/oraInventory

    from : /etc/oraInst.loc

    OPatch version : 11.2.0.1.2

    OUI version : 11.2.0.1.0

    OUI location : /u01/app/oracle/product/11.2.0/db_1/oui

    Log file location : /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch2010-07-09_21-23-36PM.log

     

    Patch history file: /u01/app/oracle/product/11.2.0/db_1/cfgtoollogs/opatch/opatch_history.txt

     

    ApplySession applying interim patch ‘9004119’ to OH ‘/u01/app/oracle/product/11.2.0/db_1’

     

    Running prerequisite checks…

     

    OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

     

     

    Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

    (Oracle Home = ‘/u01/app/oracle/product/11.2.0/db_1’)

     

     

    Is the local system ready for patching? [y|n]

    y

    User Responded with: Y

    Backing up files and inventory (not for auto-rollback) for the Oracle Home

    Backing up files affected by the patch ‘9004119’ for restore. This might take a while…

    Backing up files affected by the patch ‘9004119’ for rollback. This might take a while…

     

    Patching component oracle.rdbms, 11.2.0.1.0…

    Copying file to “/u01/app/oracle/product/11.2.0/db_1/bin/racone2rac”

    Copying file to “/u01/app/oracle/product/11.2.0/db_1/bin/Omotion”

    Copying file to “/u01/app/oracle/product/11.2.0/db_1/bin/raconefix”

    Copying file to “/u01/app/oracle/product/11.2.0/db_1/bin/raconeinit”

    Copying file to “/u01/app/oracle/product/11.2.0/db_1/bin/raconestatus”

    ApplySession adding interim patch ‘9004119’ to inventory

     

    Verifying the update…

    Inventory check OK: Patch ID 9004119 is registered in Oracle Home inventory with proper meta-data.

    Files check OK: Files from Patch ID 9004119 are present in Oracle Home.

     

    The local system has been patched and can be restarted.

     

     

    OPatch succeeded.

    [oracle@raclinux1 9004119]$

    Patching OWLS

    Form /u01/app/oracle/Middleware/utils/bsu start bsu.sh. Enter the My Oracle Support (MOS) formerly Metalink credentials.

    In the Downloaded Patches section patch WDJ7 will appear. Select to apply the patch. After applying the patch in the Default section we will have WDJ7 as show bellow. Select File and Exit to Exit bsu utility.

    Installing Oracle EM Grid Control 11g

    We installed Oracle 11g R2 grid infrastructure. After that we installed Oracle RDBMS and created two databases on ASM for the OMR and for testing. We patched both Oracle RDBMS and grid infrastructure homes with patches 9352237, 9002336 required for OEM 11g and patch 9004119 for RAC ONE node utilities. We patched the OWLS with the patch WDJ7 required as per the documentation.

    We unzip with ‘unzip –o <zipfile> ‘ the OEM11 downloads and then we start the installation as show below from the stage.

    Either enter the MOS credentials or uncheck the box. After that press Next to continue.

    If the box has been left unchecked confirm that Configuration Manager will be set at a later stage.

    Select Skip updates and press Next to continue.

    Select Install a new enterprise manager system. Press Next to continue.

    Wait dor the prerequisite checks to complete. Press Next to continue.

    Specify the OMS instance base location and Middleware home location. Press Next to continue.

    Specify the requested details for the new Grid Control domain that will be created during the course of OEM install and configuration. Press Next to continue.

    Specify the details for the OMR. Press Next to continue.

    Specify the sysman password end the location for the new tablespaces for OEM. Press Next to continue.

    Examine the ports and press Next to continue.

    Review the installation information and press Install to continue.

    Wait for the installation to complete.

    When installation completes you will be prompted to install the scripts specified as a root. Once done press OK to continue with the configuration of OEM 11g.

    The output of allroot.sh is as follows:

    [root@raclinux1 oms11g]# ./allroot.sh

     

    Starting to execute allroot.sh ………

     

    Starting to execute /u01/app/oracle/Middleware/oms11g/root.sh ……

    Running Oracle 11g root.sh script…

     

    The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME= /u01/app/oracle/Middleware/oms11g

     

    Enter the full pathname of the local bin directory: [/usr/local/bin]:

    The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

    The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

    The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

     

    Entries will be added to the /etc/oratab file as needed by

    Database Configuration Assistant when a database is created

    Finished running generic part of root.sh script.

    Now product-specific root actions will be performed.

    Adding entry to /etc/oratab file…

    Finished execution of /u01/app/oracle/Middleware/oms11g/root.sh ……

     

     

    Starting to execute /u01/app/oracle/Middleware/agent11g/root.sh ……

    Running Oracle 11g root.sh script…

     

    The following environment variables are set as:

    ORACLE_OWNER= oracle

    ORACLE_HOME= /u01/app/oracle/Middleware/agent11g

     

    Enter the full pathname of the local bin directory: [/usr/local/bin]:

    The file “dbhome” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

    The file “oraenv” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

    The file “coraenv” already exists in /usr/local/bin. Overwrite it? (y/n)

    [n]:

     

    Entries will be added to the /etc/oratab file as needed by

    Database Configuration Assistant when a database is created

    Finished running generic part of root.sh script.

    Now product-specific root actions will be performed.

    Finished product-specific root actions.

    Adding entry to /etc/oratab file…

    Finished execution of /u01/app/oracle/Middleware/agent11g/root.sh ……

    [root@raclinux1 oms11g]# pwd

    /u01/app/oracle/Middleware/oms11g

    [root@raclinux1 oms11g]#

     

    After all configuration assistants complete Close to exit.

    After login in we will have.

    We can see the database we have.

    We can examine D11P as a short tour in OEM11g.

    We can look at the cluster.

    We can also check the status of the OMS and the Agent with the following commands.

    [oracle@raclinux1 bin]$ ./emctl status agent

    Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

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

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

    Agent Version : 11.1.0.1.0

    OMS Version : 11.1.0.1.0

    Protocol Version : 11.1.0.0.0

    Agent Home : /u01/app/oracle/Middleware/agent11g

    Agent binaries : /u01/app/oracle/Middleware/agent11g

    Agent Process ID : 32378

    Parent Process ID : 32358

    Agent URL : https://raclinux1.gj.com:3872/emd/main/

    Repository URL : https://raclinux1.gj.com:4900/em/upload

    Started at : 2010-08-05 12:51:29

    Started by user : oracle

    Last Reload : 2010-08-05 12:51:29

    Last successful upload : (none)

    Last attempted upload : (none)

    Total Megabytes of XML files uploaded so far : 0.00

    Number of XML files pending upload : 210

    Size of XML files pending upload(MB) : 17.77

    Available disk space on upload filesystem : 83.93%

    Last successful heartbeat to OMS : 2010-08-05 12:53:51

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

    Agent is Running and Ready

    [oracle@raclinux1 bin]$

     

    [oracle@raclinux1 bin]$ ./emctl upload agent

    Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0

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

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

    EMD upload completed successfully

    [oracle@raclinux1 bin]$

     

    [oracle@raclinux1 bin]$ ./emctl status oms

    Oracle Enterprise Manager 11g Release 1 Grid Control

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

    WebTier is Up

    Oracle Management Server is Up

    [oracle@raclinux1 bin]$

     

    Simple scripts to start and stop OEM 11g are shown below.

     

    [oracle@raclinux1 ~]$ cat oem11start.sh

    #!/bin/bash

    # Start OEM 11

    export OMS_HOME=/u01/app/oracle/Middleware/oms11g

    export AGENT_HOME=/u01/app/oracle/Middleware/agent11g

     

    # Start everything

     

    $OMS_HOME/bin/emctl start oms

     

    $AGENT_HOME/bin/emctl start agent

    [oracle@raclinux1 ~]$ cat oem11stop.sh

    #!/bin/bash

    # Stop OEM 11g

    export OMS_HOME=/u01/app/oracle/Middleware/oms11g

    export AGENT_HOME=/u01/app/oracle/Middleware/agent11g

     

    # Stop everything

     

    $OMS_HOME/bin/emctl stop oms -all

     

    $AGENT_HOME/bin/emctl stop agent

    [oracle@raclinux1 ~]$

     

     

    Summary

    We looked at the prerequisite for OEM 11g installation and configuration. We also installed the required patches for

    • Oracle Grid Infrastructure
    • Oracle RDBMS
    • Oracle Web Logic Server

We walked through the OEM 11g installation.

 

 

 

 

 

 

 

 

 

 

 

 

 


 

July 18, 2010 Posted by | oracle | Leave a comment

Installing Oracle Web logic Server 11g 10.3.2 on Linux OEL 5.5

Installing Oracle Web logic Server 11g 10.3.2 on Linux OEL 5.5

In this note we will install OWLS 11g 10.3.2 in OEL 5.5. Download Oracle Web Logic Server from here. Stage the download and change the permissions to allow execution. Start the download as shown on the screenshot.

Press Next to continue.

Specify the Middleware home directory.

Now we have an option to register with My Oracle Support (MOS) formerly Metalink. Register or uncheck the dialog box. If you omit the registration confirm that you do not want to activate the configuration manager. In this case we skip the registration.

Press Next to continue.

Select typical Install type.

Press Next to continue.

Wait for the install to complete.

Select Quick start. Press Done to continue.

Press Getting started with Web Logic Server 10.3.2.

Select create a new Web Logic domain and press Next to continue.

Select generate domain and press Next to continue.

Specify domain name and domain location. Press Next to continue.

Specify the password for weblogic Administrator user and press Next to continue

Select Development mode and choose Sun SDK. Press Next to continue.

Select Administration Server and press Next to continue.

Enable SSL port and note down the ports. Press Next to continue.

Review domain creation. Confirm by pressing Create.

Wait until Domain is created.

Press Done to exit.

Navigate to the created domain. New domain is in $MIDDLEWARE_HOME/user_prolects/domains directory. Start the Administration Server.

Use the port from Administration Server creation (7001) to login to the Administration Server.

This concludes the Oracle Web Logic Server installation and configuration.

Summary

We looked at the Oracle Web Logic Server installation and Administration server domain configuration.

July 12, 2010 Posted by | oracle | 1 Comment

Creating disk group in Oracle 11g R2

 

In this post we will look at how to add new disks, prepare the disks using Oracle ASMLib and will create a disk group using ASM Configuration Assistant (ASMCA) based on those newly added disks. ASMCA is introduced in Oracle 11gR2 to facilitate ASM new features management.

In case ASMLib is not installed, information related to ASMLIb can be found on OTN (click here). ASMLib libraries require installing the following packages corresponding to the Linux platform and kernel:

  • oracleasm-support
  • oracleasmlib
  • oracleasm

     

  1. Download and install the ASMLib packages that match the Linux platform and Linux kernel version in use.

rpm -Uvh oracleasm-support-*.rpm \

oracleasmlib-*.rpm \

oracleasm-*.rpm

  1. Configure the ASMLib as root

# oracleasm configure -i

Configuring the Oracle ASM library driver.

This will configure the on-boot properties of the Oracle ASM library

driver. The following questions will determine whether the driver is

loaded on boot and what permissions it will have. The current values

will be shown in brackets (‘[]’). Hitting without typing an

answer will keep that current value. Ctrl-C will abort.

Default user to own the driver interface []: oracle

Default group to own the driver interface []: dba

Start Oracle ASM library driver on boot (y/n) [n]: y

Scan for Oracle ASM disks on boot (y/n) [y]:

Writing Oracle ASM library driver configuration: done

#

  1. Create the disks using ‘oracleasm createdisk’ command as root. This command will make the disks available to ASMLib. We are adding DISK4, DISK5 and DISK6 as shown on the screenshot below. Perform a refresh of the ASM configuration using scandisks option. List the existing disks using the listdisks option to verify that ASMLib is aware of the marked new disks.

 

Now when the ASMLib is aware of the new disks invoke the ASM Configuration Assistant (ASMCA) logged in as the owner of the Oracle grid infrastructure. Click on the Create button.

Specify the Name of the new disk group, redundancy level and select the available disks to be part of the disk group.

Newly created group will be listed in the disk groups’ window tab.

Summary

We configured ASMLib and marked the disks for a new disk group. After AMLib become aware of the new disks we used asmca to create the new disk group.

July 6, 2010 Posted by | oracle | 3 Comments

Installation of Oracle Enterprise Linux on a VMware Virtual machine for Oracle RAC

Installation of Oracle Enterprise Linux on a VMware Virtual machine for Oracle RAC

This article complements the post for creating RAC Virtual Machines using VMware. Here we will look at installing Oracle Enterprise Linux (OEL) 5.5. OEL can be downloaded from Oracle edelivery site. After downloading OEL 5.5 64 bit version we prepare an ISO image.

We start the already configured VMware Virtual machine either specifying the ISO file or with DVD containing the ISO image in the CD/DVD drive. After connecting to the console we are at the screen specified below. As we choose to install the OEL in graphical mode we will press ENTER at the prompt.

We are prompted to test the media. We have an option to skip the media check and start with the install or to perform the media checks before the installation. If we opt for media check the installer will check the ISO image and if the image checks passes we are ensured that we can succeed in performing the installation from the media otherwise we need to prepare a new readable (non-corrupted) media. We will choose to test the media. Press OK to perform the media test.

Press TEST to start the test.

Wait for the test to complete.

We are notified by the installer for the state of the media. If the media is fine the media check succeeds and we press OK to start the installation from the media.

We are provided an option to test another media. As we have one DVD we will press CONTINUE. As the screen suggest here we can test all CD/DVD prior to the install.

The OEL screen appears and press Next to continue.

Select the language end press Next to continue.

Select the keyboard for the system and press NEXT to continue.

As suggested by the installer at the prompt press OK to initialize the new partition.

We select ‘Create a custom layout’ and press NEXT to continue. This will enable us to specify different mount points and size of each mount point. The default is a single mount point using the LVM.

Select New and enter the specifics for the / mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /boot mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /home mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /tmp mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /usr mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /var mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the / usr/local mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /opt mount point that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the swap file system that meet your requirements as show below. Press OK to continue.

Select New and enter the specifics for the /u01 mount point that meet your requirements as show below. Press OK to continue.

Now that we have created the mount points verify the configuration and press Next to continue.

Select GRUB and press Next to continue.

The installer detects the available network adapters. We are presented with a list of available adapters. Activate all adapters and select each adapter by highlighting the adapter and pressing Edit. Enter the IP address for the adapter and the respective netmask that comply with your requirements and press OK to continue. As we are installing OEL for Oracle RAC deployment we have created four network adapters in the VMware server configuration for that Virtual machine that will run Oracle RAC.

Select the second adapter. Enter the IP address for the adapter and the respective netmask that comply with you requirements and press OK to continue.

Select next adapter. Enter the IP address for the adapter and the respective netmask that comply with you requirements and press OK to continue.

Select next adapter. Enter the IP address for the adapter and the respective netmask that comply with you requirements and press OK to continue.

Specify the additional settings that are specific for you setup end press Next to continue. For Oracle RAC we need to have a hostname and a Default Gateway. Lack of a default gateway will cause a problem with the VIP later on.

Select the region and press Next to continue.

Enter the root password and press Next to continue.

Select the software and the customization options and press Next to continue.

Select all the packages and press Next to continue.

Wait for the dependency check to complete.

Press Next to begin the installation.

Wait for the completion.

Press Forward to continue.

Select Yes and press Forward to continue.

For Oracle RAC select Firewall Disabled and press next to continue.

Acknowledge by pressing Yes.

Select SELinux disabled, acknowledge at the prompt and press Forward to continue.

Press Next to continue.

Select Next to continue and press Forward to continue.

On create user specify the username and press Forward to continue.

Acknowledge the sound card detection and press Forward to continue.

Pressing Finish will complete the installation. At the prompts press OK. The system will reboot to perform the setup we configured.

Now we have installed the OEL 5.5 x64. Login with the root credentials and continue with the VMware tools installation to synchronize the guest and host operating system.

Perform synchronization between guest OS and host OS. On the web VMware Infrastructure, highlight the created VM and click the “Install VMware Tools” link and click the subsequent “Install” button. Install VMware tools package by clicking on the tools rpm in the console by clicking the VMware tools rpm.

Wait for the rpm install to complete.

Acknowledge the VMware tools installation.

As root run the vmware-config-tools.pl script.

Acept the defaults and select the screen resolution.

Run vmware-tools as root. Select Time synchronisation… and press Close.

Reboot the VM.

Summary

In this post we looked at Oracle Enterprise Linux installation. During the installation we covered configuration of network adapters and creation of custom file systems. We saw how to disable firewall and SELinux settings so that to have OEL environment for Oracle RAC. We looked at how to synchronize the guest with the host OS.

July 2, 2010 Posted by | oracle | 7 Comments