- Is SELFTUNEBUFPOOLSIZE YES in use in the dsmserv.opt?
tsm:> query opt - What is the default configured BUFPOOLSIZE?
tsm:> query opt - What is the the current BUFPOOLSIZE and is SELFTUNE enabled?
tsm:> query db f=d
Multiply the buffer pool pages by 4096 and then divide by 1024.
Showing posts with label ANR. Show all posts
Showing posts with label ANR. Show all posts
Sunday, January 7, 2007
ANR0380W The database buffer pool recovered from an overcommit of 867 pages. Consider increasing your buffer pool size by 3468 kilobytes
This error occurs when the BUFPOOL is incorrectly sized or SELFTUNE is enabled and the server has been recently restarted - Check the following:
Thursday, October 5, 2006
ANR9999D Error Restoring From Backupsets
We have a site that uses backupsets for extended retention (which I hate, but that's beside the point). I had a number of restores (and "QUERY BACKUPSETCONTENTS" commands) that were failing with the error "Command failed – internal server error detected." Further research into the problem revealed only that 9999D means "thread terminated", with no other specific information.
After a call to Tivoli support, and some exchanging of some logs, it was determined that tape containing the backupset was not in the library. When the "request" timer would expire, the server would terminate the thread, but no "message" would return. This includes running commands from the server and client command line interfaces. You can replicate the error by running the command in one window, then canceling the request on the server in another. The Tivoli rep said that he would send it to the developers, so this may be "fixed" to include a proper error message in a future version.
After a call to Tivoli support, and some exchanging of some logs, it was determined that tape containing the backupset was not in the library. When the "request" timer would expire, the server would terminate the thread, but no "message" would return. This includes running commands from the server and client command line interfaces. You can replicate the error by running the command in one window, then canceling the request on the server in another. The Tivoli rep said that he would send it to the developers, so this may be "fixed" to include a proper error message in a future version.
Subscribe to:
Posts (Atom)