SAP Upgrade in Cluster Environment

Hi,
Need information regarding SAP upgrade in cluster environment(MSCS) like if any prerequisites need to be done.
and if any aditional steps to be performed compared to normal upgrade.
Thanks in advance.
Regards
Ram

the upgrade guide tells you what to do, read it throughly.

Similar Messages

Data storage on a SAP WEB AS cluster environment

Hi,
We are using the SAP WEB AS 7.0 and I'm facing a problem with a single sign on (SSO) in a clustered environment.
The SSO works like this:
1. On an application outside of our WEB AS (Customer Application) a user logs on and an object called Token is send to a servlet on our application on the WEB AS (Internal Application). This Token is saved within the servlet context and contains data of the user.
2. If the user then decides to call our Internal Application, he clicks a link on the Customer Application and a second Token is send to our Internal Application. A new session in our Internal Application will be created and a search in the servlet context for the first Token for this user starts. If the first Token is found, the data from the second token will be matched with the first token.
This works fine in a single node environment. But in a clustered environment the Token objects will be spread among all server nodes because each server node holds its own servlet context. And there is my question: <b>How can I store the first Token object, so that I can reach the data within other session from every other server node?</b>
Sticky sessions are not an option, because this SSO works asynchronous and we have a session for the first Token and another session for the second Token. There are up to 800 concurrent users and the time difference between the first and the second token can be milliseconds. So Im afraid storage in the database would not work either.
I hope someone can help me with that.
Nora

Hi Nora,
When you persist the information you need in the database, you don't have a problem with multiple server nodes. Simply create a CMP EJB ("Container Managed Persistence") that holds everything you need for your single sign on. You just have to keep in mind hat you need something that does a cleanup for the data you stored in the database...
As far as I know, there is no way to deal with this issue without using a persistency layer.
Best regards,
Frank

How to upgrade SAP Kernel in clustered environment

I have a SAP R3 4.6 C installed on cluster environment, such that if one server goes down, the second clustered server takes the charge of all the resources from failing server. Also I have 6 application servers.
This is the reason, I have to mantain the SAP exe files in /exe/run on the 6 different application servers seperately. My question is: If I have a shared directory for exe files on central instance, and it goes down, then the 6 application servers will lose connection to those exe files. Then, how should I then connect these 6 apps servers to exe files of the 2nd failover clustered server?
So please let me know how to resolve this problem.

Hi Matt,
Thanks for the update. The cluster is installed with virtual host. But unfortunately we have all exe files seperately on different 6 app servers. Should we NFS mount the exe directory on all apps server. Is NFS mounting sufficient or there are any additional steps to done. I heard that we have to activate sapcpe on the apps server.
Also after the kernel upgrade, do we have to distribute it on all the apps servers. Can you kindly guide me in this issue.
Thanks,
Arun

Steps to upgrade kernel patch in AIX cluster environment

Hello All,
We are going to perform kernel upgrade in AIX cluster environment.
Please let me know the other locations to copy the new kernel files ,
default location
CI+DB server
APP1
Regards
Subbu

Hi Subbu
Refer the SAP link
Executing the saproot.sh Script - Java Support Package Manager (OBSOLETE) - SAP Library
1. Extract the downloaded files to a new location using SAPCAR -xvf <file_name> as sidadm.
2. copy the extracted files to sapmnt/<SID>/exe
3. Start the DB & Application.
Regards
Sriram

SAP R/3 4.7 SR1 Migration to MSCS cluster environment

Hi all,
We are planning to move our existing standalone server R/3 production server to cluster environment.
I have some queries regarding this migration
Our R/3 system is running on SAP R/3 4.7x1.10 SR1 on Windows 2003 and Oracle 9.2
1. Central Instance has to be installed in local disk or shared disk
2. Is it correct to R3load procedures to export data from old server and import during Database installation
3. Presently our server is running with kernel 640, but for the new installation kernel will be 620. So when can i upgrade kernel immediately after central instance installation or after CI and DB Instance installation.
Give me some inputs
Thanks & Regards
KT

