AIM Application R12.1.3 to R12.2.5 Upgrade By Mustak Ahmed Contents Upgrade Target Information......................................3 OS Check........................................................3 Clone And Preparation...........................................3 Apply Application Interoperability Patches…………… .......... …………………3 Install 11.2.0.4 ORACLE_HOME...................................3 Apply PreUpgrade Database patches..............................3 Preparing Target datatabase 11.2.0.4............................4 Upgrade database from 11.2.0.3 to 11.2.0.4……………......………………………….6 Perform DB post upgrade task....................................7 Perform code level check (ETCC) for DB and apply all DB Patches11 Install R12.2.0 file system in upgrade mode..................12 Apply preinstall Patches......................................15 Apply Consolidated Upgrade Patch...............................20 Take full backup of DB and Application........................32 Install R12.2.0 to configure the 12.2.0.......................33 Oracle E-Business Suite Online Patching........................35 Perform 12.2.0 Post upgrade task ..............................39 Perform code level check (ETCC) for Application and apply all MT Patches........................................................39 Apply the Latest AD and TXK for Release 12.2...................41 Upgrade Application From 12.2.0 to 12.2.5…..................…….44 Upgrade R12.1.3 to R12.2.5 | 1
75
Embed
Web viewRegister Custom Application using ADSPLICE45. ... Apply 12.2.5 post upgrade task 54. ... Type -- Multi-node Installation
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
AIM
Application R12.1.3 to R12.2.5 Upgrade By Mustak Ahmed
Apply 12.2.5 post upgrade task ....................................................................................................54 Issues and Solutions.......................................................................................................................54
Upgrade R12.1.3 to R12.2.5 | 1
Upgrade Target Information
This document provides the basic information about Oracle Application R12.2.5 upgradation
Environment Details:
Business Suite Version – 12.2.5Type -- Multi-node InstallationInstance Name – ERPUPG Operating Systems – LINUX 6.6
Target OS Preparation
Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID 1349240.1)
Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)
Cloning Oracle DB and APPS
Cloning Oracle Application Release 12 with Rapid Clone (Doc ID 406982.1)
Before the RDBMS software Installation:
Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)
STEP 1 : On E-Business Suite Release 12.1.3 apply below patches (Doc ID 1058763.1)
Patch 7303030 (Oracle E-Business Suite 12.1.1)
Patch 9062910 (11g Release 2 interoperability patch for Release 12.1)
STEP 5: The DMSYS schema exists in the database. Prior to performing an upgrade Oracle recommends that the DMSYS schema, and its associated objects be removed from the database. Doc id 1497250.1
STEP 6: Database Links with Passwords:
Doc ID 1536345.1
WARNING: ->Database contains schemas with objects dependent on DBMS_LDAP package: Ignore
Database Check:
STEP 7: Check for the integrity of the source database.Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)
STEP 8: National Characterset
Check that the National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 or AL16UTF16.
Sql>select value from NLS_DATABASE_PARAMETERS where parameter =
'NLS_NCHAR_CHARACTERSET';
AL16UTF16
STEP 9: Run Analyze.sql
Check for logical corruption in underlying objects and their dependencies.This creates a script called analyze.sql
STEP 10 : MV Refressh DOC ID 1442457.1
Upgrade R12.1.3 to R12.2.5 | 4
Before upgrading Oracle Database, you must wait until all materialized views have completed refreshing and check that replication is stopped.
STEP 11: Media Recovery Status
Ensure that no files need media recovery and that no files are in backup mode.
STEP 12 : System Tablespace
Ensure the users SYS and SYSTEM have 'SYSTEM' as their default tablespace. You must have sufficient space in the tablespace or be set to extents unlimited.
Aud$ table:
Ensure that if the aud$ table exists that it is in the SYS schema and in the SYSTEM tablespace
STEP 13: Drop SYS.ENABLED$INDEXES
If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it: sql>drop table sys.enabled$indexes;
Copy the initialization file from source Oracle Home to <target 11GR2 home>/dbs& change diag location
STEP 18: Start Database in Upgrade mode
At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11.2.0.4 Oracle Home.$ cd $ORACLE_HOME/rdbms/admin$ sqlplus "/ as sysdba"SQL> startup upgrade
STEP 19: Catupgrade
Upgrade R12.1.3 to R12.2.5 | 5
Set the system to spool results to a log file for later verification after the upgrade is completed and start the upgrade script.SQL> set echo onSQL> SPOOL upgrade.logSQL> @catupgrd.sqlSQL> spool off
STEP 20: Post-Upgrade Status Tool
Run the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112s.sql
STEP 21: Catuppst.sql
Run catuppst.sql, located in the $ORACLE_HOME/rdbms/admin directory, to perform upgrade actions that do not require the database to be in UPGRADE mode.SQL> @catuppst.sql
From 11.2.0.3 to 11.2.0.4 home and copy to new home locationSet environment for TNS_ADMINexport TNS_ADMIN=/u01/oracle/product/11.2.0/dbhome_1/network/admin/ERPUPG_erpupgdb-01Start Listener
$ lsnrctl start ERPUPG
Upgrade R12.1.3 to R12.2.5 | 6
STEP 24: DST Upgrade Doc id 1579838.1
Check for TIMESTAMP WITH TIMEZONE Datatype. Uppgrade DST using Note 1579838.1: Actions for DST Updates When Upgrading to or applying the 11.2.0.4 Patchset
STEP 25: Create SPFILE
Sql> create spfile from pfile;
STEP 26: Post Step for DB Patch 4247037
sqlplus / as sysdbaSQL> @/home/oraerpup/upgrade/Patches/Database_patches/4247037/files/md/admin/catmgdidcode.sql
STEP 27: Post Step for DB Patch 17501296
$ sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> @?/sqlpatch/17501296/postinstall.sql
STEP 28: Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql
$ sqlplus "/ as sysdba" @adgrants.sql APPS
Sql>@?/rdbms/admin/utlrp.sql
SQL> select count(*) from dba_objects where status='INVALID';
COUNT(*)---------- 70
STEP 29: Grant create procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql
$ sqlplus apps/apps @adctxprv.sql manager CTXSYS
Set CTXSYS parameter
Use SQL*Plus to connect to the database as SYSDBA and run the following command:$sqlplus "/ as sysdba" SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');
STEP 30: Validate Workflow ruleset
On the administration server node, use SQL*Plus to connect to the database as APPS and run the
Upgrade R12.1.3 to R12.2.5 | 7
$FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command
$sqlplus apps/apps @wfaqupfix.sql APPLSYS apps
STEP 31: Re-generate appsutil
Post Patch steps: Regenerate appsutilperl $AD_TOP/bin/admkappsutil.pl This will create appsutil.zip in $APPL_TOP/admin/out
Copy appsutil:Copy appsutil to RDBMS ORACLE HOME
Unzip appsutil:Unzip the files unzip -o appsutil.zip
$ sqlplus apps/[apps password]SQL> select db_link from dba_db_links;
If you have custom self-referential database links in the database instance, use the following commands to drop and re-create them:
Upgrade R12.1.3 to R12.2.5 | 8
$ sqlplus apps/[apps password]SQL> drop database link [custom database link];SQL> create database link [custom database link] connect to [user] identified by [password] using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname]) (PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';where [custom database link], [user], [password], [hostname], [port number], and [ORACLE_SID] reflect the new Oracle Net listener for the database instance.
STEP 34: MV Refresh
SQL> conn apps/appsConnected.SQL> exec DBMS_MVIEW.REFRESH('&MVIEW_NAME','C',atomic_refresh=>true);Enter value for mview_name: XX_JE_JOURNAL_LINES_V
STEP 35: Restart Applications server processes
Start all the Application tier server processes that you shut down previously.
STEP 36: Synchronize Workflow views
Log on to Oracle E-Business Suite with the "System Administrator" responsibility.Click Requests > Run > Single Request and the OK button. Enter the following parameters:Request Name = Workflow Directory Services User/Role ValidationBatch Size = 10000Fix dangling users = YesAdd missing user/role assignments = YesUpdate WHO columns in WF tables = NoClick "OK" and "Submit".
STEP 37: Gather Fixed Object Statistics
Please create stats on fixed objects two weeks after the upgrade using the below commandSQL>EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
STEP 38: Check Apps Login pages is opening , Check Forms are opening, Check Managers status & Run Active Users and see it completes
STEP 39: Run The 12.2 EBS Technology Code Level Checker (ETCC)? (Doc ID 2008451.1)12.2 E-Business Suite - How to identify patches for listed ETCC missing database and middle tier bugs (Doc ID 2057925.1)checkDBpatch.sh
STEP 45 : R12.2: How To Create the Stage In Preparation For Installation (Doc ID 1596433.1)1. Download And Copy Files To Stage AreaBuild Stage area for 12.2.0:
2. Cleaning Up A Failed Install Attempt
There is no rapidwiz -restart option available with R12.2 and hence once the installation fails then perform the below steps to clean up failed installation first. And then perform the installation.
A. Restart the server or make sure Application service down to kill ALL applmgr processes.
B. Delete the install directory, oraInventory and /tmp.C. Run rapidwiz to start installation again.
3. Rapidwiz upgrade mode./rapidwiz
STEP 46 : Re-generate Appsutil
Post Patch steps: Regenerate appsutil perl $AD_TOP/bin/admkappsutil.plUpgrade R12.1.3 to R12.2.5 | 11
This will create appsutil.zip in $APPL_TOP/admin/out
Copy and unzip appsutil:Copy appsutil to rdbms oracle home Unzip the files unzip -o appsutil.zip
sqlplus / as sysdbaSQL> alter session set current_schema=SYS;SQL> @?/rdbms/admin/dbmsxdbschmig.sqlSQL> @?/rdbms/admin/prvtxdbschmig.plbSQL> @?/rdbms/admin/utlrp.sqlSql> @?/rdbms/admin/catmgd.sqlSQL> @adgrants.sql APPSSQL> alter system set local_listener='ERPUPG_LOCAL' scope=spfile;SQL> alter system set service_names='ERPUPG,ebs_patch';
STEP 53: Enable autoextend on system and apps_ts_seed tablespaces.
STEP 54: 1.Disable AOL Audit Trail (conditional)
SQL> select distinct enabled from dba_audit_policies ; no rows selected
STEP 55: Update init.ora with upgrade parameters (required) Database Initialization Parameters for Oracle Applications Release 12 (Doc ID: 396009.1)
Change below parameters as per doc above
SQL> alter system set java_pool_size=150m scope=both ; System altered.SQL> alter system set large_pool_size=150m scope=both; System altered.SQL> alter system set recyclebin=off scope=spfile ; System altered.SQL> alter system set open_cursors=1000;
STEP 58: Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Section 3 : Instruction for Upgrade Customers
1. Prerequisite: Apply the AD Upgrade Patch for Release 12.2 (Patch 10117518) by merging it with the latest Consolidated Upgrade Patch (CUP) for AD (Patch 22742061:R12.AD.C).
The AD Upgrade Patch for Release 12.2 (Patch 10117518) readme contains information about the latest Consolidated Upgrade Patch (CUP) for AD (Patch 22742061:R12.AD.C).
You must follow the Patch 10117518 readme and apply it by merging it with the latest Consolidated Upgrade Patch for AD, along with any other patches mentioned in the Readme, as instructed in the readme and by referring to the Upgrade Guides.
[aperpup@ERPUPGAPP-01 ~]$ grep -i errors $APPL_TOP/admin/$TWO_TASK/log/u_10117518_cup7.log 0 files had fatal errors.Errors and warnings are listed in the log file
[aperpup@ERPUPGAPP-01 ~]$ grep -i warnings $APPL_TOP/admin/$TWO_TASK/log/u_10117518_cup7.logErrors and warnings are listed in the log file
STEP 59: Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
Apply the Consolidated Upgrade Patch (CUP) for Release 12.2.0Upgrade R12.1.3 to R12.2.5 | 18
Preinstall
Section 3: Instructions for Upgrade Customers
R12.1 and 12.2 Oracle E-Business Suite Preinstall Patches Report [Video] (Doc ID 1448102.2)Download the Latest 12.2 Preinstall Patch Report: EBS_R12.2_Preinstall_2016_Dec_20.zip
[aperpup@ERPUPGAPP-01 dest]$ cd $AU_TOP/patch/115/driver[aperpup@ERPUPGAPP-01 driver]$ lsaugenmsg.drvx ausstats.drvx u10124646.drv u10201000.drv
[aperpup@ERPUPGAPP-01 dest]$ time adpatch preinstall=y
Errors and warnings are listed in the log file/u02/oracle/ERPUPG/fs1/EBSapps/appl/admin/ERPUPG/log/u_merged.log
2 Min.Upgrade R12.1.3 to R12.2.5 | 24
[aperpup@ERPUPGAPP-01 dest]$ grep -i errors $APPL_TOP/admin/$TWO_TASK/log/u_merged.log 0 files had fatal errors.Errors and warnings are listed in the log file[aperpup@ERPUPGAPP-01 dest]$ grep -i warnings $APPL_TOP/admin/$TWO_TASK/log/u_merged.logErrors and warnings are listed in the log file[aperpup@ERPUPGAPP-01 dest]$ grep -i failed $APPL_TOP/admin/$TWO_TASK/log/u_merged.log
Step 59.3:
Merge the Upgrade Drive 10124646
[aperpup@ERPUPGAPP-01 dest]$ cd /u02/oracle/ERPUPG/fs1/EBSapps/appl/admin/ERPUPG/preinstall/[aperpup@ERPUPGAPP-01 preinstall]$ lsu22742071.drv u_merged.drv
[aperpup@ERPUPGAPP-01 preinstall]$ cd $AU_TOP/patch/115/driver[aperpup@ERPUPGAPP-01 driver]$ lsaugenmsg.drvx ausstats.drvx u10124646.drv u10201000.drv
Please enter the name of your AutoPatch driver file : u_merged.drv-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Upgrade R12.1.3 to R12.2.5 | 25
This base patch contains files which may require translationdepending on the languages you currently have installed.
Oracle Corporation recommends that you obtain any translated versions of thispatch for each of your non-US languages after applying this base patch.Or you may request and apply a Translation Synchronization Patchto obtain the translation.-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Do you wish to apply this patch now [No] ? yes
ERRORS:--------
ERRRO 1.MSDODPCODE.sql
ERROR:ORA-03114: not connected to ORACLESP2-0359: memory exhausted
SOLUTION:-
SELECT PI.APPLICATION_ID ID, APP.APPLICATION_SHORT_NAME APP, APP.APPLICATION_NAME, PI.STATUS, PI.PATCH_LEVEL, PI.LAST_UPDATE_DATE FROM FND_PRODUCT_INSTALLATIONS PI, FND_APPLICATION_VL APP WHERE APPLICATION_SHORT_NAME in ('MSD') AND PI.APPLICATION_ID = APP.APPLICATION_ID ORDER BY APPLICATION_SHORT_NAME
DECLARE*ERROR at line 1:ORA-33272: Analytic workspace APPS.ODPCODE cannot be opened.ORA-33288: Another user has incompatible access to analytic workspaceAPPS.ODPCODE, and the wait timeout has expired.ORA-06512: at "SYS.DBMS_AW", line 67ORA-06512: at "SYS.DBMS_AW", line 131ORA-06512: at "SYS.DBMS_AW", line 926ORA-06512: at "SYS.DBMS_AW", line 901ORA-06512: at "APPS.MSD_AW_LOADER", line 10ORA-06512: at line 4
NOTE:-When a patch is run with parallel workers, two or more workers may try to attach the AW in read write(RW) mode.
Started the failed worker once again.
After started we have faced below error:-Upgrade R12.1.3 to R12.2.5 | 29
Sql>select node_name from fnd_nodes;Sql> exec fnd_conc_clone.setup_clean ; Sql> commit;
# Run AutoConfig on the DB Tier
Sql> select object_name, object_type, owner, status from dba_objects whereupper(object_name)='ADX_PRE_AUTOCONFIG' and object_type='TABLE'and upper(owner)='APPS';
If no rows exists then skip the below step
---To drop table ADX_PRE_AUTOCONFIG from APPS schema and recreatein APPLSYS schema, execute the following commands:
$ cd $AD_TOP/patch/115/sql
$ sqlplus apps/apps @txkDropAdxPreAutoConfig.sql
$ Run Autoconfig on Apps Tier
Step 60.3: Bounce DB
Step 60.4: Configure the PATCH FILESYSTEM using Rapidwiz
.Run Rapid Install to configure Release 12.2 E-Business Suite instance.
You must run Rapid Install (root user a second time to complete the configuration usingRun File System context file.
Upgrade R12.1.3 to R12.2.5 | 32
Step 60.5: Implement and run AutoConfig
Regenerate appsutilperl $AD_TOP/bin/admkappsutil.plThis will create appsutil.zip in $APPL_TOP/admin/out
Copy appsutil:Copy appsutil to RDBMS ORACLE HOME
Unzip appsutil:Unzip the files unzip -o appsutil.zip
Online Patching Diagnostic Reports Main Menu --------------------------------------------
1. Run edition reports
Upgrade R12.1.3 to R12.2.5 | 34
2. Patch edition reports 3. Other generic reports 4. Exit
Enter your choice [4]: 3 Other Generic Reports Sub Menu ------------------------------
1. Editions summary 2. Editioned objects summary 3. Free space in important tablespaces 4. Status of critical AD_ZD objects 5. Actual objects in current edition 6. Objects dependencies 7. Objects dependency tree 8. Editioning views column mappings 9. Index details for a table 10. Inherited objects in the current edition 11. All log messages 12. Materialized view details 13. Database sessions by edition 14. Table details (Synonyms, EV, etc.) 15. Count and status of DDL execution by phase 16. Back to main menu
Enter your choice [16]: 3=========================================================================
Important Tablespace Status=========================================================================
Take special note to ensure that all online patching objects (objects that match the pattern 'AD_ZD%') are validSelect owner,object_name,status from dba_objects where object_name like 'AD_ZD%';
SQL> Select owner,object_name,status from dba_objects where object_name like 'AD_ZD%';
ORA-38818: illegal reference to editioned object APPS.GLR03300_PKGDisconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing options
Create And Register CUSTOM Schema On EBS 12.2 (Doc ID 1929668.1)ORA-38818: Illegal Reference To Editioned Object When Creating Materialized View (Doc ID 1556379.1)
$ Compile Invalid Objects (if any) Connect to sqlplus as 'apps' and run the following: exec sys.utl_recomp.recomp_parallel;
Run the Online Patching Database Compliance Checker report to check for online patching database objects standards violations: sqlplus <Apps Username> @$AD_TOP/sql/ADZDDBCC.sql
STEP 62: Post-Upgrade Tasks
Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Step 62.1: Download code levelcheck (ETCC)
Patch 17537119 Run checkMT.sh to check missing patches on 10gaAS and webTier home APPS_ETCC_CHECH _V0
[appltest@gpcerptestapp ETCC]$ ./checkMTpatch.sh
Step 62.2 === Oracle Forms and Reports_patch
Oracle Forms and Reports 10.1.2.3.0------------------------------------------------------------------------------- Patch 22698265
- Filename: p22698265_101232_LINUX.zip
Upgrade R12.1.3 to R12.2.5 | 38
STEP 62.3 ==oracle_common_patch:
Oracle Home = /u02/oracle/ERPUPG/fs1/FMW_Home/oracle_common
NOTE :- Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes and apply all technology patches for your database and application tier versions.
After you have run ETCC as applicable, proceed to the installation steps below.
STEP 63 Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
The latest RUPs are R12.AD.C.Delta.8 (Patch 21841299) and R12.TXK.C.Delta.8 (Patch 21830810).
Oracle E-Business Suite Release 12.2.5 Readme (Doc ID 1983050.1)
Note: If the Release 12.2.0 Vision or PROD instance (New Installation) was created using startCD 12.2.0.51 (Patch 22066363), you must apply Consolidated Seed Table Upgrade Patch 17204589:12.2.0 by merging with Patch 21900871:12.2.0 on the run file system using adop hotpatch mode.
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
[aperpup@ERPUPGAPP-01 scripts]$ ./adadminsrvctl.sh status
You are running adadminsrvctl.sh version 120.10.12020000.2Upgrade R12.1.3 to R12.2.5 | 40
# ################################################### file format id (should begin with "%%%")# ##################################################%%% Single-product product data file format 12.0.A## ################################################### LIST OF PRODUCT ABBREVIATIONS and the corresponding application ids.# This list lets you forward-reference the abbreviations of shared products.# This list should match the official correspondence between id and# abbreviation, given for each product in the Product List.# #################################################### Product specific Product ID'sxxconv 20005
END_OF_PRODUCT_ABBREVIATIONS -999## ################################################### Oracle Support Diagnostic Tools# ###################################################
Upgrade R12.1.3 to R12.2.5 | 45
# application id, abbreviation, shortname, prefix20005 xxconv XXCONV APP# multiple product installations for msob, "controlled release", shared only# optional fourth field is "stub product". default is NoNo No No No# multilingual, has NLADD.sqlYes Yes# install oracle id, default ORACLE username, default ORACLE password20045 XXCONV XXCONV# concurrent conflict set id (logical database id)0# minimum version you can upgrade from, for shared and for fully-installed1.0.0 1.0.0# shared products# FND, AK, AX and AZ are required for this section# For example:# fnd ak ax az gl inv po ap fa ar oe as per pay mfg bom eng mrp crp wip pa# If you list a product in the set-to-install or required-as-installed# sections below, you MUST also list the product as a shared product# fnd ak ax aznone# product libraries needed for "make -f <product>.mk all"# For example: fnd alr gl rgnone# when install this product, set these other products to install# This is the set-to-install section# AK, AX and AZ are required for this section# For example: ak ax az rg# This section must exactly match the required-as-installed section# ak ax aznone# requires that these other products are fully installed or installing# This is the required-as-installed section# AK, AX and AZ are required for this section# For example: ak ax az rg# This section must exactly match the set-to-install section# ak ax aznone## ################################################### END OF PRODUCT LIST# ###################################################END_OF_PRODUCTS## ################################################### START OF RELEASE LIST# ################################################### For each release, the products should be listed in install/upgrade order.# FND should always be listed first in the release.## The first release listed should be the lowest release# we support upgrading from (e.g. release 10.5.0 for MPL 10)# AutoInstall will stop if a product version is lower than the lowest release.
Upgrade R12.1.3 to R12.2.5 | 46
# AutoInstall will assume that if a product version is at the lowest release,# then it can be upgraded to the current release.### ################################################### Release 12.0.0# #################################################### release name, for use by AutoInstall onlyRelease 12.0.0# release version, for FND_PRODUCT_GROUPS and the \ Help Version feature.# this value should not contain any English.12.0.0# release abbreviation, rename prefix, release typeR120 R120_ additional-this-mpl# list of products and versionsXXCONV 12.0.0END_OF_RELEASE 0.0.0### ################################################################## end of izuprod.txt file# ##################################################################
[aperpup@ERPUPGAPP-01 admin]$ cat xxconvterr.txt
#%%% Single-product territory data file format 12.0.A## Release abbreviation# 10.7 - R1107, 11.0 = R11.0.28, 11.5 = R115R120## ################################################################ LIST OF LANGUAGE INFO# ################################################################# See applterr.txt for more info on what the fields for a language mean## You should specify the product's name in American English## You do not need to include records for other languages unless you need to# specify the product's name in other languages## ############################## language id, shortname, codes and names0 usaeng US AMERICAN EN US American_English# appltape filename, appltape filename for loc. products, codesetappltape.txt appltape.txt WE8ISO8859P1# signon translated, standard dg name, other dg prefixYes Standard Data_Group# products that have dnls.drv files
Upgrade R12.1.3 to R12.2.5 | 47
none# products that have bnls.drv filesnone# products that have fnls.drv filesnone# products that have GV dnls.drv filesnone# products that have GV fnls.drv filesnone# product names in this languagec xxconv Oracle_Support_Diagnostic_ToolsEND_OF_PRODUCT_NAMES## You may specify info for other languages here, but usually you will# not need to do this.#END_OF_LANGUAGE_INFO## ################################################################## end of izuterr.txt file# #################################################################
[aperpup@ERPUPGAPP-01 admin]$ cd $APPL_TOP/admin
[aperpup@ERPUPGAPP-01 admin]$ adsplice
Copyright (c) 2002, 2012 Oracle Corporation Redwood Shores, California, USA
AD Splicer
Version 12.2.0
NOTE: You may not use this utility for custom development unless you have written permission from Oracle Corporation.
Your default directory is '/u02/oracle/ERPUPG/fs1/EBSapps/appl'.Is this the correct APPL_TOP [Yes] ?
AD Splicer records your AD Splicer session in a text fileyou specify. Enter your AD Splicer log file name or press [Return]to accept the default file name shown in brackets.
Filename [adsplice.log] : xxconv.log
Please enter the directory where your AD Splicer control file is located.
The default directory is [/u02/oracle/ERPUPG/fs1/EBSapps/appl/admin] :
Please enter the name of your AD Splicer control file [newprods.txt] :
Regenerate appsutil perl $AD_TOP/bin/admkappsutil.pl This will create appsutil.zip in $APPL_TOP/admin/out Copy appsutil: Copy appsutil to RDBMS ORACLE HOME Unzip appsutil: Unzip the files unzip -o appsutil.zip
Create CONTEXT_FILE:
adbld.xml Implement autoconfig ON DB SIDE: ./adconfig.sh contextfile=/u01/oracle/product/11.2.0/dbhome_1/appsutil/ERPUPG_erpupgdb-01.xml RUN AUTOCONFIG ON APPS SIDE:
ERROR:ORA-03114: not connected to ORACLESP2-0359: memory exhausted
SOLUTION:-
SELECT PI.APPLICATION_ID ID, APP.APPLICATION_SHORT_NAME APP, APP.APPLICATION_NAME, PI.STATUS, PI.PATCH_LEVEL, PI.LAST_UPDATE_DATE FROM FND_PRODUCT_INSTALLATIONS PI, FND_APPLICATION_VL APP WHERE APPLICATION_SHORT_NAME in ('MSD') AND PI.APPLICATION_ID = APP.APPLICATION_ID ORDER BY APPLICATION_SHORT_NAME ID APP
DECLARE*ERROR at line 1:ORA-33272: Analytic workspace APPS.ODPCODE cannot be opened.ORA-33288: Another user has incompatible access to analytic workspaceAPPS.ODPCODE, and the wait timeout has expired.ORA-06512: at "SYS.DBMS_AW", line 67ORA-06512: at "SYS.DBMS_AW", line 131ORA-06512: at "SYS.DBMS_AW", line 926ORA-06512: at "SYS.DBMS_AW", line 901ORA-06512: at "APPS.MSD_AW_LOADER", line 10ORA-06512: at line 4
NOTE:-
When a patch is run with parallel workers, two or more workers may try to attach the AW in read write(RW) mode.