LMS 3.2 Syslog purge job failed.

Unanswered Question
Jun 18th, 2010

We installed LMS 3.2 on windows server 2003 enterprise edition. RME version is 4.3.1. We have created daily syslog purge job from RME> Admin> Syslog> Set Purge Policy. This job failes with the following error.

"Drop table failed:SQL Anywhere Error -210: User 'DBA' has the row in 'SYSLOG_20100516' locked 8405 42W18
[ Sat Jun 19  01:00:07 GMT+05:30 2010 ],ERROR,[main],Failed to purge syslogs"

After server restart job will again execute normally for few days.

Please check attached log file of specified job.

Regards

Attachment: 
I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Joe Clarke Sat, 06/19/2010 - 18:44

Instead of restarting the server, try restarting the SyslogAnalyzer daemon alone.  Does the purge job run successfully after that?

pdterm SyslogAnalyzer

pdexec SyslogCollector

Joe Clarke Thu, 07/22/2010 - 21:53

How many purge jobs exist?  You can find a list of them under Common Services > Server > Admin > Job Browser.

Joe Clarke Sat, 07/24/2010 - 09:31

The only reports of this problem in the past has been with two jobs being created during an upgrade.  This would not have been something you would have done yourself.  I suggest you open a TAC service request so database locking analysis can be done to find what process is keeping that table locked.

Actions

This Discussion