Grid Control 10.2.0.5 – Recommended Method for Installation, Faster and Easier

Recommended Install Type- ‘Enterprise Manager 10g Grid Control Install Using an Existing Database’

Silent Install Scenario -‘Installing Software-Only and Configuring Later’ 10.2.0.4+ OMS

Why should I install a separate database?

  • Because you tend to get caught (a painful migration) when a major change is required – such as the timezone changes, CPU’s, database and/or OMS patchsets, migrations to different nodes or operating systems, etc.  “If your Enterprise Manager Grid Control Release is 10.1.0.2, you cannot move your Repository (from the native 9.0.1.5 to) a 10.1.0.3 database.” This is a direct quote from the document on how to uncouple the native database installation – “How to Move a Grid Control Repository to a 10.1.0.3 Database” – Note:285087.1 
  • Separating the installation allows the database install to be at 64-bit (64-bit OS) and keep the OMS install on 32-bit on a different node (32-bit OS).
  • Allows the use of 10.2.0.3+ for the database.
  • Allows newly supported platforms.
  • Install during DST (patchset has DST fixes)
  • Can’t be used to migrate any OMS installation less than 10.2.0.4.

 

Install Enterprise Edition database 10.1.0.4+ (see Document ID 412431.1 for compatibility). I would recommend using 10.2.0.3+. See  “How to Pre-configure a 10g Database to Become the EM 10g Management Repository”-Note:285209.1

If using the GUI installation: Specify full installation type (doesn’t matter what version since you are upgrading to 10.2.0.4 or 10.2.0.5 immediately)– Using an Existing Database Option (note: if init.ora parameters are not at the recommended minimums…this install will fail).

 

Cookbook for Silent install and Configuring later

Before starting the install of the Base 10.2.0.1 or 10.2.0.2 OMS, repository has already been created, see the Metalink Note in the preceding paragraph. Unzip the installation directories and create the response files (em_using_existing_db.rsp and patchset_oms.rsp, patchset_agent.rsp) in advance using the documentation/Metalink notes as a guide.  Double check the variables in the response files because there is no feedback on its success or failure until you run the configure script. Make a copy of the response files before starting, you will need two different sets of a response when patching oms and agent.

 

./runInstaller -noconfig -silent –responseFile <exact_path>/em_using_existing_db.rsp –force

$OMS_HOME/oraInstRoot.sh (as root, if no previous oracle products installed)

$OMS_HOME/allroot.sh (as root)

$OMS_HOME/opmn/bin/opmnctl stopall

Immediately install the 10.2.0.5 patchset (release notes explicitly tell you not to start an unpatched OMS server)

./runInstaller -noconfig -silent -responseFile <exact_path>/patchset_oms.rsp -force

$OMS_HOME/root.sh (as root)

Now patch the agent (the reponse files are different)

./runInstaller -noconfig -silent -responseFile <exact_path>/patchset_agent.rsp –force

$AGENT_HOME/root.sh (as root)

export PERL5LIB=$OMS_HOME/perl/lib/5.6.1

$OMS_HOME/perl/bin/perl $OMS_HOME/sysman/install/ConfigureGC.pl <GC Base Dir>

There is a bug…(imagine that!) $OMS_HOME/oms10g/sysman/log/emca_repos_drop<serial #>.log file

Could not connect to connect string ORA-01017: Invalid username/passsword: logon denied (DBD ERROR: OCISessionBegin)

ALTER user SYS identified by "default"; (repository database)

$OMS_HOME/perl/bin/perl $OMS_HOME/sysman/install/ConfigureGC.pl <GC Base Dir> (run again it will fail again)

ALTER user SYS identified by “realpassword”; (repository database)

$OMS_HOME/perl/bin/perl $OMS_HOME/sysman/install/ConfigureGC.pl <GC Base Dir> (run again it should work this time to completion)

 

Note.763314.1How to Install Enterprise Manager Grid Control 10.2.0.5.0 Using a New Database with the Software Only Method

