JDBC Sender Error: Incorrect Pollin Interval

Hi,
I have a problem with my JDBC Sender. It used to work perfectly. Then, it got an error. After that, I tried to re-start the CC in RWB. Here is the result in RWB after i restart.
http://www.imagecross.com/02/image-hosting-view-03.php?id=4564sample1.png
The time is incorrect. I set polling interval in my ID as 5 seconds and retry interval as 10 seconds but in RWB it shows that polling interval is 12 seconds which I don't know where it comes from. Moreover, in RWB my CC show only message "Processing started" which is different from the time it worked that it also has a message showing interval time like this http://www.imagecross.com/02/image-hosting-view-03.php?id=5434sample2.png
Besides, No data in my database can be retrieved by SAP XI.
Have anyone experience this before? Any suggestion please?
Thanks,
Pavin

Hi
Once Deactivate and again Activate your CC.
Check your generated SQL query format is correct
At runtime you can find the genereated sql statements by doing configuraitons in Receiver JDBC adapter.
In the JDBC Receiver adapter you have the Advanced Properties .
Over there enter the following
left column logSQLStatement
right column true
To see the query created ..
Login to adapter monitoring ..select the relevant jdbc adapter.
Now when any message is processed by the jdbc adapter in adapter monitoring at that time you will see a message link. When you click on that link a new window will open. In that window if you click on page down you will get to see the sql statement generated by the jdbc adapter.

