ODI 11g Standard Sequence not Incrementing [Solved]

Issue: ODI 11g Interface with ODI sequence to generate surrogate key does not increment correctly. As seen in the screenshot below.

ODI Standard Sequence

The issue is that when you try to use the Standard Sequence it only populates one number in the column as shown below,

ODI Sequence increment issue - Illustrated.

Cause: The cause of the issue was that the agent was not processing target row by row.

Resolution:

The resolution is to follow a set of guidelines as follows,

• Select an IKM which supports row by row processing using the ODI agent. We used the IKM SQL to SQL Control Append.

Change to an IKM that supports row processing by Agent.

• Set Flow Control attribute to False in the IKM.
• Make sure the column populated with Sequence is NOT checked for NOT NULL condition. 

This worked well for us. Try out and let us know. 

Note: The best and optimal way is to use a native database sequence. Even ODI documentation recommends the same. 

[BIP 11g] Restarting/Stopping BI Publisher 11g Services

Here is how to restart BI Publisher 11g Services from Console. 

Go to console, if you are inside the server just open localhost:7001/console or just open hostname:7001/console. Once inside the console from the domain structure panel on the left side select 'Deployments' as seen below.

Go to bifoundation_domain > Deployments

 Next select BI Publisher from the list of services listed 

 

Next go the tab on the top with 'Start' and 'Stop' buttons and Click on Stop > Force Stop Now

Confirm the action

Check the BI Publisher URL to confirm that  BI Publisher is down. 

Once confirmed, Select 'bipublisher' and select Start > Servicing all requests .

 

Now check the BI Publisher URL again,

[Solved] Impala ODBC SASL Authentication Error

Attempting connection
Failed to establish connection
SQLSTATE: HY000[Cloudera][ThriftExtension] (3) Error occurred while contacting server: ETIMEDOUT. The connection has been configured to use a SASL mechanism for authentication. Please check to see whether the server has been configured to use SASL for authentication

We came across this ODBC connectivity error while trying to connect to an Impala Data Source.

Cause: This cause of this error is that SASL Authentication has not been configured in the Impala Server. 

Resolution: This can be resolved easily by clicking Ok on the error and at the connection Information window uncheck the 'Use Simple Authentication and Security Layer(SASL)' option. 

Now Retest the connection and it will be working fine, provided you have given the correct credentials and connection details to Impala Server.

Import Cloudera Impala Tables to OBIEE Repository [Solved]

Recently we had an opportunity to work on a demo where the OBIEE data source was Cloudera Impala. So had to create a new ODBC source to import Impala tables to OBIEE repository. So here are the steps.

First you need to install the ODBC Driver for windows from Cloudera's Page.  Now install the Driver 

Installing is basically a very easy task. Advisable to gracefully stop BI Services before Installing as the Installer might ask you to stop Oracle Application Server.

Check for Sample DSN Conneciton

 Once you are done with ODBC driver installation go to run > ODBC and check if you have an entry named 'Sample Cloudera Impala DSN' to confirm that the driver Installation has successfully completed. 

Now click to add a new System DSN and select Cloudera Impala Driver as seen in the image below,

Select Cloudera Impala Driver from the list of drivers

Next provide connection details to your Cloudera Impala Server as seen below.

Default port for Cloudera Impala is 21050. Once you are done giving the details for the connection click on test to test connectivity as seen below,

 Now go to the OBIEE repository and Import metadata as shown below, Select the recently created Impala ODBC data source and proceed.

 

 

Select the Impala Tables to imported and Click Finish. Check the Physical Layer of the repository to see if the Impala Table has been successfully imported. You can use view data to feature to confirm the connection correctly.  

Table in Physical Layer of OBIEE Repository

 Tags: Big Data Cloudera Impala Server ODBC connectivity with OBIEE and BI Tools.