Printable View
Hi all,
I am having a serious problem here.
My database was working fine all these days, but recently, it has started crashing a lot. If I run more than 5 queries continously, the database crashes & then I need to restart it.
I have never come across such a scene before.
Does any one know what could be reason for this?
I am using Oracle 8.1.6 on solaris - evaluation copy.
Shiva.
What does it say in the alert log when it crashes?
My Alert log says :
Can not allocate log, archival required
Tue Jan 16 11:46:09 2001
ARCH: Connecting to console port...
Thread 1 cannot allocate new log, sequence 3473
All online logs needed archiving
Current log# 1 seq# 3472 mem# 0: /oracle8/dbms/oradata/perseus/redo01.log
Does this mean that something is wrong with my RedoLOG files??
Shiva
The redo log files are too small. Drop and recreate them with a larger size.
check whether you have disk space where you have archive log detination or shutdown the database and turn into noarchive log
Pls issue
alter system checkpoint
shutdown immediate
startup mount
alter database noarchivelog ;
If you're running in archive log mode, have you set "log_archive_start = true" in your init.ora so it archives them automatically?
the alert log says that he is unable to do the archving...
It just should be that he does not enough space for redo log files to be archived .That is the reason i am asking him to clear the archive log file..check the space in the disk where the archive log dest is there ...
turn to noarchive log ...
since he is not backing the database....(I don't think he is doing)
Well it says "All online logs need archiving". If he has archiving turned on, but not automatic archiving, and he didn't manually archive them, wouldn't it give a message that said that the logs required archival since he didn't do it?
Hi all,
Thanks for the responses.
I checked my init.ora file & it says "log_archive_start = false".
Do I need to do it manually, or can I just open my DB in noarchive mode?
Shiva.
You make it to noarchivelog...
As long as you don't want/need archiving you can open in noarchivelog and not worry about the problem. However if you do want it in archivelog mode, set log_archive_start = true instead of false. You have to bounc the database after any changes in the init.ora for them to take effect.
Thanks everyone.
I have opened my database in 'NOARCHIVELOG' mode.
I need to work on it more to see if it crashes or not.
If it still crashes, I shall again return back to the same forum.
Thanks again for all your help.
Shiva.
hi!
It is not a good idea to run your database in no archivelog mode, if it's a production database. You may loose data if the database crashes.
Keep in archive log mode. Give enough space to archivelog destination. After each backup delete the archives. Make the process in cron script.
abhijit
If you don't want to runi in archivelog mode, mount the database and disable archivelog mode by using the following comand.
svrmgrl> startup mount;
svrmgrl>alter database noarchivelog;
svrmgrl>alter database open;
Thanks,
Bhaskar
If you restart your databse in noarchivelog mode then remember that your backup strategies change entirely.
I guess that there is not enough space in the archive destination.
Why dont you move some of your older archive logs elsewhere and free up disk space.
Also if you are backing up and change to noarchivelog mode then you have to take a full database backup(closed) again.
Nizar.
This is not a production database and there is no backup involved. So I guess running the database in noarchive mode is not going to be too dangerous.
Thanks again for all your responses.
I have learnt a lot from all you guys.
Shiva.
If you think, you need this database and you have to recover it when you loose, you need to have some type of backup exp/cold backup/hotbackup with archive logs.
Justify yourself and have some plan. Sometimes we do neglect and endup having tough time when the situation arise.
Just a reminder.
The error message is not saying anything about space problem. It says files to be archived manually which has already been set in control files.
So comment the above parameter, mount the database and then disable the archivelog as below.
svrmgrl>startup mount;
svrmgrl>alter database noarchivelog;
svrmgrl>alter database open;
Thanks,
Bhaskar
[Edited by Bhaskara on 01-17-2001 at 11:48 AM]