This is a multi-part message in MIME format.
------=_NextPart_000_0000_01C37BE4.1776AFC0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
I haven't seen this specific error before, but it may not be so generic as
you think. Is the backup script you are running using wildcards in the
backup file FORMAT specifer? In the RMAN script that you are using, there
is a stanza that looks like this
BACKUP
$BACKUP_TYPE # this is my addition - ignore it
SKIP INACCESSIBLE
FILESPERSET 4
FORMAT 'bk_u%u_s%s_p%p_t%t'
TAG 'hot_db_backup_full'
DATABASE
INCLUDE CURRENT CONTROLFILE;
The "filenames" used to identify the pieces of an RMAN backup are determined
by the FORMAT line. The %<char> specifiers are wildcards for the time,
backup set, backup set piece, etc. Before the backup client starts a
backup, it constructs the name of "file" being backed up as determined by
the FORMAT; e.g.: /bk_u345_s123_p01_t165889. It then queries the NBU
catalog for a "file" with this name. The error you are getting seems to say
that it is finding such a file (which really shouldn't exist).
Steve is right about creating the dbclient directory. You might also want
to turn debugging up to 5 on this client to get a detailed log.
Mark Hickey
Senior Technology Consultant
Glasshouse Technologies
www.glasshouse.com
Steve Sesar wrote:
====================================
On the backup client, create the directory,
/opt/openv/netbackup/logs/dbclient, if you haven't already. Make the
directory world-readable/writable, bounce NBU, and rerun your backup.
This error you're getting is more or less a generic error when RMAN has
a problem with the media management layer, in this case, NBU.
HTH,
Steve
Sam Grover wrote:
> Ok.. so I'm having a seemingly random error popping out of RMAN that
> is affecting our oracle backups. The RMAN session seems to kick off,
> it prepares the files to be backed up... allocated channels for tape..
> and then..
>
> RMAN-00571: ===========================================================
> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
> RMAN-00571: ===========================================================
> RMAN-00579: the following error occurred at 09/15/2003 11:09:31
> RMAN-03007: retryable error occurred during execution of command:
> Control File Autobackup
> RMAN-12004: unhandled exception during command execution on channel
> ORA_SBT_TAPE_1
> RMAN-10035: exception raised in RPC: ORA-19506: failed to create
> sequential file, name="c-2687215805-20030915-00", parms=""
> ORA-27028: skgfqcre: sbtbackup returned error
> ORA-19511: Error received from media manager layer, error text:
> sbtbackup: Backup file already exists.
> RMAN-10031: ORA-19624 occurred during call to
> DBMS_BACKUP_RESTORE.BACKUPPIECECREATE
>
> Recovery Manager complete.
>
>
> any ideas on where to look to resolve this one? Any help is appreciated.
>
> Thank you,
>
> Sam Grover
------=_NextPart_000_0000_01C37BE4.1776AFC0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1252">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>RE: Veritas-bu digest, Vol 1 #2512 - 5 msgs</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>I haven't seen this specific error before, but it may =
not be so generic as you think. Is the backup script you are =
running using wildcards in the backup file FORMAT specifer? =
In the RMAN script that you are using, there is a stanza that looks like =
this</FONT></P>
<P><FONT SIZE=3D2>BACKUP</FONT>
<BR><FONT SIZE=3D2> $BACKUP_TYPE # this is my =
addition - ignore it</FONT>
<BR><FONT SIZE=3D2> SKIP INACCESSIBLE</FONT>
<BR><FONT SIZE=3D2> FILESPERSET 4</FONT>
<BR><FONT SIZE=3D2> FORMAT 'bk_u%u_s%s_p%p_t%t'</FONT>
<BR><FONT SIZE=3D2> TAG 'hot_db_backup_full'</FONT>
<BR><FONT SIZE=3D2> DATABASE</FONT>
<BR><FONT SIZE=3D2> INCLUDE CURRENT =
CONTROLFILE;</FONT>
</P>
<P><FONT SIZE=3D2>The "filenames" used to identify the pieces =
of an RMAN backup are determined by the FORMAT line. The =
%<char> specifiers are wildcards for the time, backup set, backup =
set piece, etc. Before the backup client starts a backup, it =
constructs the name of "file" being backed up as determined by =
the FORMAT; e.g.: /bk_u345_s123_p01_t165889. It then queries the =
NBU catalog for a "file" with this name. The error you =
are getting seems to say that it is finding such a file (which really =
shouldn't exist). </FONT></P>
<P><FONT SIZE=3D2>Steve is right about creating the dbclient =
directory. You might also want to turn debugging up to 5 on this =
client to get a detailed log.</FONT></P>
<P><FONT SIZE=3D2>Mark Hickey</FONT>
<BR><FONT SIZE=3D2>Senior Technology Consultant</FONT>
<BR><FONT SIZE=3D2>Glasshouse Technologies</FONT>
<BR><FONT SIZE=3D2>www.glasshouse.com</FONT>
</P>
<P><FONT SIZE=3D2>Steve Sesar wrote:</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
</P>
<P><FONT SIZE=3D2>On the backup client, create the directory, </FONT>
<BR><FONT SIZE=3D2>/opt/openv/netbackup/logs/dbclient, if you haven't =
already. Make the </FONT>
<BR><FONT SIZE=3D2>directory world-readable/writable, bounce NBU, and =
rerun your backup.</FONT>
</P>
<P><FONT SIZE=3D2>This error you're getting is more or less a generic =
error when RMAN has </FONT>
<BR><FONT SIZE=3D2>a problem with the media management layer, in this =
case, NBU.</FONT>
</P>
<P><FONT SIZE=3D2>HTH,</FONT>
</P>
<P><FONT SIZE=3D2>Steve</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=3D2>Sam Grover wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> Ok.. so I'm having a seemingly random error =
popping out of RMAN that </FONT>
<BR><FONT SIZE=3D2>> is affecting our oracle backups. The RMAN =
session seems to kick off, </FONT>
<BR><FONT SIZE=3D2>> it prepares the files to be backed up... =
allocated channels for tape.. </FONT>
<BR><FONT SIZE=3D2>> and then..</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> RMAN-00571: =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>> RMAN-00569: =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D ERROR MESSAGE STACK =
FOLLOWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>> RMAN-00571: =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>> RMAN-00579: the following error occurred at =
09/15/2003 11:09:31</FONT>
<BR><FONT SIZE=3D2>> RMAN-03007: retryable error occurred during =
execution of command: </FONT>
<BR><FONT SIZE=3D2>> Control File Autobackup</FONT>
<BR><FONT SIZE=3D2>> RMAN-12004: unhandled exception during command =
execution on channel </FONT>
<BR><FONT SIZE=3D2>> ORA_SBT_TAPE_1</FONT>
<BR><FONT SIZE=3D2>> RMAN-10035: exception raised in RPC: ORA-19506: =
failed to create </FONT>
<BR><FONT SIZE=3D2>> sequential file, =
name=3D"c-2687215805-20030915-00", parms=3D""</FONT>
<BR><FONT SIZE=3D2>> ORA-27028: skgfqcre: sbtbackup returned =
error</FONT>
<BR><FONT SIZE=3D2>> ORA-19511: Error received from media manager =
layer, error text:</FONT>
<BR><FONT SIZE=3D2>> sbtbackup: Backup file already =
exists.</FONT>
<BR><FONT SIZE=3D2>> RMAN-10031: ORA-19624 occurred during call to =
</FONT>
<BR><FONT SIZE=3D2>> DBMS_BACKUP_RESTORE.BACKUPPIECECREATE</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Recovery Manager complete.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> any ideas on where to look to resolve this one? =
Any help is appreciated.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Thank you,</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Sam Grover</FONT>
</P>
</BODY>
</HTML>
------=_NextPart_000_0000_01C37BE4.1776AFC0--
|
