Patch strategy for ECC6 in SAP NW2004s environment

Hi Experts,
Our SAPNW04s landscape consists of ECC6, BI 7.0, EP7.0 , SRM, XI, Solution Manager systems. We are drafting patch upgrade strategy for the ECC6 system & have 2 options:
Option 1: Apply patches only in ECC6 & not in other components.
Option 2: Patch ECC6 together with other components like SRM, BI, EP etc.
Option 2 will make things complicated but for Option 1 below are the 2 concerns/questions raised:
1. Option 1 will lead to doing UAT twice for Business Processes which have a tight integration with ECC6, for ex. UAT for data extraction needs to be done after applying patches both in the ECC6 & the BI systems. This will lead to arrange for more user resources.
2. Due to the tight integration between ECC6 & other components applying patches alone in the ECC6 might lead to other systems like BI, EP,SRM, XI etc at a lower level & they might not be able to connect to ECC6 or work properly with ECC6.
Can somebody share how they are managing the ECC6 patches upgrade in a big NW2004s environment with other components present, are the ECC6 patches done standalone & other systems like EP, BI follow their own different time schedules for patching or ECC6, BI, EP are recommended to be done together.
Are there any best practices recommendations from SAP on the same?. Can somebody share the blueprint or any strategy document they are using.
Thanks,
Abhishek

Hi Abhishek,
For the reasons you outline in 2, it is recommended to patch entire business scenarios (i.e. business processess that are coupled integrated across systems) together. Rather than go into a full discussin here, I recommend you see my paper [How To Design a SAP NetWeaver - Based System Landscape |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50a9952d-15cc-2a10-84a9-fd9184f35366].
Best Regards,
Matt

Similar Messages

Patching strategy for Production environment

Hi all,
Can anyone share their patch strategy specially for production environment?? We have production environment and we are planning to patch our databases using PSU pacthes with no downtime. Our production environment has standby. We have one option that we can make standby to primary. Is there any other options that we can use??? Also we are not using Grid control.
Thanks

Hi there,
In 11gR2 onwards it is possible to patch without downtime using a physical standby database (converts to transient logical standby). Please look at the document below. There is a script on Metalink as well which makes this all much easier.
http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-transientlogicalrollingu-1-131927.pdf

Patching Strategy for CRS and ASM homes

I'm fairly new to RAC/ASM and haven't performed any patch set upgrades yet. Back in the simple days when I wanted to apply a patch set to a database, say from 10.2.0.4 to 10.2.0.5, I would create a brand new Oracle home ahead of time and apply the patch set to it. I'd name my homes like this:
/opt/oracle/product/10.2.0.4/db1
/opt/oracle/product/10.2.0.5/db1
During the maintenance window I would change /etc/oratab to point the database to the new 10.2.0.5 and complete the database upgrade scripts. The advantages of this strategy:
1 - Less risk installing software as nothing uses the new home yet. If something goes wrong in the install, no big deal. Research the problem and try again without being under the stress of a defined maintenance window.
2 - No need to backup old home for back-out purposes.
3 - Less time required for database to be down during actual patch window since Oracle Installer does not need to run.
Now with CRS and ASM, is there a way to pre-stage a new home for those, but not have them "active" to the node until later during the maintenance window?
For ASM, it seems like it would be possible to treat the same way as database and simply update ASM SID in /etc/oratab
+ASM1:/opt/oracle/product/10.2.0.5/asm1
but I'm not totally confident in that as I'm afraid the CRS home may already have references to the ASM home in the cluster registry.
For CRS, it seems like the home is pretty well hard-wired into the node startup scripts and installing a brand new CRS home will probably disrupt the running CRS home.
Any thoughts about this?

Hi,
user5448593 wrote:
I'm fairly new to RAC/ASM and haven't performed any patch set upgrades yet. Back in the simple days when I wanted to apply a patch set to a database, say from 10.2.0.4 to 10.2.0.5, I would create a brand new Oracle home ahead of time and apply the patch set to it.
Now with CRS and ASM, is there a way to pre-stage a new home for those, but not have them "active" to the node until later during the maintenance window?Although you have not mentioned the version you are actually on, it is a quite up-to-date question and dilemma.
Starting with 11.2 for Grid Infrastructure only "out-of-place" patchset upgrades are supported.
>
For ASM, it seems like it would be possible to treat the same way as database and simply update ASM SID in /etc/oratab
+ASM1:/opt/oracle/product/10.2.0.5/asm1
but I'm not totally confident in that as I'm afraid the CRS home may already have references to the ASM home in the cluster registry.
For CRS, it seems like the home is pretty well hard-wired into the node startup scripts and installing a brand new CRS home will probably disrupt the running CRS home.
Any thoughts about this?As of 11gR2 the ASM is part of the Grid Infrastructure, therefore it is running from the same home and not recommended to separate them. (although you can do that)
By the way, what is your upgrade path? It could be easier to answer your questions if we knew that as there has been a quite a few enhancements and changes in the upgrade/patching process from 10g to 11g. (even between 11gR1 and 11gR2)
Regards,
Jozsef

