Stop TFA before applying the patches...

-
During the apply of RU patch on Oracle 12.2 opatchauto apply was failing with below errors.
Environment was single instance ASM standby database.
 Execution of [OPatchAutoBinaryAction] patch action failed, check log for more details. Failures:  
 Patch Target : racadrdb1->/u01/app/oracle/product/12.2.0/dbhome_1 Type[sidb]  
 Details: [  
 ---------------------------Patching Failed---------------------------------  
 Command execution failed during patching in home: /u01/app/oracle/product/12.2.0/dbhome_1, host: racadrdb1.  
 Command failed: /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/opatchauto apply /tmp/JAN2019/28828733 -oh /u01/app/oracle/product/12.2.0/dbhome_1 -target_type oracle_database -binary -invPtrLoc /u01/app/12.2.0.1/grid12c/grid/oraInst.loc -jre /u01/app/12.2.0.1/grid12c/grid/OPatch/jre -persistresult /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/auto/dbsessioninfo/sessionresult_racadrdb1_sidb.ser -analyzedresult /u01/app/oracle/product/12.2.0/dbhome_1/OPatch/auto/dbsessioninfo/sessionresult_analyze_racadrdb1_sidb.ser  
 Command failure output:  
 ==Following patches FAILED in apply:  
 Patch: /tmp/JAN2019/28828733/28822515  
 Log: /u01/app/oracle/product/12.2.0/dbhome_1/cfgtoollogs/opatchauto/core/opatch/opatch2019-07-29_15-07-52PM_1.log  
 Reason: Failed during Patching: oracle.opatch.opatchsdk.OPatchException: Prerequisite check "CheckActiveFilesAndExecutables" failed.  
 After fixing the cause of failure Run opatchauto resume  
 ]  
 OPATCHAUTO-68061: The orchestration engine failed.  
 OPATCHAUTO-68061: The orchestration engine failed with return code 1  
 OPATCHAUTO-68061: Check the log for more details.  
 OPatchAuto failed.  
 OPatchauto session completed at Mon Jul 29 15:08:07 2019  
 Time taken to complete the session 1 minute, 33 seconds  
  opatchauto failed with error code 42  
 root@racadrdb1 #
After going through the logs the culprit was external process which was using the Oracle homes.
Finding the processes which are using the homes,
 root@racadrdb1 # fuser -c /u01  
 /u01:   7423ctom  2070tom  
 root@racadrdb1 #
TFA was the process which was operating from Oracle Home
 root@racadrdb1 # ps -ef | grep -i 2070  
   root 11390 11162  0 15:18:49 pts/3    0:00 grep -i 2070  
   root 2070   1  0  Nov 14 ?    2633:02 /u01/app/oracle/tfa/racadrdb1/tfa_home/jre/bin/java -Xms128m -Xmx512m oracle.rat.tfa.TFAMain /u01/app/oracle/tfa/racadrdb1/tfa_                              home  
 root@racadrdb1 #  
 root@racadrdb1 # /u01/app/oracle/tfa/racadrdb1/tfa_home/bin/tfactl status  
 .--------------------------------------------------------------------------------------------------.  
 | Host   | Status of TFA | PID  | Port | Version  | Build ID       | Inventory Status |  
 +-----------+---------------+-------+-------+------------+----------------------+------------------+  
 | racadrdb1 | RUNNING    | 11444 | 51235 | 12.2.1.0.0 | 12210020161122170355 | COMPLETE     |  
 '-----------+---------------+-------+-------+------------+----------------------+------------------'  
 root@racadrdb1 # /u01/app/oracle/tfa/racadrdb1/tfa_home/bin/tfactl stop  
 Stopping TFA from the Command Line  
 TFA is running - Will wait 5 seconds (up to 3 times)  
 TFA is running - Will wait 5 seconds (up to 3 times)  
 TFA is running - Will wait 5 seconds (up to 3 times)  
 TFAmain Force Stopped Successfully  
 TFA Stopped Successfully  
 . . .  
 Successfully stopped TFA..  
 root@racadrdb1 #
Once TFA was stopped, resuming opath successfully applied all patches on both database and grid homes.


Comments

Post a Comment

Popular posts from this blog

ORA-16433: The database or pluggable database must be opened in read/write

-
Image
ORA-16433 is an error returned when a database cannot be opened. This can be a result of multiple conditions including, The inconsistency of the database Physical corruption Loss of dependent files or access issues etc.. More often than not the solution is to recover from available backups, but there can be situations where backups are not available, specially on UAT or Test setups. Although not the ideal scenario, in this type of situation you might want to open the databases even with inconsistency.  In Comes --> _ALLOW_RESETLOGS_CORRUPTION First, if you are in a position to use _ALLOW_RESETLOGS_CORRUPTION=TRUE, that means it has to be a critical moment, and when you come across more ora- errors while you are trying to reopen the databsae, that can be annoying. Note - _ALLOW_RESETLOGS_CORRUPTION=TRUE must only be used after Oracle support confirmation as a last resort. Also make sure to take cold backup before proceeding. Basic steps to be followed to resolve ORA 16433 af...
Read more

Oracle Multitenant - Create new service for PDB using DBMS_SERVICE

-
Image
When an Oracle PDB is created it starts up a default service with the PDB name. For direct connections to    PDB this service can be used. But there are situations where new service name is required in PDB level, common example is after a PDB restoration/clone, in order to enable application connections without changes in connection string. Setting service_names parameter in PDB level is not possible hence it is not an option in multitenant setup. How to create a new PDB service on Oracle 12C Check the current services, here only the default service is running, SQL> show pdbs; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 3 NFACTORPDB READ WRITE NO SQL> select service_id, name, pdb from dba_Services; SERVICE_ID NAME PDB ---------- ---------------------------------------- ---------- 7 nfactorpdb NFACTORPDB SQL> ...
Read more

Wait for unread message on broadcast channel - Blocking Sessions

-
Image
What is Wait for unread message on broadcast channel wait event? Wait for unread message on broadcast channel is a wait event where source destination communication is involved and the database is waiting for a reply from remote party. Mostly this wait is seen related to data pump export (expdp) or import (impdp) operations. Although categorized in idle wait class "Wait for unread message on broadcast channel" can become the blocking session for some other sessions. Common causes for stuck sessions waiting on this wait event includes, Broken databases links, where remote database is not responding. Abnormally killed remote processes causing the sessions to wait. When a session is waiting on "Wait for unread message on broadcast channel" it can become a blocking session for dependent sessions. Most probably these sessions will be waiting on "library cache pin" or related concurrency wait events. The blocking_session column of (g)v$session view...
Read more