Sujeet APPS DBA: July 2015

ADOP online Patching utility in R12.2.4

Online patching is the most important new feature in Oracle EBS 12.2. It is the ability to patch a running system without having to take the system down for a significant period of time while the patches are applied. Even you can apply Maintenance Pack 12.2.2 or 12.2.3 or 12.2.4 once you install or upgrade to R12.2.0 base.

It will enable R12.2 PATCH Environment.
Dependancy on opatches. All Opatches must be applied before enabling ADOP.
Missing Opatches will be reported by EBS DB CodeLevel Checker script.
All AD_ZD packages should be valid before enabling them.
To implement Online Patching Run reports/scripts mentioned in Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 [1531121.1]
Once you enable ADOP i.e. Online Patching you cannot apply any patches through ADPATCH.
If you still want to apply any patch via adpatch, source ENABLE_ADPATCH=yes. (if oracle recommends)
All patches applied using adop utility will be applied to PATCH environment i.e. fs2.
When you want to make the patches live you can execute adop using cutover phase. It will switch filesystems.
To synchronize both filesystems i.e. fs1 and fs2 you can execute adop using fs_clone phase.

‘adop’ is the utility you use to apply patches in R12.2

Important parameters and commands related to ADOP are documents below.

ADOP PATCHING PARAMETERS DETAILS:

PARAMETER DEFAULT VALUE POSSIBLE-VALUES DESCRIPTION

phase N/A PHASE=PREPARE These are the eight phases in which adop can run. It is most important and mandatory parameter that is used with adop.

You can also club multiple phases in single command like ‘PHASE=PREPARE,APPLY’ although abort and fs_clone need to be run alone and can’t be clubbed.Standard phases:

prepare – Prepare the instance for patch application.

PHASE=APPLY apply – Apply patches (to the patch edition).

PHASE=CUTOVER cutover – Make the patch edition the new run edition.

PHASE=CLEANUP cleanup – Drop obsolete objects and data from old editions. It is run automatically.

PHASE=FINALIZE finalize – Ready the instance for cutover. It is run automatically.

PHASE=ACTUALIZE_ALL actualize_all – Create new copies of all code objects in the patch edition.

PHASE=FS_CLONE fs_clone – Copy the run file system to the patch file system.

PHASE=ABORT abort – Abort the current patching cycle. The abort phase can be run after either the prepare or apply phases have been run, but not after the cutover phase.

