7 Replies Latest reply on Aug 26, 2019 11:26 AM by 3510875

    custom top - R12.1.3 to R12.2.5 upgrade

    3510875

      Hi Experts,

       

      Please help us with our concerns

       

      1)will the upgrade creates editioning views and synonyms for custom tables as well?

      2)will the custom schema gets editioned by default or do we have to manually register it?

      3)At what point in the upgrade,should we copy the existing custom top from 12.1.3 to r12.2 file system and run adsplice?(is it after completing the upgrade to R12.2.5)

       

      Thank you

        • 1. Re: custom top - R12.1.3 to R12.2.5 upgrade
          Kanda-Oracle

          Hi

           

          You should run adsplice post upgrade, using the same application ID.

          Refer (Doc ID 1577661.1) for more details. Go to, Section 1.3.1:

           

           

          Hope this helps!

           

          Thanks!

          • 2. Re: custom top - R12.1.3 to R12.2.5 upgrade
            Kanda-Oracle

            Hi

             

            In addition to the above, You may refer..

             

             

            Thanks!

            • 3. Re: custom top - R12.1.3 to R12.2.5 upgrade
              3510875

              Thanks for the update but these didn't answer to my concerns.

               

              1)will the upgrade creates editioning views and synonyms for custom tables as well?

              2)will the custom schema gets editioned by default or do we have to manually register it?

              3)At what point in the upgrade,should we copy the existing custom top from 12.1.3 to r12.2 file system and run adsplice?(is it after completing the upgrade to R12.2.5)

              • 4. Re: custom top - R12.1.3 to R12.2.5 upgrade
                Althaf Khan-Oracle

                1) will the upgrade creates editioning views and synonyms for custom tables as well?

                 

                -->Yes,online patching enablement patch 13543062 will upgrade custom.These are all the task it performs..Make sure that custom schema need to register using adzdcust.sql the details can be get by running adzdpsum.sql

                ================================================================

                Count of Current DDL Jobs per Phase and Status

                DOC>

                DOC>  Phases:

                DOC>    1.  DROP_UNUSED_OBJECT : Remove obsolete objects from XLA schema.

                DOC>    2.  COPY_TYPE           : Create EBS Types in APPS_NE schema, stop Advanced Queues.

                DOC>    3.  COMPILE_TYPE       : Recompile APPS_NE schema.

                DOC>    4.  COPY_EVOLVED_TYPE  : Create evolved types in APPS_NE schema.

                DOC>    5.  FIX_COLUMN           : Fix TYPE reference to APPS_NE.<type> at table and AQ level.

                DOC>    6.  FIX_TYPE           : Additional check, Fix TYPE reference and then drop TYPE

                DOC>                 from source schema.

                DOC>    7.  FIX_PUBLIC_SYNONYM : Fix public synonyms.

                DOC>    8.  RECREATE_AQ_OBJECT : Re-create internal AQ objects after TYPE Ref fix.

                DOC>    9.  DROP_OBJECT        : Drop objects like CTXSYS.<package>, CTXSYS.<synonym> and others if any.

                DOC>    10. ENABLE_EDITIONING  : Enable registered schemas for Online Patching.

                DOC>    11. UPGRADE_TABLE      : Create Editioning View cover layer over EBS data model.

                DOC>    12. UPGRADE_SEED       : Upgrade seed data tables to support edition based storage.

                DOC>    13. COLLECT_STATS      : Gather Statistics on Seed Data Tables after upgrade.

                DOC>    14. UPGRADE_MVIEW      : Convert Materialized Views with expand query.

                DOC>    15. CUTOVER           : Perform maintenance operations on columns and indexes after adop APPLY phase

                DOC>                 and before actually changing Patch-Edition as Default-Edition.

                DOC>    16. ACTUALIZE_ALL      : Actualize all editioned objects into the current edition.

                DOC>    17. CLEANUP           : Cleanup task after adop CUTOVER.

                 

                2)will the custom schema gets editioned by default or do we have to manually register it?

                 

                --->Make sure that custom schema need to register using adzdcust.sql the details can be get by running adzdpsum.sql which you will be running as part of upgrade process

                 

                3)At what point in the upgrade,should we copy the existing custom top from 12.1.3 to r12.2 file system and run adsplice?(is it after completing the upgrade to R12.2.5)

                --->Yes after you have applied the RUP 12.2.5 or the latest one.

                 

                NOTE:-Kindly refer the upgrade document-->https://docs.oracle.com/cd/E26401_01/doc.122/e73540.pdf

                 

                Mandatory Steps for Custom Schema Upgrade for 12.0 / 12.1

                Note:

                Do not run adsplice when you are at the Oracle E-Business

                Suite Release 12.2.0 level. Before running adsplice, you must

                upgrade to R12.AD.C.Delta.5 and R12.TXK.C.Delta.5 Release

                update packs or higher for AD and TXK.

                This step is applicable only if you have custom products. If you have add-on

                 

                Thanks,

                Althaf

                1 person found this helpful
                • 5. Re: custom top - R12.1.3 to R12.2.5 upgrade
                  3510875

                  Thanks Althaf for the helpful information.

                   

                  The custom schema can be registered by the following APIs:

                  1. If Online Patching Enablement is not yet enabled (as suggested in ADZDPCUST.sql):

                  SQL> exec FND_ORACLE_– USER_PKG.LOAD_ROW(‘CUSTOM_SCHEMA’, ‘CUSTOM’, ‘INVALID’, NULL, ‘N’, ‘B’);

                  2. If Online Patching Enablement has already been enabled:

                  sqlplus SYSTEM

                  SQL> alter session set current_schema=APPS;

                  SQL> exec AD_ZD_PREP.ENABLE_CUSTOM_– USER(‘CUSTOM_SCHEMA’);[/stextbox]

                   

                  If we follow step 1,then will online enablement patch creates editioning views and synonyms for custom schema as well?

                  If we follow steps 2,i mean registering custom schema after applying online enablement patch..in that case,it will not create custom synonyms and editioning views for the objects in custom schema right?

                   

                  Please correct me if i am wrong

                  • 6. Re: custom top - R12.1.3 to R12.2.5 upgrade
                    Althaf Khan-Oracle

                    As part of upgrade process will you come to the point where you need to run -->Run the Online Patching Enablement - Readiness Reports.Usually below is the actual process

                     

                    Run the following Readiness reports:

                    • ADZDPSUM.sql - Provides a summary of the schemas that will be editioned

                    and also schemas with objects that depend on E-Business Suite code that is

                    recommended to be editioned. You can register these schemas with the

                    application by running the commands that will be listed in the last section of

                    3-20

                      Oracle E-Business Suite

                    Upgrade Guide

                    this report. Oracle recommends that you run this report again after the custom

                    schemas are registered with the application. You should run ADZDPSUM.sql

                    repeatedly to handle dependent schemas until no further EBR violations are

                    reported.

                    Note:

                    Enter the system password when prompted. You can

                    ignore APPS_NE, and ODM schemas which may appear in

                    section 2 of the report.

                     

                    I will attach the sample report here before applying online enablement patch:-

                    =================================================================

                    DOC>  SECTION-3

                    DOC>  **********************************************************************

                    DOC>

                    DOC>   Unregistered schemas that depend on EBS Objects

                    DOC>

                    DOC>   The listed schemas are not currently registered as Custom EBS Schemas,

                    DOC>   but contain objects which depend on EBS objects. The Online Patching

                    DOC>   enablement process requires that Custom EBS Schemas be registered with

                    DOC>   EBS and enabled for editioning.

                    DOC>

                    DOC>   For each schema reported below, please do one of the following:

                    DOC>

                    DOC>        - If the schema should be retained and will continue to depend on

                    DOC>          EBS objects, then register it as a Custom EBS Schema. Custom EBS

                    DOC>          Schemas will need to comply with new EBS Custom Development

                    DOC>          Standards. See the ADZDPCUST.sql template file instructions

                    DOC>          on how to register custom schemas.

                    DOC>        - If the schema should be retained, but should not depend on EBS

                    DOC>          objects, then leave the schema unregistered and correct any

                    DOC>          object-level violations in the next phase of the readiness check.

                    DOC>        - If the schema is unused, drop it.

                    DOC>

                    DOC> Oracle recommends you perform the chosen fix by customizing template file

                    DOC> $AD_TOP/sql/ADZDPCUST.sql

                    DOC>

                    DOC> EBS objects in CTXSYS get dropped as part of EBR enablement, and will not

                    DOC> show up here due to that

                    DOC>

                    DOC>#

                     

                    Schema               Object Type          Number of Objects

                    -------------------- -------------------- -----------------

                    DLD                  SYNONYM                             87

                     

                    FEDERAL              SYNONYM                             46

                     

                    JPALMER              SYNONYM                             46

                     

                    --->There will be one more section below the above section.This is the command used to register-->sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> DLD..after running this command you need to re-run adzdpsum.sql and you will find in section 1 that custom schema listed as registered--> DLD CUSTOM

                     

                    DOC> Execute the following scripts with the APPS account in order to register

                    DOC> the custom schemas identified in the previous section:

                    DOC>

                    DOC> NOTE: There are 2 types of custom (external) schemas. Per each line below,

                    DOC>       identify the type of schema and perform the action indicated below:

                    DOC>

                    DOC> -1- External schemas which contain objects that will be accessed through a

                    DOC>     standard APPS connection, tightly integrated.    In addition to running the

                    DOC>     the script ADZDREG.sql, execute the FNDCPASS command in order to reset the password

                    DOC>     and register it with the application. Later in the upgrade you will also be

                    DOC>     asked to register this type of schema by running adsplice.

                    DOC>

                    DOC> -2- External schemas that dont use an APPS connection, but do have objects with

                    DOC>     dependencies to EBS objects. (A typical example of this is an APEX schema which

                    DOC>     users the APEX infrastructure to access the objects in the schema and never goes

                    DOC>     through the APPS schema). Running the script ADZDREG.sql below is enough to register

                    DOC>     these type of schemas.

                    DOC>

                    DOC>#

                     

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> PROJMFG

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> PSBEXCEL

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> PTE

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> DLD

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> MOBILEADMIN

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> PSTOCKMAN

                    sqlplus apps @$AD_TOP/patch/115/sql/ADZDREG.sql <system-pwd> <apps-user> MJORDAN.

                     

                    The API you mention taken from one of the document is for adding custom top in 12.2 for already existing EBS . The case would have been someone might have missed some steps while doing adsplice and it may not have properly registered and hence while creating synonym it is saying as not editioned.There by those steps are mention to re-enable it.

                     

                    Thanks,

                    Althaf

                    • 7. Re: custom top - R12.1.3 to R12.2.5 upgrade
                      3510875

                      Thanks a ton althaf...it is clear