Java Patches download for ECC6.0

Hi
Currently i have ecc 6.0 with ABAP+JAVA Stack. My java stack is on SP18 and need to upgrade. On the same server we have ESS Portal and ADS.
Kindly suggest me where to download patches in SMP. Im bit confused with path.
Thanks
Regards
Prateesh K

Hi Prateesh,
You can download, from http://service.sap.com/swdc > SAP Support package stacks (left frame) > SAP ERP 6.0 (SAP ERP 2005) (in the right frame).
Select the appropriate components based on, the usage.
Or the best way is, if you a Solution manager in your landscape, log in to that, and use DSWP > Operations > Change Management > Maintenance Optimizer > Create New Maintenance Transaction > Select the appropriate system, and continue.
If will show the current level and you need to select the target level, then it will automatically give the components that you can add to your download basket and approve them.
Also, download the stack.xml file, which will make the component target SPS level calculated, in JSPM.
Hope this info helps,
with regards,
Rajesh

Patching Strategy - poll

We have been hotfix averse in our 5.3 environment and endeavor to do better in 6. While realizing the burden that testing and regression testing incurs on every one - not to mention the 'Oops, we didn't test for that' PRD incidents that happens from time to time, I was wondering if others could share their patching strategy for Tidal.
I would be interested to know:
Do you actively look at the monthly releases and do you ALWAYS apply the monthly released hotfixes?
If not always, how often do you routinely patch (not including critical hotfixes)
Does Tidal fall under some compliance guidelines that require you to be updated on patches?
How long does the new hotfix sit in DEV before you bless it for PRD? Do you have a formal regression...or any testing that users sign off on for each hotfix before it can be applied to PRD or do you just let it sit in DEV for a month or two and apply to PRD if no issues are reported? We have 15 or so teams that use Tidal so its a challenge since they use the product differently.
If things go awry in PRD, do you perform a backout, or do you engage support but not back out hotfix?
Do you automate any of your testing (ha!) - really wanting to get some basic testing criteria for patches - in addition to the info from the readme that you care about testing.
Do you bundle your hotfix with the DB and OS patches in one go, or do you deploy them separately?
We hadn't planned on patching our agents when we upgrade to 6 (too many moving parts). Any tips on how you handle agent patching - do you do it in one go or rollout a few at a time? Is it autmated?
Thanks again - this forum is really useful to to learn how other companies use, manage and maintain this tool. It is one of our most critical applications so we really thread lightly on any changes to PRD.

Do you actively look at the monthly releases and do you ALWAYS apply the monthly released hotfixes?
5.3.1 Yes we review the readme and decide on a case by case basis
We were bit by the change in quoted behavior
6.1 We will be applying patches more frequently but apply each one – 1 month lag
If not always, how often do you routinely patch (not including critical hotfixes)
5.3.1 We do not routinely patch (current prod rev 5.3.1.318)
6.1 – 1 month lag ( honestly I feel more comfortable now that they are publishing monthly)
Does Tidal fall under some compliance guidance that require you to be updated on patches?
Not for our organization we have business and change control but no software patching requirement
How long does the new hotfix sit in DEV before you bless it for PRD? Do you have a formal regression...or any testing that users sign off on for each hotfix before it can be applied to PRD or do you just let it sit in DEV for a month or two and apply to PRD if no issues are reported? We have 15 or so teams that use Tidal so its a challenge since they use the product differently.
No formal timetable for testing in DEV but we also then apply to UAT then to PRD. In general we run for several months in DEV 1 month in UAT. We time prod with a windows patch weekend. We also leverage a Vcloud/Wmware Lab environment and look at the install via a DEMO license... which we have found very useful
Generally our internal customers are either application support or developers who can pick up on root cause easier that regular users
If things go awry in PRD, do you perform a back out, or do you engage support but not back out hotfix?
It all depends on severity of impact, ability to reach support, and time to apply fix.
We wouldn’t be afraid to either back out or fix and move forward but would likely back out to “working” version
Do you automate any of your testing (ha!) - really wanting to get some basic testing criteria for patches - in addition to the info from the readme that you care about testing.
We have a series of jobs that test some basic functionality but it could always be expanding and improved. We insert them ad-hoc to test but plan on automating a "test suite" of jobs with more frequent patching
Do you bundle your hotfix with the DB and OS patches in on go, or do you deploy them separately?
We try to limit the changes where possible. From an O/S perspective we patch Prd every other month and dev every month… so we just time properly
Depending on Cisco patch we might run on a non PRD O/S patch weekend
We hadn't planned on patching our agents when we upgrade to 6 (too many moving parts). Any tips on how you handle agent patching - do you do it in one go or rollout a few at a time? Is it autmated?
I like you thinking.. As long as Agents are at a 6x compatible level I would recommend that as a follow up change after you are confirmed stable.
Typically we roll out all simultaneously, currently not automated but we are looking to automate for 6.1.x

