JDBC error while calling wmtndocxmlrouteXml

, ,
1

Hello Friends,

I am invoking the service ‘wm.tn.doc.xml:routeXml’ from one of my flow services. I am passing content and contentType fields as input. But I am getting following error:

com.wm.app.b2b.server.ServiceException: Couldnt insert new document
(0) java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
(1) java.sql.SQLException: [wm-cjdbc33-0009][Oracle JDBC Driver][Oracle]ORA-01401: inserted value too large for column
at wm.tn.doc.persist(doc.java:789)
…
…
…
…

I am not sure why this error occurs ? I was succeeded previously with the same content.
I tried the same input passing to the wm.tn:receive service, but it also throws the same error.

Thanks in Advance.

Regards,
Nilesh

2

Same thing is happening to our system. Seems to be in all environments, DEV/QA/PROD. Just started happening today, same documents as we always send.

3

Same thing is happening here.

4

We are also facing the same issue on our Prod TN since 2:00 pm today.Assumed to be DB error. Seems like we have some greater issue.
Please keep posted if any updates.

5

Nilesh,

Have you tried recycling the IS/TN or reloading the TN related packages?

Also try to use small size xml document or create a new dummy document in TN and then push it to TN using ISAdminConsole/WmTNWeb document submission,if this works then try using routeXML service by just providing node as input.

HTH,
RMg.

6

What is you environment?
IS machine, Database, etc…

We are facing the same problem running on IBM AIX, Oracle 9.1.

Please, let me know if you find something…

Thanks

7

It seems that there is a GLOBAL webMethods ISSUE. Contact the wM Helpdesk.

Seems to be a column in BIZ_DOC that is too small.

8

Its weird everybody seeing same error?whats going on…let me check in our system too…

9

We just got off the phone with Tech Support. It’s a Global issue with TN creating a 25-byte Bizdoc Document ID and trying to insert it into a 24-byte field on the database. They’re working on a fix and will publish it as soon as they can.

10

Can everyone with this issue post your database and wM server versions? Maybe we can find a common thread. We’re on webMethods 6.1 and Oracle 9.2.0.3. We’re seeing the issue on both HP/UX and Windows 2000 servers.

RMG - we’ve tried all different types of documents and server restarts, nothing has worked yet.

11

Wow! We just started seeing that today as well in Dev/Test. I’m going to try not logging content in the Doctype settings until I can figure out what’s going on. But how weird that everyone’s seeing this at the same time. Do we have an embedded virus of some sort here?

12

Dave - thanks for posting that. I figured it was something like that from the errors, but couldn’t find any data to support the theory. Any idea how they discovered exactly where the problem was?

Michael - I doubt we’re talking about a virus. More likely webMethod simply used the date somehow in their algorithm for generating the bizdoc ID, and at a certain time that algorithm generated a larger number than they expected.

13

Thanks Dave for the update,

Skip,
Actually the same error is throwing in all 6.x versions.

14

Hello,
we are seeing the same problem. We are on WM601 on a sun 5.8 with oracle 8.17. Our sever has been working fine for month at a time, why all of a sudden today we would the same issue?
Regards,

15

Hello,
we are seeing the same problem. We are on WM601 on a sun 5.8 with oracle 8.17. Our sever has been working fine for month at a time, why all of a sudden today we would the same issue?
Regards,

16

Skip,

Yes I see, thanks. Jonathan, as Skip suggested, there’s undoubtedly some date/time-based component in the internal DocumentID that caused this string to just today become larger than the 24 bytes allocated to it in the Bizdoc table. Let’s keep an eye out for a Fix from support.

17

Thanks for the info. Hope to get the update soon.

18

Hello,

I think its really something wrong with the webMethods product itself.

RMG,
I tried sending small document and restarting server, re-enabling the TN packages, but nothing is working out.

I am using SunOS with WM 6.1

Keep posting if anyone gets some update.

Regards,
Nilesh

19

Nilesh,

Thanks for trying…

Anyways its a global issue now,WM is going to release a fix for this…somebody will definetely update…

Regards,

20

the last i called webMethods, there were atleast 35 other partners reporting this since about 2:45 PM EST.

ANyone using anything other than Oracle - we are on Oracle 9.2.04