Lost-write Messages in User Trace File
An IBM Q Capture database session that is initiating Oracle LogMiner, is producing the following messages in the associated server-side trace file. My dilemma is that there are no error messages in the database alert log, or any other location pertaining to any sort of "lost write" problem, or problems with writing to the SAN.
I am curious if anyone else has seen this behavior with the constant logging to the trace file. The LogMiner session was started with options: DICT_FROM_ONLINE_CATALOG, CONTINUOUS_MINE, NO_ROWID_IN_STMT.
One other question, is the messaging normal behavior if you do not use the COMMITTED_DATA_ONLY option?
I am curious if anyone else has seen this behavior with the constant logging to the trace file. The LogMiner session was started with options: DICT_FROM_ONLINE_CATALOG, CONTINUOUS_MINE, NO_ROWID_IN_STMT.
One other question, is the messaging normal behavior if you do not use the COMMITTED_DATA_ONLY option?
0