the folder ETL_Processes is set up as a network share. I am using an ID in the stage that has access to the dir.
Can anyone point me in the right direction?
Jim
I have been tring to get a DB2 Load stage to work for a few days now. At first it seemed to be a bit of user error, now it seems to be a bit of user confusion.
Im having trouble currently with the msg output directories. This is right from the help file
Local Message File Name*. The string containing the pathname for the local file name used for output messages.
Remote Message File Name*. The string containing the pathname for the file name used by UDB server for temporary files. Temporary files are created to store messages and consistency points and to delete phase information. You must ensure that each load has a unique fully qualified remote file name.
Does this mean that DS will create the txt file or do I have to have it already created before the job runs?
SQL3508N Error in accessing a file or path of type "TEMP_FILE" during load or
load query. Reason code: "1". Path:
"D:\ETL_Processes\temp\JOCEStageTemp.txt\DB200005.PID\DB200".
Look at the directory that it it is looking for. I supplied
It is really an old post. I encountered the same problem today. ETL server and DB2 reside on different machine. Does anyone know how to point 'Directory for Data and Command Files' to the DB2 box? It will be ok if I point it to ETL server dirctory.
JDionne wrote:Please forgive me if this is simple, but I am running on about 5 hours of sleep so Im starting to see double right about now.
This is my error:
the folder ETL_Processes is set up as a network share. I am using an ID in the stage that has access to the dir.
Can anyone point me in the right direction?
Jim
I faced this exact same problem once. I dont have access to DataStage right now but i know that in the Load stage, the first two directory paths should be pointing towards your Datastage server and the last one is the udb server. I myself couldnt believe that. But the IBM support persons asked me to test it with specifying the udb server directory. To my surprise, it worked.
If you guys can wait till monday, i can tell you exactly where the UDB server path is to be specified.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.