TimesTen Case Study: All Cache Groups On 4 Different Data Stores Failing To Refresh
Last updated on SEPTEMBER 23, 2016
Applies to:Oracle TimesTen In-Memory Database - Version 11.2.1 and later
Information in this document applies to any platform.
***Checked for relevance on 02-Jun-2014***
***Checked for relevance on 03-Feb-2016***
Customer's application was configured to run on 4 separate TimesTen data stores with an identical set of autorefreshed read-only cache groups on each data store. The base tables for all of the cache groups resided on a single Oracle database.
Customer reported that none of the cache groups on any of the 4 data stores were refreshing properly. Customer subsequently determined that any operation attempted by the cache agent hung.
-no changes were made on any of the TimesTen data stores.
-some invalid kernel parameter changes may have been enabled on the Oracle database.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms