Part 32 of series - Integrate Goldengate Manager Process with 11gr2 Grid Infrastructure, use GI to start and stop Mgr Process and so extract/replict

The rulers of the all the world are unhappy; one who chants the Name of the Lord becomes happy. Acquiring hundreds of thousands and millions, your desires shall not be contained. Chanting the Name of the Lord, you shall find release. By the countless pleasures of Maya, your thirst shall not be quenched. Chanting the Name of the Lord, you shall
be satisfied. Upon that path where you must go all alone, there, only the Lord’s Name shall go with you to sustain you.


Index of all the posts of Gurpartap Singh's Blog

Here are the steps I used to add Oracle Goldengate Manager process to Grid Infrastructure. After adding this only Grid Infrastructure should be used to stop/start/relocate Oracle Goldengate Manger Process. This will start/stop manger process and manager process in turn will start all the extracts/replicats using parameter AUTOSTART in manager process parameter file. Like add the following file in the end of the file as:

AUTOSTART extract *truth

This will make all the extracts ending with truth to start once manager process starts. You can configure similar thing for all the porcesses you have for extracts/replicats.


Step 1 is to add a new vip. Here are the steps:

Adding a vip.


/u02/app/11.2.0.1/grid/bin/appvipcfg create -network=1 \
-ip=10.10.2.199 \
-vipname=mvggatevip \
-user=root



with:
• GRID_HOME as the oracle home in which Oracle 11g Release 2 Grid infrastructure
components have been installed (e.g. /u02/app/11.2.0.1/grid).
• -network refers to the network number that you want to use. With Oracle Clusterware
11.2.0.1 you can find the network number using the command:
crsctl stat res -p grep -ie .network -ie subnet grep -ie name -ie subnet

