If you create the table as not logged initially, the assumption is that there MAY be unlogged activity tacked on to the creation statement. With auto-commit turned on, that's frequently NOT the case, but DB2 doesn't know that. So, the act of creating a table with the "not logged initially" option invalidates the logs from that point forward, even if no actual unlogged activity has occurred.

In short, when you create a table with this option, your logs are useless until you take another full backup.

I speak as one who has been burned. :-)

Brad Rowen
Senior Database Administrator
dbaDIRECT, Inc.



-----Original Message-----
From: Schleicher Jeremy D.
[mailto:db2udbdba-ezmlmshield-x24177000.[Email address protected]
Sent: Friday, April 28, 2006 10:48 AM
To: LazyDBA Discussion
Subject: not logged initially


I have a scenario that I need explained so here goes.

We have a bunch of tables that were created not logged initially, we had
to do a database restore to a point in time yesterday and now a group of
tables are unusable such is the case with tables that you do a load
nonrecoverable or not logged initially.

The question is when the table is created not logged initially is that
the default behavior for all transactions that happen to this table?

If that were the case in this example a unit of work would have to have
been running on these tables at the time the disks were yanked out from
under the database (thank you very much Aix admin) and that work was
never commited.

Jeremy Schleicher
ERP Database Administrator
Florida State University




---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


DB2 & UDB email list listserv db2-l LazyDBA home page