Online SAP testing environment

Hello friends,
I am looking for an online SAP testing environment site where i can do my FI configuration practice or alternatively a site where i can get free IDES software download so I can prepare myself for the industry. If you have an idea about how to solve my problem please help me.
Regards
Tsitsi

Hi Srikrithi,
SAP Testing is all about test business process/functionality & outcome using manual/automation testing. For this I find knowledge of some Buniess Process/Functional Module must...but as you are alerady an ABAPer so must be aware of some of them. & Being ABAPer you will be better at White Box Testing. Do not take it as switching to testing & come back to ABAP dev or vice-versa; its just a matter of work responsibilities & your role in the organization. But yes...if you go for automation testing then must have knowledge of QTP or LoadRunner. Search more for term SAP TAO as well.
Hope this will help you to explore more.
Warm Regards,
N. Singh

Need patch ID for Linux 64-bit equiv to 10.2.0.4 patch 17 for Windows 32-bi

Need patch ID for Linux 64-bit equiv to 10.2.0.4 patch 17 for Windows 32-bit
Hello,
We are transporting a database from Windows 32-bit to Linux 64-bit. Version/Patch on the Windows machine is 10.2.0.4.0 (10g Release 2 Patch Set 3), interim patch 8258839.
How do I find the equivalent patch set for the Linux 64-bit environment? We need to have the Linux environment at the same patch level.
Thank you, Tim

AFAIK, the interim patch concept is only applicable to Windows. There is no Linux/Unix equivalent. See these MOS Docs
268895.1 - Oracle Database Server Patchset Information, Versions: 8.1.7 to 11.2.0
342443.1 - 10.2.0.x Oracle Database and Networking Patches for Microsoft Platforms
Pl open an SR to confirm.
HTH
Srini

Issue in SAP GUI 7.0 for ECC6 (ABAP Editor not working)

Dear SAP Team,
We have installed SAP ECC6.0 EHP4.We have installed SAP GUI 7.0 in our clients machine but in some machines the ABAP Editor i.e Tcode SE38 is not working properly.When our Client selects any transaction for editing the system gets HANG.
We have tried uninstalling & reinstalling the software & the patch but the problem still persists.The configuration of all our client machine are same & we work on Windows XP platform.Please help us in solving our issue as soon as possible.
Thanks & Regards,
Manoj Mhatre.

Dear Manoj
you mean the SAP Gui for windows 7.20 or 7.10?
Please install the latest Sapgui Patch 3 for the Sapgui 720, or the Sapgui
Patch 19 for the Sapgui 7.10.
As workaround, please use the OLD frontend editor.
Best regards,
Sven

What is SAP's strategy for XSI (Express Shipping Interface)?

We are investigating if we can use SAP XSI for parcel tracking with DHL. We like the idea of having an integrated tracking solution that we can call from SO, PO, delivery note and shipment. However, I found information on the internet related to XSI versus UPS telling me UPS is no longer supporting new implementations of SAP. Does somebody know why they stopped supporting XSI? See URL below for all details:
http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/vtrc-xsi-and-interface-into-ups-3265707
According to this discussion XSI is not the direction SAP is going with transportation in the future. Event Management is the solution for tracking. Their recommendation is to use XML API's from carriers instead like e.g. TrackIT from DHL? Does somebody know whether this information is reliable or not?
Does somebody have information about SAP's strategy for XSI ? Is it worthwhile spending time on configuring XSI for DHL tracking or does somebody have better or other options?
We are aiming for as less custom changes as possible.
kind regards,
Angelique Heutinck
IFF

