On Tue, 2005-05-03 at 18:55 -0400, Tom Shaw wrote:
 At 6:09 PM -0400 5/3/05, D. Richard Hipp wrote:
 >On Tue, 2005-05-03 at 17:45 -0400, Tom Shaw wrote:
 >>  Hi.
 >>
 >>  I was using SQLite with PHP 5 (MacOSX) and due to some issues the php
 >>  page timedout before completing the DB update. Now I can't read the
 >>  DB via php nor via the sqlite command line tool. I keep getting DB
 >>  busy/DB locked.  How do I repair the DB and remove the "lock"and
 >>  either 1) try to recover the data in the DB or 2) verify the data is
 >>  OK and begin to reuse.
 >>
 >
 >SQLite is suppose to automatically repair itself.  If you
 >are getting "locks" that stick around, it must mean that PHP
 >is somehow holding the database open (and locked) after it
 >times out.  Try shutting down and restarting your webserver
 >and see if that doesn't clear the problem.

 Richard,

 I restarted Apache - No luck :-)  Any other ideas?


Do a "ps uax" and look for processes that seem to be PHP related. Then "kill -9" them.

Richard,

None running.

Tom
--

Tom Shaw - Chief Engineer, OITC
<[EMAIL PROTECTED]>, http://www.oitc.com/
US Phone Numbers: 321-984-3714, 321-729-6258(fax), 321-258-2475(cell/voice mail,pager)
Text Paging: http://www.oitc.com/Pager/sendmessage.html
http://www.oitc.com/Antarctica/


PGP Public Keys available at:
<A HREF="ldap://keyserver.pgp.com/";>PGP's Key Server</A>
<A HREF="http://www.oitc.com/OITC/PGPKeys.html";>OITC's Public Key List</A>
14A7 A308 266A 3646 FBA8  9A86 E139 F108 B1BE 37BD

Reply via email to