Derby
  1. Derby
  2. DERBY-5391

The syscs_diag.error_log_reader() and syscs_diag.statement_duration() vtis do not work on derby error logs created since 10.7.1

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1, 10.8.1.2, 10.9.1.0
    • Fix Version/s: 10.7.1.4, 10.8.2.2, 10.9.1.0
    • Component/s: SQL
    • Labels:
      None
    • Urgency:
      Normal
    • Issue & fix info:
      Patch Available, Repro attached
    • Bug behavior facts:
      Regression

      Description

      The format of timestamps in Derby logs seems to have changed. As a result, the ErrorLogReader vti can't parse the text of derby.log. That vti is looking for the literal string "GMT" in order to locate timestamps.

      To reproduce the problem, run ij with -Dderby.language.logStatementText=true and issue the following query:

      select * from table (syscs_diag.error_log_reader( )) as t1;

      You will get an empty result.

      This regression was not caught by our tests because SysDiagVTIMappingTest uses a hardcoded derby.log created by version "10.3.0.0 alpha".

      The same problem seems to have broken the statement duration vti too. The following query returns an empty result from 10.7 onward:

      select * from table (syscs_diag.statement_duration()) as t1;

        Issue Links

          Activity

            People

            • Assignee:
              Rick Hillegas
              Reporter:
              Rick Hillegas
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development