Xixi,
this is the reason why you need a backup.
From the DB2 doc's:
Because changes to the table are not logged, you should consider the
following when deciding to use the NOT LOGGED INITIALLY table attribute:
a.. All changes to the table will be flushed out to disk at commit
time. This means that the commit may take longer.
b.. If the NOT LOGGED INITIALLY attribute is activated and an activity
occurs that is not logged, the entire unit of work will be rolled back if a
statement fails or a ROLLBACK TO SAVEPOINT is executed (SQL1476N).
c.. 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.
Note:
When a table is created, row locks are held on the catalog tables
until a COMMIT is done. To take advantage of the no logging behavior, you
must populate the table in the same unit of work in which it is created.
This has implications for concurrency
Regards,
Joachim
"xixi" <da****@yahoo.com> schrieb im Newsbeitrag
news:c0*************************@posting.google.co m...
hi, we are using db2 v8.1 win 64 bit with fp3. i get this error message
from the control panel : Administrative Tools, Event Viewer, application
2003-10-22-17.52.43.850000 Instance:DB2 Node:000
PID:2608(db2syscs.exe) TID:3100 Appid:AC10049E.G79D.00F866005503
data management sqldEndNoLogList Probe:1 Database:NJIPD
ADM5530E The COMMIT processing of table "TBSPACEID=4.TABLEID=2828" that
used NOT LOGGED INITIALLY has been initiated. It is recommended that you take
a backup of this table's table space(s).
What does this mean? why i need to do a backup? thanks