Hi, the best place for your questions would have been the forum SAP on Windows.
However, here the answers.
1) CI must be on a shared disk
2) Right, if you don't change the database platform and its release you can also use backup/restore
3) Right. You can also perform the installation with the latest NW04 installation master

Move SAP ECC standalone system to High Availability cluster environment.

Hi,
I have requirement to move SAP ECC stand alone system to cluster environment.
OS - MS server 2003
DB - Oracle 10
What steps need to follow to perform this activity?
What down time required?
Please Help.
Regards
Amit

Hi Amit
1. You have to perform SAP Homogeneous system copy method from soure to target
Kindly refer the system copy guide
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00f3087e-2620-2b10-d58a-c50b66c1578e?QuickLink=index&…
refer the SAP note FAQ 112266
2. Before that check the PAM you present version supported Windows 20008 / Oracle 11 G?
refer the SAP link http://service.sap.com/PAM
3. Over all down time may be 20 hrs time
BR
SS

SAP BusinessOne Upgrade in citrix environment

Hi experts ,
I ahave a question regarding upgrade in citrix environment
I have a client who is using 2007 and I am planning to upgrade to 8.8 . After server and client upgrade , do I need to publish the application or it will automatically replaces the old apllication (2007) to 8.8
At this point , application 2007 is published .
Please share your experience with me .
Thank you
Bishal

Hi Bishal,
When you say after server and client upgrade, do you mean all clients are upgraded?
Thanks,
Gordon

SQL PATCH IN CLUSTER ENVIRONMENT

Dear All,
One of my client is having SAP ECC6.0 , SQL 2005 , windows 2003 64 bit.
They are having SQL 2005 version 9.00.1399 and according to SAP it is no more supported so they want to upgrade it to 9.00.4035.
In DEV and QAS (non cluster environment) they are already having 9.00.4035 .
- Can you guys please guide me about how to apply SQL patch in Cluster environment.
- Shall I apply patch 9.00.4035 directly from 9.00.1399
- Any recommendations before and after applying patched
Kindly guide.
Regards,
Rmoihnitii

Hello my friend
Unfortunately this is not a zero down time solution since Database Services and Analysis Services checkboxes will not be available while patching SP3:
1. Launch SP3 package on the active node;
2. Select authentication mode for the instance you are going to update;
3. Enter credentials of the login you want to run service pack on behalf of;
4. Click all the way next to start installing;
Then you need to update the inactive node it is necessary to execute all the steps except steps 2 and 3. There can be some problems with updating database service in the cluster. Restart of each node of the cluster and restart of the cluster service usually resolves all the problems. After restart try to update database service one more time.
Regards,
Effan

Livecache patch upgrade in MSCS environment

Hello everyone,
I have installed livecache 7.7.02   BUILD 008-123-149-275 in MSCS and planning to upgrade the patch level to KERNEL    7.7.04   BUILD 029-123-196-543.
My installation type is,
Independent Programs directory      - local hard disk
Independent Data Directory             - distributed disk
Instance Dependent directory          - local hard disk
So note Note 508979 - Upgrade of SAP DB/MaxDB/liveCache w/ Cluster MSCS Var.1 applies in my case.
However, need help in understanding one section of this note,
Points 14 and 15 talk about notes on how to run SDBUPD, however do not specify whether SDBUPD is to be run on node B. After manually copying the files to node B, as described in the note, do we still need to run upgrade (SDBUPD) on node 2 ?
Also, It would be great to have some more reading on Livecache upgrades in MSCS environment.
Thanks in advance.
Regards,
Kiran

Hello Ivan,
Thanks for the reply.
I started upgrading livecache patch as per note 508979. Completed the patch upgrade node 1 using SDBINST. Completed all the steps till step 13. On step 14, I started SDBUPD on node B.
At this stage I get following message on command prompt,
Install>SDBUPD -d MLP -u control,<password>
        SAP liveCache INSTANCE UPDATE
starting installation We, Jun 10, 2009 at 14:59:10
operating system: Windows AMD64 NT 5.2 Service Pack 2
callers working directory: C:/Dumps/Latest_Livecache_Kernel/lca600018_livecache-
win-64bit-x86_64-7_7_04_29
installer directory: C:/Dumps/Latest_Livecache_Kernel/lca600018_livecache-win-64
bit-x86_64-7_7_04_29
archive directory: C:/Dumps/Latest_Livecache_Kernel/lca600018_livecache-win-64bi
t-x86_64-7_7_04_29
beginning to check sap db instances
start new instance update
The installation remains stuck after this message.
I ensured xserver and sap instance were stopped before installation. Tried rebooting the server (Node B), but same result.
Pls can you suggest something on this.
Regards,
Kiran

Deploying Java Web Application (WAR-File) into a cluster environment

Hi,
we have a web application which has to read from and write to the file system.
Since a short time we have a cluster environment (2 parallel servers) and since thisa time we have the problem, that files are worked double in the cluster. The application is working on both servers now and so we have this problem.
Does anybody know how we have to deploy the application correctly in a cluster environment or do we have to change anything in our source code of the application?
I didn't find any documentation about this.
At the moment we have deployed the application on one of the two servers only, but I think there must be a better way to solve this problem.
Thanks for your replies.
Regards
Thorsten

Hi,
I think first you need to wrap it into an EAR file, then you can deploy it.
As far as I know standalone deployment of WAR is deprecated as of 640.
similar threads:
How to deploy .war on NWDI
Deploying an existing WAR file into the Portal
Hopefully this tutorial also gives some idea:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/70/13353094af154a91cbe982d7dd0118/frameset.htm
Regards,
Ervin

PI 7.1 in a cluster environment (multiple ip-adresses): P4 port

We want to install PI 7.1 on unix in a cluster environment.Therefore we installed also DEV+QA with virtual hostnames like the prodsystem, which will be later installed.
At all sapinst installation screens we have used only the virtual hostname <virtual-hostname-server interface>.We have also set the SAPINST_USE_HOSTNAME=<virtual-hostname-server interface>. Although the P4-port seems to have used the physical hostname: in step 57 of sapinst we got problems and in dev_icm were:
[Thr 05] *** ERROR => client with this banner already exists:
1:<physical-hostname>:35644 {000306f5} [p4_plg_mt.c 2495]
After we have set
icm/server_port_1 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-server interface>
icm/server_port_6 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-user interface>
icm/server_port_7 = PROT=P4,PORT=5$$04, HOST=<physical hostname>
icm/server_port_8 = PROT=P4,PORT=5$$04, HOST=127.0.0.1
the sapinst was successfull.
Now we're not sure how to set these P4-parameters in our future productive cluster environment.
Our productive system PX1 will live in a HA environment, so we don't want to use the physical hostnames in any profile.
Our environment will look like:
HOST-A (<physical-hostname-A>):
<virtual-hostname-server interface>
<virtual-hostname-user interface>
HOST-B (<physical-hostname-B>):
Normally our prodsystem will live on Host-A (physical-hostname-A). All parameters should
only take the virtual hostname <virtual-hostname-server-interface>. During switchover the
virtual hostnames (server and user interface) will be taken over to HOST-B, while the physical
hostnames of HOST-A and HOST-B will stay like there are.
How do the parameters have to be set here ?
Have also the physical hostnames of both cluster nodes set in the
instance profile, e.g:
icm/server_port_1 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-server interface>
icm/server_port_6 = PROT=P4,PORT=5$$04, HOST=<virtual-hostname-user interface>
icm/server_port_7 = PROT=P4,PORT=5$$04, HOST=<physical-hostname-A>
icm/server_port_8 = PROT=P4,PORT=5$$04, HOST=<physical-hostname-B>
icm/server_port_9 = PROT=P4,PORT=5$$04, HOST=<localhost>
Any recommendations ? In note 1158626 is some infomation regarding P4 ports with multiple network interfaces, but it's not 100% clear for us.
Best regards,
Uta

