Leslie,
The trace file should have the current SQL for the
session that generated the error and I suspect it has
nothing to do with the drop tablespace command. The
ORA-600 [18062] is signaled as part of the two-phase
commit process when it attempts to get the current
globally unique database ID
Leslie,
It appears that there is an action occuring on your database at 18:20
each day that needs the tablespace that was deleted. It might be a
scheduled job or an application that is external to the server. try
restoring the tablespace from your backup and see if the errors
continue.
I also wo
Hi Ron,
Thank you! Actually the "Dropping TS" only happened
on 7/15. There are no other special actions since
7/15. And after 7/15, the error shows after "alter
database open".
Sorry didn't make it clear.
--- Ron Rogers <[EMAIL PROTECTED]> wrote:
> Leslie,
> You say the message appears at
Leslie,
You say the message appears at 18:20 each day. Check and see what jobs
have been added to the system since 7/15 that would effect the database.
Perhaps an erronious, undocumented action has been added that is
altering your system and dropping a critical tablespace.
Why would you want to
open an iTAR.
Reply Separator
Author: Leslie Lu <[EMAIL PROTECTED]>
Date: 7/23/2002 11:54 AM
Hi all,
I have a 817 db on NT. In the alter log, I have the
following error since 7/15. (The error repeats about
30 times.)
Mon Jul 15 16:11:32 2002
Erro