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.