Technote Number: 1086228
Problem:
This issue was reported to Lotus Quality Engineering and has been addressed in
Domino release 5.0.5. In versions prior to 5.0.5 and post 5.0.2x to resolve
the crash add the TRANSLOG_Recreate_Logctrl=1 parameter to the notes.ini to
recreate the log control file, as follows:
Note: The following steps are an example and demonstrate how to carry this out
using a partition scenario:
-- Shutdown all three partitions.
-- Set the notes.ini variable TRANSLOG_Recreate_Logctrl=1 on all three
partitions.
-- Delete the control file (nlogctrl.lfh) in each of the logging directories,
but NOT the log extents (Sxxxxxxx.TXN).
-- Restart each partition. This will recreate the log file and all of the log
extents. This may take a little time.
-- After the server is up, the notes.ini TRANSLOG_Recreate_Logctrl variable
that was previously added will be changed to a value of 0 (so that the logs are
not created each time). This variable should be deleted as a precaution.
Please remember that this INI variable only needs to be set on the creation of
the logs. Additionally, when using this setting, you must have the old logs in
the directory (or the server will PANIC) and you must delete the control file.
After the logs are re-initialized the ini setting will change to 0, as
described above.
Supporting Information:
There was an issue prior to release 5.0.5 on AIX where the control file could
be created incorrectly. There appeared to be a bug in the AIX compiler that
when one of the transaction log files was compiled in optimized mode for
production versions (the one that creates the log control file), it would not
increment a counter to populate which log extents to use. This made the log
control file think it always should use extent 0, resulting in circular log
setups only using this extent and continuing to overwrite it or, in archive
setups, causing this type of crash.
The fix was to build this file non-optimized on AIX. The way to tell if you
are experiencing this issue, supply the nlogctrl.lfh file to Lotus Support so
that Development can run the dumplfh utility on it to see if all of the extents
are 0. More >
|  |
|
|
|
|
|