loglevel	LOGLEVEL=EVENT	LOGLEVEL=STATEMENT LOGLEVEL=PROCEDURE LOGLEVEL=EVENT LOGLEVEL=WARNING LOGLEVEL=ERROR LOGLEVEL=UNEXPECTED	STATEMENT > for debugging. PROCEDURE > for debugging high level procedures. EVENT > to capture informational messages in normal processing. (default) WARNING > to capture any internal error that is handled by the system and does not affect processing. ERROR > indicates action failed, need to be reviewed, but the system continue processing. UNEXPECTED > indicates an unrecoverable error, requires user intervention before processing can continue.
cleanup_mode	CLEANUP_MODE=STANDARD	CLEANUP_MODE=FULL CLEANUP_MODE=STANDARD CLEANUP_MODE=QUICK	Cleanup processing needs to happen after adop finishes the patching work.Quick mode > shortest execution time, skips non-essential actions Standard mode > All quick mode action + drops covered objects Full mode > All quick mode action + remove all unused code, data, and old editions and takes much longer
finalize_mode	FINALIZE_MODE=QUICK	FINALIZE_MODE=QUICK FINALIZE_MODE=FULL	Quick mode > shortest execution, skips non-essential actions, no gather statistics. Full mode > Gather statistics, may improve performance after cutover, can take an hour extra to complete.
input_file	N/A	INPUT_FILE=<Absolute input_file path>	To specify the name of the input_file supplied to adop. (see details on input_file later in this post)
workers	N/A (depends on number of available CPU cores)	WORKERS=<User-specified-value>	Number of parallel workers used to execute tasks.In earlier released adpatch used to prompt for number of workers. With adop in R12.2, if you want to override the default formula that oracle uses now to calculation number of workers, use the WORKERS parameter. Take care that you don’t specify very high number of workers or else adop will fail.
maxworkers	N/A (depends on number of available CPU cores)	MAXWORKERS=<User-specified-value>	Maximum parallel workers that can be engaged. maxworkers should always be set to greater than the desired number of workers.
runcontextfile	$CONTEXT_FILE	RUNCONTEXTFILE=<Absolute context_file path>	To specify the non-default context file patch in RUN filesystem
patchcontextfile	Standard context file path in patch FS	PATCHCONTEXTFILE=<Absolute context_file path>	To specify the non-default context file patch in PATCH filesystem
patches	N/A	PATCHES=<User-specified-value>For Standard Patch:when>patch directory is a 6- to 8-digit numberPATCHES=<patch_number> For Non-Standard Patch when > patch directory is not a 6- to 8-digit number example NLS patches <patch_number>_<language_code>. > patch driver files are not named *<patchnum>.drv example merged patchesPATCHES=<patch_number>:<driver_file>.drv	This parameter specifies the patches adop needs to apply.Remember the numbered-only patches (standard) and containing-a-colon categories of patch (non-standard) can be mixed.Like:PATCHES= <patch_number1>, <patch_number2>:<driver_file2>.drv
defaultsfile	$APPL_TOP/admin/<SID>_patch/adalldefaults.txt	DEFAULTSFILE=<Absolute defaults_file path>	Default file locations on both the run APPL_TOP and patch APPL_TOP is: $APPL_TOP/admin/<SID>_patch/adalldefaults.txtIn case you have created your own defaults file and want to use that instead, then use this parameter.
patchtop	$NE_BASE/EBSapps/patch	PATCHTOP=<Absolute patch_location_file path>	Default patch_top location is below.$NE_BASE/EBSapps/patchIf you want to keep your patches in some other lcoation, then you need to use this patrameter to let ADOP know where to search for patches pointed by ‘patches’ parameter.If you have a multi-node environment, you must download and unzip the patches (under $APPL_TOP_NE/EBSapps/patch) on the respective nodes.
merge	MERGE=NO	MERGE=NO MERGE=YES	In R12.2, oracle has integrated patch merging action in the patching command itself. In earlier releases we used to first merge patches using admrgpch command.By using MERGE=YES option ADOP will merge all the unified driver files into a single driver file.
abandon	ABANDON=NO	ABANDON=YES ABANDON=NO	If the patch you are applying went into error, you have two option when you start the adop utility again.1) you corrected error and want to continue with previous adop session:ABANDON=NO2) you decided that you don’t want to correct issue for now and want to abandon the previous adop session:ABANDON=YES
restart	RESTART=YES	RESTART=NO RESTART=YES	If the patch you are applying went into error and you corrected the issue and want to restart the previous patching session.It is just the reverse of ABANDON parameter.Remember ABANDON and RESTART will always have opposite value.
flags	N/A	FLAGS=AUTOSKIP	Use “flags=autoskip” in conjunction with the “abandon=no” parameter at the command-line to skip a failing patching step to “Continue as if a patch were successful”. You need to review the “autoskip” log that gets generated during the patching cycle in order to make sure that their were no errors and to take required actions in case of any errors
allnodes	ALLNODES=NO	ALLNODES=NO ALLNODES=YES	This parameter comes into picture when you have multi node setup. If you want to run adop on all nodes then use ALLNODES=YES.
action	ACTION=DB	ACTION=DB ACTION=NODB	Use this parameter to specify whether to perform database actions or skip. For example if you are in a multi-node environment and adop has already updated the database so when running on other node just use ACTION=NODB to save time.Remember when you are using ‘allnodes=yes’ in a multi-node ‘action=db’ must be specified.
apply	APPLY=YES	APPLY=YES APPLY=NO	To run adop in test mode (without applying any patches),specify apply=no
autoskip	AUTOSKIP=YES	AUTOSKIP=YES AUTOSKIP=NO	This parameter control whether the user is prompted about skipping actions in non-interactive patching. This is specifically useful when you are applying patches in multi node setup.
mtrestart	MTRESTART=YES	MTRESTART=YES MTRESTART=NO	This parameter specify whether to restart application tier services after cutover phase or not.
cm_wait	CM_WAIT=INFINITE (will wait forever)	CM_WAIT=<user_specified_number	Specifies the number of minutes to wait until the ICM will be forced down.
allowcoredump	ALLOWCOREDUMP=NO	ALLOWCOREDUMP=NO ALLOWCOREDUMP=YES	To specify that a core dump will be generated if adop crashes.
analytics	ANALYTICS=NO	ANALYTICS=NO ANALYTICS=YES	To specify that a report will be generated that can help debug certian adop issue.
preinstall	N/A	PREINSTALL=Y	This mode is used only if the patch readme instructs. Generally this mode is used during the upgrade process to update AD utilities, apply pre-upgrade patches, or work around other patching issues.It will Compares version numbers, Copies files, Relinks FND and AD executables, Saves patch information. It also runs autoconfig if required.The dual file system in Release 12.2 means that there is no need to shut down application tier services before running AutoConfig.
-help	N/A	N/A	Shows the help screen.
-status-status -detail	Latest Session	-STATUS (for latest session) -STATUS <SESSION_ID> (for specific session)	Display status of the latest adop session.Use ‘adop -status -detail’ for detailed info
-examples	N/A	N/A	Displays some commonly used adop ample commnads

ADOP PATCHING EXAMPLE COMMANDS:

‘Complete’ adop patching cycle using parameters input through command line (INTERACTIVE MODE)

So in R12.2 we have complete patching cycle to follow to apply a patch. These are set of commands which needs to executed in specific order.

You must set the environment by executing the run file system environment file.

$ . <run APPL_TOP path>/APPS<CONTEXT_NAME>.env

1) adop phase=prepare
2) adop phase=apply patches=<patch_number1>,<patch_number2> workers=<number_of_worker>
3) adop phase=finalize workers=<number_of_worker> (called automatically)
4) adop phase=cutover workers=<number_of_worker>
5) adop phase=cleanup (called automatically)

Running all phases in single command:

adop phase=prepare,apply,finalize,cutover,cleanup patches=<patch_number1>,<patch_number2>

All the phases need to be completed and you can’t skip any of these. For example, if you try to skip prepare phase, you may get error message like “Apply phase can only be run while in a patching cycle, i.e. after prepare phase.”

