Upgrade Oracle Applications from 11.5.10.2 to 12.0.

4
Section A: system overview and summary of changes Section B: installation of oracle application (11.5.10.2) on Rhel 4.0 Section C: upgrading to 12.0.0 from 11.5.10.2 Section D: upgrading to 12.0.4 from 12.0.0 Section E: issues faced during upgrade Section F: Job timing Report Section G: Metalink references SECTION A SYSTEM OVERVIEW Version Installation Type Operating system Type Application OS user Database OS user Installed directory 9i Database home 10 g Database home Data top Memory Total Swap Total URL of application system Sysadmin password 11.5.10.2 Oracle application vision instance Enterprise Linux Enterprise Linux AS release 4 Single Node instance applhyd orahyd /home /home/orahyd/hyddb/9.2.0 /orahyd1/db/tech_st/10.2.0 /home/orahyd/hyddata 2064628 kB 4087792 kB http://forms1.ad.infosys.com:8099 sysadmin

SUMMARY OF CHANGES Component Database Developer Application server Client plug-in Java containers Release 11i(11.5.10.2) 9.2 6i 1.0 JINTIATOR JSERV Release 12(12.0.4) 10.2 10g 10.1 SUN JRE OC4J

SECTION B INSTALLING ORACLE APPLICATION 11.5.10.2 ON RHEL 4

Installation steps Step 1 Create a group # groupadd upg Step 2 Create users for maintaining application & database tiers # useradd g upg d /home/oraupg oraupg # useradd g upg d /home/applupg applupg Step 3 Check hostname is set or not # Hostname It should display fully qualified domain name. if not edit the following file # vi /etc/hosts Add the following line <IP address > hostname. Domain name alias Ex: 192.168.0.15 hyddba.ad.infosys.com hyddba Step 4 Set kernel parameters Edit /etc/sysctl.conf and add following parameters # vi /etc/sysctl.conf Kernel =100 1024 100 100 Kernel.shmmax = (half size of RAM) Kernel.shmmni = 100 Fs.file-max =65536 Net.ipv4.ip_local_port_range =1024 65000 Step 5 File descriptor entry in /etc/security/limits.conf # vi /etc/security/limits.conf Hard nofile 65535 Soft nofile 4096 Step 6 Set the kernel entry in both users bash profiles # su oraupg $ vi .bash_profile LD_ASSUME_KERNEL=2.4.19

# su - applupg $ vi .bash_profile LD_ASSUME_KERNEL=2.4.19 Final Check list for installation 1) Kernel version Kernel version should be 2.6.9-5.EL To check kernel version # uname r 2) Perl version Perl version should be 5.0035 above To check perl version # Perl v 3) Check operating system memory RAM should be 1 GB or above To check RAM # cat /proc/meminfo Or # grep Memtotal /proc/meminfo To check Swap # cat /proc/meminfo Or # grep SwapTotal /proc/meminfo 4) Check os tmp space /tmp free space should be 2.0 GB above # df h /tmp 5) Check required packages installed or not To check whether package installed or not # rpm qa| grep <package name> Following packages are required to install 11.5.10.2 on RHEl 4.0

- Compat-db-4.1.25-9 compat-gcc-32-3.2.3-47.3 compat-gcc-32-c++-3.2.3-47.3 compat-oracle-rhel4-1.0-5 compat-libcwait-2.0-2 compat-libgcc-296-2.96-132.7.2 compat-libstdc++-296-2.96-132.7.2 compat-libstdc++-33-3.2.3-47.3 xorg-x11-deprecated-libs-devel-6.8.1-23.EL xorg-x11-deprecated-libs-6.8.1-23.EL - Openmotif-2.1.30-x If any of packages are not installed already, apply package by using rpm # rpm ivh <package name>

6) Disk Space Requirements Stage area 24 GB Single-Node installation needs Application tier file system 26 GB (includes iAS/8.0.6 ORACLE_HOME, COMMON_TOP, and APPL_TOP) Database tier file system 31 GB (Fresh database) Database tier file system 65 GB (Vision Demo) Language Files 10GB per language