Hi Uta!
Obviously we are the only human beings in the SAP community having this problem. Nevertheless let's give it another try with a - hopefully - more simple problem description (and maybe it will be helpful to copy and paste this description into the open SAP CSN also).
So here comes the scenario:
We have one physical host:
Physical hostname: physhost
Physical IP address: 1.1.1.1
On this physical host there is running one OS: SUN Solaris 10/SPARC
On top of this we have two virtual hosts where we install 2 completely independent PI 7.1 instances with separate virtual hostnames and separate virtual IP addresses and separate DB2 9.1 databases. That is this is not an MCOD installation.
Virtual Host no. 1 is PI 7.1 Development System:
Virtual hostname: virthostdev
Virtual IP address: 2.2.2.2
Java Port numbers: 512xx
Virtual Host no. 2 is PI 7.1 QA System:
Virtual hostname: virthostqa
Virtual IP address: 3.3.3.3
Java Port numbers: 522xx
With this constellation we face serious problems with the P4 port. Currently for example the JSPM for virthostdev does not start, because JSPM cannot connect to the P4 port.
In SAP note 1158626 we have learned that by default always the physical hostname/IP address is used to address the P4 port and that we have to configure instance profile parameter icm/server_port_xx to avoid this.
So how do we have to configure the instance profile parameter icm/server_port_xx for both systems to resolve these P4 port conflicts?
Additionally: Is it important to use distinct server port slot numbers xx in both systems?
Additionally: Is it possible to configure this parameter with hostnames instead of using IP addresses?
So far we have tried several combinations, but with each combination at least one or even both systems have problems with that f.... P4 port.
Please help! Thanx a lot in advance!
Regards,
Volker

DB2 is not starting the Cluster environment

Hi, Experts
we are using HP Unix Service Guard cluster envirnment for our
production server.
I have sucessfully installed SAP SR3 in this environment. When the
failover happen, then filesystem is automatically moving. when i try to
start in Node B.
It's throwing error "
02/12/2009 16:09:31 0 0 SQL6048N A communication error
occurred during
START or STOP DATABASE MANAGER processing.
02/12/2009 16:09:32 1 0 SQL6048N A communication error
occurred during
START or STOP DATABASE MANAGER processing.
SQL1032N No start database manager command was issued. SQLSTATE=57019"But it's working fine in Node A. I am attaching the db2diag.log and
trans.log for your reference.
In db2diag.log
2009-02-02-10.42.05.176811+330 I1A1279            LEVEL: Event
PID     : 2928                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, RAS/PD component, pdLogInternal, probe:120
START   : New Diagnostic Log file
DATA #1 : Build Level, 152 bytes
Instance "db2sop" uses "64" bits and DB2 code release "SQL09016"
with level identifier "01070107".
Informational tokens are "DB2 v9.1.0.6", "s081007", "U817477", Fix Pack "6".
DATA #2 : System Info, 1568 bytes
System: HP-UX SOGLPRDP B.11.31 U ia64
CPU: total:8 online:4 Threading degree per core:1
Physical Memory(MB): total:16363 free:11923
Virtual Memory(MB): total:65515 free:61075
Swap     Memory(MB): total:49152 free:49152
Kernel   Params: msgMaxMessageSize:65535 msgMsgMap:4098 msgMaxQueueIDs:4096
                 msgNumberOfHeaders:4096 msgMaxQueueSize:65535
                 msgMaxSegmentSize:248 shmMax:17179869184 shmMin:1 shmIDs:512
                 shmSegments:300 semMap:8194 semIDs:8192 semNum:16384
                 semUndo:4092 semNumPerID:2048 semOps:500 semUndoPerProcess:100
                 semUndoSize:824 semMaxVal:32767 semAdjustOnExit:16384
