Direct links to fixes
APAR status
Closed as program error.
Error description
Library server monitor returned error "GetDatabaseLock Did not get database lock". The error message logged in library server log is as below: "... GetDatabaseLock Did not get database lock ..."
Local fix
Restart library server monitor.
Problem summary
**************************************************************** * USERS AFFECTED: * * 999 * **************************************************************** * PROBLEM DESCRIPTION: * * When activating a quiesced Content Manager system, the * * library server monitor does not release the database lock * * flag as it should. This prevents the library server monitor * * from correctly monitoring the status of associated resource * * managers. * **************************************************************** * RECOMMENDATION: * * No * ****************************************************************
Problem conclusion
Fixed in IBM Content Manager 8.5 fix pack 4
Temporary fix
Restarting Library Server Monitor
Comments
APAR Information
APAR number
IO23252
Reported component name
SYSTEM ADMIN CL
Reported component ID
5724B1900
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-05-18
Closed date
2016-01-20
Last modified date
2016-01-20
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
999
Fix information
Fixed component name
SYSTEM ADMIN CL
Fixed component ID
5724B1900
Applicable component levels
R850 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSRS7Z","label":"Content Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]
Document Information
Modified date:
24 September 2021