this is the extract of my alertlog,pl help soon-
thread 1 cannot allocate new log,sequence 1036
all online logs need archivelog
shutting down instance
ora-00600-internal error code,arguments :,,,,,
hello,and thanks for response
yesterday I recreated a database in archivelog mode.previously it was in noarchivelog mode.
today morning i saw some errors in alertlog like this-
ARC0: Beginning to archive log# 1 seq# 1021
Mon Nov 06 11:47:19 2000
Thread 1 cannot allocate new log, sequence 1023
All online logs needed archiving
Current log# 2 seq# 1022 mem# 0: E:\ORACLE\ORADATA\ORTEL\REDO02.LOG
Mon Nov 06 11:47:21 2000
ARC0: Completed archiving log# 1 seq# 1021
ARC0: re-scanning for new log files
ARC0: prodding the archiver
ARC0: STARTING ARCH PROCESSES
ARC1: Failed to archive log# 2 seq# 1022
so on seeing this i changed the parameters in init.ora
as i am not being able to connect as internal -
so i cant do alter database noarchivelog;
restarted the db.
within 5 minutes i got this errors
oracle error during redolog archival ,cannot allocate log
as previuosly stated-
can u get it?hurry pl.
so basically you are still in archivelog, why you cant connect with internal? Do you use passwordfile, if you do you can connect with sys or system with sysdba or sysoper role to startup or shutdown the database.
Is it in UNIX or NT, production or development
alter system archive log start to '/another_directory';
to change the directory of archive logs
alter system archive log stop;
this will stop archive process ARCH0 & ARCH1