By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
445,870 Members | 1,212 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 445,870 IT Pros & Developers. It's quick & easy.

Strange IMPORT warning

P: n/a
Hi!

When I'm using IMPORT with INSERT_UPDATE I sometimes get
SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table.

I'm not sure why this happens. The problem is that I get rejected rows
because of this.

Best regards,
Kovi
--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Nov 11 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
This is what I see for the IMPORT output:
SQL3150N The H record in the PC/IXF file has product "DB2 02.00", date
"20061111", and time "121511".

SQL3153N The T record in the PC/IXF file has name
"C:\MBS\HIPER\VERSION\..\REPLICATION\OUT\IDNAPLAFA KTURA.I", qualifier "",
and
source " ".

SQL3109N The utility is beginning to load data from file
"D:\MBS\HIPER\VERSION\SERVER\REPLIKACIJA\CENT\IDNA PLAFAKTURA.IXF".

SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table. SQLSTATE=02000

SQL3185W The previous error occurred while processing data from row "3" of
the input file.

SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table. SQLSTATE=02000

SQL3185W The previous error occurred while processing data from row "4" of
the input file.

SQL3110N The utility has completed processing. "6" rows were read from
the
input file.

SQL3221W ...Begin COMMIT WORK. Input Record Count = "6".

SQL3222W ...COMMIT of any database changes was successful.

SQL3149N "6" rows were processed from the input file. "0" rows were
successfully inserted into the table. "2" rows were rejected.
Number of rows read = 6
Number of rows skipped = 0
Number of rows inserted = 0
Number of rows updated = 4
Number of rows rejected = 2
Number of rows committed = 6

Strange things are the numbers (6 read, 2 rejected and 6 commited).
I have to say that the table I was importing to was not empty.

Best regards,
Kovi
--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Nov 11 '06 #2

P: n/a
Gregor Kovač wrote:
This is what I see for the IMPORT output:
SQL3150N The H record in the PC/IXF file has product "DB2 02.00", date
"20061111", and time "121511".

SQL3153N The T record in the PC/IXF file has name
"C:\MBS\HIPER\VERSION\..\REPLICATION\OUT\IDNAPLAFA KTURA.I", qualifier "",
and
source " ".

SQL3109N The utility is beginning to load data from file
"D:\MBS\HIPER\VERSION\SERVER\REPLIKACIJA\CENT\IDNA PLAFAKTURA.IXF".

SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table. SQLSTATE=02000

SQL3185W The previous error occurred while processing data from row "3"
of the input file.

SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a
query is an empty table. SQLSTATE=02000

SQL3185W The previous error occurred while processing data from row "4"
of the input file.

SQL3110N The utility has completed processing. "6" rows were read from
the
input file.

SQL3221W ...Begin COMMIT WORK. Input Record Count = "6".

SQL3222W ...COMMIT of any database changes was successful.

SQL3149N "6" rows were processed from the input file. "0" rows were
successfully inserted into the table. "2" rows were rejected.
Number of rows read = 6
Number of rows skipped = 0
Number of rows inserted = 0
Number of rows updated = 4
Number of rows rejected = 2
Number of rows committed = 6

Strange things are the numbers (6 read, 2 rejected and 6 commited).
I have to say that the table I was importing to was not empty.

Best regards,
Kovi
I've solved this strange problem.
There was a unique index on the target table that does not exists on source
table and dropping the unique index solved the problem.
Well, the docs say
(http://publib.boulder.ibm.com/infoce...r0008304.htm):
INSERT_UPDATE
Adds rows of imported data to the target table, or updates existing rows
(of the target table) with matching primary keys.

But this is not the case. Is there a bug in DB2 or documentation?

Best regards,
Kovi

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Nov 14 '06 #3

P: n/a

could it be that there is a program at work while your are doing your
load?
eg.
load checks existence of row A
row A exists -load will do an update
program X deletes row A
load performs update -error 100, row rejected

Nov 16 '06 #4

P: n/a
www.spaceboot.eu wrote:
>
could it be that there is a program at work while your are doing your
load?
eg.
load checks existence of row A
row A exists -load will do an update
program X deletes row A
load performs update -error 100, row rejected
No, becuase the program doing the IMPORTs is the ony one in out applcation
doing changes to those tables.

--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-
Nov 16 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.