Database shutdown (immediate) hang - SAP Netweaver

[former_member482483]

Hi,

Everyday, we have a job to run the sap command 'stopsap' on our app and DB server and then follow by 'startsap'. However, recently we have a problem in our database not able to shutdown successfully (or hang).

Our database is Oracle database.

Based on feedback from dba, the current stop db command is 'shutdown immediate' and they suggest to use 'shutdown abort'.

My question is

1) What is the recommended frequency to restart the database? Is restarting it everyday too much?

2) Is it advisable to use 'shutdown abort' to force the database to down?

Please advise.

Thanks in advance.

[stefan_koehler]

Hi Wai,

> 1) What is the recommended frequency to restart the database? Is restarting it everyday too much?

Restart the system if needed by maintenance or whatever.

> Based on feedback from dba, the current stop db command is 'shutdown immediate' and they suggest to use 'shutdown abort'.

Sorry, but this is ridiculous. Your DBA should do his job and analyze this issue (common issue like "SMON: disabling tx recovery") or bugs (with oradebug short stack traces).

Regards

Stefan

[Former Member]

Addition to above:

I suggest you to apply latest available patches, fix the issue (if it is not realted to bug) then do not take any restarts without a requirement/genuine need.

Frequent restarts never give you any performance improvements etc, and infact there are some negative factors that leads to poor performance due to low buffer quality etc.

Regards,

Nick Loy

[Reagan]

Hello

1) What is the recommended frequency to restart the database? Is restarting it everyday too much?
You should first check why the system is restarted everyday.

There is no suggestion by SAP and Oracle to restart the systems on a regular basis unless there is a planned maintenance.

2) Is it advisable to use 'shutdown abort' to force the database to down?

Please read this link to have a clear understanding about the Oracle shutdown concepts:

http://www.dba-oracle.com/t_oracle_shutdown_immediate_abort.htm

Cheers

RB

[Former Member]

My question is

1) What is the recommended frequency to restart the database? Is restarting it everyday too much?

Whenever you are changing  DB memory parameters, that time youshould restart the server... There is NO Standard recommendation that to restart the server once in a day or a month... It depends on your business policy..

Like OS patching once in 6 months or year.. whenever you would need to restart your System that time you can restart your DB.. Till that time, DB can be up and running.

2) Is it advisable to use 'shutdown abort' to force the database to down?

Shutdown abort is NOT advisable. Reason is it will terminate all the active connections to DB.. Leading to inconsistency  with the DB...you MIGHT face problem to start the DB when you have shutdown the DB with abort command..

Just issue shutdown immediate... DB will wait till all the active connections are closed. Then it will shutdown the DB.

[former_member188883]

Hi Wai,

1) What is the recommended frequency to restart the database? Is restarting it everyday too much?

  => there is no standard recommendation to restart database. Ideally you production database should be always up and running unless planned downtime is taken to avoid business distruption.

2) Is it advisable to use 'shutdown abort' to force the database to down?

  => Shutdown abort is not recommended as it shall not commit running operations leading to data loss. Shutdown immediate or shutdown normal is recommended to stop the database gracefully.

Regards,

Deepak Kori