Yes, the log reports every ORA- Error seperatly. Here are some excerpts:
Thu Feb 7 09:44:40 2008
Errors in file /ora/app/oracle/admin/INSTANCE/udump/instance_ora_19929.trc:
ORA-00600: internal error code, arguments: [17182], [0x0B6F41C08], [], [], [], [], [], []
Tue Mar 18 22:19:51 2008
Errors in file /ora/app/oracle/admin/INSTANCE/udump/instance_ora_21413.trc:
ORA-27037: unable to obtain file status
Tue Mar 18 22:28:29 2008
Thread 1 advanced to log sequence 10531
Current log# 2 seq# 10531 mem# 0: /u01/oradata/INSTANCE/redo02m1.dbf
Current log# 2 seq# 10531 mem# 1: /u01/oradata2/INSTANCE/redo02m2.dbf
Wed Mar 19 07:03:05 2008
Errors in file /ora/app/oracle/admin/INSTANCE/bdump/instance_arc1_9854.trc:
ORA-16038: log 3 sequence# 10532 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 3 thread 1: '/u01/oradata/INSTANCE/redo03m1.dbf'
ORA-00312: online log 3 thread 1: '/u01/oradata2/INSTANCE/redo03m2.dbf'
So for every "event" it lists the date, some additional info i.e. where the error occured and the errorcode(s) itself (if it's an error that got loged), each in a seperate line. There's no summary like the one we get sent by Hyperic HQ anywhere in the logfile.
Message was edited by: David