JDBC : Storing clob

Hi,
I will be retrieving the clob from result set and store the name and cloc as name , value pair in hashmap. Is there any known limitations in this approach ?
Thanks
Poornima

Okay. A bit of a better understanding. In that case:
When you set-up the CLOB's (in Oracle) you have two options. You can store them in the filesystem or store them in the database. If you opt for the former, your commit times should decrease slightly, as the commit only encompases the actual row that contains the pointer to the data. So, setup Oracle to use the filesystem to hold the CLOB data. Your access times may very slightly increase, but you should see a slight performance increase when commiting an insert."I am using CallableStatement as I am using Stored Procedures. I am using Stored Procedures as I have designed a framework for my application. doing this removes all SQL Code from the java application."
Huh? SQL is interoperable (mostly) like Java. Stored procedures, on the other hand, tie you explicitly to Oracle. What do you gain with this?
If flush() is causing performance issues, set the buffered writer for a smaller amount (2048 or 4096, or better yet, look up what Oracle's optimal buffer size is. I think they even provide a method in their implementation-specific version of CLOB).- Saish
"My karma ran over your dogma." - Anon

Similar Messages

  • JDBC stored procedure not working in Weblogic 12.1.3

    Hi,
    We are migrating from WLS 12.1.2 to 12.1.3.
    We have a JDBC stored procedure which used to work correctly under 12.1.2. I understand that 12.1.2 uses ojdbc5/ojdbc6 jars (11.2.0.x). After migrating to 12.1.3, the stored procedure is not working.
    We have narrowed it down to the different between 12.1.2 using ojdbc5/6 and 12.1.3 using ojdbc7 jars, though we do not understand what the difference here is.
    Connection connection = getConnection();
    CallableStatement callableStatement = connection.prepareCall("{call RECEIPT_LOG (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}");
    callableStatement.registerOutParameter("PIO_RECEIPT_LOG_ID", java.sql.Types.INTEGER);
    callableStatement.setLong("PIO_RECEIPT_LOG_ID", 0);
    callableStatement.setString("PIO_DRAWER_NAME", request.getDrawerName());
    callableStatement.setString("PIO_DRAWER_FIRST_NAME", request.getDrawerFirstName());
    callableStatement.setString("PIO_DRAWER_OTHER_NAMES", "");
    callableStatement.setString("PIO_DRAWER_STREET_NO", "");
    callableStatement.setString("PIO_DRAWER_STREET", "");
    callableStatement.setString("PIO_DRAWER_LOCALITY", "");
    callableStatement.setLong("PIO_DRAWER_POSTCODE", 0);
    callableStatement.setString("PI_PAYMENT_TYPE", request.getPiPaymentType());
    callableStatement.setLong("PI_APPLICATION_ID", request.getApplicationId());
    callableStatement.setString("PI_PRIMARY_ID", request.getPiPrimaryId());
    callableStatement.setString("PI_SECONDARY_ID", request.getPiSecondaryId());
    callableStatement.setDouble("PI_AMOUNT", request.getPiAmount());
    callableStatement.setInt("PI_TAX_AMOUNT", 0);
    callableStatement.setNull("PI_VPC_TXNRESPONSECODE", java.sql.Types.VARCHAR);
    callableStatement.setInt("PI_VPC_TRANSACTIONNO", 0);
    callableStatement.setString("PI_VPC_MESSAGE", "");
    callableStatement.setString("PI_VPC_ACQRESPONSECODE", "");
    callableStatement.setString("PI_VPC_RECEIPTNO", "");
    callableStatement.setString("PI_VPC_BATCHNO", "");
    callableStatement.setString("PI_VPC_CARD", "");
    callableStatement.setString("PI_VPC_MERCHTXNREF", "");
    callableStatement.setString("PI_VPC_MERCHANT", "");
    callableStatement.setString("PI_VPC_ORDERINFO", "");
    callableStatement.setInt("PI_VPC_AMOUNT", 0);
    callableStatement.setString("PI_VPC_AUTHORIZEID", "");
    callableStatement.registerOutParameter("PO_RECEIPT_NO", java.sql.Types.VARCHAR);
    callableStatement.registerOutParameter("PO_SOURCE_ID", java.sql.Types.INTEGER);
    callableStatement.registerOutParameter("PO_PAYMENT_METHOD_TEXT", java.sql.Types.VARCHAR);
    callableStatement.registerOutParameter("PO_CREATE_COMMENT", java.sql.Types.VARCHAR);
    callableStatement.registerOutParameter("PO_ERROR_MESSAGE", java.sql.Types.VARCHAR);
    boolean isSuccessful = callableStatement.execute();
    Long receiptLogId = callableStatement.getLong("PIO_RECEIPT_LOG_ID");
    Here, when the callableStatement.execute() is fired, the isSuccessful is false and the output parameter receiptLogId is 0
    Any help appreciated.
    Regards,
    Rahul

    Hi All,
    We still haven't figured out what the problem is with JDBC when using ojdbc7.jar but, as an alternate solution we ported the code to Spring JDBC and got it working.
    Regards,
    Rahul

  • Help required in JDBC Stored Procedure

    Hi All,
    i have a requirement where i need to update the Database table using Stored Procedure from PI.
    I have the receiver JDBC channel and have done the mapping.
    The stored procedure has inputs of type NUMBER, VARCHAR2,DATE. in the message mapping i tried passing the same values in the type field, it throwed an error like UnSuppoted Format. Then i changed the type to integer for NUMBER and String for Varchar2 then also it is throwing an error like
    +java.sql.SQLException: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'PUT_XXXXX' ORA-06550: line 1, column 7: PL/SQL: Statement ignored +
    Can any please help with what type i need to send from PI to Stored procedure?
    Also, there two out type fileds defined in the Stored procedure..which i didnt create in my PI structure. Do we need to create that fileds in our structure?
    Please help me.
    Thanks,
    Hemanth.

    Hi Hemanth Kumar,
    I understand that you want to execute a stored procedure using JDBC receiver channel and looking at error message, you think there is an issue with type defined in Data Type.
    Now you need to debug step by step.
    Step 1:- In Interface Mapping Determination, do not refer to Operational Mapping (delete only OM from there, not the receiver Message Interface). By doing so, you are not call the OM (which refer to Graphical Mapping (MM refer to Data Type (which you think is wrong)). Note: As there is no OM, we need to send the exact payload required by receiver JDBC from Runtime Work Bench, for testing purpose.
    Step 2:- In receiver JDBC channel, change u2018Message Protocolu2019 from u201CXML SQL Formatu201D to u201CNative SQL Stringu201D. By doing this, you can do testing very fast; receiver JDBC channel will take only String. And we need to send the exact String which is needed by JDBC Stored Procedure. [Link1|http://help.sap.com/saphelp_nwpi711/helpdata/en/44/7c24a75cf83672e10000000a114a6b/frameset.htm]
    Step 3:- Now from RWB test the scenario. Payload should like this, please take help of Data base team to find the String which needs to send.
    EXECUTE PUT_uspAddress @City = 'New York'
    OR If you have access to the database, logon to it directly and try running the Stored Procedure.
    Step 4:- Now, you should have the string which executes the Stored Procedure correctly to go ahead. Your job is 60% done.
    Step 5:- Now, in receiver JDBC channel, change u2018Message Protocolu2019 from u201CNative SQL Stringu201D to u201CXML SQL Formatu201D. So that receiver JDBC channel will take only XML.
    Step 6:- So now, you have to construct equalant XML structure to String you got in Step 4.
    It may look like this [Link2|http://help.sap.com/saphelp_nwpi711/helpdata/en/44/7b72b2fde93673e10000000a114a6b/frameset.htm]
    <StatementName>
        <storedProcedureName action=u201D EXECUTEu201D>
           <table> PUT_uspAddress </table>
            < City [isInput=u201Dtrueu201D] type=SQLDatatype>val1</ City>
        </storedProcedureName >
      </StatementName>
    Step 7:- Now use the XML you have constructed in Step 6, to test the scenario from RWB. Try to correct if you come up with some errors. Your job is 90% done.
    Step 8:- Now, in Interface Mapping Determination refer back the Operational Mapping again, which contain the Message Mapping. Make sure that Message Mapping give the XML output same as XML you have developed in Step 6.
    FYI. 1. Whatever youu2019re sending, it will be converted to JDBC statement and will be executed on the database. logSQLStatement(JDBC Additional parameters sapnote_0000801367) will be show in logging not in payload.
    2. Most of the cases, type defined in Data Type has no control of what we can send in that element (except Date type). Let say, you can define an element u2018Ageu2019 as u2018numberu2019, but you can always send u201Casdfasdfu201D as input in Message Mapping.
    Regards,
    Raghu_Vamsee

  • JDBC Stored procedure help required

    Hi All,
    Please let me know simple blogs how to use JDBC Stored procedure or any other method  in receiver jdbc adapter to insert or select in 2 tables
    Please  let me know simple blogs how to use JDBC Stored procedure or any other method  in sender jdbc adapter to select from 2 tables
    Thanks

    Hi,
    I am also looking for JDBC Stored procedure or any other method in sender jdbc adapter to select data from 2 tables
    Thanks

  • JDBC/select/async statement to JDBC/stored procedure/sync call

    Hi
    We have JDBC/select/async statement to JDBC/stored procedure/sync call i.e sender and receiver are JDBC.
    PI has to pick all the the records of single internal order number at a time from sender system and upload to receiver JDBc,
    gets the response and routes to sender/insert statement.
    This should run only once per day.
    We will have multiple Internal orders daily, each order consisting of 10 to 20 records but only one IO related records has
    to upload to Receiver/JDBC
    What are the options available ?
    We have thought of following options
    1. SQL query is already to pick, but we have to pick records at one time daily. example: morning,evening or midnight.
       At that time it can pick multiple times but it should not pick through out day
    2. Is there any option in BPM so that we can group IO's at a time and upload ? If so what are the steps need to use
       Any additonal receive step need to be used to pick the records from the table.
    Thanks

    hi
    as i can understando you, you will receive mani IO and you must execute one IO in the receiver SP? if so, you can solve this usssing a ccBPM where you will have to create a mapping(0.N) where the source and the target structure will be the same, the diferrence will be in the occurrance of the target structure which will have to be 0.N (Tab signature in Message Mapping). then back to the ccBPM define a block with the property ForEach. this will  loop any times accord with the number of IO that you receive from the sender. as a result you will execute one SP for each IO.
    so, you ccBPM will be
    RS>TS>BLOCK(Multiline container and single container of source structure)>TS->SS
    RS:Receive Step
    TS:Trans. Step
    SS:Send Step
    Also the container will be:
    source--> type Abs
    source_multiline --> type Abs
    target -->type Abs
    Thanks
    Rodrigo P.
    Edited by: Rodrigo Alejandro Pertierra on Jun 24, 2010 4:54 PM

  • 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.

  • $200 reward to solve problem with JDBC and CLOB.getCharacterOutputStream

    I'm trying to update CLOB with the getCharacterOutputStream as suggested in the example code. It works with US7ASCII DB instance but not instances in UTF8.
    I've been browsing through all the Oracle doc's and found some rather confusing statements:
    In the page at http://oradoc.photo.net/ora816/java.816/a81354/oralob2.htm#1043220
    it says: [When writing to or reading from a CLOB, the JDBC drivers perform all character set conversions for you.]
    also: [The oracle.sql.CLOB class supports all the character sets that the Oracle data server supports for CLOB types.]
    So far so good.
    In the page at http://oradoc.photo.net/ora816/java.816/a81354/oraint3.htm#1012518
    it says [The oracle.sql package supports these datatypes in several ways: CLOBs point to large fixed-width character data items (that is, characters that require a fixed number of bytes per character) and are supported by the oracle.sql.CLOB class.]
    Ooh no! Is this for real? UTF8 is variable width and does this mean it is not supported?
    Any way to get around this?
    In the page at http://oradoc.photo.net/ora816/java.816/a81358/03_pub2.htm#36009
    says [6.The mappings to oracle.sql classes are optimal because they preserve data formats and require no character-set conversions (apart from the usual network conversions). Those classes are especially useful in applications that "shovel" data between SQL and Java.]
    "No character set conversion"? Very confusing!
    I've been hammering on this CLOB/JDBC/UTF8 problem for more than a week now and I really appreciate some solutions, workarounds, or whatever help I can get. I'm running java stored procedure in 8.1.6 on Linux RH6.2.
    For your trouble, I'd pay $200 for the first guy who come up with a verifiable solution.

    This is just findings based upon your comments:
    Please refer to document Oracle8i National Language Support Guide
    Release 2 (8.1.6) from Oracle Documentation Library, Release 8.1.7
    Chapter 6 Java,
    There its clearly mention that:
    "Oracle JDBC drivers provide globalization support by allowing users to retrieve data from or insert data into a database in any character set that Oracle supports. Because Java strings are UCS2 encoded (16-bit Unicode) for JDBC programs, the target character set on the client is always UCS2. Character set conversion is required to convert data from the database character set (Db Charset) to UCS2. This applies to CHAR, LONG, CLOB, and VARCHAR2 data types; RAW data is not converted. "
    Also..please refer this...
    "oracle.sql.CLOB's method getCharacterStream() returns the contents of a CLOB as a Unicode stream."
    "The techniques that Oracle's drivers use to perform character set conversion for Java applications depend on the character set the database uses. The simplest case is where the database uses a US7ASCII or WE8ISO8859P1 character set. In this case, the driver converts the data directly from the database character set to UCS2,which is used in Java applications. "
    "If you are working with databases that employ a non-US7ASCII or non-WE8ISO8859P1 character set (for example, Japanese or Korean), then the driver converts the data, first to UTF8, then to UCS2. "
    In my case the characte-set of the database is WE8ISO8859P1 and for security reason i can't change the character set but my feeling is that if you are updating the CLob from the java client you are forming a reference of a clob in the client which is UCS2 at the Java side. Now when you are populating the clob through java.io.Writer and call the procedure to pass the reference of the clob to the procedure then I believe the JDBC will convert the UCS2 datatype of Clob to UTF8 in the database.
    You can try out the code snippet:
    package ServletGDC;
    import java.io.*;
    import java.util.*;
    import javax.servlet.*;
    import javax.servlet.http.*;
    import oracle.sql.*;
    import java.sql.*;
    import oracle.jdbc.driver.*;
    import ClassesGDC.*;
    public class testUpload extends HttpServlet {
    private String m_strMessage="";//It stores the message to be uploaded along with the Document
    Connection conn=null;
    public void doPost(HttpServletRequest req, HttpServletResponse res)
    throws ServletException, IOException {
    String strContent="";
    //res.setContentType("application/msword");
    res.setContentType("text/html");
    PrintWriter out = res.getWriter();
    try {
    CallableStatement cmt=null;
    OutputStream output=null;
    ByteArrayOutputStream byteoutput=null;
    String strDocString="";
    oracle.sql.CLOB tempClob = null;
    String strPassedFileName="";     // the file name passed in the request object
    String strStdFilename="";//the file name to be given to the best practice
    String strSaveDirectory="";     //the directory in which the bp is to be saved
    String strParamName="";//name of parameters
    String strParamValue="";//value of parameters
    int intTempVariable=0; // temporaty variable
    long lngSizeOfFileUploaded=0;//stores the size of the file which had been uploaded in the file system
    File filePathOfFileUploaded=null;//stores the path of the file uploaded to the file system
    String strQuery="";
    //ST------------checks if the user has logged in or not-----------------------
    HttpSession session=req.getSession(true);
    if(req.getContentLength()>20*1024*1024)
    throw new skip("The size of the posted content is more than 10 MB . If you have a best practice whose size is more than 1 MB please mail it to Us.");
    byteoutput = new ByteArrayOutputStream();
    MultipartParser mp = new MultipartParser(req, 20*1024*1024); // 10MB is the limit of the file to be uploaded
    Part part;//Its an abstact part which helps in retrieving information about the file and the parameters
    while ((part = mp.readNextPart()) != null) {//Reads the next part
    strParamName = part.getName();
    // the following if is executed if the part is for a parameter rather than a file
    if (part.isParam()) {
    }else if (part.isFile()) {
    // it's a file part
    m_strMessage="inside file part";
    FilePart filePart = (FilePart) part;
    strPassedFileName = filePart.getFileName();
    strContent= filePart.getContentType();
    out.println("<BR><font color=red>strPassedFileName is "+strPassedFileName+"</font>");
    if(strPassedFileName != null || !(strPassedFileName.trim().equals("")) ) {
    // the part actually contained a file
    out.println("<BR><font color=red> before forming long</font>");
    //lngSizeOfFileUploaded = filePart.writeTo(filePathOfFileUploaded);      //the statement upload the bestpractice in the
    lngSizeOfFileUploaded = filePart.writeTo(byteoutput);     //specified file path filePathOfFileUploaded.
    out.println("<BR><font color=red> after file is written into the outputstream</font>");
    else {
    throw new skip("The file name is null or it is empty space. Files in such Format are not accepted");
    }//end of else if
    }//end of while loop
    if(     lngSizeOfFileUploaded==0)     {// the size of the file uploaded is zero then the file supplied was not proper and hence exception is to be thrown
    //if(filePathOfFileUploaded.exists())
    //     filePathOfFileUploaded.delete();
    throw new skip("The File could not be uploaded,Possible reasons may be that the file is sent null or the file is corrupted");
    //END---------------the file is uploaded in the proper directory--------------------
    //res.setContentType(strContent);
    out.println("<BR><font color=red>long value is : "+lngSizeOfFileUploaded+" and content is "+strContent+"</font>");
    String strbyte= byteoutput.toString();
    byteoutput.flush();
    Class.forName("oracle.jdbc.driver.OracleDriver");
    // Establish network connection to database
    conn = DriverManager.getConnection("jdbc:oracle:thin:@pc-p32670:1521:GDCDBI","gdc_user","myuser");
    //if(conn!=null)
    out.println("<BR><font color=red>Connection formed"+conn);
    //els
    //out.println("<BR><font color=red>long value is : "+strbyte+"</font>");
    try{
    tempClob = oracle.sql.CLOB.createTemporary(conn,true, oracle.sql.CLOB.DURATION_SESSION);
    out.println("<BR><font color=red>tempClob : "+tempClob);
    tempClob.open( oracle.sql.CLOB.MODE_READWRITE);
    java.io.Writer tempClobWriter = tempClob.getCharacterOutputStream();
    // writing the string formed from the multipart file to the clob
    tempClobWriter.write(strbyte);
    if(tempClob!=null){}
    out.println("<BR><font color=red>CLOB value is : "+tempClob+"</font>");
    strQuery="{call INSERT_CLOB(?,?)}";
    cmt=conn.prepareCall(strQuery);
    cmt.setString(1,strPassedFileName);
    cmt.setClob(2,tempClob);
    cmt.registerOutParameter(2,java.sql.Types.CLOB);
    cmt.execute();
    tempClobWriter.flush();
    tempClobWriter.close();
    tempClob.freeTemporary();
    //res.setContentType(strContent);
    //strDocString.toString();
    out.println("<BR><font color=red>bob is "+strbyte+"</font>");
    tempClob.close();
    }catch(Exception e){
    tempClob.close();
    out.println("<font color=blue> Error is :"+e.getMessage()+"</font>");
    //e.printStackTrace(out);
    cmt.close();
    //out.println("<BR><font color=red><h2><b>SUCCESS</h2></font>");
    //res.sendRedirect("../test/showfile.jsp?contentype="+strContent.trim()+"");
    }catch(Exception e){
    java.util.Date d = new java.util.Date();
    String s =d.toString();
    out.println("<font color=blue> Error is :"+e.getMessage()+"</font>");
    //e.printStackTrace(out);
    }finally{
    try{
    if(conn!=null)
    conn.close();
    }catch(Exception e){
    out.println("<font color=blue> Error is :"+e.getMessage()+"</font>");
    }// end of finally
    } //end of doPost
    } //end of class
    in the Procedure you will be inserting/updating the clob in a table with the reference clob in the out parameter of the procedure
    Thanks.

  • Problem with JDBC stored procedure

    Hi...
    We are implementing an interface from SAP r/3 4.7 to Oracle DB 9.0. On sender side we have used IDOC Adapter and on Receiver side we have used JDBC Adapter.
    Here we are using stored procedures in JDBC Adapter. I have 2 stored procedures(one for header and one for items) and SISCSO.SISCSO01 IDOC.
    Here we are getting following error in RWB for JDBC Receiver adapter....
    <b>Error</b>
    " Receiver Adapter v2112 for Party '', Service 'BS_ORADEV':
    Configured at 2006-08-16 10:12:14 GMT+05:30
    History:
    - 2006-08-16 11:02:04 GMT+05:30: Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. 'PR_SPARES_VOR_PO_HDR_UPLOAD' (structure 'statement'): java.sql.SQLException: ORA-06550: line 1, column 7:
    PLS-00201: identifier 'PR_SPARES_VOR_PO_HDR_UPLOAD' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored ".
    <b>My mapping file is like this.....</b>
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:TVS_MST_SPARES_ORDER xmlns:ns0="urn:tvsmotor:salesorder"><statement><PR_SPARES_VOR_PO_HDR_UPLOAD action="execute"><table>PR_SPARES_VOR_PO_HDR_UPLOAD</table><IN_DEALER_ID isInput="true" type="String">efde</IN_DEALER_ID><IN_SPARE_PO_NO isInput="TRUE" type="STRING">sdfsdf</IN_SPARE_PO_NO><IN_PO_DATE isInput="TRUE" type="STRING">12.12.2555</IN_PO_DATE><IN_ORDER_TYPE isInput="TRUE" type="STRING">23</IN_ORDER_TYPE><IN_REMARKS isInput="TRUE" type="STRING">Remark</IN_REMARKS><IN_SAP_SALE_ORD_NO isInput="TRUE" type="STRING">146546</IN_SAP_SALE_ORD_NO><IN_SAP_SALE_ORD_DT isInput="TRUE" type="STRING">12.12.2555</IN_SAP_SALE_ORD_DT><IN_TOT_VAL isInput="TRUE" type="STRING">2323</IN_TOT_VAL></PR_SPARES_VOR_PO_HDR_UPLOAD><PR_SPARES_VOR_PO_DTL_UPLOAD action="execute"><IN_DEALER_ID isInput="TRUE" type="STRING">efde</IN_DEALER_ID><IN_SPARE_PO_NO isInput="TRUE" type="STRING">sdfsdf</IN_SPARE_PO_NO><IN_PO_DATE isInput="TRUE" type="STRING">12.12.2555</IN_PO_DATE><IN_PART_NO isInput="TRUE" type="STRING">cfgdfw4w</IN_PART_NO><IN_ORDER_QTY isInput="TRUE" type="STRING">2</IN_ORDER_QTY><IN_PENDING_QTY isInput="TRUE" type="STRING">20</IN_PENDING_QTY><IN_RATE isInput="TRUE" type="STRING">2432</IN_RATE><IN_TAX isInput="TRUE" type="STRING">18</IN_TAX></PR_SPARES_VOR_PO_DTL_UPLOAD></statement></ns0:TVS_MST_SPARES_ORDER>
    Please help me out with this error... tell me if more information is required.
    Thanks,
    Audumbar.

    hi mario,
    tell me one thing.... does case metter for stored procedure name? and even for the parameters used in stored procedure?
    i have changed the case of stored procedure name... (its small in Oracle) but have not changed the case of parameters....
    after changing the case also i m getting the following error....
    " Receiver Adapter v2112 for Party '', Service 'BS_ORADEV':
    Configured at 2006-08-16 10:12:14 GMT+05:30
    History:
    - 2006-08-16 14:18:19 GMT+05:30: Error: TransformException error in xml processor class: Error processing request in sax parser: Error when executing statement for table/stored proc. <b>'pr_spares_vor_po_hdr_upload'</b> (structure 'statement'): java.sql.SQLException: ORA-06550: line 1, column 7:
    PLS-00201: identifier <b>'PR_SPARES_VOR_PO_HDR_UPLOAD'</b> must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored "
    Reply me as soon as possible.
    Thanx,
    Regards,
    Audumbar
    Message was edited by: Audumbar Pikle

  • Jdbc - stored procedures

    Please, can anyone show me how to retrieve an array from a stored procedure using JDBC?
    The code below are not working (the exception at bottom). The problem seem to be the third parameter to registerOutParameter, this type do however exist in the database.
    This error occurs also when I use OracleCallableStatement.
    Any help and tips is MUCH appreciated.
    Thanks!
    ++++++++++++++++++
    java.sql.Connection con;
    java.sql.CallableStatement cstmt = con.prepareCall("{call pck_test_array.get_company_array(?)}");
    cstmt.registerOutParameter(1,java.sql.Types.ARRAY, "pck_test_array.app_user_name_text_table");
    cstmt.execute();
    ++++++++++++++++++++++
    This generates the following exception:
    java.sql.SQLException: Fail to construct descriptor: Unable to resolve type: "pc
    k_test_array.app_user_name_text_table"
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
    at oracle.jdbc.dbaccess.DBError.check_error(DBError.java:775)
    at oracle.sql.ArrayDescriptor.<init>(ArrayDescriptor.java:166)
    at oracle.sql.ArrayDescriptor.createDescriptor(ArrayDescriptor.java:89)
    at oracle.jdbc.driver.OracleCallableStatement.registerOutParameter(Oracl
    eCallableStatement.java:162)

    Here is a sample from Metalink on how to
    fetch arrays from pl/sql
    Program Notes
    o This program can be run with any of the three forms of Oracle JDBC driver.
    o Run the script noted in the comments of the program to create the type
    and the procedure that is called.
    o This program uses the most basic method of calling objects,
    via Oracle.sql.STRUCT.
    References
    "Oracle8i JDBC Developers Guide and Reference" (A64685-01)
    Program
    import java.sql.*;
    import java.io.*;
    import java.util.*;
    import java.math.BigDecimal;
    import oracle.sql.*;
    import oracle.jdbc.driver.*;
    public class callInOutStructArray extends Object {
    This program demonstrates how to emulate calling a stored procedure
    with PL/SQL table of record parameters via JDBC. You cannot call a
    PL/SQL table of records parameter directly, however, you can use an
    Object with the same structure as your table of records.
    The Script used to create the procedure in this example is as follows:
    drop type rectab;
    create or replace type rectype as object(col1 varchar2(10),col2 varchar2(10));
    create or replace type rectab as table of rectype;
    create or replace package ioStructArray as
    procedure testproc(iorec in out rectab,orec out rectab);
    end ioStructArray;
    create or replace package body ioStructArray as
    procedure testproc(iorec in out rectab,orec out rectab) is
    begin
    orec := iorec;
    for i in 1..iorec.count loop
    iorec(i).col1 := orec(i).col2;
    iorec(i).col2 := orec(i).col1;
    end loop;
    end testproc;
    end ioStructArray;
    public static void main(String[] args) throws SQLException {
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    // Connect to the database
    Connection conn =
    DriverManager.getConnection ("jdbc:oracle:oci8:@S692815.WORLD",
    "scott", "tiger");
    // First, declare the Object arrays that will store the data.
    Object [] p1recobj = {"FIRST","LAST"};
    Object [] p2recobj = {"SECOND","LAST"};
    Object [] p3recobj;
    Object [] p4recobj;
    // Declare the Object Arrays to hold the STRUCTS.
    Object [] p1arrobj;
    Object [] p2arrobj;
    // Declare two descriptors, one for the ARRAY TYPE
    // and one for the OBJECT TYPE.
    StructDescriptor desc1=StructDescriptor.createDescriptor("RECTYPE",conn);
    ArrayDescriptor desc2=ArrayDescriptor.createDescriptor("RECTAB",conn);
    // Create the STRUCT objects to associate the host objects
    // with the database records.
    STRUCT p1struct = new STRUCT(desc1,conn,p1recobj);
    STRUCT p2struct = new STRUCT(desc1,conn,p2recobj);
    // Initialize the Input array object - to an array of STRUCT Objects.
    p1arrobj = new Object []{p1struct,p2struct};
    // Set up the ARRAY object.
    ARRAY p1arr = new ARRAY(desc2,conn,p1arrobj);
    ARRAY p2arr;
    // Declare the callable statement.
    // This must be of type OracleCallableStatement.
    OracleCallableStatement ocs =
    (OracleCallableStatement)conn.prepareCall("{call iostructarray.testproc(?,?)}");
    // The first parameter is in out so we have to use setARRAY to
    // pass it to the statement
    ocs.setARRAY(1,p1arr);
    // The first parameter is in out, so we have to Register the
    // parameter as well.
    // Note the re use of the TYPE.
    ocs.registerOutParameter(1,OracleTypes.ARRAY,"RECTAB");
    // The second paramter is out, so that has to be registered too.
    // Note the re use of the TYPE.
    ocs.registerOutParameter(2,OracleTypes.ARRAY,"RECTAB");
    // Execute the procedure
    ocs.execute();
    // Associate the returned arrays with the ARRAY objects.
    p1arr = ocs.getARRAY(1);
    p2arr = ocs.getARRAY(2);
    // Get the data back into the data arrays.
    p1arrobj = (Object [])p1arr.getArray();
    p2arrobj = (Object [])p2arr.getArray();
    // Get the data records from each array element (which is of type STRUCT).
    p1recobj = ((STRUCT)p1arrobj[0]).getAttributes();
    p2recobj = ((STRUCT)p1arrobj[1]).getAttributes();
    p3recobj = ((STRUCT)p2arrobj[0]).getAttributes();
    p4recobj = ((STRUCT)p2arrobj[1]).getAttributes();
    // Show the results:
    System.out.println("First Object is now "+p1recobj[0]+" and "+p1recobj[1]);
    System.out.println(" "+p2recobj[0]+" and "+p2recobj[1]);
    System.out.println("Second Object is now "+p3recobj[0]+" and "+p3recobj[1]);
    System.out.println(" "+p4recobj[0]+" and "+p4recobj[1]);
    Sample Output
    First Object is now LAST and FIRST
    LAST and SECOND
    Second Object is now FIRST and LAST
    SECOND and LAST
    Copyright (c) 1995,1999 Oracle Corporation. All Rights Reserved. Legal Notices and Terms of Use.
    null

  • File to JDBC stored procedure

    Hi JDBC gurus,
    I am using the File-XI-JDBC interface in which I am calling a Oracle stored procedure. The parameters I have to send to this SP has one parameter which is a RECORD.
    The input fields which I receive from the File should be send as ONE SINGLE PARAMETER in the stored procedure.
    Is there a way that we can send all these incoming fields into single parameter in the stored procedure?
    Please help.
    Thanks
    Kalyan

    Hi Kalyan,
    You can use XSLT mapping with following function.
    The <xsl:copy-of> element creates a copy of the current node.
    Note: Namespace nodes, child nodes, and attributes of the current node are automatically copied as well!
    Tip: This element can be used to insert multiple copies of the same node into different places in the output.
    Hope it helps,
    Regards,
    Tuhin
    *Please mark useful answers.

  • JDBC stored procedure / java.lang.IllegalArgumentException

    Hi,
    I have created a JDBC adapter to access for a Oracle DB and the connection works successfully. I have tested the posting into the DB via xml-format and it works also fine.
    Accordingly i added a stored procedure (SP) into the xml-format and i get following error in the communication channel (in Pi monitoring the message is fine - no error):
    com.sap.aii.af.ra.ms.api.RecoverableException: Error processing request
    in sax parser: Error when executing statement for table/stored proc.
    'em_end_load' (structure 'STATEMENT_StoreProcedure'):
    java.lang.IllegalArgumentException
    SP in DB:
    PROCEDURE em_end_load
        p_1                      IN  VARCHAR2,
        p_2                      IN  VARCHAR2    DEFAULT NULL,
        p_3                      IN  NUMBER,
        p_4                      IN  VARCHAR2    DEFAULT NULL,
        p_time                      IN  DATE        DEFAULT NULL
    AS
    I'm not sure if i have to use an output parameter, because in the description of the SP i read following:
    USAGE
         To compile from the SQL*Plus prompt:
         SQL> start [folder spec]/sp_em_end_load.pls
         To run from the SQL*Plus prompt:
         SQL> exec em_em_end_load
    PARAMETERS
         INPUT
            p_1
            p_2
            p_3
            p_4
          p_5
          p_6
         OUTPUT
            p_error_msg
    I have created in PI the data type for SP as follow:
                             value
    MT_JDBC
      STATEMENT_SP          0..1
         action          required     EXECUTE
         table          0..1          em_end_load
         p_1          1..1          010
           type          optional     VARCHAR
         p2               1..1          main
           type          optional     VARCHAR
         p3               1..1          100
           type          optional     VARCHAR
         p4               1..1          load
           type          optional     VARCHAR
         p5               1..1          26.04.2010
           type          optional     DATE
         p_error_msg     0..1          
           isInput          optional     1
           type          otpional     VARCHAR
    What is wrong with the processing of this SP? Could anyone help me?
    Regards,
    Lutz

    Sorry the explanation of the data type was a little bit misunderstanding:
    data type in PI:
    MT_JDBC
    -STATEMENT_SP           0..1
    --action                required        EXECUTE
    --table                 0..1            em_end_load
    --p_1                   1..1            010
    ---type                 optional        VARCHAR
    --p_2                   1..1            main
    ---type                 optional        VARCHAR
    --p_3                   1..1            100
    ---type                 optional        VARCHAR
    --p_4                   1..1            load
    ---type                 optional        VARCHAR
    --p_time                1..1            26.04.2010
    ---type                 optional        DATE
    --p_error_msg           0..1
    ---isInput              optional        1
    ---type                 optional        VARCHAR
    ...but the names of the parameters are identical - that i have checked several times.

  • SAP PI JDBC Stored Procedure Call

    Dear All,
    I have a requirement, where i have to call a stored procedure through reciever JDBC adapter by providing multiple records at a time as input to the stored procedure, and also recieve multiple records at a time.
    Can any one tell me, how the structure of data type should be, to provide multiple input to the stored procedure.
    Please reply soon.
    Thanks in Advance.
    Regards,
    Zafar Ali

    For stored procedure the data type should be designed as mentioned in documentaion for JDBC formats-
    http://help.sap.com/saphelp_nw70/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    Make the occurance of Statement tag as 0..unbounded to send multiple records in a single message.But each record will inturn call stored procedure.
    Sending multiple records in a single call seems to have restrictions-
    Inserting multiple rows into DB via SQL insert or stored procedure?

  • Problems storing CLOBs with build-in Oracle 8.1.6 thin driver of WebLogic 6.0 SP2

    Hi,
    I'm using the build-in Oracle 8.1.6 thin driver that comes with
    weblogic.jar of WebLogic 6.0 SP2. It doesn't store CLOBs. Here I have
    to use the class weblogic.jdbc.common.OracleClob. Why?
    WebLogic 5.1 SP 9 + Oracle 8.1.6 thin driver (external) does. Here I
    use the class oracle.sql.CLOB.
    Must I use a OCI driver?
    Thanks,
    Juergen

    I'd also recommend to switch to 8.1.7 thin driver. It's more stable.
    Regards,
    Slava Imeshev
    "NhaBep" <[email protected]> wrote in message
    news:3b71bbcf$[email protected]..
    >
    You can use thin driver to persist CLOB. One thing you must be sure to setautocommit
    to false. Hope this help.
    [email protected] (Juergen) wrote:
    Hi,
    I'm using the build-in Oracle 8.1.6 thin driver that comes with
    weblogic.jar of WebLogic 6.0 SP2. It doesn't store CLOBs. Here I have
    to use the class weblogic.jdbc.common.OracleClob. Why?
    WebLogic 5.1 SP 9 + Oracle 8.1.6 thin driver (external) does. Here I
    use the class oracle.sql.CLOB.
    Must I use a OCI driver?
    Thanks,
    Juergen

  • Testing JDBC - Stored Procedure

    Hi,
    We're working on creating a new JDBC in weblogic server 11g. The data source is created and we have a business service, which was built based on a jca built in JDeveloper. When testing the connection between the server and the db, it seems to be working as expected, but when the business service is executed, which is supposed to executed a stored procedure in the db, nothing is returned even though it should.
    Is there any way to verify whether the business service is executing the stored procedure or not?

    Can you do any of these:
    1 - turn on WebLogic debugging for JDBCSQL, to log all/most JDBC Calls.
    2 - edit the procedure in the DBMS to verify/log when it is called, whether
    it does anything else or not?
    3 - turn on DBMS tracing to log what clients are doing?
    4 - set up/turn on the driver debug logging?
    Depending on the WebLogic version and driver version these may
    be done in different ways, and the instructions are not appropriate
    to all copy here, so I would open a support SR to get help if/as you need it.

  • 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.

Maybe you are looking for