iginal Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Del Hoobler
> Sent: Tuesday, October 30, 2007 12:11 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] ANS0328E
>
> Please review this:
>
>
> http://www-1.ibm.com/support/d
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Tuesday, October 30, 2007 12:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANS0328E
Please review this:
http://www-1.ibm.com/support/docview.wss?uid=swg1IC31372
"ADSM: Dist Stor Manager"
Please review this:
http://www-1.ibm.com/support/docview.wss?uid=swg1IC31372
"ADSM: Dist Stor Manager" wrote on 10/30/2007
12:44:22 PM:
> MSSQL dba tells me that his backups have been failing for weeks with
> ANS0328E (text below). A select on the backup table shows succ
PROTECTED] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Tuesday, October 30, 2007 12:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] ANS0328E
Seems to be a design issue.
A quick Google search says you get this is you have changed the
management
class and already have SQL backups for this node. You
]>
Sent by: "ADSM: Dist Stor Manager"
10/30/2007 12:45 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
[ADSM-L] ANS0328E
MSSQL dba tells me that his backups have been failing for weeks with
ANS0328E (text below). A select on the backup
MSSQL dba tells me that his backups have been failing for weeks with
ANS0328E (text below). A select on the backup table shows successful
backups all month, but mostly full backups. Is the transaction log not
getting added properly?
Server is at 5.4.1.2, TDP at latest available.
ANS0328EThe
t;From: Del Hoobler <[EMAIL PROTECTED]>
>Subject: Re: [ADSM-L] ANS0328E
>To: ADSM-L@VM.MARIST.EDU
>
>Fred,
>
>That should work as well, you will just want to make sure
>that all the filespaces are renamed in the same manner,
>following the naming standard.
>
>
Fred,
That should work as well, you will just want to make sure
that all the filespaces are renamed in the same manner,
following the naming standard.
For example, assume you original filespaces are:
SERVER1\meta\
SERVER1\data\0001
SERVER1\data\0002
SERVER1\data\0003
Rena
sage
>Date: Wed, 14 Mar 2007 12:12:30 -0400
>From: Del Hoobler <[EMAIL PROTECTED]>
>Subject: Re: [ADSM-L] ANS0328E
>To: ADSM-L@VM.MARIST.EDU
>
>Hi Fred,
>
>This is a known issue. Search on Google, www.ibm.com,
>and/or this list and you will see multiple
t; We changed the management class on a group of MSSQL machines
> and started to see a lot of errors coming from MSSQL that
> also cause failed backups. The DBA tried to do a manual
> backup and received ANS0328E.
>
> Fred Johanson
We changed the management class on a group of MSSQL machines
and started to see a lot of errors coming from MSSQL that
also cause failed backups. The DBA tried to do a manual
backup and received ANS0328E.
Fred Johanson
ect: TDP for SQL messages - ACO0302E ... rc = 1301 ... ANS0328E
(RC45)
These messages appear in the tdpsql.log file (TDP SQL 2.2.0, 2.2.0.01, and
2.2.1) from time to time (seems to follow changing management classes for a
database backup):
ACO0302E A failure occured on stripe number (
> ACO0302E A failure occured on stripe number (0), rc = 1301
> ANS0328E (RC45) The specified objects failed the merge test.
> .
> Does anyone know what is causing these, whether they are serious (our
DBAs
> do not trust the backups that produce them,) and what I can do to prevent
These messages appear in the tdpsql.log file (TDP SQL 2.2.0, 2.2.0.01, and
2.2.1) from time to time (seems to follow changing management classes for a
database backup):
ACO0302E A failure occured on stripe number (0), rc = 1301
ANS0328E (RC45) The specified objects failed the merge test.
Our
14 matches
Mail list logo
