on 01-15-2007 2:25 PM
Hello,
I try to write to a table on an Oracle DB.
This is my request:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_JDBC_WRITE_GARANTIEFALL xmlns:ns0="http://www.zeiss.org/excel">
- <STATEMENT>
- <TABLENAME ACTION="INSERT">
<TABLE>IRIS.T_GARANTIE_FALL</TABLE>
- <ACCESS>
<FALL_NR>1</FALL_NR>
<MASCHINEN_NR>12</MASCHINEN_NR>
<CALL_ID>123</CALL_ID>
<IDENT_NR>e</IDENT_NR>
<DAT_ESKALATION>12.01.07</DAT_ESKALATION>
<DAT_SAT>12.01.07</DAT_SAT>
<DAT_END_GARANTIE>12.01.07</DAT_END_GARANTIE>
<PULS_NR>126</PULS_NR>
<AUSFALLGRUND>m</AUSFALLGRUND>
<ST_MDRV_MDRV_ID>4</ST_MDRV_MDRV_ID>
<DAT_SWAP_ENTSCHEIDUNG>12.01.07</DAT_SWAP_ENTSCHEIDUNG>
<BEMERKUNG>s</BEMERKUNG>
</ACCESS>
</TABLENAME>
</STATEMENT>
</ns0:MT_JDBC_WRITE_GARANTIEFALL>
Simple and nice! But in comm.channel monitoring I have this error message:
Eroor when parsing or executing XML-SQL-Document: Error processing request in sax parser: Error when executing statement for table/stored proc. 'IRIS.T_GARANTIE_FALL' (structure 'STATEMENT'): java.sql.SQLException: ORA-00917: missing comma
Whats going on with this comma?
Regards
Dirk
hi,
try setting: logSQLStatement
from sap note 801367
to see how your statement really looks like
Regards,
michal
-
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This means that you want to insert a record with a key that already exists.
<b>ORA-00001:</b> unique constraint (string.string) violated
<b>Cause:</b> An UPDATE or INSERT statement attempted to insert a duplicate key. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.
<b>Action:</b> Either remove the unique restriction or do not insert the key.
Regards,
Sandro
Thank you, Sandro!
Thats it!
Possibly it would be easier to work on a scenario where you have access to all participating systems. The JDBC here is unfortunately in access of a third party.
So I can only guess whats going on, when at the 3rd party nobody knowing about the JDBC is in the office!
I made a call and somebody looking at the DB-table could confirm to that idea!
Regards
Dirk
User | Count |
---|---|
96 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.