Similar Messages

  • Avoid JDBC sender error: Execute statement did not return a result set

    Hi!
    My JDBC sender adapter towards MS SQL server works fine, with an Execute statement calling a stored procedure that returns the source data needed. The stored procedure itself updates the status of database table records, so that only the unread records are returned each time the stored procedure is called.
    However, the communication channel monitoring sets a red flag for the JDBC sender adapter, when there are no values to fetch from the database table (using the stored procedure). Message says: "Database-level error reported by JDBC driver while executing statement 'EXECUTE FetchMessage 1, 9000'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: The statement did not return a result set.'. For details, contact your database server vendor."
    This is not an error situation, as I do not expect there to be any values to fetch from the database at all times.
    I do not see how to change the stored procedure to avoid this error.
    Is there a parameter to be set on the JDBC adapter that I can use, so the red flag is avoided?
    Thanks for any input!
    Regards,
    Oeystein Emhjellen

    Hi Oeystein Emhjellen.
    The problem is Store Procedure that has to generate always a ResultSet (or cursor). If it doesn't have a output, you have to generate an Empty ResultSet.
    Like a SELECT Statement:
    If there are data, SELECT get an output result but if it get nothing the SELECT Statement get a empty ResultSet.
    Ask to your database team.
    I hope it helps you.
    Bruno.

  • JDBC Sender Error

    Hi,
    We have a JDBC Sender adapter configured to pull data from the SQL database. This pulls data for every one hour.
    Some times we are getting the below error on the communication channel -
    Database-level error reported by JDBC driver while executing statement 'select * from HR_ExitEvents'. The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: An exception occurred during the DBComms.receive method. Operation:Connection reset. Context:(12) [XI JDBC2XI[CC_JDBC_out_HRExitEvents/EMSSQLServer2005/]_15550, IO:a82f3, Dbc:9b28b]. PktNum:0. TotalReceived:0. PktSize:4,096.'. For details, contact your database server vendor.
    Please help.

    Hi Sudeer
    This is a general error message that is raised whenever the SQL server forcibly closes the TCP/IP connection for any of a number of reasons while the driver is waiting for a response to a query.
    This error indicates that the connection with the server has been reset for some reason. The actual cause of the failure could be anything from network (hardware) issues to a problem in either SQL Server or the JDBC driver or any software in between like firewall
    Thanks
    Abhishek

  • JDBC Sender Error "RuntimeException in Message-Mapping transformation"

    Hi All,
    I have JDBC as sender and i am able to poll the data from the database,which is available in SXMB_MONI but its giving an error "RuntimeException in Message-Mapping transformation".I have tested the mapping in TEST and its working fine but when i tested the same in configuration its throwing an error in Interface mapping(<NOT FOUND>).
    I have also created a node <b>row</b> in my sender data type.
    Expecting your help soon.
    Thanks and regards,
    Zabi.

    Hi,
    Check the data  coming  inside..the XI... that is before mapping..
    Regards
    Agasthuri Doss

  • Receiver JDBC Channel Error : Incorrect syntax near 'OR'

    hi,
    we are facing the below error at the receiver communication channel:
    Error while parsing or executing XML-SQL document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'table' (structure 'statement'): com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 'OR'.
    When we again reprocess the message,it shows the exact error at the channel.
    Any ideas why the first error shows up?

    Hi, Anu
    The most probable it's that your target XML it's not correct because it haven't a correct format.
    Please, check your target XML and see
    http://help.sap.com/saphelp_nwpi711/helpdata/en/48/465581929734d9e10000000a42189d/frameset.htm
    Regards,
    Carme

  • JDBC Sender Adapter -  NOT FETCHING RECORDS -PROCESSING STARTED

    Hello all,
    I have set up a JDBC sender adapter .With polling interval as 30 Seconds. Polling is done successfully
    but it does not fetch the records .
    Valid Data is present in the tables.In the Communication Channel Monitoring log shows :
    "Processing Started"
    after each poll interval.
    Adding to this , it was working fine  with the same parameters two days back.
    I have enabled the Driver Trace but didnot get any information from Trace.
    How to resolve this issue?Any help
    Regards
    Ganga Prasad

    Hello maheshwari,
    Valid Data is there & many records are there to be fetched.
    One more thing  Normally in the Communication Channel Monitoring
    for an JDBC adapter even if there are no records to fetch we get the Log information in detail that :
    Polling interval started.
    Processing finished successfully
    Processing started
    Polling interval started.
    Processing finished successfully
    Processing started
    But here in my case am getting only : (polling interval : is 60 Seconds)
            2/5/08 8:29:19 AM           Processing started
         2/5/08 8:28:19 AM           Processing started
         2/4/08 3:34:54 PM           Processing started
         2/4/08 3:33:54 PM           Processing started
    One more observation is that my poll interval is 60 seconds but now it is polling after every 120sec
           2/5/08 11:17:31 AM           Processing started
         2/5/08 11:15:31 AM           Processing started
         2/5/08 11:13:31 AM           Processing started
         2/5/08 11:11:31 AM           Processing started
    I have tried refreshing Cache but no change .
    Regards
    Prasad

  • JDBC sender adapter outofmemory error

    Dear friends,
    We are getting following error on JDBC sender Adapter: Error during conversion of query result to XML: java.lang.OutOfMemoryError: Java heap space (failed to allocate 1073741848 bytes)
    I have read blogs where there have been suggestions to limit the amount of data picked by using WHERE condition and not using SELECT *
    In our scenario we are creating GL IDOCs . In SQL when PI picks it up it needs to get all the corresponding Header and line items together. We cannot randomly pick 1000 records at a time. The SQL table has 500,000 rows in the following format
    H H H  L1 L1 L1
    H H H L2 L2 L2
    H H H  L3 L3 L3
    H1 H1 H1 L1 L1 L1
    H1 H1 H1 L2 L2 L2
    H1 H1 H1 L3 L3 L3
    Please let me know how can we solve this issue?
    Thank you,
    Teresa
    Edited by: Teresa lytle on Sep 27, 2011 3:13 PM

    If you are using oracle database, uses ROWNUM field to fetch first set of records and you can update those records with the flag as true.
    similarly If you are using MS SQL database, uses SELECT TOP command to fetch first set of records and you can update those records with the flag as true.
    Like File/FTP adapter, the next poll interval would be as scheduled. The Administrator can then alter the table contents, to ensure lesser no of records are picked up.
    Here You need to limit the no of rows if you again face the problem. Please chec the SAP Note
    https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1296819

  • JDBC Sender Adapter Error

    HI Friends,
    I have configured the JDBC Sender Adapter with parameters as
    Driver : oracle.jdbc.driver.OracleDriver
    Connection : jdbc:oracle:thin:system:netweaver:@172.25.4.221:1521
    But Iam getting an error in Componenet Monitoring:
    <b>History:
    - 2006-05-30 04:55:36 UTC: Error: Stopped unexpectedly - reconfigure and activate to continue processing. Error: java.lang.NullPointerException
    - 2006-05-30 04:55:36 UTC: Processing started</b>
    How to resolve this??
    Regards,
    Raju

    Hi
    Thanks for the reply.
    I tried with <b>jdbc:oracle:thin:@172.25.4.221:1521:netweaver</b> and
    <b>jdbc:oracle:thin:@172.25.4.221:1521:system</b>
    Now Iam getting another error.
    <b>Sender Adapter v2108 for Party '', Service 'TBIT40_XI_LEGACY_BS_04':
    Configured at 2006-05-30 05:12:30 UTC
    History:
    - 2006-05-30 05:13:00 UTC: Retry interval started. Length: 20.000 s
    - 2006-05-30 05:13:00 UTC: Error: Accessing database connection 'jdbc:oracle:thin:@172.25.4.221:1521:system' failed: DriverManagerException: Cannot establish connection to URL 'jdbc:oracle:thin:@172.25.4.221:1521:system': SQLException: Io exception: Connection refused(DESCRIPTION=(TMP=)(VSNNUM=153093376)(ERR=12505)(ERROR_STACK=(ERROR=(CODE=12505)(EMFI=4))))
    - 2006-05-30 05:13:00 UTC: Processing started</b>
    Can U please solve it..
    regards,
    Raju

  • JDBC Sender Polling Interval

    Hi All,
    What is the maximum limit of the poll interval to be specified in JDBC sender.
    We had faced some problem when we give a 9 or 10 digit polling interval.
    But when we give something near to 6 7 digits, its working fine
    Any such practical situations handled by any1?
    Thanks,
    Greg

    Hi Greg,
    give a small number (minute or so) and schedule the adapter via RWB
    to start it once a day or once a week
    /people/shabarish.vijayakumar/blog/2006/11/26/adapter-scheduling--hail-sp-19-
    this approach will have much better performance
    Regards,
    michal

  • JDBC Sender Conversion error

    Hi
    My Scenario is JDBC Sender-> XI ->IDOC.
    I have written a following select querry and update but I am getting and error from sender...
    select *  from bi5filmm.bsimhp
    UPDATE  HMPRCFG SET  VALUE =  'P' from  bi5filmm.bsimhp
    Error during conversion of query result to XML: java.lang.IllegalArgumentException: Unsupported date format!
    Please help....
    Regards
    Ria

    Hi VJ,
    Data looks like this......
    State  Market  Channel  Corp   Channel                Week        Product           Article      Outlet   Delivery
    Code   Code    Code     Group  ID                     Ending                                     Name     Loc  
                            Code                                                                               
    NSW     A        C      AC    05NSW                  2007-12-21  0026                   26   2,320,736     NP 
    NSW     A        C      AC    05NSW                  2007-12-21  0026                   26   2,312,091     NP 
    NSW     A        C      AC    05NSW                  2007-12-21  0026                   26   2,503,996     NU 
    NSW     A        C      AC    05NSW                  2007-12-21  0026                   26   2,287,125     NY 
    NSW     A        C      AC    05NSW                  2007-12-21  0026                   26   2,696,852     QF 
    NSW     A        C      AC    05NSW                  2008-01-04  0026                   26   2,280,281     NL 
    NSW     A        C      AC    05NSW                  2008-01-04  0026                   26   2,290,131     NN 
    NSW     A        C      AC    05NSW                  2008-01-11  0026                   26   2,172,753     NA 
    NSW     A        C      AC    05NSW                  2008-01-11  0026                   26   2,189,592     NA 
    NSW     A        C      AC    05NSW                  2008-01-11  0026                   26   2,180,110     NA 
    NSW     A        C      AC    05NSW                  2008-01-11  0026                   26   2,165,458     NA 
    NSW     A        C      AC    05NSW                  2008-01-11  0026                   26   2,277,061     NI 
    Deliv   Load       Deliv   MNEPRCSTA  Delivery    Checkout    Checkout   Load    PRMS       
        Date    No         Date               Date        Date        Time       Origin  UserID     
        Act                                                                               
    1,071,218   BL202  1,071,218      INF     2007-12-18  2007-12-17    55,109      1    71218BL202 
    1,071,219   DU303  1,071,219      INF     2007-12-19  2007-12-18    55,908      1    71219DU303 
    1,071,219   BCSN2  1,071,219      INF     2007-12-19  2007-12-18    55,919      1    71219BCSN2 
    1,071,218   WA202  1,071,218      INF     2007-12-18  2007-12-17    55,103      1    71218WA202 
    1,071,218   Q2002  1,071,218      INF     2007-12-18  2007-12-17    55,056      1    71218Q2002 
    1,080,103   TSD30  1,080,103      INF     2008-01-03  2008-01-02    63,235      1    80103TSD30 
    1,080,103   P3001  1,080,103      INF     2008-01-03  2008-01-02    63,236      1    80103P3001 
    1,080,109   R4301  1,080,109      INF     2008-01-09  2008-01-08    60,422      1    80109R4301 
    1,080,109   R4301  1,080,109      INF     2008-01-09  2008-01-08    60,422      1    80109R4301 
    1,080,109   R4302  1,080,109      INF     2008-01-09  2008-01-08    60,422      1    80109R4302 
    1,080,110   R5412  1,080,110      INF     2008-01-10  2008-01-09    63,601      1    80110R5412 
    1,080,108   N2002  1,080,108      INF     2008-01-08  2008-01-07    60,712      1    80108N2002
    Checkout              CheckIn   Create       Create   Week     Proc           Proc   Proc
    Qty                   Qty       Date         Time     Period   Date           Time   Flag
                                                                                    1.0000                .0000   2007-12-17  224,850            2008-12-16        0      
      1.0000                .0000   2007-12-18  205,817            2008-12-16        0      
      1.0000                .0000   2007-12-18  205,817            2008-12-16        0      
      2.0000                .0000   2007-12-17  224,850            2008-12-16        0      
      1.0000                .0000   2007-12-17  224,850            2008-12-16        0      
      1.0000                .0000   2008-01-02  211,104            2008-12-16        0      
      1.0000                .0000   2008-01-02  211,104            2008-12-16        0      
      1.0000                .0000   2008-01-08  212,952            2008-12-16        0      
      1.0000                .0000   2008-01-08  212,952            2008-12-16        0      
      1.0000                .0000   2008-01-08  212,952            2008-12-16        0      
      1.0000                .0000   2008-01-09  211,624            2008-12-16        0      
      1.0000                .0000   2008-01-07  214,424            2008-12-16        0
    Regards
    Hema

  • JDBC Sender Channel polling before polling interval is complete

    Hi all,
    On our Production Server, we have found that a few JDBC Sender Channels are polling multiple times within one polling interval.
    Eg: Suppose for one channel, the polling interval is 7200 secs. It polls once and the polling interval starts. But it polls again 1 or 2 times more maybe just 5 secs later before its next scheduled poll in 7200 secs.
    Unfortunately, our scenarios are such that when there are multiple polls within a short span of time, there are data anomolies, causing inconsistancies on Receiver side DB. Hence this is a serious uissue.
    Please Help. FYI, all the affected channels run on the same schedule. I am not sure if that can be causing this abnormality.

    H Varun
    I have not come across this behavior earlier. But if you are polling same data base using multiple channel at same time data inconsistency can be there. We always prefer to poll the same data base tables with different timings. Setting up poll timings always consider peak loads. Try to change the polls and see if the same behavior exists.
    For performance and JDBC issues
    Check https://service.sap.com/sap/support/notes/831162
    Specially Q 14
    Thanks
    Gaurav

  • JDBC Sender adapter - Oracle - Stored Procedure - Error

    Hello,
    Need few clarifications on JDBC sender adapter and stored procedures when connecting to Oracle DB.
    My scenario is, Oracle to SAPBW. So in sender JDBC adapter, we have used a SP having multiple SQL statements it, esp. one of the SELECT statment having Joins on a table and View.
    My questions are,
    1) Is it possible to have more SQL statements in SP for Sender JDBC?
    2) Is the SP of Oracle DB returns resultset or cursor?
    I have tried in searching the forum perticularly for connecting to Oracle as Sender and below like said  that there is a limitation of XI JDBC when connecting to Oracle.
    Executing an Oracle Stored Procedure from Sender JDBC adapter
    So please clarify the doubts and help me.
    With regards,
    Jilan

    Hi Jilan,
    Unlike what was mentioned in the link given by you that oracle returns cursor and not resultset is not completely true. It may be difficult but certainly not impossible.
    Refer : http://www.enterprisedt.com/publications/oracle/result_set.html
    regards
    joel

  • JDBC Sender - ORA-08177 on UPDATE, but Table is updated - no message

    Hi,
    I have a problem with JDBC Adapter:
    I use a JDBC Sender adapter, polling every minute on an Oracle DB.
    I use isolation level "serializable".
    No what happens sometimes is, that the update statement fails because of "ORA-08177: can't serialize access for this transaction", so no message is forwarded to the IS. Curiously, the entries in the table are updated, so the JDBC Driver seems to update the data anyways.
    Has anybody experience with similar problems? This is a really hard issue because no messages are transmitted althought the condition field in the table is updated and everything seems normal. Also the status light of the communication channel will be green again after a while, so it is really hard to trace.
    System:
    XI 3.0 SP20
    ORACLE 8.1.7.4
    I use the following statements with a rownum limit:
    select ... from TABLE where CONDITION = '_to_send' AND rownum <= 20 order by NACHRICHT_ID
    update TABLE set CONDITION = '_sending' where PRIMARY_KEY in (select PRIMARY_KEY from TABLE where CONDITION = '_to_send' and rownum <= 20)
    (just to complete the picture...)
    This message goes to BPM, where it is split into single messages. These messages are processed separately, and after an successfull processing an update statement is sent back to the DB:
    update TABLE set CONDITION = '_processed' where PRIMARY_KEY = <PK of processed message>
    So the condition "_sending" is an interim status for the messages sent to BPM, but not finally processed.
    What happens is, that the receiver of the messages complained about missing messages. I could find some messages in the interim status, but no message has ever been sent.
    I appreciate any help.
    Thank you very much.

    Sainath Chutke wrote:
    As you have used the Isolation level as serialiable whenever the transaction fails the data gets updated because once the transaction reaches the end of the adapter level processing " the update statemnets gets executed " Irrespective of whether the transaction is sucessful or failure."
    Curiously, the select statement does not throw the error, the update statement does. But even though the update statement does not work (ORA-08177), it works (rows in DB are updated). That is what causes headache to me.
    Try to change the Isolation level and get the message id generated using an UDF.´
    Sorry, but I do not completely understand what you suggest here.
    My needs are:
    - select rows that fulfill condition (limit to a max number per poll interval)
    - update the selected rows to not fulfill the condition any more (to not double sent data)
    - the update statement must update exactly the same rows that have been selected before (transaction)
    or in other words:
    I need to make sure the data is sent only once and exactly once.
    If your idea can satisfy these needs, I kindly ask you to explain it more detailed.
    Thank you very much.

  • JDBC Sender Adapter : java.sql.SQLException: Cursor state not valid.

    Hello all,
    We have configured JDBC Sender Adapter which fetches around 10K records with poll interval 1hr  from DB2 System .
    It was working fine,suddenly it started throwing an exception in Adapter Monitoring :
    Error during conversion of query result to XML: java.sql.SQLException: Cursor state not valid.
    It is not fetching any records.
    Without changing any configurations when we tried to fetch to around 1000 records it's working fine.
    For 10K records same exception persists
    What could be the reason ?How to resolve this issue?
    regards
    GangaPrasad

    Hello Christophe ,
    Trace in VA :::
    Date : 05/09/2008
    Time : 11:45:57:750
    Message : Unexpected error converting database resultset to XML, reason: java.sql.SQLException: Cursor state not valid.
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.sql.SQLException.<init>(SQLException.java:40)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
         at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
         at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
         at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:309)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
         at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
         at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
         at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
    Severity : Error
    Category : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
    Location : com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(ResultSet, ResultSetMetaData)
    Application :
    Thread : XI JDBC2XI[JDBC_SND_DB2_VehicleReceiving/DB2PRD00/]_170
    Datasource : 12428950:/usr/sap/PXI/DVEBMGS01/j2ee/cluster/server0/log/applications/com.sap.xi/xi.log
    Message ID : 00145E742794005E0014980B000000BE00044CC763766C4F
    Source Name : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
    Argument Objs : java.sql.SQLException: Cursor state not valid.
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.sql.SQLException.<init>(SQLException.java:40)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
         at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
         at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
         at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:309)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
         at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
         at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
         at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
    Arguments : java.sql.SQLException: Cursor state not valid.
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.sql.SQLException.<init>(SQLException.java:40)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:389)
         at com.ibm.as400.access.JDError.throwSQLException(JDError.java:366)
         at com.ibm.as400.access.AS400JDBCResultSet.getValue(AS400JDBCResultSet.java:3580)
         at com.ibm.as400.access.AS400JDBCResultSet.getString(AS400JDBCResultSet.java:3223)
         at sun.reflect.GeneratedMethodAccessor459222074.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:309)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.TraceInvocationHandler.invoke(TraceInvocationHandler.java:45)
         at com.sap.aii.adapter.jdbc.sql.jdbctrace.$Proxy254.getString(Unknown Source)
         at com.sap.aii.adapter.jdbc.JDBC2XI.convert2XML(JDBC2XI.java:954)
         at com.sap.aii.adapter.jdbc.JDBC2XI.invoke(JDBC2XI.java:492)
         at com.sap.aii.af.service.scheduler.JobBroker$Worker.run(JobBroker.java:475)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:99)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:119)
    Dsr Component :
    Dsr Transaction : d1f629d01d9b11dd984200145e742794
    Dsr User :
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : com.sap.aii.adapter.jdbc.JDBC2XI
    Resource Bundlename :
    Session : 0
    Source : /Applications/ExchangeInfrastructure/AdapterFramework/Services/ADAPTER/ADMIN/JDBC
    ThreadObject : XI JDBC2XI[JDBC_SND_DB2_VehicleReceiving/DB2PRD00/]_170
    Transaction : SAP J2EE Engine JTA Transaction : [0ffffffbdffffffa6ffffff960086]
    User : J2EE_GUEST
    Regards
    Ganga Prasad

  • Require Configuration Details regarding JDBC Sender Adapter Parameters

    Hi All,
    I have a scenario in which I need to read around 2 million records from an SQL Server table and process.
    Since the data content is very huge, I have decided to split the data and execute.
    So, in the select statement of my SQL Server Query, I used Select top(2000) from table name with my where condition.
    In the update statenment, I used update tablename set my required values from (my select query written above).
    QOS -> EOIO
    I have given the queuename as my tablename
    Poll Interval is "120" seconds.
    My idea is to process 2000 records at a time.
    When I am executing this interface through RWB, I am getting an error in update statement saying
    The JDBC driver returned the following error message: 'com.microsoft.sqlserver.jdbc.SQLServerException: Unable to start a nested transaction for OLE DB provider "SQLNCLI" for linked server (serverdetails). A nested transaction was required because the XACT_ABORT option was set to OFF.'. For details, contact your database server vendor."
    I have also tried in advanced tab the name of the variable as XACT_ABORT and its value as "ON", but to no avail.
    Please let me know if I have missed anything. Do I need to set any additional parameters in the advanced tab of JDBC sender communication channel?
    Any help is highly appreciated.
    Regards
    Kiran.

    HI Kiran
    Fist of all suggestion is to increase the polling time. It may not process 2000 records in 120 second and you will poll again.
    Paste your query to check if there is a problem
    Also do check with SAP Note 831162 to verify if there is something you are doing wrong.
    Thanks
    Gaurav

Maybe you are looking for