Updated Batch Best Practices
Posted
by ACShorten
on Oracle Blogs
See other posts from Oracle Blogs
or by ACShorten
Published on Thu, 30 Jun 2011 19:49:36 -0700
Indexed on
2011/07/01
8:27 UTC
Read the original article
Hit count: 373
/Oracle/Advice
The Batch Best Practices whitepaper has been updated and published to My Oracle Support with the latest advice and new facilities.
Two of the more interesting updates are:
- Addition of a Bache Cache Flush - Just like the online, the batch component of the framework caches data. It is now possible to refresh the cache manually using a new batch jobs F1-FLUSH. This is particularly useful if you execute long running threadpool workers across many different batch processes (submitters).
- New EXTENDED execution mode - A new specialist mode has been introduced for sites that use a large number of submitters (concurrent threads) and are experiencing intermittent communication issues in the threadpoolworker. This mode uses Oracle Coherences Extend mode to allow submitters to be allocated to threadpoolworkers via proxy connections. It differs from CLUSTERED mode in that a submitter can be explicitly allocated to a specific threadpoolworker via a proxy connection. This mode is only used for specific situation and customers should continue to use CLUSTERED mode gemerally.
The whitepaper outlines advice for these new facilities and provides advice for existing functionality.
The whitepaper is available from My Oracle Support at Doc Id: 836362.1.
© Oracle Blogs or respective owner