7) check required os utilities are installed or not # which cc ld make ar ksh gcc 8) Check OS version #vi /etc/issue 9) Check DISPLAY #echo $DISPLAY (if not set) #export DISPLAY=hostname: 0.0 If you met all above requirements, then you can start installation by invoking rapidwiz To start Installation: # cd /stage_apps/unzip_stag/startCD/Disk1/rapidwiz #. /rapidwiz This will bring rapidwiz wizard home page through you can perform Complete installation

SECTION C UPGRADING ORACLE APPLICATION TO 12.0.0 FROM 11.5.10.0

THE PRE-UPGRADE PROCESS

Step 1:- Apply 11i.AD.I If you have not previously done so, apply the 11i.AD.I minipack on all application tier nodes. It must be present in your system in order to upgrade to Release 12 To check Ad patch set level SQL> SELECT PATCH_LEVEL FROM FND_PRODUCT_GROUPS WHERE PATCH_LEVEL LIKE %AD%;

Step 2:- Run TUMS utility

TUMS is a utility to help customers to reduce the number of steps in the upgrade. It looks at customers specific situation, and identifies which steps are relevant for that customer. The upgrade manual script (TUMS) is used to create to create a report that lists the upgrade steps that do not apply to the oracle application installation. You can ignore these steps Apply patch 5120936 You need to download and apply the TUMS 5120936 patch using adpatch utility to generate the TUMS report Once the patch is applied successfully the adtums.sql script is used to generate report. $ cd $AD_TOP/patch/115/sql $ sqlplus <apps username>/<apps password> @adtums.sql Note: To apply above patch your AD level should be AD.i5 or above

Step 3:- Back up database, Applications Make a cold backup of the Oracle Applications database. If you encounter problems during the upgrade process, you can use this backup to restore your system to the same state as before you began the upgrade

Step 4:- Convert to Multiple Organizations architecture (required) Multiple Organizations architecture supports performance improvements across all Oracle Applications. It also supports Multiple Organizations Access Control, which enables an Applications responsibility to access multiple operating units if desired. Release 12 requires that Multiple Organizations be enabled. If you have not done so already, you must convert to this architecture now. To check your system is Multi-Org enabled or not, execute following sql $ cd $AD_TOP/sql $ sqlplus <apps username>/<apps schema password> @adutlconf.sql Note: You can use the Metalink note DOC ID: 210193 FOR converting to the multiple org

Step 5:- Drop event alert triggers in custom schemas If you have event alert database triggers in custom schemas then you need to drop the same. You can drop them using the script alrdtrig.sql located at ALR_TOP/patch/115/sql.if you dont have any event alert triggers in the custom schemas then you can ignore this step. Re-create the triggers after the upgrade is complete Step 6:- Review sizes of old and new tablespaces Before starting upgrade you must ensure that you have enough space in tablespaces.if you don not have enough space, you need to add more space in the tablespace Note: You can go through the Matalink note 399362.1 for sizing on various tablespaces

Step 7:- Run AD preparation scripts (required) To prepare your system for the Oracle Applications Tablespace Model (OATM) functionality in Release 12, you must run some preparation scripts. Download and unzip patch 5726010. Follow the instructions in the readme for running these scripts: adgncons.sql The tablespace model for Release 12 (OATM) is based on database object type rather than product affiliation. The adgncons.sql script prepares adcrtbsp.sql, configures the database to hold the new products to be added during the upgrade, and switches your system to use the new tablespace model. $ sqlplus apps/apps @adgncons.sql apps apps adcrtbsp.sql Generated by adgncons.sql, this script creates the new tablespaces, allocates unlimited tablespace to all APPS users, updates fnd_product_installation table with correct data and index tablespace information, assigns default tablespace to all APPS users, and sets the new_ts_mode flag in fnd_product_groups to Y.

$ sqlplus system/manager @ adcrtbsp.sql

adgrants.sql Grants SYS privileges needed by Applications, and creates required views in SYS. $ sqlplus /as sysdba @ adgrants.sql APPLSYS

Step 8:- Gather schema statistics for CBO (required) Release 12 employs cost-based optimization, which examines FND table statistics to determine the most efficient access paths and join methods for executing SQL statements. These statistics are gathered by the FND_STATS process, which you initiate by running the Gather Schema Statistics concurrent program From your Release 11i APPL_TOP, complete the following steps: 1. Log in to Oracle Applications with the System Administrator responsibility. 2. Navigate to the Submit Request window (Request > Run) 3. Submit the Gather Statistics program THE UPGRADE PROCESS

Step 9:- Run Rapid Install for creating the file system You use the Rapid Install wizard to lay down the file system and install the new technology stack for your Release 12 Oracle Applications system. The wizard collects configuration parameters and stores them in a configuration file (config.txt) in the Applications database. When you run Rapid Install, it uses these values to lay down the file system structure and technology stack components for your configuration. As it runs, it creates a context file (<CONTEXT_NAME>.xml) that contains all the parameters that describe your system. This context file is created and managed by AutoConfig. Run rapidwiz to create R12 code tree The installation will install R12 applications components and the database home Select upgrade to Oracle Applications R12 Select upgrade actions screen Select create upgrade file system enter the parameters required to set up your new environment Run rapid install Here are the screen shots for the same

The Installation creates APPL_TOP, COMMON_TOP, INST_TOP and 10g Oracle Home

Step 9:- Disable AOL Audit Trail

If you use the Oracle Applications Object Library Audit Trail feature, you must disable it before the upgrade. From the System Administrator responsibility under the 11i APPL_TOP, navigate to Security > Audit Trail > Groups. In the Audit Groups window, set the Group State field to Disable - Prepare for Archive for each audit group defined. Run the Audit Trail Update Tables report from the Submit Requests window (Requests > Run). If you plan to re-enable auditing after the upgrade, archive and purge the shadow tables now. Data changes made after implementing this step are not audited. Step 10:- Shutting down middletier Since we would be doing the database upgrade in the next step so shutdown all middle tier in both 11i and R12 instance Step 11:- Upgrade your database to Oracle 10g Release 2 Step1: Before you start upgrade you have to check your system for any necessary changes. The pre-upgrade tool provide information about the following

1. 2. 3. 4. 5.

The SYSAUX tablespace Log files sizing Tablespace sizes Initializations parameters database versions and compatibility levels and also time estimates

To start pre-upgrade information tool run the following (Note: you should run this step from 9i ORACLE_HOME) #sqlplus /as sysdba SQL>spool list SQL>@$ORACLE_HOME/rdbms/admin/utlu102i.sql Step2: Before proceeding with upgradation process, ensure that you have backup of your database. Step3: Copy your current init.ora file to its default location into the new oracle database10g release home($ORACLE_HOME/dbs) and you should also make changes that pre-upgradation tool recommendations. db_file_multiblock_read_count - Remove this parameter. (this is not required). _db_file_optimizer_read_count = 8 (default setting is 8. Keep default setting). job_queue_processes (set the value of this parameters equal to number of CPUs). parallel_max_servers (set the value of this parameters equal to twice the number of CPUs). pga_aggregate_target (refer to metalink note ID 396009.1 for recommended value).

Note: Once the upgrade process completes, reset the parameters back Step4: Shutdown the current database if it is running and startup it under new oracle home. Now you must use new startup upgrade command to startup your database. $ sqlplus /as sysdba SQL>startup upgrade Step5: Once you have brought up database instance you can create the SYSAUX tablespace (As per pre-upgrade tool). SQL>create tablespace SYSAUX datafile /oraupg/citihyddata/sysaux.dbf size 500M reuse extent management local segment space management auto online; Step6: Make sure that you logged in as user with sysdba privilege and run the upgrade script from new release oracle home environment. SQL>@$ORACLE_HOME/rdbms/admin/catupgrd.sql Step7: After completion of above step, we need to check invalid objects. SQL>select owner, count (*) from dba_objects where status=INVALID group by owner; Step8: We can recompile all invalidated oracle database objects using utlrp.sql, as below

SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql Step9: After completion of upgradation process, you must run the post upgrade status tool SQL>@$ORACLE_HOME/rdbms/admin/utu102s.sql Step10: You can now shutdown and restart the instance. So you are ready for normal database operation on new release. SQL>shutdown immediate; SQL> startup

