Reading using Stored Procedure Calls

Hi All,
I have a scenario where I need to read data froma table and post it to ECC. A stored procedure call is used to generate the data from the database. How do I handle this in sender JDBC adapter?
XIer

Hey
there are some restrictions on executing stored procedures for Oracle,anyways have a look at the following blog
/people/jegathees.waran/blog/2007/03/02/oracle-table-functions-and-jdbc-sender-adapter
Thanx
Aamir suhail

Similar Messages

How to use Stored Procedure Call in Sender JDBC adapter

Hi All,
Could someone send me a blog on how to use Stored Procedure call in Sender JDBC adapter?
Xier

Hi Xler
refer these links
/people/yining.mao/blog/2006/09/13/tips-and-tutorial-for-sender-jdbc-adapter
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
Also, you can check Sriram's blog for executing Stored Procedures,
/people/sriram.vasudevan3/blog/2005/02/14/calling-stored-procs-in-maxdb-using-sap-xi
/people/jegathees.waran/blog/2007/03/02/oracle-table-functions-and-jdbc-sender-adapter
This blog might be helpfull on stored procedures for JDBC
JDBC Stored Procedures
/people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures
Please go through these threads and see if it helps...
Re: How to execute Stored Procedure?
Re: Problem with JDBC stored procedure
Thnaks !!

Stored procedure call returns null result set when using temp table in sp!

Here's a really odd problem...
SQL Server stored procedure called sp_Test takes 1 input INT. Here is the code I call it with
cStmt = connection.prepareCall("{call sp_Test(?)}");
cStmt.setInt(1, 44);
cStmt.execute();
rs = cStmt.getResultSet();When the body of the stored proc is
CREATE PROCEDURE sp_Test(@i_NodeID INT)
AS
BEGIN
SELECT node_id FROM tbl_NavTree
END
GOthe query works and I get all node_id back in rs
BUT when the body of the stored proc is
CREATE PROCEDURE sp_Test(@i_NodeID INT)
AS
BEGIN
CREATE TABLE #Descendants(
descendant_id INT
SELECT node_id FROM tbl_NavTree
DROP TABLE #Descendants
END
GOThe rs comes back as NULL. Really really weird if you ask me. I also tried removing the DROP TABLE line just in case the SELECT had to be the last statement but still NULL.
Final note is that BOTH the above stored proc bodies work when executed within SQL Server query analyser.
Must be JDBC .. what can it be!??

DROP TABLE #DescendantsMS SQL Server - right?
Then don't drop the table.
From the MS docs for "create table"
Local temporary tables are visible only in the current session;
A local temporary table created in a stored procedure is dropped automatically when the stored procedure completes. The table can be referenced by any nested stored procedures executed by the stored procedure that created the table. The table cannot be referenced by the process which called the stored procedure that created the table.

Use Stored Procedure to call up DI API

HI all,
I will like to know whether i can use stored procedure to create DI API when i triggers on new document on particular customer?
Example:
Database A create AR Invoice then i triggers on it directly use stored procedure to call up DI API to create AP Invoice on Database B without create any necessary add-on on the same server.
Thank you.
Cheers,
danny

