Problem Note 4165: Catalog becomes corrupted leaving header information unreadable
Any operation that writes to a SAS catalog may potentially corrupt the
catalog preventing future additions to the catalog. The problem occurs
as the catalog is being closed. Specifically, if the current page
becomes full during the close operation thus requiring an additional
page, the header information does not correctly track the new page. If a
catalog entry is shortened on a subsequent operation, the catalog may be
incorrectly truncated losing the page that was not correctly tracked.
This prevents the catalog from being updated again but does not prevent
read access.
The following error message occurs when an attempt is made to update a
catalog where this corruption has occurred. It can occur in any product
or procedure which writes to a catalog.
ERROR: Unable to read header information for catalog XXX.YYY.
To circumvent the problem, copy the catalog to a temporary
location and then recreate it. The problem with the header information
is corrected in the copying process. For example, assume a catalog
named MYLIB.CAT1 has become corrupted. To correct the problem, you could
use the following code.
proc catalog catalog=MYLIB.CAT1;
copy out=work.temp new;
run;
proc catalog catalog=work.temp;
copy out=MYLIB.CAT1 new;
run;
A Technical Support hot fix for Release 8.2 TSLEVEL TS2M0 for this
issue is available at:
http://www.sas.com/techsup/download/hotfix/82_sbcs_prod_list.html#004165
For customers running SAS with Asian Language Support (DBCS), this
hot fix should be downloaded from:
http://www.sas.com/techsup/download/hotfix/82_dbcs_prod_list.html#004165
Operating System and Release Information
| SAS System | Base SAS | Microsoft Windows 2000 Server | 8.1 TS1M0 | 9 TS M0 |
| Microsoft Windows NT Workstation | 8.1 TS1M0 | 9 TS M0 |
| Microsoft Windows 95/98 | 8.1 TS1M0 | |
| Microsoft Windows 2000 Datacenter Server | 8.1 TS1M0 | 9 TS M0 |
| Microsoft Windows 2000 Professional | 8.1 TS1M0 | 9 TS M0 |
| Microsoft Windows 2000 Advanced Server | 8.1 TS1M0 | 9 TS M0 |
| Solaris | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| OpenVMS VAX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| 64-bit Enabled Solaris | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| IRIX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| z/OS | 8.1 TS1M0 | 9 TS M0 |
| OS/2 | 8.1 TS1M0 | |
| ABI+ for Intel Architecture | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| Tru64 UNIX | 8.1 TS1M0 | 9 TS M0 |
| 64-bit Enabled AIX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| OpenVMS Alpha | 8.1 TS1M0 | 9 TS M0 |
| CMS | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| HP-UX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| 64-bit Enabled HP-UX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
| AIX | 8.1 TS1M0 | 9.1 TS1M3 SP4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Topic: | Data Management ==> Access ==> SAS I/O
|
| Date Modified: | 2002-11-26 10:46:30 |
| Date Created: | 2001-01-23 11:29:29 |