RMAN backup fails with ORA-19513 and ORA-27206 error

Today we received a mail regarding RMAN backup of archive log to tape got failed from the customer.

RMAN backup error details are below

RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 05/06/2014 20:05:31

ORA-19513: failed to identify sequential file

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

From the above message we can easily identify that they are taking a backup to tape directly from the network server not from the db server.

I have checked MOSC note related to the above error & found one document which is described below.

The MOSC note is " RMAN Backup to tape using Legato Networker fails ORA-19513 and ORA-27206 (Doc ID 1312448.1)"

According to that note,

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.

SOLUTION

Delete the host definition inside Networker and recreate it in order to flush bad index.

Also try using client hostname with domain extension instead of using client IP address in Netbackup Master Server while configuring backup policy for client

For further assistance please contact your media manager vendor .

Comments

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...

Cloud Control EM13c - Loader Throughput (rows per second) for Loader_D crossed the critical threshold and Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold

Hello Guys, Here is an another post related to Cloud Control EM13c - Real-time Scenario. Suddenly We were receiving the following warning and critical alerts from EM13c Cloud Control during the time slot between 12 AM and 04:00 AM daily. 1) Message= Loader Throughput (rows per second) for Loader_D crossed the critical threshold (xx). Current value: xx.xx 2) Message= Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold (x,xxx). Current value: xxxx.xx 3) ORA-error stack (3,136) and ORA-error stack (609) were also logged in alert log 4) Message= Incident (BEA-310003 [LowMemory]) detected in $OMS_HOME/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml at time/line number: When we analyzed the AWR reports of EM PDB repository database, we found there were few PL/SQL statements given below causing this issue with wait event SQL*Net Break/reset To Client...

Oracle Database Administration

Search This Blog