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

Similar Messages

Kernel Upgrade in MSCS cluster

Hi all,
I have to do Kernel Upgrade in MSCS environment.
Please suggest me how to do?
Regards,
shanker C

Hi Shanker,
Given below is the procedure to perform kernel upgrade in MSCS environment
Activities to be done at OS level
1. Stop all instances and take all the resource offline(including windows cluster service) in cluster administrator.
2. Unpack the archives to a working directory and take backup of usr\sap\<SAPSID>\SYS\exe\uc(nuc)\<Platform>:and replace all old files with the new one.
3. On all MSCS nodes, replace the SAP cluster dlls with those in NTCLUST.SAR
a) Copy ntcluster\saprc.dll %windir%\system32
b) Copy ntcluster\saprcex.dll %windir%\system32
4. On all MSCS nodes, replace the following dlls and exe in the
windir%\SapCluster folder with those in folder \usr\sap\<SAPSID>\SYS\exe\uc(nuc)\<Platform>:
sapevents.dll
sapntchk.exe
sapstartsrv.exe
sapxpg.exe
5. Bring cluster resources online and start the instances.
Hope this answer your question
Regards
Waseem

System Core Dumped after Oracle patch upgrade 9.2.0.6 to 9.2.0.8

Hi,
We are continously getting dumps on our BW Central instance server after we did an Oracle patch upgrade from 9.2.0.6 to 9.2.0.8.
Following is our system environment
SAP Release.............. "640"
Application server....... "abci"
Operating system......... "SunOS"
Release.................. "5.10"
Hardware type............ "sun4v"
Database server.......... "abdb"
Database type............ "ORACLE"
Database name............ "ABP"
Database owner........... "SAPABP"
SAP kernel............... "640"
Database version......... "OCI_920 "
Patch level.............. "175"
Following below is the Core Dump that is generated for any process chains that we schedule on our BW server
Runtime Errors         SYSTEM_CORE_DUMPED
Date and Time          14.04.2008 09:26:17
ShrtText
     Process terminated by signal 11.
What happened?
    The current ABAP program had to be terminated because the
    ABAP processor detected an internal system error.
    The current ABAP program "SAPMSSY2" had to be terminated because the ABAP
    processor discovered an invalid system state.
What can you do?
    Make a note of the actions and input which caused the error.
    To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
    termination messages, especially those beyond their normal deletion
    date.
Error analysis
    An SAP System process was terminated by an operating system signal.
    Possible reasons for this are:
    1. Internal SAP System error.
    2. Process was terminated externally (by the system administrator).
               Last error logged in SAP kernel
    Component............ "Taskhandler"
    Place................ "SAP-Server awci_ABP_00 on host awci (wp 5)"
    Version.............. 1
    Error code........... 11
    Error text........... "ThSigHandler: signal"
    Description.......... " "
    System call.......... " "
    Module............... "thxxhead.c"
    Line................. 9780
How to correct the error
    The SAP System work directory (e.g. /usr/sap/c11/D00/work ) often
    contains a file called 'core'.
    Save this file under another name.
    If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
    1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
    2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
    3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
    4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
Kindly help.
Regards
Sachin
Edited by: Sachin N on Apr 14, 2008 12:26 PM

No. If the environment would be wrong the system wouldn´t start up.
Core dumps are in 99 % of the cases program errors (in the SAP kernel or in an interface (libdbora*)), misaligend accesses of data etc.
If you encounter such an error have a look in the C-Stack. If you can´t see where the error is happening opening an OSS call. Most of those errors are fixed by installing the latest patches for the kernel and the database interface.
Markus

System Copy in MSCS environment

Hi all!
We are in the process of upgrading our R/3 4.7x200 system to ERP2005 unicode. The upgrade and unicode conversion of Dev and Test have been successful, and now Production is next. By the way, we are not doing a combined upgrade and unicode conversion. The difference is that Prod is in a MSCS environment, while the other to are Central systems.
I have a question about how to perform a system copy procedure in a MSCS environment. As part of the Unicode conversion where I have to uninstall SAP (source and target systems are to be on the same hardware), and install it again as a system copy. I am wondering about the steps, and sequence of steps that needs to be performed in order to get the installation identical to what it is today. One node contains the Central Instance and the second node contains the database instance with MS SQL 2005. Do you have any tips for me?
I have recieved some information saying that I can perform the system copy as a Distributed environment, installing the central instance on one host, and the database on the other. My concern is that this will not fullfill the requirements for a cluster environment, where one node (node A) can failover to the other (node B) and vice versa.
Can you please advise on what the best option is and steps are?
Any input is highly appreciated!
Best Regards,
Thomas