Information in this record is only valid at the time when this file was
created (see this record's time stamp)
2009-02-02-10.42.38.940922+330 I4655A1629         LEVEL: Event
PID     : 3883                 TID : 1           PROC : db2stop
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 31 bytes
/db2/db2sop/sqllib/adm/db2stop2
DATA #2 : Hexdump, 256 bytes
0x9FFFFFFFFFFFAD60 : 2F64 6232 2F64 6232 736F 702F 7371 6C6C    /db2/db2sop/sqll
0x9FFFFFFFFFFFAD70 : 6962 2F61 646D 2F64 6232 7374 6F70 3200    ib/adm/db2stop2.
0x9FFFFFFFFFFFAD80 : 4E4F 4D53 4700 464F 5243 4500 534E 0000    NOMSG.FORCE.SN..
0x9FFFFFFFFFFFAD90 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADA0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADB0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADC0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADD0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADE0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFADF0 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE00 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE10 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE20 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE30 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE40 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
0x9FFFFFFFFFFFAE50 : 0000 0000 0000 0000 0000 0000 0000 0000    ................
2009-02-02-10.42.49.871047+330 I6285A289          LEVEL: Event
PID     : 4005                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dir_cache" From: "1" To: "0"
2009-02-02-10.42.49.934583+330 I6575A306          LEVEL: Event
PID     : 4006                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Sysadm_group" From: "DBSOPADM" To: "dbsopadm"
2009-02-02-10.42.50.000401+330 I6882A299          LEVEL: Event
PID     : 4007                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Sysctrl_group" From: "" To: "dbsopctl"
2009-02-02-10.42.50.062186+330 I7182A300          LEVEL: Event
PID     : 4008                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Sysmaint_group" From: "" To: "dbsopmnt"
2009-02-02-10.42.50.127927+330 I7483A295          LEVEL: Event
PID     : 4009                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_bufpool" From: "0" To: "1"
2009-02-02-10.42.50.203836+330 I7779A292          LEVEL: Event
PID     : 4012                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_lock" From: "0" To: "1"
2009-02-02-10.42.50.265351+330 I8072A292          LEVEL: Event
PID     : 4021                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_sort" From: "0" To: "1"
2009-02-02-10.42.50.329484+330 I8365A292          LEVEL: Event
PID     : 4022                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_stmt" From: "0" To: "1"
2009-02-02-10.42.50.390840+330 I8658A293          LEVEL: Event
PID     : 4023                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_table" From: "0" To: "1"
2009-02-02-10.42.50.514969+330 I8952A291          LEVEL: Event
PID     : 4025                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dft_mon_uow" From: "0" To: "1"
2009-02-02-10.42.50.576102+330 I9244A294          LEVEL: Event
PID     : 4026                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Mon_heap_sz" From: "90" To: "128"
2009-02-02-10.42.50.701560+330 I9539A296          LEVEL: Event
PID     : 4028                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Rqrioblk" From: "32767" To: "65000"
2009-02-02-10.42.50.761306+330 I9836A295          LEVEL: Event
PID     : 4029                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Svcename" From: "" To: "sapdb2SOP"
2009-02-02-10.42.50.826115+330 I10132A291         LEVEL: Event
PID     : 4030                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Aslheapsz" From: "15" To: "16"
2009-02-02-10.42.50.886807+330 I10424A290         LEVEL: Event
PID     : 4031                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Keepfenced" From: "1" To: "0"
2009-02-02-10.42.50.951758+330 I10715A294         LEVEL: Event
PID     : 4032                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Maxagents" From: "400" To: "1024"
2009-02-02-10.42.51.017562+330 I11010A295         LEVEL: Event
PID     : 4033                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Dftdbpath" From: "" To: "/db2/SOP"
2009-02-02-10.42.51.078023+330 I11306A328         LEVEL: Event
PID     : 4034                 TID : 1           PROC : db2flacc
INSTANCE: db2sop               NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Diagpath" From: "/db2/db2sop/sqllib/db2dump" To: "/db2/SOP/db2dump"
2009-02-10-15.23.47.236724+330 I11635A213         LEVEL: Error
PID     : 25606                TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-10-16.28.21.589909+330 I11849A213         LEVEL: Error
PID     : 6745                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-10-18.38.17.375623+330 I12063A213         LEVEL: Error
PID     : 16296                TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-10-19.53.31.036205+330 I12277A213         LEVEL: Error
PID     : 6044                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-11-23.37.20.156996+330 I12491A213         LEVEL: Error
PID     : 15427                TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-11-23.57.56.959811+330 I12705A213         LEVEL: Error
PID     : 4895                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-00.42.20.199428+330 I12919A213         LEVEL: Error
PID     : 5424                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-00.55.15.231691+330 I13133A213         LEVEL: Error
PID     : 4065                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-01.23.40.283293+330 I13347A213         LEVEL: Error
PID     : 4345                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-01.59.06.153079+330 I13561A213         LEVEL: Error
PID     : 4145                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-02.40.06.335045+330 I13775A213         LEVEL: Error
PID     : 4515                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-03.09.22.341443+330 I13989A213         LEVEL: Error
PID     : 4423                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
2009-02-12-03.31.31.201911+330 I14203A213         LEVEL: Error
PID     : 4135                 TID : 1
FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60
MESSAGE : ECF=0x90000390 Invalid process id
In R3trans.log
4 ETW000 [dev trc     ,00000]    (0.144) MSSQL: ODBC fastload on separate connection (note 1131805)
4 ETW000                                                                              46 0.514332
4 ETW000 [dev trc     ,00000] Supported features:                                   30 0.514362
4 ETW000 [dev trc     ,00000] ..retrieving configuration parameters                 29 0.514391
4 ETW000 [dev trc     ,00000] ..done                                              3613 0.518004
4 ETW000 [dev trc     ,00000] Running with UTF-8 Unicode                            30 0.518034
4 ETW000 [dev trc     ,00000] Running with CLI driver                           126609 0.644643
4 ETW000 [dev trc     ,00000] *** ERROR in DB6Connect[dbdb6.c, 1632] CON = 0 (BEGIN)
4 ETW000                                                                          180751 0.825394
4 ETW000 [dev trc     ,00000] &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL30081N A communication error has been detected. Communication
4 ETW000                                                                              57 0.825451
4 ETW000 [dev trc     ,00000] &+      protocol being used: "TCP/IP". Communication API being used: "SOCKETS". Location where the error was detected:
4 ETW000                                                                              49 0.825500
4 ETW000 [dev trc     ,00000] &+     "128.0.0.35". Communication function detecting the error: "connect". Protocol specific error code(s): "239", "*"
&+
4 ETW000                                                                              49 0.825978
4 ETW000 [dev trc     ,00000] *** ERROR in DB6Connect[dbdb6.c, 1632] (END)          30 0.826008
4 ETW000 [dbdb6.c     ,00000] *** ERROR => DbSlConnect to 'SOP' as 'sapsop' failed
4 ETW000                                                                             554 0.826562
2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'SOP'"
Please provide me the solution to solve the issue.
Thanks & Regards

Hi, Malte
I have given individual nodes address in db2nodes.cfg, as per your instruction I have run the db2 list database directory I have got the following output
System Database Directory
Number of entries in the directory = 1
atabase 1 entry:
Database alias                       = SOP
Database name                        = SOP
Local database directory             = /db2/SOP
Database release level               = b.00
Comment                              = SAP database SOP
Directory entry type                 = Indirect
Catalog database partition number    = 0
Alternate server hostname            =
Alternate server port number         =
=> db2 list node directory
=> SQL1027N The node directory cannot be found
Regards

Error in SAP Upgrade 4.6C to ECC 6.0 in CONFLICT_CHECK Phase

Hi All,
I am doing an SAP Upgrade frm SAP 4.6C SR2 to ECC 6.0 SR2. When it enters the CONFLICT_CHECK we are facing the following error. i am performing this on Production system. Your immediate help is highly appreciated.
#---- MASKING file CONFLCHK.LOG from E:\usr\sap\put\log
#---- TIME: 20091212095249
1 ETQ201XEntering upgrade-phase "CONFLICT_CHECK" ("20091212094722")
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '22', GwService = 'sapgw22'
4 ETQ399 Environment variables:
4 ETQ399   dbs_ora_schema=SAPR3
4 ETQ399   auth_shadow_upgrade=0
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
4 ETQ399 (trc) R3upExtendedInclusion: TRUE (default)
2 ETQ160 Starting conflict check
4 ETQ010 Date & Time: 20091212094722
4 ETQ230 Starting RFC Login to: System = "CPA", GwHost = "DERSHASKFI140", GwService = "sapgw22"
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SPDA_CONFLICT_CHECK" by RFC
2EETQ360 RFC of "spda_conflict_check" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key             : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message         :
2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ                    .
4 ETQ359 RFC Login to: System="CPA", Nr="22", GwHost="DERSHASKFI140", GwService="sapgw22"
4 ETQ232 RFC Login succeeded
2EETQ235 Call of function module "SPDA_CONFLICT_CHECK" by RFC failed (error-status "-2")
4 ETQ239 Logging off from SAP system
4 ETQ010 Date & Time: 20091212094903
4 ETQ010 Date & Time: 20091212094903
Hemanth

Hi,
> 2EETQ399 SQL error 1654 occurred when accessing table OCSCMPLOBJ
Have you checked tablespace have sufficient space ?
Thanks
Sunny        .

Installation of CRM 2007 in Windows with oracle and cluster environment

Dear Experts,
We are about to start the installation of CRM 2007 (ABAP+JAVA) with
Oracle 10g on Windows x64 in cluster environment. In the SAPINST dialog
box under High availability option, I could see installation options like ASCS
Instance, SCS Instance, First MSCS node, Database Instance, Additional
MSCS Node, Enqueue Replication Server, Central Instance and Dialog
Instance.
I have gone through the installation guide. I have below queries
regarding the same. Can you please clarify the same
1) Our requirement is we want to have an ACTIVE-ACTIVE cluster setup
with sap service running in Node A and Database running in Node B. Can
we have this setup in ABAP+JAVA setup
2) Also,in the SAPINST dialog box as said above except last two
(Central and Dialoge instance) as per standard installation guide are
to be installed in shared drives as per the requirement. But, central
and dialog are said to be installed locally on any one node in MSCS or
in separate server. As per my understanding Dialog instance will be
used for load balancing which we do not require now. Hence I feel this
is optional in our case. Where as Central Instance I am not able to
understand why this option is for? Is it mandatory to be installed or optional. If
so, when I installed it in one of the MSCS node the incase of failover
how does it effect the system. As per my understanding ASCS and SCS
comprise central instance.
Please clarify and thanks in advance.
Regards,
Sharath Babu M
+91-9003072891

