Database shutdown when online backup is running

[Former Member]

Hi All,

By mistakenly oracle has been shutdown when an online backup is running what would be the effects.Since we are not able to get oracle and lot of process exist as defunct even after shutdown abort.How should we proceed.Thanks.

[Former Member · Accepted solution]

You are clubbing different issues in one message.

1) Initial issue was related to DB recovery (refer 4161 and 4162 )

Just exectue the script attached in 4162 to bring up your DB

2) Then try to start SAP (This is different issue related to SAP Instance connectivity)

If you are facing shared memory issue, you can freed-up with cleanipc command OR you can reboot the server.

Let us know the current status.

Regards,

Nick Loy

[Former Member]

Refer SAP Note 4161 and 4162.

Regards,

Nick Loy

[Former Member]

logon to database SQL level and run

SQL>ALTER DATABASE BEGIN BACKUP;

to verify:

SQL>select file#,status from v$backup;

FILE# STATUS

-

---

-

---

1 NOT ACTIVE

2 NOT ACTIVE

3 NOT ACTIVE

4 NOT ACTIVE

-- All the datafiles are out of backup mode now.

Start SAP if not running.

[former_member204746]

simple command:

alter database end backup;

there ya go. problem fixed!

[Former Member]

Hi Eric,

As of now oracle has been shutdown.Should i start it up in no mount and then execute the command.Thanks.

[Former Member]

Hi,

Here you go...

startup mount;
alter database end backup;
alter database open;

Regards,

Varadharajan M

[former_member204746]

you an also do this:

startup;

alter database end backup;

[Former Member]

The database was not mounting and even the shared memory was not getting released with ipcrm.Finally had to restart the server.

[former_member188883]

Hi,

Take a server reboot.

Then start the database with above mentioned commands.

After starting database check R3trans -d to ensure proper database connectivity.

Regards,

Deepak Kori

[Former Member]

Hi,

Post us the error message and the last few lines of alret log file. That will help us guide you.

Regards,

Varadharajan M

[Former Member]

Hi ,

Pls use the command ipcrm as per note 4557.

see note 17108 as for the cleanipc command.

the shared memory segments that have to be

removed by the commands I mentioned before Or an OS restart which is themost effective way for this. (although I understand that this could be

unwanted).

Next time ensure that all of the systems processes have stopped. If

necessary, run the files kill.sap and shutdown.sap in the SAP System

Working Directory. (/usr/sap/<system-name>/<unit name>/work). Ensure

that all IPC objects (shared mem, semaphores, ...) have been deleted.

(showipc <system-no) bzw. cleanipc <system-no>). Delete file sapstart.

sem.

Regards

[Former Member]

even the ipcrm was not working.Had to reboot the server.I know this was the wrong way but had no other option.

[Former Member]

Hello,

Check the oracle alert.log. Do not forget to run "ALTER TABLESPACE ... END BACKUP" to startup the database.

Best regards,

Roger Vier

[Former Member]

Hi,

The very situation and the resolution steps are explained in the [SAP Note 4162|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=4162]

During the backup, the tablespaces will be in the backup state and at the end of the backup this will be changes. In case if the DB is shutdown while the backup is running the mode will remain in the backup state itself and thus allowing us not to stop/start the DB.

Hope this will resoves ur issue.

Regards,

Varadharajan M

[former_member185954]

Hello Ambarish,

First investigate the cause of the sudden failure as trying to restart database without fixing the cause might result into more errors.

I hope you have a successfull previous backup and REDO log backups with you. As killing Oracle processes most of the times results into RECOVERY of the database during next startup.

Regards,

Siddhesh