on 03-26-2009 11:31 PM
Dear All,
This is to request you that anyone having a sure shot Installation guide /Solution to Install SAP in High Availablity using following platform.
1. AIX 6.1
2. DB2 9.1
3. HACMP
4. ECC 6.0 SR 2
Note: Not Failover by scripting. High Availablity like Microsoft MCSC. Complete installation on Virtual host, IP and Shared File system/stirage.
Please....................................................
Regards
Dharmendra
On Node B, as root
su u2013 db2prd
you should be in /db2/db2prd now
rm ._dbserver (remove the env profile with hostname in the filenames)
rm ._ciserver
logout
su u2013 db2prd (environment should be fine now)
db2 terminate (donu2019t forget this)
db2 start
db2 connect to PRD
This should be successful (i.e. its good to HACMP)
logout
as root
su u2013 prdadm
rm ._dbserverrm
rm ._ciserverrm
logout
su u2013 prdadm
cdpro (you will be in /sapmnt/PRD/profile)
Check and modify DEFAULT.PFL correctly to indicate DB hostname, etc.
R3trans u2013d (this should be successful, SAP is good to start now).
As of now SAP and DB2 resources are available in Node B
startsap ciserver
SAP should come up
stopsap ciserver
SAP and DB2 should go down.
Move DB2 and SAP resources to Node A
as prdadm
startsap ciserver
SAP and DB2 should come up
stopsap R3 ciserver
only SAP should go down
move SAP resource to Node B
on node B
as sidadm u201Cstartsap ciserveru201D
SAP should come up.
At this stage DB2 is running on Node A and SAP CI is running on Node B.
We have achieved what we want.
If you are doing several attempts of installation, you may have difficulties removing DB2.
How to delete and clean up DB2 installation?
Drop database: As db2prd > db2start > db2 drop database PRD > db2stop force
Drop instance: As root go to /db2/PRD/db2_software/instance > db2idrop db2prd
Uninstall db2: As root go to /db2/PRD/db2_software/install > ./db2_deinstall u2013a
Cleanup db2: As root > rm /tmp/db2* > rm /var/db2 > rm /db2/DB2// > rm /db2/db2svp/*
GOOD LUCK !!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Installing SAP NW07 SR3 with DB2 on AIX HACMP
Scenario:-
DB will run on Node A
SAP CI will run on Node B
If node A fails DB will failover to Node B
If node B fails CI will failover to Node A
Shared SAP and DB filesystem are in SAN
Filesystems will failover accordingly
Requirements:-
SAP NW07 SR3 DVDs
AIX Node A
AIX Node B
HACMP supports node failures. We are not using HACMP to probe Application (SAP/DB) failures. i.e. if SAP or DB process crashes HACMP will not failover the resource groups.
/etc/hosts should have IPs of both nodes
Assumptions:-
PRD = PRD
Node A hostname: dbserver
Node B hostname: ciserver
Shared filesystems
These filesystems can be moved/ failed over (unmounted /mounted) from one node to another.
/usr/sap/PRD
/sapmnt/PRD
/db2/PRD
/db2/db2prd
/db2/PRD/sapdata1
/db2/PRD/sapdata2
/db2/PRD/sapdata3
/db2/PRD/sapdata4
/db2/PRD/log_dir
/db2/PRD/db2dump
Users and Groups will be created by SAPINST.
Please make a note of the UIDs as we have to use the same UIDs and GIDs on other node as well.
User Home directory:- For prdadm please use a home directory on shared disk
For e.g. /usr/sap/PRD/home/prdadm
Use Distributed Installation option in SAPINST
Installation steps:-
Node A:
Mount SAP filesystems
Mount DB2 filesystems
Check /etc/hosts that IP of both nodes are available
Ping both nodes and check the IP address
Check output of command ifconfig u2013a and confirm that both IPs are available
Start SAPINST with SAPINST_USE_HOSTNAME option.
For e.f. ./sapinst SAPINST_USE_HOSTNAME=dbserver
Step 1: Global host preparation (this should be easy to finish)
Step 2: Database instance installation
During this step note down UIDs and GIDs created by sapinst.
During this step please choose /usr/sap/PRD/home/prdadm as user home for prdadm user.
With SR3 DVDs db2 software will be installed in /db2/PRD/db2_software
Step 3: Install SAP Central Instance with SAPINST_USE_HOSTNAME=ciserver
Stop / Start SAP -> Login and confirm SAP instance is running fine.
Shutdown SAP and DB2
Add entries in .rhosts in home directory on user prdadm and db2prd
For example in /usr/sap/PRD/home/prdadm/.rhots
<IP Address of Node A> prdadm
<IP Address of Node B> prdadm
<all possible IP address> prdadm
Similarly for /db2/db2prd/.rhosts
<IP Address of Node A> db2prd
<IP Address of Node B> db2prd
<all possible IP address> db2prd
Node B:
Move SAP resources from Node A to B (i.e. SAP filesystems should become available on Node B)
DO NOT MODE DB RESOURCES, Let it stay on Node A alone.
Create /db2/PRD and /db2/db2prd directories (this should have some free space, 10 GB is good to go)
Start SAP installation under Distributed installation option
Step 1: Global host preparation
Temporarily change /etc/hosts and make the IP of dbserver same as ciserver.
dbserver line should be written above ciserver line
i.e. u2018ping dbserveru2019 and u2018ping ciserveru2019 should return same IP address on Node B (NOT NODE A)
Step 2: Database instance installation with option SAPINST_USE_HOSTNAME=dbserver
During this installation, make sure UIDs and GIDs are given same as in Node A.
You can confirm the UIDs from /etc/passwd and GID from /etc/group
Also, make sure you specify user home for prdadm as /usr/sap/PRD/home/prdadm
Once installation starts ABAP Load and one or two jobs are completed, please cancel the installation.
as db2prd
db2stop force
db2start
db2 connect to PRD
It should be successful. This confirms the DB2 is setup properly.
db2stop terminate
db2stop force
rm u2013r /db2/db2prd/*
rm u2013r /db2/PRD/sapdata1
rm u2013r /db2/PRD/sapdata2
rm u2013r /db2/PRD/sapdata3
rm u2013r /db2/PRD/sapdata4
rm u2013r /db2/PRD/log_dir
rm u2013r /db2/PRD/db2dump
Retain these directories so that you can mount the shared filesystems from Node A to Node B during failover.
Change and correct IP address in /etc/hosts of host dbserver, which we changed temporarily earlier.
Failover DB resources to Node B
Check if all DB2 filesystems are correctly available.
On Node A, check and double confirm that there are no files/directories under /db2 and its subdirectories. i.e. all filesystems have come to Node B.
In our case there was one filesystem /db2/PRD/db2prd which did not come to node B and we had to struggle a lot to find the same.
CONTINUED BELOW !!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
NO DB2 CATALOGING IS REQUIRED TO ACHIVE DB2 FAILOVER
Several documents in net explains the db2 cataloging. Which is not really necessary to achieve HACMP failover.
Below is the procedure we adopted to achive this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dharmendra,
I would suggest you to go through the installation guide URL to find the appropriate installation guide for you and all the pre-requisites like JDK version, patch level for OS and DB.
You can find installation guides at http://service.sap.com/instguides
Also you can go through the pam at http://service.sap.com/pam
Hope this helps.
Manoj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.