Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 8 Database Failure and Failover : TIBCO iProcess Engine Behavior

TIBCO iProcess Engine Behavior
The following table shows how different TIBCO iProcess Engine components behave in the event of a database failure or failover.
On SQL and DB2: Each TIBCO iProcess Engine process clears down any database connections it already has (as they are used) and attempts to re-establish a new connection. If necessary, the process retries the connection attempt until the database becomes available again, when the attempt succeeds.
On Oracle: The server processes use the Oracle Client to establish and maintain database connections. The Oracle Client therefore attempts to re-establish the database connection. If necessary, it retries the connection attempt until the database becomes available again, when the attempt succeeds.
For example, if you use SWDIR\util\swsvrmgr to issue a Restart event for a process when the database has failed, the process is not restarted until the database connection is restored.
For example, if you have a SWDIR\util\swadm session open when the database fails, and you then try to add a BG process, the command hangs until the database connection is restored. As soon as the database is available again, the command completes and the new BG process is added.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved