ADOP Patching Procedure and Example of Log File
ADOP Patching Procedure and Example of Log File
R12.2
Posted on February 21, 2016 by Brijesh Gogia
Online patching is supported by the capability of storing multiple application editions in
the database, and the provision of a dual application tier file system. At any given point
in time, one of these file systems is designated as run (part of the running system) and
the other as patch (either being patched or awaiting the start of the next patching cycle).
For applying a patch in R12.2 you need to use adop and run through all below phases
in sequence mentioned below.
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)
OR
adop phase=prepare,apply,finalize,cutover,cleanup
patches=<patch_number1>,<patch_number2>
——————————————————————————————————————–
$ echo $FILE_EDITION
run
$ echo $TWO_TASK
dbSID
C) Download Patches
Download patches to be applied and place then in the $PATCH_TOP directory of your
system. This directory is pre-created by the install in the non-editioned file system
(fs_ne) and should not be changed.
Important: On a multi-node system with non-shared file systems, you must copy the
patch files to each separate $PATCH_TOP directory, so that the patch files are
available from the same location on all nodes.
D) Unzip the patch
$ unzip <patch>.zip
Prepare the system for patching by running the following command to start a new
patching cycle:
$ adop phase=prepare
Here dba is the SID of our database and ebs_patch is additional service_name which is
required by online patching tool.
If you look at tnsnames.ora file in the Application tier $TNS_ADMIN directory you will
find below kind of entry:
<SID>_patch=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=<your_database_server_name>)(PORT
=<your_database_port>))
(CONNECT_DATA=
(SERVICE_NAME=ebs_patch)
(INSTANCE_NAME=<your_database_SID>)
)
)
During patching phase, adop will use this tns entry to connect to database.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
In the apply phase, adop applies the specified patches to the system. Patches are
applied to the patch edition of the database and file system.
How to execute:
Example:
If a post-installation patch step mentions any tasks that need to be performed explicitly,
where they are run from depends on the type of patching:
• In a normal online patching cycle, the steps should be executed from the patch file
system after the apply phase.
• If the patch is being applied in hotpatch mode or downtime mode, the steps should be
executed from the run file system after the apply phase.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
The finalize phase will be executed while the application is still online. It is used to
perform any remaining processing that is needed to ensure the system is ready for the
fastest possible cutover.
How to execute:
$ adop phase=finalize
VERY IMPORTANT 1 : Up to this phase, you can run a special phase called abort,
which will undo the changes made so far in the patching cycle. After cutover is
complete, however, you cannot do this.
VERY IMPORTANT 2 : In an online patching cycle, the requisite JAR files are initially
stored in the $APPL_TOP/admin/<SID>/out directory, and then uploaded into the
database during the cutover phase. Therefore, the out directory must not be deleted at
least until cutover (next phase) is complete.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
Used to perform the transition to the patched environment. Shuts down application tier
services, makes the patch edition the new run edition, and then restarts application tier
services. This is the only phase the involves a brief downtime.
Important: No users should remain on the system during cutover, as there will be a
short downtime period while the application tier services are restarted. Also, any third-
party processes connected to the
old run edition of the database should be shut down, or they will be terminated
automatically.
How to execute:
$ adop phase=cutover
Note: Cutover will take longer if it has to wait for long-running concurrent processes to
complete. In such a case, you can expect to see an informational message of the form:
[STATEMENT] [END 2013/10/28 23:47:16] Waiting for ICM to go downIf you do not
want to wait for in-progress concurrent requests to finish normally, you can terminate
the internal concurrent manager by executing the adcmctl.sh abort command from a
different shell.
• Shut down application tier services: All application tier services are brought down.
During this period, the system is unavailable to users.
• Cutover database: Promote patch database edition to become the new run database
edition, using adzdpmgr.pl script.
• Cutover file system: Promote patch file system to become the new run file system,
switching the $FILE_EDITION values in the patch and run enviroments. The current
patch APPL_TOP becomes the new run APPL_TOP, and the current run APPL_TOP
becomes the new patch APPL_TOP. Terminate old database sessions: Terminate any
database connections to the old run edition of the database.
• Start application tier services: Application tier services are restarted, on the new run
edition. The system is now available again to users
• ADZDPATCH concurrent program is cancelled when the cutover phase is complete.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
This adop phase is used to remove obsolete code and data from old editions.
How to execute:
$ adop phase=cleanup
• Various actions are performed during cleanup, including dropping (removing) obsolete:
Crossedition triggers, Seed data, Editioned code objects (covered objects), Indexes,
Columns, Editions.
Using parameter cleanup_mode:
Use quick cleanup when you need to start the next patching cycle as soon as possible.
For example, if you want to start a new patching cycle right away, but have not yet run
cleanup from the previous patching cycle, you can use quick cleanup mode to complete
the essential cleanup tasks as fast as possible.
b) cleanup_mode=standard – Does the same as quick mode, and also drops (removes)
obsolete editioned code objects (covered objects).
Use full cleanup when you want to recover the maximum amount of space in the
database. If you have run a large number of patching cycles, or applied a very large
patch such as a rollup, significant space may be consumed by obsolete table columns
and recovered by running a full cleanup. A full cleanup should only be performed when
there is no immediate need to start a new patching cycle.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
Abort PHASE is conditional phase. This phase cannot be specified with any other
phase.
If for some reason either the prepare or apply phase failed or gave problems, you can
abort the patching cycle at either of these points by running a special phase with the
Command. The actions taken will be discarded (rollbacked).
IMPORTANT: This abort command is only available up to (but not including) the cutover
phase. After cutover, the system is running on the new edition, and abort is no longer
possible for that patching cycle.
How to execute:
$ adop phase=abort
• Confirms that there is an in-progress online patching cycle, so the abort call is
therefore valid.
• Checks for the existence of a patch edition and drops one if it exists.
• Cancels the ADZDPATCH concurrent program, if it is running.
• Deletes the rows inserted for the pending session ID from the ad_adop_sessions and
ad_adop_session_patches tables.
VERY IMPORTANT: After running abort, a full cleanup must be performed. The cleanup
command is: adop phase=cleanup cleanup_mode=full). This will remove any columns
that were added by the patch but are no longer needed because of the abort. If they are
not removed, they may cause problems in a later patching cycle.
Alternatively, you can run a combined command to abort the patching cycle and perform
a full cleanup:
$ adop phase=abort,cleanup cleanup_mode=full
If any attempt was made to apply patches to the patch edition, after abort you must run
the fs_clone phase (adop phase=fs_clone) to recreate the patch file system.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++
How to execute:
$ adop phase=fs_clone
This phase is useful if the APPL_TOPs have become very unsynchronized (meaning
that there would be a large number of delta patches to apply). It is a heavyweight
process, taking a backup of the entire current patch APPL_TOP and then cloning the
run APPL_TOP to create a new patch APPL_TOP. As this method requires more time
and disk space, it should only be used when the state of the patch file system is
unknown. This command must be invoked from the run file system, before the next
prepare phase is run.
Note: The patch file system requires at least 25 GB of free disk space to be available for
adop operations, including fs_clone. If there is insufficient free space, the adop
operation will fail.
If an fs_clone operation fails, you can rerun it with the option force=yes to restart it from
the beginning (with the same session ID), or force=no to restart it from the point where it
failed.
——————————————————————————————————————–
IMPORTANT POINTS REGARDING ONLINE PATCHING:
2. adop will automatically set its environment as required, but it is the user’s
responsibility to set the environment correctly for any other commands that may be run.
Set the run edition environment whenever executing commands that you intend to affect
the run edition.
For example:
$ . <EBS_ROOT>/EBSapps.env run
$ adstrtal.sh
Set the patch edition environment whenever you intend to execute commands that
affect the patch edition.
For example:
$ . <EBS_ROOT>/EBSapps.env patch
$ sqlplus apps/apps @my_custom_patch_script.sql
3. 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.”
4. After an online patching cycle is started, you should not perform any configuration
changes in the run edition file system. Any that are made will not be propagated and will
therefore be lost after cutover is complete.
5. You should not attempt to clone an Oracle E-Business Suite system while an online
patching cycle is in progress.
6. The prepare, apply, and fs_clone phases all require at least 10GB of free disk space.
All other phases require 1GB of free space. A warning message will be displayed if less
than the needed amount is available.
7. The directories where you extracted the patches applied in a given patching cycle
must be retained, in the same location and with the same contents, until the next
prepare phase completes. This is also a requirement for patches applied in a hotpatch
session.
8. Maintenance Mode is not needed for online patching, and so Maintenance Mode is
not available in Oracle E-Business Suite Release 12.2.
——————————————————————————————————————-
ADOP ON MULTI-NODE
In a multi-node environment, one application tier node will be designated as the primary
node. This is the node where the Admin Server is located, and will usually also be the
node that runs Oracle HTTP Server. All other application tier nodes are designated as
secondary nodes.
adop commands are invoked by a user on the primary node. Internally, adop uses
Secure Shell (ssh) to automatically execute required patching actions on all secondary
nodes. You must set up passwordless ssh connectivity from the primary node to all
secondary nodes.
If a node unexpectedly becomes inaccessible via ssh, it will be abandoned by adop, and
the appropriate further actions taken. Consider a scenario where the adop
phase=prepare command is run in a system with ten application tier nodes. The
command is successful on nine nodes, but fails on the tenth. In such a case, adop will
identify the services enabled on nodes 1-9. If they are sufficient for Oracle E-Business
Suite to continue to run normally, adop will mark node 10 as abandoned and then
proceed with its patching actions. If they are not sufficient, adop will proceed no further.
——————————————————————————————————————–
Patch 24576605 in CVQA
Refer to My Oracle Support Knowledge Document 1594274.1 to identify the patch that delivers
this bug fix.
calling: /EQ02/CVQA/fs1/FMW_Home/webtier/perl/bin/perl
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateSetup.pl -
contextfile=/EQ02/CVQA/fs1/inst/apps/CVQA_cvapq01/appl/admin/CVQA_cvapq01.xml -
patchctxfile=/EQ02/CVQA/fs2/inst/apps/CVQA_cvapq01/appl/admin/CVQA_cvapq01.xml -
logloc=/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01 -
phase=prepare -promptmsg=hide
---------------------------------------
[WARNING]: There could be issues while validating the ports used for E-Business Suite instance against
ports used in /etc/services. Refer the log file for more details.
[WARNING]: Either some of the required entries in /etc/hosts file might be missing (e.g. localhost or
hostname) OR the file /etc/hosts could not be read.
[EVENT] Calling:
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/TXK_SANITY_fil
esystemcheck_Mon_Mar_6_23_23_59_2017/txkADOPPreparePhaseSanityCheck_Mon_Mar_6_23_23_5
9_2017.log
Program : completed @ Mon Mar 6 23:23:59 2017
[EVENT] Calling:
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl
[EVENT] [START 2017/03/06 23:24:02] Performing check to see if pending cleanup actions exist
[EVENT] [END 2017/03/06 23:24:03] Performing check to see if pending cleanup actions exist
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/adzdshowts.out
[END 2017/03/06 23:24:03] Generating Tablespace Report
[EVENT] [START 2017/03/06 23:24:06] Checking status of the ADZDPATCH concurrent program
Manager. This request cannot yet begin execution because other requests
may conflict with it. The Conflict Resolution Manager will determine when
this request may begin execution. User SYSADMIN submitted this request on
[EVENT] [END 2017/03/06 23:24:07] Checking status of the ADZDPATCH concurrent program
[EVENT] [START 2017/03/06 23:24:07] Waiting for ADZDPATCH concurrent program to run
[EVENT] [END 2017/03/06 23:24:38] Waiting for ADZDPATCH concurrent program to run
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/adzdshowlog_cl
eanup.out
[EVENT] [START 2017/03/06 23:24:39] Check and create Patch Edition (if required)
[EVENT] [END 2017/03/06 23:24:53] Check and create Patch Edition (if required)
[EVENT] Calling:
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
========================================
========================================
SYNCHRONIZATION is in progress. This may take a little longer depending on the number and size of
patches that are being synchronized.
"/EQ02/CVQA/fs2/EBSapps/appl/ad/12.0.0/java/adjava.zip:/EQ02/CVQA/fs2/EBSapps/comn/util/jdk32/
lib/dt.jar:/EQ02/CVQA/fs2/EBSapps/comn/util/jdk32/lib/tools.jar:/EQ02/CVQA/fs2/EBSapps/comn/util/j
dk32/jre/lib/rt.jar:/EQ02/CVQA/fs2/EBSapps/comn/shared-libs/ebs-3rdparty/WEB-
INF/lib/ebs3rdpartyManifest.jar:/EQ02/CVQA/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-
fmw/WEB-INF/lib/ebsFMWManifest.jar:/EQ02/CVQA/fs2/FMW_Home/Oracle_EBS-app1/shared-
libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/EQ02/CVQA/fs2/FMW_Home/oracle_common/modules/oracle.uix_1
1.1.1/uix2.jar:/EQ02/CVQA/fs2/EBSapps/comn/java/classes:/EQ02/CVQA/fs2/EBSapps/10.1.2/forms/jav
a:/EQ02/CVQA/fs2/EBSapps/10.1.2/forms/java/frmall.jar:/EQ02/CVQA/fs2/EBSapps/10.1.2/jlib/ewt3.jar
:/EQ02/CVQA/fs2/EBSapps/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-
INF/lib/frmsrv.jar"
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/TXK_SYNC_upd
ate_Mon_Mar_6_23_24_54_2017/txkADOPPreparePhaseSynchronize_Mon_Mar_6_23_24_54_2017.lo
g
[EVENT] Calling:
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/TXK_SANITY_db
check_Mon_Mar_6_23_33_13_2017/txkADOPPreparePhaseSanityCheck_Mon_Mar_6_23_33_13_2017.
log
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/adzdshowed.ou
t
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/prepare_20170306_232145/CVQA_cvapq01/adzdshowlog.ou
t
[EVENT] [START 2017/03/06 23:33:44] Check and Stop patch FS Admin Server
[EVENT] [END 2017/03/06 23:33:50] Check and Stop patch FS Admin Server
[EVENT] [START 2017/03/06 23:33:51] Check and Stop patch Node Manager
[EVENT] [END 2017/03/06 23:33:57] Check and Stop patch Node Manager
Phase: apply
"/EQ02/CVQA/fs2/EBSapps/appl/ad/12.0.0/java/adjava.zip:/EQ02/CVQA/fs2/EBSapps/comn/util/jdk32/
lib/dt.jar:/EQ02/CVQA/fs2/EBSapps/comn/util/jdk32/lib/tools.jar:/EQ02/CVQA/fs2/EBSapps/comn/util/j
dk32/jre/lib/rt.jar:/EQ02/CVQA/fs2/EBSapps/comn/shared-libs/ebs-3rdparty/WEB-
INF/lib/ebs3rdpartyManifest.jar:/EQ02/CVQA/fs2/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-
fmw/WEB-INF/lib/ebsFMWManifest.jar:/EQ02/CVQA/fs2/FMW_Home/Oracle_EBS-app1/shared-
libs/ebs-appsborg/WEB-
INF/lib/ebsAppsborgManifest.jar:/EQ02/CVQA/fs2/FMW_Home/oracle_common/modules/oracle.uix_1
1.1.1/uix2.jar:/EQ02/CVQA/fs2/EBSapps/comn/java/classes:/EQ02/CVQA/fs2/EBSapps/10.1.2/forms/jav
a:/EQ02/CVQA/fs2/EBSapps/10.1.2/forms/java/frmall.jar:/EQ02/CVQA/fs2/EBSapps/10.1.2/jlib/ewt3.jar
:/EQ02/CVQA/fs2/EBSapps/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/WEB-
INF/lib/frmsrv.jar"
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/apply_20170306_234506/CVQA_cvapq01/adzdshowlog.out
applebs@cvapq01 patch$
applebs@cvapq01 patch$
applebs@cvapq01 patch$
applebs@cvapq01 patch$
applebs@cvapq01 patch$
applebs@cvapq01 patch$ adop phase=finalize workers=8
Refer to My Oracle Support Knowledge Document 1594274.1 to identify the patch that delivers
this bug fix.
Phase: finalize
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/finalize_20170307_005805/CVQA_cvapq01/adzdshowlog.out
Refer to My Oracle Support Knowledge Document 1594274.1 to identify the patch that delivers
this bug fix.
Phase: cutover
calling: /EQ02/CVQA/fs1/FMW_Home/webtier/perl/bin/perl
/EQ02/CVQA/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkValidateSetup.pl -
contextfile=/EQ02/CVQA/fs1/inst/apps/CVQA_cvapq01/appl/admin/CVQA_cvapq01.xml -
patchctxfile=/EQ02/CVQA/fs2/inst/apps/CVQA_cvapq01/appl/admin/CVQA_cvapq01.xml -
logloc=/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cutover_20170307_005945/CVQA_cvapq01 -
phase=cutover -promptmsg=hide
---------------------------------------
[EVENT] [START 2017/03/07 01:00:16] Checking if all nodes were synchronized in the previous apply
phase
[EVENT] [END 2017/03/07 01:00:16] Checking if all nodes were synchronized in the previous apply
phase
ORACLE Password:
ORACLE Password:
[EVENT] [START 2017/03/07 01:04:24] Check and Stop patch FS Admin Server
[EVENT] [END 2017/03/07 01:04:31] Check and Stop patch FS Admin Server
[EVENT] [START 2017/03/07 01:04:31] Check and Stop patch Node Manager
[EVENT] [END 2017/03/07 01:04:36] Check and Stop patch Node Manager
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cutover_20170307_005945/CVQA_cvapq01/TXK_CTRL_force
shutdown_Tue_Mar_7_01_04_37_2017/txkADOPCutOverPhaseCtrlScript_Tue_Mar_7_01_04_37_2017.
log
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cutover_20170307_005945/CVQA_cvapq01/TXK_CTRL_ctxup
date_Tue_Mar_7_01_08_04_2017/txkADOPCutOverPhaseCtrlScript_Tue_Mar_7_01_08_04_2017.log
NMProcess: <Mar 7, 2017 1:09:13 AM> <INFO> <Loaded node manager configuration properties from
'/EQ02/CVQA/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanager.prope
rties'>
NMProcess:
NMProcess:
NMProcess:
NodeManagerHome=/EQ02/CVQA/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1
NMProcess: ListenAddress=cvapq01.dana.com
NMProcess: ListenPort=5566
NMProcess: ListenBacklog=50
NMProcess: SecureListener=false
NMProcess: AuthenticationEnabled=true
NMProcess: NativeVersionEnabled=true
NMProcess: CrashRecoveryEnabled=false
NMProcess: JavaHome=/EQ02/CVQA/fs2/EBSapps/comn/util/jdk64
NMProcess: StartScriptEnabled=false
NMProcess: StopScriptEnabled=false
NMProcess: StartScriptName=startWebLogic.sh
NMProcess: StopScriptName=
NMProcess:
LogFile=/EQ02/CVQA/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodemanage
r.log
NMProcess: LogLevel=INFO
NMProcess: LogLimit=0
NMProcess: LogCount=1
NMProcess: LogAppend=false
NMProcess: LogToStderr=true
NMProcess: LogFormatter=weblogic.nodemanager.server.LogFormatter
NMProcess:
DomainsFile=/EQ02/CVQA/fs2/FMW_Home/wlserver_10.3/common/nodemanager/nmHome1/nodema
nager.domains
NMProcess: DomainsFileEnabled=true
NMProcess: StateCheckInterval=500
NMProcess: QuitEnabled=true
NMProcess: UseMACBroadcast=false
NMProcess: DomainRegistrationEnabled=false
NMProcess: DomainsDirRemoteSharingEnabled=false
NMProcess:
NMProcess:
NMProcess:
NMProcess: <Mar 7, 2017 1:09:14 AM> <INFO> <EBS_domain_CVQA> <forms_server1> <Startup
configuration properties loaded from
"/EQ02/CVQA/fs2/FMW_Home/user_projects/domains/EBS_domain_CVQA/servers/forms_server1/dat
a/nodemanager/startup.properties">
NMProcess: <Mar 7, 2017 1:09:14 AM> <INFO> <Plain socket listener started on port 5566, host
cvapq01.dana.com>
NMProcess: INFO: Plain socket listener started on port 5566, host cvapq01.dana.com
NMProcess: <Mar 7, 2017 1:09:32 AM> <INFO> <EBS_domain_CVQA> <AdminServer> <Rotated server
output log to
"/EQ02/CVQA/fs2/FMW_Home/user_projects/domains/EBS_domain_CVQA/servers/AdminServer/logs/
AdminServer.out00008">
NMProcess: <Mar 7, 2017 1:09:32 AM> <INFO> <EBS_domain_CVQA> <AdminServer> <Server error log
also redirected to server log>
NMProcess: <Mar 7, 2017 1:09:33 AM> <INFO> <EBS_domain_CVQA> <AdminServer> <Rotated server
output log to
"/EQ02/CVQA/fs2/FMW_Home/user_projects/domains/EBS_domain_CVQA/servers/AdminServer/logs/
AdminServer.out00009">
NMProcess: <Mar 7, 2017 1:09:33 AM> <INFO> <EBS_domain_CVQA> <AdminServer> <Server error log
also redirected to server log>
NMProcess: <Mar 7, 2017 1:09:33 AM> <INFO> <EBS_domain_CVQA> <AdminServer> <Server output
log file is
'/EQ02/CVQA/fs2/FMW_Home/user_projects/domains/EBS_domain_CVQA/servers/AdminServer/logs/
AdminServer.out'>
LOG FILE :
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cutover_20170307_005945/CVQA_cvapq01/TXK_CTRL_force
startup_Tue_Mar_7_01_10_29_2017/txkADOPCutOverPhaseCtrlScript_Tue_Mar_7_01_10_29_2017.log
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cutover_20170307_005945/CVQA_cvapq01/adzdshowlog.ou
t
applebs@cvapq01 patch$
applebs@cvapq01 patch$
applebs@cvapq01 patch$
Refer to My Oracle Support Knowledge Document 1594274.1 to identify the patch that delivers
this bug fix.
Phase: cleanup
[EVENT] Output:
/EQ02/CVQA/fs_ne/EBSapps/log/adop/39/cleanup_20170307_011514/CVQA_cvapq01/adzdshowlog.ou
t
no rows selected
SQL> select * from ad_bugs where bug_number = '24576605';
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
1138128
5 07-MAR-17 5 ont
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
n US
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
1138151
5 07-MAR-17 5 ont
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
nD
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
1138174
5 07-MAR-17 5 ont
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
nE
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
1138197
5 07-MAR-17 5 ont
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
nF
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
1138220
5 07-MAR-17 5 ont
BUG_ID APPLICATION_SHORT_NAME
---------- --------------------------------------------------
BASELINE_NAME
--------------------------------------------------------------------------------
G LANG
- ----
nS
SQL> select object_name, owner, object_type from all_objects where status like 'INVALID';
SQL> /
------------------------------ -------------------------------------------------
7 rows selected.
1* select object_name, owner, object_type from all_objects where status like 'INVALID'
SQL> /
12 rows selected.
Trigger altered.
SQL> select object_name, owner, object_type from all_objects where status like 'INVALID';
11 rows selected.
Trigger altered.
Trigger altered.
Trigger altered.
SQL> commit;
Commit complete.
SQL> select object_name, owner, object_type from all_objects where status like 'INVALID';
7 rows selected.