cancel
Showing results for 
Search instead for 
Did you mean: 

Database not shutting down

Former Member
0 Kudos

Hi,

Archive (oraarch) file system was full yesterday midnight. instead of deleting old redo log , we deleted recent redo logs.

we are not able to logon to sap also try to restart the sever DB not shutting down.

How to resolve the problem. Kindly help me.

OS - AIX 5.3

DB - oracle 10.2.0.2

kvl

Edited by: KulandaivelS on Jul 6, 2010 12:12 PM

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos
sql>shutdown abort 
sql>startup

Do not use shutdown abort until unless you have expertise skills in recovery process.

If you have deleted archivelogs under archive directory, doesn't matter (in your situation).

Just login into your SAP system and you can work normal.

Regards,

Nick Loy

Former Member
0 Kudos

Just some Tipps.

If your oraarch was full and you got an archiver stuck and deleted the offline redo logs without backupping them do a full backup.

Else you´ll run into problems when you have to restore the system.

Also to help you when you had such a stuck sap suggests to have a file within oraarch thats around 500MB big. So when run into a archiver stuck you can just delete that file. If you just backup the current files in there it takes longer as oracle will immediately after one file is backuped write its other redolog to disk and the filesystem is full again.

@Topic

please have a post related alert log files.

Former Member
0 Kudos

Hi,

No need to restart the batabase. As you see oraarch is full immediately check the overview of redo log files in redo log backup's. If there are some redo log files first backup those redo log files and the space will be cleared in oraarch.

Former Member
0 Kudos

Hi ,

Not required to stop db , if archive log was filled .

pls take the backup of archivelog and delete the arch files .

your Actual issue is SAP is not working becoz of Archivelog 100 % and DB may gone Inconsistant .

so u can stop DB using SQL :

sqlplus /nolog

connect /as sysdba

u wil be connected to Oracle .

>shutdown abort

>startup

or even if the DB is not start ...try to stop DB throudg Brtools and try to start SAP also .

It should work...

Regards

Former Member
0 Kudos

Hi ,

Not required to stop db , if archive log was filled .

pls take the backup of archivelog and delete the arch files .

your Actual issue is SAP is not working becoz of Archivelog 100 % and DB may gone Inconsistant .

so u can stop DB using SQL :

sqlplus /nolog

connect /as sysdba

u wil be connected to Oracle .

sql>shutdown abort

sql>startup

or even if the DB is not start ...try to stop DB through Brtools and start Db and try to start SAP also .

It should work...

Regards

0 Kudos

Hi,

as you deleted the archive logs, you should be able to login in SAP as archive dir will have free space.

i don't know the reason why you want to shutdown the DB. if u want you can bring down with shutdown abort cmd

if backup task is not going on at that time of archive struck then there is no problem

if you deleted the logs for which db is in backup mode then you should go for restore..

Regards,

navin

Former Member
0 Kudos

Hi

Hope the below link will help you

http://www.oracle-dba-online.com/managing_redo_logfiles.htm

Regards

Sirigiri