Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

Tagged

Mailing list users (luciddb-users) can "claim" their threads in the archives by registering with the same account they used to post to the email list. NOTE: List threads are updated once every 24hrs.
Mondrian and Luciddb
  • bostoncheesy July 2012
    Hi there,

    I am connecting to luciddb through mondrian using the olap4j API. I am able to connect to the database. However, when Mondrian submits its generated SQL the Trace.log file reveals that the query fails because no default schema has been set. I have tried setting the default schema for a user and connecting as them, as well as changing the table names to full path (i.e. schema_name.table_name). Neither of these have worked. Any suggestions?

    Thanks.
  • nagoodmannagoodman July 2012
    Bostoncheesy,

    If you've added the schema/name and you're certain that the user can select from those tables (try connecting as your user via sqllineClient or Squirrel or Kettle) then I'm betting it's almost certainly the case.  Mondrian sends table/schema names properly quoted so it will be case sensitive.  You need to make sure that the schema/table/column names match exactly including case, the values in your mondrian.xml and DBA_SCHEMAS, DBA_TABLES, and DBA_COLUMNS.

    If that doesn't sort it out  (proper GRANTS to user and avail via sqllineClient, exact case matching in mondrian.xml and DBA_ views) then please post the relevant SQL statements, grants, DDL, and error logs for us to try and further help.
  • bostoncheesy July 2012
    Thanks for the reply. I have looked into the SQL queries and am encountering various errors there based on my xml file that holds my cube description. I can manually fix those errors myself. Most of them are the result of lowercase column names in the xml file or tables without a specified alias which result in mondrian trying to alias the table "schema_name.table_name" as "schema_name.table_name" which causes the parser to fail due to the period. The case sensitivity of luciddb can be a bit difficult to deal with when trying to use an xml file with both mysql and lucid simultaneously if the mysql db is not kept in all caps.

    Thanks for your help.
  • nagoodmannagoodman August 2012
    Well, if MySQL engineers would have at least glanced at the ANSI SQL standard (CAPS unquoted has been standard since beginning) then it wouldn't create these issues.  :)  Glad to see you got it sorted.
Add a Comment