I created a sample database in hive and some sample tables in it.when I am connecting to Hive from my BI tool 'Tableau'I am unable to view the databases that are created.Only the defualt database is shown.
Could anyone help me with the issue so that I can access the newly created database in Tableau.
Thank You,
Divya Teja Y.
First: Make sure that you are calling your hive server connection from the same directory (or referencing the same metastore) as the one in which you created the database/tables.
Second: When you open up the Cloudera Hadoop Connection, you should be able to see your database under "Step 4: Select a schema on the server" Click the magnifying glass.
Related
I created an schema in Schema Workbench and publish with no errors, but when I got in BI Server with the standard user admin, I choose New->jpivot, then it display the name of the schema I created but it does not display the cube. For reference the error I get from catalina.out is:
17:11:45,174 ERROR [PentahoDataSourceResolver] PentahoXmlaServlet.ERROR_0002 - IDatasourceService.UNABLE_TO_INSTANTIATE_OBJECT
org.pentaho.platform.api.data.DBDatasourceServiceException: javax.naming.NameNotFoundException: Name [Esquema Salario] is not bound in this Context. Unable to find [Esquema Salario].
Name [Esquema Salario] is not bound in this Context errors usually appear if you use JNDI name, which is not defined on your system. So, I assumed, that this is the name of the datasource, which you reference while publishing Mondrian schema files to BI server.
Xml file with Mondrian schema definition generated by Schema Workbench does not contain any information regarding how to connect to database. So, you need to specify these details when you upload your schema file on BI server (It's done on step 4 below).
But first you have to create the connection itself (steps 1-2):
Create new JDBC datasource:
Define connection parameters:
If cubes still don't appear after these steps, you may republish your cube: follow same steps as in step 1, but select "Analysis" instead of "JDBC" in the end.
Upload the xml file, generated by schema workbench and select the datasource, which you have created on step 2. .
If cube still does not appear - check your log again. If you see the same Name is not bound error, you may try to restart your BI server application (new connections usually get recongnized immediately, but if you had a connection with same name before, than you might need to restart tomcat).
If that does not work, than once again, check log files. I guess, you'll have some different error in this case.
I had the same problem as the OP (blank screen when clicking New View) with the latest version of Pentaho BI server 7.1 (latest at the moment) and even with the 6.0 version one, Pivot4J SNAPSHOT 1.0 plug in version (latest as of today), Schema Workbech 3.14 (latest as of today).
And as, in line with OP, my catalina.out log was also spitting the Name [DatasourceName] is not bound in this Context. Unable to find [DatasourceName].
After several trials and errors I noticed the problem showed up when I checked the "Register the XMLA Data Source" when publishing the schema on Schema Workbench. So to fix the problem I just unchecked it before publishing.
Another way to fix this is going to the Manage Datasources option on the BI server, Import Analysis, choosing the schema created by Schema Workbench, AND manually setting the data source parameter value EnableXmla to false and saving changes. Now the schema should show up when clicking on Create New > Pivot4J view.
I have a database I connect to using the IntelliJ Built in tool, and it connects properly to the test database and displays it, however, it doesn't display the tables with another database. I then tried connecting with the open source tool SQL Workbench, with the same information and it does properly connect to the database and displays the tables.
test database:
other database:
other database in SQL Workbench:
When I click "Test Connection" In IntelliJ it connects properly for both the test and the other database, however one isn't actually displaying the tables.
How can I fix this?
Figured out what was wrong:
In the Database configuration file if you go to "Schemas & Tables" you can tick and untick what to show.
While I had never unticked anything, ticking the proper schema and adding it allowed me to visualize my database properly.
I have a question, in pentaho 5.1, how can I deploy a cube without using the schema workbench? I'm kind of newbie in Pentaho.
Is there a cmd line? Java code? Or something like...
Thanks a lot!
You can do that in the User Console.
There is a menu Manage Data source... There you can upload your xml and refer to a database connection for it.
First, I suppose you have installed BA Server and have made at least fact table.
In case you don't know what the fact table is, or someone else is reading this answer, you can find brief explanation here.
Of course, it's better to have full Star Schema. You cannot create Snow Flake inside Pentaho User Console. You can create it with Pentaho Schema Workbench or by manually edit mondarian.xml.
Make sure that your JDBC driver is inside BA Server driver directory. Look! Open Pentaho User Console. It's by default at localhost:8080/pentaho or yourdomain.name:8080/pentaho and login as administrator
File -> New -> Data Source
Choose Data source
Type Choose fact table and define connections to dimensions (if exists)
Choose to modify cube on the end of data source wizard
.
I'm trying to create a Penaho Dashboard using CDE and I have problems accessing my Data.
I have found tutorials but they always use SampleData or Steel Wheels. I have managed to do that myself, but I need to access my own database.
I was able to connect with my oracle database from the Data Source manager and created my own Data Source. But now I don't know how to access those tables from CDE. If I chose "sql datasource" I see the SampleData datasource and can do queries on it, but not the one I created with my database.
So, once I create a connection with my orcale database, how do I access my tables from CDE?
Thanks
There are two options:
SQL over JDBC: you define the db host, port, name, username and password;
SQL over JNDI: it'll use a registered JNDI from the Pentaho platform.
The JNDI field is an auto-complete field and fills in the various available options. However, if your newly created connection doesn't show up there, don't worry. Just type it in, it'll work.
you have to setup your data-source..
Click on datasources-panel on right corner
Click on sql Queries from the list you have seen on left side.
then click on sql over sqljndi
now here in properties in jndi set your database connection you want to access.
you can-not see the out-put of particular query in CDE for that open the same file in CDA for checking particular query's result(which you can find under files section).
I'm using Oracle SQL Developer 3.0.04. Trying to connect to a remote DB. Don't have any issues with database connection, it connects.
But when trying to view a selected tables rows a small progress bar within a small dialog box titled "Display Results" appears saying "Waiting for Checking if Object is Editable" and the progress is stuck. Cannot see any data of the selected table.
I tried to export the schema and data, but it freezed at once. So I closed SQL Developer.
Tried to attempt that again but now cannot even view the tables details.
Used TOAD in another machine and connected using that, no issue then the table listed all the data. Checked on the remote machine using putty and "sqlplus" to connect and the data showed as expected.
So that tells me that something in my local machine is wrong. Cannot connect using SQL Developer. Has anyone out there faced similar issue? please any idea on this matter?
Thanks
Did you try connecting to any other database, remote and local ? Does this happen with every database or only one connection? Perhaps something is wrong with that installation folder of SQL Developer, perhaps something got corrupt while it was stuck. Perhaps try to download the latest version of SQL Developer from this link and try again.