Roland Gruber <[email protected]> le vendredi 12 septembre 2014 à 18:00 +0200 a écrit: >in this case there are only a few possibilities: > >* account locked by PPolicy if you use this (can be checked with LAM's >PPolicy user module) e.g. because of too many failed login attempts >* some other server side overlay >* master-slave replication problem >* database corruption Hi Roland, I solved this problem by increasing the cache size and adjusting the settings locks, lockers, and lock objects, all in DB_CONFIG. For all practical purposes. Best regards Pascal
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
