ORA-12777: A non-continuable error encountered.

This post is also available at: Português

Scenario

I needed to apply the 19.26 patch to a database, and every way was giving me an error.
My last attempt was:
– copy the current ORACLE_HOME, with the 19.25 patch
– change the name to 19.26
– upload the database to the ORACLE_HOME that was copied
– and apply the patch to it.

E.g:

# mkdir -p /u01/app/oracle/product/19.26.0.0/dbhome_1
# cp -pR /u01/app/oracle/product/19.25.0.0/dbhome_1 /u01/app/oracle/product/19.26.0.0/dbhome_1
# chown -R oracle:oinstall /u01/app/oracle/product/19.26.0.0/dbhome_1
ShellScript

When I started the database from the new home, the following error occurred:

$ srvctl start database -d dmdsbr01

PRCR-1079 : Failed to start resource ora.dmdsbr01.db

CRS-5017: The resource action "ora.dmdsbr01.db start" encountered the following error:

ORA-12777: A non-continuable error encountered.  Check the error stack for additional information [ksm_check_ob_paths:1], [ORACLE_BASE], [], [].

ORA-08275: Environment variable unset

. For details refer to "(:CLSN00107:)" in "/u01/app/oracle/diag/crs/cealdmdsbr01/crs/trace/ohasd_oraagent_oracle.trc".

 

CRS-2674: Start of 'ora.dmdsbr01.db' on 'cealdmdsbr01' failed
ShellScript

As I copied the binary, the orabasetab file had the information from the old ORACLE_HOME.

cat /u01/app/oracle/product/19.26.0.0/dbhome_1/install/orabasetab

#orabasetab file is used to track Oracle Home associated with Oracle Base
/u01/app/oracle/product/19.25.0.0/dbhome_1:/u01/app/oracle:Orasidb19c_home1_583:N:
ShellScript

Correction

To fix this, I had to add the new ORACLE_HOME to the inventory. And then update the orabasetab file.

$ORACLE_HOME/oui/bin/runInstaller -attachhome ORACLE_HOME=/u01/app/oracle/product/19.26.0.0/dbhome_1 ORACLE_HOME_NAME=OraDB19Home3
ShellScript
cat /u01/app/oracle/product/19.26.0.0/dbhome_1/install/orabasetab

#orabasetab file is used to track Oracle Home associated with Oracle Base
/u01/app/oracle/product/19.26.0.0/dbhome_1:/u01/app/oracle:OraDB19Home3:N:
ShellScript

After making the adjustments, the database started up normally.

$ srvctl start database -d dmdsbr01

$ ps -ef | grep pmon

oracle    191871       1  0 14:30 ?        00:00:00 asm_pmon_+ASM
oracle    198392       1  0 14:59 ?        00:00:00 ora_pmon_dmdsbr01
ShellScript
Previous Article

OPATCHAUTO-72083: Performing bootstrap operations failed.

Next Article

Error installing Oracle Grid Infrastructure on Red Hat 8

Write a Comment

Leave a Comment

Your email address will not be published. Required fields are marked *