Hi Danny,
Sorry to inform you that it is impossible to call DI in stored procedure.
An AddOn handling FormDataEvent, DI Event service and B1iSN would be the right approches to your requirement.
1.DI Event Service and B1iSN are solutions in server side. You can find DI EventService here:
SAP Business One Tools [original link is broken]
=>DI Event Service=>View this article
Then you can find a sample project in its installation folder.
2.AddOn soultion will be in the client of source company, just one addon is fine.
sample code:
Private Sub FormDataEventHandler( _
    ByRef BusinessObjectInfo As SAPbouiCOM.BusinessObjectInfo, _
    ByRef BubbleEvent As Boolean) Handles oApp.FormDataEvent
        'You may add the target documents, 133 - A/R invoice.
        'Before action = true, start the transation
        If BusinessObjectInfo.FormTypeEx = "133" _
                And BusinessObjectInfo.EventType = SAPbouiCOM.BoEventTypes.et_FORM_DATA_ADD _
                And BusinessObjectInfo.BeforeAction = True Then
            oCompany.StartTransaction()
            'BubbleEvent = False
        End If
        'Before Action = false,
        'Update product item tree
        'Succeed, commit, otherwise rollback
        If BusinessObjectInfo.FormTypeEx = "133" _
        And (BusinessObjectInfo.EventType = SAPbouiCOM.BoEventTypes.et_FORM_DATA_ADD) Then
            If BusinessObjectInfo.BeforeAction = False And BusinessObjectInfo.ActionSuccess Then
                Dim objectKey As String = String.Empty
                oCompany.GetNewObjectCode(objectKey)
                MsgBox(BusinessObjectInfo.Type)
                Dim oInvoice As SAPbobsCOM.Payments = Nothing
                oInvoice = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices)
                If oInvoice.GetByKey(CInt(objectKey)) Then
                    Dim paymentInvoices As SAPbobsCOM.Payments_Invoices = oInvoice.Invoices
                    Dim oInvoices As SAPbobsCOM.Documents = oCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices)
                    '======================================================================
                    'add you code to add A/P Invoice in company B
                    'oInvoices.GetByKey(***)
                    'lRetCode = add an A/P invoice according to A/R invoice above...
                    '======================================================================
                    'We don't need to rollback manually, it will be automatically rollbacked if any error ocurrs
                    If lRetCode = 0 Then
                        'update the production tree succesfully,
                        oCompany.EndTransaction(SAPbobsCOM.BoWfTransOpt.wf_Commit)
                    End If
                End If
            End If
        End If
    End Sub
Kind Regards, Yatsea

Stored Procedure call from JDBC sender for Oracle Database

Hi,
I have a requirement to call stored procedure using JDBC sender adapter for retriving data from an Oracle database.
I need to execute first stored procedure call from Querry SQL statement and then trigger second stored procedure call for confirming the succesful retrival of those records from the update SQL statement.
Querries:
1. Can we trigger stored procedure from Update statement of JDBC sender.
2. Can we call stored procedure from Querry statement, since I have read on other sdn threads that stored procedure calls on Oracle database are not allowed. If not possible to have "Execute stored procedure" would the function call (select * from table(function name)) work same as stored procedure.
3. In a JDBC sender the Querry statement and Update statement are executed in same session call and same database connection. What happens if the querry statement was not succesful, would the update be still triggered.
Please note PI does not have direct access to main table and hence the need to have separate stored procedure calls.
The PI version is PI 7.11 sp4.
Appreciate your inputs.
Thanks.
Siddhesh S.Tawate

>1. Can we trigger stored procedure from Update statement of JDBC sender.
I think not possible using update statement.
> Can we call stored procedure from Querry statement, since I have read on other sdn threads that stored procedure calls on Oracle database are not allowed. If not possible to have "Execute stored procedure" would the function call (select * from table(function name)) work same as stored procedure.
Yes using select query you can call stored procedure.
>. In a JDBC sender the Querry statement and Update statement are executed in same session call and same database connection. What happens if the querry statement was not succesful, would the update be still triggered.
No select and update handles in the same session using the same thread so if one transaction fails update should not proceed.

Structure for Stored Procedure Call

