Yeah, it looks like theres something quirky happening with SMON.

Errors in file c:\oracle\product\10.2.0\admin\orcvista\bdump\orcvista_smon_3436.trc:
ORA-00600: internal error code, arguments: [25027], [0], [16776974], [], [], [], [], []

Tue Jun 05 13:35:58 2007
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Tue Jun 05 13:36:02 2007
Completed: alter database open
Tue Jun 05 13:36:03 2007
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Tue Jun 05 13:41:02 2007
Errors in file c:\oracle\product\10.2.0\admin\orcvista\bdump\orcvista_smon_3436.trc:
ORA-00600: internal error code, arguments: [25027], [0], [16776974], [], [], [], [], []

Tue Jun 05 13:41:03 2007
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Tue Jun 05 13:46:04 2007
Errors in file c:\oracle\product\10.2.0\admin\orcvista\bdump\orcvista_smon_3436.trc:
ORA-00600: internal error code, arguments: [25027], [0], [16776974], [], [], [], [], []

Tue Jun 05 13:46:05 2007
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 3 out of maximum 100 non-fatal internal errors.

Can you make any possible suggestions? I tried viewing the trace file referenced in the alert log but most of the info is so cryptic I can't make heads or tails of it. Is there any tool that I could use to make better use of the trace file other than viewing the data in notepad???

thx