Forum Discussion

ajaydeshp's avatar
ajaydeshp
Level 3
5 years ago

Re: NetBackup 8.1.2 and Oracle RMAN

Thanks but this is a AS IS migration and we want all our existing RMAN scripts to work with 8.1.2. Now I have created legacy policies with schedule of type "Application Backup" and now I get different error:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 03/12/2020 10:47:17
ORA-19513: failed to identify sequential file
ORA-27206: requested file not found in media management catalog

10 Replies

  • ajaydeshp 

    I have moved your comment to a new discussion, as this is a new, different issue to your original post.

    Please give us more info :

    Did the job go active in Activity monitor?
    If so, what is the error message in Job Details?

    Could you please share the script and the rman '.out' file? 

    Do you have dbclient log folder on the Oracle client?
    If not, please create the log folder under /usr/openv/netbackup/logs and change permissions to 777.

    After next failure, please copy logs to rman.txt and dbclient.txt and upload as attachments.

    In the meantime, please also ensure that bprd log folder exists on the master. (NBU needs to be restarted after folder is created for the 1st time).
    bprd will show us how request from client is interpreted and why the request failed. 

    • Genericus's avatar
      Genericus
      Moderator

      Once you have the script path variable, and the script and rcv files, NetBackup hands over to RMAN.

      review your scripts for correct client name, correct policy name, etc.

      99% of the issues I see are typos in scripts.

      The other 1% is misconfiguration or local server permission issues.

       

    • ajaydeshp's avatar
      ajaydeshp
      Level 3

      Hi Marianne,

      I am testing with basic RMAN command: backup database it gives me this error:

      RMAN-00571: ===========================================================

      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

      RMAN-00571: ===========================================================

      RMAN-03009: failure of backup command on td1 channel at 03/14/2020 02:11:10

      ORA-19513: failed to identify sequential file

      ORA-27206: requested file not found in media management catalog

       

      ++++++++++++++++++++

      In dbext logs at client backup is shown as successful

       

      Backup by oracle on client ******* using policy ORABACKUP_LP49 , sched db:the requested operation was successfully completed

       

      ++++++++++++++++++

       

      Master server lists the backup

       bplist -C xxxxxxx -t 4 -l -R -s 03/13/20 /
      -rw-rw---- oracle dba 52038144K Mar 16 03:10 /ORA_ONL_BKUP_xxxxx_42386_1_1035169805

      -rw-rw---- oracle dba 52038144K Mar 13 03:10 /ORA_ONL_BKUP_xxxxx_42382_1_1034910604
      -

      +++++++++++++++++++++++

       

      It seems issue is with interaction between Master and media server. bprd logs are not enabledd on master server please provide steps to enable that and any additional debug to identify the issue.

       

      Ref:Oracle note RMAN Backup to tape using Legato Networker fails ORA-19513 and ORA-27206 (Doc ID 1312448.1)

       

      SYMPTOMS

      RMAN backup to SBT_TAPE using Legato Networker fails:

      channel t1: starting piece 1 at 11-04-08
      released channel: t1
      RMAN-00571: ===========================================================
      RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
      RMAN-00571: ===========================================================
      RMAN-03009: failure of backup command on t1 channel at 04/08/2011 11:16:29
      ORA-19513: failed to identify sequential file
      ORA-27206: requested file not found in media management catalog
      CHANGES

      A new DNS alias was created on the Network for the Server or new

      CAUSE

      This error is raised whenever the Media Manager, Legato Networker in this case, is unable to write the file to tape.

      The creation of new DNS alias can cause index corruption between TAPE and MNO interface inside Networker backup server.

       

      Thanks,

      Ajay

      • Marianne's avatar
        Marianne
        Level 6

        ajaydeshp 

        If you have a Legato Networker issue, then you should look for a Networker forum and post there.

        This is the Veritas NetBackup forum, for users with NetBackup software.

        If you have both products in the environment, then please note that you can only link one product's library in the oracle lib folder.