Patching Issues

Datapatch -verbose error:

1)

----------
1)Opatch apply was successful.
2)opatch lsinventory was showing latest patch applied in the inventory.

But,


When I give datapatch –verbose to apply modified sqls into database as part of post patch steps, we were getting 


D:\oracle\product\12.1.0.2\dbhome\OPatch>datapatch -verbose 

SQL Patching tool version 12.1.0.2.0 Production on Sat Feb 18 01:13:34 2017 
Copyright (c) 2012, 2017, Oracle. All rights reserved. 

Log file for this invocation: D:\oracle\product\12.1.0.2\dbhome\cfgtoollogs\sqlpatch\sqlpatch_4772_2017_02_18_01_13_34\sqlpatch_invocation.log 


Connecting to database...OK 

Bootstrapping registry and package to current versions...done 

Queryable inventory could not determine the current opatch status. 

Execute 'select dbms_sqlpatch.verify_queryable_inventory from dual' 
and/or check the invocation log 
D:\oracle\product\12.1.0.2\dbhome\cfgtoollogs\sqlpatch\sqlpatch_4772_2017_02_18_01_13_34\sqlpatch_invocation.log 
for the complete error. 
Prereq check failed, exiting without installing any patches. 

Please refer to MOS Note 1609718.1 and/or the invocation log 

D:\oracle\product\12.1.0.2\dbhome\cfgtoollogs\sqlpatch\sqlpatch_4772_2017_02_18_01_13_34\sqlpatch_invocation.log 
for information on how to resolve the above errors. 

SQL Patching tool complete on Sat Feb 18 01:13:41 2017 

D:\oracle\product\12.1.0.2\dbhome\OPatch>opatch lsinventory -xml 
Oracle Interim Patch Installer version 12.1.0.1.3 
Copyright (c) 2017, Oracle Corporation. All rights reserved. 

Syntax Error... Unrecognized Command or Option: failed to parse arguments "illegal value '' for option -xml/--xml" 

Please use the option 'opatch lsinventory -help' to get correct syntax 

OPatch failed with error code = 14 


D:\oracle\product\12.1.0.2\dbhome\OPatch>select dbms_sqlpatch.verify_queryable_inventory from dual; 

'select' is not recognized as an internal or external command, 
operable program or batch file.


The solution is:


To apply like, datapatch -apply 25115951 -force -bundle_series DBBP


25115951- Replace with your patch number.


(But this  way cannot be used to apply all the time) we had to use this option as this error is sometime expected in Windows\unix environments when Oracle have too many DLL to handle.


Next time when you face this issue, you can request Wintel/Unix team to do a clean reboot and then retry.

--------------
2
--------------
Expected error:
perl510.dll is missing while executing datapatch –verbose in patch post-installation.

Workaround:

SET PERL5LIB=


set PATH=%ORACLE_HOME%\perl\bin;%PATH%  

======================================================
Note: While applying patch to OEM databases, stop Agent and OMS before applying patch and start once patching completed.

Before patching:

Check Agent and OMS status:
Get OMS and Agent home location,

D:\oracle\mw\oms12c\oms\BIN
emctl status oms

D:\oracle\Agent13c\agent_inst\bin
emctl status agent

D:\oracle\mw\oms12c\oms\BIN
emctl stop oms

D:\oracle\Agent13c\agent_inst\bin
emctl stop agent

stop database and listener
===============================
After Patching:

start database and listener

datapatch -verbose

D:\oracle\Agent13c\agent_inst\bin
emctl start agent

D:\oracle\mw\oms12c\oms\BIN
emctl start oms


finally check status of Agent and OMS, Make sure both are running.

Comments

Popular posts from this blog

Profile password verify function issue - From root

Change character set of Oracle database and using CSSAN and DMU

Upload patch to OEM (12c/13c)