Hello, I had exactly the same problem since upgrading to 6.1.2.1. Today, I upgraded to 6.1.3.0 but it the problem still persisted. Following Jörg's hints I also "reactivated" report creation successfully. Thanks to Jörg for sharing your expirience!
That's definitly an annoying bug in TSM... kind regards an happy holidays, Stephan 2009/9/6 J. Pohlmann <jpohlm...@shaw.ca> > Just an FYI - in a couple of situations including one I came across last > week, a select * from events resulted in an "ANR0102E admsql.c error 1 > inserting in table EVENTS.SQL" message that caused the admin session to > hang > on this and any subsequent select (whatever) from events. The admin session > will eventually time out. Many reporting environments (including ITM - TSM > Reporting in 6.1) rely on select (something) from events and will hang if > this problem is encountered. It appears that the error is caused by a TSM > administrator having removed nodes. We ended up setting eventretention to 0 > days and re-registering the nodes, and then removing them again, then > rebooting the server and had our problem cleared so that we were able to > select (something) from events and had our reporting operational again. I > do > not know if this is a real work-around of this problem or if we were just > lucky and TSM 6.1.2.0 healed itself. You might want to be careful about > removing nodes, especially those that were recently active. > > > > Joerg Pohlmann > > 250-245-9863 >
