LDAP: Banner removed the 2,872 graduates and changed 10,809 others and with all the new approx indices, the 31,054 changes took an hour and ten minutes to process (ldapmodify)! Yikes.
Sun: called in the failed disk drive Case 65032845
Documented the meta* commands in the TSG Wiki for Solaris Volume Manager
LDAP: Update refused to create entry based on PeopleSoft claim of STU class -- found in student information system and combined new information with existing record.
Lab system -- more fibre channel zoning fun
LDAP: PeopleSoft's use of SSN 999999999 causes another broken account... I really need to fix this
ldap.uvm.edu -- deadlock and poor performance. Emergency upgrade to 2.3.23 and recreation of the substring index that was removed over the weekend and should not have been. -- 8 hours...
AD update -- duplicate group names... need to determine why the expired group was not reclaimed
LDAP update generated a two character userid this morning which was legal everywhere except on the mail servers. Update the code to prevent userids fewer than three characters to be created
Footprints Project 36 Issue 1964 -- retiree's and department names in peoplesoft
Examine and attempt to reproduce the ldap update problem from Saturday morning. The step that took almost an hour to run Saturday runs in eight minutes using the copy of the database that was backed up two hours before the run. Theories include memory shortage and large insertion of entries from the grey-listing function on the mail servers
Electrical room overheating. Condensor for the A/C unit is malfunctioning. Notified by building supervisor of the heat and looking at the graphs, it appears it broke at the same time as the power outage last Thursday evening. Institute cron job to monitor heat and email at 25 (degrees C) and page at 30.
Reboot test calendar server (hardware raid card screwed up last Friday late in the day). Unfortunately, a unidbfix was running ... open a SR with Oracle to see how to get the system to realize that unidbfix is NOT running so I can in fact run it...
In /tmp there lives a file named .mutex.CALSERV.35629.oracle.006.023 (or probably something similar) which needs to get removed for unidbfix to be able to run!
Send out third notice to accounts that will be removed in July.