Of course:)
What I did was basically to follow the instructions provided in the ERP 2005 installation guide, chapter 7. This refers to MSCS installation steps. I also used the System Copy guide for ERP 2005, which referred heavily to the installation guide. It wasn't as hard as it seemed to in the first place.
Good luck to anyone in the same situation, and do not hesitate to ask questions if needed.
Regards,
Thomas

Repository connect issue after MDM Patch Upgrade

MDM Expert
We recently upgraded our MDM patch from SP06 5.5.63.73 to SP06 5.5.65.91
after patch upgrade we are not able to connect to repository.SAP is saying that we have wong NLS Character set.It should be 'UTF8' or 'AL32UTF8'
We checked and found that we do not have character set as per SAP Recommendation but everything was working fine before upgrading the patch.As per SAP in new Patch MDM is lokking for Unicode Character set
SAP is asking to create new DB Instance for MDM.
If we create new instance for MDM then how we are going to use our existing repository.Our environment is clustered environment and name of MDM DB instance is also mentioned in cluster.We have to use same Instance name.We are also using oracle failsafe
Creating new instance seems to be risky for Production environment.Currently we are applying the Patch in Sandbox Environment
has anyone of you faced this problem while upgrading MDM patch, if yes then how you resolve the issue
Please help
Thanks
Deelip

Solution provided by sAP

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.

Kernel Patch upgrade results into error

Recently, we upgraded our R/3 640 kernel from patch number 196 to 327. It went successful.
But now, the Sales and order team is having problem in saving the orders(VA02, VA01).
While saving Sales order, error pops up saying "dialog step number missing".
Kindly suggest.

Hi ppl,
The problem has been resolved.
As i said, problem wasnt with the upgrade, but came thereafter, functional team faced issues while switching between the windows.
Problem was with the Gui level, it needed to be upgraded too after the kernel patch upgrade.
Thanks a lot for putting your thoughts.
Thanks

10.2.0.2 Patch Upgrade issue

hi,
SAP was installed on 10.2.0.1 (SuSe Linux Ent 10 ) . now i am applying patch upgrade to 10.2.0.2. when i am doing patch the below problem was occured,
"Unable to create new central inventory at location /oracle/orainventory. A non empty inventory already exists at this location. Please select another location or clean the inventory at /oracle/orainventory."
please help me on this issue
Regards
Ramesh

Hai,
Please check the oraInst.loc file has the correct entry or not.
File oraInst.loc should have the entries similar to the below:
inventory_loc=/oracle/SID/oraInventory
inst_group=dba
Check the permissions of this file as well, atleast the file should have read access to others.
Also check the permissions of /oracle/SID/oraInventory, it should be owned by ora<sid> user and group dba.
Regards,
Yoganand.V
Edited by: Yoganand Vedagiri on Feb 23, 2009 12:05 PM

How to do patch upgradation in citrix server ?

Dear all,
How to do patch upgradation in citrix server (SAP B1 2005B PL41 to PL49) ?
Whether i also need to do same in db server ?
Jeyakanthan

Hi Jayakanthan,
Patch Upgrade is done on SAP Server only.After Completion of Patch 49 upgrade in SAP Server
then open SAP B1 in server machine it start to upgrade DB after completed DB Upgrade
In Citrix Server open the SAP B1 it start the upgrade process after completed
restart the citrix server.
There is no separate Patch instalation in citrix server.
in Citrix server SAP client only installed so you can just open the
SAP B1 in citrix server and other client machine also it automatically start to
upgrade.
*Close the thread if issue solved.
Regards
Jambulingam.P

Patch / Upgrade

Hello,
I was looking into patching/upgrading from 10.2.0.3 to a 10.2.0.5 verison.
Are the two zip files for 10.2.0.5 from http://www.oracle.com/technology/ "Patch Installers"
The same as Patches from Metalink ?
Please explain the difference.
Thanks..

Hello,
I found out they would be the same. I was looking for more of a general answer not specfic to a product like what is "Patch Installers"
The two zip files I want are for 10.2.0.5 from http://www.oracle.com/technology/software/products/oem/index.html "Patch Installers"
are the same as Patch 3731593 from Metalink.
I thought the patch would only be from Metalink.
Thanks..

Best Practice: SAPGUI Version and Patch Upgrades

Hello -
Does anyone have some thoughts/information on best practices relating to SAPGUI version and patch upgrades.
Obviously, sometimes upgrades are forced upon us (e.g. 7.10 for Vista) and in other cases it may just be considered "nice to have".
Either way - it always signifies regression test and deployment effort. How do we balance the benefit and cost?
Thanks, Steve

