By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,606 Members | 3,802 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,606 IT Pros & Developers. It's quick & easy.

questions on HADR on tables with "not logged initially"

P: n/a
we are using db2 udb v8.2 on windows. all our tables are created with
not logged initially property,

So if i want to activate HADR (high availability disaster recovery) for

the database, in the document it said " non-replicated operations
include, but are not limited to --Tables created with the NOT LOGGED
initially option specified", so does that means i can't do HADR on our
current database because all the tables are created with the NLI
option? thanks

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
db********@yahoo.com wrote:
we are using db2 udb v8.2 on windows. all our tables are created with
not logged initially property,

So if i want to activate HADR (high availability disaster recovery) for

the database, in the document it said " non-replicated operations
include, but are not limited to --Tables created with the NOT LOGGED
initially option specified", so does that means i can't do HADR on our
current database because all the tables are created with the NLI
option? thanks

No it doesn't mean that.
If a table is created with not logged initially thsi is only in effect
for the first insert. After that that table is no different than any
other in DB2 V8.1 and V8.2
Presuming you don't start with an empty database the issue would only
arise if you ALTER TABLE .. ACTIVATE NOT LOGGED INITIALLY
everything happening on that table until the next commit would not be
logged and hence not applied to the secondary.

Cheers
Serge
--
Serge Rielau
DB2 SQL Compiler Development
IBM Toronto Lab
Nov 12 '05 #2

P: n/a

This depends a bit on what is meant by "tables are created."
For existing tables that were created with NLI and are now logged,
there
shouldn't be a problem, as long as the standby is initialized using a
backup taken after all the tables became logged. However, if it means
that new tables are regularly created in the database with NLI, then
this
will be in conflict with HADR.

Regards,
- Steve P.
-----------------------
Steve Pearson
IBM DB2 UDB Development
Portland, OR, USA

Nov 12 '05 #3

P: n/a
Ian
Steve Pearson wrote:
This depends a bit on what is meant by "tables are created."
For existing tables that were created with NLI and are now logged,
there
shouldn't be a problem, as long as the standby is initialized using a
backup taken after all the tables became logged. However, if it means
that new tables are regularly created in the database with NLI, then
this will be in conflict with HADR.


Steve,

I think he meant that because V8.2 does not require you to create tables
explicitly with the NOT LOGGED INITIALLY parameter (it's implicit), does
the simple act of creating a table (CREATE TABLE T1 (c1 int);) break
HADR.

Nov 12 '05 #4

P: n/a
Ian wrote:
Steve Pearson wrote:
This depends a bit on what is meant by "tables are created."
For existing tables that were created with NLI and are now logged,
there
shouldn't be a problem, as long as the standby is initialized using a
backup taken after all the tables became logged. However, if it means
that new tables are regularly created in the database with NLI, then
this will be in conflict with HADR.

Steve,

I think he meant that because V8.2 does not require you to create tables
explicitly with the NOT LOGGED INITIALLY parameter (it's implicit), does
the simple act of creating a table (CREATE TABLE T1 (c1 int);) break
HADR.


Not really since logging for the table is on until you do an:

alter table schema.table activate not logged initially

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.