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

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

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 row 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

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:
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
How to resolve this??
Regards,
Raju

Hi
Thanks for the reply.
I tried with jdbc:oracle:thin:@172.25.4.221:1521:netweaver and
jdbc:oracle:thin:@172.25.4.221:1521:system
Now Iam getting another error.
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
Can U please solve it..
regards,
Raju

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

Error in adapterlog: JDBC connection error

Hi Experts,
I am getting this error during database connection to the database URL 'jdbc:sqlserver:// <servername>:1433;database=HRBD' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://<servername>:1433;database=HRBD': com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection timed out'
I am able to connect this server from Microsoft SQL Server2005(Which does not require the port number) but when I am trying to connect from PI JDBC sender adapter ,I am getting this error.
It is a SQL Server.JDBC driver seems ok(com.microsoft.sqlserver.jdbc.SQLServerDriver) because I connected the Staging database server from PI but unable to connect to this production database.
After starting the channel ,after 5-7 minutes I am getting this error.
Need your help on urgent basis!!
regards
Anupam

Anupam Ghosh wrote:
Hi Navin,
>
> I made a telnet test from putty giving the server name and port number and it showed me the "connection timed out".
> But I made telnet test to other database which resulted in successful connection.
> So is it a firewall issue with that particular databse?
> In that case only network team of that databse can handle this issue?
>
> Thanks,
> Jaydeep
Few things that mght help u
1. Check the port no for the DB that is getting timed out. .check
2. Disable the firewall. and check
3. Consult the N/w and the DB team.. .telling clearly the issue
Good Luck
XA

JDBC send data to oracle, oracle only accept column name in Upper case

Hi experts,
I am doing a scenario File --> XI --> JDBC, JDBC send data to a Oracle 10g database, I have configured JDBC receiver to use XML-SQL format. in oracle database , table "EMPLOYEE" has a column "NAME", but when I send data to oracle using JDBC receiver, the column is "name", then XI complains
" 'EMPLOYEE' (structure 'insert'): java.sql.SQLException: FATAL ERROR: Column 'name' does not exist in table 'EMPLOYEE'.
can anyone help me to let oracle accpet column "name". I can't change colum in JDBC receiver from "name" to "NAME".
Thanks a lot.

can anyone help me to let oracle accpet column "name"
Making Oracle case insensitive is not possible (in my opinion). By default all object names are stored in UPPER case in the rdbms dictionary.
When XI searches for column name in Oracle, this search is case sensitive. So u have to configure accordingly.
Regards,
Prateek

JDBC Sender Adapter - No Namespace found

Hello
I am currently using PI 7.1. The scenario is JDBC to ECC ABAP Client Proxy. When the JDBC Sender Adapter sends the data to the Integration Server, the root element does not contain the xmlns attribute. This root element is constructed from the Document Name of the JDBC Sender Adapter attribute.
I am getting the following error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_HIS_Material_Consumption_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_Material_</SAP:P3>
<SAP:P4>Consumption_ECC/Material. Values missing in queue~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_HIS_Material_Consumption_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_Material_Consumption_ECC/Material. Values missing in queue~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I perform a test at RWB, the message gets posted successfully. Once posted, the payload of this message contains the xmlns attribute.
Here is the root element from both the instances:
From RWB: <ns0:MT_Material_Consumption_JDBC xmlns:ns0="http://xxx.com/xxx/finance">
From JDBC Adapter: <ns0:MT_Material_Consumption_JDBC>
Could you please let me know, what has to be done to obtain the xmlns in the sender payload?
Thank you in advance.
John Jeyaraj
Edited by: John jeyaraj on Apr 7, 2011 8:22 AM

Hi Hiren
When I test the MM without the xmlns attribute, I get the following error:
The prefix "ns0" for element "ns0:MT_Material_Consumption_JDBC" is not bound.
When I add the xmlns attribute, the mapping is successful.
Thanks
John

JDBC Sender Adapter

Hi everybody
I have the following error in my JDBC to JDBC scenario; I configured the JDBC sender adapter and receive the following message back. In the Configuration I set Document Name to MT_ScanningStatus:
<?xml version="1.0" encoding="utf-8" ?>
<MT_ScanningStatus>
<row>
<ScannerNb>1</ScannerNb>
<Status>0</Status>
</row>
<row>
<ScannerNb>2</ScannerNb>
<Status>2</Status>
</row>
<row>
<ScannerNb>3</ScannerNb>
<Status>0</Status>
</row>
<row>
<ScannerNb>4</ScannerNb>
<Status>2</Status>
</row>
</MT_ScanningStatus>
I defined the corresponding datatype as follow:
DT_ScanningStatus Complex Type
 row Element 1...unbounded
 ScannerNb Element 1
 STatus Element 1
