Release Date: Oct-2015
|
Oracle
E-Business Suite Release 12.1.3+ Recommended Patch Collection 4 (RPC4): Patch
- 21236633
Oracle
Reference:
1.
Oracle
E-Business Suite Release 12.1.3+ Recommended Patch Collection 4 (RPC4) (Doc
ID 2053709.1)
2.
How
to check if a certain Patch was applied to Oracle Applications instance (11i
or R12) ? (Doc ID 443761.1)
3.
How
to check, which EBS Technology Patchsets have been applied on 11i or Release
12.1.x ? (Doc ID 390864.1)
Environment:
Apps Tier– Oracle EBS R12.1.3 on
Oracle Linux EL 6.7 64bit
Database Tier– Database 11.1.0.7 on
Oracle Linux EL 6.7 64bit
Instance Name: VIS
Accounts – applmgr (Apps Tier) and
oravis (DB tier)
Host Names: ebsapps.oracle (Apps tier)
and ebsdb.oracle(db tier)
Application Environment set to applmgr
user (VIS_ebsapps.env)
Database Envinoment set to oravis
user(VIS_ebsdb.env)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Pre Upgrade Activities
|
·
Run
the adgrants.sql script as a user that can connect as SYSDBA to grant
privileges to selected SYS objects and create PL/SQL profiler objects.
1.
Create $ORACLE_HOME/appsutil/admin on the
database server if not exist.
2.
Get
adgrants.sql file from Apps tier $APPL_TOP/admin
3.
3.
Copy adgrants.sql from this patch directory to $ORACLE_HOME/appsutil/admin.
4.
Set
the environment to point to ORACLE_HOME on the database server.
5.
Use
SQL*Plus to run the script:
$
sqlplus /nolog
SQL>
@$ORACLE_HOME/appsutil/admin/adgrants.sql apps
Note: If it is already executed ignore
this step.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Invalid Object Count
|
·
Get
the Invalid object count
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
RPC4
Requirements
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Patch Levels
|
·
RPC4 Patch Applied Status:
SQL> select bug_number from ad_bugs where bug_number =
‘21236633’;
·
Patch Requirements
1.
R12.AD.B.Delta.7
SQL> select bug_number from ad_bugs
where bug_number = ‘21314548’
2.
R12.ADO.B.Delta.8
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Apply patch R12.AD.B.Delta.7
|
·
Patch Applied Status:
SQL> select bug_number
from ad_bugs where bug_number = ‘21314548’;
·
Patch Requirements:
Required Patch Levels:
1.
R12.AD.B.1
SQL> select bug_number from ad_bugs where
bug_number = '7461070';
If not apply with adpatch
in apps tier
2.
R12.ATG_PF.B.delta.3
SQL> select bug_number FROM ad_bugs WHERE
bug_number = '8919491';
·
Apply Patch Requirements:
Login Apps tier with
applmgr account
$cd $ADMIN_SCRIPTS_HOME
$adstpall.sh apps/apps
Run the adgrants.sql on
Database tier if not completed.
$cd /mnt/software/RPC4patches/21314548
$adpatch
(udriver)
Verify Patch log.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Apply Patch R12.ADO.B.Delta.8
|
·
Patch Applied Status:
SQL> select bug_number
from ad_bugs where bug_number = ‘21285343’;
·
Patch Requirements:
Required Patch Levels:
1.
R12.AD.B.delta.3
SQL> select bug_number
from ad_bugs where bug_number = '9239089';
If not apply with adpatch
in apps tier
2.
R12.ATG_PF.B.delta.3
SQL> select bug_number
from ad_bugs where bug_number = '8919491';
·
Apply Patch Requirements:
$cd /mnt/software/RPC4patches/21285343
$adpatch
(udriver)
Verify Patch log
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Apply RPC4 - 21236633
|
$cd /mnt/software/RPC4patches/21285343
$adpatch
(udriver)
Verify Patch log
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Auto config
|
·
Run
Auto Config on DB tier first
·
Run
Auto config on Apps Tier
·
Start
all EBS Service
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Perform product-specific
post-install step
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
After Applying Oracle E-Business Suite Release 12.1.3+ RPC4
|
Note:
After completed the steps to update all database tier nodes with the latest
code level, perform the following post-update steps only if have licensed
these respective products:
Metalink Doc ID 2053709.1
·
Oracle Mobile Field Service (CSM) - [Required] Downtime Required - No
·
Oracle Trade Management (OZF) - [Required] Downtime Required
- No
·
Financials tasks
Oracle Payables (AP)
[Required] Downtime Required - Yes
1.
Document
1341317.1
2.
Document
1450194.1
Oracle Subledger
Accounting (XLA) - [Required] Downtime Required - No
·
Human Resources tasks
1.
Document
1989740.1
·
Supply Chain Management tasks
Oracle Complex
Maintenance, Repair & Overhaul (AHL) - [Conditional] Downtime Required -
No
1.
Document
1983084.1
Oracle Manufacturing
Operations Center (MTH) - [Required] Downtime Required - No
1.
Document
1618426.1
Oracle Mobile Application
Server (MWA) [Conditional] Downtime Required - No
Oracle Product Workbench
(DNA) - [Conditional] Downtime
Required - No
Oracle Shipping Execution
(WSH) - [Conditional] Downtime Required - No
·
Value Chain Planning tasks
Oracle Value Chain
Planning (VCP) - [Required] Downtime Required - Yes
1.
Document
746824.1
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Functional Information
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Oracle
Applications Technology (ATG)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Oracle Financials (FIN):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Oracle Supply Chain Management (SCM):
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Validate Patches
|
Validate
the all patches
ad_applied_patches
ad_bugs
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
4 comments:
Hi Sudheer,
Thanks for sharing this valuable information !!
This (Doc 2053709.1) doesn't describes about running autoconfig on both DB & Apps tier.
Please confirm, is this mandate to run autoconfig post completion patching?
Yes, you have to because it is included technology upgrade also. you need down time for this patch.
Thanks
Sudheer
Hi Sudheer,
Recently in my application , after RPC5 patching many objects became invalid.
So I have reviewed and compiled successfully the ones that were missing db_link but still following are invalid and need correction .
Why this invalid objects?
How to fix them ? Please provide some guide.
Many thanks!
Regards,
Kalpana
Hi Sudheer,
I am going to apply RPC5 on EBS R12.1.3. What is the estimated time duration for applying the patch along with prerequisite patch. Which impact analysis is better for the developer to know impact of code if customer have custom code. Patch wizard or autopatch adpatch apply=no option.
How much time duration the patch analysis take for RPC5 on EBS R12.1.3?
Regards,
Ranjith R
Post a Comment