Patch Upgrade Step

Hi Gurus,
We are doing an upgrade of system from patch level 52 to 53 in 4.6 C .
I have read some documents.Following them, I'm trying to clear SPAU list.First i'm clearing 'sap note corrections'
I have reset the obsolete notes(ones displayed with grey light).
Now I come to semi-automatic adjustment(Ones with yellow light).Here i'm confused what to do.
If i click on light,it prompts me to download the note or apply it.Shall I simply go ahead and apply that note ??
Please help me in that.

Problems when checking for files that are active.
The following files have active processes when there should be no activity.
Before you proceed, shutdown and stop all active processes.
1. /d01/xxxxx/EBSTEST/apps/tech_st/10.1.2/bin/wrap
2. /d01/xxxxx/EBSTEST/apps/tech_st/10.1.2/bin/proc
3. /d01/xxxxx/EBSTEST/apps/tech_st/10.1.2/bin/rmanUse fuser command to find the process ID and kill it manually -- http://linux.die.net/man/1/fuser
Or, issue "ps -ef | grep applmgr" assuming applmgr is the owner of the files and kill any active processes using "kill -0 <PID>".
Or, simply reboot the box and make sure none of the services is autostarted.
Thanks,
Hussein

Similar Messages

11i upgrade - Step: Apply latest product patches (required)

Hi,
I am in the process of upgrading 11.5.9 (DB 9.2.0.4) to 12.1.1 (DB 10.2.0.5).
As part of the upgrade steps in document titled *"Oracle® E-Business Suite Upgrade Guide Release 11i to 12.1.1 Part No. / E16342-04 / August 2010"*, I was directed to apply the latest product patche. Chapter 3, section 5.
I downloaded the latest copy of the patchsets.sh from Oracle and ran it with the following parameters:
patchsets.sh connect=apps/<apps_password> available=metalink
This tool generated a bunch of reports including one called "Report.txt" and "Report_R12.txt"
Which one of these patches am I supposed to download and apply to be able to continue with the upgrade?
An excerpt From "Report.txt":
=============================================================================
        Report Generated: Fri Sep 16 15:34:12 EDT 2011               Tool Version: 4.52
Patchsets List Updated: Sep 15 22:30
              Machine/OS: Linux xxxxxxxxxxxxxxxxxxxx 2.6.9-101.ELlargesmp #1 SMP Fri May 27 19:07:07 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
                  Domain:
         applptch Source: Patch.csv
   Version from APPLPTCH: 12.1.1
                Database: PROD
       Limited Report to: APPLFULL and APPLSHAR products
                APPLFULL: AK ALR AP AR AS AX AZ BNE CE CHV EC ECX EDR FA FND FRM FV GHR GL GMS HZ IBY ICX IGI IGW ITG JTF JTM PA PER PN PO PQH PSA PSB PSP RG SSP
                APPLSHAR: AD AMV ASO AU BEN BOM CRP CS CUA DT ENG FF INV MFG MRP ONT PAY QA QP SHT WIP XLA
         Pseudo Products: ADO AHL AME AML AMS AMW ASF ASG ASL ASN ASP AST BIC BIL BIM BIS BIV BIX BPA BSC CAC CCT CDR CLA CLE CLJ CLL CLN CN CSC CSD CSE CSF CSI CSK CSL CSM CSP CSR CSZ CTB CUG CZ DDD DDR DNA DOM DPP EAM EDW EGO ENI EWS FEM FII FLM FPA FTE FTP FUN FWK GCS GHG GMA GMD GME GMF GMI GML GMO GMP GR HCP HCT HRI HXT IA IBC IBE IBU IBW IEB IEC IEM IEO IES IEU IEX IGP IGR IGS IMC INL IPA IPM IRC ISC ITA ITM IZU JA JAI JE JG JL JMF JTA JTH JTO JTT JTY LNS MSC MSD MSE MSO MSR MST MTH MWA OAM OCM OE OIE OIR OKC OKE OKI OKL OKS OKX OPI OTA OWF OZF PFT PJB PJC PJF PJI PJL PJM PJR PJT PMI POA POM PON POS PQP PRP PV QOT QPR QRM RCI RLM RRS TXK UMX VEA WMS WPS WSH WSM XDO XDP XLE XNB XNP XTR ZPB ZX
              Written By: Oracle Support, SSANDREW
                 WARNING: DOWNLOAD CHANGING NOVEMBER 3rd, 2006
         Program Updates: ftp://ftp.oracle.com/support/outgoing/PATCHSET_COMPARE_TOOL
      Download Patchsets: Go to link below or click on Patches
     http://metalink.oracle.com/metalink/plsql/dis_download.startup
