Avamar Oracle Backups were failing with the error message "Oracle not Available"

Avamar Oracle Backups were failing with the error message _Oracle not Available_ _ (home변경).pdf

0.09MB

요약: Avamar Oracle Backups were failing with the error message "Oracle not Available" error message

 

문서 콘텐츠

---

증상

This was a fresh Oracle install in an Avamar - IDPA Environment. Oracle backups were failing with the following error message

Following was recorded in the RMAN
connected to target database (not started)
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 04/02/2018 17:40:54
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
Recovery Manager complete.

Following was recorded in the Avoracle logs:

2018-04-02 17:41:02 avoracle Error <7934>: Snapup of PPGIS aborted due to rman terminated abnormally - check the logs
2018-04-02 17:41:02 avoracle Info <7271>: Final summary generated subwork 1, cancelled/aborted 1, snapview 0, exitcode 157

원인

Conflicting entries in the Oratab for the same database.

해결

First, we verified that the DB is in Archive Log Mode: 
 

SQL> select log_mode from v$database;
 
LOG_MODE
------------
ARCHIVELOG
 
SQL>

Then, we found if the database is in Running state
 

SQL> select open_mode,db_unique_name from v$database;
 
OPEN_MODE            DB_UNIQUE_NAME
-------------------- ------------------------------
READ WRITE           ppgis
database is running
 

SQL> select instance_name,status,database_status from v$instance;
 
INSTANCE_NAME    STATUS       DATABASE_STATUS
---------------- ------------ -----------------
ppgis            OPEN         ACTIVE
 
SQL>

We then checked the lsnrctl status:
 

[oracle@ppgisdb03 oracle11204]$ lsnrctl status
 
LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 02-APR-2018 18:20:44
 
Copyright (c) 1991, 2013, Oracle.  All rights reserved.
 
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=ppgisdb03)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                03-MAR-2018 22:56:41
Uptime                    29 days 19 hr. 24 min. 2 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oracle11204/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File         /oracle11204/app/oracle/diag/tnslsnr/ppgisdb03/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ppgisdb03)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
  Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "ppgis" has 1 instance(s).
  Instance "ppgis", status READY, has 1 handler(s) for this service...
Service "ppgisXDB" has 1 instance(s).
  Instance "ppgis", status READY, has 1 handler(s) for this service...
The command completed successfully

Finally, we checked the oratab file, 
 

[oracle@ppgisdb03 etc]$ cat oratab
#
# This file is used by ORACLE utilities.  It is created by root.sh
# and updated by either Database Configuration Assistant while creating
# a database or ASM Configuration Assistant while creating ASM instance.
 
# A colon, ':', is used as the field terminator.  A new line terminates
# the entry.  Lines beginning with a pound sign, '#', are comments.
#
# Entries are of the form:
#   $ORACLE_SID:$ORACLE_HOME:<N|Y>:
#
# The first and second fields are the system identifier and home
# directory of the database respectively.  The third filed indicates
# to the dbstart utility that the database should , "Y", or should not,
# "N", be brought up at system boot time.
#
# Multiple entries with the same $ORACLE_SID are not allowed.
#
#
PPGIS:/oracle/app/oracle/product/11.2.0/dbhome_1:N
ppgis:/oracle11204/app/oracle/product/11.2.0/dbhome_1:N

When we checked the Oracle Home information in oratab file, we found that the Oracle was started using the following ORACLE_HOME as :
/oracle11204/app/oracle/product/11.2.0/dbhome_1
But, Avamar rman plugin gets the ORACLE_HOME from oratab as:
PPGIS:/oracle/app/oracle/product/11.2.0/dbhome_1:N
Which was an invalid entry.

There were two options to resolve this:
a) We could have removed the invalid entry
b) We could point AvOracle to use the correct Home Directory

Because, we didn't want to make any changes to Oratab, we preferred the other option which was to point Avamar Oracle to correct Home Directory
So we setup the correct oracle home using avoracle.cmd file in /usr/local/avamar/var/avoracle.cmd
 
--oracle_home=/oracle11204/app/oracle/product/11.2.0/dbhome_1
 
After this change the backup started to run and completed successfully.

문서 속성

---

영향을 받는 제품

Avamar

제품

Avamar, Avamar Plug-in for Oracle, Integrated Data Protection Appliance Software

마지막 게시 날짜

20 11월 2020

버전

2

문서 유형

Solution