Question

I’m trying to use the openedge jdbc connector to pull data from an existing progress db but im running into column width issues.

Here is the error that is holding me up.

[DataDirect][OpenEdge JDBC Driver][OpenEdge] Column TabDisplayName in table PUB.Menu has value exceeding its max length or precision.

I’ve looked at many posts, each offering different advice, and here’s what I’ve given a go this far:

1. Manually modify the SQL width via the data dictionary.
   • I ran a quick check on PUB.Menu.TabDisplayName to find a max value of 44 Characters
   • Set the width to x(50) to no avail and then x(100) out of a fix of irrational rage, again with no luck.
2. Use the SUBSTR() SQL Function to truncate the field -not optimum but better than nothing
   • I get weird results with this. It works fine in sqlexp but in a java environment its like the column is never selected.
3. Use the dbtool to automatically fix width problems with option #2
   • After selecting all tables and “areas” (not sure what those are…) and submitting the final option I am returned to the proenv cmdline as if nothing ever happened.
4. Modify the sql width programmatically via 4gl
   • This is the only option I found that I have yet to try.
   • I am a little reluctant to try this only because a manual modification failed. Also this is a live development environment(for me only) and Im trying to mess it up too terribly, although i am taking snaps regularly.

Running progress 10.2B on a unix machine.

Any comments and suggestions would be appreciated.

-Thanks

Answer 1

The dbtool option is the best. It is designed for this. From proenv you should see something like this:

proenv> dbtool s2k

       DATABASE TOOLS MENU - 10.2B
       ---------------------------

  1. SQL Width & Date Scan w/Report Option
  2. SQL Width Scan w/Fix Option
  3. Record Validation
  4. Record Version Validation
  5. Read or Validate Database Block(s)
  6. Record Fixup
  7. Schema Validation
  9. Enable/Disable File Logging
          Q. Quit

  Choice: 2

: (0=single-user 1=self-service >1=#threads)? 1

Padding % above current max: 100

: (Table number or all)? all

: (Area number or all)? all

: (verbose level 0-3)? 0

Total records read: 31357

SQLWidth errors found: 0, Date errors found: 0

SQLWidth errors fixed: 0

If your db has a server up & running choose “1” at the connect: prompt. If not, choose “0”.

Pick 100 for padding to double the width of fields.

Try it on a copy of the “sports” database if you are unsure. Use a higher level of verboseness if you want some insight into what it is doing.

It does not take very long to run on a small development database. (It is basically instantaneous on “sports”.)