=============================================================================
Applied Patchsets that Match ARU:
FAMILY PACKS
Prod      Patchset             Bug     RELEASED Release Status      Distribution
=======================================================================================
atg_pf    R12.ATG_PF.A.1      5907545 07/04/15 23:44:46 Checkin Released     Not_Distributed
atg_pf    R12.ATG_PF.A.2      5917344 07/07/13 05:48:57 Checkin Released     Not_Distributed
atg_pf    R12.ATG_PF.A.3      6077669 07/10/14 21:48:17 Checkin Released     Not_Distributed
atg_pf    R12.ATG_PF.A        4461237 07/01/18 17:08:25 Checkin Released     Not_Distributed
atg_pf    R12.ATG_PF.A.4      6272680 08/01/13 09:10:12 Checkin Released     By_Metalink
atg_pf    R12.ATG_PF.B.1      7307198 09/04/07 22:45:29 Checkin Released     Not_Distributed
APPLIED PATCHSETS
Prod      Patchset             Bug     RELEASED Release Status      Distribution
=======================================================================================
ado       R12.ADO.B.1         7460276 09/04/07 22:19:25 Checkin Released     Not_Distributed
ado       R12.ADO.B           6867824 08/08/11 22:59:18 Checkin Released     Not_Distributed
ad        R12.AD.A.1          5905728 07/04/13 13:11:10 Checkin Released     Not_Distributed
ad        R12.AD.A.2          6014659 07/07/13 05:30:06 Checkin Released     Not_Distributed
ad        R12.AD.A.3          6272715 07/10/14 17:33:24 Checkin Released     Not_Distributed
ad        R12.AD.A            4502962 07/01/18 17:08:25 Checkin Released     By_Metalink
ad        R12.AD.A.4          6510214 08/01/13 07:38:00 Checkin Released     By_Metalink
The Most Recent Release Family Packs on Metalink(Not Included Above) are:
=======================================================================================
atg_pf    R12.ATG_PF.A.6      7237006 08/11/05 20:30:52 Checkin Released     By_Metalink
atg_pf    R12.ATG_PF.B.2      7651091 09/12/16 08:03:30 Checkin Released     By_Metalink
atg_pf    R12.ATG_PF.B.3      8919491 10/07/08 01:40:33 Checkin Released     By_Metalink
cc_pf     R12.CC_PF.A.6       7291073 08/11/06 03:57:36 Checkin Released     By_Metalink
cc_pf     R12.CC_PF.B.2       8522000 09/12/17 01:08:48 Checkin Released     By_Metalink
The Most Recent Release Patchsets on Metalink(Not Included Above) are:
=======================================================================================
ad        R12.AD.A.6          7305220 08/11/05 11:14:22 Checkin Released     By_Metalink
ad        R12.AD.B.2          8502056 09/12/16 06:44:40 Checkin Released     By_Metalink
ad        R12.AD.B.3          9239089 10/07/07 14:22:15 Checkin Released     By_Metalink
cdr       R12.CDR.A          10161040 11/05/11 08:39:23 Checkin Released     By_Metalink
cla       R12.CLA.B           8506229 09/06/30 23:13:11 Checkin Released     By_Metalink
Base Patchset List for 12.1.1 included below:
=============================================================================
7461070 - R12.AD.B.1 ad 10-APR-09 Checkin Released By_Metalink
6665350 - R12.AD.B ad 13-AUG-08 Checkin Released Not_Distributed
7458155 - R12.AD.B.1 ad 08-APR-09 Checkin Released Not_Distributed Thanks,
Sinan

Hi,
In your above output it will be
The Most Recent Release Patchsets on Metalink(Not Included Above) are:
=======================================================================================
ad        R12.AD.A.6          7305220 08/11/05 11:14:22 Checkin Released     By_Metalink
ad        R12.AD.B.2          8502056 09/12/16 06:44:40 Checkin Released     By_Metalink
ad        R12.AD.B.3          9239089 10/07/07 14:22:15 Checkin Released     By_Metalink
cdr       R12.CDR.A          10161040 11/05/11 08:39:23 Checkin Released     By_Metalink
cla       R12.CLA.B           8506229 09/06/30 23:13:11 Checkin Released     By_Metalink
Thanks

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

Upgrade steps from 10.1.2.0.2 to 10.1.4.0.

Suggest the upgrade steps from 10.1.2.0.2 to 10.1.4.0.1.
IS there any patch need to be apply for this upgrade or we need to do new installation for it.
Platform is AIX
Thanks in advance.