Dear Angelique,
ProcessWeaver u2018Global Enterprise Centralized Shipping (ECS)u2019 solution certified by the SAP and DHL.
Advantages:
- No middleware required.
- SAP Certified
- Around 25 parcel carriers certified including FedEx, UPS and DHL.
- You can track shipments directly within SAP
We are happy to provide demo.
Best Regards,
Prasad
Edited by: ProcessWeaver Inc on May 29, 2010 4:17 PM

Implementation strategy for non sap sources

hai friends,
could anyone help with the
'implementation strategy for non sap sources'.

Hi,
Its the same as with R3 sources.Only difference is you'll have different underlying interfaces. Non SAP systems can either be flat files, ETL systems or legacy systems using ETL connection, Oracle or Java systems XML, etc.
But your stategy would remain the same only per your non sap source system, the transactions and the ways you configure your datasources would differ.
Cheers,
Kedar

R/3 Patch level for SAP BW 3.5

I all could you send me information about the minimum sap r/3 patch level for BW 3.5?
thanks a lot...

Hi,
You would find the info on http://service.sap.com/instguides based on the OS and the database.
Bye
Dinesh

ADS for SAP NW2004s Sneak Preview ABAP..

Hello folks,
Do we need ADS (Adobe Document Services) on SAP NW2004s Sneak Preview ABAP to run Interactive Adobe forms?
Regards,
Sarath.

I figured out we need ADS for SAP NW2004s Sneak Preview ABAP. Moreover we need a Java engine also.

How to make a SAP note compatibale for 4.6c which is designed for ECC6.0

Hi ABAP gurus
I have an OSS note :1093165 which is designed for ECC6.0 but i want to make that features available in 4.6c .how to do that ?any idea please suggest.

So, you want the features of ECC6 in 4.6c? That's quite interesting! You have not however mentioned few sample features. Perhaps you should talk to SAP for this.
Thanks

How to find out SAP J2EE Patch Level for 04s

Hi all
I want to find out SAP J2EE Patch Level for 2004s installation i tried to get information from SYSTEM INFORMATION link on WAS homepage but it gave only version :7.00 details and PATCH LEVEL was not mentioned .
I also tried to find out by looking into VERSION.TXT file for server & dispatcher in ....USR\SAP\J2E.....engine installation but again no details about PatchLevel was mentioned can anyone provide some information regarding what is the PatchLevel for WAS 7.0 , J2SE used is 1.4.2_09
Thanks in Advance !!
Asif

Thanks Kenny ,
But as you can see from version.txt file for Server0 it does not mention PatchLevel it is
blank
Specifies the version of the system
Cluster-Version: 7.00 PatchLevel
Build-On:Thursday, March 23, 2006 18:47 GMT
Perforce-Server:
Project-Dir:JKernel/645_VAL_REL
JKernel Change-List:102557
Build machine:SAPInternal
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
SP-Number: 07
Source-Dir: D:\make\engine\645_VAL_REL\builds\JKernel\645_VAL_REL\archive\dbg
i also checked version.txt for dispatcher it is as below
Specifies the version of the system
Cluster-Version: 7.00 PatchLevel
Build-On:Thursday, March 23, 2006 18:47 GMT
Perforce-Server:
Project-Dir:JKernel/645_VAL_REL
JKernel Change-List:102557
Build machine:SAPInternal
Build java version:1.3.1_12-b03 Sun Microsystems Inc.
SP-Number: 07
Source-Dir: D:\make\engine\645_VAL_REL\builds\JKernel\645_VAL_REL\archive\dbg
I tried this on different 2004s server but the Patch Level is not mentioned whereas for 2004
servers it is mentioned
so can u give some inference based on above descriptions about What should be SAP J2EE Patch
Level for the 2004s servers
Regards !!
Asif

How to find the latest SAP patch release for SRM and BI 7.0?

Hi experts,
I know how to check my sytem patch level in BI 7.0 and SRM. My question is how and where to check the latest patch level on SAP service market place.
Thanks in advance.
Sharat.

Hello,
Goto service.sap.com -> software download -> sap support packages -> Entry by application group -> Sap Frontend components -> SAP GUI for windows
In SAP Frontend components you have patches for BI add-on too.
Assign points if this helps
Regards,
Jorge Diogo

Patch strategy for ECC6 in SAP NW2004s environment

Similar Messages

Maybe you are looking for