Killing Tracing Causes Database Invalidation
Last updated on NOVEMBER 01, 2015
Applies to:Oracle TimesTen In-Memory Database - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
User was tracing TimesTen using ttTraceMon to a file on disk. It was writing out lots of tracing messages to file on disk. User killed the process that was holding a lock on the trace ouput file. That caused the TimesTen database to get invalidated.
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