I am following as per the standard installation guide.
Regards
Sharath

OPMN fails in cluster environment after the machie reboots.

Dear All:
Have you ever meet the following problem or have any suggestion for it? Thanks a lot.
There are machine A and B have been setup successfully in a cluster environment, everything is fine.
However, after the machine B reboots, the Oracle BI Server and Presentation Server in machine B could not start.
The error message for Oracle BI Server is:
[2011-06-02T10:40:34.000+00:00] [OracleBIServerComponent] [NOTIFICATION:1] [] [] [ecid: ] [tid: 1060] Server start up failed: [nQSError: 43079] Oracle BI Server could not start because locating or importing newly published repositories failed.
The error message for presentation server is:
[2011-06-02T18:40:24.000+08:00] [OBIPS] [ERROR:1] [] [saw.sawserver.initializesawserver] [ecid: ] [tid: ] Another instance of Oracle Business Intelligence is trying to upgrade/update/create the catalog located at \\?\UNC\10.91.61.158\BIEEShare\CATALOG\SampleAppLite\root. Retry after it finishes.[
The detail information is:
1)     Machine A and B both run Windows 2008 server 64bit.
2)     Machine A runs Admin Server+BI_Server1(managed server). Machine B is configured with “Scale out an existing installation” option and runs BI_Server2(managed server).
3)     BIEE 11.1.1.3
4)     In EM, the shared location of shared repository has been set to something like \\10.91.61.158\shared\RPD. The catalog path has been set to \\10.91.61.158\BIEEShare\CATALOG\SampleAppLite. Both path could be accessed by machine A and B.
5)     Before machine B reboots, everything is fine. All the servers could be started.
6)     After machine B reboots, the managed server BI_server2 could be started successfully. However, “opmnctl startall” would incur the above error message.
Any suggestion is welcome. Thanks a lot!

