VDB fails to start with ORA-46362 after Oracle patching (KBA9472)
KBA
KBA# 9472
Issue
Post Oracle patching, starting a VDB from Delphix fails with:
Environment 10.10.1.111 1. OS user 'oracle' failed to connect to sqlplus for Oracle Home '/u01/apps/oracle/vdb/19.0.0.0/dbhome_1' on host 'ip-10.10.1.111.intranet.local (10.10.1.111)'. 2. OS user 'oracle' failed to connect to RMAN for Oracle Home '/u01/apps/oracle/vdb/19.0.0.0/dbhome_1' on host 'ip-10.10.1.111.intranet.local (10.10.1.111)'. 1. Make sure that the OS User has SYSBACKUP (12c only) or SYSDBA permissions for this Oracle Home and is able to execute sqlplus. SYSDBA privileges are required for target environments. Output: ' SQL*Plus: Release 19.0.0.0.0 - Production on Fri Aug 19 16:01:26 2022 Version 19.15.0.0.0 Copyright (c) 1982, 2022, Oracle. All rights reserved. ERROR: ORA-46362: Could not translate variable ORACLE_BASE. ORA-46362: Could not translate variable ORACLE_BASE. Enter user-name: 2. Make sure that the OS User has SYSBACKUP (12c only) or SYSDBA permissions for this Oracle Home and is able to execute RMAN. SYSDBA privileges are required for target environments. Output: ' Recovery Manager: Release 19.0.0.0.0 - Production on Fri Aug 19 16:01:27 2022 Version 19.15.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. RMAN> RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== ORA-46362: Could not translate variable ORACLE_BASE. ORA-46362: Could not translate variable ORACLE_BASE. RMAN> Recovery Manager complete.
All of the Oracle environment variables appear correct in the Delphix UI including ORACLE_HOME and ORACLE_BASE.
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
-
Major Release All Sub Releases 6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1, 6.0.11.0, 6.0.12.0, 6.0.12.1, 6.0.13.0, 6.0.13.1, 6.0.14.0, 6.0.15.0
5.3
5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0 5.2
5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1
5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0
5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4
Resolution
This issue has been encountered when using vFiles for the ORACLE_HOME on the target host, although this issue could occur otherwise. The problem is the $ORACLE_HOME/install/orabasetab
file contains the incorrect ORACLE_HOME value.
For example, the ORACLE_HOME is:
/u01/apps/oracle/vdb/19.0.0.0/dbhome_1
The $ORACLE_HOME/install/orabasetab has an incorrect value for the ORACLE_HOME
. For example:
[oracle@host install]$ cat orabasetab #orabasetab file is used to track Oracle Home associated with Oracle Base /u01/app/oracle/wrong/19.0.0.0/dbhome_1:/u01/app/oracle:OraHome1:N:
The value of the first field in the orabasetab
file above is incorrect. Correcting the value and rerunning the VDB start job resolves the issue. Correction below:
[oracle@host install]$ cat orabasetab #orabasetab file is used to track Oracle Home associated with Oracle Base /u01/app/oracle/vdb/19.0.0.0/dbhome_1:/u01/app/oracle:OraHome1:N:
Related Articles
The following articles may provide more information or related information to this article: