469,589 Members | 2,048 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,589 developers. It's quick & easy.

Path error when using DB2 load dumpfile modifier - related to partitioned database?

I searched for this topic and already read this article:


However while I wait for the DBA's here to respond to my e-mail, I wanted to make a post and ask the question, is use of the dumpfile modifier on the db2 load command in any way related to whether or not you partition your database? I noticed all of our load scripts here have no dumpfile (like Oracle's .bad/.dsc files) and I thought that was really odd in a high volume ETL shop like ours.

The reason behind that, I was told by another developer, is that you can't use that modifier when you have a partitioned database. Is that true? I find that hard to believe, since knowing which records are rejected on a load is critical.

Here is the error I constantly get:

u060dw97:/u/uelmetl/etl/subject/tlogs/file>pfile = /u/uelmetl/etl/bin/rejected.log replace into ELMS.PHM_MDL nonrecoverable" <
SQL2036N The path for the file or device
"/u/uelmetl/etl/bin/rejected.log.load.084" is not valid.

On this command:

db2 "load client from $ETLROOT/subject/tlogs/file/phm_mdl.rpl of del modified by coldel| dumpfile = /u/uelmetl/etl/bin/rejected.log replace into ELMS.PHM_MDL nonrecoverable"

No matter which path I specify (all valid to the OS), I get that error.

Thanks in advance for any tips!
Dec 20 '06 #1
0 2034

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

reply views Thread by MrTulley | last post: by
5 posts views Thread by Sumanth | last post: by
2 posts views Thread by Ruymán | last post: by
39 posts views Thread by Leonardo Korndorfer | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.