Hi All,
Guys I am trying to call a stored procedure call using receiver jdbc adapter...
This is the outgoing message:
<b><?xml version="1.0" encoding="UTF-8" ?>
- <ns0:SP_DB xmlns:ns0="urn:sce-com:xi:dev:mohammf">
- <Test>
- <PP_TEST_P action="EXECUTE">
<table>PP_TEST_P</table>
<RECTYPEIND type="CHAR">CC</RECTYPEIND>
<JENUMBER type="CHAR">76724</JENUMBER>
<COMPANY type="CHAR">BCEO</COMPANY>
<CONSTANT1 type="CHAR">AB</CONSTANT1>
<SYSTEMDATE type="CHAR">08/12/2007</SYSTEMDATE>
<DR_CR_ID type="CHAR">0</DR_CR_ID>
<AMOUNT type="CHAR">934928599475843</AMOUNT>
<MONTH_NUMBER type="CHAR">000008</MONTH_NUMBER>
<COST_CENTER type="CHAR">LosAngeles</COST_CENTER>
<ORDERNO type="CHAR">694950375830</ORDERNO>
<WBS type="CHAR">Southern California Edis</WBS>
<ACCOUNTID type="CHAR">6949503758</ACCOUNTID>
<BATCH_ID type="CHAR">3408102007</BATCH_ID>
<ASSIGNMENT type="CHAR">Technology Solutio</ASSIGNMENT>
<GL_JOURNAL_CATEGORY type="CHAR">GHTF</GL_JOURNAL_CATEGORY>
<PROFIT_CENTER type="CHAR">3434694950</PROFIT_CENTER>
<REFDOCNUMBER type="CHAR">00000000004304300056006056</REFDOCNUMBER>
</PP_TEST_P>
- <PP_TEST_P action="EXECUTE">
<table>PP_TEST_P</table>
<RECTYPEIND type="CHAR">XX</RECTYPEIND>
<JENUMBER type="CHAR">76724</JENUMBER>
<COMPANY type="CHAR">BCEO</COMPANY>
<CONSTANT1 type="CHAR">AB</CONSTANT1>
<SYSTEMDATE type="CHAR">08/12/2007</SYSTEMDATE>
<DR_CR_ID type="CHAR">0</DR_CR_ID>
<AMOUNT type="CHAR">934928599475843</AMOUNT>
<MONTH_NUMBER type="CHAR">000008</MONTH_NUMBER>
<COST_CENTER type="CHAR">LosAngeles</COST_CENTER>
<ORDERNO type="CHAR">694950375830</ORDERNO>
<WBS type="CHAR">Southern California Edis</WBS>
<ACCOUNTID type="CHAR">6949503758</ACCOUNTID>
<BATCH_ID type="CHAR">3408102007</BATCH_ID>
<ASSIGNMENT type="CHAR">Technology Solutio</ASSIGNMENT>
<GL_JOURNAL_CATEGORY type="CHAR">GHTF</GL_JOURNAL_CATEGORY>
<PROFIT_CENTER type="CHAR">3434694950</PROFIT_CENTER>
<REFDOCNUMBER type="CHAR">00000000004304300056006056</REFDOCNUMBER>
</PP_TEST_P>
</Test>
</ns0:SP_DB></b>
The error I am getting is:
<b><i>2007-08-20 09:44:05 Error Unable to execute statement for table or stored procedure. 'PP_TEST_P' (Structure 'Test') due to java.sql.SQLException: ERROR: Invalid XML document format for stored procedure: 'type="<SQL-type>"' attribute is missing for element 'table' (Setting a SQL-type (e.g. INTEGER, CHAR, DATE etc.) is mandatory !)
2007-08-20 09:44:05 Error JDBC message processing failed; reason Error processing request in sax parser: Error when executing statement for table/stored proc. 'PP_TEST_P' (structure 'Test'): java.sql.SQLException: ERROR: Invalid XML document format for stored procedure: 'type="<SQL-type>"' attribute is missing for element 'table' (Setting a SQL-type (e.g. INTEGER, CHAR, DATE etc.) is mandatory !)
2007-08-20 09:44:05 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PP_TEST_P' (structure 'Test'): java.sql.SQLException: ERROR: Invalid XML document format for stored procedure: 'type="<SQL-type>"' attribute is missing for element 'table' (Setting a SQL-type (e.g. INTEGER, CHAR, DATE etc.) is mandatory !)
2007-08-20 09:44:05 Error Exception caught by adapter framework: null
2007-08-20 09:44:05 Error Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PP_TEST_P' (structure 'Test'): java.sql.SQLException: ERROR: Invalid XML document format for stored procedure: 'type="<SQL-type>"' attribute is missing for element 'table' (Setting a SQL-type (e.g. INTEGER, CHAR, DATE etc.) is mandatory !).</i></b>
Pls advice..
XIer
Message was edited by:
XIer

