Upgrade Oracle Database onUpgrade Oracle Database on
Solaris (64bit) 11.1 fromSolaris (64bit) 11.1 from
11.2.0.3 to11.2.0....
Introduction
◦ How to upgrade Oracle Database Instance ver 11.2.0.3 to 11.2.0.4 on Solaris 11.1
◦ This document describes ...
Oracle Database Ver 11.2.0.3 Single node (gsxcrp1db) OS Solaris 11.1, with required OS patches
Oracle EBS version 12.2.0 s...
This document is divided into Sections(4) major sections
Section 1: Upgrading an R12 Database to Oracle Database 11g Relea...
EBS Architecture DiagramEBS Architecture Diagram
contact@gowrainfosys.comcontact@gowrainfosys.com
EBS Architecture DiagramEBS Architecture Diagram
contact@gowrainfosys.comcontact@gowrainfosys.com
Source Virtual Machine configuration (DB only):
Virtual Machine Disks:
contact@gowrainfosys.comcontact@gowrainfosys.com
Vi...
Target Virtual Machine configuration (DB only):
Virtual Machine Disks:
contact@gowrainfosys.comcontact@gowrainfosys.com
Vi...
Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2
(11.2.0)
◦ Follow the instructions in this section p...
After the installation, make sure that:
◦ The ORACLE_BASE environment variable must be set accordingly.
◦ The ORACLE_HOME ...
Shut down Applications server processes and database listener
Drop SYS.ENABLED$INDEXES (conditional)
◦ If the SYS.ENABLED$...
Prepare to Manual upgrade to 11.2.0.4
Pre-Upgrade Steps
Step 1:
◦ Log into the system as the owner of the Oracle Database ...
Step 2:
◦ Change to the directory where utlu112i.sql had been copied in the previous step.
◦ Start SQL*Plus and connect to...
Step 3:
◦ Check for the integrity of the source database.
◦ Check for the integrity of the source database prior to starti...
$ sqlplus "/as sysdba“
SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
Step 6:
Step 7:
Disable Oracle Database Vault
Optimiz...
SQL> select distinct(trunc(last_refresh)) from dba_snapshot_refresh_times;
SQL> select s.obj#,o.obj#,s.containerobj#,lastr...
Step 12 Through Step XX are purposely skipped :
For Missing Steps
Contact: Info@GowraInfoSys.com
You should have a valid C...
$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus "/ as sysdba"
SQL> startup UPGRADE
SQL> set echo on
SQL> SPOOL upgrade_11204.log
S...
$ lsnrctl start
Post-Upgrade Steps: Database to 11.2.0.4
Step XX2:
Start database Listener
EXECUTE DBMS_STATS.UPGRADE_STAT...
After the Database Upgrade:
• Start database Listener
sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql) [APPS schem...
After the Database Upgrade:
$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;
Deregister the current da...
Re-create custom database links (conditional)
Uses the generated script from pre-upgrade step and verify
$ sqlplus apps/[a...
Section 2: Unsupported Products
Since the database was already at 11.2.0.3, not an issue
The following EBS products are cu...
Database Version: 11.2.0.4 (Solaris 11.1) Oracle Applications: 12.2.0 (Linux x86-64)
ResultResult
contact@gowrainfosys.com...
Database Version: 11.2.0.4 (Solaris 11.1)
ResultResult
contact@gowrainfosys.comcontact@gowrainfosys.com
Database Version: 11.2.0.3 (Solaris 11.1) Oracle Applications: 12.2.0 (Linux x86-64)
ResultResult
contact@gowrainfosys.com...
Oracle Database Utilities 11g Release 2 (11.2). - Documentation
Database Initialization Parameters for Oracle E-Business S...
◦ How to upgrade Oracle Applications database Instance 11.2.0.3 to
11.2.0.4
◦ Database and Application server running on S...
11gR2.0.4 RAC Installation and configuration, Non-GNS,
ASM, on Oracle Private Cloud with Vmotion on Linux,
Solaris, AIX, H...
Upcoming SlideShare
Loading in …5
×

How to Upgrade Oracle Database on Solaris (64bit) 11.1 from 11.2.0.3 to 11.2.0.4 for Oracle Apps DBA (EBS) - Ver 12.2.0

1,367 views

Published on

Upgrade Oracle Database from Solaris 11.1 (64bit) 11.2.0.3 to 11.2.0.4 for Oracle Apps DBA (EBS) on Linux 6.5 (64bit) - Ver 12.2.0, Oracle Private Cloud

Published in: Technology, News & Politics
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,367
On SlideShare
0
From Embeds
0
Number of Embeds
50
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

How to Upgrade Oracle Database on Solaris (64bit) 11.1 from 11.2.0.3 to 11.2.0.4 for Oracle Apps DBA (EBS) - Ver 12.2.0

  1. 1. Upgrade Oracle Database onUpgrade Oracle Database on Solaris (64bit) 11.1 fromSolaris (64bit) 11.1 from 11.2.0.3 to11.2.0.3 to 11.2.0.411.2.0.4 for Oraclefor Oracle Apps DBA (EBS)Apps DBA (EBS) -- VerVer 12.2.0,12.2.0, By GowraInfosysBy GowraInfosysBy GowraInfosysBy GowraInfosys Upgrade Oracle Database from Solaris 11.1 (64bit) 11.2.0.3 to 11.2.0.4 for Oracle Apps DBA (EBS) on Linux 6.5 (64bit) - Ver 12.2.0, Oracle Private Cloud contact@gowrainfosys.com
  2. 2. Introduction ◦ How to upgrade Oracle Database Instance ver 11.2.0.3 to 11.2.0.4 on Solaris 11.1 ◦ This document describes the process of upgrade database in multi not Oracle Apps R12.2 implementation ◦ This document assumes that you are already familiar with MOS. ◦ Following Oracle’s Patching & Maintenance Advisor: Database (DB) Oracle Database 11.2.0.x Evaluate Plan Test Welcome and IntroductionWelcome and Introduction contact@gowrainfosys.comcontact@gowrainfosys.com Test Implement ◦ Trouble shooting Error’s, Warning and Know Issues. ◦ Don’t forget to have fun while upgrade.
  3. 3. Oracle Database Ver 11.2.0.3 Single node (gsxcrp1db) OS Solaris 11.1, with required OS patches Oracle EBS version 12.2.0 single node (g6ebscrp2) Linux6.5 x64, with required OS patches Target Database version 11.2.0.4 Single node (gsxcrp1db) OS, Solaris 11.1 x64. This document assumes that the instance R12.2.x is stable and no errors and warnings from OS or Database or Applications (components), database Init parameters or set for the Upgrade. Linux OS 6.5 (g6ebscrp2) is running on Oracle VM and VM server Version 3.2.8-735 Using iSCSI to access Storage, with 520MB/s read/write, with 10GbE Network with Jumbo Frames. ◦ Target Application OS, Oracle VM configuration:(Linux6.5 x64) 12 virtual CPU’s, 14GB RAM, with two virtual NIC’s. Virtual Disk 50GB for the OS, Virtual Disk 200GB for Application file system (d01) OverviewOverview contact@gowrainfosys.comcontact@gowrainfosys.com Solaris 11.1 x64 (gsxcrp1db) is running on Oracle VM and VM server Version 3.2.8-735 Using iSCSI to access Storage, with 520MB/s read/write, with 10GbE Network with Jumbo Frames. ◦ Source/target Oracle VM configuration: (DB and EBS) 12 virtual CPU’s, 24GB RAM, with two virtual NIC’s. Virtual Disk 50GB for the OS, Virtual Disk 300GB for Oracle EBS data files (u02) and Virtual Disk 30GB binaries (u01), Assumes good understanding and knowledge of R12.2 Application architecture and EBS adop patching tool and oracle opatch tool and other sizing tools like SLOB2, Hammerora, swingbench , OATS, RAT, etc.
  4. 4. This document is divided into Sections(4) major sections Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2 (11.2.0) Instructions for upgrading an Oracle E-Business Suite Release 12 database server and instance earlier versions of Oracle Database 11g Release 2 (11.2.0) to the latest version of Oracle Database 11g Release 2 (11.2.0.4). a) Before the Database Installation b) Database Installation c) Database Upgrade d) After the Database Upgrade Section 2: Unsupported Products This section lists products that are currently not supported with Oracle E-Business Suite Release 12 on Oracle Database 11g Release 2 (11.2.0.4). VocabularyVocabulary contact@gowrainfosys.comcontact@gowrainfosys.com This section lists products that are currently not supported with Oracle E-Business Suite Release 12 on Oracle Database 11g Release 2 (11.2.0.4). Section 3: Known Issues This section lists known issues with Oracle E-Business Suite Release 12 on Oracle Database 11.2.0.4. Section 4: Verification and Testing end Result Testing using OATS and Manual verification of the Migration.
  5. 5. EBS Architecture DiagramEBS Architecture Diagram contact@gowrainfosys.comcontact@gowrainfosys.com
  6. 6. EBS Architecture DiagramEBS Architecture Diagram contact@gowrainfosys.comcontact@gowrainfosys.com
  7. 7. Source Virtual Machine configuration (DB only): Virtual Machine Disks: contact@gowrainfosys.comcontact@gowrainfosys.com Virtual Machine Networks:
  8. 8. Target Virtual Machine configuration (DB only): Virtual Machine Disks: contact@gowrainfosys.comcontact@gowrainfosys.com Virtual Machine Networks:
  9. 9. Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2 (11.2.0) ◦ Follow the instructions in this section plan to upgrade the database server and instance to the latest version of Oracle Database 11g Release 2 (11.2.0.4). a) Before the Database Installation: 1. Verify software versions Non required as the current database at version 11.2.0.3, and DST is already at ver 17 b) Database Installation: 1. Prepare to create the 11.2.0 Oracle home The 11.2.0.4 Oracle home must be installed on the database server node in a different directory than the current Oracle home. contact@gowrainfosys.comcontact@gowrainfosys.com directory than the current Oracle home. ***DBA skill required if you are manipulating Inventory and installing in the same directory structure 2. Install the 11.2.0.4 software Log in to the database server node as the owner of the Oracle RDBMS file system and database instance. Ensure that environment settings, such as ORACLE_HOME, are set for the new Oracle home you are about to create, and not for any existing Oracle homes on the database server node. Perform all the steps in Chapter 4, "Installing Oracle Database" of the Oracle Database Installation Guide 11g Release 2 (11.2) for Solaris 11.1 x86-64bit Apply One of patches, requited for R12.2.0
  10. 10. After the installation, make sure that: ◦ The ORACLE_BASE environment variable must be set accordingly. ◦ The ORACLE_HOME environment variable points to the new 11.2.0 Oracle home. ◦ The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin). ◦ The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib. ◦ The PERL5LIB environment variable points to the directories where the new perl libraries are located (usually $ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version]) Create nls/data/9idata directory ◦ On the database server node, as the owner of the Oracle RDBMS file system and database instance, run the following command to create the $ORACLE_HOME/nls/data/9idata directory. contact@gowrainfosys.comcontact@gowrainfosys.com Apply additional 11.2.0.4 RDBMS patches ◦ Apply the following patches: For all Solaris 11.1 x86-64 platforms: Patch 4247037 Patch 17402822 Patch 17468141 Patch 17501296 Patch 17892268 ***Do not run any of the post install instructions as those will be done after the upgrade.
  11. 11. Shut down Applications server processes and database listener Drop SYS.ENABLED$INDEXES (conditional) ◦ 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: Disable Database Vault (conditional) ◦ If you have Database Vault installed, perform steps 1 to 6 of Part 2 of document 1091083.1 on My Oracle Support to disable Database Vault. Prepare to Manual upgrade to 11.2.0.4 Pre-Upgrade Steps drop table sys.enabled$indexes; contact@gowrainfosys.comcontact@gowrainfosys.com Pre-Upgrade Steps
  12. 12. Prepare to Manual upgrade to 11.2.0.4 Pre-Upgrade Steps Step 1: ◦ Log into the system as the owner of the Oracle Database 11g Release 2 (11.2.0.3) Oracle Home directory. ◦ Copy the Pre-Upgrade Information Tool (utlu112i.sql) from the Oracle Database 11g Release 2 (11.2.0.4) ORACLE_HOME/rdbms/admin directory to a directory outside of the Oracle Home, such as the temporary directory on your system. $ORACLE_HOME/rdbms/admin/utlu112i.sql contact@gowrainfosys.comcontact@gowrainfosys.com
  13. 13. Step 2: ◦ Change to the directory where utlu112i.sql had been copied in the previous step. ◦ Start SQL*Plus and connect to the database instance as a user with SYSDBA privileges. Then run and spool the utlu112i.sql file. Please note that the database should be started using the source Oracle Home export ORACLE_HOME=/u01/oracle/EBSCRP1/11.2.0.4 $ sqlplus '/ as sysdba' SQL> spool upgrade_info_11204.log SQL> @utlu112i.sql SQL> spool off Review out put file from upgrade_info_11204.log, provide appropriate fixes, for each of the selections. •Database contact@gowrainfosys.comcontact@gowrainfosys.com •Database •Logfiles •Tablespaces •Update Parameters •Deprecated Parameters •Obsolete Parameters: •Components •Miscellaneous Warnings •SYSAUX Tablespace
  14. 14. Step 3: ◦ Check for the integrity of the source database. ◦ Check for the integrity of the source database prior to starting the upgrade by downloading and running the dbupgdiag.sql script from the My Oracle Support article below oracle@gsxcrp1db:$ sqlplus "/ as sysdba" @$ORACLE_HOME/rdbms/admin/utlrp.sql Step 4: Create script for DBLINK (in case the database has to be downgraded again). After validating the invalid objects, re-run dbupgdiag.sql in the database once again and make sure that everything is fine. SELECT 'CREATE '||DECODE(U.NAME,'PUBLIC','public ')||'DATABASE LINK '||CHR(10) contact@gowrainfosys.comcontact@gowrainfosys.com SELECT 'CREATE '||DECODE(U.NAME,'PUBLIC','public ')||'DATABASE LINK '||CHR(10) ||DECODE(U.NAME,'PUBLIC',Null, 'SYS','',U.NAME||'.')|| L.NAME||chr(10) ||'CONNECT TO ' || L.USERID || ' IDENTIFIED BY "'||L.PASSWORD||'" USING '''||L.HOST||'''' ||chr(10)||';' TEXT FROM SYS.LINK$ L, SYS.USER$ U WHERE L.OWNER# = U.USER#; Step 5: Check that the National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 or AL16UTF16. select value from NLS_DATABASE_PARAMETERS where parameter = NLS_NCHAR_CHARACTERSET‘;
  15. 15. $ sqlplus "/as sysdba“ SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS; Step 6: Step 7: Disable Oracle Database Vault OptimizerStatistics: When upgrading to Oracle Database 11g Release 2 (11.2), optimizer statistics are collected for dictionary tables that lack statistics. This statistics collection can be time consuming for databases with a large number of dictionary tables, but statistics gathering only occurs for those tables that lack statistics or are significantly changed during the upgrade. Step 8: This optional check is introduced to spot any logical corruption in underlying objects and their contact@gowrainfosys.comcontact@gowrainfosys.com This optional check is introduced to spot any logical corruption in underlying objects and their dependencies. SELECT 'Analyze cluster "'||cluster_name||'" validate structure cascade;' FROM dba_clusters WHERE owner='SYS' UNION SELECT 'Analyze table "'||table_name||'" validate structure cascade;' FROM dba_tables WHERE owner='SYS’ AND partitioned='NO’ AND (iot_type='IOT' OR iot_type is NULL) UNION SELECT 'Analyze table "'||table_name||'" validate structure cascade into invalid_rows;' FROM dba_tables WHERE owner='SYS’ AND partitioned='YES'; spool off
  16. 16. SQL> select distinct(trunc(last_refresh)) from dba_snapshot_refresh_times; SQL> select s.obj#,o.obj#,s.containerobj#,lastrefreshdate,pflags,xpflags,o.name,o.owner#, bitand(s.mflags, 8) from obj$ o, sum$ s where o.obj# = s.obj# and o.type# = 42 AND bitand(s.mflags, 8) = 8; Step 9: Step 10: Ensure that no files need media recovery and that no files are in backup mode. SELECT * FROM v$recover_file; SELECT * FROM v$backup WHERE status != 'NOT ACTIVE‘; Before upgrading Oracle Database, you must wait until all materialized views have completed refreshing and check that replication is stopped. Run the following query to determine if there are any materialized view refreshes still in progress: SELECT * FROM v$backup WHERE status != 'NOT ACTIVE‘; Step 11: Disable all batch and cron jobs. About jobs initiated with Oracle the packages DBMS_JOB, DBMS_SCHEDULER can be used , regarding cron jobs (external jobs controlled at the OS level), this is a task for your Unix administrator
  17. 17. Step 12 Through Step XX are purposely skipped : For Missing Steps Contact: Info@GowraInfoSys.com You should have a valid CSI number with Oracle Apps Implementation
  18. 18. $ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba" SQL> startup UPGRADE SQL> set echo on SQL> SPOOL upgrade_11204.log SQL> @catupgrd.sql SQL> spool off Upgrading Database to 11.2.0.4 Step XX1: At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11.2.0.4 Oracle Home. contact@gowrainfosys.comcontact@gowrainfosys.com Post Upgrade status $ cd $ORACLE_HOME/rdbms/admin $ sqlplus "/ as sysdba“ SQL> STARTUP SQL> @utlu112s.sql SQL> @catuppst.sql SQL> @utlrp.sql
  19. 19. $ lsnrctl start Post-Upgrade Steps: Database to 11.2.0.4 Step XX2: Start database Listener EXECUTE DBMS_STATS.UPGRADE_STAT_TABLE('SYS','dictstattab'); Step XX3: Upgrade Statistics Tables Created by the DBMS_STATS Package.c Step XX4: Remove all deprecated parameters contact@gowrainfosys.comcontact@gowrainfosys.com Remove all deprecated parameters Step XX5: Gather Fixed Object Statistics Please create stats on fixed objects two weeks after the upgrade using the below command SQL>EXECUTE DBMS_STATS.GATHER_FIXED_OBJECTS_STATS; Step XX6: Run all the database patch post install instructions.
  20. 20. After the Database Upgrade: • Start database Listener sqlplus "/ as sysdba" @adgrants.sql (or adgrants_nt.sql) [APPS schema name] Run adgrants.sql : Copy $APPL_TOP/admin/adgrants.sql from the administration server node to the database server node. Grant create procedure privilege on CTXSYS Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node. $ sqlplus apps/[APPS password] @adctxprv.sql [SYSTEM password] CTXSYS contact@gowrainfosys.comcontact@gowrainfosys.com 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'); Validate Workflow ruleset On the administration server node, use SQL*Plus to connect to the database as APPS and run the $FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command: $ sqlplus [APPS user]/[APPS password] @wfaqupfix.sql [APPLSYS user] [APPS user]
  21. 21. After the Database Upgrade: $ sqlplus apps/[APPS password] SQL> exec fnd_conc_clone.setup_clean; Deregister the current database server (conditional) If you plan to change the database port, host, SID, or database name parameter on the database server, you must also update AutoConfig on the database tier and deregister the current database server node. Use SQL*Plus to connect to the database as APPS and run the following command: Implement and run AutoConfig Implement and run AutoConfig in the new Oracle home on the database server node. If the database listener of the new Oracle home is defined differently than the old Oracle home, you must also run AutoConfig on each application tier server node to update the system with the new listener. *See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 contact@gowrainfosys.comcontact@gowrainfosys.com *See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 on My Oracle Support for instructions on how to implement and run AutoConfig. Section 3.2 explains how to generate a context file on the database tier. Gather statistics for SYS schema Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node. Note that adstats.sql has to be run in restricted mode. Use SQL*Plus to connect to the database as SYSDBA and use the following commands to run adstats.sql in restricted mode: $ sqlplus "/ as sysdba" SQL> alter system enable restricted session SQL> @adstats.sql $ sqlplus "/ as sysdba" SQL> alter system disable restricted session; SQL> exit;
  22. 22. Re-create custom database links (conditional) Uses the generated script from pre-upgrade step and verify $ sqlplus apps/[apps password] SQL> select db_link from all_db_links; Re-create grants and synonyms - adadmin Oracle Database 11g Release 2 (11.2) contains new functionality for grants and synonyms compared to previous database releases. As a result, you must re-create the grants and synonyms in the APPS schema. On the administration server node, as the owner of the Applications file system, run AD Administration and select the "Recreate grants and synonyms for APPS schema" task from the Maintain Applications Database Objects menu. Restart Applications server processes contact@gowrainfosys.comcontact@gowrainfosys.com 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 Validation Batch Size = 10000 Fix dangling users = Yes Add missing user/role assignments = Yes Update WHO columns in WF tables = No Click "OK" and "Submit".
  23. 23. Section 2: Unsupported Products Since the database was already at 11.2.0.3, not an issue The following EBS products are currently not supported with E-Business Suite Release 12 on Oracle Database 11g Release 2 (11.2.0): Oracle Enterprise Data Warehouse (EDW) Oracle Enterprise Planning and Budgeting (EPB) Section 3: Known Issues The following are known issues with E-Business Suite 12.0 and 12.1 on Database 11.2: PLS-00306: wrong number or types of arguments in call to 'SYNCRN' is encountered when trying to create sales contacts. More information may be found in bug 17441178. FRM-99999: Error 408 occurs when trying to modify HRMS contact information. More information may be found in bug 17446933.may be found in bug 17446933.
  24. 24. Database Version: 11.2.0.4 (Solaris 11.1) Oracle Applications: 12.2.0 (Linux x86-64) ResultResult contact@gowrainfosys.comcontact@gowrainfosys.com
  25. 25. Database Version: 11.2.0.4 (Solaris 11.1) ResultResult contact@gowrainfosys.comcontact@gowrainfosys.com
  26. 26. Database Version: 11.2.0.3 (Solaris 11.1) Oracle Applications: 12.2.0 (Linux x86-64) ResultResult contact@gowrainfosys.comcontact@gowrainfosys.com
  27. 27. Oracle Database Utilities 11g Release 2 (11.2). - Documentation Database Initialization Parameters for Oracle E-Business Suite Release 12 (Doc ID 396009.1) Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1) Using Oracle E-Business Suite Release 12.2 with a Database Tier Only Platform on Oracle 11.2 (Doc ID 1613707.1) Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1) Oracle Database Net Services Administrator's Guide, 11g Release 2 (11.2) - Documentation RefrencesRefrences contact@gowrainfosys.comcontact@gowrainfosys.com Oracle E-Business Suite Setup Guide Release 12.2 - Documentation Oracle E-Business Suite Release 12 Technology Stack Documentation Roadmap (Doc ID 380482.1) Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1) Complete Checklist for Manual Upgrades to 11gR2 (Doc ID 837570.1)
  28. 28. ◦ How to upgrade Oracle Applications database Instance 11.2.0.3 to 11.2.0.4 ◦ Database and Application server running on Single Node ◦ Oracle Database version 11.2.0.4 apply required patches. ◦ Database Post-upgrade Steps ◦ Apps R12.2.0 Post-database upgrade steps SummarySummary contact@gowrainfosys.comcontact@gowrainfosys.com ◦ OATS or RAT, SLOB2 or Hammerora or swingbench are not part of this document, contact us for steps with valid CSI id. ◦ Multinode configuration is not part of this are not part of this document, contact us for steps with valid CSI id.
  29. 29. 11gR2.0.4 RAC Installation and configuration, Non-GNS, ASM, on Oracle Private Cloud with Vmotion on Linux, Solaris, AIX, HP-UX, Linux 6.511.1. Oracle Apps R12.2 /R12.1/11i Migration, Upgrade, re - implementation Reference oracle Installation and configuration documents, and Admin documents, As always, My oracle support for changes and updates with oracle technology. To engage and services from GowraInfosys, Please contact, contact@gowrainfosys.com, Phone: (510) 371-6999 with Oracle databases, oracle applications, installation Contact and other informationContact and other information contact@gowrainfosys.comcontact@gowrainfosys.com contact@gowrainfosys.com, Phone: (510) 371-6999 with Oracle databases, oracle applications, installation configure, update, Migrate, DR, Tuning, Infrastructure sizing and recommendations for Oracle Apps and Oracle database. Remote support for customers Send your Question’s to contact@gowrainfosys.com

×