Step12:- Updating the int.ora Since we would be upgrading the database with the R12 patches in the upcoming section so it is required to change init.ora parameters of the database for any performance bottlenecks Note: you can refer the Mata link note 396009.1 for the details of the initialization parameters

Step13:- Disable custom triggers, constraints, and indexes Disable custom triggers or constraints on Oracle Applications tables. Re-enable these triggers after the upgrade. If you have custom indexes on Applications tables, determine whether they can affect performance during the upgrade, and drop them if necessary. If you are not sure, it is best to drop the indexes and add them after the upgrade, if the new release has not created a similar index.

Step14:- Drop MRC schema

All programs and reports now use the APPS schema. Because the MRC_APPS schema is no longer needed, dropping it frees space and reduces processing overhead during the upgrade. If you have not previously done so, drop the MRC schema now. $ cd APPL_TOP/admin$ sqlplus <SYSTEM username>/<SYSTEM password> @addrpmrc.sql \ <APPLSYS username> FORCE

Step15:- Ensure that Maintenance Mode is enabled

Maintenance Mode restricts logons and the type of operations that the system can perform. Make sure that Maintenance Mode is enabled before you continue. 1. From the AD Administration Main Menu, choose the Change Maintenance Mode option. 2. The Change Maintenance Mode menu displays the current Maintenance Mode status at the top of the screen. The status should be disabled at this point. 3. Select Option 1, Enable Maintenance Mode.

Step16:- Apply Release 12 AD minipack

Download and unzip the R12.AD.A minipack (4502962). Use AutoPatch to run it On all application tier server nodes on your Release 12 APPL_TOP.Before applying patch make sure that the maintenance mode is enabled Note: To know more about above patch you refer 401424.1 metalink note SQL> SELECT PATCH_LEVEL FROM FND_PRODUCT_GROUPS WHERE PATCH_LEVEL LIKE %AD%; 12.AD.A Step17:- Run the American English upgrade patch driver To bring your database to the full Oracle Applications Release 12 level, use AutoPatch to run the (American English) unified driver (u4440000.drv). It is located in $AU_TOP/patch/115/driver. Run the driver on the administration server node on your Release 12 APPL_TOP using the following commands: $ adpatch options=nocopyportion, nogenerateportion After completion of above check log files for any errors, if you did not found any errors check the application version. SQL> select release_name from fnd_product_groups 12.0.0

Step18:- Run the NLS upgrade patch driver

If American English is the only language that is active in your system, you can omit this step. After you have successfully applied the American English unified driver, download the NLS Release 12 patch (4440000) for each active language in your system, and run each driver (u4440000.drv) on your Release 12 APPL_TOP. Note that the NLS patch driver has the same name as the American English patch driver. If you have several languages to download and run, you can merge the patches and apply them as a single, merged patch.

Step19:- Apply latest product patches Determine the latest product-specific patches. Then, download the American English patches. Using AD Merge Patch, create a merged patch and apply it to your Release 12 APPL_TOP. Step20:- Disable Maintenance Mode Maintenance mode controls the system downtime period by managing user logons. To disable maintenance mode, use the Change Maintenance Mode menu in AD Administration. 1. From the AD Administration Main Menu, choose the Change Maintenance Mode option 2. The Change Maintenance Mode menu displays the current Maintenance Mode status at the top of the screen. It should be enabled. 3. Select Option 2, Disable Maintenance Mode. Step21:- Reset init.ora parameters Reset the init.ora parameters which were changed before the upgrade Note: you can refer the matalink note 396009.1 for the details of the initialization parameters

Step22:- Back up Oracle Applications Have the system administrator back up the Oracle Applications product files. On a server or standalone machine, have the database administrator back up the Oracle Applications database.

