![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.Note - On the Oracle (UNIX/Linux) TIBCO iProcess Engine the event system used by the Process Sentinels is provided by the database. This means that the use of Oracle’s Transparent Application Failover (TAF) feature is required to provide failure or failover support. See page 109 for more information. 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 |