RealTime Publish Fails or Hangs, and Database Lock Escalations Are Seen In Logs
(Doc ID 1427928.1)
Last updated on FEBRUARY 09, 2024
Applies to:
Oracle WebCenter Sites - Version 7.5.0 and laterInformation in this document applies to any platform.
Symptoms
Real-Time publish fails or hangs and warnings about lock escalations are seen in the target log or when monitoring MS SQL Server. The log warning appears like:
"[CS.DB][ERROR] SQLException in prepared execute on table AssetPublication: SELECT * FROM AssetPublication WHERE assetid = ? AND assettype = ?
assetid = 1298923874255
assettype = Content_C
java.sql.SQLException: Transaction (Process ID 59) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)
at net.sourceforge.jtds.jdbc.TdsCore.getNextRow(TdsCore.java:764)
at net.sourceforge.jtds.jdbc.MSCursorResultSet.processOutput(MSCursorResultSet.java:956)
at net.sourceforge.jtds.jdbc.MSCursorResultSet.cursorCreate(MSCursorResultSet.java:541)
at net.sourceforge.jtds.jdbc.MSCursorResultSet.(MSCursorResultSet.java:154)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:424)
at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:777)
at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |