Uploaded image for project: 'SET - Setups'
  1. SET - Setups
  2. SET-59

The database field SCHEDULER_INSTANCES.DB_NAME is too short for some JDBC connection strings

    XMLWordPrintable

Details

    • Feature
    • Status: Released (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • 1.9.10, 1.10.4, 1.11
    • None

    Description

      Current Situation

      The createDailySchedules job writes the JDBC connection string into the database field SCHEDULER_INSTANCES.DB_NAME which is a varchar(250).
      JDBC urls in Oracle particularly could be longer so that the job raises the error

      ORA-12899: value too large for column "SCHEDULER_INSTANCES"."DB_NAME" (actual: xxx, maximum: 250)

      Maintainer Notes

      The field will be created as varchar(1000) in the setup.

      Attachments

        Issue Links

          is related to

          Fix - JID-112 The job CreateDaysSchedule should not insert the dbname value in the table SCHEDULER_INSTANCES

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Released
          links to

          Web Link SourceForge forum: JDBC connection strings field in database is not long enough

          Activity

            People

              oh Oliver Haufe
              oh Oliver Haufe
              Santiago Aucejo Petzoldt Santiago Aucejo Petzoldt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 hours
                  2h
                  Remaining:
                  Remaining Estimate - 2 hours
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified