REQUEST:trace dump in directory cdmp_***

I found cdmp**** folders on Database of every nodes:
They created by Oracle Diag:
(REQUEST:trace dump in directory cdmp***)

$ tail db1_diag_16582.trc

REQUEST:trace dump in directory cdmp_20080604120000
Trace dumping is performing id=[cdmp_20080604120000]....
*** 2008-06-04 12:00:01.546
Trace dumping is done
*** 2008-06-04 12:00:53.232
A dump event msg is rcv'd
REQUEST:trace dump in directory cdmp_20080604120052
Trace dumping is performing id=[cdmp_20080604120052]....
*** 2008-06-04 12:00:54.623
Trace dumping is done

$ls -la
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:49 cdmp_20080604114916
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:50 cdmp_20080604115007
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:50 cdmp_20080604115058
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:51 cdmp_20080604115148
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:52 cdmp_20080604115239
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:53 cdmp_20080604115334
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:54 cdmp_20080604115433
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:55 cdmp_20080604115521
drwxr-x--- 2 oracle oinstall 4096 Jun 4 11:56 cdmp_20080604115610
drwxr-x--- 2 oracle oinstall 4096 Jun 4 12:00 cdmp_20080604120000

They made disk PATH be full.

...........................................

So, I checked about Database.

I found a problem about datafile:

SQL> select * from V$DATABASE_BLOCK_CORRUPTION;

FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# CORRUPTIO
---------- ---------- ---------- ------------------ ---------
49 515632 1 8.3019E+12 LOGICAL
49 463340 5 8.3019E+12 LOGICAL

SQL> select * from v$backup_corruption;

RECID STAMP SET_STAMP SET_COUNT PIECE# FILE# BLOCK# BLOCKS CORRUPTION_CHANGE# MAR CORRUPTIO
---------- ---------- ---------- ---------- ---------- ---------- ---------- ---------- ------------------ --- ---------
1805 656488622 656488411 28602 1 49 463340 5 8.3019E+12 NO LOGICAL
1806 656488622 656488411 28602 1 49 515632 1 8.3019E+12 NO LOGICAL


After that, I used blockrecover by RMAN:

run{
allocate channel t1 type disk;
allocate channel t2 type 'SBT_TAPE';
BACKUP VALIDATE DATABASE;
BLOCKRECOVER CORRUPTION LIST;
}

..........................
That's resolve; REQUEST:trace dump in directory cdmp cdmp***

.........................

something wrong or Bug on SCHEDULER: after Patch 10.2.0.4 on linux x86_64

After I patched Oracle database 10.2.0. linux x86_64, I found something wrong about Scheduler Job.

I have created "TEST" Scheduler Job:

SQL> select job_name, repeat_interval, state from user_scheduler_jobs where job_name='TEST';

JOB_NAME REPEAT_INTERVAL STATE
-------------------- ------------------------------ ----------
TEST FREQ=MINUTELY SCHEDULED

My job should run every minutes, But I found It haven't done like that.

JOB_NAME STATUS REQ_START_DATE ACTUAL_START_DATE
---------- --------------- --------------------------------------------- ---------------------------------------------
RUN_DURATION ERROR#
------------- ----------
+000 00:00:00 0

TEST SUCCEEDED 31-MAY-08 03.15.42.000000 AM ASIA/BANGKOK 31-MAY-08 03.15.42.102738 AM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 31-MAY-08 03.16.42.000000 AM ASIA/BANGKOK 01-JUN-08 12.57.23.500716 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 12.57.42.000000 PM ASIA/BANGKOK 01-JUN-08 01.07.19.938139 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 01.07.42.000000 PM ASIA/BANGKOK 01-JUN-08 01.27.57.945628 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 05.09.42.000000 PM ASIA/BANGKOK 01-JUN-08 05.20.35.476359 PM ASIA/BANGKOK
+000 00:00:01 0

TEST SUCCEEDED 01-JUN-08 05.20.42.000000 PM ASIA/BANGKOK 01-JUN-08 05.21.15.454726 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 05.21.42.000000 PM ASIA/BANGKOK 01-JUN-08 05.31.04.582346 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 05.31.42.000000 PM ASIA/BANGKOK 01-JUN-08 11.18.02.179848 PM ASIA/BANGKOK
+000 00:00:00 0

JOB_NAME STATUS REQ_START_DATE ACTUAL_START_DATE
---------- --------------- --------------------------------------------- ---------------------------------------------
RUN_DURATION ERROR#
------------- ----------

TEST SUCCEEDED 01-JUN-08 11.18.42.000000 PM ASIA/BANGKOK 01-JUN-08 11.48.32.325631 PM ASIA/BANGKOK
+000 00:00:00 0

TEST SUCCEEDED 01-JUN-08 11.48.42.000000 PM ASIA/BANGKOK 02-JUN-08 06.10.06.902078 AM ASIA/BANGKOK
+000 00:00:00 0


I'm not sure I patched to resolve Bug or increase more ... Bug on my system......

Solved =>

SQL> select * from DBA_SCHEDULER_GLOBAL_ATTRIBUTE where attribute_name='CURRENT_OPEN_WINDOW';

ATTRIBUTE_NAME  VALUE
---------------------   ---------
CURRENT_OPEN_WINDOW WEEKNIGHT_WINDOW

SQL> exec DBMS_SCHEDULER.close_window ('WEEKNIGHT_WINDOW');

PL/SQL procedure successfully completed.

SQL> select * from DBA_SCHEDULER_GLOBAL_ATTRIBUTE where attribute_name='CURRENT_OPEN_WINDOW';

ATTRIBUTE_NAME   VALUE
---------------------   ---------
CURRENT_OPEN_WINDOW

Force to close by "DBMS_SCHEDULER.close_window"