Gary, It might be useful to turn on server side tracing before the db backup begins and turn it off after it finishes. That way you would have a trace file to look at the next time it fails. The following link deals with a db backup issue which does not seem to fit your case because yours is intermittent but it does document the trace flags to use.
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0ahUKEwiq_abOlr7NAhUI94MKHabgA-cQFggmMAE&url=http%3A%2F%2Fwww.ibm.com%2Fsupport%2Fdocview.wss%3Fuid%3Dswg21691186&usg=AFQjCNEYMYQEtoOZ2eqhOssoqnrOWOiDww David -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary Sent: Thursday, June 23, 2016 8:39 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] trouble with db backups inside scripts Tsm server 6.3.4 under redhat 6.7. About every third time our daily maintenance script runs, the db backup fails with the message Anr4588e a database configuration might be incorrect. However, as soon as I see this anywhere from a couple of minutes to an hour or so later, I can run the same exact backup by hand and it works fine; only giving the expected anr4976 message. Anyone out there have a clue? I'm stumped.