Hello,
Thanks for answering.
I am using OBIEE 11.1.1.5.0 enterprise software-only install scaleout existing Bi system option on HostMachine2. All services and coreapplication systems are running except coreapplication_obis1, coreapplication_obis2, coreapplication_obips1 and coreapplication_obips2 of bi_server2 on HostMachine2.
Here is my ClusterConfig.xml, as you can see all changes in this file is done by em and primary and secondary controller settings are already applied. The same file also exist in the same location on HostMachine2.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<Cluster xmlns="oracle.bi.cluster.services/config/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="oracle.bi.cluster.services/config/v1.1 ClusterConfig.xsd">
<ClusterProperties>
<ClusterEnabled>true</ClusterEnabled>
<ServerPollSeconds>5</ServerPollSeconds>
<ControllerPollSeconds>5</ControllerPollSeconds>
</ClusterProperties>
<NodeList>
<Node>
<NodeType>PrimaryController</NodeType>
<NodeId>instance1:coreapplication_obiccs1</NodeId>

<HostNameOrIP>HostMachine1</HostNameOrIP>
<ServicePort>9706</ServicePort>
<MonitorPort>9700</MonitorPort>
<ListenAddress>HostMachine1.localdomain.com</ListenAddress>
</Node>
<Node>
<NodeType>Server</NodeType>
<MasterServer>true</MasterServer>
<NodeId>instance1:coreapplication_obis1</NodeId>
<HostNameOrIP>HostMachine1.localdomain.com</HostNameOrIP>
<ServicePort>9703</ServicePort>
<MonitorPort>9701</MonitorPort>
</Node>
<Node>
<NodeType>Scheduler</NodeType>
<NodeId>instance1:coreapplication_obisch1</NodeId>
<HostNameOrIP>HostMachine1.localdomain.com</HostNameOrIP>
<ServicePort>9705</ServicePort>
<MonitorPort>9708</MonitorPort>
</Node>
<Node>

