0

I have a business process that uses Oracle LogMiner periodically and I notice that every time the LogMiner API is invoked by this process, the database writes a number of entries to the alert log. Is there any way to customize or reduce the verbosity of LOGMINER so that it doesn't write these log entries every time an ad-hoc session is started and a query is executed?

An example of the entries I'd like to avoid are as follows:

2022-09-08T13:25:27.747284+00:00
LOGMINER: summary for session# = 2148178945
LOGMINER: StartScn: 6452026 (0x000000000062733a)
LOGMINER: EndScn: 6452099 (0x0000000000627383)
LOGMINER: HighConsumedScn: 0
LOGMINER: PSR flags: 0x0
LOGMINER: Session Flags: 0x4000441
LOGMINER: Session Flags2: 0x0
LOGMINER: Read buffers: 4
LOGMINER: Region Queue size: 256
LOGMINER: Redo Queue size: 4096
LOGMINER: Memory LWM: limit 10M, LWM 12M, 80%
LOGMINER: Memory Release Limit: 0M
LOGMINER: Max Decomp Region Memory: 1M
LOGMINER: Transaction Queue Size: 1024
2022-09-08T13:25:27.755395+00:00
LOGMINER: Begin mining logfile for session -2146788351 thread 1 sequence 48, /opt/oracle/oradata/ORCLCDB/redo03.log
Naros
  • 19,928
  • 3
  • 41
  • 71
  • I'm afraid there is nothing you can do. Also these CDC tools which are based on LOGMINER utilize single CPU almost exclusively and they might reach the limit when single CPU's power is not enough. – ibre5041 Sep 09 '22 at 11:29

0 Answers0