comment on

Sounds like a db lock to me. Are you sure there are no new processes that have been introduced into your workflow recently that could be causing contention?

You should log the database activity using Enterprise Manager and pore (paw?) through the results looking for inserts and/or updates that could be occurring at the same time.

If you can't find out yourself what changed (because remember, your program didn't change, its environment did), then ask around in your workplace. It just might be that you run into someone who says that they moved a job back from 8am to 7am because they need to run some reports afterwards that have to be ready at 7:30.

Good luck.

• another intruder with the mooring in the heart of the Perl

In reply to Re: Fetching Madness by grinder
in thread Fetching Madness by jlongino

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Problems? Is your data what you think it is?
	PerlMonks