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

load vs. import ( warnings )

P: n/a
Hello,
If i import data into tables, import will write all warnings in
message file and will tell me why any exception row is rejected.
I wanted to get exception rows in seperate table which i assume i can
not do with import

If i use load, i can get exception rows in exception table but now
load does not give details in message file on why those rows were
exception rows and why they were rejected.
How can i achieve both using any of the utilities.

Regards,
Jagdip Singh

Jul 11 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
On Jul 11, 5:49 pm, db2admin <jag...@gmail.comwrote:
Hello,
If i import data into tables, import will write all warnings in
message file and will tell me why any exception row is rejected.
I wanted to get exception rows in seperate table which i assume i can
not do with import

If i use load, i can get exception rows in exception table but now
load does not give details in message file on why those rows were
exception rows and why they were rejected.
How can i achieve both using any of the utilities.

Regards,
Jagdip Singh
1. Use load as you described above, where rejects go into an exception
table.
2. Export all rows from the exception table.
3. Use import on the exported data, which will all be rejected with
reasons in the message file ...

--
Jeroen

Jul 11 '07 #2

P: n/a
On Jul 11, 12:10 pm, Jeroen van den Broek
<nlt...@baasbovenbaas.demon.nlwrote:
On Jul 11, 5:49 pm, db2admin <jag...@gmail.comwrote:
Hello,
If i import data into tables, import will write all warnings in
message file and will tell me why any exception row is rejected.
I wanted to get exception rows in seperate table which i assume i can
not do with import
If i use load, i can get exception rows in exception table but now
load does not give details in message file on why those rows were
exception rows and why they were rejected.
How can i achieve both using any of the utilities.
Regards,
Jagdip Singh

1. Use load as you described above, where rejects go into an exception
table.
2. Export all rows from the exception table.
3. Use import on the exported data, which will all be rejected with
reasons in the message file ...

--
Jeroen
Thanks for your reply.

When i use following file type modifiers

modified by coldel| dumpfile=dumpfile.$1 dumpfileaccessall=x

where $1 is command line parameter i provide when i run shell script
containing my load script
I get error

SQL3016N An unexpected keyword "accessall=x" was found in the
filetmod
parameter for the filetype.

What could be wrong ? dumpfile will be really helpful for me to test
migration. Please help me if someone experienced same problem before
or someone knows how to deal with this problem.
Regards,
Jagdip Singh

Jul 16 '07 #3

P: n/a
db2admin wrote:
On Jul 11, 12:10 pm, Jeroen van den Broek
<nlt...@baasbovenbaas.demon.nlwrote:
>On Jul 11, 5:49 pm, db2admin <jag...@gmail.comwrote:
>>Hello,
If i import data into tables, import will write all warnings in
message file and will tell me why any exception row is rejected.
I wanted to get exception rows in seperate table which i assume i
can not do with import
>>If i use load, i can get exception rows in exception table but now
load does not give details in message file on why those rows were
exception rows and why they were rejected.
How can i achieve both using any of the utilities.
>>Regards,
Jagdip Singh

1. Use load as you described above, where rejects go into an
exception table.
2. Export all rows from the exception table.
3. Use import on the exported data, which will all be rejected with
reasons in the message file ...

--
Jeroen

Thanks for your reply.

When i use following file type modifiers

modified by coldel| dumpfile=dumpfile.$1 dumpfileaccessall=x

where $1 is command line parameter i provide when i run shell script
containing my load script
I get error

SQL3016N An unexpected keyword "accessall=x" was found in the
filetmod
parameter for the filetype.

What could be wrong ? dumpfile will be really helpful for me to test
migration. Please help me if someone experienced same problem before
or someone knows how to deal with this problem.
Did you check DB2's Infocenter for valid filetype modifiers for the load
utility?
Here's the link for version 9:
http://publib.boulder.ibm.com/infoce...c/r0011044.htm

As you can see (in Table 2), the modifier to grant read access for the
dumpfile to 'OTHERS' is just 'dumpfileaccessall', i.e. no '=x' appended to
it.
Also be sure to comply with the other restrictions mentioned:
1. also specify the 'dumpfile' modifier (which you did)
2. make sure the user has at least SELECT privs on the target table for the
load
3. you should be running on a Unix (or alike) environment
Also note that this only works for newly created dumpfiles, for existing
files the permissions will not be changed.

HTH

--
Jeroen
Jul 16 '07 #4

P: n/a
On Jul 16, 3:39 pm, "The Boss" <use...@No.Spam.Please.invalidwrote:
db2admin wrote:
On Jul 11, 12:10 pm, Jeroen van den Broek
<nlt...@baasbovenbaas.demon.nlwrote:
On Jul 11, 5:49 pm, db2admin <jag...@gmail.comwrote:
>Hello,
If i import data into tables, import will write all warnings in
message file and will tell me why any exception row is rejected.
I wanted to get exception rows in seperate table which i assume i
can not do with import
>If i use load, i can get exception rows in exception table but now
load does not give details in message file on why those rows were
exception rows and why they were rejected.
How can i achieve both using any of the utilities.
>Regards,
Jagdip Singh
1. Use load as you described above, where rejects go into an
exception table.
2. Export all rows from the exception table.
3. Use import on the exported data, which will all be rejected with
reasons in the message file ...
--
Jeroen
Thanks for your reply.
When i use following file type modifiers
modified by coldel| dumpfile=dumpfile.$1 dumpfileaccessall=x
where $1 is command line parameter i provide when i run shell script
containing my load script
I get error
SQL3016N An unexpected keyword "accessall=x" was found in the
filetmod
parameter for the filetype.
What could be wrong ? dumpfile will be really helpful for me to test
migration. Please help me if someone experienced same problem before
or someone knows how to deal with this problem.

Did you check DB2's Infocenter for valid filetype modifiers for the load
utility?
Here's the link for version 9:http://publib.boulder.ibm.com/infoce...ic/com.ibm.db2....

As you can see (in Table 2), the modifier to grant read access for the
dumpfile to 'OTHERS' is just 'dumpfileaccessall', i.e. no '=x' appended to
it.
Also be sure to comply with the other restrictions mentioned:
1. also specify the 'dumpfile' modifier (which you did)
2. make sure the user has at least SELECT privs on the target table for the
load
3. you should be running on a Unix (or alike) environment
Also note that this only works for newly created dumpfiles, for existing
files the permissions will not be changed.

HTH

--
Jeroen
Hello Jeroen,

I am using DB2 8.2 with fixpak 12 and i got these parameters from
command reference for DB2 V8.2
Although i did not try using dumpfileaccessall' without x but Command
reference for 8.2 says that I should use dumpfileaccessall=x

regards,
jagdip

Jul 16 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.