Bruce
It may not apply in your case, but check out APAR IC31372.
Neil Schofield
APAR= IC31372 SER= MS MSGANS0246E
ANS0246E RC2070 ANS0328E RC45 TDP MS SQL DATA LOSS
Status: CLOSED Closed: 08/30/01
Apar Information:
RCOMP= 5698DPSCL TDP FOR MS SQL/ RREL= R22W
FCOMP= 5698DPSCL TDP FOR MS SQL/ PFREL= F999 TREL= T
SRLS: NONE
Return Codes:
Applicable Component Level/SU:
R22W PSY UP
Error Description:
Changes to management classes and their related copy
destinations for TDP for MS SQL data and data objects can
lead to data loss due to a defect in the TDP for MS SQL code.
.
The actual data loss will be observed based on the
following error message in the dsierror.log all with the
TDP SQL messages following below:
ANS0246E (RC2070) Issue dsmEndTxn and then begin a new
transaction session.
.
A SERVICE,API trace of the API will show the following
backupdb.cpp(8573):Calling AGTDSMRCMSG( 2070 )
backupdb.cpp(8584):AGTDSMRCMSG() completed
backupdb.cpp(8590):DSMSENDOBJ() failed, rc = 2070, msg =
ANS0246E (RC2070) Issue dsmEndTxn and then begin a
new transaction session.
......
backupdb.cpp(8990):Exit CBackupDb::mergeErrorFixup(), rc = 418
backupdb.cpp(5271):Unable to to correct rename merge error!
mergeErrorFixup() failed, rc = 418, msg = ANS0328E (RC45)
The specified objects failed the merge test.
.
The TDP for MS SQL code will show the following errors in
the tdpsql.log:
ANS0328E (RC45) The specified objects failed the merge
test.
ACO0151E Errors occurred while processing the request.
.
These errors may occur due to other problems encountered
and do not indicate data loss unless the above errors and
trace data are seen as well:
.
The problem occurs during processing that happens after a
change to the management classes that the TDP for MS SQL data
are going to. If the management class is changed, TDP attempts
to rectify information on the server about the TDP for MS SQL
data. TDP fails to perform this correctly when the copy
destinations of the management classes are different and lose
the last active object before the management class and copy
destination changes.
.
This data loss can be verified with a comparison of the
TDPSQLC QUERY and SELECT * FROM BACKUPS server query for
the TDP for MS SQL nodename.
.
This applies strictly to a change in a management class that
results in multiple copy destinations. The customer is still
able to change management classes that data and meta data go
to as long as the copy destinations of all management classes
are the same. It is only when multiple copy destinations are
used that data loss occurs.
.
Initial Severity: High
.
Additional Keywords:
SEQUEL DATA PROTECTION MICROSOFT SQL DATA INTEGRITY LOSS
MSANS0246E MSANS0328E MSGANS0328E
Local Fix:
TDP for MS SQL documentation recommends the following setup
for policy in regards to data and meta data backups:
"Data objects and their associated meta objects should have
the same version limits and retention values. However,
because meta objects may need to be restored as a result of
a TDP for SQL query, you may want to consider storing meta
objects in a disk-only storage pool so that a media mount is
not necessary to resolve the query. To do this, one can:
1. Define a separate management class with a Copy
Destination pointing to a disk pool that does not have
any removable media in its hierarchy.
2. Bind all meta objects to that management class using an
INCLUDE statement in the TDP for SQL options file. "
.
If customers adhere to these recommendations and have not
changed their management classes and copy destinations,
then no data loss will occur. It is only when a change has
been made (after prior backups have already been perfomred)
where multiple copy destinations are used that data loss
will occur.
.
If a customer is experiencing this problem they need to setup
their management classes how they would prefer, create a new
node name and then perform a full backup of their databases.
They must continue to use these management classes and copy
destinations until this problem is resolved.
.
If any changes are made to management class copy destinations
until this problem is resolved, data loss can occur.
Problem Summary:
****************************************************************
* USERS AFFECTED: TDP SQL users who have multiple copy *
* destinations *
****************************************************************
* PROBLEM DESCRIPTION: When backup objects are directed to *
* multiple copy destinations and the *
* management classes are changed, a *
* transaction error will cause the last *
* active copy of the object to be deleted *
****************************************************************
* RECOMMENDATION: Obtain the TDPS ptf when available *
****************************************************************
Temporary Fix:
Comments:
MODULES/MACROS: EXE SQLDSMC
Problem Conclusion:
The mergeErrorFixup routine incorrectly set dummyObjCreated to
bTrue and incorrectly deleted the current active backup when
multiple copy destinations were used and a transaction error
occured. The routine will be fixed by setting dummyObjCreated
to bTrue only when the dsmEndTxn is successful and the Vote is
Commit.
The information in this e-mail is confidential and may also be legally
privileged. The contents are intended for recipient only and are subject
to the legal notice available at http://www.keldagroup.com/email.htm
Yorkshire Water Services Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682
