SAS Metadata Server journaling is enabled by default to store details about metadata transactions. After a successful backup, a new journal file is created with the time stamp in the file name. If this file is corrupted, the SAS Metadata Server fails to start and messages like the following might appear in the metadata server log:

If no other errors are found in the logs for the SAS Metadata Server, take the following actions to address this issue:

1. Stop all SAS processes.
2. Rename the SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal directory to SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal.old.
3. Create a new empty SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal directory with the same ownership and permissions as the original Journal directory.
4. Start SAS Metadata Server. If it is a clustered metadata server, start the master server with -startNoCluster option.
5. If the server fails to start, follow the instructions provided in the links below for recovering an unresponsive metadata server.
6. If the server successfully starts, check the log for any errors.
7. Run an adhoc backup of the metadata repository by following the instructions in Using SAS Management Console to Run an Ad Hoc Metadata Server Backup.
8. Analyze and repair metadata by following the instructions in Analyzing and Repairing Metadata.
9. Run an adhoc backup of the metadata repository with the reorg option selected.
10. If this is a clustered metadata server, stop the master metadata server and restart all metadata servers and SAS processes normally.
11. If this is a non-clustered environment, start all other SAS processes normally.

For more information about SAS Metadata Server journaling, see the following links:

• Configuring Metadata Server Journaling
• What to Do If the 9.4 SAS Metadata Server Is Unresponsive
• SAS Note 43649, "Recovering an Unresponsive 9.3 SAS^® Metadata Server"

Operating System and Release Information