autocommit every n rows?

Michael Mueller

unread,

Feb 23, 2001, 8:30:41 AM2/23/01

to

Is there a command to have DB2 automatically commit inserts every n rows?
A command similar to the COMMITCOUNT in the IMPORT statement.

thanks
Michael

Dmitry

unread,

Feb 23, 2001, 9:14:14 AM2/23/01

to

Hi,
As I know DB2 doesn't provide this (Oracle too). As a way you can use
nologging ('not logged initially' in DB2) on the table.
I think this is the best decision when you want to fill a table with

insert into s.tb1
select * from s.tb2 (or a complex query here)

because you can always recreate the table without data loss, so you don't
need logging.

Dmitry.
www.ispirer.com - Database migration tools and services for Oracle and IBM
DB2.

.
"Michael Mueller" <mmue...@netway.at> wrote in message
news:975om1$j1k$1...@news.netway.at...

Günther Schöllhammer

unread,

Feb 26, 2001, 3:20:33 AM2/26/01

to

What is the nologging feature? What does it do?

Thanks

Günther

Dmitry schrieb:

Blair Kenneth Adamache

unread,

Feb 26, 2001, 9:07:42 AM2/26/01

to

It allows you to create a table that is not logged. Some logging is required
(for example, the table's addition to the system catalogs). This feature also
imposes permanent restrictions on the table and is somewhat dangerous for obvious
reasons. Don't use it to store bank records!

Günther Schöllhammer

unread,

Feb 27, 2001, 2:15:39 AM2/27/01

to

Is there a corresponding section in any DB2 manual in order to read into the topic?

Thanks,

Günther

Blair Kenneth Adamache schrieb:

Blair Kenneth Adamache

unread,

Feb 27, 2001, 7:01:19 AM2/27/01

to

See CREATE TABLE in the SQL Reference.

Günther Schöllhammer

unread,

Feb 28, 2001, 4:21:11 AM2/28/01

to

Hi Sailesh!

I looked through all the Deja threads, but:

I didn't find the NOT LOGGED INITIALLY in the DB2 UDB 6.0 for OS/390 SQL Reference. Maybe in
V7? Or not supported on OS/390?

AutoCommit: Does AutoCommit exist for static SQL (in PL/I) on OS/390? Or can one set a table
to AutoCommit Mode? We could use this feature very much for application logging (like user
login, user access, ...) to a DB2 table (VSAM isn't that good for reporting purposes). If the
application crashes all the log records should be kept (no ROLLBACK!). How can one set or use
AutoCommit on OS/390 (with static SQL)?

Could it also be used in one single (PL/I) application in such a way that table A is updated
in non AutoCommit mode (consistency needed, ROLLBACK issues, etc.), but table B in AutoCommit
mode (application logging, trace, etc.)?

Is NOT LOGGED INITIALLY a little bit like AutoCommit? Any logical similarity? Any relations?

Thanks very much,

Günther

Sailesh Krishnamurthy schrieb:

> Günther Schöllhammer <noadv...@noadvertise.net> writes:
>
> > I searched for the nologging option in the DB2 UDB 6.0 for OS/390 SQl Reference but
> > couldn't find it. Maybe it's AUDIT? Or when creating tablespaces?
> >
> > What does nologging do exactly? Does it mean no audit log is written or has it something
> > to do with COMMIT / ROLLBACK?
> >
>
> It's there in CREATE TABLE. Try a deja search under my name. I've
> posted twice about it in the last 3 months. The keyword can be NOT
> LOGGED INITIALLY
>
> --
> Toodle-pip
> Sailesh Krishnamurthy
> IBM Almaden Research Center
> Ph: (408) 927-1913