I hope this will be helpful to you:

How to Recover Locked or Corrupt Profile Catalogs


Occasionally, a Sasuser.Profile catalog becomes locked or corrupted. SAS uses SASHELP.PROFILE and SASUSER.PROFBACK to replace the locked or corrupted catalog.

If your Sasuser.Profile catalog is locked, SAS will check for SASHELP.PROFILE. If SASHELP.PROFILE exists, SAS copies it to WORK.PROFILE and then saves the customizations in Work.Profile instead of in Sasuser.Profile. The following notes will appear in the SAS log:

  ERROR: Expecting page 1, got page -1 instead.
  ERROR: Page validation error while reading SASUSER.PROFILE.CATALOG.
  NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.
  NOTE: SASHELP.PROFILE has been copied to WORK.PROFILE.
  NOTE: All profile changes will be lost at the end of the session.
If your Sasuser.Profile catalog is corrupted, SAS copies the corrupted catalog to SASUSER.BADPRO. SAS then checks for SASUSER.PROFBACK. If SASUSER.PROFBACK exists, SAS copies it to Sasuser.Profile. Any changes made to the Sasuser.Profile catalog during the previous session will be lost. The following notes will appear in the SAS log:

ERROR: Expecting page 1, got page -1 instead.                                   
ERROR: Page validation error while reading SASUSER.PROFILE.CATALOG.            
NOTE: A corrupt SASUSER.PROFILE has been detected. A PROFILE catalog can        
      become corrupt when a SAS session is prematurely terminated.              
NOTE: SASUSER.PROFILE.CATALOG has been renamed to SASUSER.BADPRO.CATALOG.      
NOTE: SASUSER.PROFILE.CATALOG has been restored from SASUSER.PROFBAK.CATALOG.   
NOTE: Changes made to SASUSER.PROFILE.CATALOG during the previous SAS session   
      have been lost. The type of data stored in the PROFILE catalog is         
      typically related to SAS session customizations such as key               
      definitions, fonts for graphics, and window attributes.
If your Sasuser.Profile catalog is corrupted and there is no SASUSER.PROFBACK, SAS will check for SASHELP.PROFILE. If SASHELP.PROFILE exists, SAS copies it to WORK.PROFILE and then saves the customizations in Work.Profile instead of in Sasuser.Profile. The following notes will appear in the SAS log:

  ERROR: Expecting page 1, got page -1 instead.
  ERROR: Page validation error while reading SASUSER.PROFILE.CATALOG.
  NOTE: Unable to open SASUSER.PROFILE. WORK.PROFILE will be opened instead.
  NOTE: SASHELP.PROFILE has been copied to WORK.PROFILE.
  NOTE: All profile changes will be lost at the end of the session.