Troubleshooting
Problem
This technote explains how the IBM® Rational® ClearCase® Scheduler database can be replaced if it has become corrupt without fear of losing the default jobs that have been customized over time on Microsoft® Windows®, Linux® and UNIX®.
Symptom
A possible symptom of a corrupt scheduler database comes in the form of the albd_server process crashing with a memory dump every time the Scheduler runs.
If the ClearCase scheduler database becomes corrupt, the ALBD process will:
- Consider jobs that have terminated to still be running, and/or
- Think the next scheduled run time for a job is years in the future or
When this happens, the most common warning message reported in the ALBD log is:
"Albd(1064): Warning: Job ... is still running -- skipping scheduled execution."
Another indication of a corrupt scheduler database on Windows is that the albd process may crash. In the Windows event viewer you would see errors such as the following when trying to edit or change a scheduled job:
C:\Program Files\Rational\ClearCase\bin\albd_server.exe (pid: 1732, tid: 1744) nt_gendump("C:\Program Files\Rational\ClearCase\var\log\albd_server.1732.dmp"): Unhandled exception was caught!
This problem can also be seen as a Permission Denied error when root attempts to edit the ACL on UNIX or Linux:
$ /usr/atria/bin/cleartool schedule -edit -acl
cleartool: Error: Unable to edit scheduler ACL: Permission denied.
Doe, John [1:49 PM]:
$ id
uid=0(root) gid=3(sys)
groups=0(root),1(other),2(bin),4(adm),5(daemon),6(mail),7(lp),20(users)
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
29 September 2018
UID
swg21251457