adop patching cycle in NON-INTERACTIVE mode

During apply phase, Non-interactive patching is a way to save time by avoiding some of the prompts and automating the patching process.You can apply patches in non-interactive way by using a defaults file that contains much of the information you would have supplied at the adop prompts and by creating another file known as input file. Then, when you run adop, you specify the name of the input file. The location of the defaults file will also need to be included in the input file.

$ adop phase=apply input_file=<input_file.txt>

Location of Default file on both the run APPL_TOP and patch APPL_TOP is:

$APPL_TOP/admin/<SID>_patch/adalldefaults.txt

Just in case this file gets corrupted or lost, you can run AutoConfig and it will automatically instantiate a new copy.

NOTE: In R12.2, you don’t need to create this defaults file. The file is already created by oracle process. However you need to create one ‘input file’ to use with adop (The defaults file is not specified on the adop command line. It is the input file.)

The input_file contents should include the following required parameters:

patches=<patch number>
workers=<number of workers>
patchtop=<directory where patches are staged>
defaultsfile=<defaults file on patch APPL TOP>

To skip specific patching portion or action

During apply phase:

adop phase=apply options=nodatabaseportion, nogenerateportion

In above command we are instructing adop to not run database and generate portion.

Other options can be

options=noactiondetails — if you do not want the details to be printed.

options=noautoconfig — if you are applying a number of patches in sequence and want to run
AutoConfig only once in the end.

option=nocheckfile –to turn off the checkfile feature. Using checkfile adop skip some actions which are already done.

option=nocompiledb –when applying multiple NLS, documentations patches etc

option=nocompilejsp –when applying multiple NLS, documentations patches etc

option=nocopyportion –for skipping copy portion of the patch

To apply patch in ‘HOTPATCH’ mode

During apply phase:

# adop phase=apply options=hotpatch

Upgrade Oracle EBS R12.1.3 to R12.2.4

First Upgrade R12.1.3 to R12.2.0 After that Upgrade R12.2.0 to R12.2.4..

Step:-1

Upgrade Oracle EBS R12.1.3 to R12.2.0

http://sujeetdba.blogspot.in/2015/07/upgrade-oracle-ebs-r1213-to-r1220.html

Step:-2

Upgrade Oracle EBS R12.2.0 to R12.2.4

Oracle strongly recommends that you always obtain the latest OPatch utility available from My Oracle Support via Patch 6880880.
Technology bug fixes can be provided by different patch types: for example, Bundle Patch, Merge Patch, and Database Patch Set Update. A given patch may include more than one fix.
In certain cases, you may be able to obtain the recommended technology patches as part of a set of patches (such as a Critical Patch Update, Database Patch Set Update, or Exadata Bundle) that includes them.
Some technology bug fixes such as Daylight Saving may have a later version that can be installed as an alternative.
If you see a notice that a patch is obsolete or superseded, apply the replacement patch.
The installation path chosen determines which additional patches need to be applied:
- For installations that used a startCD which was also used to install the Oracle Database, you only need to apply patches that were made available in any later startCDs.
- For installations that used a startCD which was not used to create the Oracle E-Business Suite Release 12.2 Database (an existing Oracle Database was used), you need to obtain and install all the patches listed in Section 2, Table 1.
More information on patching the technology Oracle Homes is available in My Oracle Support Knowledge Document 1355068.1.
You must ensure that all technology patches are fully applied. Refer to each individual patch readme file for additional details on how to apply that patch; this includes post-install steps that must be run, and any known warnings that can be ignored.
In the event of a patch failure that cannot be resolved, you must contact Oracle Support for assistance.

Environment: Oracle Enterprise Linux 6.5 (64-Bit)
EBS Version : Oracle EBS R12.2.0 (using start CD 12.2.0.48)

Database – 11.2.0.3

Architecture – Single Node

RAM:- 20 GB

Hard-disk:- 2 TB <Dell server>

CPU:- 6

Oracle EBS using start CD R12.2.0.48 then you need to Install minimum number of patches in order to upgrade to R12.2.4.

Step:1

we have need to apply the below patches sequence according to Doc. ID 1594274.1

Note:- Before starting database upgrade, please confirm the below steps.

1.) Application should be down.

2.) Database should be down.

3.) export PATH=$ORACLE_HOME/OPatch:$PATH

4.) which opatch

5.) Skip all those patch which are already applied

check by below command:
$ opatch lsinventory

DATABASE Patch 12.2.0.48 & not included in any startCD

Step:2

Install Oracle RDBMS patches:

[ora@sujeet 16989137]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/16989137_Oct_28_2014_14_29_47/apply2014-10-28_14-29-47PM_1.log

Applying interim patch '16989137' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Backing up files...

Patching component oracle.ctx, 11.2.0.3.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

Verifying the update...

Patch 16989137 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/16989137_Oct_28_2014_14_29_47/apply2014-10-28_14-29-47PM_1.log

OPatch succeeded.

Step:2

[ora@sujeet 17875948]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/17875948_Oct_28_2014_14_33_15/apply2014-10-28_14-33-15PM_1.log

Applying interim patch '17875948' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

Interim patch 17875948 is a superset of the patch(es) [ 16587934 ] in the Oracle Home

OPatch will roll back the subset patches and apply the given patch.

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Rolling back interim patch '16587934' from OH '/u01/ora_test/11.2.0'

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

