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

does Not logged initally affect rolling forward recover?

P: n/a
we are using db2 udb v8.2 on windows. All our tables are created with
"not logged initially" parameter. Our application with auto commit on.
I would like to do an online backup and rolling forward recovery, is
this allowed? because in the document, i read these: You cannot recover
these tables when rolling forward. If the rollforward operation
encounters a table that was created or altered with the NOT LOGGED
INITIALLY option, the table is marked as unavailable. After the
database is recovered, any attempt to access the table returns
SQL1477N. If there any workaround to get rid of the parameter so we
could do online backup? thanks

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


P: n/a
<db********@yahoo.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
we are using db2 udb v8.2 on windows. All our tables are created with
"not logged initially" parameter. Our application with auto commit on.
I would like to do an online backup and rolling forward recovery, is
this allowed? because in the document, i read these: You cannot recover
these tables when rolling forward. If the rollforward operation
encounters a table that was created or altered with the NOT LOGGED
INITIALLY option, the table is marked as unavailable. After the
database is recovered, any attempt to access the table returns
SQL1477N. If there any workaround to get rid of the parameter so we
could do online backup? thanks

NOT LOGGED INITIALLY is turned off as soon as one does a commit (explicitly
or with auto-commit), so if you do a backup after that and use the later
backup, you should be able to roll forward from the later backup forward.
You just cannot roll forward through a point in time when NOT LOGGED
INITIALLY is active.
Nov 12 '05 #2

P: n/a
In V8.2, this attribute is on by default.
It means that whenever you issue ALTER TABLE ... ACTIVATE NOT LOGGED
INITIALLY then everything between that and the next commit is not logged.
If you do not issue it, nothing changes and the table is in ormal state
and can be backed in its tablespace and recovered and rolled forward.

If you do and encounter a a rollback or a failure, as you recover the
table is marked inaccessible and you cannot recover it.

The fact it is enabled to be NLI does not do anything until you issue
the ACTIVATE.
HTH, Pierre.

db********@yahoo.com wrote:
we are using db2 udb v8.2 on windows. All our tables are created with
"not logged initially" parameter. Our application with auto commit on.
I would like to do an online backup and rolling forward recovery, is
this allowed? because in the document, i read these: You cannot recover
these tables when rolling forward. If the rollforward operation
encounters a table that was created or altered with the NOT LOGGED
INITIALLY option, the table is marked as unavailable. After the
database is recovered, any attempt to access the table returns
SQL1477N. If there any workaround to get rid of the parameter so we
could do online backup? thanks


--
Pierre Saint-Jacques - Reply to: sescons at attglobal dot net
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.
Nov 12 '05 #3

P: n/a
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 #4

This discussion thread is closed

Replies have been disabled for this discussion.