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

Useful OEM Queries to get Target details from OEM Repository

List Targets with TNS Listener ports configured : SELECT mgmt$target.host_name , mgmt$target.target_name , mgmt$target.target_type , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$target.target_name = mgmt$target_properties.target_name ) AND ( mgmt$target.target_type = mgmt$target_properties.target_type ) and ( mgmt$target.target_type = 'oracle_listener' ) and ( mgmt$target_properties.property_name = 'Port' ); Devora02       LISTENER_ora02                       oracle_listener Port 1529 Devora01       LISTENER_ora01                       oracle_listener Port 1529 Devora04       LISTENER_ora04                       oracle_listener Port 1529 List Machine_Names, CPU Count & Database Verion for Licensing SELECT mgmt$target.host_name , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$
Read more

WARNING: Subscription for node down event still pending' in Listener Log

Image
These messages are related to the Oracle TNS Listener's default subscription to the Oracle Notification Service (ONS). In a non-RAC environment it is recommended to disable this subscription.   This feature was introduced in Oracle 10g. SOLUTION Set the following parameter in the listener.ora: SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF Where <listener_name> should be replaced with the actual listener name configured in the LISTENER.ORA file. SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name> parameter is to be placed by itself on an empty line. It will be necessary to restart or reload the listener following the addition of this parameter. This will prevent the messages from being written to the log file and may also prevent the TNS Listener from hanging periodically.  See (10g only) NOTE 340091.1 Intermittent TNS Listener Hang, New Child Listener Process Forked Please Note: Setting SUBSCRIBE_FOR_NODE_DOWN_<listener_n
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