Home » RDBMS Server » Server Administration » Oracle .trc files consuming large amounts of disc space (Oracle Enterprise Edition 12.1.0.2.0 - 64 bit on Windows 10)
Oracle .trc files consuming large amounts of disc space [message #658088] Fri, 02 December 2016 17:22 Go to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
I am a retired developer, not a DBA, running Oracle Enterprise Edition, version 12.1.0.2.0 - 64 bit on Windows 10 on my laptop computer. I purchased this laptop and installed Oracle on it in December of 2015. A long time ago, I noticed that I was seeing less and less disk space available at a rate that struck me as unreasonably high for the things that I was doing. I was too busy with many other non-computer things to have time to diagnose it at that time, but I did make a note of the disk space at the time. Now that I have finally gotten around to trying to diagnose it, I have 32 gb less disk space available than I did on September 29, 2016. I used Windows Explorer to search for any gigantic files. The only thing that I found that struck me as odd was that in the following Windows sub-directory:

c:\app\baboehme\diag\rdbms\orcl\orcl\incident

I have a huge number of sub-directories of the format incdir_NNNNN, where each NNNNN represents different 5-digit numbers, with one or more such sub-directories per date, since June 25, 2016. There are a few others before that, but not daily. Each of these folders contains one trc file and one trm file with the same name of the format orcl_j00N_NNNN_iNNNNN.trc, where each N represents a number. Most of these trace files are 404 mb. So, it appears that the rapid consumption of disk space is due to these Oracle trace files. I tried reading one of these files, but since I am a retired developer, not a DBA, it is meaningless to me. They are too big to upload and attach here. The majority of each file seems to be repeating sections such as three in the excerpt below.

  Chunk        044540020 sz=      112    freeable  "mbr node memory"
Dump of memory from 0x0000000044540020 to 0x0000000044540090
044540020 00000071 00B38F00 00000000 00000000  [q...............]
044540030 2788CAB8 00007FF6 A891AC19 BFDAFC3D  [...'........=...]
044540040 0CD818C2 BFE55A3A 5AB7BF0A 3FE3A5BD  [....:Z.....Z...?]
044540050 00000000 00000000 630CD9F4 BFDAF9C6  [...........c....]
044540060 B60FB34A BFE55902 467ECFE5 3FE3A7E8  [J....Y....~F...?]
044540070 00000000 00000000 00000000 3FF00000  [...............?]
044540080 445400A8 00000000 00000000 00000000  [..TD............]
  Chunk        044540090 sz=      104    freeable  "mbr node memory"
Dump of memory from 0x0000000044540090 to 0x00000000445400F8
044540090 00000069 00B38F00 44540020 00000000  [i....... .TD....]
0445400A0 2788CAB8 00007FF6 ED1C24A7 BFDB1FEB  [...'.....$......]
0445400B0 D4650DAA BFE56031 719FEDBE 3FE393DA  [..e.1`.....q...?]
0445400C0 00000000 00000000 D4EAB206 BFDB1D42  [............B...]
0445400D0 899930CE BFE55E36 52915DCC 3FE39518  [.0..6^...].R...?]
0445400E0 00000000 00000000 00000000 3FF00000  [...............?]
0445400F0 44540110 00000000                    [..TD....]        
  Chunk        0445400f8 sz=      104    freeable  "mbr node memory"
Dump of memory from 0x00000000445400F8 to 0x0000000044540160
0445400F0                   00000069 00B38F00          [i.......]
044540100 44540090 00000000 2788CAB8 00007FF6  [..TD.......'....]
044540110 1A9BD919 BFDB23E6 09857EDD BFE559F0  [.....#...~...Y..]
044540120 F37DBEFA 3FE39A32 00000000 00000000  [..}.2..?........]
044540130 FFA0C219 BFDB1D24 729ADCDD BFE55844  [....$......rDX..]
044540140 F0A7522C 3FE39AC7 00000000 00000000  [,R.....?........]
044540150 00000000 3FF00000 44540178 00000000  [.......?x.TD....]

I can easily just delete the files to free the disk space, but if there is something that needs to be fixed, I would like to know about it. I have not noticed any problems while using Oracle. I don't even know if the trace files mean that there is anything wrong or if they are just logging things that Oracle does automatically. I seem to remember a similar problem with rapid consumption of disk space on another computer that was solved by disabling the OracleJobSchedulerORCL service, but that is already disabled. The following Oracle services are running:

Oracle_app_baboehme_product_121~1.0_dbhome_2ConfigurationManager
OracleOraDB12Home1MTSRecoveryService
OracleOraDB12Home1TNSListener
OracleServiceORCL
OracleVssWriterORCL

I tried reading the following file:

c:\app\baboehme\diag\rdbms\orcl\orcl\trace\alert_orcl.txt

to see if that might give me some clues. The top of that file begins on December 24, 2015, which is about when I installed Oracle. All of the information for recent days look similar, so I have just included one day, yesterday, below:

Thu Dec 01 01:42:07 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Thu Dec 01 01:42:08 2016
Setting Resource Manager plan SCHEDULER[0x4445]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Thu Dec 01 01:42:15 2016
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Thu Dec 01 01:42:18 2016
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P4161 (42704) VALUES LESS THAN (TO_DATE(' 2016-12-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P4164 (42704) VALUES LESS THAN (TO_DATE(' 2016-12-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Thu Dec 01 01:42:22 2016
Thread 1 cannot allocate new log, sequence 1011
Private strand flush not complete
  Current log# 2 seq# 1010 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Thu Dec 01 01:42:24 2016
Thread 1 advanced to log sequence 1011 (LGWR switch)
  Current log# 3 seq# 1011 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Thu Dec 01 01:43:11 2016
Thread 1 advanced to log sequence 1012 (LGWR switch)
  Current log# 1 seq# 1012 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Thu Dec 01 01:43:14 2016
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P4165 (2527) VALUES LESS THAN (TO_DATE(' 2016-12-02 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P4166 (2527) VALUES LESS THAN (TO_DATE(' 2016-12-02 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P4169 (2526) VALUES LESS THAN (TO_DATE(' 2016-12-01 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Thu Dec 01 01:43:59 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j001_9732.trc  (incident=85636):
ORA-00600: internal error code, arguments: [723], [144520], [73440376], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85636\orcl_j001_9732_i85636.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Thu Dec 01 02:00:01 2016
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Thu Dec 01 02:42:11 2016
Sweep [inc][85636]: completed
Sweep [inc2][85636]: completed
Thu Dec 01 11:42:38 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Thu Dec 01 13:00:03 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_3692.trc:
ORA-12012: error on auto execute of job "APEX_040200"."ORACLE_APEX_WS_NOTIFICATIONS"
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
Thu Dec 01 13:00:03 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_3692.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
ORA-12012: error on auto execute of job "APEX_040200"."ORACLE_APEX_WS_NOTIFICATIONS"
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
Thu Dec 01 13:25:40 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Thu Dec 01 17:15:11 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Thu Dec 01 18:00:06 2016
Thread 1 advanced to log sequence 1013 (LGWR switch)
  Current log# 2 seq# 1013 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Thu Dec 01 20:35:03 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_3772.trc:
ORA-12012: error on auto execute of job "APEX_040200"."ORACLE_APEX_MAIL_QUEUE"
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
Thu Dec 01 20:35:03 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_3772.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
ORA-12012: error on auto execute of job "APEX_040200"."ORACLE_APEX_MAIL_QUEUE"
ORA-00001: unique constraint (TRACE_FILES.AVAIL_TRACE_FILES_PK) violated
ORA-06512: at line 6
Thu Dec 01 20:39:11 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.

I have Windows set to automatically get the time from the internet, so that might account for the repeated time drift warnings. My internet searches indicate that these time drift warnings can be ignored.

Could some of the problems be due to allowing so many trace files to accumulate? Should I try deleting most of the old ones and see what happens with the new ones? Does anyone see anything else that might suggest a problem or have any other suggestions as to where to look for what or what to do?
Re: Oracle .trc files consuming large amounts of disc space [message #658091 is a reply to message #658088] Sat, 03 December 2016 00:55 Go to previous messageGo to next message
Michel Cadot
Messages: 65387
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

jNNNN means it comes from a job which is confirmed by the error message in alert.log:
ORA-12012: error on auto execute of job

I don't know APEX so I can't help on this specific job maybe Littlefoot could.

In the meantime, you can drop all these "incident" directories but the first and last one related to this error to get back space. Maybe you could also have a look at the table associated to this PK and truncate it if you don't care about it.

If you don't use VSS to backup your database you can disable OracleVssWriterORCL:
sc stop "OracleVssWriterORCL"
sc config "OracleVssWriterORCL" start= disabled 
Re: Oracle .trc files consuming large amounts of disc space [message #658092 is a reply to message #658088] Sat, 03 December 2016 02:22 Go to previous messageGo to next message
John Watson
Messages: 7262
Registered: January 2010
Location: Global Village
Senior Member
This sort of thing is often a bug. I guess you won't have access to PSUs, so perhaps the easiest "solution" would be to set MAX_DUMP_FILE_SIZE=1.

As for that APEX job, you could just remove APEX and re-install.

Or, come to think of it, just drop the database and create a new one. Take a different path through DBCA and you might not have the problem hat all.
Re: Oracle .trc files consuming large amounts of disc space [message #658093 is a reply to message #658091] Sat, 03 December 2016 03:52 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Hi Michel,

I tried to drop all of the incident directories except the first and last using Windows Explorer. I checked the box to mark all of them, which I thought just marked the first page that I could see, like my email does, then I unchecked just the first. I selected delete and it said it was too big for the recycle bin and asked if I wanted to permanently delete, so I did that. Then, all that was left was the first one. Apparently, checking the box to mark all of them doesn't just mark all on the first page. So, I have accidentally deleted the most recent. It freed 82 gb of disk space.

As to the TRACE_FILES.AVAIL_TRACE_FILES_PK, when I looked at the trace_files user and associated tables and such, it jogged my memory. I checked and found that I created the trace_files user just before the huge trace file problem started. It had to do with some experimenting I was doing with one of Tom Kyte's tkprof utilities. So, I just dropped the trace_files user cascade and that should fix the biggest part of the problem.

I don't use VSS, so I stopped and disabled the OracleVssWriterORCL, using the Windows Services menu.

I expect all of that should eliminate most or all of the problems. I will have to wait and check the alert log and new trace files and see what happens.

Thanks for your help.

Regards,
Barbara

[Updated on: Sat, 03 December 2016 04:01]

Report message to a moderator

Re: Oracle .trc files consuming large amounts of disc space [message #658094 is a reply to message #658092] Sat, 03 December 2016 03:56 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Hi John,

I don't want to disable trace files, so I will leave the max_dump_file_size alone. I think it would be more hassle than it is worth to do any re-installation or database creation. I think most or all of the problems have been resolved now, so I will wait and see what turns up in the alert log and trace files now.

Regards,
Barbara
Re: Oracle .trc files consuming large amounts of disc space [message #658100 is a reply to message #658094] Sat, 03 December 2016 13:53 Go to previous messageGo to next message
Littlefoot
Messages: 21364
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Apex 4.2 is bundled with Oracle 12c; that's what "APEX_040200" in the alert file represents (it is its user name).

Jobs (mentioned in the alert file) are shortly described here:Oracle

ORACLE_APEX_PURGE_SESSIONS: Purges sessions older than 12 hours (the default). This job runs every hour.

ORACLE_APEX_MAIL_QUEUE: Sends mail that is in the mail queue every 5 minutes.

ORACLE_APEX_WS_NOTIFICATIONS: Determines Websheet notifications that need to be sent every 30 minutes.

ORACLE_APEX_DAILY_MAINTENANCE: Performs nightly maintenance, every day at 0100. This job archives the activity summary and runs the workspace purge process.
If you don't use Apex, you most probably don't need these jobs to run at all so - stop them; why would they fill the log file?
Re: Oracle .trc files consuming large amounts of disc space [message #658105 is a reply to message #658100] Sat, 03 December 2016 14:43 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Hi Littlefoot,

Thanks for replying. After all of the changes previously listed, I don't see anything about APEX anymore. I have listed below what I now see in the following file:

c:\app\baboehme\diag\rdbms\orcl\orcl\trace\alert_orcl.txt

Regards,
Barbara

Sat Dec 03 00:27:51 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sat Dec 03 00:28:02 2016
Setting Resource Manager plan SCHEDULER[0x4447]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sat Dec 03 00:28:27 2016
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sat Dec 03 00:29:03 2016
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P4170 (42706) VALUES LESS THAN (TO_DATE(' 2016-12-04 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Sat Dec 03 00:29:07 2016
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P4173 (2528) VALUES LESS THAN (TO_DATE(' 2016-12-03 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P4174 (2528) VALUES LESS THAN (TO_DATE(' 2016-12-03 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P4177 (2528) VALUES LESS THAN (TO_DATE(' 2016-12-03 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P4178 (42706) VALUES LESS THAN (TO_DATE(' 2016-12-04 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Sat Dec 03 00:29:28 2016
Thread 1 cannot allocate new log, sequence 1015
Private strand flush not complete
  Current log# 3 seq# 1014 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
Sat Dec 03 00:29:31 2016
Thread 1 advanced to log sequence 1015 (LGWR switch)
  Current log# 1 seq# 1015 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Sat Dec 03 00:30:32 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_6728.trc  (incident=85644):
ORA-00600: internal error code, arguments: [723], [144520], [73440328], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85644\orcl_j000_6728_i85644.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Sat Dec 03 01:27:56 2016
Sweep [inc][85644]: completed
Sweep [inc2][85644]: completed
Sat Dec 03 02:00:02 2016
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Sat Dec 03 09:28:37 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sat Dec 03 09:28:54 2016
Setting Resource Manager plan SCHEDULER[0x4448]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sat Dec 03 09:29:12 2016
Thread 1 cannot allocate new log, sequence 1016
Private strand flush not complete
  Current log# 1 seq# 1015 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Sat Dec 03 09:29:16 2016
Thread 1 advanced to log sequence 1016 (LGWR switch)
  Current log# 2 seq# 1016 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Sat Dec 03 09:29:25 2016
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sat Dec 03 09:30:41 2016
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P4179 (2529) VALUES LESS THAN (TO_DATE(' 2016-12-04 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P4180 (2529) VALUES LESS THAN (TO_DATE(' 2016-12-04 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Sat Dec 03 09:31:28 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_16512.trc  (incident=85652):
ORA-00600: internal error code, arguments: [723], [144520], [73440680], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85652\orcl_j000_16512_i85652.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Sat Dec 03 09:58:43 2016
Thread 1 advanced to log sequence 1017 (LGWR switch)
  Current log# 3 seq# 1017 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
Sat Dec 03 10:28:42 2016
Sweep [inc][85652]: completed
Sweep [inc2][85652]: completed
Sat Dec 03 11:19:40 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Re: Oracle .trc files consuming large amounts of disc space [message #658121 is a reply to message #658105] Mon, 05 December 2016 04:01 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
The problem continues with 2 or 3 trace files per day consuming about 1 gb per day. I don't know what else to do, other than just delete them periodically, which I would find more convenient than a re-installation that might just have the same problem. Any other ideas?

Re: Oracle .trc files consuming large amounts of disc space [message #658122 is a reply to message #658121] Mon, 05 December 2016 04:09 Go to previous messageGo to next message
Michel Cadot
Messages: 65387
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Anything in the alert.log file at the time of the files?

Re: Oracle .trc files consuming large amounts of disc space [message #658123 is a reply to message #658122] Mon, 05 December 2016 04:20 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Here is the most recent alert log data (all of yesterday and today so far):

Sun Dec 04 12:59:29 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sun Dec 04 12:59:43 2016
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Setting Resource Manager plan SCHEDULER[0x4449]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Sun Dec 04 13:00:44 2016
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sun Dec 04 13:01:09 2016
Thread 1 cannot allocate new log, sequence 1020
Private strand flush not complete
  Current log# 2 seq# 1019 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Sun Dec 04 13:01:13 2016
Thread 1 advanced to log sequence 1020 (LGWR switch)
  Current log# 3 seq# 1020 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Sun Dec 04 13:01:15 2016
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P4183 (42707) VALUES LESS THAN (TO_DATE(' 2016-12-05 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P4186 (42707) VALUES LESS THAN (TO_DATE(' 2016-12-05 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Sun Dec 04 13:01:31 2016
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P4187 (2530) VALUES LESS THAN (TO_DATE(' 2016-12-05 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P4188 (2530) VALUES LESS THAN (TO_DATE(' 2016-12-05 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P4191 (2529) VALUES LESS THAN (TO_DATE(' 2016-12-04 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Sun Dec 04 13:02:54 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_9044.trc  (incident=85676):
ORA-00600: internal error code, arguments: [723], [144520], [73440448], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85676\orcl_j000_9044_i85676.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Sun Dec 04 13:59:32 2016
Sweep [inc][85676]: completed
Sweep [inc2][85676]: completed
Sun Dec 04 14:05:56 2016
Thread 1 advanced to log sequence 1021 (LGWR switch)
  Current log# 1 seq# 1021 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Sun Dec 04 15:03:13 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sun Dec 04 16:18:23 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sun Dec 04 17:54:49 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Sun Dec 04 17:55:31 2016
Thread 1 cannot allocate new log, sequence 1022
Private strand flush not complete
  Current log# 1 seq# 1021 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Sun Dec 04 17:55:35 2016
Thread 1 advanced to log sequence 1022 (LGWR switch)
  Current log# 2 seq# 1022 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Sun Dec 04 17:56:25 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_15408.trc  (incident=85684):
ORA-00600: internal error code, arguments: [723], [144520], [73440696], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85684\orcl_j000_15408_i85684.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Sun Dec 04 18:54:54 2016
Sweep [inc][85684]: completed
Sweep [inc2][85684]: completed
Mon Dec 05 00:37:57 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Mon Dec 05 00:38:32 2016
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P4207 (42708) VALUES LESS THAN (TO_DATE(' 2016-12-06 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P4210 (42708) VALUES LESS THAN (TO_DATE(' 2016-12-06 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Mon Dec 05 00:39:32 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j002_15224.trc  (incident=85692):
ORA-00600: internal error code, arguments: [723], [144520], [73440456], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85692\orcl_j002_15224_i85692.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Mon Dec 05 01:08:01 2016
Thread 1 advanced to log sequence 1023 (LGWR switch)
  Current log# 3 seq# 1023 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
Mon Dec 05 01:38:01 2016
Sweep [inc][85692]: completed
Sweep [inc2][85692]: completed
Mon Dec 05 02:00:01 2016
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Re: Oracle .trc files consuming large amounts of disc space [message #658124 is a reply to message #658123] Mon, 05 December 2016 04:33 Go to previous messageGo to next message
Littlefoot
Messages: 21364
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
BB

The problem continues with 2 or 3 trace files per day consuming about 1 gb per day
Are these TRC files listed in your last message (#658123), such as
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_9044.trc (incident=85676):

I know, it is AVG 300 MB per file, but - if you look at them, is there anything suspicious?
Re: Oracle .trc files consuming large amounts of disc space [message #658128 is a reply to message #658123] Mon, 05 December 2016 04:48 Go to previous messageGo to next message
Michel Cadot
Messages: 65387
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

ORA-600 723 is a memory leak in PGA (all Oracle versions) detected at logoff time.
The best thing to do, in my opinion, is to determine which job was completing at this time, see if it is mandatory and if not disable it.

Re: Oracle .trc files consuming large amounts of disc space [message #658129 is a reply to message #658124] Mon, 05 December 2016 05:13 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Littlefoot wrote on Mon, 05 December 2016 02:33
BB

The problem continues with 2 or 3 trace files per day consuming about 1 gb per day
Are these TRC files listed in your last message (#658123), such as
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_9044.trc (incident=85676):

I know, it is AVG 300 MB per file, but - if you look at them, is there anything suspicious?
The following is the contents of

c:\app\baboehme\diag\rdbms\orcl\orcl\incident\incdir_85676\orcl_j000_9044_i85676.trc

without the repetitive sections beginning with Chunk that consumes the most space, expect for the first and last 3 such sections, where indicated by my comment line.

A lot of lines here


[LF applied spoiler tags, to shorten the message]

[Updated on: Mon, 05 December 2016 06:21] by Moderator

Report message to a moderator

Re: Oracle .trc files consuming large amounts of disc space [message #658130 is a reply to message #658128] Mon, 05 December 2016 05:17 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Michel Cadot wrote on Mon, 05 December 2016 02:48

ORA-600 723 is a memory leak in PGA (all Oracle versions) detected at logoff time.
The best thing to do, in my opinion, is to determine which job was completing at this time, see if it is mandatory and if not disable it.

How do I do that?

SCOTT@orcl_12.1.0.2.0> select count(*) from dba_jobs;

  COUNT(*)
----------
         0

1 row selected.
Re: Oracle .trc files consuming large amounts of disc space [message #658132 is a reply to message #658130] Mon, 05 December 2016 05:34 Go to previous messageGo to next message
Roachcoach
Messages: 1513
Registered: May 2010
Location: UK
Senior Member
How about dba_scheduler_jobs?

Also it might honestly be worth limiting the dumpfile size if you have no fix for this. You can always turn it back on if you need the full dumps for a while.
Re: Oracle .trc files consuming large amounts of disc space [message #658133 is a reply to message #658132] Mon, 05 December 2016 06:13 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Thanks Roachcoach.

This is the latest ORA-600 723 memory leak in the alert log:

Mon Dec 05 00:39:32 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j002_15224.trc  (incident=85692):
ORA-00600: internal error code, arguments: [723], [144520], [73440456], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_85692\orcl_j002_15224_i85692.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

This is some of the data from dba_scheduler_jobs

SCOTT@orcl_12.1.0.2.0> column job_name		format a30
SCOTT@orcl_12.1.0.2.0> column last_start_date	format a40
SCOTT@orcl_12.1.0.2.0> column last_run_duration format a30
SCOTT@orcl_12.1.0.2.0> select job_name, state, failure_count, last_start_date, last_run_duration
  2  from   dba_scheduler_jobs
  3  order  by last_start_date+last_run_duration desc
  4  /

JOB_NAME                       STATE           FAILURE_COUNT LAST_START_DATE                          LAST_RUN_DURATION
------------------------------ --------------- ------------- ---------------------------------------- ------------------------------
FILE_WATCHER                   DISABLED                    0
XMLDB_NFS_CLEANUP_JOB          DISABLED                    0
LOAD_OPATCH_INVENTORY          DISABLED                    0
FGR$AUTOPURGE_JOB              DISABLED                    0
HM_CREATE_OFFLINE_DICTIONARY   DISABLED                    0
ORACLE_APEX_MAIL_QUEUE         SCHEDULED                   0 05-DEC-16 07.15.01.195000 AM -05:00      +000000000 00:00:00.010000
FILE_SIZE_UPD                  SCHEDULED                   0 05-DEC-16 07.10.39.174000 AM -05:00      +000000000 00:00:00.001000
ORACLE_APEX_PURGE_SESSIONS     SCHEDULED                   0 05-DEC-16 07.00.01.538000 AM -05:00      +000000000 00:00:00.007000
ORACLE_APEX_WS_NOTIFICATIONS   SCHEDULED                   0 05-DEC-16 07.00.01.194000 AM -05:00      +000000000 00:00:00.026000
CLEANUP_ONLINE_PMO             SCHEDULED                   0 05-DEC-16 06.55.39.371000 AM -05:00      +000000000 00:00:00.048000
CLEANUP_TRANSIENT_PKG          SCHEDULED                   0 05-DEC-16 06.55.31.160000 AM -05:00      +000000000 00:00:00.006000
CLEANUP_TAB_IOT_PMO            SCHEDULED                   0 05-DEC-16 06.55.09.395000 AM -05:00      +000000000 00:00:00.005000
CLEANUP_ONLINE_IND_BUILD       SCHEDULED                   0 05-DEC-16 06.55.01.166000 AM -05:00      +000000000 00:00:00.005000
CLEANUP_TRANSIENT_TYPE         SCHEDULED                   0 05-DEC-16 01.00.42.852000 AM -08:00      +000000000 00:00:00.107000
CLEANUP_NON_EXIST_OBJ          SCHEDULED                   0 05-DEC-16 01.00.25.576000 AM -08:00      +000000000 00:00:00.062000
PURGE_LOG                      SCHEDULED                   0 05-DEC-16 03.00.00.867000 AM US/CENTRAL  +000000000 00:00:00.686000
ORA$AUTOTASK_CLEAN             SCHEDULED                   0 05-DEC-16 03.00.00.926000 AM US/CENTRAL  +000000000 00:00:00.027000
ORACLE_APEX_DAILY_MAINTENANCE  SCHEDULED                   0 05-DEC-16 03.38.05.416000 AM -05:00      +000000000 00:00:02.125000
PMO_DEFERRED_GIDX_MAINT_JOB    SCHEDULED                   0 05-DEC-16 02.38.05.760000 AM US/CENTRAL  +000000000 00:00:01.469000
RSE$CLEAN_RECOVERABLE_SCRIPT   SCHEDULED                   0 05-DEC-16 02.38.05.338000 AM US/CENTRAL  +000000000 00:00:00.828000
SM$CLEAN_AUTO_SPLIT_MERGE      SCHEDULED                   0 05-DEC-16 02.38.05.338000 AM US/CENTRAL  +000000000 00:00:00.110000
BSLN_MAINTAIN_STATS_JOB        SCHEDULED                   0 04-DEC-16 04.00.18.902000 PM -05:00      +000000000 00:00:44.422000
DRA_REEVALUATE_OPEN_FAILURES   SCHEDULED                   0 04-DEC-16 03.00.22.574000 PM US/CENTRAL  +000000000 00:00:02.859000

23 rows selected.

I don't quite see how to figure out which job(s) were running when the error occurred.

[Updated on: Mon, 05 December 2016 06:16]

Report message to a moderator

Re: Oracle .trc files consuming large amounts of disc space [message #658134 is a reply to message #658133] Mon, 05 December 2016 06:18 Go to previous messageGo to next message
Michel Cadot
Messages: 65387
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Given the previous posts, maybe you can disable all APEX jobs and see if the error still comes, if not then enable these jobs one by one until you find the culprit.

Re: Oracle .trc files consuming large amounts of disc space [message #658135 is a reply to message #658134] Mon, 05 December 2016 06:38 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
Michel Cadot wrote on Mon, 05 December 2016 04:18

Given the previous posts, maybe you can disable all APEX jobs and see if the error still comes, if not then enable these jobs one by one until you find the culprit.

Done. I will have to wait and see what happens tomorrow. Thanks for your continued support.

SCOTT@orcl_12.1.0.2.0> select job_name, state
  2  from   dba_scheduler_jobs
  3  where  job_name like '%APEX%'
  4  /

JOB_NAME                       STATE
------------------------------ ---------------
ORACLE_APEX_DAILY_MAINTENANCE  DISABLED
ORACLE_APEX_WS_NOTIFICATIONS   DISABLED
ORACLE_APEX_MAIL_QUEUE         DISABLED
ORACLE_APEX_PURGE_SESSIONS     DISABLED

4 rows selected.

Re: Oracle .trc files consuming large amounts of disc space [message #658136 is a reply to message #658100] Mon, 05 December 2016 07:10 Go to previous messageGo to next message
Littlefoot
Messages: 21364
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Littlefoot wrote on Sat, 03 December 2016 20:53

If you don't use Apex, you most probably don't need these jobs to run at all so - stop them; why would they fill the log file?

Right; altough, I never met such problems with my Apex (and I use it since 2009) so - maybe Apex jobs won't solve the problem (I wish they would!).
Re: Oracle .trc files consuming large amounts of disc space [message #658149 is a reply to message #658136] Mon, 05 December 2016 18:52 Go to previous messageGo to next message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
This morning everything had a problem. I had a bad case of acid reflux and insomnia in the middle of the night last night, so I sat up and watched television and used my computer to browse the OraFAQ forums and such, which is when I posted here, during the early morning hours. So, after I finally went back to bed, I overslept and was awakened about 9 a.m. by somebody yelling and banging on my gate. It turned out to be the gas company, here to replace the gas regulator, without telling me in advance that they would be coming. The safety shield to prevent vehicles from hitting the gas meter was in the way, so he had to saw through the pipe to the old regulator. The new regulator leaked, but he fortunately had another that didn't, so that was fixed. After that, one of my cats got out, but with the help of a little salmon fancy feast, I got him back inside. By the time I got things done and got to breakfast it was lunchtime.

Eventually, I started up my computer, but Firefox seemed to freeze and I couldn't even shut it down, so I re-started the whole computer. After re-starting the computer, I got a message that Firefox had crashed, but this time I was able to close it and start a new session, so Firefox is working again now. I checked my Oracle alert log and found that the Oracle database had recovered from a crash.

I have done a little searching and received some suggestions from multiple sources regarding the memory leak issue, that say that minor memory leaks are common and inconsequential and can be ignored, and suggest setting the following in the init.ora in order to ignore small memory leaks to keep from cluttering the disk with trace files:

event = "10262 trace name context forever, level 4000"

However, I am apparently using an spfile:

SCOTT@orcl_12.1.0.2.0> show parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string      C:\APP\BABOEHME\PRODUCT\12.1.0
                                                 \DBHOME_2\DATABASE\SPFILEORCL.
                                                 ORA
SCOTT@orcl_12.1.0.2.0>

SCOTT@orcl_12.1.0.2.0> show parameter event

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
event                                string
xml_db_events                        string      enable
SCOTT@orcl_12.1.0.2.0>

So, I did the following:

SCOTT@orcl_12.1.0.2.0> alter system set event = '10262 trace name context forever, level 4000' scope=spfile
  2  /

System altered.

SCOTT@orcl_12.1.0.2.0> show parameter event

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
event                                string
xml_db_events                        string      enable
SCOTT@orcl_12.1.0.2.0>

Then, I re-started the database and now I see:

SCOTT@orcl_12.1.0.2.0> show parameter event

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
event                                string      10262 trace name context forev
                                                 er, level 4000
xml_db_events                        string      enable
SCOTT@orcl_12.1.0.2.0>

So, now I am waiting to see what happens.

I need to stop and get some things done before it gets dark. Where did the day go?



[Updated on: Mon, 05 December 2016 20:49]

Report message to a moderator

Re: Oracle .trc files consuming large amounts of disc space [message #658165 is a reply to message #658149] Tue, 06 December 2016 01:36 Go to previous messageGo to next message
Littlefoot
Messages: 21364
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Barbara Boehmer

Where did the day go?

I know you're somewhere in California (don't know where exactly, though). As it is late Autumn, in Los Angeles daylight lasts only 10 hours (today's sunrise and sunset times are 06:44 & 16:44) so - that's where it went. Into the darkness. /forum/fa/10057/0/
Re: Oracle .trc files consuming large amounts of disc space [message #658167 is a reply to message #658149] Tue, 06 December 2016 01:48 Go to previous messageGo to next message
Michel Cadot
Messages: 65387
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

Wow, as Shakespeare said:
When sorrows come, they come not single spies
But in battalions.

(or one of former French president: hassles are like airplanes, they fly in squadron. Sad )

Re: Oracle .trc files consuming large amounts of disc space [message #658174 is a reply to message #658167] Tue, 06 December 2016 04:24 Go to previous message
Barbara Boehmer
Messages: 8804
Registered: November 2002
Location: California, USA
Senior Member
After everything, I still get another huge trace file and the following, including the memory leak (apparently not small enough to ignore), in the alert log. It looks like the time drifts and/or memory leak are the source(s) of the huge trace file. So, I guess I will just delete the trace files periodically, after checking the alert log, to make sure that there isn't anything else new that I need to know about.

Tue Dec 06 01:02:56 2016
Warning: VKTM detected a time drift.
Time drifts can result in an unexpected behavior such as time-outs. Please check trace file for more details.
Tue Dec 06 01:03:04 2016
Setting Resource Manager plan SCHEDULER[0x4443]:DEFAULT_MAINTENANCE_PLAN via scheduler window
Setting Resource Manager plan DEFAULT_MAINTENANCE_PLAN via parameter
Tue Dec 06 01:03:23 2016
Begin automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Tue Dec 06 01:03:45 2016
Thread 1 cannot allocate new log, sequence 1025
Private strand flush not complete
  Current log# 1 seq# 1024 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO01.LOG
Tue Dec 06 01:03:50 2016
Thread 1 advanced to log sequence 1025 (LGWR switch)
  Current log# 2 seq# 1025 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO02.LOG
Tue Dec 06 01:04:18 2016
TABLE SYS.WRI$_OPTSTAT_HISTHEAD_HISTORY: ADDED INTERVAL PARTITION SYS_P4232 (42709) VALUES LESS THAN (TO_DATE(' 2016-12-07 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRI$_OPTSTAT_HISTGRM_HISTORY: ADDED INTERVAL PARTITION SYS_P4235 (42709) VALUES LESS THAN (TO_DATE(' 2016-12-07 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
Tue Dec 06 01:04:33 2016
TABLE SYS.WRP$_REPORTS: ADDED INTERVAL PARTITION SYS_P4236 (2532) VALUES LESS THAN (TO_DATE(' 2016-12-07 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_DETAILS: ADDED INTERVAL PARTITION SYS_P4237 (2532) VALUES LESS THAN (TO_DATE(' 2016-12-07 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
TABLE SYS.WRP$_REPORTS_TIME_BANDS: ADDED INTERVAL PARTITION SYS_P4240 (2531) VALUES LESS THAN (TO_DATE(' 2016-12-06 01:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
End automatic SQL Tuning Advisor run for special tuning task  "SYS_AUTO_SQL_TUNING_TASK"
Tue Dec 06 01:05:59 2016
Thread 1 advanced to log sequence 1026 (LGWR switch)
  Current log# 3 seq# 1026 mem# 0: C:\APP\BABOEHME\ORADATA\ORCL\REDO03.LOG
Tue Dec 06 01:06:39 2016
Errors in file C:\APP\BABOEHME\diag\rdbms\orcl\orcl\trace\orcl_j000_1640.trc  (incident=90500):
ORA-00600: internal error code, arguments: [723], [144520], [73440392], [memory leak], [], [], [], [], [], [], [], []
Incident details in: C:\APP\BABOEHME\diag\rdbms\orcl\orcl\incident\incdir_90500\orcl_j000_1640_i90500.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

Tue Dec 06 02:00:03 2016
Closing scheduler window
Closing Resource Manager plan via scheduler window
Clearing Resource Manager plan via parameter
Tue Dec 06 02:03:01 2016
Sweep [inc][90500]: completed
Sweep [inc2][90500]: completed

[Updated on: Tue, 06 December 2016 04:43]

Report message to a moderator

Previous Topic: Can we find blocking query by tracing?
Next Topic: Validating external libraries in oracle 11g - AIX
Goto Forum:
  


Current Time: Wed Feb 21 18:01:09 CST 2018

Total time taken to generate the page: 0.03165 seconds