|
Could there be a trigger on this file? We've had issues with mass updates or inserts getting clobbered by a trigger. Another idea, is the file journaled? If the receiver threshold value is too small, you may be swapping out receivers too often, though this seems unlikely. Have you tried STRDBMON to watch your job doing the INSERTs? Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 > -----Original Message----- > From: Weatherly, Howard [mailto:Howard.Weatherly@dlis.dla.mil] > Sent: Tuesday, July 02, 2002 9:52 AM > To: Midrange Mailing List (E-mail) > Subject: CLRPFM and DB2 Tables > > > This message is in MIME format. Since your mail reader does > not understand > this format, some or all of this message may not be legible. > -- > [ Picked text/plain from multipart/alternative ] > I am looking for some words of wisdom here, we have a project that is > building a cross-reference table from several systems. Had I had some > insight into what exactly was being done, I might have > prevented the table > from being put into DB2 however what is done is too hard to > undo around > here. The problem is that on a periodic basis this table needs to be > replaced. In between, I am updating the table which seems ok. > My problem is > that this table is just shy of 4 million rows and because of > the way the > table was implemented (not a DB2 issue) I am not permitted to > use DDL in the > job stream. My thought is to use CLRPFM to clear the table > and reload it > using CPYF however something strange happened in testing the > program (before > I decided to use CPYF) it took forever using Exec SQL Insert.... and I > eventually killed the job. > > Is there some reason that I should not use CLRPFM to clean > out this table > for a reload? > > ____________________________________________ > Howard Weatherly > Systems Advisor > Computer Task Group, Inc. > > howard.weatherly@dlis.dla.mil > Howard_weatherly@ameritch.net > Howard.Weatherly@ctg.com > > > > "luck favors those who prepare" > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.