Skip to Content

JDBC adapter error

I have an ECC to JDBC scenario. The record has seventy fields and there are around 3000 records in one payload sent from ECC.

At times, the ECC is sending more characters in a field and due to that the entire payload is failing.

For ex: the third field has character length of three fields. If ECC sends four characters it will fail. The JDBC receiver adapter doesn't show which field has more characters and the interface just fails. There may be upto 3000 records in the payload.

Is it possible to make sure that the records with proper data can be processed in JDBC receiver adapter and the error ones fail?

Is there any work around available?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Sep 08, 2015 at 09:27 AM

    Hi Harish,

    Go to DB and check the fields lengths and types. Later set you sender schema with this characteristics, then the sender ECC proxy will have these restrictions.

    Regards.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Harish Babu

      Hi Harish,

      Say, ECC sends 100 records in one payload. There are three records with extra charcaters. Will the 97 records in the payload go through?

      No, but XML validation would atleast give you the details of possible record which is failing. Morever, still you would have the message in failed status in PI which can be edited for erroneous record and batch can be re-processed from PI.

      However, I would still recommend to make validation in proxy code of ECC to truncate excessive characters for fields due to which database update may fail and when you do this you are actually reducing the frequency of redundant KNOWN errors.

      I also agree with solution proposed by Vinay of trncating extra characters in PI by using substring but standard substring function sometimes doesn't behave as expected so my recommendation is for handling the validations in proxy code to extent possible.

      Thanks,

      Amit

  • Sep 08, 2015 at 08:37 AM

    set the logSQLStatement parameter to "true" in he advanced adapter properties of jdbc adapter then you can see the query in RWB and the exact place where it fails.

    Add comment
    10|10000 characters needed characters exceeded

    • if its failing because of length problem then you should be able to see the error in Message logs, can you see the exact query in message monitoring? That's the only place i know where you can diagonose such errors

  • Sep 08, 2015 at 05:22 PM

    Hi,

    >>Is it possible to make sure that the records with proper data can be processed in JDBC receiver adapter and the error ones fail?

    Could be possible, but it depends whether u are using SP or Insert/Update statement?

    Check my reply in this thread

    proxy to jdbc insert | SCN

    Thanks

    Amit Srivastava

    Add comment
    10|10000 characters needed characters exceeded