Last updated on SEPTEMBER 23, 2016
Applies to:Oracle TimesTen In-Memory Database - Version 220.127.116.11.0 to 18.104.22.168.1 [Release 7.0 to 11.2]
Information in this document applies to any platform.
*** Checked for relevance 30-Oct-2015 ***
Customer operated a large telephone billing system running on TimesTen V22.214.171.124.4 under IBM AIX V6.1; the system was configured to accommodate up to 1024 concurrent connections.
On 2 successive days, at just about the same time, all end users reported serious performance problems with many insisting that the application had become completely hung. In both cases the problem was eventually resolved by rebooting the host server.
Examination of TimesTen diagnostics showed nothing that might normally be associated with an application-wide blockage and did not even show anything that might cause a small subset of the processes to hang. Beginning with the time in which the system hanging was reported, there was not a single TT6002 deadlock nor TT6003 lock timeout error or any other error we might expect to find when a group of processes were blocked or hanging. In fact, subsequent examination of TimesTen diagnostics indicated that there were no failures of any kind and system execution was never interrupted at any point prior to the customer's decision to reboot the host server.
The only change was the addition of a script submitting a large series of batch invoice processing commands.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms