TERADATA

5510 Invalid session mode for procedure execution

Problem:

CALL USERAdmin.Create_User ('C34576','TD','U_Administrators','')

Executed as Single statement. Failed [5510 : HY000] Invalid session mode for procedure execution.

Elapsed time = 00:00:00.031

STATEMENT 1: Unknown failed.

Cause:

The session mode within which the CALL SQL is submitted is different than the one in which the stored procedure was created. A stored procedure created in Teradata mode cannot be executed in ANSI mode and vice versa.

Solution:

Change the session mode and resubmit the request or recreate the procedure in the desired session mode and resubmit the request.

Example:

For the above error, its failing because the transaction mode of the stored procedure is different than the transaction mode of the session.

Here I am checking the Transaction Mode of the stored Procedure.

help procedure USERADMIN.Create_USER attributes;

We can see from the Transaction Sematics column the mode is TERADATA. Now, Lets check the Transaction mode of the current session.

SELECT transaction_mode from dbc.SessionInfoV WHERE SessionNO=SESSION;

Transaction Semantics	Print Mode	Platform	Character Set	Default Character DataType	Collation	SPL Text	Version Number	Default Database	Warning Option	Creation Timezone	Creation Timezone String
TERADATA	N	WINDOWS	ASCII	LATIN	CHARSET_COLL	Y	11	USERADMIN	Y	00:00

Transaction_Mode

A

We can see the Transaction mode of the current session is ANSI. So lets change the Transaction mode of the session from ANSI to TERA, then it should work. So the transaction mode of the stored procedure should be same as your session Transaction mode.

Right Click to the database connection and Click Properties.

Select the TMODE and click Remove.

Click ADD and from the drop down menu select JDBC Property TMODE and select property Value TERA. Click OK.

Now it should be look like this.

Now click OK and Click Yes in the pop up Dialog box.

Now executing the procedure working fine.

CALL USERAdmin.Create_User ('C34576','TD','U_Administrators','')

Executed as Single statement.

Elapsed time = 00:00:00.920

STATEMENT 1: Unknown completed.

Thank You

Manoj Kumar 

Olympic BI Dashboard using Pentaho CE 5.4 version

                    Olympic BI Dashboard

1) Bootstrap panels
2) Relatively adjustment of the charts and other components when preview in different devices like laptop, desktop, ipad, mobile phone using mozilla firefox web browser (shft+ctrl+m).

I have developed cross tab report and scan report more then 150+ reports using pentaho report designer  and btable components using reports in CDE and LDAP also build for security (user based and role based security )

 

Thanks

Manoj Kumar 

Pentaho BI Developer

Running Fully Functional Eclipse BIRT Reports in Pentaho

Running Fully Functional Eclipse BIRT Reports in Pentaho - UPDATE

When I wrote my post about integrating the Eclipse BIRT report viewer in Pentaho almost a year ago, Pentaho was at release 3.6. Since then, 3.7 and 3.8 have been released, and 3.9/4.0 is about to go GA. The biserver's plugin architecture has seen some changes over these releases, causing the BIRT plugin to break.
A new plugin is now available, compatible with Pentaho >= 3.6 and BIRT releases 2.6.x and 3.7. The installation instructions remain unchanged, check my original post for reference.
BIRT switched to a jar-based runtime with version 3.7. The default runtime jar, however, does not include the OpenDocument emitters that were also introduced in 3.7. If you want to offer your users the possiblity to export reports to ODF-formats, you’ll need to add some jars to the runtime webapp. All this takes is to copy the necessary jars from the full Eclipse BIRT (designer) download (<ECLIPSE>/plugins/org.eclipse.birt.report.engine.emitter.od*.jar and org.eclipse.birt.report.engine.odf_3.7.0.v20110609.jar, timestamps in file names may vary slightly) to <PENTAHO>/biserver-ce/tomcat/webapps/WebViewerExample/WEB-INF/lib/. Recent BIRT versions also need a commons-logging jar in the classpath. You can copy this file from the <PENTAHO>/tomcat/webapps/pentaho/WEB-INF/lib to <PENTAHO>/tomcat/lib or to <PENTAHO>/tomcat/webapps/WebViewerExample/WEB-INF/lib.




In addition to the original post: you can apply security to your BIRT reports by adding the BIRT report file extension (.rptdesign) to the ‘acl-files’ element in /pentaho-solutions/system/pentaho.xml, so it looks something like the element below:

xaction,url,prpt,xdash,xcdf,rptdesign

This plugin is very simple. All it does is tell the biserver to recognice the .rptdesign file extension, and point it to the BIRT report viewer for execution. As simple as it is, I will release the code for this plugin in a couple of days.