RMAN Issues and Solutions – (ORA-00020) and (ORA-00245)
Error-1:
RMAN failed to connect target database with ORA-00020: maximum number of processes (150) exceeded
Solution:
Here, we can see in error as maximum number of processes has exceeded.
So, we need to Increase the number of processes from sys user with sysdba privilege which may help here as shown below:
SQL> show parameter processes;
NAME TYPE VALUE
———————————— ———– ——————————
processes integer 150
SQL> alter system set processes=300 scope=spfile;
System altered.
SQL>
Bounce the database so changes will be reflected in database instance and then you can initiate RMAN backup.
Error-2:
$ pwd
/rmanbkp/ORA-DATA/backup
$ cat rman_ORA-DATA_full-18Jan2021.log
Starting backup at 18-Jan-21
channel c1: starting full datafile backup set
channel c1: specifying datafile(s) in backup set
released channel: c1
released channel: c2
released channel: c3
released channel: c4
released channel: c5
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 18/01/2021 07:22:25
ORA-00245: control file backup failed; target is likely on a local file system
Recovery Manager complete.
Solution:
As we can see that control file backup is failed. So we checked for RMAN configuration as shown below:
Before:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORA-DATA are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default
CONFIGURE COMPRESSION ALGORITHM ‘BASIC’ AS OF RELEASE ‘DEFAULT’ OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘$ORACLE_HOME/dbs/snapcf_ORA-DATA.f’; # default
RMAN>
In above configuration, we can see that CONTROLFILE autobackup is OFF.
So, we enabled it as shown below command.
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON;
After:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name ORA-DATA are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘/rmanbkp/ORA-DATA/backup/csfiles/%F’;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM ‘AES128’; # default
CONFIGURE COMPRESSION ALGORITHM ‘BASIC’ AS OF RELEASE ‘DEFAULT’ OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘+DATA /ORA-DATA/CONTROLFILE/snapcf_ORA-DATA.f’;