<NodeType>Server</NodeType>

<MasterServer>false</MasterServer>

<NodeId>instance1:coreapplication_obis2</NodeId>

<HostNameOrIP>HostMachine1.localdomain.com</HostNameOrIP>

<ServicePort>9702</ServicePort>

<MonitorPort>9709</MonitorPort>
</Node>
<Node>

<NodeType>Server</NodeType>

<MasterServer>false</MasterServer>

<NodeId>instance2:coreapplication_obis1</NodeId>

<HostNameOrIP>HostMachine2</HostNameOrIP>

<ServicePort>9761</ServicePort>

<MonitorPort>9762</MonitorPort>
</Node>
<Node>

<NodeType>Server</NodeType>

<MasterServer>false</MasterServer>

<NodeId>instance2:coreapplication_obis2</NodeId>

<HostNameOrIP>HostMachine2</HostNameOrIP>

<ServicePort>9763</ServicePort>

<MonitorPort>9764</MonitorPort>
</Node>
<Node>

<NodeType>SecondaryController</NodeType>

<NodeId>instance2:coreapplication_obiccs1</NodeId>

<HostNameOrIP>HostMachine2</HostNameOrIP>

<ServicePort>9765</ServicePort>

<MonitorPort>9766</MonitorPort>

<ListenAddress>HostMachine2</ListenAddress>
</Node>
<Node>

<NodeType>Scheduler</NodeType>

<NodeId>instance2:coreapplication_obisch1</NodeId>

<HostNameOrIP>HostMachine2</HostNameOrIP>

<ServicePort>9770</ServicePort>

<MonitorPort>9771</MonitorPort>
</Node>
</NodeList>
<SSLProperties>
<SSL>false</SSL>
<SSLCertificateFile/>
<SSLPrivateKeyFile/>
<SSLCACertificateFile/>
<SSLVerifyPeer>false</SSLVerifyPeer>
</SSLProperties>
</Cluster>

SAP Upgrade in Cluster Environment

Similar Messages

Maybe you are looking for