7 Replies Latest reply: Jan 20, 2013 10:22 PM by 969526 RSS

    RMAN ERROR

    969526
      Hi,

      When I am executing the Delete Obsolete command i am getting the following error.

      RMAN> delete obsolete;

      RMAN retention policy will be applied to the command
      RMAN retention policy is set to recovery window of 30 days
      allocated channel: ORA_DISK_1
      channel ORA_DISK_1: sid=278 devtype=DISK
      released channel: ORA_DISK_1
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03002: failure of delete command at 01/19/2013 17:06:09
      RMAN-12001: could not open channel ORA_SBT_TAPE_1
      RMAN-10008: could not create channel context
      RMAN-10003: unable to connect to target database
      ORA-01031: insufficient privileges

      Please suggest the solution...
        • 1. Re: RMAN ERROR
          mseberg
          Hello;

          Is it possible the password file is missing?

          Or did somebody change the password?

          Best Regards

          mseberg
          • 2. Re: RMAN ERROR
            969526
            No i dont think so. I am able to connect the target database using that same password.
            • 3. Re: RMAN ERROR
              mseberg
              Post :

              RMAN> show all;

              Best Regards

              mseberg
              • 4. Re: RMAN ERROR
                969526
                RMAN> show all;

                RMAN configuration parameters are:
                CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS;
                CONFIGURE BACKUP OPTIMIZATION OFF; # default
                CONFIGURE DEFAULT DEVICE TYPE TO DISK;
                CONFIGURE CONTROLFILE AUTOBACKUP ON;
                CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
                CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
                CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
                CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
                CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
                CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
                CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
                CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
                CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'F:\Rman_Prod\Backup%d_DB_%u_%s_%p_%a';
                CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' CONNECT '*';
                CONFIGURE MAXSETSIZE TO UNLIMITED; # default
                CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
                CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
                CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
                CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFORCL.ORA'; # default

                RMAN>

                i joined this company recently.

                Today i change the RETENTION POLICY TO RECOVERY WINDOW OF 30 DAYS.... previously it was set to 7.

                and when i check for report obsolete i find obsolete data are there from 2010
                • 5. Re: RMAN ERROR
                  mseberg
                  Hello again;

                  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' CONNECT '*';

                  If this is NOT a RAC environment the CONNECT should not be needed. So if is correct remove it and try again.

                  Otherwise I'm not seeing it.

                  Best Regards

                  mseberg
                  • 6. Re: RMAN ERROR
                    TSharma-Oracle
                    Can you run other commands like crosscheck backup? Do you get any error?
                    • 7. Re: RMAN ERROR
                      969526
                      I Case of crosscheck Backup i am also getting the same error.