In the following Mapping I tried to Map this structure to the Structure used to send an Update SQL Statement to the JDBC Receiver to update the same table. A normal Test in the Mapping Tool runs fine but when I enter under source the above incoming Message from the JDBC Adapter I got the following error. I think the incoming message cannot be interpreted. Can someone support me? I read the documentation for the JDBC adapter and also a lot of weblogs and discussion threads. Maybe someone knows a weblog describing more detailed the sender adapter and how to handle the incoming Message!!
Thanks in advance Oliver
14:58:03 Start of test
Compilation of MM_JDBC_to_JDBC_test successful
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
Root Cause:
com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128)
at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68)
Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2009)
at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2657)
at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2713)
at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:132)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:142)
at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:245)
at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276)
at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338)
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)
... 3 more
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)

Hi Oliver,
>>>>source the above incoming Message from the JDBC Adapter I got the following error. I think the incoming message cannot be interpreted.
do this:
in the test tab try your mapping once more
(the correct one)
then save the source xml as file
next compare this saved file with the one
you get from the jdbc sender
>>>>>Declaration not allowed here.(:main:, row:1, col:8)
and compare the first lines in those two XML files
are they the same?
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Operating System Command in JDBC Sender

Hello everybody,
I'm trying to find some syntax to execute an operating system command on Windows Server 2003, but the commands don't seem to work I'm actually trying to generate a directory, now the problem is that I can't find syntax examples on how to do this I tried something like MKDIR TEST, now is the syntax of the command lines as you write them in Command Prompt, or maybe there is my error, thanks in advance.
Regards,

Confirmed.
JDBC sender also support OS command.
Refer to note 841704 if you face any issue while executing OS command in JDBC adapter.
Note: OS Command execute when processing in database executed successfully. It is even independent on OS command Errors.
Thanks
Farooq
Edited by: Farooq Farooqui on Jan 16, 2009 11:36 AM

JDBC(Sender)-XI-RFC (Request) RFC (Response)-XI-JDBC(Receiver)

Hi All,
JDBC(Sender)-XI-RFC (Request)
RFC (Response)-XI-JDBC(Receiver).
Need some solution for sending email for successfully completion of scenario after updating SQL DB Table.
Let me explain the scenario:
We are pooling the SQL DB table to pull the records and map the records to RFC request parameters, after successful Posting the entries in R3 HR, RFC response contain the same with E (Error) S (Success) records status, we are updating the same in SQL DB table, I implemented the complete scenario without BPM with the help of module processor in Sending JDBC Adapter, scenario is working fine but now we have to send the successful mail to our support team with status contain Number of success, Error and total records as email.
I need the solution how to implement the same requirement in current scenario.
Is their way to do something with the RFC receiver adapter module addition to send the successful mail or generating Alert with all the description?
I am at PI 7.0 SP12 with HP unix box.
Thanks in Advance for creative idea
With Regards
Sunil

Hi Bhavesh,
Thanks for your help and your blog is really helpful. I implemented the UDF for generating Email Alert but this alert is generating before Updating the SQL Database, is their any way to generate alert after updating the SQL.
Actually in my scenario we are sending the data from SQL to R3 by RFC and again updating the SQL status whatever the RFC return, after successfully updating SQL we need to send success email to support people but if we are sending the email before updating the DB then their will be problem.
JDBC receiver after updating the SQL DB returns the response with No. of row updated but how to capture this response, if we can capture this response then we can send email through email adapter even their is one more problem, In my scenario I am counting the number of rows with status S and E and sending the same in alert email but if are sending email after updating the SQL DB where can hold the row count value and use it while sending the email.
Implemented the scenario without using BPM..i am using sender JDBC module processor for Syn-Asyn bridge.
Even I do not find the link to reward point. Please let me know how to do it.
With Regards
Sunil

JDBC Channel ERROR

