cancel
Showing results for 
Search instead for 
Did you mean: 

effect of executing db_offline when users are still logged in

Former Member
0 Kudos

Dear All,

We want to implement scheduled shutdown of SAP.

If we stop first the database, what will happen if the users

are still logged or in the middle of processing a transaction?

Will it corrupt the data?

When the log area is full, the database also stops, though not

totally offline and the effect on the users is that SAP gui hangs.

Is the effect the same?

Any information is greatly appreciated.

Thank you very much.

Regards,

Rayel

Accepted Solutions (0)

Answers (2)

Answers (2)

debasissahoo
Active Contributor
0 Kudos

Hi Rayel,

If there is a scheduled outage, its better to always shutdown SAP before you bring database down.

If you shutdown the database while users are connected, then it depends on how you use the shutdown command. oracle shutdown default option is immediate. which closes all the connection to user in database level and then shuts down the database. if you use other option normal/transactional it might take a lot of time to shutdown the database as it will wait for users to finish their work. however, you shouldn't try the abort option which will need recovery of the database next time its opened.

http://help.sap.com/saphelp_NW70EHP1/helpdata/en/fe/2bdfa2fffe974aba6cea92667fd6fe/content.htm

If SAP is up and database is down, then work process will be in a status of "reconnect" status trying to reconnect to the database shadow process. Once the database is up, the work process automatically gets the connection established.

In the log full case, SAP will be up and running, however Oracle can't write the data to log area everything will be hung. Symptoms may be similar in both the cases.

Regards,

Debasis.

Former Member
0 Kudos

Hi Rayel Dacx,

If we stop first the database, what will happen if the users are still logged or in the middle of processing a transaction?

It is standard practice that while stopping the SAP system you first have to stop the SAP Instance & then Database. If you are not doing this may create data courruption or other issues.

When the log area is full, the database also stops, though not totally offline and the effect on the users is that SAP gui hangs.
Is the effect the same?

This situation is known as Archiver Stuck. It does not shutdown the database or R/3 system.

If you want to schedule Offline Backup see the link

[;

Thanks,

Shambo