RollbackSession removing interim patch '16587934' from inventory

OPatch back to application of the patch '17875948' after auto-rollback.

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

Verifying the update...

Patch 17875948 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/17875948_Oct_28_2014_14_33_15/apply2014-10-28_14-33-15PM_1.log

OPatch succeeded.

Step:3

[ora@sujeet 17875948]$

[ora@sujeet 17912217]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/17912217_Oct_28_2014_14_38_04/apply2014-10-28_14-38-04PM_1.log

Applying interim patch '17912217' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Patching component oracle.rdbms, 11.2.0.3.0...

Verifying the update...

Patch 17912217 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/17912217_Oct_28_2014_14_38_04/apply2014-10-28_14-38-04PM_1.log

OPatch succeeded.

Step:4

[ora@sujeet 17912217]$

[ora@sujeet 18419770]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/18419770_Oct_28_2014_14_40_02/apply2014-10-28_14-40-02PM_1.log

Applying interim patch '18419770' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Patching component oracle.rdbms, 11.2.0.3.0...

Verifying the update...

Patch 18419770 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/18419770_Oct_28_2014_14_40_02/apply2014-10-28_14-40-02PM_1.log

OPatch succeeded.

Step:5

[ora@sujeet 18419770]$

[ora@sujeet 18614015]$ pwd

/u01/patch_stage/database/DB/18614015

[ora@sujeet 18614015]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/18614015_Oct_28_2014_14_42_00/apply2014-10-28_14-41-59PM_1.log

Applying interim patch '18614015' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Backing up files...

Patching component oracle.rdbms.dbscripts, 11.2.0.3.0...

Verifying the update...

Patch 18614015 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/18614015_Oct_28_2014_14_42_00/apply2014-10-28_14-41-59PM_1.log

OPatch succeeded.

Step:6

[ora@sujeet 18685209]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/18685209_Oct_28_2014_14_44_11/apply2014-10-28_14-44-10PM_1.log

Applying interim patch '18685209' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Patching component oracle.rdbms, 11.2.0.3.0...

Verifying the update...

Patch 18685209 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/18685209_Oct_28_2014_14_44_11/apply2014-10-28_14-44-10PM_1.log

OPatch succeeded.

Step:7

As per footnote-11 patch "18259911" was Installed. So we need to rollback this patch first Installing patch "19078951".

[ora@sujeet DB]$ opatch lsinventory | grep 18259911

Patch 18259911 : applied on Mon Oct 27 21:54:20 AST 2014

[ora@sujeet DB]$ opatch lsinventory | grep 17461865

[ora@sujeet DB]$ opatch rollback -id 18259911

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/18259911_Oct_28_2014_14_53_03/rollback2014-10-28_14-53-03PM_1.log

RollbackSession rolling back interim patch '18259911' from OH '/u01/ora_test/11.2.0'

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

Patching component oracle.rdbms, 11.2.0.3.0...

RollbackSession removing interim patch '18259911' from inventory

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/18259911_Oct_28_2014_14_53_03/rollback2014-10-28_14-53-03PM_1.log

OPatch succeeded.

Step:8

[ora@sujeet 19078951]$ opatch apply

Oracle Interim Patch Installer version 11.2.0.3.0

Oracle Home : /u01/ora_test/11.2.0

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/ora_test/11.2.0/oraInst.loc

OPatch version : 11.2.0.3.0

OUI version : 11.2.0.3.0

Log file location : /u01/ora_test/11.2.0/cfgtoollogs/opatch/19078951_Oct_28_2014_15_00_03/apply2014-10-28_15-00-03PM_1.log

Applying interim patch '19078951' to OH '/u01/ora_test/11.2.0'

Verifying environment and performing prerequisite checks...

Interim patch 19078951 is a superset of the patch(es) [ 14751895 12849688 ] in the Oracle Home

OPatch will roll back the subset patches and apply the given patch.

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/ora_test/11.2.0')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Rolling back interim patch '14751895' from OH '/u01/ora_test/11.2.0'

Patching component oracle.rdbms, 11.2.0.3.0...

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

RollbackSession removing interim patch '14751895' from inventory

Rolling back interim patch '12849688' from OH '/u01/ora_test/11.2.0'

Patching component oracle.rdbms, 11.2.0.3.0...

RollbackSession removing interim patch '12849688' from inventory

OPatch back to application of the patch '19078951' after auto-rollback.

Patching component oracle.rdbms.rsf, 11.2.0.3.0...

Patching component oracle.rdbms, 11.2.0.3.0...

Verifying the update...

Patch 19078951 successfully applied

Log file location: /u01/ora_test/11.2.0/cfgtoollogs/opatch/19078951_Oct_28_2014_15_00_03/apply2014-10-28_15-00-03PM_1.log

OPatch succeeded.

Step:9

Perform post Installation of all patches after applying all RDBMS Patches:

SQL> @?/sqlpatch/16989137/postinstall.sql

Session altered.

Grant succeeded.

Session altered.

Calling ctx/admin/driacc.plb on 28-OCT-14 03.06.10.208289 PM +03:00

Package body created.

SQL> @?/sqlpatch/17875948/postinstall.sql

Package body created.

No errors.