Refer doc below:
http://docs.oracle.com/cd/B28196_01/upgrade.1014/b28235/im_upgrade_1014.htm#BABBAHGJ
regards,
GP

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

Production and standby upgrade steps..

Can anybody tell me steps for applying patch and upgrade steps of production and standby database.
I have applied patch and upgraded test database, Now I want to apply it on production & standby database.
I checked the readme its says review document 278641.1
Please, Can any body tell me steps, I will appreciate for this.
Regards.

below links may help you
http://ayyudba.blogspot.com/2007/12/applying-patch-sets-interim-patches.html
http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/upgrades.htm#CHDBJAGG
Regards,
Pavan
http://pavandba.wordpress.com

MW R12 - key upgrade steps clarification

OS: RHEL4 x86
DB: 11.2.0.3
EBS Upgrade: 11.5.10.2 -> R12.1.1
MW: 2.20
<-> Process Step: Upg to Rel 12.1.1
<---> Product Family: Perform the Upgrade
<-----> Task: Apply Preinstall Patches
<------->Step 1-Check for critical pre-upgrade patches for Financials
I am on my 2nd upgrade. With the first upgrade I had lots of problems with this step since it refers to an MOS note that has lots of information and refers to other MOS notes and it isn't clear what steps in those notes is duplicated within the MW steps.
The first time I did some things in the wrong order since there was no clear direction between the MW steps and all of the notes.
Is there anything that can help clarify how to correctly proceed through this task and the next task, Perform the Upgrade, which are so critical?
Thanks!

It would be really nice to have the exact steps spelled out in detail since this is too crucial to have it be vague and not well understood.
Here's how the MW explains it.
- Process Step: Upg to Rel 12.1.1
--- Product Family: Perform the Upgrade
1) Apply pre-install patches
----- Task: Apply Preinstall Patches
-------- Step 1-Check for critical pre-upgrade patches for Financials (Required)
I think that I understand this section except that I don't know whether patch 7303029 should be applied in this step or not.
2) Apply DBA CUP and related patches
----- Task: Perform the Upgrade
-------- Step 9: Apply DBA CUP and related patches
This is basic and understood.
3) Step 9.1:Apply patch 7303029
Here's what the MW says for the "setup" section:
"This step will download patch 7303029. It will also verify that the u67780700.drv driver is in the correct location and ready to be merged."
Here's what it says for the "execute" section:
cd $AU_TOP/patch/115/driver
admrgpch -d . -preinstall -master u6678700.drv
Neither of these steps actually applies patch 7303029 in pre-install mode but I am under the impression that this needed to be done at some point.
So, please provide the exact steps needed to get this done correctly.
Thanks

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

Category 3 Upgrade Steps for Rel 11i

Upgrading Oracle Applications Rel 11i manual page 4-2 lists three upgrade steps for Oracle Common Modules.
Step 1: Delete all AK data for Production 16 Global Demo databases (conditionally required)
Step 2: Check for invalid AK data in non-Global Demo databases (condionally required)
Step 3: Fix invalid data in non-Global Demo databases (conditionally required)
My Questions:
1. What is AK data?
2. What is the difference between a Global Demo database and a non-Global Demo database?
3. Does the AutoUpgrade utility migrate the data from the Global Demo and non-Global Demo databases to the Vision database?
null

I do not have any experience with standbys, but pl see if these MOS Docs can help
How To Upgrade A Primary Database And A Physical Standby To Oracle10gR2 (10.2)          (Doc ID 407040.1)
Oracle11g Data Guard: Database Rolling Upgrade Shell Script          (Doc ID 949322.1)
Applying Patch Sets / Interim Patches with Physical Standby Database in Place          (Doc ID 187242.1)
Is it possible to use different RDBMS-releases on primary/standby within a Dataguard Configuration?          (Doc ID 1294585.1)
HTH
Srini

Patch upgrade on IDM

Dear All,
I've been looking for a couple of days to properly patch my IDM systems.
At the moment we are running on 7.20 SP9 p0 and I would like to apply the IDENT. CENTER DESIGNTIME 7.2 patch 6.
However till now I never have found any documentation or guide to properly patch IDM.
We already applied a few patches when we were running 7.20 SP8 but I would like to verify if the way we are using is the correct one.
Has anyone ever seen this kind of doc ?
Thx,
Laurent

