cancel
Showing results for 
Search instead for 
Did you mean: 

Correct shutdown and start for MAXDB standby database

Former Member
0 Kudos

Hello Colleagues,

Please could you confirm the right way to stop a standby MAXDB database and start it again, please confirm if this sequence is the right one:

-db_stop

start maintenance task at server....

.... after all is ok again for start it again

-db_cold

start aplying logs backups.

Is that right?

Kind Regards.

Accepted Solutions (0)

Answers (2)

Answers (2)

markus_doehr2
Active Contributor
0 Kudos

> Please could you confirm the right way to stop a standby MAXDB database and start it again, please confirm if this sequence is the right one:

I do (for example) on a shadow database:

db_admin
db_connect
recover_start logsich log 6743
recover_replace logsich /archivelog/log 6744
recover_cancel

After the "recover_cancel" the database is offline again.

Using that method you will have to "recover_start logsich log 6744" again (not 6745!)

Markus

Former Member
0 Kudos

Thank you Markus,

My Maxdb version is 7.4 so for start it back is suppossed to be db_admin instead of db_cold for 7.4?

For shutdown the Maxdb standby database what is the command you use?

Thank you!

markus_doehr2
Active Contributor
0 Kudos

Enrique,

as I said - after 'recover_cancel' the database will write a checkpoint and is offline. So what is your question?

Markus

Former Member
0 Kudos

Is there any other way to make it offline consistently apart from recover_cancel?

That´s my question.

Regards

Former Member
0 Kudos

Also I´m not using logs to refresh the standby database but incremental backups

markus_doehr2
Active Contributor
0 Kudos

> Is there any other way to make it offline consistently apart from recover_cancel?

No.

Why is recover_cancel a problem?

Markus

lbreddemann
Active Contributor
0 Kudos

Nope, it isn't!

DB_STOP KILLS the database instance. There is no gracefull shutdown, no ending of current activities, no nothing.

It simply pulls the plug.

DB_WARM is a command that is wrong for two reasons:

1. It is obsolete since MaxDB 7.4 - the correct command nowadays is DB_ONLINE

2. If this is your standby instance and you don't want to open the database, then DON'T use DB_WARM/DB_ONLINE!!

You cannot recover additional log backups after the database was started and opened!

Best would be: check the current documentation for MaxDB!

regards,

Lars

Former Member
0 Kudos

Hello Colleague,

But i didn´t write db_warm in my message (just db_cold). My MaxDB version is 7.4

Thank you for clarify how I can:

Stop the Maxdb standby database in a consistent way.

Start it again in admin state just to wait for the next backup to be applied.

Kind Regards