Thanks a lot ! :>
As someone told me before, if the executable has been run, then the problem occur, otherwise, it works well. Why would this happen ???
If the executable being run, the library file will be revised ???
[Help] Fatal error
Moderators: chulett, rschirm, roy
Hi,
What version of PX are you using? Your job will not get successfully exported when one of the process is not released from the memory (Hope this problem resolved the latest release in DS EE). The workaround way is to export the job to restart the whole server (not only DataStage) and export the job and import it into the production environment. Becuase while exporting the job, this object file was not included in the export due to one of the process was not released from the previous run this problem would occur when there is a transformer in the job.
Hope this would resolve the issue.
Regards
Saravanan
What version of PX are you using? Your job will not get successfully exported when one of the process is not released from the memory (Hope this problem resolved the latest release in DS EE). The workaround way is to export the job to restart the whole server (not only DataStage) and export the job and import it into the production environment. Becuase while exporting the job, this object file was not included in the export due to one of the process was not released from the previous run this problem would occur when there is a transformer in the job.
Hope this would resolve the issue.
Regards
Saravanan
Saravanan, thank you for you reply. I am using PX 7.1
elavenil wrote:Hi,
What version of PX are you using? Your job will not get successfully exported when one of the process is not released from the memory (Hope this problem resolved the latest release in DS EE). The workaround way is to export the job to restart the whole server (not only DataStage) and export the job and import it into the production environment. Becuase while exporting the job, this object file was not included in the export due to one of the process was not released from the previous run this problem would occur when there is a transformer in the job.
Hope this would resolve the issue.
Regards
Saravanan
Hi,
We had the same problem in 7.1. You should restart the whole server if you encounter any problem (The error message is something like "some of the library files not included in the export") while exporting the job and then export the job. Ensure that you do not get any problem while exporting/importing the job.
Hope this would help.
Regards
Saravanan
We had the same problem in 7.1. You should restart the whole server if you encounter any problem (The error message is something like "some of the library files not included in the export") while exporting the job and then export the job. Ensure that you do not get any problem while exporting/importing the job.
Hope this would help.
Regards
Saravanan
Saravanan, you mean the error message will occur while exporting the job? But in my case, there is no error message while exporting. However, when I open the .dsx file with Notepad, something like your message coded in the dsx file.
elavenil wrote:Hi,
We had the same problem in 7.1. You should restart the whole server if you encounter any problem (The error message is something like "some of the library files not included in the export") while exporting the job and then export the job. Ensure that you do not get any problem while exporting/importing the job.
Hope this would help.
Regards
Saravanan
Hi,
Could think of two possiblities.
1. The library path got changed and based on your email that the library path is not changed.
2. The other thing you need to check the version of C++ libraries in both machine that are used to compile PX job.
If version of C++ is not the same, this kind of problem would occur. So check the above two things.
Regards
Saravanan
Could think of two possiblities.
1. The library path got changed and based on your email that the library path is not changed.
2. The other thing you need to check the version of C++ libraries in both machine that are used to compile PX job.
If version of C++ is not the same, this kind of problem would occur. So check the above two things.
Regards
Saravanan
Hi,
In my case, the version of C++ is the same, it is in the same machine, but different project.
Regards,
benny.lbs
In my case, the version of C++ is the same, it is in the same machine, but different project.
Regards,
benny.lbs
elavenil wrote:Hi,
Could think of two possiblities.
1. The library path got changed and based on your email that the library path is not changed.
2. The other thing you need to check the version of C++ libraries in both machine that are used to compile PX job.
If version of C++ is not the same, this kind of problem would occur. So check the above two things.
Regards
Saravanan
As elavenil suggested when you export the file you get such errors when as process is not terminated. If there is any issue during export DataStage writes the error message to dsx file which is happening in your case. The object file created by DataStage on compilation of the job. All teh libraries are linked at this point of time. When a process is not terminated related to this job you cannot get proper export of the executable, which generally causes these kind of problems.
Killing all such process or restarting the server, recompile and export/import of executable should solve the problem.
Killing all such process or restarting the server, recompile and export/import of executable should solve the problem.
Happy DataStaging