not able to use load method
Moderators: chulett, rschirm, roy
not able to use load method
Hi All,
I am not able to use LOAD Method in my job.....It is showing following error message
DB2 Load Binary Error
SQLCODE=-3025
SQL3025N
A parameter specifying a filename or path is not valid
Failed opening fifo /dstage/Ascential/datastage/scretch/ordb21531966fb686b1c after 90 seconds no such device or address.
I am using DB2 partitioning in this job and with WRITE and UPSERT method its working fine......please suggest me how to resolve this.
Thanks in Advance
stiwari
I am not able to use LOAD Method in my job.....It is showing following error message
DB2 Load Binary Error
SQLCODE=-3025
SQL3025N
A parameter specifying a filename or path is not valid
Failed opening fifo /dstage/Ascential/datastage/scretch/ordb21531966fb686b1c after 90 seconds no such device or address.
I am using DB2 partitioning in this job and with WRITE and UPSERT method its working fine......please suggest me how to resolve this.
Thanks in Advance
stiwari
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 94
- Joined: Wed May 08, 2002 8:44 am
- Location: Germany
- Contact:
-
- Charter Member
- Posts: 193
- Joined: Tue Sep 05, 2006 8:01 pm
- Location: Australia
Re: not able to use load method
Hi Stiwari,stiwari wrote:Hi All,
I am not able to use LOAD Method in my job.....It is showing following error message
DB2 Load Binary Error
SQLCODE=-3025
SQL3025N
A parameter specifying a filename or path is not valid
Failed opening fifo /dstage/Ascential/datastage/scretch/ordb21531966fb686b1c after 90 seconds no such device or address.
I am using DB2 partitioning in this job and with WRITE and UPSERT method its working fine......please suggest me how to resolve this.
Thanks in Advance
stiwari
Did you manage to resolve this issue? I had the same problem and would like to find out from you what the resolution was.
Please send reply to nick.chuah@bearingpoint.com
Thanks
nick
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You check for this possible cases,
"The parameter contains a path, directory, or file name that is not valid.
For IMPORT and EXPORT, verify the datafile parameter.
For LOAD, verify that each entry in the parameters of type sqlu_media_list : datafile should contain valid filenames; lobpaths copytarget , and workdirectory should contain valid paths on the server including the final separator and a null terminator.
The pointer to lobpaths, copytarget and workdirectory must be valid or null.
The pointer to the targets in these structures must be valid.
Check that sessions and media_type are specified correctly.
Also, if the lobpaths parameter is specified, check that the media_type is the same as that specified for the datafile structure.
If the filetype is IXF, the length of the file name may be too long.
The command cannot be processed. "
"The parameter contains a path, directory, or file name that is not valid.
For IMPORT and EXPORT, verify the datafile parameter.
For LOAD, verify that each entry in the parameters of type sqlu_media_list : datafile should contain valid filenames; lobpaths copytarget , and workdirectory should contain valid paths on the server including the final separator and a null terminator.
The pointer to lobpaths, copytarget and workdirectory must be valid or null.
The pointer to the targets in these structures must be valid.
Check that sessions and media_type are specified correctly.
Also, if the lobpaths parameter is specified, check that the media_type is the same as that specified for the datafile structure.
If the filetype is IXF, the length of the file name may be too long.
The command cannot be processed. "
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
-
- Participant
- Posts: 18
- Joined: Tue Nov 15, 2005 9:36 am
Hi
Hi,
I have seen the same issue as above. The problem is that the table load job that i ran was running fine for the last 15 runs.
Recently it started giving troubles. It aborts sometimes with the -3025 SQLCODE and i wont be able to simulate the same error after 3 days.
Still not able to figure out why this job aborts when there is no change in the DataStage or Db2 env. And its like a real pain to not be able to understand the issue and fix it.
I have seen the same issue as above. The problem is that the table load job that i ran was running fine for the last 15 runs.
Recently it started giving troubles. It aborts sometimes with the -3025 SQLCODE and i wont be able to simulate the same error after 3 days.
Still not able to figure out why this job aborts when there is no change in the DataStage or Db2 env. And its like a real pain to not be able to understand the issue and fix it.