FIX: Expired Dump Media Cannot Be Overwritten After 12/31/99
Article ID: 192953
Article Last Modified on 3/14/2006
APPLIES TO
- Microsoft SQL Server 6.5 Standard Edition
- Microsoft SQL Server 6.5 Enterprise Edition
This article was previously published under Q192953
BUG #: 17947 (SQLBUG_65)
SYMPTOMS
An expired dump will not be able to be overwritten if the system time has
moved beyond 12/31/99.
WORKAROUND
To work around this problem, delete the existing dump image before
attempting the dump.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:
197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a
For more information, contact your primary support provider.
MORE INFORMATION
You can use the DUMP statement options EXPIREDATE and RETAINDAYS to specify
the expiration date of a dumped image. The expiration date specifies when a
subsequent DUMP (with the INIT option) should be able to overwrite the
previous dump image.
If an expiration date has been specified, then after the system time has
moved past 12/31/99, this dumped image cannot be overwritten.
You can get confirmation that an expiration date was specified by examining
the ExpireDate column from the LOAD HEADERONLY statement.
For the syntax and more information on the DUMP and LOAD statements and the
EXPIREDATE and RETAINDAYS options, see the SQL Server Books Online.
Additional query words: prodsqlsp sp5Year 2000 y2k 2k ExpireDate
Keywords: kbbug kbfix kbsqlserv650sp5fix KB192953