Sample output is:
[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/crsctl stat res -p grep -ie .network -ie subnet grep -ie name -ie subnet
NAME=ora.net1.network
USR_ORA_SUBNET=10.10.2.0
[root@rac1 ~]#

net1 in NAME=ora.net1.network indicates this is network 1, and the second line
indicates the subnet on which the VIP will be created.

10.10.2.199 - Is a ip on the above mentioned subnet and which router can support but is not allocated to any other machine and is not pingable as of now. Grid infrastrucure will bring it up and then it will become pingable.

• mvggatevip is the name of the application VIP that you will create.
Oracle recommends the use of the appvipcfg utility to define applications VIPs. The VIP is
created with a set of pre-defined settings and dependencies. Please refer to the Oracle
Clusterware documentation for further details:
http://download.oracle.com/docs/cd/E11882_01/rac.112/e10717/crschp.htm#BGBJHJHC
Oracle White Paper—Oracle GoldenGate high availability with Oracle Clusterware


Step 2:

As root, allow the Oracle Grid infrastructure software owner (e.g. oracle) to run the script
to start the VIP.

/u02/app/11.2.0.1/grid/bin/crsctl setperm resource mvggatevip -u user:oracle:r-x


Step 3:

Then, as oracle, start the VIP:

/u02/app/11.2.0.1/grid/bin/crsctl start resource mvggatevip


To validate whether the VIP is running and on which node it is running, execute:

GRID_HOME/bin/crsctl status resource mvggatevip

For example:
[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/crsctl status resource mvggatevip
NAME=mvggatevip
TYPE=app.appvip.type
TARGET=ONLINE
STATE=ONLINE on rac2

[root@rac1 ~]#

At this point you can also connect to another server in the subnet and ping the VIP's IP address.

You should get a reply from this IP address.

oracle : rac1.rac.meditate.com : @crs : /home/oracle
$ ping -c5 10.10.2.199
PING 10.10.2.199 (10.10.2.199) 56(84) bytes of data.
64 bytes from 10.10.2.199: icmp_seq=1 ttl=64 time=0.165 ms
64 bytes from 10.10.2.199: icmp_seq=2 ttl=64 time=0.168 ms
64 bytes from 10.10.2.199: icmp_seq=3 ttl=64 time=0.172 ms
64 bytes from 10.10.2.199: icmp_seq=4 ttl=64 time=0.172 ms
64 bytes from 10.10.2.199: icmp_seq=5 ttl=64 time=0.188 ms

--- 10.10.2.199 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 0.165/0.173/0.188/0.008 ms

oracle : rac1.rac.meditate.com : @crs : /home/oracle
$



Step 4:

We will use the following script to tell Grid Infrastructure to start and stop manager process I am using ACFS. These steps can also be used for NFS mount points.
Place this script at the shared location where you have installed the goldengate binaries.

I am placing at the following location:

oracle : rac1.rac.meditate.com : @crs : /home/oracle
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
84G 35G 45G 44% /
/dev/sda1 99M 16M 78M 17% /boot
tmpfs 1.6G 429M 1.2G 28% /dev/shm
/dev/asm/shared_vol1-106
3.0G 424M 2.6G 14% /u01/app/oracle/acfsmounts/data1_shared_vol1

oracle : rac1.rac.meditate.com : @crs : /home/oracle
$ cd /u01/app/oracle/acfsmounts/data1_shared_vol1

oracle : rac1.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1
$ cd script

oracle : rac1.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1/script
$ lst
total 12
drwxrwx--- 7 root oinstall 4096 Feb 10 22:32 ..
-rwxr-xr-x 1 oracle oinstall 3278 Feb 12 15:00 11gr2_gg_action.scr
drwxr-xr-x 2 oracle oinstall 4096 Feb 12 15:06 .

oracle : rac1.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1/script
$




oracle : rac1.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1/script
$ cat 11gr2_gg_action.scr
#!/bin/sh
##GGS_HOME=
export GGS_HOME=/u01/app/oracle/acfsmounts/data1_shared_vol1/goldengate
##DBFS_MOUNT_POINT=
##DBFS_FILE_SYSTEM=
##specify delay after start before checking for successful start
start_delay_secs=5
##Include the GoldenGate home in the library path to start GGSCI
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${GGS_HOME}
##set the oracle home to the database to ensure GoldenGate will get the
##right environment settings to be able to connect to the database
export ORACLE_HOME=/u01/app/oracle/product/11.2.0.1/dbhome_1
##check_process validates that a manager process is running at the PID
##that GoldenGate specifies.
check_process () {
if ( [ -f "${GGS_HOME}/dirpcs/MGR.pcm" ] )
then
pid=`cut -f8 "${GGS_HOME}/dirpcs/MGR.pcm"`
if [ ${pid} = `ps -e grep ${pid} grep mgr cut -d " " -f2` ]
then
##manager process is running on the PID . exit success
exit 0
else
if [ ${pid} = `ps -e grep ${pid} grep mgr cut -d " " -f1` ]
then
##manager process is running on the PID . exit success
exit 0
else
##manager process is not running on the PID
exit 1
fi
fi
else
##manager is not running because there is no PID file
exit 1
fi
}
##call_ggsci is a generic routine that executes a ggsci command
call_ggsci () {
ggsci_command=$1
ggsci_output=`${GGS_HOME}/ggsci << start_dependencies="'hard(mvggatevip,ora.asm)" start_dependencies="'hard(mvggatevip)" action_script="/u01/app/oracle/acfsmounts/data1_shared_vol1/script/11gr2_gg_action.scr," check_interval="30," start_dependencies="'hard(mvggatevip,ora.asm)" stop_dependencies="'hard(mvggatevip)'">
(In my case I am using oracle user to do goldengate stuff so its not required)



Step 6:

[root@rac2 ~]# /u02/app/11.2.0.1/grid/bin/crsctl start resource ggateapp -f
CRS-2673: Attempting to stop 'mvggatevip' on 'rac2'
CRS-2677: Stop of 'mvggatevip' on 'rac2' succeeded
CRS-2672: Attempting to start 'mvggatevip' on 'rac3'
CRS-2676: Start of 'mvggatevip' on 'rac3' succeeded
CRS-2672: Attempting to start 'ggateapp' on 'rac3'
CRS-2674: Start of 'ggateapp' on 'rac3' failed
CRS-2679: Attempting to clean 'ggateapp' on 'rac3'
CRS-2681: Clean of 'ggateapp' on 'rac3' succeeded
CRS-2673: Attempting to stop 'mvggatevip' on 'rac3'
CRS-2677: Stop of 'mvggatevip' on 'rac3' succeeded
CRS-2672: Attempting to start 'mvggatevip' on 'rac2'
CRS-2676: Start of 'mvggatevip' on 'rac2' succeeded
CRS-2563: Attempt to start resource 'ggateapp' on 'rac3' has failed. Will re-retry on 'rac2' now.
CRS-2672: Attempting to start 'ggateapp' on 'rac2'
CRS-2676: Start of 'ggateapp' on 'rac2' succeeded
[root@rac2 ~]#



oracle : rac2.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1/script
$ crs_stat -t -v
Name Type R/RA F/FT Target State Host
----------------------------------------------------------------------
ggateapp clus...esource 0/1 0/0 ONLINE ONLINE rac2
mvggatevip app....ip.type 0/0 0/0 ONLINE ONLINE rac2
ora.DATA1.dg ora....up.type 0/5 0/ ONLINE ONLINE rac1
ora....ER.lsnr ora....er.type 0/5 0/ ONLINE ONLINE rac1
ora....N1.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE rac1
ora.OCR1.dg ora....up.type 0/5 0/ ONLINE ONLINE rac1
ora.RECV1.dg ora....up.type 0/5 0/ ONLINE ONLINE rac1
ora.asm ora.asm.type 0/5 0/ ONLINE ONLINE rac1
ora.eons ora.eons.type 0/3 0/ ONLINE ONLINE rac1
ora.gsd ora.gsd.type 0/5 0/ ONLINE ONLINE rac1
ora....network ora....rk.type 0/5 0/ ONLINE ONLINE rac1
ora.ons ora.ons.type 0/3 0/ ONLINE ONLINE rac1
ora.prabgun.db ora....se.type 0/2 0/2 ONLINE OFFLINE
ora....sv3.svc ora....ce.type 0/0 0/0 ONLINE OFFLINE
ora....SM1.asm application 0/5 0/0 ONLINE ONLINE rac1
ora....C1.lsnr application 0/5 0/0 ONLINE ONLINE rac1
ora.rac1.gsd application 0/5 0/0 ONLINE ONLINE rac1
ora.rac1.ons application 0/3 0/0 ONLINE ONLINE rac1
ora.rac1.vip ora....t1.type 0/0 0/0 ONLINE ONLINE rac1
ora....SM2.asm application 0/5 0/0 ONLINE ONLINE rac2
ora....C2.lsnr application 0/5 0/0 ONLINE ONLINE rac2
ora.rac2.gsd application 0/5 0/0 ONLINE ONLINE rac2
ora.rac2.ons application 0/3 0/0 ONLINE ONLINE rac2
ora.rac2.vip ora....t1.type 0/0 0/0 ONLINE ONLINE rac2
ora....SM3.asm application 0/5 0/0 ONLINE ONLINE rac3
ora....C3.lsnr application 0/5 0/0 ONLINE ONLINE rac3
ora.rac3.gsd application 0/5 0/0 ONLINE ONLINE rac3
ora.rac3.ons application 0/3 0/0 ONLINE ONLINE rac3
ora.rac3.vip ora....t1.type 0/0 0/0 ONLINE ONLINE rac3
ora....ry.acfs ora....fs.type 0/5 0/ ONLINE ONLINE rac1
ora.scan1.vip ora....ip.type 0/0 0/0 ONLINE ONLINE rac1
ora.simar.db ora....se.type 0/2 0/1 ONLINE ONLINE rac1
ora....sv1.svc ora....ce.type 0/0 0/0 ONLINE ONLINE rac1

oracle : rac2.rac.meditate.com : @crs : /u01/app/oracle/acfsmounts/data1_shared_vol1/script
$


[root@rac2 ~]# /u02/app/11.2.0.1/grid/bin/crsctl status resource ggateapp
NAME=ggateapp
TYPE=cluster_resource
TARGET=ONLINE
STATE=ONLINE on rac2

[root@rac2 ~]#


Logs of goldengate:

2011-02-12 15:12:07 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): start manager.
2011-02-12 15:12:12 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop er *.
2011-02-12 15:12:12 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop er *.
2011-02-12 15:12:12 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop manager.
2011-02-12 15:12:16 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): start manager.
2011-02-12 15:12:21 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop er *.
2011-02-12 15:12:21 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop er *.
2011-02-12 15:12:21 GGS INFO 399 Oracle GoldenGate Command Interpreter for Oracle: GGSCI command (root): stop manager.
2011-02-12 15:12:27 GGS INFO 330 Oracle GoldenGate Manager for Oracle, mgr.prm: Manager started (port 7909).
2011-02-12 15:12:47 GGS INFO 330 Oracle GoldenGate Manager for Oracle, mgr.prm: Manager started (port 7909).


Step 7:

If one ASM instance goes down it should not effect our manager process and for that use the following entries of ASM on every node of RAC:

ASM entry on 3 nodes should look like:

Node 1:

RAC1ASM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = +ASM1)
)
)


Node 2:

RAC1ASM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = +ASM2)
)
)


Node 3:

RAC1ASM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = +ASM3)
)
)



You shall not be saved by hundreds of thousands and millions of helping hands. Chanting the Naam, you shall be lifted up and carried across. Where countless misfortunes threaten to destroy you, the Name of the Lord shall rescue you in an instant. Through countless incarnations, people are born and die. Chanting the Name of the Lord, you shall come to rest in peace. The ego is polluted by a filth which can never be washed off. The Name of the Lord erases millions of sins.

Part 31 of series - Move/Migrate/Relocate OCR and Vote disk in 11gr2 Grid infrastructure from one ASM diskgroup to another ASM diskgroup

Remembering God, one's works are accomplished. Remembering God, one never grieves. Remembering God, one speaks the Glorious Praises of the Lord. Remembering God, one is absorbed into the state of intuitive ease. Remembering God, one attains the unchanging position. Remembering God, the heart-lotus blossoms forth. Remembering God, the unstruck melody vibrates. The peace of the meditative remembrance of God has no end or limitation.
They alone remember Him, upon whom God bestows His Grace.




Index of all the posts of Gurpartap Singh's Blog


I had a bad experience while downgrading grid infrastructure from 11.2.0.2 to 11.2.0.1
I had a 7 node cluster with multiple databases and only 2 disk groups. One data and one recv.

Data diskgroup had OCR and vote disk. When executed deinstall on last node with last node option it deletes OCR and Vote disk and past of it is to clean up the header of the disk having OCR and VOTE disk. Since headers of the disk were cleaned as the past of deinstall script with last node option, I was not able to mount DATA diskgrup and so lost all the data and had to restore all the databases. Then came to know that the best practice is to have OCR and Vote disk
in different diskgroup. Here are the steps to move or migrate OCR and vote disk to new diskgroup in 11gr2 grid infrastructure.

All the following steps can be done while all databases are online. I created a new diskgroup +OCR1 using asmca. You can create this from comandline also. It can be 1GB or 2GB lun only. This diskggroup is mounted on all the 3 nodes.



Document I used is following:

http://download.oracle.com/docs/cd/E18283_01/rac.112/e16794.pdf
Page 61,65:


Here we go:

oracle : rac1.rac.meditate.com : @crs : /u02/app/11.2.0.1/grid
$ su -
Password:
[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 3
Total space (kbytes) : 262120
Used space (kbytes) : 3200
Available space (kbytes) : 258920
ID : 174947145
Device/File Name : +DATA1
Device/File integrity check succeeded

Device/File not configured

Device/File not configured

Device/File not configured

Device/File not configured

Cluster registry integrity check succeeded

Logical corruption check succeeded

[root@rac1 ~]#






[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/ocrconfig -add +OCR1

Logs:

2011-02-07 22:19:12.726
[crsd(7242)]CRS-1007:The OCR/OCR mirror location was replaced by +OCR1.





[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 3
Total space (kbytes) : 262120
Used space (kbytes) : 3200
Available space (kbytes) : 258920
ID : 174947145
Device/File Name : +DATA1
Device/File integrity check succeeded
Device/File Name : +OCR1
Device/File integrity check succeeded

Device/File not configured

Device/File not configured

Device/File not configured

Cluster registry integrity check succeeded

Logical corruption check succeeded

[root@rac1 ~]#





[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/ocrconfig -delete +DATA1


2011-02-07 22:21:17.963
[crsd(7242)]CRS-1010:The OCR mirror location +DATA1 was removed.



[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/ocrcheck
Status of Oracle Cluster Registry is as follows :
Version : 3
Total space (kbytes) : 262120
Used space (kbytes) : 3200
Available space (kbytes) : 258920
ID : 174947145
Device/File Name : +OCR1
Device/File integrity check succeeded

Device/File not configured

Device/File not configured

Device/File not configured

Device/File not configured

Cluster registry integrity check succeeded

Logical corruption check succeeded

[root@rac1 ~]#



Logs on node 2:

2011-02-07 22:19:15.521
[crsd(6789)]CRS-1007:The OCR/OCR mirror location was replaced by +OCR1.
2011-02-07 22:21:18.611
[crsd(6789)]CRS-1010:The OCR mirror location +DATA1 was removed.



Logs on node 3:

2011-02-07 22:19:16.395
[crsd(6914)]CRS-1007:The OCR/OCR mirror location was replaced by +OCR1.
2011-02-07 22:20:09.459
[ctssd(6539)]CRS-2408:The clock on host rac3 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
2011-02-07 22:20:25.467
[ctssd(6539)]CRS-2408:The clock on host rac3 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
2011-02-07 22:21:18.967
[crsd(6914)]CRS-1010:The OCR mirror location +DATA1 was removed.

--------------------------------------------------
page 65:

If there were multiple OCR locations then following command cold be used:
ocrconfig -replace current_OCR_location -replacement new_OCR_location

=============================================================================

http://download.oracle.com/docs/cd/E18283_01/rac.112/e16794.pdf
Page 279:

Moving vote disk:

[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/crsctl query css votedisk
## STATE File Universal Id File Name Disk group
-- ----- ----------------- --------- ---------
1. ONLINE 44d575b60a4b4fb5bf3cf8b51d001778 (/dev/sdc) [DATA1]
Located 1 voting disk(s).
[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/crsctl replace votedisk +OCR1
Successful addition of voting disk 28657f1692a04fd3bf80dd7451fc1817.
Successful deletion of voting disk 44d575b60a4b4fb5bf3cf8b51d001778.
Successfully replaced voting disk group with +OCR1.
CRS-4266: Voting file(s) successfully replaced

In cluster alert log:

rac1:

2011-02-07 22:39:47.924
[cssd(6548)]CRS-1605:CSSD voting file is online: /dev/sdl; details in /u02/app/11.2.0.1/grid/log/rac1/cssd/ocssd.log.
2011-02-07 22:39:49.104
[cssd(6548)]CRS-1626:A Configuration change request completed successfully
2011-02-07 22:39:49.608
[cssd(6548)]CRS-1601:CSSD Reconfiguration complete. Active nodes are rac1 rac2 rac3 .


rac2:

2011-02-07 22:39:12.120
[ctssd(6300)]CRS-2408:The clock on host rac2 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
2011-02-07 22:39:48.614
[cssd(6166)]CRS-1605:CSSD voting file is online: /dev/sdl; details in /u02/app/11.2.0.1/grid/log/rac2/cssd/ocssd.log.
2011-02-07 22:39:49.186
[cssd(6166)]CRS-1626:A Configuration change request completed successfully
2011-02-07 22:39:49.608
[cssd(6166)]CRS-1601:CSSD Reconfiguration complete. Active nodes are rac1 rac2 rac3 .
2011-02-07 22:43:04.315
[ctssd(6300)]CRS-2408:The clock on host rac2 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.
2011-02-07 22:43:20.321
[ctssd(6300)]CRS-2408:The clock on host rac2 has been updated by the Cluster Time Synchronization Service to be synchronous with the mean cluster time.



rac3:

2011-02-07 22:39:48.621
[cssd(6444)]CRS-1605:CSSD voting file is online: /dev/sdl; details in /u02/app/11.2.0.1/grid/log/rac3/cssd/ocssd.log.
2011-02-07 22:39:49.100
[cssd(6444)]CRS-1626:A Configuration change request completed successfully
2011-02-07 22:39:49.604
[cssd(6444)]CRS-1601:CSSD Reconfiguration complete. Active nodes are rac1 rac2 rac3 .





[root@rac1 ~]# /u02/app/11.2.0.1/grid/bin/crsctl query css votedisk
## STATE File Universal Id File Name Disk group
-- ----- ----------------- --------- ---------
1. ONLINE 28657f1692a04fd3bf80dd7451fc1817 (/dev/sdl) [OCR1]
Located 1 voting disk(s).
[root@rac1 ~]#



------------------------------------

crsctl add css votedisk

------------------------------------

File Universal Id (FUID) obtained from (crsctl query css votedisk)
crsctl delete css votedisk 28657f1692a04fd3bf80dd7451fc1817





Remembering the Lord, His devotees are famous and radiant. Remembering the Lord, the Vedas were composed. Remembering the Lord, we become Siddhas, celibates and givers. Remembering the Lord, the lowly become known in all four directions. For the remembrance of the Lord, the whole world was established. Remember, remember in meditation the Lord, the Creator, the Cause of causes. For the remembrance of the Lord, He created the whole creation. In the remembrance of the Lord, He Himself is Formless. By His Grace, He Himself bestows understanding.

Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS

Those who remember God are wealthy. Those who remember God are honorable. Those who remember God are approved. Those who remember God are the most distinguished persons. Those who remember God are not lacking. Those who remember God are the rulers of all. Those who remember God dwell in peace. Those who remember God are immortal and eternal. They alone hold to the remembrance of Him, unto whom He Himself shows His Mercy.




Index of all the posts of Gurpartap Singh's Blog


---------------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html


---------------------------------------------------------------


Now we will upgrade the Additional OMS.

Primary OMS is up and running on sever grid01. Keep it up and running and start extending (upgrading the additional oms server)

oracle : grid02 : @agent10g : /home/oracle/software/GridContol/11.1
$ ./runInstaller
On first screen uncheck "I wish to receive security updates via MY Oracle Support" and click next.
On next pop up click Yes to "Do you wish to remain uninformed of critical security issues ….."
On next screen make sure "Skip Software Updates is clicked and click next.
On next screen make sure "Upgrade to Enterprise Manager 11g" and click next.
On next screen make sure the current agent/oms base and version is correct and is checked/selected and click next.
There are prerequisites on next screen and make sure all succeed and click next.

At next screen if it doesn’t accept the sys password and error at invalid username/password, just stop instance 2 on server grid02 and make sure all the services are running and try again and it will move to next screen.
And if the connect descriptor is incorrect, you have to change the $ORACLE_HOME/sysman/config/emoms.properties

oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION\=(ADDRESS_LIST\=(FAILOVER\=ON)(ADDRESS\=(PROTOCOL\=TCP)(HOST\=grid01)(PORT\=41521)))(CONNECT_DATA\=(SERVICE_NAME\=GRIDsv1)(SERVER\=DEDICATED)))

And retry connectivity.

On next screen "Change the OMS instance base location to end in "11.1" instead of "gc_inst"
and make sure the Middleware and the OMS base location is correct and click next. Here installer checks for space and
will error out if we don’t have enough space.

On the next screen Admin Server Host grid01 (where existing upgraded OMS is hosted)
Admin Server Port : 7102 (Check the range from the primay OMS install snapshot that we took)
Enter weblogic username and password that you used in the primay oms upgrade.

On next keep the ports default and click next.
On next screen click "Install" and the install will starts.

At the end of the installation you will be prompted to run a script for the root.
If prompted, accept all defaults and it should finish without errors and after that click ok
and some Configuration Assistants will run. The process will take at least 2-3 hours so be prepared to wait:

(The Repository Upgrade portion takes the longest)
After keeping the snapshot of last window that has the url to connect click close.



Update the oratab with the new agent and OMS home:

#oms10g:/ora/fs0000/app/oracle/product/10.2/oms10g:N
#agent10g:/ora/fs0000/app/oracle/product/10.2/agent10g:N
agent11g:/ora/fs0000/app/oracle/product/Middleware/oms11g:N
agent11g:/ora/fs0000/app/oracle/product/Middleware/agent11g:N

Now apply PSU2 patch to OMS and agent.

Last step:
Submit the Refresh Weblogic job
Follow document How to Enable job "Refresh WebLogic Domain" ? [ID 1088537.1]


Thats it !!!!!


-------------------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html


-------------------------------------------------------------------

Remembering God, one's works are accomplished. Remembering God, one never grieves.
Remembering God, one speaks the Glorious Praises of the Lord. Remembering God, one is absorbed into the state of intuitive ease. Remembering God, one attains the unchanging position. Remembering God, the heart-lotus blossoms forth. Remembering God, the unstruck melody vibrates. The peace of the meditative remembrance of God has no end or limitation.
They alone remember Him, upon whom God bestows His Grace.

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS

The remembrance of God is the highest and most exalted of all. In the remembrance of God, many are saved. In the remembrance of God, thirst is quenched. In the remembrance of God, all things are known. In the remembrance of God, there is no fear of death. In the remembrance of God, hopes are fulfilled. In the remembrance of God, the filth of the mind is removed. The Ambrosial Naam, the Name of the Lord, is absorbed into the heart. God abides upon the tongues of His Saints.




Index of all the posts of Gurpartap Singh's Blog


----------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html


---------------------------------------------------------

INSTALLING and Upgrading GRID CONTROL

Grid Control 11.1.0.1.0 Install and Upgrade (from 10.2.0.4+)

I have already downloaded and extracted Grid Control 11g for Sun64 and placed it in the software directory at “/home/oracle/software/GridContol/11.1” After unzipping the downloaded files it will be approximately 4.7 GB

Prerequisites :
Your existing OMS must be 10.2.0.4 or higher. If not, you cannot upgrade to 11g until it’s at least 10.2.0.4. The first step is to stop all OMS servers and upgrade 1 OMS first as this will also upgrade the repository.
You must have at LEAST 8.4 GB free to install 11g OMS.
Verify the OS package prerequisites at: http://download.oracle.com/docs/cd/E11857_01/install.111/e15838/appdx_package_reqs.htm#BABIJAJB
For Solaris 10 we only needed: SUNWbtool

Database Init parameters:
cluster_database
(Only for Oracle RAC Database) TRUE

Compatible 10.2.0.1.0 or higher
max_commit_propogation_delay
(Only for Oracle RAC Database) 0

remote_login_passwordfile SHARED or EXCLUSIVE
statistics_level TYPICAL
timed_statistics TRUE
undo_management AUTO
workarea_size_policy AUTO
db_block_size 8192 or greater
job_queue_processes (For Installation) 10 or greater
(For Upgrade) If you are upgrading Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, then ensure that you set the value to 0 before upgrading. And after upgrading, reset it to the original value that existed before upgrading the product.
log_buffer 10485760 or greater
open_cursors 300 or greater
Processes 500 or greater
session_cached_cursors 200 or greater


Verify the database has the Partitioning option enabled. If this is an upgrade, it would already be there.

SQL> select value from v$option where parameter = 'Partitioning';

VALUE
----------------------------------------------------------------
TRUE

Ensure all SYSMAN objects are valid

SQL> select object_name, object_type from all_objects where owner='SYSMAN' and status <> 'VALID';

no rows selected

If there are invalid objects, recompile them.

@admin_recompile_invalid.sql SYSMAN

Verify all SYS objects are valid:

SQL> select object_name, object_type from all_objects where status<>'VALID' and object_name like 'DBMS%';

no rows selected

If there are invalid objects, also compile them.

Get the value of the current job queue processes in all the instances and make a note of it as we will be changing it temporarily:

SQL> select a.instance_name as sid, b.value as jobqueue from gv$instance a, gv$parameter b where a.inst_id = b.inst_id and b.name='job_queue_processes';

SID
----------------
JOBQUEUE
--------------------------------------------------------------------------------
REPR2
20

REPR1
20



Here starts the downtime.

First, verify the repository database is not in QUIESCE mode:

SQL> select active_state from v$instance;

ACTIVE_ST
---------
NORMAL

Set job_queue_processes to 0 during the upgrade and remove the em jobs (we’ll add them back later).
Connect to the repository as SYSMAN.

SQL> conn sysman
Enter password:
Connected.
SQL> execute emd_maintenance.remove_em_dbms_jobs;

PL/SQL procedure successfully completed.

SQL> alter system set job_queue_processes=0;

System altered.

SQL> commit;

Commit complete.

SQL>

Ensure there are no active jobs:

SQL> select l.id2 job, l.sid, to_char(last_date, 'DD-MON-YYYY:HH24.MI.SS') last_date, to_char(this_date, 'DD-MON-YYYY:HH24.MI.SS') this_date, l.inst_id instance from sys.job$ j, gv$lock l where l.type = 'JQ' and j.job (+) = l.id2 order by 5, 4;

no rows selected

Disable dbms scheduler jobs:
SQL> execute dbms_scheduler.set_scheduler_attribute('SCHEDULER_DISABLED','TRUE');

PL/SQL procedure successfully completed.

Verify (wait if necessary) until there are no more running jobs

SQL> select count(*) from dba_scheduler_running_jobs where SLAVE_PROCESS_ID IS NOT NULL;

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


Log in as SYS and stop the jobs

SQL> conn / as sysdba
Connected.
SQL> execute dbms_scheduler.disable('GATHER_STATS_JOB',TRUE);

PL/SQL procedure successfully completed.

SQL> execute dbms_scheduler.stop_job('GATHER_STATS_JOB',TRUE);
BEGIN dbms_scheduler.stop_job('GATHER_STATS_JOB',TRUE); END;

*
ERROR at line 1:
ORA-27366: job "SYS.GATHER_STATS_JOB" is not running
ORA-06512: at "SYS.DBMS_ISCHED", line 164
ORA-06512: at "SYS.DBMS_SCHEDULER", line 483
ORA-06512: at line 1

Ensure SYSMAN and DBSNMP users have EXECUTE on DBMS_RANDOM.

SQL> GRANT EXECUTE ON DBMS_RANDOM TO SYSMAN;

SQL> GRANT EXECUTE ON DBMS_RANDOM TO DBSNMP;

Now stop all OMS servers even if you are upgrading just one.

oracle : grid01 : @oms10g : /home/oracle/software
$ $ORACLE_HOME/opmn/bin/opmnctl stopall
opmnctl: stopping opmn and all managed processes...


oracle : grid01 : @oms10g : /home/oracle/software
$ emctl stop oms
Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle Management Server is Down.
OPMN may not be up.


Now stop on othernode and if you have more oms servers, stop them too.

oracle : grid02 : @oms10g : /home/oracle/software
$ $ORACLE_HOME/opmn/bin/opmnctl stopall
opmnctl: stopping opmn and all managed processes...

oracle : grid02 : @oms10g : /home/oracle/software
$ emctl stop oms
Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle Management Server is Down.
OPMN may not be up.


Create a rollback point for OMS repository + binaries

Actually grid control has so many bugs and I want to have my own backout plan. I am creating a flashback point in the repository and back up the OMS binaries and agent binaries as these three components will be upgraded.

Tar up the binaries where there is space, you will need at least 5-6 GB.

oracle : grid01 : @oms10g : /home/oracle/software/OMS10g_backup
$ tar cvf oms10g.tar /ora/fs0000/app/oracle/product/10.2/oms10g

Do the same command on the other server/servers. I only have two oms servers so will do only on servers grid01/grid02.

oracle : grid02 : @oms10g : /home/oracle/software/OMS10g_backup
$ tar cvf oms10g.tar /ora/fs0000/app/oracle/product/10.2/oms10g


Also tar the agent binaries as:
oracle : grid01 : @oms10g : /home/oracle/software/Agent10g_backup
$ tar cvf oms10g.tar /ora/fs0000/app/oracle/product/10.2/agnet10g

Do the same command on the other server/servers. I only have two oms servers so will do only on servers grid01/grid02.

oracle : grid02 : @oms10g : /home/oracle/software/ Agent10g_backup
$ tar cvf oms10g.tar /ora/fs0000/app/oracle/product/10.2/agent10g



Now create a guaranteed flashback point on database level. Here we are enabling flashback in the database too.

SQL> select flashback_on from v$database;

FLASHBACK_ON
------------------
NO

SQL> show parameter recovery

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest string
db_recovery_file_dest_size big integer 0

SQL> alter system set db_recovery_file_dest_size=30G;

System altered.

SQL> alter system set db_recovery_file_dest="+ RECV1 " ;

System altered.

oracle : grid01 : @REPR1 : /home/oracle/software/ Agent10g_backup
$ srvctl stop database -d REPR

Log back in and startup mount + start flashback

SQL> startup mount
ORACLE instance started.

Total System Global Area 3758096384 bytes
Fixed Size 2045064 bytes
Variable Size 1342180216 bytes
Database Buffers 2399141888 bytes
Redo Buffers 14729216 bytes
Database mounted.
SQL> alter database flashback on;

Database altered.

SQL> shutdown immediate

SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP, Data Mining
and Real Application Testing options

oracle : grid01 : @REPR1 : /home/oracle/software/ Agent10g_backup
$ srvctl start database -d REPR

oracle : grid01 : @REPR1 : /home/oracle/software/ Agent10g_backup
$ srvctl start service -d REPR

oracle : grid01 : @REPR1 : /home/oracle/software/ Agent10g_backup
$sqlplus / as sysdba
SQL> create restore point before_OMS11g_upgrade guarantee flashback database;

Restore point created.

Check that everything is enabled:

SQL> select FLASHBACK_ON from v$database;

FLASHBACK_ON
------------------
YES

SQL> ALTER SYSTEM SWITCH LOGFILE;

System altered.

SQL> select estimated_flashback_size,flashback_size from v$flashback_database_log;

ESTIMATED_FLASHBACK_SIZE FLASHBACK_SIZE
------------------------ --------------
0 31866880






Now lets Install/upgrade Grid Control 11g

Now stop the Management agent on the OMS you are upgrading. I am doing that on first node i.e. grid01.

. oraenv
agent10g

oracle : grid01 : @agent10g : /home/oracle/software
$ emctl stop agent
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Agent is Not Running

Now we will install.

Check your DISPLAY property is set and start your X Window app.

oracle : grid01 : @agent10g : /home/oracle/software
$ env |grep DISPLAY
DISPLAY=192.168.1.140:0.0

cd /home/oracle/software/GridContol/11.1

oracle : grid01 : @agent10g : /home/oracle/software/GridContol/11.1
$ ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 150 MB. Actual 87354 MB Passed
Checking swap space: must be greater than 150 MB. Actual 94539 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed
...
oracle : grid01 : @agent10g : /home/oracle/software/GridContol/11.1
$ ./runInstaller

On first screen uncheck “I wish to receive security updates via MY Oracle Support” and click next.
On next pop up click Yes to “Do you wish to remain uninformed of critical security issues …..”
On next screen make sure “Skip Software Updates is clicked and click next.
On next screen make sure “Upgrade to Enterprise Manager 11g” and click next.
On next screen make sure the current agent/oms base and version is correct and is checked/selected and click next.
There are prerequisites on next screen and make sure all succeed and click next.

At next screen if it doesn’t accept the sys password and error at invalid username/password, just stop instance 2 on server grid02 and make sure all the services are running and try again and it will move to next screen.
And if the connect descriptor is incorrect, you have to change the $ORACLE_HOME/sysman/config/emoms.properties

oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION\=(ADDRESS_LIST\=(FAILOVER\=ON)(ADDRESS\=(PROTOCOL\=TCP)(HOST\=grid01)(PORT\=41521)))(CONNECT_DATA\=(SERVICE_NAME\=GRIDsv1)(SERVER\=DEDICATED)))

And retry connectivity.

On next screen “Change the OMS instance base location to end in “11.1” instead of “gc_inst”
and make sure the Middleware and the OMS base location is correct and click next. Here installer checks for space and will error out if we don’t have enough space.
On next screen enter the password of GCDomain user. Username is “weblogic” and password whatever you want. On this screen also enter the password of “nodemanager”. The password you create has to be 8 digits and contain alphanumeric. Also for “JVM diagnostic data tablespace” enter following +DATA1/REPR/DATAFILE/mgmt_ad4j.dbf. Now click next.

On next keep the ports default and click next. (Remember to take and save the snapshot of this window, will help you in checking port no.s in extending ths OMS to new server)
On next screen click “Install” and the install will start.

At the end of the installation you will be prompted to run a script for the root.
If prompted, accept all defaults and it should finish without errors and after that click ok and some Configuration Assistants will run. The process will take at least 2-3 hours so be prepared to wait:

It may fail at step oms configuration, just execute the script in the error popup window as sysman and click retry and then it should be ok. This error may be due to some invalid objects.
(The Repository Upgrade portion takes the longest)
After keeping the snapshot of last window that has the url to connect click close.


Now some post steps:

Change the job_queue_processes parameter back to the original value

SQL> sho parameter job_queue

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes integer 0

SQL> alter system set job_queue_processes=20;

System altered.

SQL> sho parameter job_queue

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes integer 20

Start DBMS Scheduler as sys:

SQL> execute dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','FALSE');

PL/SQL procedure successfully completed.

SQL> conn sysman
Enter password:
Connected.

SQL> execute emd_maintenance.submit_em_dbms_jobs;

Reconnect as sys and submit the gather stats jobs:

SQL> conn / as sysdba
Connected.
SQL> execute dbms_scheduler.enable('GATHER_STATS_JOB');

PL/SQL procedure successfully completed.



PL/SQL procedure successfully completed.


Update the oratab with the new agent and OMS home:

#oms10g:/ora/fs0000/app/oracle/product/10.2/oms10g:N
#agent10g:/ora/fs0000/app/oracle/product/10.2/agent10g:N
agent11g:/ora/fs0000/app/oracle/product/Middleware/oms11g:N
agent11g:/ora/fs0000/app/oracle/product/Middleware/agent11g:N

And test you can query them:

oracle : grid01 : @agent11g : /home/oracle
$ 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 : /ora/fs0000/app/oracle/product/Middleware/agent11g
Agent binaries : /ora/fs0000/app/oracle/product/Middleware/agent11g
Agent Process ID : 21210
Parent Process ID : 21195
Agent URL : https://grid01:3872/emd/main/
Repository URL : https://grid01:1159/em/upload
Started at : 2011-01-15 02:49:16
Started by user : oracle
Last Reload : 2011-01-22 02:57:35
Last successful upload : 2011-01-22 05:15:38
Total Megabytes of XML files uploaded so far : 37.80
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 17.72%
Last successful heartbeat to OMS : 2011-01-22 05:24:30
---------------------------------------------------------------
Agent is Running and Ready

oracle : grid01 : @oms11g : /home/oracle
$ 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

Next remove old 10g Middleware targets

Now log into your new 11.1 Grid control OMS and we’ll have to do some cleanup

In particular, remove

_home
_OC4J_EM
_OC4J_EMPROV
_HTTP Server
Web Cache.

Some have to be removed one at a time for proper cleanup.

Other issues you may notice:

"EMGC_ADMINSERVER/FMW Welcome Page Application(11.1.0.0.0)" -Target Down [ID 1100553.1]

Apply patch 9431704 to fix this.


At the time of writing this note we had PSU 2 released a few days ago. So, apply it on top of this 11gr1 OMS. It may take 2-3 hours to apply this PSU. Before applying this PSU upgrade the OPatch to latest OPatch for 11gR1 and not 11gR2 for both OMS and Agent.

-------------------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html


-----------------------------------------------------------------------

Those who remember God generously help others. Those who remember God -- to them, I am forever a sacrifice. Those who remember God -- their faces are beautiful. Those who
remember God abide in peace. Those who remember God conquer their souls. Those who remember God have a pure and spotless lifestyle. Those who remember God experience all sorts of joys. Those who remember God abide near the Lord. By the Grace of the Saints, one remains awake and aware, night and day.

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic

Meditate, meditate, meditate in remembrance of Him, and find peace. Worry and anguish shall be dispelled from your body. Remember in praise the One who pervades the whole Universe. His Name is chanted by countless people, in so many ways. The Vedas, the Puraanas and the Simritees, the purest of utterances, were created from the One Word of the Name of the Lord. That one, in whose soul the One Lord dwells -- the praises of his glory cannot be recounted.

Index of all the posts of Gurpartap Singh's Blog

---------------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html

--------------------------------------------------------------

Here are the steps required to upgrade a 10.2.0.4+ Enterprise Manager Grid
control OMS + Repository to 11G Release 1.

You can also refer too:
http://download.oracle.com/docs/cd/E11857_01/install.111/e15838/upgrade_em.htm#CHDEJGAH

I did this upgrade on a Solaris 10 Sparc64 machine.

2. Prerequisites
Oracle Grid Control 11g Release 1 installation is now a web app on top of a Weblogic tier, so there are specific
requirements and prerequisites before you can install the OMS.

Make sure you are running on a supported OS. Make use of Oracle Enterprise Manager Grid Control Certification Checker 412431.1

If you want to do a fresh install and are not upgrading then look at following post from the main index of my blog:
http://gurpartapblog.blogspot.com/2010/11/index-of-all-posts.html

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
Part 14 of series, Install Enterprise Manager Grid Control 11gR1

The OMS repository database must be at 10.2.0.4 or above. If it is not, upgrade it first. Also check the documented
prerequisites in case your database version requires oneoff patches applied.

In this case OMS repository database is at 10.2.0.4 and is a two node RAC hosted on top of 11.2.0.2 Grid infrastructure
that was upgraded from 11.2.0.1 grid infrastructure. The hostnames are grid01 and grid02 and the database name is “repr”
and the instance names are “repr01” and “repr02”. I already have grid control oms10g (10.2.0.5, PSU4) installed on both
the servers.



You will also need:

1.Java JDK 1.6 Update 18 for Sparc 64
http://java.sun.com/products/archive/j2se/6u18/index.html

2.Oracle WebLogic Server 10.3.2 32 and 64 bit
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html

3.Oracle Enterprise Manager Grid Control 11gR1 for Sparc 64
http://www.oracle.com/technetwork/oem/grid-control/downloads/solsoft-094433.html

Do NOT install newer versions of WebLogic server. It must be the EXACT required version.
You can install the newest version of JDK as it fixes few bugs in Grid Control , like some performance problems on high CPU usage.

Disk space: It is recommended to have at least 8GB free for the Weblogic and Grid Control binaries
on EACH OMS server.


Installing JDK 1.6 Update 18

I am installing JDK on both grid01 and grid02 servers as I have two oms in the configuration. If you have more
then install on all the oms servers. Here, I am showing the steps to install only on one server.

Navigate to http://java.sun.com/products/archive/j2se/6u18/index.html and select Solaris SPARC/LINUX for your platform.
Click Continue.

You will see 4 files, the .sh files are self extracting binaries. The .Z files are Solaris packages.

To install the 64 bit Java in Solaris Sparc 64, you need 2 files, the 32 and 64 bit versions of the self extracting binaries. Download both of them.

Copy the file to the product directory on the the OMS server to be upgraded. I will put them under
/ora/fs0000/app/oracle/product/gridcontrol_11g_jdk

Make sure it’s execute permissions are set.

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk
$ chmod +x jdk*.sh
oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk
$ ls -lrt *.sh
-rwxr-xr-x 1 oracle oinstall 12088713 Jan 20 20:29 jdk-6u18-solaris-sparcv9.sh
-rwxr-xr-x 1 oracle oinstall 89823634 Jan 20 22:02 jdk-6u18-solaris-sparc.sh

Now we will install the 32 bit libraries first. Execute jdk-6u18-solaris-sparc.sh. You’ll see a lengthy License Agreement to review just keep scrolling down and type “yes” in the end to accept the agreement.

Then you will the prompt “Press Enter to Continue” just hit Enter
The files will get unpacked and you will get the command prompt.

Now let’s verify if the java is installed by going into the jdk1.6.0_18/bin directory and running “java –version”

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk/jdk1.6.0_18/bin
$ ./java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Server VM (build 16.0-b13, mixed mode)

Now we will install the 64 bit portion. Execute the following command from directory:
/ora/fs0000/app/oracle/product/gridcontrol_11g_jdk

./jdk-6u18-solaris-sparcv9.sh

You will see another license agreement to review. Type “yes” at the end.
The installation will then unpack the files again as it did with the previous command. i.e. it will extract the binaries into the same directory as the 32 bit we unpacked earlier. Now you can check if the install went fine.. The 64-bit binaries are in the sparcv9 directory, so I will use a flag to test it. Run “./java –d64 –version”

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk/jdk1.6.0_18/bin
$ ./java -d64 -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)

If you want to save space remove the 2 .sh files to clean it up.

oracle : grid01: @ oms10g: /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk
$ rm jdk-6u18-solaris-sparcv9.sh
oracle : grid01: @ oms10g: /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk
$ rm jdk-6u18-solaris-sparc.sh

Now insall JDK on grid02 server by repeating the same steps.
So, jdk install is done and lets do the WebLogic Server install.
1.1 Installing WebLogic Server 10.3.2 + WDJ7 Patch
Download Weblogic Server by going to:
http://www.oracle.com/technetwork/middleware/ias/downloads/wls-main-097127.html

Click “See all files +” to expand the 10.3.2 selection.

We are installing the 64-bit version, so we want the Generic installer as per the directions:

Note: This table includes links to WebLogic Server installers that include 32-bit JVMs for the platform in question, and links to WebLogic Server generic installers that can be used on any supported platform. To use WebLogic Server with 64-bit JVM's on Linux and Solaris or to use WLS on other supported platforms, use the WebLogic Server generic installer listed under "Additional Platforms".

Install Weblogic:
Now transfer the files to the server using Winscp. If you have created a ACFS file system that will be very helpful here or you can place these files on the NFS mount that is mounted on botht the servers grid01 and grid02. In this case I neither have ACFS file system and nor I have common NFS mount. So we will store the software and move it to the other server wih scp once we will be done on fires server.

My staging directory to place softwares is “/home/oracle/software”. Copy the downloaded files over there on server grid01 server.
oracle : grid01 : @oms10g : /home/oracle/software
$ ls -ltr
total 1848167
-rw-r--r-- 1 oracle oinstall 945517652 JAN 10 21:43 wls1032_generic.jar

Set display
oracle : grid01 : @oms10g : /home/oracle/software
$ env grep display
DISPLAY=192.168.1.140:0.0

Start you x-server software i.e. Xming/Exceed/Reflection and start the install.
/java -d64 -jar wls1032_generic.jar

oracle : grid01 : @oms10g : /home/oracle/software
$ /ora/fs0000/app/oracle/product/gridcontrol_11g_jdk/jdk1.6.0_18/bin/java -d64 -jar wls1032_generic.jar

You will need at least 1.2 GB under /var directory or this install will fail with a fatal error.

“fatal error encountered on space”

1. After that the weblogic instal will start and the window will open. Click next on this window.
2.On next screen type the directory path where you want to install weblogic. I am entering
/ora/fs0000/app/oracle/product/Middleware and click next.
3.On next screen uncheck “I wish to receive security updates via My Oracle Support” and click next.
4.On next screen click “Yes” to bypass the configuration manager.
5. Click next again and then wait for 5 minutes (you may think the installer is hung but its not) after 5 minutes on next window uncheck "I wish to remain uninformedof security issues in my configuraton on this machine and has no internet access" and click continue.
6. On next screen click next and make sure "Typical" is checked.
7. On next screen make sure hte jdk you installed in the last step is checked and click next.
8. On next screen enter the location where you want to install weblogic and in my case I am doing on:
/ora/fs0000/app/oracle/product/Middleware/wlserver_10.3 and click next.
9. On next screen you will Installation summry and just click next.
10. Now instal will start.
11. After installation unckeck "Run Quickstart" and click done. As quick start configures wls domain for trail use and that is not required.

Now we will patch weblogic before upgrading OMS.
Refer to Note 1072763.1 for instructions on how to apply offline patch to WLS.

Direct link is:
https://support.oracle.com/CSP/main/article?cmd=show&type=ATT&id=1072763.1:WDJ7

Download it and place it under software directory and unzip it.
oracle : grid01 : @oms10g : /home/oracle/software/WLS_patch
$ ls -lrt
total 1797
-rw-r--r-- 1 oracle oinstall 895498 Jan 11 00:05 WDJ7.zip

oracle : grid01 : @oms10g : /home/oracle/software/WLS_patch
$ unzip WDJ7.zip
Archive: WDJ7.zip
inflating: 4D53.jar
inflating: NIXN.jar
inflating: patch-catalog.xml
inflating: prod-info.xml
inflating: WDJ7.jar
inflating: XLXA.jar

oracle : grid01 : @oms10g : /home/oracle/software/WLS_patch
$ ls -lrt
total 1803
-rw-r--r-- 1 oracle oinstall 127196 Jun 7 2010 prod-info.xml
-rw-r--r-- 1 oracle oinstall 9762796 Jun 7 2010 patch-catalog.xml
-rw-r--r-- 1 oracle oinstall 4904 Jun 7 2010 XLXA.jar
-rw-r--r-- 1 oracle oinstall 3652 Jun 7 2010 NIXN.jar
-rw-r--r-- 1 oracle oinstall 8683 Jun 7 2010 4D53.jar
-rw-r--r-- 1 oracle oinstall 387 Jun 7 2010 WDJ7.jar

The WDJ7 patch is a collection of 3 other bugfix patches hence all the different jar files. Change to the /utils/bsu directory and verify the files are readable:

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/Middleware/utils/bsu
$ ./bsu.sh -prod_dir=/ora/fs0000/app/oracle/product/Middleware/wlserver_10.3 -patch_download_dir=/home/oracle/software/WLS_patch -status=downloaded -view -verbose

If output is ok then apply the patch with the following command.

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/Middleware/utils/bsu
$ ./bsu.sh -prod_dir=/ora/fs0000/app/oracle/product/Middleware/wlserver_10.3 -patch_download_dir=/home/oracle/software/WLS_patch -patchlist=WDJ7 -verbose -install

You will see all the 3 patches as a success and then lets verify if its ok with the following command,
The patch is installed. Now we’ll verify the patch

oracle : grid01 : @oms10g : /ora/fs0000/app/oracle/product/Middleware/utils/bsu
$ ./bsu.sh -report -patch_id_mask=WDJ7

Now do these same steps on grid02 and once done we are ready to install and upgrade grid control from 10.2.0.5 to 11.1.0.1.0

------------------------------------------------------------------

To do a Fresh install of 11gR1 Look at posts 12,13 and 14.

Part 12 of series, Install JDK for Enterprise Manager Grid COntrol 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control.html

Part 13 of series, Install Weblogic wls10.3.2 for Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_29.html

Part 14 of series, Install Enterprise Manager Grid Control 11gR1
http://gurpartapblog.blogspot.com/2010/09/install-oracle-install-grid-control_2064.html



To upgrade existing Enterprise Manager Grid control from 10.2.0.4/10.2.0.5 to 11.1.0.1


Part 30 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Upgrade Additional Grid Control , OMS
http://gurpartapblog.blogspot.com/2011/02/part-30-of-series-upgrade-enterprise.html

Part 29 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install and upgrade Grid Control, OMS
http://gurpartapblog.blogspot.com/2011/02/part-29-of-series-upgrade-enterprise.html

Part 28 of series - Upgrade Enterprise Manager Grid Control from 10.2.0.5 to 11gr1 (11.1.0.1) on Solairs/Unix, Install JDK and Weblogic
http://gurpartapblog.blogspot.com/2011/02/part-28-of-series-upgrade-enterprise.html



------------------------------------------------------------------

Remembering God, one does not have to enter into the womb again. Remembering God, the pain of death is dispelled. Remembering God, death is eliminated. Remembering God, one?s enemies are repelled. Remembering God, no obstacles are met. Remembering God, one remains awake and aware, night and day. Remembering God, one is not touched by fear. Remembering God, one does not suffer sorrow. The meditative remembrance of God is in the Company of the Holy.