Topic
  • 2 replies
  • Latest Post - ‏2013-03-15T09:17:37Z by SystemAdmin
SystemAdmin
SystemAdmin
197 Posts

Pinned topic Crawler error

‏2013-03-12T11:39:46Z |
Lately I see my crawler stops nearly everyday with the following error:

FFQD4927E A database error occurred when accessing the internal repository. Table Name: URL. SQLCODE: 40000. SQLSTATE: 08003.
FFQD4927E A database error occurred when accessing the internal repository. Table Name: URL. SQLCODE: 40000. SQLSTATE: 08003.
FFQD4927E A database error occurred when accessing the internal repository. Table Name: URL. SQLCODE: 40000. SQLSTATE: 08000.
FFQD4869E A database exception occurred while writing to the database. Bucket(http://+website1+:80,3672364330256241598) is the crawler operation that was in progress. save is what was being written.
FFQD4869E A database exception occurred while writing to the database. Bucket(http://+website2+:80,-2409034866377773623) is the crawler operation that was in progress. save is what was being written.
FFQD4869E A database exception occurred while writing to the database. Bucket(http://+website3+:80,-2351455566579934049) is the crawler operation that was in progress. save is what was being written.

I have no clue what this means, and I don't find the help helpfull. Can someone enlighten me?
Updated on 2013-03-15T09:17:37Z at 2013-03-15T09:17:37Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    197 Posts

    Re: Crawler error

    ‏2013-03-14T07:02:19Z  
    Could you try this solution?
    http://www.ibm.com/support/docview.wss?uid=swg21569632
  • SystemAdmin
    SystemAdmin
    197 Posts

    Re: Crawler error

    ‏2013-03-15T09:17:37Z  
    I think it's unlikely that the issue discussed at the link is applicable to my situation. First of all, the crawler is running when the error occurs, I have no trouble starting it. In fact, that is the action I use to resolve this troublesome state, I stop and start the crawler in the administration console. Furthermore I cannot find an java.sql.SQLException in the logs on the date/time of the occurance.
    The SQLState suggests there is a connection problem, which I totally do not understand. I would think that's something that Jetty manages.