Jetspeed 2
  1. Jetspeed 2
  2. JS2-658

COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0107N The name "FK_PA_METADATA_FIELD_1" is too long. The maximum length is "18". SQLSTATE=42622

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.1
    • Fix Version/s: 2.2.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      Database -- DB2. JDK 1.5_06. Maven 1.0.2

      Description

      When I try to generate and populate my DB2 Database for Jetspeed using Jetspeed-Maven Plugin I am getting the above exception. To fix this temporarly what I went along with was to identify the foreign keys with a name longer then 18 chars and make them shorter. This is a bit of manual step, but works fine with all the databases. So basically we need to get into the jetspeed plugin inside maven_repo (<maven installation dir>\maven_repo\cache\maven-jetspeed2-plugin-2.1-dev\plugin-resources\schema) and manually edit the schema xml's to overcome the above limitation.

      Now, what I would like to know here is, whether this is a known issue or there is something wrong with my configurations moreover is there a better fix for this issue. And if this is a known issue, which release of Jetspeed-maven Plugin will have a solution for the same.

      Any help on this regard will be greatly appreciated.

      Regards
      Mahesh

        Activity

        Hide
        Ate Douma added a comment -

        Wow, 18 characters max. for a foreign key name? That is absurd

        Well, we can look into reducing the length of all our foreign key names some time.

        Note: fixing a bug cannot be done against the same (release) version it was detected in, so I'm gonna bump the Fix Version up to 2.2-dev

        Show
        Ate Douma added a comment - Wow, 18 characters max. for a foreign key name? That is absurd Well, we can look into reducing the length of all our foreign key names some time. Note: fixing a bug cannot be done against the same (release) version it was detected in, so I'm gonna bump the Fix Version up to 2.2-dev
        Hide
        Ate Douma added a comment -

        I'll verify if the new Apache DB DdlUtils now used for version 2.2 already handles this as required.

        Show
        Ate Douma added a comment - I'll verify if the new Apache DB DdlUtils now used for version 2.2 already handles this as required.
        Hide
        Ate Douma added a comment -

        Vivek,

        Could you also please look into upgrading to and validating the latest DddlUtils release?

        We currently are still using a patched version which was specifically needed for Oracle. That might no longer be needed (so do test against Oracle at least).

        Show
        Ate Douma added a comment - Vivek, Could you also please look into upgrading to and validating the latest DddlUtils release? We currently are still using a patched version which was specifically needed for Oracle. That might no longer be needed (so do test against Oracle at least).
        Hide
        Vivek Kumar added a comment -

        Issue is fixed with latest new Apache DB DdlUtils

        Show
        Vivek Kumar added a comment - Issue is fixed with latest new Apache DB DdlUtils

          People

          • Assignee:
            Vivek Kumar
            Reporter:
            Mahesh Mohan
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development