Tuesday, March 11, 2014


Upgrade OEM 11g to 12C - Two System Approach


Pre-requisite before you start Upgrade –

Once the pre-requisite patches (PSU and 12c pre-upgrade patch) are done, login to OEM console.
Go to 11g OMS deployment page and Select UPGRADE TYPE.
Also one needs to restore the backup of the OMS Repository i.e. 11g OMS database on different host, which will be used for 12c upgrade.
Make sure database name stays same otherwise the upgrade will fail

ENTER HOST AND PORTS, WHERE YOU ARE GOING TO INSTALL NEW 12c OMS


ALSO PROVIDE THE TIME OF THE BACKUP, THE ONE YOU USED TO RESTORE THE DATABASE.




On the new host start the 12c installer

[oracle@Host11G em12c]$ ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 400 MB.   Actual 3611 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 65535 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 65536    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-07-12_06-24-41AM. Please wait ...[oracle@ushofsvpracb







PROVIDE MIDDLEWARE HOME LOCATION WHERE YOUR WEBLOGIC 10.3.5 AND ABOVE SERVER IS RUNNING. 
Also enter your Agent Base directory and Host name.


If you hit the above error, one needs to modify following parameters from Repository Database.

SQL> conn / as sysdba
Connected.
SQL> alter system set job_queue_processes=0;
System altered.

SQL> exec dbms_scheduler.disable('SYS.GATHER_STATS_JOB');
BEGIN dbms_scheduler.disable('SYS.GATHER_STATS_JOB'); END;

*
ERROR at line 1:
ORA-27476: "SYS.GATHER_STATS_JOB" does not exist
ORA-06512: at "SYS.DBMS_ISCHED", line 4407
ORA-06512: at "SYS.DBMS_SCHEDULER", line 2737
ORA-06512: at line 1

One has to run following pre-req checks and modify the parameters on the restored oms repository database.

SQL> conn / as sysdba
Connected.
SQL> alter system set job_queue_processes=0;
System altered.

SQL> show parameter nls_length

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
nls_length_semantics                 string      BYTE
SQL> grant execute on dbms_random to dbsnmp;
Grant succeeded.

SQL> grant execute on dbms_random to sysman;
Grant succeeded.

SQL> alter user oracle_ocm account unlock;
User altered.

SQL> sho parameter process
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes                      integer     1
cell_offload_processing              boolean     TRUE
db_writer_processes                  integer     2
gcs_server_processes                 integer     0
global_txn_processes                 integer     1
job_queue_processes                  integer     0
log_archive_max_processes            integer     4
processes                            integer     500
processor_group_name                 string
SQL> show parameter stream
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
streams_pool_size                    big integer 0

SQL> alter system set streams_pool_size=300m;
System altered.

 SQL> alter database add logfile group 4 '+DATA_PSFT_HR'  size 300M;
 Database altered.

SQL> alter database add logfile group 5  '+DATA_PSFT_HR'  size 300M;
 Database altered.

SQL>  alter database add logfile group 6 '+DATA_PSFT_HR'  size 300M;
 Database altered.

SQL> alter database drop logfile group 1;
 Database altered.

SQL> alter database drop logfile group 2;
 Database altered.

SQL> alter database drop logfile group 3;
 Database altered.
Now select the plugins required for the 12c OMS. 


Enter the WebLogic server credentials.

Now one needs to enter old OMS Repository connection string. What happens is that the link to old OMS Repository is created and is being used to sync data from old OMS to new OMS.







This information is also available at:

                /u01/app/oracle/Middleware/oms/install/setupinfo.txt

See below for information pertaining to your Enterprise Manager installation:

Use the following URL to access:

                1. Enterprise Manager Cloud Control URL: https://Host11G.searshc.com:7799/em
                2. Admin Server URL: https://Host11G.searshc.com:7101/console

The following details need to be provided during the additional OMS install:

                1. Admin Server Hostname: Host11G.searshc.com
                2. Admin Server Port: 7101

 NOTE:
 An encryption key has been generated to encrypt sensitive data in the Management Repository. If this key is lost, all encrypted data in the Repository becomes unusable. Please run following command to backup the Management Service configuration including the emkey and keep the backup on another system:
 emctl exportconfig oms -dir <backup location>

Since the OMS also needs to backup one needs to export the OMS configuration as follows and keep it some where safe. 
Note - This is one of the component needed as part of OMS backup strategy, others are OMS_HOME, GC_INST Home and Fusion MIDDLEWARE_HOME

[oracle@Host11G OEM12c]$ cd ../Middleware/oms/bin/
[oracle@Host11G bin]$ ./emctl exportconfig oms -dir /u01/app/oracle/OEM12c/emctl_confg_exp_DONOTDELETE
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
ExportConfig started...
<Jul 15, 2013 11:18:33 AM CDT> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
Machine is Admin Server host. Performing Admin Server backup...
Exporting emoms properties...
Exporting secure properties...

Export has determined that the OMS is not fronted
by an SLB. The local hostname was NOT exported.
The exported data can be imported on any host but
resecure of all agents will be required. Please
see the EM Advanced Configuration Guide for more
details.

Exporting configuration for pluggable modules...
Preparing archive file...
Backup has been written to file:/01/app/oracle/OEM12c/emctl_confg_exp_DONOTDELETE/opf_ADMIN_20130715_111837.bka


The export file contains sensitive data.
Please ensure that it is kept secure.

ExportConfig completed successfully!








No comments:

Post a Comment