ORA-604 error

[Former Member]

(I'm using Oracle 10.2.0.4, on Linux RedHat)

I'm getting this error every hour but the system datafiles are on line....

Errors in file /oracle/PB1/saptrace/background/pb1_smon_36600.trc:

ORA-00604: error occurred at recursive SQL level 1

ORA-00376: file 1 cannot be read at this time

ORA-01110: data file 1: '/oracle/PB1/sapdata1/system_1/system.data1'

adcsdb2:orapb1 77> oerr ora 604

00604, 00000, "error occurred at recursive SQL level %s"

// *Cause: An error occurred while processing a recursive SQL statement

// (a statement applying to internal dictionary tables).

// *Action: If the situation described in the next error on the stack

// can be corrected, do so; otherwise contact Oracle Support.

adcsdb2:orapb1 79> oerr ora 376

00376, 00000, "file %s cannot be read at this time"

// *Cause: attempting to read from a file that is not readable. Most likely

// the file is offline.

// *Action: Check the state of the file. Bring it online

adcsdb2:orapb1 80> oerr ora 1110

01110, 00000, "data file %s: '%s'"

// *Cause: Reporting file name for details of another error

// *Action: See associated error message

[Former Member]

How is your storage attached?

Local disks, SAN, ... ?

Might there be any hiccup?

[Former Member]

0) The storage is NetApp and the database backups are done through NetApp's SMSAP utility

1)

I mv'ed the old alert log to a saved copy.

The alert logs have no ORA-#### errors

so the main issue is why is there a hourly trace file.

2)

But I am getting these trc file hourly: pb1_m001_#####.trc

2)

And they are have this message (except for the date & Time):

/oracle/PB1/saptrace/background/pb1_m001_11287.trc

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production

With the Partitioning, Data Mining and Real Application Testing options

ORACLE_HOME = /oracle/PB1/102_64

System name: Linux

Node name: adcsdb2

Release: 2.6.18-238.12.1.el5

Version: #1 SMP Sat May 7 20:18:50 EDT 2011

Machine: x86_64

Instance name: PB1

Redo thread mounted by this instance: 1

Oracle process number: 106

Unix process pid: 11287, image: oracle@adcsdb2 (m001)

• ACTION NAME:(Auto ADDM Slave Action) 2011-07-29 08:00:24.704

• MODULE NAME:(MMON_SLAVE) 2011-07-29 08:00:24.704

• SERVICE NAME:(SYS$BACKGROUND) 2011-07-29 08:00:24.704

• SESSION ID:(554.28306) 2011-07-29 08:00:24.704

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

4)

In the alert log the only thing happeing at this time is:

Fri Jul 29 07:37:05 2011

Completed checkpoint up to RBA [0x9438.2.10], SCN: 604506724

Fri Jul 29 08:00:26 2011

ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18090'

Fri Jul 29 08:00:27 2011

Completed: ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18090'

Fri Jul 29 08:00:27 2011

ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18091'

Completed: ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18091'

Fri Jul 29 08:00:27 2011

ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18092'

Completed: ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS '/tmp/SM_18092'

Fri Jul 29 08:00:28 2011

ALTER DATABASE BEGIN BACKUP

Fri Jul 29 08:00:37 2011

Completed: ALTER DATABASE BEGIN BACKUP

Fri Jul 29 08:03:05 2011

5) Can 'ALTER DATABASE BACKUP CONTROLFILE' cause an hourly trc file?

[Former Member]

Hello!

I found the answer in MetaLink....

After Upgrading To 10.2.0.4 Receiving Mmon Trace Files With Message [kdl_trim]: newlen [ID 567307.1]

________________________________________

Modified 03-MAR-2011 Type PROBLEM Status PUBLISHED

In this Document

Symptoms

Cause

Solution

References

________________________________________

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.4 to 10.2.0.4 - Release: 10.2 to 10.2

Information in this document applies to any platform.

**Checked for relevance on 07-Jan-2010**

Symptoms

After upgrading database to 10.2.0.4,mmon generates trace files every hour.

Trace file content,

• ACTION NAME:(Auto ADDM Slave Action) 2008-03-26 16:00:31.890

• MODULE NAME:(MMON_SLAVE) 2008-03-26 16:00:31.890

• SERVICE NAME:(SYS$BACKGROUND) 2008-03-26 16:00:31.890

• SESSION ID:(625.3179) 2008-03-26 16:00:31.890

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

[kdl_trim]: newlen: 0

Cause

This is due to the unpublished 6972843 which is fixed in 10.2.0.5.

Solution

1) These trace files are unnecessary and we can disregard / delete them.

Or

2) Apply the patch for the unpublished 6972843 if its available for your OS.

The issue is fixed in the 10.2.0.5 patchset.