Hi Steve,
you're right for the first part, yes, we (usually) patch twice a year.
Now for the rest
An uninstall will only happen on release changes (6.20->6.40->7.10), i. e. about every 4-5 years as SAP releases them.
Patches are applied to the installation server and the setup on the client will only update changed program parts. For example, upgrading 6.40->7.10 took about 10 minutes (incl. uninstall), applying patch 1 less than 5 minutes.
I recommend, you read the "SAP Frontend Installation Guide - 7.10" which you find at SMP alias sapgui. Navigate to Media Library - Literature. It explains setup of the installation server (sounds like a big thing, but ain't much more than creating a share), creating packages, applying updates etc.
Peter
Points always appreciated

Backup error after kernel patch upgrade

Hi.
I have a backup problem after the kernel patch upgrade. I have SAP R3 4.6C on HPUX11.0 with an Oracle 8.17 database.
I have upgraded kernel patch from 1655 to 2337.
Afterward, I am getting following backup error:
BR280I Time stamp 2007-11-06 09.29.01
BR279E Return code from '/usr/sap/HAD/SYS/exe/run/backint -u HAD -f backup -i /oracle/HAD/sapbackup/.bdwnpztp.lst -t file_online -c': 2
BR232E 0 of 115 files saved by backup utility
BR280I Time stamp 2007-11-06 09.29.01
BR231E Backup utility call failed
Does anyone know how to correct this?
Thank you.

Hi Jun,
backint is a link file that is in SAP kernel directory which links to the backup client on the server.
eg:
lrwxrwxrwx 1 root other 32 Aug 13 2004 backint -> /usr/openv/netbackup/bin/backint
As part of kernel upgrade process, the kernel is backed up, mostly on the disk before upgrading. Check if this link exists and recreate it in the kernel directory, if no backup was done, compare it with other systems to get the details of the backint link.
Cheers,
Nisch

Delta links on applying patches/upgrade.

Hi,
I have a basic question. What happens on applying patch/upgrade to the delta linked copies, when the source objects have been updated/upgraded with new SAP changes.
Will the delta linked object properties get over written by new upgraded (or SAP patches) source objects.
I have made delta links of the SAP delivered WPC IView container objects and using them in the custom pages. Lets say on applying a patch or upgrade, the orginal source objects are changed. Will those changes undo my changes on target delta linked objects.

Hi,
Copying to your namespace is possible but by that you loose all the advantages in the delta-link.
What exactly are you copying Roles, iView, Pages everything?
Adding additional delta link layer between the roles and SAP content is a wise step but copying everything will only dupplicate content and will not allow you upgrade safty with SAP features.
Regards, Elisha
PCD Team Leader
SAP

Update Customized LKM after patch upgrade

We currently have over 100 interfaces that use a customized version of a default LKM,CKM and IKM. We are going to implement a patch upgrade over the weekend which includes new versions of the LKM,CKM and IKM. How do we apply the new versions to the 100 interfaces?
The customization that we had done was to modify the some of the options. When we receive a new version how do we apply the new KM with the customized options to all the interfaces?
Thank you in advance.

Best paractise is always to dulicate then modify the new KM, not to modify the original KMs. This allows you to deal with the issues which arise when new KMs are released which contain new functionality you'd like to get.
I suggest that your best approach is to import the new KMs, modify them with your changes, then export them. Next do an IMPORT REPLACE on your KMs with the modified version of the new ones. Now all you have to do is to re-generate the interfaces which use the KMs.

Adjustment Modifications after Patch upgrade?

Hello,
Is it possible that the Modifications Adjustments (done in SPAU and SPDD and occured due to SAP_BASIS and SAP_ABA patches) be carried out after the patches upgrade?
To be more clear, instead of Adjusting the Modifications while patch upgrade is in progress can i configure the patch upgrade in SPAM transaction someway that the Modification Adjustments is directly shown to the user upon their login after my patch upgrade?
Regards,
Vasu

Hi Vasu,
Yes you just need to transport the request to next system.
Than you don't need to redo the adjustment.
But some time due to incosystency between the system, you still get some object not adjusted after you apply the request, and for this you need to transport the object from your development or direct adjust.
After 12 days than when you change the object, SAP will ask you for the object key, and you need to request the key in SAP MarketPlace before you can change the object.
Regards,
Fendi Suyanto

Livecache patch upgrade in MSCS environment

Similar Messages

Maybe you are looking for