Adjusting Oracle failover retry settings

In some cases, after a failover, the database connections that are cached in a connection pool become stale and point to the previous Oracle RAC database server, which is unavailable. Normally, the application server handles the retry before the Content Platform Engine server attempts the retry. However, in some circumstances, the default number of retry attempts for Content Platform Engine must be increased from the default of 1 to a higher number, such as 20, so that the failover of Oracle RAC can work. To change the number of attempts, add JVM arguments to the Content Platform Engine server.

Content Platform Engine usually relies on the retry mechanism in the application server to purge stale connections. However, if for some reason the application server fails and continues to point to a stale database connection, the JVM argument enables the use of Content Platform Engine's retry mechanism. The default setting is com.filenet.db.DBMaxConnectionAttempts=1, which means no retry. Increase the setting as needed.