asteng5000
ADSM.ORG Member
We had a DR scenario where we had to restore the DB. However the DR process was not straight forward. We had to recreate the DB volumes and the Log volumes and then restore the latest backup copy of the DB.
All worked fine but then we started getting these error messages during migrations:
Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740958. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 5B3855D8 hdr version 39016 hdr length 50810 sequence number 1192815965 data length C63B859C server id -1836211519 segment id 10321090521601071163 crc 7AD892CD. (PROCESS: 225)
2005-10-13 13:46 ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740960. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 6E958C06 hdr version 11501 hdr length 10898 sequence number 1124953744 data length 64EA0519 server id 682445064 segment id 9149496896754115484 crc 0CD2CD9A. (PROCESS: 225)
2005-10-13 13:46 ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740962. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic C02DEF52 hdr version 5623 hdr length 28391 sequence number -1281831699 data length E76813FA server id -708628760 segment id 18086761016193466693 crc EE3E0565
At this stage we recreated all diskpools with data in it which was yet to be migrated because of the TSM server crash. The discard option was set to YES. This was done because we thought that some of the data may have been migrated prior to the server crash and because we had restored a DB previous to those migrated data, no reference was available in the DB.
Now the same kind of messages are appearing during the reclaim process in the copypool.
Can someone suggest how to tackle this.
We have TSM 5.2.3.3 server
All worked fine but then we started getting these error messages during migrations:
Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740958. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 5B3855D8 hdr version 39016 hdr length 50810 sequence number 1192815965 data length C63B859C server id -1836211519 segment id 10321090521601071163 crc 7AD892CD. (PROCESS: 225)
2005-10-13 13:46 ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740960. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 6E958C06 hdr version 11501 hdr length 10898 sequence number 1124953744 data length 64EA0519 server id 682445064 segment id 9149496896754115484 crc 0CD2CD9A. (PROCESS: 225)
2005-10-13 13:46 ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00000001 server id 00000000 segment id 0000000070740962. (PROCESS: 225)
2005-10-13 13:46 ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic C02DEF52 hdr version 5623 hdr length 28391 sequence number -1281831699 data length E76813FA server id -708628760 segment id 18086761016193466693 crc EE3E0565
At this stage we recreated all diskpools with data in it which was yet to be migrated because of the TSM server crash. The discard option was set to YES. This was done because we thought that some of the data may have been migrated prior to the server crash and because we had restored a DB previous to those migrated data, no reference was available in the DB.
Now the same kind of messages are appearing during the reclaim process in the copypool.
Can someone suggest how to tackle this.
We have TSM 5.2.3.3 server