#167 Never finishes

Paul Flores

Pointed at a DB2 data base through the SchemaSpy GUI but it never appears to complete the diagram creation portion. There are over 700 tables in the data base. There are a handful of table diagrams in the output and I let it run for over 10 hours. Is there any way of determining where it is hanging up?


  • Jim Garrison

    Jim Garrison - 2013-05-14

    I see this same behavior. However when looking at the Java process with Sysinternals Process Monitor I see it issuing TCP/IP network calls periodically. Examining the traffic with Wireshark I see that it's doing select count(*) from each table. On Postgres at least, this involves a full table scan (I was surprised but my DBA said it's what pgsql will do). If you have 700 large tables and DB2 does the same thing you may be running up against the same problem.

  • Michael Reese

    Michael Reese - 2013-06-05

    I think I see a similar behavior in mySQL. My problem seems to be table row names that match up with a key value in another table. But only some cause the problem. I will attach the SQL for the error producing structure and also the structure modified (which completes). It seems that the graph production will perhaps soetime just drop into an infinite loop.

  • Michael Reese

    Michael Reese - 2013-06-05

    here is the modified (very slightly) structure that does NOT hang. It was as simple as changing the name of a field from address_id to address_id_modified

  • Martin Walke

    Martin Walke - 2013-09-30

    I have the same problem. Just downloaded the latest version and it hangs when writing diagramming info (This is my first time using the software). How can I determine what field is causing this?

    I'm on Windows XP SP3, Oracle 10 (thin client). There are over 300 tables each with at least 5 columns - some with considerably more. Are there restrictions that apply to the size of the db?

  • Jason Davenport

    Jason Davenport - 2014-01-08

    Hi guys,

    This is the first time I have used SchemaSpy too. I got it to work on a small DB - 5 tables but when I moved to a larger DB it would hang (when diagramming the dots just stop). So what I did - started stripping out the script from the generated .DOT file (its easy to work out) and noticed that it was hanging on those tables that had more than 25 columns.

    So then what I then did was I changed the parameters calling schemaspy to exclude those tables with columns > 25 and it worked.

    My question to John (Currier) is there some limitation of the number of columns we can have in a table (i.e. 25) or is it something with my DB/drivers. I am going to play about a bit more with the DOT file today to see if I can figure out what the problem is....

    BTW - I am using SQLServer 2008R2 and the JTDS 1.3.1 driver




Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks