SLA Pre-Upgrade program - Post steps

Dear All,
We upgrade our oracle applications to R12.1.3 from 11.5.10.2. Before upgrade, we applied the patch patch 5233248 and ran the concurrent program with the below values
Migrate all sets of books: Yes
Start Date: “01/01/1976”: Jan-76
End Date : (Left Blank)
The above concurrent in 11i insance took only 1 minute. Is this normal ?. There are many steps mentioned in the document R12.0 and R12.1: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch [ID 604893.1] .
Since I already mentioned to upgrade all GL during the upgrade process itself by mentioning the above parameters in the concurrent program. Do I have to still do anything on this regard after the upgrade
Please advise

936074 wrote:
Thanks Hussein. the pre upgrade program ran only for 1 minute. is this normal ?It should take more time. Please query GL_PERIOD_STATUSES table to verify.
Thanks,
Hussein

Similar Messages

  • SLA Pre- upgrade programs and process and SLA Post upgrade

    Hi Guys
    Can anybody please let me know what are the SLA Pre- upgrade programs and process we have to run and SLA Post upgrade process and programs.
    Thanks
    Ajeesh

    Pl post details of OS and EBS versions. Pl see if MOS Doc 604893.1 (R12: FAQ for the SLA Upgrade: SLA Pre-Upgrade, Post-Upgrade, and Hot Patch) can help
    HTH
    Srini

  • Record Count deviation in SLA pre-upgrade

    Hi Everyone
    We have applied SLA pre-upgrade patch for data migration from 11.5.10.2 to 12.1.3.
    Below is the record count we got it after applying SLA pre-upgrade patch in 11.5.10.
    Record count was taken it from “GL_PERIOD_STATUSES” Table.
    154620 with MIGRATION_STATUS_CODE   is   "P"
    123546 with MIGRATION_STATUS_CODE   is “NULL”
    Below is the count, after upgraded it into 11.5.10 to 12.1.3
    125075 with MIGRATION_STATUS_CODE   is   "U"
    153091 with MIGRATION_STATUS_CODE   is “NULL”
    Just let me know, why this much record count deviation happened   and is this right move to go further with this deviation.
    Thanks,
    prasatH.

    please see this
    R12 SLA Upgrade: Check that the SLA Pre-Upgrade Completed Successfully [ID 747216.1]
    NOTE:604893.1 - R12 SLA: FAQ for the R12 SLA Pre-Upgrade Process
    for your count difference please log an SR with oracle
    AppsMAstI
    shairng is Caring

  • What is the Difference  Between the  Pre-Upgrade and Post-upgrade in UMT in SAP BO

    Could anyone give me details.

    UMT is used to upgrade and migrate from older version to newer version.
    There is no pre or post migration terms used for UMT.
    Check the guide for more information.

  • I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes:Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufac

    I am trying to update my iTunes to 10.5.1 so that I can upgrade my 3GS phone but am getting the following error message when trying to install the itunes: Install step failed: Run pre upgrade script for apple mobile device support. Contact software manufacturer for assistance. I am on a MacBook pro running 10.5.8 OS. Has anyone seen this before and how can I get it resolved.
    Thanks for your help in advance....

    Did you ever figure out the problem? "Contact Software Manufacturer"?? That sounds ominous... I've got the same issue and I'm pretty durn aggravated right about now....
    Thanks!

  • 11i Upgrade - Projects Pre-Upgrade steps

    We are upgrading from 10.7SC to 11i (11.5.2) and in running several of the Category 2 pre-upgrade steps, we have found that only really old projects show up as exceptions that should be "fixed" prior to the upgrade.
    These projects are now closed and the revenue/invoices etc. are for prior fiscal years. We will probably get accounting errors (from flexfield/acct combinations that have been disabled) if we try to process the old transactions. We are also not sure that we want to write revenue events or create changes for fiscal years already closed.
    Has anyone else seen this? How did you handle it -- did you reopen projects, re-enable accounts and process the exceptions noted by the scripts? Will upgrade FAIL because of the presence of these exceptions?
    Any input you can provide would be helpful.
    Thanks in advance,
    Maria
    null

    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

  • Pre and post steps of client copy

    Hi,
    There are some client copy official guide?
    I was reading the help.sap.com, but in this guide not appears the pre- and post- steps of the client copy.
    More thanks

    >>If i  use the copy profile SAP_APPL, this steps will not be necessay,no? The user master data from target system will be maintained.
    Yes. You are right. This Profile will not over right the User Master Record. It is given on the document.
    http://help.sap.com/saphelp_nw04/helpdata/en/99/0a2a887e2511d2a6250000e82deaaa/content.htm
    Regards,
    Subhash
    Edited by: Subhash.Chandra on Jun 3, 2011 3:18 PM

  • Pre-Upgrade functional steps

    I need to know the pre-upgrade functional steps in SCM modules. Can you refer a document or SOP

    Attiq wrote:
    Thank you hussain i have the same document already but it does not have detailed FUNCTIONAL steps for Financials, SCM and projectsIt is covered in the same doc under "Preparing for the Upgrade" section.
    Thanks,
    Hussein

  • Physical movement of SAP Servers ( Procedure,Odds n Cons, Pre/Post Steps )

    Physical movement of SAP Server and Pre,Post steps ?
    Hello Experts,
    Need your help here..  Our Data Center is moving to Different Place  , hence IM team proposed Physical movement of SAP Server to New Location.
    In our Landscape we have SRM 4.0, XI 3.0 & BW 3.5 , ITS 620 and Requisites Servers available . As these are out of  SAP support we don't have expert for ITS and Requisite Server installation and configutaiton.
    Please  please  tell me Will this process work ? if yes then what are odds n cons in this procedure , Pre and Post Steps need to perform.
    Please help me as early as possible as we need to take decision ASAP.
    Thanks and Regards,
    Raja.
    Net-weaver Consultant.

    Hi Raja,
    You need to take care of following
    1) Ensure that IP address and hostname are retained in the new DC. If IP is changing you need to take a note of all the RFC and JCO connections where IP is used and replace them with hostname.
    2) For ITS you can re-install and re-configure. It is not a big task.
       Make a note which all places ITS is configured.
    3) You need to have full offline backup of the system before movement.
    4) You need to plan for some System integration testing post movement to ensure things are working post DC migration.
    Some useful information can also be found in http://christian.bergeron.voila.net/DC_Guide/Data_Migration_Methodology_for_SAP_V01a.doc
    Hope this helps.
    Regards,
    Deepak Kori

  • What are  Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.

    BW on HANA :  Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.
    We are trying to copy database from SAP BW7.0 to SAP BW on HANA 7.4 SPS6 so we are in search for list of steps or activities during database copy both pre and post steps.
    Along with the above we are in search of Pre and post migration steps ones database is transferred successfully from oracle to HANA on 7.4 SPS6.
    Kindly help us in getting the exact course of action as requested.
    Thanks and Regards,
    Lavina Joshi

    Hi Lavina,
    try this link for starters: Upgrade and Migration - BW on HANA | SAP HANA
    Points to remember are:
    Preparation:
         -- Hardware Sizing
         -- Preparation of Data Centres
         -- HANA Hardware preparation
         -- System Landscape Readiness (upgrade software downloads, system readiness checks, etc)
         -- House Keeping activities on BW system (data clean up, etc)
    Post Installation:
         -- Sanity checks / Preparation and License checks
         -- JAVA Configurations
         -- Infoprovider conversions 
    Overall Stages are described below:
    # Environmental setup (HANA box)
         -- Initial system checks and Building Activities (system copy, Appln server setups, etc)
    # System readiness
                   - ZBW_HANA_COCKPIT Tool
                   - ZBW_HANA_CHECKLIST Tool
                   - ZBW_ABAP_ANALYZER Tool
                   - ZBW_TRANSFORM_FINDER Tool
                   - SIZING Report
                   - System Clean up Activities
                   - Impact of 7.4 on source system checks
                   - Java Upgrade for portal
    # DMO Stages
                   - Preparation & Pre Migration checks
                   - Execution / Migration
                   - Post Migration Activities
    # Testing Phase
                   - Source system checks/Activities
                   - System and Integration Testing
                   - End to End Testing
                   - Performance testing
                   - Reports
                   - BO reports / Interfaces
    Do let me know if you require any further information.
    Regards,
    Naren

  • Your Windows 7 upgrade program failure

    TO Lenovo, Microsoft, Mentor Media;
        You FAILED!
        Your Windows 7 upgrade program has FAILED badly. I bought a Lenovo desktop PC a couple of months ago on the PROMISE that I would receive a FREE Windows 7 upgrade. I have found that it is impossible to ascertain the status of the order or shipment.
       YOU set certain EXPECTATIONS that YOU failed to live up to. YOU could help alleviate this problem by COMMUNICATING with your customers via an effective ONLINE mechanism. YOU have FAILED to do that.
        I would suggest that you watch these advertisements to help remind you of what it is to be a PC and that your competitors seem to crave my business more than you.
    http://movies.apple.com/media/us/mac/getamac/2009/apple-mvp-broken_promises-us-20091023_480x272.mov
    http://movies.apple.com/media/us/mac/getamac/2009/apple-mvp-teeter_tottering-us-20091023_480x272.mov

    I think you are being a little harsh here. How exactly has lenovo failed you? Have you submitted an upgrade request? Have you tried to call lenovo support about the issue? The Upgrade process seemed pretty clear to me from the home page. Perhaps you could provide more details on what happened in your situation, instead of flaming lenovo. I am sure that someone here can help you get your upgrade sorted out.
    Perhaps you can check out this post. It gives you the steps required to check on your order status
    -c
    edit: included new link

  • Pre Upgrade Project details Required

    Hi Experts,
    Could anyone please explain in detail with sufficient links/materials as to what kind of a role does an Abapper Play in Pre Upgrade Project.
    What kind of Problems one can face and solutions to it if possible.
    Thanks in Advance.
    Regards
    Ullas

    Hi Ullas,
    please check this link
    abaper role in Upgradation project
    SAP Upgrade project
    Regarding the Steps involved in Upgrade Project
    First it will be to find objects whcih are impacted by upgrade. Now most of the solution providers have tools to do this work automatically with less human involvement. These tools give you a list of custom developments that will be impacted by upgrade which need correction in higher version. Each object in the list will be distributed to a person in team for fix. It is the responsibity of the Abaper to find out the error and fix the error in a given program and make it error free. This is checked by testing the object after the correction is completed. For exapmle a screen number has changed in higher version for a particular transaction. This implies a correction to all custom programs where this screen is used in BDC. Another example may be an obsolete function module which is not available in higher version and it is the responsibility of Abaper to find out suitable replacement for this.
    But prior to this activity there is one more activity. If there are any changes to standard SAP developments like user exits or changes to standard code or changes to data dictionary, then they will not be reflected automatically after upgrade. There are transaction SPAU for workbench objects and SPDD for data dictionary objects. Abaper has to analyse the changed done to standard programs and dictionary objects and has to decide whther these are required in higher version. If they are required then correct them through these transaction codes.
    There is a document given by SAP on roles played by different people in an upgrade project. I suggest you to read that.
    Best regards,
    raam

  • Upgrade defaults checking step with no web acces

    Hi
    We are moving over our servers between datacenters along with a Peoplesoft Upgrade, Our present peoplesoft environment is on tools 8.47.11 which cannot be brought up in web on the new x64 servers. Due to not having the web access, what are the other options of doing the upgrade defaults checking step which is part of the upgrade, with just 2-tier and database access.
    Please suggest on this.
    Regards
    Milind

    can you post some more additional details?
    What is the web server installed on the new server etc...
    Thanks
    Soundappan

  • I use sites with pdf's a lot. Why isn't pdf viewing built into Firefox? The extensions can't keep up with your rapid upgrade program.

    I use sites with pdf's a lot. Why isn't pdf viewing built into Firefox? The extensions can't keep up with your rapid upgrade program.

    Thank you for your post. This forum is for Sony Consumer and Vaio products - for gaming questions and discussions there is a separate PlayStation forum:
    http://community.us.playstation.com

  • Oracle Upgrade --  Pre-Upgrade 10.2.0.4 to 11.2.0.1

    Hello,
    I want to do an Oracle Upgrade to version 11.2g!
    At this point I did some things (in Windows Server 2003 X64):
    1-) Install Oracle 10.2.0.1 (DVD Media);
    2-) Installation of Oracle patchset 10.2.0.4 (note 871735);
    3-) Installation of interim / last generics patch (note 1137346);
    4-) Installation of SAP ECC 6.0 SR3 by SAPInst
    5-) After SAP installation I did all the corrections in Oracle parameters as it mentioned in note 830576.
    As you see above, all the SAP system was well installed!
    But now I want to do the Oracle Upgrade process to the last version, Oracle DB 11.2g  (11.2.0.1)... and so I´m following the Upgrade guide "Upgrade to Oracle Database 11g Release 2 (11.2) Windows.pdf" with some SAP notes for Upgrade process.
    So I´m at this point in planning chapter where is recommended to check so things in actual database, one of this checks are running some SQL-scripts to perform an Oracle database upgrade with DBUA to release 11.2 (as mentioned in note 1431793 - Oracle 11.2.0: Upgrade Scripts)
    I ran two Pre-Scripts, the @pre_upgrade_status.sql and @pre_upgrade_tasks.sql but both outputs showed some warnings and they are worrying me... so what I ask to you is some kind of help in analyse of them and tell me if this issues are relevant for the upgrading process and if so, what you recommend me to do to correct their!
    Next I will post here this two log scripts... they are long!!!

    PRE_UPGRADE_TASKS.log:
    SQL> @pre_upgrade_tasks.sql
    PRE-UPGRADE Tasks: === START ===
    2010-08-05 18:24:13                                                                               
    Recompiling invalid objects
    This reduces the number of invalid objects as much as possible.
    COMP_TIMESTAMP UTLRP_BGN  2010-08-05 18:24:13                                                      
    DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
    DOC>   objects in the database. Recompilation time is proportional to the
    DOC>   number of invalid objects in the database, so this command may take
    DOC>   a long time to execute on a database with a large number of invalid
    DOC>   objects.
    DOC>
    DOC>   Use the following queries to track recompilation progress:
    DOC>
    DOC>   1. Query returning the number of invalid objects remaining. This
    DOC>       number should decrease with time.
    DOC>          SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
    DOC>
    DOC>   2. Query returning the number of objects compiled so far. This number
    DOC>       should increase with time.
    DOC>          SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
    DOC>
    DOC>   This script automatically chooses serial or parallel recompilation
    DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
    DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
    DOC>   On RAC, this number is added across all RAC nodes.
    DOC>
    DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
    DOC>   recompilation. Jobs are created without instance affinity so that they
    DOC>   can migrate across RAC nodes. Use the following queries to verify
    DOC>   whether UTL_RECOMP jobs are being created and run correctly:
    DOC>
    DOC>   1. Query showing jobs created by UTL_RECOMP
    DOC>          SELECT job_name FROM dba_scheduler_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>
    DOC>   2. Query showing UTL_RECOMP jobs that are running
    DOC>          SELECT job_name FROM dba_scheduler_running_jobs
    DOC>          WHERE job_name like 'UTL_RECOMP_SLAVE_%';
    DOC>#
    COMP_TIMESTAMP UTLRP_END  2010-08-05 18:24:15                                                      
    DOC> The following query reports the number of objects that have compiled
    DOC> with errors (objects that compile with errors have status set to 3 in
    DOC> obj$). If the number is higher than expected, please examine the error
    DOC> messages reported with each object (using SHOW ERRORS) to see if they
    DOC> point to system misconfiguration or resource constraints that must be
    DOC> fixed before attempting to recompile these objects.
    DOC>#
                      0                                                                               
    DOC> The following query reports the number of errors caught during
    DOC> recompilation. If this number is non-zero, please query the error
    DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
    DOC> are due to misconfiguration or resource constraints that must be
    DOC> fixed before objects can compile successfully.
    DOC>#
                              0                                                                        
    Purging Recyclebin
    This reduces the time needed for upgrading the database.
    Truncating SYS.AUD$
    This reduces the time needed for upgrading the database.
    Gathering Oracle Dictionary Statistics
    This reduces the time needed for upgrading the database.
    Running Pre-Upgrade-Information Tool utlu112i.sql
    This is a mandatory task for manual database upgrades.
    This tool is also run in pre_upgrade_status.sql.
    Oracle Database 11.2 Pre-Upgrade Information Tool 08-05-2010 18:24:45                              
    Script Version: 11.2.0.1.0 Build: 003                                                              
    Database:                                                                               
    --> name:          PRD                                                                             
    --> version:       10.2.0.4.0                                                                      
    --> compatible:    10.2.0                                                                          
    --> blocksize:     8192                                                                            
    --> platform:      Microsoft Windows x86 64-bit                                                    
    --> timezone file: V4                                                                               
    Tablespaces: [make adjustments in the current environment]                                         
    --> SYSTEM tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 905 MB                                                                 
    --> PSAPUNDO tablespace is adequate for the upgrade.                                               
    .... minimum required size: 84 MB                                                                  
    --> SYSAUX tablespace is adequate for the upgrade.                                                 
    .... minimum required size: 210 MB                                                                 
    --> PSAPTEMP tablespace is adequate for the upgrade.                                               
    .... minimum required size: 61 MB                                                                  
    Flashback: OFF                                                                               
    Update Parameters: [Update Oracle Database 11.2 init.ora or spfile]                                
    Note: Pre-upgrade tool was run on a lower version 64-bit database.                                 
    --> If Target Oracle is 32-Bit, refer here for Update Parameters:                                  
    -- No update parameter changes are required.                                                       
    --> If Target Oracle is 64-Bit, refer here for Update Parameters:                                  
    WARNING: --> "shared_pool_size" needs to be increased to at least 472 MB                           
    Renamed Parameters: [Update Oracle Database 11.2 init.ora or spfile]                               
    -- No renamed parameters found. No changes are required.                                           
    Obsolete/Deprecated Parameters: [Update Oracle Database 11.2 init.ora or spfile]                   
    --> remote_os_authent            11.1       DEPRECATED                                             
    --> background_dump_dest         11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    --> user_dump_dest               11.1       DEPRECATED   replaced by  "diagnostic_dest"            
    Components: [The following database components will be upgraded or installed]                      
    --> Oracle Catalog Views         [upgrade]  VALID                                                  
    --> Oracle Packages and Types    [upgrade]  VALID                                                  
    Miscellaneous Warnings                                                                             
    WARNING: --> Database is using a timezone file older than version 11.                              
    .... After the release migration, it is recommended that DBMS_DST package                          
    .... be used to upgrade the 10.2.0.4.0 database timezone version                                   
    .... to the latest version which comes with the new release.                                       
    Recommendations                                                                               
    Oracle recommends gathering dictionary statistics prior to                                         
    upgrading the database.                                                                            
    To gather dictionary statistics execute the following command                                      
    while connected as SYSDBA:                                                                               
    EXECUTE dbms_stats.gather_dictionary_stats;                                                                               
    Oracle recommends removing all hidden parameters prior to upgrading.                                                                               
    To view existing hidden parameters execute the following command                                   
    while connected AS SYSDBA:                                                                               
    SELECT name,description from SYS.V$PARAMETER WHERE name                                        
            LIKE '\_%' ESCAPE '\'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    Oracle recommends reviewing any defined events prior to upgrading.                                                                               
    To view existing non-default events execute the following commands                                 
    while connected AS SYSDBA:                                                                         
      Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) FROM sys.v$parameter2                           
          WHERE  UPPER(name) ='EVENT' AND  isdefault='FALSE'                                                                               
    Trace Events:                                                                               
    SELECT (translate(value,chr(13)||chr(10),' ')) from sys.v$parameter2                           
          WHERE UPPER(name) = '_TRACE_EVENTS' AND isdefault='FALSE'                                                                               
    Changes will need to be made in the init.ora or spfile.                                                                               
    PRE-UPGRADE Tasks: === FINISHED ===
    SQL> spool off

Maybe you are looking for