Hitachi Vantara Pentaho Community Forums
Results 1 to 3 of 3

Thread: DB2 Problem - SQL dialect

  1. #1
    Join Date
    Jan 2007

    Default DB2 Problem - SQL dialect

    After upgrading pentaho to version 1.6, erlier defined cubes stoped working.
    We found that the reason is inserting by mondrian unnecesery quotes - here is example:

    select "czas"."rok" as "c0" from "czas" as "czas" group by "czas"."rok" order by "czas"."rok" ASC

    DB2 returns errors about mising objects. After changing query (in isql) to:

    select czas.rok as c0 from czas as czas group by czas.rok order by czas.rok ASC

    results are returned.

    How can I fix this problem?


  2. #2
    Join Date
    Nov 1999


    I wish I had a dime every time this problem came up.

    DB2 is case sensitive. If you specify a table or column name without double-quotes, it is converted to upper case. This happens in both a CREATE TABLE statement and in SELECT statements.

    Your table, for example, is really called CZAS. In your mondrian schema, you told mondrian that it was called czas, so mondrian encloses it in quotes.

    The solution is either to use double-quotes when creating your schema (so your table will be called czas) or to specify the table and column names in upper-case in your mondrian schema file.


  3. #3
    Join Date
    Jan 2007

    Default It works

    Thank you, your sotlution works.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.