Hi,
We sended data from DB using PI JDBC Sender Adapter. Some times we
found error ocuured in RWB when the data rows is large.
Here is the Audit log for the error message. It tell me
that "java.io.IOException: Error writing to server".
The data about 15461 row(s) and each row has about 200 colums, the
query result size is about 12M.
Can someone get me some help? Some parameters should be changed ?
Best Regards,
Terry
Audit Log for Message: 59e0f073-6206-48b2-109a-922e33b71e36
Time Stamp Type Description
2012-01-10 09:34:31 Information Channel JDBC_SEND_EB_CO_PA: Executed
Query successfully, start executing update.
2012-01-10 09:34:32 Information Channel JDBC_SEND_EB_CO_PA: Updated
15461 row(s) successfully.
2012-01-10 09:34:32 Information Send query result, size 108737266
characters.
2012-01-10 09:34:44 Information MP: entering1
2012-01-10 09:34:44 Information MP: processing local module
localejbs/CallSapAdapter
2012-01-10 09:34:44 Information The application tries to send an XI
message asynchronously using connection
JDBC_http://sap.com/xi/XI/System.
2012-01-10 09:34:44 Information Trying to put the message into the send
queue.
2012-01-10 09:35:29 Information Message successfully put into the
queue.
2012-01-10 09:35:29 Information The application sent the message
asynchronously using connection JDBC_http://sap.com/xi/XI/System.
Returning to application.
2012-01-10 09:35:29 Information MP: leaving
2012-01-10 09:35:29 Information The message was successfully retrieved
from the send queue.
2012-01-10 09:35:44 Information The message status was set to DLNG.
2012-01-10 09:35:44 Error Transmitting the message to endpoint
http://sapxiprd:9000/sap/xi/engine?type=entry using connection
JDBC_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException:
Error writing to server.
2012-01-10 09:35:44 Information The message status was set to WAIT.
2012-01-10 09:35:44 Information The asynchronous message was
successfully scheduled to be delivered at Tue Jan 10 09:40:44 CST 2012.
2012-01-10 09:40:44 Information The message status was set to TBDL.
2012-01-10 09:40:46 Information Retrying to send message. Retry: 1
2012-01-10 09:40:46 Information The message was successfully retrieved
from the send queue.
2012-01-10 09:40:46 Information The message status was set to DLNG.
2012-01-10 09:40:47 Error Transmitting the message to endpoint
http://sapxiprd:9000/sap/xi/engine?type=entry using connection
JDBC_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException:
Error writing to server.
2012-01-10 09:40:47 Information The message status was set to WAIT.
2012-01-10 09:40:47 Information The asynchronous message was
successfully scheduled to be delivered at Tue Jan 10 09:45:47 CST 2012.
2012-01-10 09:45:47 Information The message status was set to TBDL.
2012-01-10 09:45:48 Information Retrying to send message. Retry: 2
2012-01-10 09:45:48 Information The message was successfully retrieved
from the send queue.
2012-01-10 09:45:48 Information The message status was set to DLNG.
2012-01-10 09:45:49 Error Transmitting the message to endpoint
http://sapxiprd:9000/sap/xi/engine?type=entry using connection
JDBC_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException:
Error writing to server.
2012-01-10 09:45:49 Information The message status was set to WAIT.
2012-01-10 09:45:49 Information The asynchronous message was
successfully scheduled to be delivered at Tue Jan 10 09:50:49 CST 2012.
2012-01-10 09:50:49 Information The message status was set to TBDL.
2012-01-10 09:50:50 Information Retrying to send message. Retry: 3
2012-01-10 09:50:50 Information The message was successfully retrieved
from the send queue.
2012-01-10 09:50:50 Information The message status was set to DLNG.
2012-01-10 09:50:51 Error Transmitting the message to endpoint
http://sapxiprd:9000/sap/xi/engine?type=entry using connection
JDBC_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messaging.api.exception.MessagingException:
Error transmitting the message over HTTP. Reason: java.io.IOException:
Error writing to server.
2012-01-10 09:50:51 Error The message status was set to NDLV.

Hi,
Have a look at a similar thread java.io.IOException during large file processing on PI 7.1. It says about a file adapter error, but the reason seems similar - exceeding the maximum size of a HTTP request allowed in PI configuration. Try checking the value of parameter icm/HTTP/max_request_size_KB and make sure it is greater then the size of your message (in XML size).
Hope this helps,
Grzegorz

JDBC Sender Error

Similar Messages

Maybe you are looking for