Hi All,
we are getting JDBC begin transaction failed: in the process model when one record going to store in database.
and another process model we are getting -Unable to write to or delete from the source due to system error.Error Details: Failed to update database "TN_Transaction" because the database is read-only.
note : both error happening at same time.
could you please someone help me on which scenario we wil get this error.
thanks!
Discussion posts and replies are publicly visible
suresh said:because the database is read-only
This smells like an issue on the DB side. I suggest to contact your DB admin team.
suresh ,It could be due to connectivity issues with the database, incorrect credentials, or database settings that restrict write operations, probably when database is being backed up or during maintenance periods. check with your admin if you have been given 'write' access. check if you have appropriate permissions to write to the "TN_Transaction" database.
Hi suresh , As Stefan Helzle mentioned, it would be a failure from the database side—database in read-only mode, transaction locking, and connection loss. I suspect there might be an issue with the Appian connection pool. Did you check the system logs? Did you find any information in the logs?
HI Abhishek Karumuru thanks for response, this is issue happens in the production, that to its not happening for all all records its happens for only 2 records in the specific data source.
Did you check the data for those two records? Is the data correct? Are there any triggers set up for that database table? Also, please check if any processes are running in the background.
hi Abhishek Karumuru yes for the both records the data is correct.
Can you check with your DB admin once? and get the analysis, is there any foreign key error? i suspect there is some locking issue
Sound like permissions at the table level. User has read but not write permission on those 2 tables.
Could you check table locking and Appian logs when the error is raised please? It seems to be database related, but if it were only database related you would get the error on all records.