Patching using Datapatch from 12c

From 12c on wards we don’t need to run Patching post  installation scripts postinstall.sql  &  @catbundle.sql psu apply  and validate log files manually ..

All we need to do is just run  datapatch  after applying patch.

*****************************************************
In 11G  After applying patch we need to run like following order ..

postinstall.sql    =>  for OJVM in upgrade mode

@catbundle.sql psu apply  =>  for PSU in normal startup mode
*****************************************************

But from 12c datapatch will take care of post scripts work.


./datapatch –verbose

Please see log for datapatch.

[oracle@s24-oratl15 OPatch]$ ./datapatch -verbose
SQL Patching tool version 12.1.0.2.0 on Tue May  3 01:50:33 2016
Copyright (c) 2015, Oracle.  All rights reserved.

Log file for this invocation: /u01/app/oracle/base/cfgtoollogs/sqlpatch/sqlpatch_25942_2016_05_03_01_50_33/sqlpatch_invocation.log

Connecting to database...OK
Bootstrapping registry and package to current versions...done
Determining current state...done

Current state of SQL patches:
Patch 22674709 (Database PSU 12.1.0.2.160419, Oracle JavaVM Component (Apr2016)):
  Installed in the binary registry only
Bundle series PSU:
  ID 160419 in the binary registry and not installed in the SQL registry

Adding patches to installation queue and performing prereq checks...
Installation queue:
  Nothing to roll back
  The following patches will be applied:
    22674709 (Database PSU 12.1.0.2.160419, Oracle JavaVM Component (Apr2016))
    22291127 (Database Patch Set Update : 12.1.0.2.160419 (22291127))

Installing patches...
Patch installation complete.  Total patches installed: 2

Validating logfiles...
Patch 22674709 apply: SUCCESS
  logfile: /u01/app/oracle/base/cfgtoollogs/sqlpatch/22674709/20057886/22674709_apply_S24EETST_2016May03_01_51_09.log(no errors)
Patch 22291127 apply: SUCCESS
  logfile: /u01/app/oracle/base/cfgtoollogs/sqlpatch/22291127/19694308/22291127_apply_S24EETST_2016May03_01_52_14.log (no errors)
SQL Patching tool complete on Tue May  3 01:52:33 2016
**************************************************************


How to apply patch from 12c:

Stop All services and run following to apply April 2016 PSU  patch .

[oracle@s24-oratl15 22291127]$ /u01/app/oracle/base/product/12.1.0/dbhome_1EE/OPatch/opatch apply
[oracle@s24-oratl15 22674709]$ /u01/app/oracle/product/12.1.0.2/db_home_1/OPatch/opatch apply

Start services and run datapatch from OPatch directory.

./datapatch -verbose

Refer to know more about datapatch 

Datapatch: Database 12c Post Patch SQL Automation (Doc ID 1585822.1)

Comments

Post a Comment

Popular posts from this blog

ORA-28086: The data redaction policy expression has an error

Image
Error: ERROR at line 1: ORA-28086: The data redaction policy expression has an error. ORA-06512: at "SYS.DBMS_REDACT_INT", line 3 ORA-06512: at "SYS.DBMS_REDACT", line 42 ORA-06512: at line 1 When we try to run same as sys user it is working perfectly fine, but as a normal user it is failing with below errors. No Privileges issue because AVO user had DBA Privilege .. Versions  confirmed  as being affected 12.1.0.2 (Server Patch Set) 11.2.0.4 Fixed: The fix for 20693579 is first included in 12.2.0.1 (Base Release) Cause : Bug 20693579 - DBMS_REDACT.ADD_POLICY fails with ORA-28086 when CURSOR_SHARING is force (Doc ID 20693579.8) To Bottom Bug 20693579  DBMS_REDACT.ADD_POLICY fails with ORA-28086 when CURSOR_SHARING is force  This note gives a brief overview of bug 20693579.  The content was last updated on: 17-FEB-2017   Click  here  for details of each of the sections below. Aff...
Read more

ORA-65139: Mismatch between XML metadata file and data file

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .
Read more

TFA-00002 : Oracle Trace File Analyzer (TFA) is not running

TFA Failed to start listening for commands on one of the Rac Node : As a root user /etc/init.d/init.tfa  start Starting TFA.. start: Job is already running: oracle-tfa Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA-00002 : Oracle Trace File Analyzer (TFA) is not running TFA Failed to start listening for commands Solution : run synctfanodes.sh  if you have root password . if no root password copy below files to TFA Failed node and try to restart TFA .. Please check whether these 4 files exist on all nodes are similar. TFA_HOME/server.jks TFA_HOME/client.jks TFA_HOME/internal/ssl.properties   TFA_HOME/internal/ portmapping.txt If not similar just copy these files to TFA Failing node and try TFA Restart ..It Worked for me .   [root@host01]# ./tfactl  -v "debug" start Starting TFA...
Read more