Loading/Logging/workfile errors

Rick McClendon

Loading/Logging/workfile errors
UDB DBA's -
We are trying to LOAD a Data Warehouse table from the mainframe onto UDB
7.1(AIX). The table holds about 1,000,000 rows (800 chars per row) and we
continue to get errors when using the apply program.

Is it possible to issue COMMITS every Nth rows in UDB 7.1 ? (This should
eliminate the Temp log files?)
or
Can we turn off logging(??)

Another error we ran into is: - 662203 - "The apply program could not write
to the work files.... ?"

Does anyone have any Ideas or Experiences you would like to share?

We have logretain set to "No" and userexit set to "No - However, my
understanding is they do not actually affect whether logging takes place;
instead, they determine whether (some of) the files that are logged to are
retained after transactions are committed. There are permanent and
temporary log files, and the temporary log files are created and removed
dynamically upon need.

Thank you for your time -

Rick McClendon
D.B.A. Systems Analyst
Florida State University
C6124 University Center
Tallahassee, FL 32306-2620
E-Mail : [login to unmask email]
Voice : (850) 644 - 4953



[login to unmask email]

Re: Loading/Logging/workfile errors
(in response to Rick McClendon)
Dick,
No, you can't turn logging off.
We are on UDB EE V5.2, but we are doing something similar, loading a
datawarehouse (or datamarts)
from legacy OS/390 DB2 tables.
Since this is read only data, I'm also not archiving logs, BUT, I did size
the logs large enough to accomdate the loads.

We ran into problems with work, and tmp, so we researched the load parms
and added these commands to our large loads scripts:

remote file /db2padm/utmp/admapp \
using /tmp/db2

Hope this helps.........

Sean

Sean O'Keefe
Virginia Commonwealth University
Administrative Information Technology
Data Services
(804) 828-8415
[login to unmask email]




"McClendon,
Rick" To: [login to unmask email]
<[login to unmask email] cc:
N.FSU.EDU> Subject: Loading/Logging/workfile errors
Sent by: DB2
Data Base
Discussion List
<[login to unmask email]>


12/20/00 11:47
AM
Please respond
to DB2 Data Base
Discussion List






UDB DBA's -
We are trying to LOAD a Data Warehouse table from the mainframe onto UDB
7.1(AIX). The table holds about 1,000,000 rows (800 chars per row) and we
continue to get errors when using the apply program.

Is it possible to issue COMMITS every Nth rows in UDB 7.1 ? (This should
eliminate the Temp log files?)
or
Can we turn off logging(??)

Another error we ran into is: - 662203 - "The apply program could not write
to the work files.... ?"

Does anyone have any Ideas or Experiences you would like to share?

We have logretain set to "No" and userexit set to "No - However, my
understanding is they do not actually affect whether logging takes place;
instead, they determine whether (some of) the files that are logged to are
retained after transactions are committed. There are permanent and
temporary log files, and the temporary log files are created and removed
dynamically upon need.

Thank you for your time -

Rick McClendon
D.B.A. Systems Analyst
Florida State University
C6124 University Center
Tallahassee, FL 32306-2620
E-Mail : [login to unmask email]
Voice : (850) 644 - 4953








Ashish Mohan

Re: Loading/Logging/workfile errors
(in response to sokeefe@VCU.EDU)
No, I don't think you can COMMIT after every Nth row; but you have the
SAVECOUNT option (expressed in number of records) which means that if you
load fails in the LOAD phase and you restart it (after correcting the reason
for it's failure) , it will restart from the last point it did a savecount
on.

As for logging, LOAD can be invoke with NONRECOVERABLE option so that
logging does not take place (there may be other ways also for accomplishing
this). But be absolutely sure to take an image copy of all your tablespaces
on UDB immediately after loading the tablespaces (UDB will not prompt you
for this).

Thanks.

Ashish.
/****all disclaimers apply****/

-----Original Message-----
From: McClendon, Rick [SMTP:[login to unmask email]
Sent: Wednesday, December 20, 2000 8:48 AM
To: [login to unmask email]
Subject: Loading/Logging/workfile errors

UDB DBA's -
We are trying to LOAD a Data Warehouse table from the mainframe onto
UDB
7.1(AIX). The table holds about 1,000,000 rows (800 chars per row)
and we
continue to get errors when using the apply program.

Is it possible to issue COMMITS every Nth rows in UDB 7.1 ? (This
should
eliminate the Temp log files?)
or
Can we turn off logging(??)

Another error we ran into is: - 662203 - "The apply program could
not write
to the work files.... ?"

Does anyone have any Ideas or Experiences you would like to share?

We have logretain set to "No" and userexit set to "No - However, my
understanding is they do not actually affect whether logging takes
place;
instead, they determine whether (some of) the files that are logged
to are
retained after transactions are committed. There are permanent and
temporary log files, and the temporary log files are created and
removed
dynamically upon need.

Thank you for your time -

Rick McClendon
D.B.A. Systems Analyst
Florida State University
C6124 University Center
Tallahassee, FL 32306-2620
E-Mail : [login to unmask email]
Voice : (850) 644 - 4953




can



Ashish Mohan

Re: Loading/Logging/workfile errors
(in response to Ashish Mohan)
Just a correction to my previous mail; interpretted it wrongly;
NONRECOVERABLE turns logging off 'after' the load and not during it.

Thanks.

Ashish.

-----Original Message-----
From: Mohan, Ashish
Sent: Wednesday, December 20, 2000 9:18 AM
To: 'DB2 Data Base Discussion List'
Subject: RE: Loading/Logging/workfile errors

No, I don't think you can COMMIT after every Nth row; but you have
the SAVECOUNT option (expressed in number of records) which means that if
you load fails in the LOAD phase and you restart it (after correcting the
reason for it's failure) , it will restart from the last point it did a
savecount on.

As for logging, LOAD can be invoke with NONRECOVERABLE option so
that logging does not take place (there may be other ways also for
accomplishing this). But be absolutely sure to take an image copy of all
your tablespaces on UDB immediately after loading the tablespaces (UDB will
not prompt you for this).

Thanks.

Ashish.
/****all disclaimers apply****/

-----Original Message-----
From: McClendon, Rick [SMTP:[login to unmask email]
Sent: Wednesday, December 20, 2000 8:48 AM
To: [login to unmask email]
Subject: Loading/Logging/workfile errors

UDB DBA's -
We are trying to LOAD a Data Warehouse table from the
mainframe onto UDB
7.1(AIX). The table holds about 1,000,000 rows (800 chars
per row) and we
continue to get errors when using the apply program.

Is it possible to issue COMMITS every Nth rows in UDB 7.1 ?
(This should
eliminate the Temp log files?)
or
Can we turn off logging(??)

Another error we ran into is: - 662203 - "The apply program
could not write
to the work files.... ?"

Does anyone have any Ideas or Experiences you would like to
share?

We have logretain set to "No" and userexit set to "No -
However, my
understanding is they do not actually affect whether logging
takes place;
instead, they determine whether (some of) the files that are
logged to are
retained after transactions are committed. There are
permanent and
temporary log files, and the temporary log files are created
and removed
dynamically upon need.

Thank you for your time -

Rick McClendon
D.B.A. Systems Analyst
Florida State University
C6124 University Center
Tallahassee, FL 32306-2620
E-Mail : [login to unmask email]
Voice : (850) 644 - 4953


To change your subscription options or to cancel your
subscription visit the DB2-L webpage at http://www.ryci.com/db2-l. The
owners of the list can