Unable to write to DB - time allocated was insufficient

Hi Baghavathi,Are you using Store Procedure or Write to DB Smart service?

@Baghavathi
1) Is unattended node remains green or blue ?
2) Is CDT contains multiple rows of data to write ?

Hi Zubair, the unattended node remained green and turns out to be red aborted after sometime. The CDT contains single row, I'm trying to save single row in db.
@Ashma, I'm using write to DB smart service.

Try checking whether CDT is mapped with DB Table.

try checking whether you're able to connect to the database using a direct connection...maybe due to network issues database/schema isnt reachable.

Just try firing the same insert query manually in your SQL Database and check how fast it gets inserted over there ?
Incase it delays in inserting the data into your table check indexing is properly done with respect to the primary key of your table. Sometimes when large amount of data is there in any table and without indexing there might be a chance of taking some time to execute the query and from appian it like there few seconds of internal timings for WTD SS.

@Baghavathi - Is there any trigger being called while inserting the data which has complex logic? If not then as suggested please try to insert a row explicitly in your database. If it is successful then it might be connection issue.

@ Zubair, I was unable to update values in that particular table directly in DB though sql. The indexing is correct, it is pointing to the primary key. @sagar - There is no trigger being called.

If you are unable to insert directly then there should be an issue at your DB side. Please try to get what ORA error or other errors you are getting in when you try direct insert query. When you get any error and that is your problem. Resolving that would solve your problem

-> Before that try inserting data in some other tables which is present in the same schema. That would give us solution like is there problem at schema level or table level,as there could be a chance of network issue at database/schema level

It was a problem with that particular table, it was locked, The issue has been resolved after killing that lock.