THE POST-UPGRADE PROCESS Step23:- Configure and start server processes When you ran Rapid Install in the Prepare for the Upgrade section of Chapter 2, it created and stored an instance-specific context by replacing system variables you entered on the wizard screens with the specific values you saved in the configuration file (config.txt). At this point in the upgrade, you point Rapid Install to the Applications context file. Rapid Install (using AutoConfig) updates your system configuration using the values it finds in the context file. Rapid Install creates the appropriate server process control scripts and starts all server processes, including the concurrent managers. Any concurrent programs created during the upgrade run automatically at this point. Concurrent processing (CP) may run PLSQL (inside of the database) that creates output and log files using the utl_file package. On all CP nodes, ensure that the $APPLPTMP environment variable is set to the first directory listed in the UTL_FILE_DIR parameter from the databases init.ora. If you use a RAC database, $APPLTMP should point to a directory on a shared file system visible to all the RAC nodes. This ensures that CP can locate the output and log files created from PLSQL. 1.Update the RDBMS ORACLE_HOME file system with AutoConfig files. On the application tier (as the applhyd user): Log on to the APPL_TOP environment (source the environment file). Run the following Perl script to create appsutil.zip in <INST_TOP>/admin/out. perl <AD_TOP>/bin/admkappsutil.pl On the database tier (as the ORACLE user): Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>. cd <RDBMS ORACLE_HOME> unzip -o appsutil.zip 2. Run AutoConfig on the database tier nodes. <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh 3.Start Rapid Install by typing rapidwiz on the command line. Click Next on the Welcome screen to move to the Wizard Operation screen. 4.Select the Upgrade to Oracle Applications Release 12 option and click Next. 5. On the Select Upgrade Action screen, select Configure Upgraded Release 12 Instance. 6.In the associated screen flow, complete the directory path to point Rapid Install to the Applications context file. It is located in <APPL_TOP>/admin/<CONTEXT_NAME>.xml. Enter the directory directly in the text box, or click Browse and highlight the path in the directory.

7. For security reasons, the APPS password is not saved in the context file. Enter it at the Rapid Install prompt on the Review Application User Information screen. Click Next. Here are the screen shots for the same

After completion of above steps it will automatically start all application services

Step24:- Reset ORACLE schema passwords During the upgrade, Rapid Install preserves the passwords that you set previously for existing products. However, as it creates a schema for each new product installed, it sets up a default password derived from the product abbreviation (short name). To maintain product security, reset these default passwords now. Use the Oracle Users window from the System Administrator responsibility Step25:- Reapplying customizations If you have done any customizations in oracle application you need to integrate all of them at this stage. Though it may be done by functional consultants and oracle application developers but an apps dba is often required to integrate these customizations with the apps schema Step26:- Sanity testing Before releasing environment to the users, perform complete sanity testing of environment and ensure that all middle tiers are running and you are able to navigate properly in without any issue 1) Check all services status from backend as well as front end. 2) Perform aoljsetup test with following URL http://forms1.ad.infosys.com:8099/OA_HTML/jsp/fnd/aoljtest.jsp 3) Submit Active users concurrent program and see the output If all above tests went through we can release environment to users

SECTION D UPGRADING ORACLE APPLICATION TO 12.0.4 FROM 12.0.0

Step 1:- Back up database, Applications Make a cold backup of the Oracle Applications database. If you encounter problems during the upgrade process, you can use this backup to restore your system to the same state as before you began the upgrade

Step 2: Apply Release 12.0.4 AD minipack Download and unzip the apply R12.AD.A.DELTA.4 (6510214) Use AutoPatch to run It On all application tier server nodes on your Release 12 APPL_TOP.Before applying patch make sure that the maintenance mode is enabled SQL> SELECT PATCH_LEVEL FROM FND_PRODUCT_GROUPS WHERE PATCH_LEVEL LIKE %AD%; 12. AD.A.4 Step 3: Download and apply RUP4 (6435000) patch

12.0.4 Is also called as Release 12 Update 4 or RUP4 and cumulative patchset (include 12.0.1, 12.0.2, 12.0.3). Use Autopatch to run it on all application tier server nodes on your Release 12 APPL_TOP. Before applying patch make sure that the maintenance mode is enabled After completion of above patch check the patch log files for any errors and also check application version SQL> select release_name from fnd_product_groups 12.0.4 Step 4: Bring database context to 12.0.4 code 1 .Update the RDBMS ORACLE_HOME file system with AutoConfig files. On the application tier (as the applhyd user): Log on to the APPL_TOP environment (source the environment file). Run the following Perl script to create appsutil.zip in <INST_TOP>/admin/out. $ perl <AD_TOP>/bin/admkappsutil.pl On the database tier (as the ORACLE user) Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>. cd <RDBMS ORACLE_HOME> unzip -o appsutil.zip

2. Run AutoConfig on the database tier nodes. <RDBMS ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh

Step5: Sanity testing Before releasing environment to the users, perform complete sanity testing of environment and ensure that all middle tiers are running and you are able to navigate properly in without any issue 1) Check all services status from backend as well as front end.

2) Perform aoljsetup test with following URL

http://forms1.ad.infosys.com:8099/OA_HTML/jsp/fnd/aoljtest.jsp 3) Submit Active users concurrent program and see the output If all above tests went through we can release environment to users

SECTION E

Issues Faced during upgrade process

We faced lot of issues during upgrade process. Issues faced during 12.0.0 maintenance patch (4440000) 1) /usr/tmp permission error All workers failed due to the insufficient permissions on /usr/tmp while executing plsql code. Solution: we gave 755 permissions to /usr/tmp directory $ chmod R 755 /usr/tmp End result: problem solved 2) ORA-03114: not connected to ORACLE, SP2-0359: memory exhausted All workers were failed. Worker is not getting the memory for server process at OS Solution: we increased size of sga_target to 800m, previously it was 520m End result: problem solved 3) ORA-29875: failed in the execution of the ODCIINDEXINSERT routine ORA-20000: Oracle Text error: DRG-50857: oracle error in textindexmethods: ODCIIndexInsert ORA-20000: Oracle Text error: DRG-10602: failed to queue DML change to column for in Package CS_ServiceRequest_PVT procedure Create_ServiceRequest All workers failed due to the above problem. Solution: Apply 5005469 patch by using OPatch utility. For more information About this patch and above error read metalink doc (373363.1) End result: problem solved 4) ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

All workers either have failed or are waiting Actually problem is the value for environment variable NLS_LANG is different than the database character set (NLS_CHARACTERSET) when invoking FNDLOAD Solution: Verify NLS_LANG setup in the Autoconfig Context file. Edit the context file using Oracle Applications Manager(OAM) or Context Editor and find value for NLS_LANG: If the database characterset is UTF8 it should be: <NLS_LANG oa_var="s_tools_nlslang">American_America.UTF8</NLS_LANG> If NLS_LANG has different value than expected please change it. Then execute Autoconfig and make sure it was successful To know more information about issue and solution you can refer Doc id (452095.1) On metalink End result: problem solved Issues faced while login to 12.0.0 instance

1) During 11i to R12 upgrade post upgrade step of running rapidwiz fails on Login following error: Login Page ----------checking URL = http://<hostname.domainname>:<port>/OA_HTML/AppsLogin RW-50016: Error: - {0} was not created: File = {1} Solution: Following workarounds can be followed in sequence: 1) Try to login with following URL: http://<hostname.domainname>:<port>/OA_HTML/fndvald.jsp? username=sysadmin&password=<sysadmin_password>

Page with

If main home page appears then try to click any responsibility. If resposibilities are not working i.e. while clicking on responsibility page getting blank or getting "The page cannot be displayed" then clear the cache and compile jsp's as given in Step 2. If Step 1 doesn't work then move to Step2: 2) Clear the cache and compile jsp's Remove _pages under $COMMON_TOP

cd $FND_TOP/patch/115/bin ./ojspCompile.pl --compile --flush -p 2 Try to login again as per Step 1 End result: problem solved Issues faced during 12.0.4(RUP4) maintenance patch (6345000)