Hi,
Check your DATA TYPE attributes with the attributes of the column names in the Database table. There is a mismatch between the DT and Table in the database.
<b>Cheers,
*RAJ*</b>

Response from one stored proc. to another stored procedure call in JDBC

Hi,
I have to call 2 stored procedures, where the response from first stored procedure ( an id) is mapped as a parameter to the second stored procedure call.
My question is that can this be achieved without using BPM?
Can we somehow map the response from the stored procedure 1 to stored procedure 2 parameter w/o using BPM?
I have to insert multiple rows using the stored procedure.
Should I use STATEMENT unbounded times ( which means stored procedure is called multiple times) or should I use the parameter as unbounded ( like an array, maybe define the parameter as an array in the stored procedure)?
From the performance standpoint, which approach is better?
Please suggest.

Hi Ardent !
I think you could use 2 mapping programs (message mapping objects) in your interface mapping. The first one, executes and returns the ID to a message type defined by you for internal use only between both stored procedure executions. The second ones uses that message type as source message and the XML required by the JDBC for the second stored procedure execution as target message type. This can be done without BPM.
Regards,
Matias.

JDBC callableStatement stored procedure call cancellation?

up vote0down votefavorite
I have a very complex oracle stored procedure that searches and retrieves some data. The procedure returns an output parameter - an oracle cursor. I execute the procedure by JDBC:
CallableStatement stmt = conn.prepareCall("{call myprocedure(?,?,?,?}");
The problem is, the queries can sometimes take quite long (few minutes) and i would like user to be able to cancel the query anytime by clicking button. I have reference to stmt object, but unfortunatelly calling stmt.cancel() (from other thread) has NO EFFECT.
On the other hand when i change the CallableStatement sql to some query like:
CallableStatement stmt = conn.prepareCall("select * from all_objects");
i get "java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation" after calling stmt.cancel() - so thats the right reaction.
Does that mean than i cannot cancel stored procedure call via jdbc, but only simple select statements? Does anyone else had and resolved similar problem?
I guess i could cancel the query by oracle kill session, but i use connection pooling (jboss) and i have plenty of sessions for the same user existing.
Database Product Version is Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production JDBC Driver Version is 11.2.0.4.0
any help will be appreciated.

This property didnt help, still no reaction after statement.cancel().
I could not cancel the statment from the db size , so i decided to spawn new java thread and run the statement in that thread, and when user clicks cancel button i just cancel the thread, some snipper of code below:
               AtomicBoolean userCanceled - this must be AtomicBoolean or volatile variable, so other threads would see the change of variable after clicking button
               try{
                MyCallableQuery callable = new MyCallableQuery(rs,stmt,this,rsh,outParameter);
                FutureTask<T> queryTask = new FutureTask<T>(callable);
                ExecutorService executor = Executors.newFixedThreadPool(1);
                executor.execute(queryTask);
                while (!queryTask.isDone()){         //stil processing statement
                 Thread.sleep(100);
                      if (userCanceled)){               //user decided to cancel
                       futureTask1.cancel(true);
                       executor.shutdown();
                       throw new SQLException("User decided to cancel procedure call");
                 result = futureTask1.get();
                 //here the code after the resultset has been processed without cancelation
               catch (SQLException e}{
               //here the code when user decided to cancel like clearing the datatable
and my callable class is like:
public class MyCallable<T> extends ProcRunner implements Callable<T> {
    private ResultSet rs;
    private CallableStatement stmt;
    private ProcRunner procRunner;
    private ResultSetHandler<T> rsh;
    private Integer outParameter;
    public MyCallable(ResultSet rs,CallableStatement stmt,ProcRunner procRunner,ResultSetHandler<T> rsh,Integer outParameter){
        this.rs = rs;
        this.stmt = stmt;
        this.procRunner = procRunner;
        this.rsh = rsh;
        this.outParameter = outParameter;
    @Override
    public T call() throws Exception {
       T result = null;
      stmt.executeUpdate();
       rs = (ResultSet) stmt.getObject(outParameter);
       rs = this.wrap(rs);
       result = rsh.handle(rs);
    return result;

WCF OData Service stored procedure call generates "Operation could destabilize the runtime" error with $select option

I've been trying to call a stored procedure through Entity Framework and WCF Data Services (OData). It returns an entity not a complex type. Following walkthroughs found all over the web, I came up with this code inside my service:
[WebGet]
public IQueryable<Entity> GetEntitiesByParameterId(int parameterId)
return CurrentDataSource.GetEntitiesByParameterId(parameterId).AsQueryable();
Calling the proc this way: ~WcfService.svc/GetEntitiesByParameterId?parameterId=1 executes
the stored procedure and returns entities that should be returned. No problem there.
Everything works well until I try to use $select OData option ie. ~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$select=name.
Upon debugging, the method above runs without any error but it returns an Operation could destabilize the runtime error upon reaching the
client. After so much research, apparently it is a very general error pointing to a lot of different causes. I haven't found one that really matches my particular problem. Closest are
http://stackoverflow.com/questions/378895/operation-could-destabilize-the-runtime
https://social.msdn.microsoft.com/Forums/en-US/d2fb4767-dc09-4879-a62a-5b2ce96c4465/for-some-columns-entity-properties-executestorequery-failed-with-error-operation-could?forum=adodotnetdataservices
but none of the solutions worked on my end.
Also, from the second article above:
This is a known limitation of WCF DS. ...
Second is that some of the queries won't work correctly because LINQ to EF needs little different LINQ expressions than LINQ to Objects in some cases. Which is the problem you're seeing.
It has been posted on 2012. If it its true, are there still no updates on this? And is there any other workaround to get the $select working on the stored proc call?
What works:
~WcfService.svc/GetEntitiesByParameterId?parameterId=1
~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$top=1
~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$skip-5
~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$filter={filter query}
~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$expand=SomeNavigationProperty
What doesn't work:
~WcfService.svc/GetEntitiesByParameterId?parameterId=1&$select=name
Tech details:
EntityFramework 5, WCF Data Service 5.0, OData V3
*I've also tried upgrading to EF6 and WCF 5.6.2 and it still didn't work.
Any help would be appreciated. Thanks!

Someone from SO replied to my question there and said that $select is still not supported though I couldn't find any definitive documentation about it.
From what I gather and observed, $select breaks the stored procedure call because it tries to alter the data shape already gotten from the database and attempts to return a dynamic entity instead. Something about the stored proc returning an ObjectResult might
be messing it up. As I have said, these are merely my observations.
Workaround: I found a simple and elegant workaround for it though. Since my stored procedures are only getting data from the database and does
not alter data in any way (INSERT, UPDATE, DELETE), I tried using table-valued functions that returns a table equivalent to the entity on my EF. I've found that calling this function on the Service Operation method returns an IQueryable<Entity> which
is basically what is needed. $select also works now and so does other OData query options.
Steps:
Create a function on the database
Update EDMX -> Add function
Add new Function Import with Entity return type
Create service operation in WCF Data Service that calls CurrentDataSource.<FunctionName>()
Test in fiddler.
CODES
Database Function:
CREATE FUNCTION GetEntities(@parameter)
RETURN @entites TABLE(
[Id] [int],
[Name] [nvarchar](100),
AS
BEGIN
INSERT INTO @entities
SELECT [Id], [Name], ... FROM [EntityTable]
RETURN
END
WCF:
[WebGet]
public IQueryable<Entity> GetEntity(int parameter)
return CurrentDataSource.GetEntity(parameter);
It doesn't really solve the stored procedure problem but I'm marking this as answer until someone can provide a better one as it does solve what I'm trying to do.
Hope this helps others too. :)

Pass a null value to a JDBC stored procedure call?

pass a null value to a JDBC stored procedure call? Is this even possible? My DBA gave me a procedure to call that sometimes requires a null value. I don't think this is even possible.

do you mind tell me how to resolve your problem?i using the setnull method,but it doesn't work.

Best approach for performing DMLs using stored procedures

Hi,
I have a really general question and would like to hear your say about this.
I want my application to manipulate or read data using stored procedures (or packages in that manner) and not directly using queries against the DB.
Let's say I have a table with many columns:
create table test (pkid number(10),col1 varchar2(30), col2 number(10), col3 date,...);For such a DML procedure, is it best to do something like
procedure do_update(i_pkid IN number,i_col1 IN varchar2, i_col2 IN number, i_col3 IN date,...) as
begin
   update test
   set col1=i_col1,
        col2=i_col2,
        col3=i_col3...
   where pkid=i_pkid;
   commit;
end;Or do a selective update, meaning update only a certain column every time, given only 1 column actually changes? (and how to do that - separate procedures for each column? [columns can be nulls])
Also, is it better to work with test.col1%type instead of specifying the data type in the procedure?
And one last question - If I have a table with 100 columns and I don't want to create a procedure with 100 parameters - the best approach would be to use a record?
I just need to be set on the way I start implementing things in order to do it well from the start.
Many thanks.
Edited by: Pyrocks on Nov 17, 2010 1:58 PM

Pyrocks wrote:
One last clarification (although it may be more related to c/c++ developers - maybe one of you will know):
We are working with C++ and VB against a SQLServer and my part is to translate all the existing procedures to Oracle in order to migrate the application to work with Oracle DB.
The existing procedures use an IN parameter for each column in the table and I would really like to use rowtype like you mentioned.
Since I'm not a c/c++/vb developer - is there an easy way of working with such types, or even User-Defined Types, from c/c++/vb (as in passing a rowtype record from c++ to a SP ?)
I'm not looking for the actual way - just want to know how hard it would be and how much code needs to be changed in order to be able to convince the developers that this is the RIGHT way to work.
PS. none of our developers have experience with ORACLE so they wouldn't know the answer...Not actually an Oracle server-side (SQL language or PL/SQL language) question - but a client one. And it has been a long time since I wrote a fat client using C/C++ or Delphi.
The OCI (<i>Oracle Call Interface</i>) supports advance (user defined) SQL data types. Has since Oracle 8i. So in that respect, yes the client can support custom SQL data types.
How well it does depends entirely on that client language's features wrt OCI integration. For example, Delphi 4 was release around Oracle 8i and supported custom SQL types. I would expect that most languages today (like Java and C#) will provide support for it.
As for usiong +%ROWTYPE+ - this is a PL/SQL clause as far as I know. Unsure whether it is supported by the OCI. What could support it is a pre-compiler like Pro*C. These enable you to mix pseudo SQL source code with client language source code. The pre-compilation step then replaces the pseudo SQL code with native client language calls to the OCI. The code is then compiled by that client language's compiler. Pre-compilers can pull all kinds of interesting "tricks" with their pseudo SQL code support.
The best would be to consult the applicable client language's manuals that describe the interface it supports (via OCI) to Oracle.

Best practices to use stored procedure

Just wondering about best practices of using Stored procedures in TOPLink with respect to Objects. Any thoughts on this?
I find the approach suggested at re:Coding for Stored Procedures is a lot of work! seems to be fine.
Is there any thoughts on converting results directly into Java objects?
Murali

I encountered the same problems.
See the topic I posted: Re: Mapping a Java attribute to the result of a function call
The solution I used is good, but has its restrictions.
I created a database view on the query that uses stored functions. Then, I mapped my object to the database view. Problem solved.
However, like I said, this solution has its restrictions:
1) Your database must support views
2) This only works for read-only queries
I hope this helps you any further.
Kind regards,
Erwin

Using stored procedures for insert, update and delete

Hello all;
We have a question from our customer (who is the DBA), who has not in the past used TopLink, about whether it makes sense to tie TopLink into existing stored procedures to save and retrieve informations.
Is it possible?
Is there any circumstance under which it is a good idea?
Thanks

In TopLink any operation for which TopLink generates SQL, can be replaced by custom SQL, or a stored procedure call.
Custom SQL or stored procedures can be used for each of the descriptor's CRUD operations, but also for mapping queries and named queries. The Mapping Workbench only supports defining custom SQL for the descriptor CRUD operations and named queries, so many of the stored procedures call from the descriptor and mappings will need to be done through amendment methods.
Whether it makes sense or not depends on the application and the company and their requirements. It will add significant overhead to the development process to have to define and maintain all of the stored procedures, and the stored procedure calls in the descriptors. You may wish develop your application using TopLink generated SQL, and once you have the model and queries stabilized then switch to using stored procedures.
Whether it is a good idea depends on the application and the company and their requirements. Stored procedures may give the DBA more freedom to change the data-model once in production, and may allow for adding database-level security checks. In general using stored procedures will not improve performance if the procedures contain the same SQL that would have be executed anyway, but they may allow for the DBA to tune the SQL better.

Regional settings influences jdbc stored procedure calls?

Hi,
We have a strange problem: we use a jdbc test client
that does a simple stored procedure call with one
input parameter (integer) and one output parameter
(integer). Like:
"? = callprocedure(?)" . The database resides on a different server.
The problem is: this only works when we use "netherlands" regional setting on the windows 2000 machine that
java client program runs on. If we switch to
"english (united states)" the call gives other results
in the output parameter / returns an error code.
Does this have something to do with the Locale of the
virtual machine? Or do I have to do something with
NLS_LANG to eliminate the behaviour that is dependent on
the windows regional settings? Please help!
Thanks,
Michel Schudel
We use the Oracle JDBC thin driver, latest version.
(archive: classes12.zip)

Ok, here it is. Basically, I first call a stored procedure called SETPARAM which receives two Strings:
a parameter name and a a parameter value. After that, I
call a procedure called RUNSQLKIT without any input parameters. The output parameter is an integer that indicates the number of "cells" in the output message. After that, I start to retrieve the cells but that is not important here. What happens is: with Dutch regional settings, the number of cells is normal (387) but with
US settings, the number of cells is -1 (indicates an error.) Why? I use no dates or floating point values as
input/output!
Jvm version is 1.3.1_08, oracle driver is 8.1.7
(Oracle 8i) thin jdbc driver. Oracle runs on AIX.
conn = m_dataSource.getConnection();
// Setup the input params
stmtInput = conn.prepareCall("BEGIN Pck_Sqlmast.setparam(?,?); END;");
for (final Iterator iter = m_kitParameterNames.iterator(); iter.hasNext();) {
final String sName = (String) iter.next();
final String sValue = input.getParameter(sName);
if (sValue != null) {
stmtInput.setString(1, sName);
stmtInput.setString(2, sValue);
stmtInput.executeUpdate();
// Call the kit
stmtRun = conn.prepareCall("BEGIN ? := Pck_Sqlmast.runsqlkit(?); END;");
stmtRun.registerOutParameter(1, Types.INTEGER);
stmtRun.setString(2, m_kitName);
stmtRun.executeUpdate();
final int iCells = stmtRun.getInt(1);
Hi Michel,
Perhaps you would care to post some more information
including:
1. Entire error message and stack trace you are
getting.
2. The part of your java code where the error
occurs.
3. Java version you are using.
4. Oracle database version you are using.
5. Platform on which Oracle database is running.
Good Luck,
Avi.

Capture error messages from stored procedure calls

Hi there,
How do I capture a stored procedure calls error messages provided the stored procedures does not have output parameters? This questions applies to Oracle 7.3.4 stored procedures calls.
TQ
Neo

There are two parts.
The stored proc must 'throw' an exception.
And java must catch it.
You probably already have the java part. That is the catch(SQLException).
As for the stored proc you can use the following search string in the jdbc forum
raise oracle
You need to use 'raise' in the stored proc but I am not sure of the exact form, but one of the threads using the above search string is likely to have it.

Reading using Stored Procedure Calls

Similar Messages

Maybe you are looking for