Hello Laurent,
You can do so but that doesnt make any difference if you were using Copy of SAP Provisioning framework.
By chance if you have made changes in your SAP Standard provisioning framework then I would recommmend to copy it before upgrading so you need not to do export import of your old framework and continue using with new updated scripts.
In case you want to perform Patch upgrade, then below are the steps I used to follow :
1.Make sure the system is backed up based on your current backup procedures
2.Stop all dispatchers and event agents
3.Uninstall the old DESIGNTIME and RUNTIME components (Not always required to uninstall, you can simple install the latest component and those should upgrade)
4.From the new version folder locate the database folder and select your database type (SQLServer/Oracle/DB2
5.Run the appropriate upgrade script (check the Database specific PDF file for
information on customization and detailed procedure) You'll probably need to engage your DBAs on this as well.
6.Install the new DESIGNTIME and RUNTIME components
7.Verify the new version is installed through the MMC Console (you should notice the change in version on the splash screen and then when you go into look at the ID Store
8.Restart your dispatchers and event agents
Regards
Deepak Gupta

XSS patch upgrade

Hi All,
We are planning to upgrade XSS patch , could you please let me know initial step .
How should i need to start what are the prerequisite need to take care .
Thanks
Rashi
Edited by: Rashi on May 20, 2010 9:51 AM

Hi All,
Thanks for the support.
I have successfully done the patch upgrade in dev portal.
I am facing the issue in custom WD application in QA portal system, in dev portal the application is working fine and after transporting the objects into QA portal ,while on preview the iview its giving me error : "Failed in WD JNDI lookup ".
I have tested the WD application from Web dynpro console and its working fine , even i have created iview in QA portal and its working fine but while transporting the iview from DEV to QA Portal is not working . Can any one help me on that .
Details error :
com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name home~eth_dis
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
    at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
    at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
    at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:442)
    ... 40 more

ASU-process POST Upgrade Step on SQL database

Hi All,
To check this message in the right format kindly click on reply first then click on quote original icon ("").
I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
IS-OIL Application Test 600                                                 Optional
KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
CGPL: Entries are blank after upgrade                                                Obligatory
Error handling of task group execution                                Optional
Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Convert customizing for warehouse funds ctr scenarios     Optional
Various problems classification commitment items (class type     Obligatory
Unauthorized error messages udring fiscal year change/reassi     Obligatory
RFFMUDX1 migrates incomplete budgeting tables                          Obligatory
Non-7bit-ASCII character used for BCS key figures             Obligatory
Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory
BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory
BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory
Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory
Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
Activating VMC for the Internet Pricing and Configurator     Obligatory
Customer specific BSEG-fields not transferred                  Optional
Conversion of report headers in drilldown-reporting            Optional                                   600
IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
Conversion of CO-Total-Tables                                              Obligatory     46C                      500
Conversion of CO-line-item table COEP                                Obligatory     46C                       600
New General Ledger, problems in CO-documents                 Obligatory                               500
No receivers found in allocations                                          Obligatory     46C                        470
Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
Migration of process parameters in recipe management     Optional     110                        600
FAQ new depreciation calculation                                        Optional                                600
Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
Reloading Table T512W                                                        Optional
Converting Short Texts                                                         Obligatory
Migrating Data                                                                         Optional     4.7
Activating SAP ECC Extensions                                          Optional
I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
Please suggest me, how to proceed and what to do. please guide if i skip this step now and later on I apply latest SP than still I need to do all this.
Regards
Vinay

Hi All,
I also faced a similar issue during upgrade. Some useful findings.
1. Only super user can access this /n/ASU/START
2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
4. Execute all the checks /n/ASU/UPGRADE
5. This surely can be skipped, but not advisable.
regards,
Amit

Upgrade step ASU-process post upgrade step

Hi All,
To check this message in the right format kindly click on reply first then click on quote original icon ("").
I am performing an upgrade from R/3 4.7 to ERP 6.0 SR3, while doing upgrade sapup asking me To perform the manual application specific post upgrade step.
This phase says to run ASU toolbox by using tx /n/asu/upgrade. when i run this tx is show the below list of steps to be performed with showing severity level of some as optional and many as obligatory.
Task List                                                                                Severity     SAP R/3 release frm     SAP R/3 release to
IS-OIL Application Test 600                                                 Optional
KP06xx: Termination SYNTAX_ERROR                                                 Obligatory     470                           500
CGPL: Entries are blank after upgrade                                                Obligatory
Error handling of task group execution                                Optional
Mobile device cannot confirm TO after release upgrade     Obligatory     470                         600
Mobile device doesn't find transfer orders after upgrade     Obligatory     470                          600
Grantee Management - Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Convert customizing for warehouse funds ctr scenarios     Optional
Various problems classification commitment items (class type     Obligatory
Unauthorized error messages udring fiscal year change/reassi     Obligatory
RFFMUDX1 migrates incomplete budgeting tables                          Obligatory
Non-7bit-ASCII character used for BCS key figures             Obligatory
Changes in TKEDR for /ISDFPS/RFFMDISTDERIVALE          Obligatory
BCS - Tool for Deleting Obsolete Derivation Strategies     Obligatory
BCS Syntax Error on Upgrade from EA-PS 2.00 to ECC 600     Obligatory
Migration to ERP 6.0 (EA-PS 6.00)                                         Obligatory
Migration EA-PS 2.00 to ERP 5.0 (EA-PS 5.00)                      Obligatory
Missing initialization of new fields in table ANLZ                  Obligatory     46C                       470
Activating VMC for the Internet Pricing and Configurator     Obligatory
Customer specific BSEG-fields not transferred                  Optional
Conversion of report headers in drilldown-reporting            Optional                                   600
IBase: Upgrade to Release 4.6C and higher                         Optional     46C                         600
ZSAPRCKML_COGS: Upgrade to release 4.7 or higher     Optional     46C                      470
Conversion of CO-Total-Tables                                              Obligatory     46C                      500
Conversion of CO-line-item table COEP                                Obligatory     46C                       600
New General Ledger, problems in CO-documents                 Obligatory                               500
No receivers found in allocations                                          Obligatory     46C                        470
Conversion Of New Process Parameter Long Texts For Search     Optional     110                       600
Migration of process parameters in recipe management     Optional     110                        600
FAQ new depreciation calculation                                        Optional                                600
Upgrading to SAP R/3 47x200 and SAP ECC 500 with RMGMT     Obligatory     100                       500
Reloading Table T512W                                                        Optional
Converting Short Texts                                                         Obligatory
Migrating Data                                                                         Optional     4.7
Activating SAP ECC Extensions                                          Optional
I am not sure about which steps I have to perform, I am a bit confused.. because some are optional and some are not relevant to my release (as target or source release is different from mine). and also few things are not applied in my envirnoment hence those steps are also not relevant.
Please suggest me, how to proceed and what to do. please guide if i skip this step now and later on I apply latest SP than still I need to do all this.
Regards
Vinay
Edited by: Vinay Paul on Sep 11, 2009 10:11 PM

Hi All,
I also faced a similar issue during upgrade. Some useful findings.
1. Only super user can access this /n/ASU/START
2. All the obligatory executable tasks are automatically performed by the system automatically during upgrade.      SAPADM. Only errors (if any) are to be corrected.
3. Some of the tasks are only to go through some SAP notes as a precaution before upgrade.
4. Execute all the checks /n/ASU/UPGRADE
5. This surely can be skipped, but not advisable.
regards,
Amit

Upgrade steps Details for 9.2.0.8 to 11.2.0.3 Database

Support,
We have one requirement from our client like "Upgrade the Database from 9.2.0.8 to 11.2.0.3". They are asking only the DB upgrade except Application.
Our Current Database is running in Solaris OS and DB is an 9.2.0.8 and Application is an 11.5.10.2.
I am going to follow the below documents for the Database Upgrade process using DBUA for First Iteration,
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0.3) (Doc ID 1585577.1)
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
In the above documents they mentioned the steps related to the 11g new home installation and upgrade process but before starting the process what are all the things i have to check it in my current Database and Applications.
Because i have clear idea on what we have to do in the new Oracle Home 11g and the Upgrade process but still have some confusion on the Pre-Upgrade Steps in current database.
Kindly suggest me what are the details i have to collect and check in my Current Database or provide any proper Oracle documents for the Database Pre-Upgrade Process.
Thanks in advance,
Vijay.

Vijay,
We would suggest you advice your customer to upgrade to 11.2.0.4 instead on 11.2.0.3
Interoperability Notes Oracle EBS 11i with Oracle Database 11gR2 (11.2.0) (Doc ID 881505.1)
https://blogs.oracle.com/stevenChan/entry/11_2_0_4_database
Preparing to Upgrade Oracle Database can be found at http://docs.oracle.com/cd/E11882_01/server.112/e23633/toc.htm
You would also need to refer to:
How To Get The Proper Environment Set To Run Adbldxml.pl When Upgrading To 11g/11gR2? (Doc ID 1310854.1)
11i: ad_parallel_compile: Ora-01031: Insufficient Privileges in adadmin / re-create grants and synonyms for APPS schema after upgrade from 10gR2 to 11gR2 (Doc ID 1148264.1)
Note: Please note that we have a dedicated forum for EBS questions -- https://forums.oracle.com/community/developer/english/e-business_suite
Thanks,
Hussein

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

Patch Upgrade Step

Similar Messages

Maybe you are looking for