PowerProtect: Oracle backups fail with ABO0022: because of an internal error
Summary: PowerProtect Data Manager (PPDM) Oracle backups fail with "ABO0022: PowerProtect Data Manager Oracle agent cannot perform the backup for the Oracle database DBNAME with database ID DBID because of an internal error." ...
Symptoms
During a PPDM Oracle backup that a centralized protection policy initiates, the backup of the Oracle database fails. And the following error appears in the Protection Jobs window:
ABO0022: PowerProtect Data Manager Oracle agent cannot perform the backup for the Oracle database db19 with database ID 854318690 because of an internal error. The backup is unsuccessful because of an SBT error that is caused by the loss of DD connectivity or by an Oracle RMAN error. Check the DD connectivity from the client. Edit the required protection policy to enable the debug logging. Resubmit the backup request, and check the sbtio.log file under $ORACLE_BASE. Make sure that the database is running during the backup. RMAN-06149: cannot BACKUP DATABASE in NOARCHIVELOG mode Recovery Manager complete.
Cause
In order to perform online Oracle online backups, the target database must be running in archivelog mode. This is an Oracle requirement. PPDM centralized protection policies cannot change the mode of the database during the backup, that is, shutdown DB, startup mount, then perform backup. The expectation is that Oracle db is open and in the appropriate archive log mode state.
Resolution
Ensure that the target database is in archivelog mode. For example:
Connect to the target database over sqlplus and issue the command archive log list.
sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 - Production on Mon Dec 4 22:05:42 2023 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.3.0.0.0 SQL> archive log list; Database log mode No Archive Mode Automatic archival Disabled Archive destination USE_DB_RECOVERY_FILE_DEST Oldest online log sequence 16 Current log sequence 18 SQL>
The above example shows that the databas is in no archive log mode.
The DBA must switch the database into archivelog mode. This would require the DB to be shut down, and started in the appropriate mode.