Calling rdbms/admin/prvtmet2.plb on 28-OCT-14 03.14.49.012276 PM +03:00

Package body created.

Calling rdbms/admin/catmet2.sql on 28-OCT-14 03.14.49.548401 PM +03:00

/SQL procedure successfully completed.

SQL> @?/sqlpatch/18614015/postinstall.sql

Calling rdbms/admin/prvtutil.plb on 28-OCT-14 03.24.58.515625 PM +03:00

Package body created.

Step:10

Install Oracle Fusion Middleware 11.1.1.6 patches

Set oracle home for FMW (11.1.1.6)

[appl@sujeet ~]$ export ORACLE_HOME=/u01/appl_test/fs1/FMW_Home/webtier

[appl@sujeet ~]$ export PATH=/u01/appl_test/fs1/FMW_Home/webtier/OPatch:$PATH

Verify the opatch is set from the proper Oracle Home

[appl@sujeet ~]$ opatch lsinventory

Oracle Interim Patch Installer version 11.1.0.9.9

Oracle Home : /u01/appl_test/fs1/FMW_Home/webtier

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/appl_test/fs1/FMW_Home/webtier/oraInst.loc

OPatch version : 11.1.0.9.9

OUI version : 11.1.0.9.0

Log file location : /u01/appl_test/fs1/FMW_Home/webtier/cfgtoollogs/opatch/opatch2014-10-28_16-05-24PM_1.log

OPatch detects the Middleware Home as "/u01/appl_test/fs1/FMW_Home"

Lsinventory Output file location : /u01/appl_test/fs1/FMW_Home/webtier/cfgtoollogs/opatch/lsinv/lsinventory2014-10-28_16-05-24PM.txt

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

Installed Top-level Products (1):

Oracle WebTier and Utilities CD 11.1.1.6.0

There are 1 products installed in this Oracle Home.

Interim patches (7) :

Patch 16199894 : applied on Tue Oct 28 02:29:40 AST 2014

Unique Patch ID: 16066707

Created on 6 Mar 2013, 12:42:03 hrs US/Pacific

Bugs fixed:

16199894

Patch 14616819 : applied on Tue Oct 28 02:29:23 AST 2014

Unique Patch ID: 15565088

Created on 11 Oct 2012, 12:30:28 hrs US/Pacific

Bugs fixed:

14616819

Patch 10638758 : applied on Tue Oct 28 02:29:05 AST 2014

Unique Patch ID: 14860855

Created on 15 May 2012, 05:32:01 hrs PST8PDT

Bugs fixed:

10638758

Patch 17325559 : applied on Tue Oct 28 02:28:46 AST 2014

Unique Patch ID: 16698102

Created on 19 Aug 2013, 16:11:34 hrs US/Pacific

Bugs fixed:

16856341, 13837241, 13025456, 14110089, 16021044, 14386112, 14345153

14003476, 12959202

Patch 13643211 : applied on Tue Oct 28 02:28:27 AST 2014

Unique Patch ID: 14814441

Created on 2 May 2012, 11:34:23 hrs

Bugs fixed:

13588565, 13104787, 13637410

Patch 12949905 : applied on Tue Oct 28 02:28:07 AST 2014

Unique Patch ID: 14148563

Created on 29 Sep 2011, 11:48:28 hrs PST8PDT

Bugs fixed:

12949905

Patch 7695070 : applied on Tue Oct 28 02:27:50 AST 2014

Unique Patch ID: 11421601

Created on 16 Jun 2009, 21:13:15 hrs PST8PDT

Bugs fixed:

7695070

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

OPatch succeeded.

Step:11

Apply patches on 11.1.1.6 FMW Home

[appl@sujeet ~]$ cd /u01/patch_stage/Apps/Pre_REQS_Apps/17639414

[appl@sujeet 17639414]$ ls

etc files README.txt

[appl@sujeet 17639414]$ opatch apply -jre $ORACLE_HOME/jdk/jre

Oracle Interim Patch Installer version 11.1.0.9.9

Oracle Home : /u01/appl_test/fs1/FMW_Home/webtier

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/appl_test/fs1/FMW_Home/webtier/oraInst.loc

OPatch version : 11.1.0.9.9

OUI version : 11.1.0.9.0

Log file location : /u01/appl_test/fs1/FMW_Home/webtier/cfgtoollogs/opatch/17639414_Oct_28_2014_16_06_40/apply2014-10-28_16-06-39PM_1.log

OPatch detects the Middleware Home as "/u01/appl_test/fs1/FMW_Home"

Applying interim patch '17639414' to OH '/u01/appl_test/fs1/FMW_Home/webtier'

Verifying environment and performing prerequisite checks...

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Backing up files...

Patching component oracle.as.clone.ohs, 11.1.1.6.0...

Verifying the update...

Patch 17639414 successfully applied

Log file location: /u01/appl_test/fs1/FMW_Home/webtier/cfgtoollogs/opatch/17639414_Oct_28_2014_16_06_40/apply2014-10-28_16-06-39PM_1.log

OPatch succeeded.

Step:12

[appl@sujeet 18989444]$ opatch apply

Oracle Interim Patch Installer version 11.1.0.9.9

Oracle Home : /u01/appl_test/fs1/FMW_Home/oracle_common

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/appl_test/fs1/FMW_Home/oracle_common/oraInst.loc

OPatch version : 11.1.0.9.9

OUI version : 11.1.0.9.0

Log file location : /u01/appl_test/fs1/FMW_Home/oracle_common/cfgtoollogs/opatch/18989444_Oct_28_2014_16_12_31/apply2014-10-28_16-12-31PM_1.log

OPatch detects the Middleware Home as "/u01/appl_test/fs1/FMW_Home"

Applying interim patch '18989444' to OH '/u01/appl_test/fs1/FMW_Home/oracle_common'

Verifying environment and performing prerequisite checks...

Interim patch 18989444 is a superset of the patch(es) [ 13947608 ] in the Oracle Home

OPatch will roll back the subset patches and apply the given patch.

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/appl_test/fs1/FMW_Home/oracle_common')

Is the local system ready for patching? [y|n]

User Responded with: Y

Backing up files...

Rolling back interim patch '13947608' from OH '/u01/appl_test/fs1/FMW_Home/oracle_common'

Patching component oracle.jrf.opss, 11.1.1.6.0...

RollbackSession removing interim patch '13947608' from inventory

OPatch back to application of the patch '18989444' after auto-rollback.

Patching component oracle.jrf.opss, 11.1.1.6.0...

Verifying the update...

Patch 18989444 successfully applied

Log file location: /u01/appl_test/fs1/FMW_Home/oracle_common/cfgtoollogs/opatch/18989444_Oct_28_2014_16_12_31/apply2014-10-28_16-12-31PM_1.log

OPatch succeeded.

Step:13

[appl@sujeet 19462638]$ opatch apply

Oracle Interim Patch Installer version 11.1.0.9.9

Oracle Home : /u01/appl_test/fs1/FMW_Home/oracle_common

Central Inventory : /u01/ora_prod/oraInventory

from : /u01/appl_test/fs1/FMW_Home/oracle_common/oraInst.loc

OPatch version : 11.1.0.9.9

OUI version : 11.1.0.9.0

Log file location : /u01/appl_test/fs1/FMW_Home/oracle_common/cfgtoollogs/opatch/19462638_Oct_28_2014_16_16_48/apply2014-10-28_16-16-47PM_1.log

OPatch detects the Middleware Home as "/u01/appl_test/fs1/FMW_Home"

Applying interim patch '19462638' to OH '/u01/appl_test/fs1/FMW_Home/oracle_common'

Verifying environment and performing prerequisite checks...

Interim patch 19462638 is a superset of the patch(es) [ 14588599 ] in the Oracle Home

OPatch will roll back the subset patches and apply the given patch.

All checks passed.

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Backing up files...

Rolling back interim patch '14588599' from OH '/u01/appl_test/fs1/FMW_Home/oracle_common'

Patching component oracle.as.common.clone, 11.1.1.6.0...

Updating jar file "/u01/appl_test/fs1/FMW_Home/oracle_common/jlib/cloningclient.jar" with "/u01/appl_test/fs1/FMW_Home/oracle_common/.patch_storage/14588599_Sep_27_2012_15_42_28/files//jlib/cloningclient.jar/oracle/as/clone/cloner/component/j2ee/constants/J2EEIntrospectorConstants.class"

RollbackSession removing interim patch '14588599' from inventory

OPatch back to application of the patch '19462638' after auto-rollback.

Patching component oracle.as.common.clone, 11.1.1.6.0...

Verifying the update...

Patch 19462638 successfully applied

Log file location: /u01/appl_test/fs1/FMW_Home/oracle_common/cfgtoollogs/opatch/19462638_Oct_28_2014_16_16_48/apply2014-10-28_16-16-47PM_1.log

OPatch succeeded.

Step:14

Install Oracle 10.1.2.3 Forms & Reports Patches

Set the Environment variable for 10.1.2 ORACLE HOME

[appl@sujeet 18186693]$ pwd

/u01/patch_stage/Apps/Pre_REQS_Apps/18186693

[appl@sujeet 18186693]$ opatch apply

Oracle Interim Patch Installer version 1.0.0.0.64

Oracle recommends you to use the latest OPatch version

and read the OPatch documentation available in the OPatch/docs

directory for usage. For information about the latest OPatch and

other support-related issues, refer to document ID 293369.1

