Usage Note 61824: SAS® Metadata Server fails to start with "An error occurred while attempting to Initialize the Journal File..." when the journal file is corrupted
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:
INFO [00000007] :sas - Initializing journal file: Journal/2018-02-07T00_59_59-05_00_Journal.dat.
ERROR [00000007] :sas - End of file
ERROR [00000007] :sas - An error occurred while attempting to Initialize the Journal File Journal/2018-02-07T00_59_59-05_00_Journal.dat.
If no other errors are found in the logs for the SAS Metadata Server, take the following actions to address this issue:
- Stop all SAS processes.
- Rename the SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal directory to SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal.old.
- Create a new empty SAS-configuration-directory/Lev1/SASMeta/MetadataServer/Journal directory with the same ownership and permissions as the original Journal directory.
- Start SAS Metadata Server. If it is a clustered metadata server, start the master server with -startNoCluster option.
- If the server fails to start, follow the instructions provided in the links below for recovering an unresponsive metadata server.
- If the server successfully starts, check the log for any errors.
- 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.
- Analyze and repair metadata by following the instructions in Analyzing and Repairing Metadata.
- Run an adhoc backup of the metadata repository with the reorg option selected.
- If this is a clustered metadata server, stop the master metadata server and restart all metadata servers and SAS processes normally.
- 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:
Operating System and Release Information
| SAS System | SAS Metadata Server | Microsoft Windows Server 2003 Datacenter Edition | 9.3 | | 9.3 TS1M0 | |
| z/OS | 9.3 | | 9.3 TS1M0 | |
| Microsoft® Windows® for x64 | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2003 Enterprise Edition | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2003 Standard Edition | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2003 for x64 | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2008 | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2008 R2 | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows Server 2008 for x64 | 9.3 | | 9.3 TS1M0 | |
| Microsoft Windows XP Professional | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Enterprise 32 bit | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Enterprise x64 | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Home Premium 32 bit | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Home Premium x64 | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Professional 32 bit | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Professional x64 | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Ultimate 32 bit | 9.3 | | 9.3 TS1M0 | |
| Windows 7 Ultimate x64 | 9.3 | | 9.3 TS1M0 | |
| Windows Vista | 9.3 | | 9.3 TS1M0 | |
| Windows Vista for x64 | 9.3 | | 9.3 TS1M0 | |
| 64-bit Enabled AIX | 9.3 | | 9.3 TS1M0 | |
| 64-bit Enabled HP-UX | 9.3 | | 9.3 TS1M0 | |
| 64-bit Enabled Solaris | 9.3 | | 9.3 TS1M0 | |
| HP-UX IPF | 9.3 | | 9.3 TS1M0 | |
| Linux | 9.3 | | 9.3 TS1M0 | |
| Linux for x64 | 9.3 | | 9.3 TS1M0 | |
| Solaris for x64 | 9.3 | | 9.3 TS1M0 | |
*
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: | 2020-01-10 14:04:47 |
| Date Created: | 2018-02-09 09:01:26 |