Ludbfix was unable to repair broken links - Resource governor for 'prepared statements' exceeded in ludbfix.log,

TECH182350
Last Updated July 31, 2012
Copy Article Title/URL
Feedback
Subscribe

Customer wanted to remove Failed to clean up LiveUpdate downloaded content errors from DB with ludbfix tool.

After running ludbfix errors were not repaired. 

In ludbfix.log there was an errror Resource governor for 'prepared statements' exceeded.

ludbfix.log
******************************************
java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Resource governor for 'prepared statements' exceeded
 at ianywhere.ml.jdbcodbc.jdbc3.IConnection.nativePrepareStatement(Native Method)
 at ianywhere.ml.jdbcodbc.jdbc3.IConnection.prepareStatement(IConnection.java:552)
 at com.sygate.scm.tools.ludbfix.Main.updateBinaryFileDeleteFlag(Main.java:188)
 at com.sygate.scm.tools.ludbfix.Main.doLuDbFix(Main.java:114)
 at com.sygate.scm.tools.ludbfix.Main.main(Main.java:267)
*****************************************

Resource governors in Sybase DB need to be disabled during repair process.

To make ludbfix tool working you need to change max_cursor_count and max_statement_count values in DB.

1. Go to ISQL (%ProgramFiles%\Symantec\Symantec Endpoint Protection Manager\ASA\win32\dbisqlc.exe)
2. Run 

  • Set option public.max_cursor_count = 0;
  • Set option public.max_statement_count = 0;

3. Run ludbfix tool.

4. Go to ISQL  and run

  • Set option public.max_cursor_count = 50;
  • Set option public.max_statement_count = 50;

After this procedure you should not have Failed to clean up LiveUpdate downloaded content errors in SEPM  console.


Imported Document ID: TECH182350

Thanks for your feedback. Let us know if you have additional comments below. (requires login)

    © 1995-2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.