We enable change tracking but it immediately stops after enabling. This did work for a long time but it stopped a month or two ago. I don't believe anything changed in the environment to cause this.
Looked at stderr_sc_rep and found information below:
Mon Jun 24 12:21:26 2013: ERROR: sc_rep_mngr:db_utils.cxx:36: <DATABASE ERROR> Code: 9002; Message: [Microsoft][ODBC SQL Server Driver][SQL Server]The transaction log for database 'Quest_Performance_Repository' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases; SQL Text: {CALL CM_MSSQL_DELETE_TIME_EXPIRED_RECORDS(? , ? )}; VAR Info: </DATABASE ERROR>
Mon Jun 24 12:21:26 2013: WARN: sc_rep_mngr:db_utils.cxx:104: Can't ignore from database error (9002) with sevirty 17
In SQL studio, go to your Quest Performance Repository get to properties of Log files and make sure log file expand set to unlimited.
Go back to agent administration to see Change Tracking should show 'Working'
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center