Usage Note 43100: Possible reasons for a corrupted SASUSER profile catalog in UNIX environments
The following errors indicate a corrupted SASUSER profile catalog.
ERROR: Expecting page x, got page -1 instead.
ERROR: Page validation error while reading xxxx.xxxx.xxxx
To solve the problem, first test to confirm that a corrupted
profile catalog is in fact the problem. You can use the -SASUSER option
to cause a new profile catalog to be created in the /tmp directory:
sas -sasuser /tmp &
If the errors no longer occur, then rename the old profile catalog
in your home directory:
cd $HOME/sasuser.v94
mv profile.sas7bcat old_profile.sas7bcat
mv profbak.sas7bcat old_profbak.sas7bcat
When you invoke a new SAS session, a new profile catalog will be created.
Profile catalogs become corrupted for various reasons, including:
- Using the X button in a SAS window to close
a SAS session, rather than using the pulldown menu.
- Using the X button to close your X emulator window
while a SAS session is active.
- A recurring problem
with corrupted profile catalogs could indicate a problem with
the file system.
Operating System and Release Information
SAS System | Base SAS | 64-bit Enabled AIX | 9.2 TS2M0 | |
64-bit Enabled HP-UX | 9.2 TS2M0 | |
64-bit Enabled Solaris | 9.2 TS2M0 | |
HP-UX IPF | 9.2 TS2M0 | |
Linux | 9.2 TS2M0 | |
Linux for x64 | 9.2 TS2M0 | |
Solaris for x64 | 9.2 TS2M0 | |
*
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.
Date Modified: | 2011-05-04 14:34:10 |
Date Created: | 2011-04-28 12:45:54 |