Note.763347.1 How to Install Enterprise Manager Grid Control 10.2.0.5.0 Using an Existing Database with the Software Only Method:

Note.793870.1How to Install Grid Control 10.2.0.5.0 on Enterprise Linux 4 Using the Existing Database (11g) Option

Note.784963.1 How to Install Grid Control 10.2.0.5.0 on Enterprise Linux 5 Using the Existing Database (11g) Option

Advertisements

11 Responses to Grid Control 10.2.0.5 – Recommended Method for Installation, Faster and Easier

  1. Manas Prakash says:

    HI,
    Currently I am having Database as 10.2.0.4 without grid control.
    Now i need to have 10.2.0.4 grid control which needs 10.2.0.1 grid control as a base version for Higher version of grid control.
    So do i need to downgrade 10.2.0.4 database to continue with the up-gradation of Grid control by below path
    10.2.0.1 database to install 10.2.0.1 grid control or
    i can directly install 10.2.0.1 grid control on top of 10.2.0.4 database and then upgrade to 10.2.0.4 grid control by using upgrade existing database or install software only using existing database.

    • aprilcsims says:

      Directly install 10.2.0.1 grid control on top of 10.2.0.4 database and then upgrade to 10.2.0.4 grid control by using upgrade existing database or install software only using existing database….That will work.

  2. Satish says:

    I’ve a newly installed Oracle RAC 10.2.0.4 version and a new database created for Grid control purpose. I want to use this database a repository when I install the Grid Control 10.2.0.5.

    Is there is any document that tells me how to use the RAC database as a repository for the Grid Control?

  3. ifti says:

    Hi There,

    We have Grid control 10.2.0.1 installed on Solaris 9, we have to move it to new server before upgrade to 10.2.0.5. Can you please tell what whould be the steps to do it.

    Also we want to create a development/test box from production grid control box with same settings, is it possible?

    Thanks in advance.

    • aprilcsims says:

      Transportable tablespaces are the recommended method for migrating GC Repositories across platforms and can even be utilized for upgrading the database version.

      Limitations and Requirements:
      1. Source and target database must use the same character set
      2. If source and target database are NOT on 10g – only Export/Import can be used for cross platform migration
      3. If Source and target database are on 10g – either of three options Cross platform transportable tablespaces migration, Data Pump or Export/Import can be used for cross platform repository migration
      4. Tablespace(s) cannot already exist.
      5. Both databases must have compatibility set to at least 10.0.
      6. Query the V$TRANSPORTABLE_PLATFORM view to see the platforms that are supported, and to determine their platform IDs and their endian format (byte ordering).
      7. Source and Destination host should have an EM agent running and configured to the instance which is to be migrated
      8. If target database has EM repository installed, it should be first dropped using RepManager before target database related steps are carried out.

      The above comes from Article-ID: Note 388090.1 Circulation: UNDER_EDIT (LIMITED) Title: Cross Platform EM Grid Control Repository/OMS Migration
      http://kr.forums.oracle.com/forums/thread.jspa?threadID=517164&tstart=-6

      Also check out…the following article. Either way it is a lot of work to preserve your current database repository data.
      Subject: How To Move Grid Control Oms & Repository To Another Server
      Doc ID: 853293.1 Type: HOWTO
      Modified Date: 03-JUL-2009 Status: MODERATED

      About your second question…..same settings? You can’t make the development environment exactly like production, it would have to be a completely separate install.

  4. ifti says:

    Hi aprilcsims,

    Thanks for your input. Before migration and subsequent upgrade the production grid control, I want to test the migration and upgrade in a test environment. Can you please tell me is this possible.

    Thanks once again.

    Ifti

    • aprilcsims says:

      Sure, I don’t see any reason why you can’t do this in a test environment. Just be aware that production is a separate install.

  5. kemsaigon says:

    Hi,
    I’ve already have 10.2.0.4 grid control. Can you tell me the steps to upgrade the whole grid control to 10.2.0.5. Many thanks,
    kemsaigon

  6. Pingback: 2010 in review « Oracle High Availability

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s