available on My Oracle Support (https://myoraclesupport.oracle.com)

Oracle Home : /u01/appl_test/fs1/EBSapps/10.1.2

Oracle Home Inventory : /u01/appl_test/fs1/EBSapps/10.1.2/inventory

Central Inventory : /u01/ora_prod/oraInventory

from : /etc/oraInst.loc

OUI location : /u01/appl_test/fs1/EBSapps/10.1.2/oui

OUI shared library : /u01/appl_test/fs1/EBSapps/10.1.2/oui/lib/linux/liboraInstaller.so

Java location : /u01/appl_test/fs1/EBSapps/10.1.2/jdk/jre/bin/java

Log file location : /u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage//*.log

Creating log file "/u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage/18186693/Apply_18186693_10-28-2014_15-40-55.log"

Invoking fuser to check for active processes.

Patch "18186693" overlays " 14825718 ". Conflict check between them is skipped.

Subset patches: 17303472,

The fixes for Patch 17303472, are included in the patch currently

being installed (18186693). OPatch will roll back the subset patch(es) and

install the new patch (18186693).

Provide your email address to be informed of security issues, install and

initiate Oracle Configuration Manager. Easier for you if you use your My

Oracle Support Email address/User Name.

Visit http://www.oracle.com/support/policies.html for details.

Email address/User Name:

You have not provided an email address for notification of security issues.

Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y

Oracle Configuration Manager has been installed but not configured. OCM enables

Oracle to provide superior, proactive support for our customers. Oracle

strongly recommends customers configure OCM. To complete the configuration of

OCM, refer to the OCM Installation and Administration Guide

(http://www.oracle.com/technology/documentation/ocm.html).

Backing up comps.xml ...

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Please shut down Oracle instances running out of this ORACLE_HOME

(Oracle Home = /u01/appl_test/fs1/EBSapps/10.1.2)

Is this system ready for updating?

Please respond Y|N >

Rolling back patch 17303472...

Creating log file "/u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage/17303472/RollBack_17303472_10-28-2014_15-41-47.log"

Rolling back with all-node mode.

OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.

Oracle instances have been shut down, proceeding with auto-rollback.

Removing patch 17303472...

Restoring archive files...

OPatch found "/u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage/17303472/lib/ixdn.o_libix.a_opatch_new_17303472". So, deleting the file from the archive.

OPatch found "/u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage/17303472/lib/ixvw.o_libix.a_opatch_new_17303472". So, deleting the file from the archive.

OPatch found "/u01/appl_test/fs1/EBSapps/10.1.2/.patch_storage/17303472/lib/ixwn.o_libix.a_opatch_new_17303472". So, deleting the file from the archive.

Restoring copied files...

Running make for target sharedlib.

Running make for target install.

Running make for target sharedlibs.

Running make for target install.

Inventory is good and does not have any dangling patches.

Updating inventory...

Verifying patch...

Backing up comps.xml ...

OPatch succeeded.

Step:15

Install Oracle Weblogic server (10.3.6) Patches

Copy and unzip Patches in weblogic server "cache_dir"

[appl@sujeet cache_dir]$ cp /u01/patch_stage/Apps/Pre_REQS_Apps/p17893334_1036_Generic.zip .

[appl@sujeet cache_dir]$ ls

32I2.jar LL4G.jar patch-catalog_17260.xml patch-catalog_18408.xml patch-catalog_19461.xml S9MN.jar YHJK.jar

CIH8.jar p17893334_1036_Generic.zip patch-catalog_18030.xml patch-catalog_19037.xml patch-catalog_20352.xml TTEM.jar YIJF.jar

D33T.jar patch-catalog_16936.xml patch-catalog_18239.xml patch-catalog_19345.xml patch-catalog.xml VFS8.jar

[appl@sujeet cache_dir]$

[appl@sujeet cache_dir]$ unzip p17893334_1036_Generic.zip

Archive: p17893334_1036_Generic.zip

inflating: 7FC9.jar

inflating: README.txt

inflating: patch-catalog_21169.xml

Step:16

[appl@sujeet cache_dir]$

Install "7FC9.jar" jar file on weblogic server using bsu

- Set proper GUI enable display variable

- Execute script "bsu.sh" from FMW_HOME/utils/bsu

This is the list of patch which is not applied on Server. Install this patch on weblogic Server.

The Patch has been successfully Installed

Step:17

Install EBS Application patches:

All application patches should be Installed using "adop" online patching utility.

Install patch "17204589"

[applebs@erpnode3 Pre_REQS_Apps]$ cp -rf 17204589 /u01/appl_test/fs_ne/EBSapps/patch

[applebs@erpnode3 Pre_REQS_Apps]$ adop phase=apply patches=17204589 hotpatch=yes

Enter the APPS password: *****

Enter the SYSTEM password: *****

Enter the WLSADMIN password: ******

Please wait. Validating credentials...

Enter the RUN file system context file name [/u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml]:

Step:18

Install patch "18283295"

Run "adgrants.sql" script on APPS schema from patch directory before Installing the patch.

[oraebs@sujeet db_scripts]$ cp /u01/EBS_patches/Apps_pre_1224/18283295/admin/adgrants.sql .

[oraebs@sujeet db_scripts]$ sqlplus /nolog

SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 4 21:13:14 2014

SQL> @adgrants.sql APPS

Connected.

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

--- adgrants.sql started at 2014-11-04 21:13:26

Creating PL/SQL profiler objects.

Package created.

Package body created.

Testing for correct installation

SYS.DBMS_PROFILER successfully loaded.

PL/SQL procedure successfully completed.

Commit complete.

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

Step:19

Install all remaining patches with adop patch utility.

Execute adop fs_clone to synchronize file systems

- Source environment variable for run file system

- Make sure admin server is up and running

[appl@sujeet appl_test]$ ls

EBSapps.env fs1 fs2 fs_ne

[appl@sujeet appl_test]$ . EBSapps.env

E-Business Suite Environment Information

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

RUN File System : /u01/appl_test/fs1/EBSapps/appl

PATCH File System : /u01/appl_test/fs2/EBSapps/appl

Non-Editioned File System : /u01/appl_test/fs_ne

DB Host: sujeet.oralabs.com Service/SID: test

E-Business Suite Environment Setting

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

- Enter [R/r] for sourcing Run File System Environment file, or

- Enter [P/p] for sourcing Patch File System Environment file, or

- Enter anything else to exit

Please choose the environment file you wish to source [R/P]:R

Sourcing the RUN File System ...

Step:20

[appl@sujeet appl_test]$ adop phase=fs_clone

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Please wait. Validating credentials...

RUN file system context file: /u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

PATCH file system context file: /u01/appl_test/fs2/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

Execute SYSTEM command : df /u01/appl_test/fs2

adop phase=fs_clone - Completed Successfully

Log file: /u01/appl_test/fs_ne/EBSapps/log/adop/7/adop_20141105_201909.log

adop exiting with status = 0 (Success)

Step:21

Upgrade:

- Shutdown all application services

- Perform full application and database backup

- Install patch in a "downtime" mode

[appl@sujeet scripts]$ adadminsrvctl.sh stop

You are running adadminsrvctl.sh version 120.10.12020000.9

Enter the WebLogic Admin password:

Enter the APPS Schema password:

Stopping WLS Admin Server...

Refer /u01/appl_test/fs1/inst/apps/test_erpnode3/logs/appl/admin/log/adadminsrvctl.txt for details

adadminsrvctl.sh: exiting with status 0

adadminsrvctl.sh: check the logfile /u01/appl_test/fs1/inst/apps/test_erpnode3/logs/appl/admin/log/adadminsrvctl.txt for more information ...

[appl@sujeet scripts]$ adnodemgrctl.sh stop

You are running adnodemgrctl.sh version 120.11.12020000.11

Enter the WebLogic Admin password:

adnodemgrctl.sh: exiting with status 0

adnodemgrctl.sh: check the logfile /u01/appl_test/fs1/inst/apps/test_erpnode3/logs/appl/admin/log/adnodemgrctl.txt for more information ...

Check Release of existing system

Start Installation of patch. I have used 12 workers and you can use it according to available resources.

Step:22

[appl@sujeet patch]$ adop phase=apply apply_mode=downtime patches=17919161 workers=12

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Please wait. Validating credentials...

RUN file system context file: /u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

PATCH file system context file: /u01/appl_test/fs2/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

Execute SYSTEM command : df /u01/appl_test/fs2

Worker count determination...

[END 2014/11/07 13:17:29] Generating Post Apply Reports

[END 2014/11/07 13:17:29] adzdoptl.pl run

adop phase=apply - Completed Successfully

Log file: /u01/appl_test/fs_ne/EBSapps/log/adop/8/adop_20141106_182058.log

adop exiting with status = 0 (Success)

Step:23

After Successful Installation of Patch start all Application services

[appl@sujeet appl_test]$ . EBSapps.env run

E-Business Suite Environment Information

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

RUN File System : /u01/appl_test/fs1/EBSapps/appl

PATCH File System : /u01/appl_test/fs2/EBSapps/appl

Non-Editioned File System : /u01/appl_test/fs_ne

DB Host: sujeet.oralabs.com Service/SID: test

Sourcing the RUN File System ...

[appl@sujeet appl_test]$ adstrtal.sh apps/apps

Execute cleanup and clone operations on file system

[appl@sujeet ~]$ adop phase=cleanup

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Please wait. Validating credentials...

RUN file system context file: /u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

PATCH file system context file: /u01/appl_test/fs2/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

Execute SYSTEM command : df /u01/appl_test/fs2

Worker count determination...

[END 2014/11/08 06:56:19] adzdoptl.pl run

adop phase=cleanup - Completed Successfully

Log file: /u01/appl_test/fs_ne/EBSapps/log/adop/8/adop_20141108_061727.log

adop exiting with status = 0 (Success)

Step:24

[appl@sujeet ~]$ adop phase=fs_clone

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Please wait. Validating credentials...

RUN file system context file: /u01/appl_test/fs1/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

PATCH file system context file: /u01/appl_test/fs2/inst/apps/test_erpnode3/appl/admin/test_erpnode3.xml

Execute SYSTEM command : df /u01/appl_test/fs2

Worker count determination...

Validation successful. All expected nodes are listed in ADOP_VALID_NODES table.

[END 2014/11/08 12:45:52] adzdoptl.pl run

adop phase=fs_clone - Completed Successfully

Log file: /u01/appl_test/fs_ne/EBSapps/log/adop/9/adop_20141108_070728.log

adop exiting with status = 0 (Success)

[appl@sujeet ~]$

The upgrade form 12.2.0 to 12.2.4 completed.

Step:25

Verify the version of applications after upgrade:

Post Upgrade:

- Install online help patch "17919162" using adop

- verify all application services are up and running

- check the status of managed serves

References:

- Oracle E-Business Suite Release 12.2.4 Readme (Doc ID 1617458.1)

- Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)

- Oracle E-Business Suite 12.2 Patching Technology Components Guide (Doc ID 1355068.1)

- Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)

ADOP online Patching utility in R12.2.4

Upgrade Oracle EBS R12.1.3 to R12.2.4

First Upgrade R12.1.3 to R12.2.0 After that Upgrade R12.2.0 to R12.2.4..

Step:-1

Upgrade Oracle EBS R12.1.3 to R12.2.0

Step:-2

Upgrade Oracle EBS R12.2.0 to R12.2.4

ORA-00059: Maximum Number Of DB_FILES Exceeded in 19C database