dbTalk Databases Forums  

Rollforward stop vs complete

comp.databases.ibm-db2 comp.databases.ibm-db2


Discuss Rollforward stop vs complete in the comp.databases.ibm-db2 forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Gladiator
 
Posts: n/a

Default Rollforward stop vs complete - 04-26-2011 , 04:20 AM






Hi ,

Can someone tell me what happens when we issue a rollforward stop and
a rollforward complete.

Kamal.

Reply With Quote
  #2  
Old   
Lennart Jonsson
 
Posts: n/a

Default Re: Rollforward stop vs complete - 04-26-2011 , 06:46 AM






On 2011-04-26 11:20, Gladiator wrote:
Quote:
Hi ,

Can someone tell me what happens when we issue a rollforward stop and
a rollforward complete.

They are synonyms, so there is no difference. Snipped from the 9.5
online help
(http://publib.boulder.ibm.com/infoce...r5/index.jsp):

COMPLETE | STOP
Stops the rolling forward of log records, and completes the
rollforward recovery process by rolling back any incomplete transactions
and turning off the rollforward pending state of the database. This
allows access to the database or table spaces that are being rolled
forward. These keywords are equivalent; specify one or the other, but
not both. The keyword AND permits specification of multiple operations
at once; for example, db2 rollforward db sample to end of logs and
complete. When rolling table spaces forward to a point in time, the
table spaces are placed in backup pending state.



/Lennart

Reply With Quote
  #3  
Old   
Gladiator
 
Posts: n/a

Default Re: Rollforward stop vs complete - 04-27-2011 , 12:57 AM



On Apr 26, 4:46*pm, Lennart Jonsson <erik.lennart.jons... (AT) gmail (DOT) com>
wrote:
Quote:
On 2011-04-26 11:20, Gladiator wrote:

Hi ,

Can someone tell me what happens when we issue a rollforward stop and
a rollforward complete.

They are synonyms, so there is no difference. Snipped from the 9.5
online help
(http://publib.boulder.ibm.com/infoce...r5/index.jsp):

COMPLETE | STOP
* * Stops the rolling forward of log records, and completes the
rollforward recovery process by rolling back any incomplete transactions
and turning off the rollforward pending state of the database. This
allows access to the database or table spaces that are being rolled
forward. These keywords are equivalent; specify one or the other, but
not both. The keyword AND permits specification of multiple operations
at once; for example, db2 rollforward db sample to end of logs and
complete. When rolling table spaces forward to a point in time, the
table spaces are placed in backup pending state.

/Lennart
Thanks for the reply,

But my question is if both are performing the same operation why do we
have two keywords STOP|COMPLETE ?
What are the situations in which we use STOP and in what situations we
use COMPLETE.


Thanks,
Kamal.

Reply With Quote
  #4  
Old   
Mark A
 
Posts: n/a

Default Re: Rollforward stop vs complete - 04-27-2011 , 01:11 AM



Quote:
"Gladiator" <vkamalnath1237 (AT) gmail (DOT) com> wrote in message
news:497cb7cc-4692-46ff-baf0-f18de5b17e08 (AT) r35g2000prj (DOT) googlegroups.com...
Thanks for the reply,

But my question is if both are performing the same operation why do we
have two keywords STOP|COMPLETE ?
What are the situations in which we use STOP and in what situations we
use COMPLETE.

Thanks,
Kamal.
There is absolutely no difference between them. Both are accepted and do the
exact same thing. They probably both exist because of a decision to make the
rollforward command more compatible with syntax for other DB2 products (such
as DB2 for z/OS, etc), but I don't recall the exact history of this.

Reply With Quote
  #5  
Old   
Helmut Tessarek
 
Posts: n/a

Default Re: Rollforward stop vs complete - 04-27-2011 , 01:27 AM



Hi Kamal,

On 27.04.11 1:57 , Gladiator wrote:
Quote:
But my question is if both are performing the same operation why do we
have two keywords STOP|COMPLETE ?
What are the situations in which we use STOP and in what situations we
use COMPLETE.
You can either use COMPLETE or STOP. Both commands are performing the same
operation. STOP is an alias for COMPLETE.
The reason why there are 2 keywords is a historical one.

But aliases are not uncommon. e.g.:

DB2:
'db2 get dbm cfg' alias for 'db2 get database manager configuration'

PHP:
'join' alias for 'implode'
'chop' alias for 'rtrim'

--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab

Reply With Quote
  #6  
Old   
Gladiator
 
Posts: n/a

Default Re: Rollforward stop vs complete - 04-27-2011 , 04:53 AM



On Apr 27, 11:27*am, Helmut Tessarek <tessa... (AT) evermeet (DOT) cx> wrote:
Quote:
Hi Kamal,

On 27.04.11 1:57 , Gladiator wrote:

But my question is if both are performing the same operation why do we
have two keywords STOP|COMPLETE *?
What are the situations in which we use STOP and in what situations we
use COMPLETE.

You can either use COMPLETE or STOP. Both commands are performing the same
operation. STOP is an alias for COMPLETE.
The reason why there are 2 keywords is a historical one.

But aliases are not uncommon. e.g.:

DB2:
'db2 get dbm cfg' alias for 'db2 get database manager configuration'

PHP:
'join' alias for 'implode'
'chop' alias for 'rtrim'

--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab
Thanks everyone for the clarification.

Kamal.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.