import & internal commit

[Fan Ruo Xin]

Hi,
I ran a couple of testing today. One of them I ran the following:
(1). truncate mytbl. (4 db partitions; Version8.1 + FixPak5)
(2) run "import from myfile.del of del insert into myble"
I knew I would get "Log full". But I didn't expect I still got some records
after "Log space used up on each db partitiion". I supposed all the inseted
rows should be rolled back.

It looks like db2 will automatelly call "commit" at some point. This is not
like when I ran the import process against a Version7 table. I am quite sure
the import without option "commitcount" is just like import with
"COMMITCOUNT <# of myfile.del>" in version7.2.

I couldn't find any documentation about this modification. Does anyone know
this?

Thanks,

[Knut Stolze]

Fan Ruo Xin wrote:

Hi,
I ran a couple of testing today. One of them I ran the following:
(1). truncate mytbl. (4 db partitions; Version8.1 + FixPak5)
(2) run "import from myfile.del of del insert into myble"
I knew I would get "Log full". But I didn't expect I still got some
records after "Log space used up on each db partitiion". I supposed all
the inseted rows should be rolled back.

It looks like db2 will automatelly call "commit" at some point. This is
not like when I ran the import process against a Version7 table. I am
quite sure the import without option "commitcount" is just like import
with "COMMITCOUNT <# of myfile.del>" in version7.2.

I couldn't find any documentation about this modification. Does anyone
know this?

Have a look at the "Usage notes" for the IMPORT command:
http://publib.boulder.ibm.com/infoce...e/r0008304.htm

There it says: "By default, online import performs automatic COMMITs to free
both the active log space and the lock list. Automatic COMMITs are not
performed only if a COMMITCOUNT value of zero is specified."
You will also find several other things explaining under which conditions a
COMMIT is executed.

--
Knut Stolze
Information Integration
IBM Germany / University of Jena