1) CREATE INDEX APPLSYS.FND_CONCURRENT_QUEUES_N2 ON APPLSYS.FND_CONCURRENT_QUEUES (CONCURRENT_QUEUE_ID) LOGGING STORAGE (INITIAL 4K NEXT 32K MINEXTENTS 1 MAXEXTENTS UNLIMITED PCTINCREASE 0 FREELIST GROUPS 4 FREELISTS 4) PCTFREE 0 INITRANS 11 MAXTRANS 255 COMPUTE STATISTICS TABLESPACE APPLSYSX AD Worker error: The following ORACLE error: ORA-00054: resource busy and acquire with NOWAIT specified Actually problem is worker unable to execute adcmgr.odf because of lock on FND_CONCURRENT_REQUESTS table. Solution: so I restarted database server, but problem is still remain. Then we skipped the adworker and we did the job manually by using adodfcomp compiler as follows $ adodfcmp userid=applsys/apps mode=tables odffile=/applhyd1/apps/apps_st/appl/fnd/12.0.0/patch/115/odf/afcmgr.odf touser=apps/apps priv_schema=system/manager changedb=yes End result: problem solved

2) Start uploading... Target file: PAYCARL2ERR.rtf Creating a new record in XDO_LOBS: PAYCARL2ERR.rtf java.sql.SQLException: ORA-01653: unable to extend table XDO.XDO_LOBS by 16 In tablespace APPS_TS_TX_DATA Actually this problem arise due to the insufficient free space in APPS_TS_TX_DATA tablespace Solution: we added two datafiles with 750m to APPS_TS_TX_DATA tablespace End result: problem resolved 3) sqlplus -s APPS/***** @/applhyd1/apps/apps_st/appl/xla/12.0.0/patch/115/sql/xlaaxuar.sql &un_ax &batchsize Session altered.

DECLARE * ERROR at line 1: ORA-12801: error signaled in parallel query server P004 ORA-00600: internal error code, arguments: [qerhjNewFlushedPartitions1], [], [], [], [], [], [], [] ORA-06512: at line 566 Here actual problem with Temp segments. Solution: we added two more datafiles to temporary tablespace, then we resolved the problem End result: problem solved

SECTION F Job timing report of 12.0.0 upgrade

Sno

Task name

Elapsed Time 19 min 3 min 4hr 30 min N/A N/A 5min 6 min

1 2 3 4 5 6 7

Apply 11i.AD.I Run TUMS utility Back up database, Applications Convert to Multiple Organizations architecture Drop event alert triggers in custom schemas Review sizes of old and new tablespaces Run AD preparation scripts

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Gather schema statistics for CBO(estimate % is 10) Run Rapid Install for creating the file system Disable AOL Audit Trail Shutting down middle tier services Upgrade your database to Oracle 10g Release 2 Updating the int.ora Disable custom triggers, constraints, and indexes Drop MRC schema Ensure that Maintenance Mode is enabled Apply Release 12 AD minipack Run the American English upgrade patch driver Run the NLS upgrade patch driver Apply latest product patches Disable Maintenance Mode Reset init.ora parameters Back up Oracle Applications(db+application) Reset ORACLE schema passwords Reapplying customizations

13 min 47 min N/A 3 min 16 hrs 4 min N/A N/A 2min 28 min 53 hrs N/A N/A 2min 5min 4hr 45 min N/A N/A

26

Sanity testing

7min

Job timing report of 12.0.4 upgrade

Sno

Task name

Elapsed Time 4hrs 30min 14 min 14 hrs 30min 7min 7min

1 2 3 4 5

Back up database, Applications Apply Release 12.0.4 AD minipack Download and apply RUP4 (6435000) patch Bring database context to 12.0.4 code Sanity testing

SECTION G Metalink references for 12.0.4 upgrade

sno 1

Document Id 403339.1

Description Oracle 10gR2 Database Preparation Guidelines for an EBusiness Suite R12 Note E-Business Suite Release 12 Upgrade Sizing and Best Practices Database Initialization Parameters for Oracle Applications Release 12 12 AD.A minipack notes FOR converting to the multiple org Oracle E-Business Suite 12.0.4 Release Update Pack Readme

399362.1

396009.1

4 5

401424.1 210193.1

465776.1

You can access our 12.0.4 instance using following URL

http://forms1.ad.infosys.com:8099 Sysadmin password=sysadmin IP address =172.21.14.171