DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: RMAN

  1. #1
    Join Date
    Aug 2000
    Posts
    52
    Hello !


    I have already taken the successful backup before two days only...and suddenly got this error.
    Please guide me to resolve following error.
    I will be highly oblige if you send full detail explaination.

    Sanjay
    --------------------------
    Oracle ver 8.0.6.0.0
    OS Sun solaris 5.7
    ---------------------------
    RMAN> run {
    2> allocate channel ch1 type 'SBT_TAPE'
    3> parms="ENV=(NB_ORA_CLASS=upsf_fprd75_hot)";
    4> allocate channel ch2 type 'SBT_TAPE'
    5> parms="ENV=(NB_ORA_CLASS=upsf_fprd75_hot)";
    6> allocate channel ch3 type 'SBT_TAPE'
    7> parms="ENV=(NB_ORA_CLASS=upsf_fprd75_hot)";
    8> allocate channel ch4 type 'SBT_TAPE'
    9> parms="ENV=(NB_ORA_CLASS=upsf_fprd75_hot)";
    10>
    11> # Enforce restrictions on:
    12> # - single backup piece < 2G;
    13> # - buffers to be read per file per second < 200;
    14> # - maximum files to be opened at any one time = 32.
    15> #setlimit channel ch1 kbytes 2097150 maxopenfiles 32 readrate 200;
    16>
    17> # Abort the backup if the system datafile has any corruptions.
    18> set maxcorrupt for datafile 1 to 0;
    19>
    20> backup full
    21> # skip offline
    22> # skip readonly
    23> skip inaccessible
    24> tag fprd75_hot_backup_full
    25> #filesperset 22
    26> format '%d_%t_%s_hot.dbf'
    27> (database);
    28>
    29> release channel ch1;
    30> release channel ch2;
    31> release channel ch3;
    32> release channel ch4;
    33>
    34> sql 'alter system archive log current';
    35>
    36> # Backup all archived logs to tape.
    37> allocate channel t1 type 'SBT_TAPE';
    38> allocate channel t2 type 'SBT_TAPE';
    39> allocate channel t3 type 'SBT_TAPE';
    40> allocate channel t4 type 'SBT_TAPE';
    41> backup
    42> format '%d_%t_%s.arc'
    43> #(archivelog like '/u01/oradata/fprd75/arch/% ' channel t1 delete input);
    44> (archivelog all);
    45> release channel t1;
    46> release channel t2;
    47> release channel t3;
    48> release channel t4;
    49> }
    50>
    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch1
    RMAN-08500: channel ch1: sid=39 devtype=SBT_TAPE

    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch2
    RMAN-08500: channel ch2: sid=88 devtype=SBT_TAPE

    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch3
    RMAN-08500: channel ch3: sid=101 devtype=SBT_TAPE

    RMAN-03022: compiling command: allocate
    RMAN-03023: executing command: allocate
    RMAN-08030: allocated channel: ch4
    RMAN-08500: channel ch4: sid=52 devtype=SBT_TAPE

    RMAN-03022: compiling command: set

    RMAN-03022: compiling command: backup
    RMAN-03023: executing command: backup
    RMAN-08008: channel ch1: starting datafile backupset
    RMAN-08502: set_count=4482 set_stamp=434262608
    RMAN-08010: channel ch1: including datafile 3 in backupset
    RMAN-08010: channel ch1: including datafile 49 in backupset
    RMAN-08010: channel ch1: including datafile 62 in backupset
    RMAN-08010: channel ch1: including datafile 1 in backupset
    RMAN-08008: channel ch2: starting datafile backupset
    RMAN-08502: set_count=4483 set_stamp=434262608
    RMAN-08010: channel ch2: including datafile 2 in backupset
    RMAN-08010: channel ch2: including datafile 48 in backupset
    RMAN-08010: channel ch2: including datafile 61 in backupset
    RMAN-08010: channel ch2: including datafile 68 in backupset
    RMAN-08010: channel ch2: including datafile 7 in backupset
    RMAN-08010: channel ch2: including datafile 59 in backupset
    RMAN-08010: channel ch2: including datafile 13 in backupset
    RMAN-08010: channel ch2: including datafile 9 in backupset
    RMAN-08010: channel ch2: including datafile 29 in backupset
    RMAN-08010: channel ch2: including datafile 42 in backupset
    RMAN-08010: channel ch2: including datafile 26 in backupset
    RMAN-08010: channel ch2: including datafile 6 in backupset
    RMAN-08010: channel ch2: including datafile 41 in backupset
    RMAN-08010: channel ch2: including datafile 53 in backupset
    RMAN-08010: channel ch2: including datafile 20 in backupset
    RMAN-08010: channel ch2: including datafile 25 in backupset
    RMAN-08010: channel ch2: including datafile 39 in backupset
    RMAN-08008: channel ch3: starting datafile backupset
    RMAN-08502: set_count=4484 set_stamp=434262608
    RMAN-08010: channel ch3: including datafile 58 in backupset
    RMAN-08010: channel ch3: including datafile 28 in backupset
    RMAN-08010: channel ch3: including datafile 60 in backupset
    RMAN-08010: channel ch3: including datafile 66 in backupset
    RMAN-08010: channel ch3: including datafile 56 in backupset
    RMAN-08010: channel ch3: including datafile 63 in backupset
    RMAN-08010: channel ch3: including datafile 24 in backupset
    RMAN-08010: channel ch3: including datafile 8 in backupset
    RMAN-08010: channel ch3: including datafile 18 in backupset
    RMAN-08010: channel ch3: including datafile 32 in backupset
    RMAN-08010: channel ch3: including datafile 55 in backupset
    RMAN-08010: channel ch3: including datafile 23 in backupset
    RMAN-08010: channel ch3: including datafile 50 in backupset
    RMAN-08010: channel ch3: including datafile 34 in backupset
    RMAN-08010: channel ch3: including datafile 33 in backupset
    RMAN-08010: channel ch3: including datafile 37 in backupset
    RMAN-08010: channel ch3: including datafile 46 in backupset
    RMAN-08008: channel ch4: starting datafile backupset
    RMAN-08502: set_count=4485 set_stamp=434262608
    RMAN-08010: channel ch4: including datafile 4 in backupset
    RMAN-08010: channel ch4: including datafile 5 in backupset
    RMAN-08010: channel ch4: including datafile 57 in backupset
    RMAN-08010: channel ch4: including datafile 64 in backupset
    RMAN-08010: channel ch4: including datafile 52 in backupset
    RMAN-08010: channel ch4: including datafile 12 in backupset
    RMAN-08010: channel ch4: including datafile 65 in backupset
    RMAN-08010: channel ch4: including datafile 10 in backupset
    RMAN-08010: channel ch4: including datafile 30 in backupset
    RMAN-08010: channel ch4: including datafile 43 in backupset
    RMAN-08010: channel ch4: including datafile 27 in backupset
    RMAN-08010: channel ch4: including datafile 11 in backupset
    RMAN-08010: channel ch4: including datafile 35 in backupset
    RMAN-08010: channel ch4: including datafile 51 in backupset
    RMAN-08010: channel ch4: including datafile 19 in backupset
    RMAN-08010: channel ch4: including datafile 22 in backupset
    RMAN-08010: channel ch4: including datafile 38 in backupset
    RMAN-08011: channel ch1: including current controlfile in backupset
    RMAN-08010: channel ch1: including datafile 47 in backupset
    RMAN-08010: channel ch1: including datafile 14 in backupset
    RMAN-08010: channel ch1: including datafile 14 in backupset
    RMAN-08010: channel ch1: including datafile 67 in backupset
    RMAN-08010: channel ch1: including datafile 17 in backupset
    RMAN-08010: channel ch1: including datafile 31 in backupset
    RMAN-08010: channel ch1: including datafile 44 in backupset
    RMAN-08010: channel ch1: including datafile 16 in backupset
    RMAN-08010: channel ch1: including datafile 15 in backupset
    RMAN-08010: channel ch1: including datafile 45 in backupset
    RMAN-08010: channel ch1: including datafile 54 in backupset
    RMAN-08010: channel ch1: including datafile 21 in backupset
    RMAN-08010: channel ch1: including datafile 36 in backupset
    RMAN-08010: channel ch1: including datafile 40 in backupset
    RMAN-00569: ================error message stack follows================
    RMAN-03007: retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel ch3
    RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
    ORA-19506: failed to create sequential file, name="FPRD75_434262608_4484_hot.dbf
    ", parms=""
    ORA-27007: failed to open file
    SVR4 Error: 17335756: Unknown system error
    Additional information: 7009
    Additional information: 1
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 408
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE
    ATE

    RMAN-08010: channel ch1: including datafile 14 in backupset
    RMAN-08010: channel ch1: including datafile 67 in backupset
    RMAN-08010: channel ch1: including datafile 17 in backupset
    RMAN-08010: channel ch1: including datafile 31 in backupset
    RMAN-08010: channel ch1: including datafile 44 in backupset
    RMAN-08010: channel ch1: including datafile 16 in backupset
    RMAN-08010: channel ch1: including datafile 15 in backupset
    RMAN-08010: channel ch1: including datafile 45 in backupset
    RMAN-08010: channel ch1: including datafile 54 in backupset
    RMAN-08010: channel ch1: including datafile 21 in backupset
    RMAN-08010: channel ch1: including datafile 36 in backupset
    RMAN-08010: channel ch1: including datafile 40 in backupset
    RMAN-00569: ================error message stack follows================
    RMAN-03007: retryable error occurred during execution of command: backup
    RMAN-07004: unhandled exception during command execution on channel ch3
    RMAN-10035: exception raised in RPC: ORA-19624: operation failed, retry possible
    ORA-19506: failed to create sequential file, name="FPRD75_434262608_4484_hot.dbf
    ", parms=""
    ORA-27007: failed to open file
    SVR4 Error: 17335756: Unknown system error
    Additional information: 7009
    Additional information: 1
    ORA-06512: at "SYS.DBMS_BACKUP_RESTORE", line 408
    RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE.BACKUPPIECECRE
    ATE

    Recovery Manager complete.

  2. #2
    Join Date
    Feb 2000
    Location
    New York,U.S.A.
    Posts
    245
    I would suggest you check and verify that the third party's storage subsystem product is operating properly.

    Dragon

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width