Page 1 of 2
Dscmdexport Memory Error
Posted: Fri Jun 12, 2009 11:20 am
by Vivek Vazarkar
Hi All,
I'm using datastage 8x server edition & Windows 2003 NT as a OS. While executing the dscmdexport command I'm getting memory error.
Command:-
D:\IBM\InformationServer\Clients\Classic\dscmdexport.exe /D=DS_QA:1080 /U=Dsadmin /P=???? /H=DS_QA DataWarehouse D:\Temp\DataWarehouse.dsx
Domain Name:- DS_QA:1080
User Name:- Dsadmin
Host:- DS_QA
Project:- DataWarehouse
Error:-
The instruction at "0x00000000" referenced memory at "0x00000000". The memory could not be "written".
Click OK to terminate the program.
If you any idea, please let me know.
Posted: Sun Jun 14, 2009 4:14 pm
by ray.wurlod
Do you have at least 2GB of memory in the client machine?
Posted: Sun Jun 14, 2009 11:56 pm
by Vivek Vazarkar
ray.wurlod wrote:Do you have at least 2GB of memory in the client machine? ...
yes 3.5 GB memory is free.
Posted: Mon Jun 15, 2009 3:14 am
by ArndW
Looks like a null pointer somewhere. Does it happen only with this job?
Posted: Mon Jun 15, 2009 3:20 am
by priyadarshikunal
Vivek Vazarkar wrote: yes 3.5 GB memory is free.
Is it RAM?
Vivek Vazarkar wrote:Domain Name:- DS_QA:1080
Is your script working with this port?
Posted: Mon Jun 15, 2009 3:27 am
by Vivek Vazarkar
priyadarshikunal wrote:Vivek Vazarkar wrote: yes 3.5 GB memory is free.
Is it RAM?
Vivek Vazarkar wrote:Domain Name:- DS_QA:1080
Is your script working with this port?
Hi,
Its not a RAM memory, its 3.5 GB harddisk memory is free.
I tried both ways domain name as DS_QA & DS_QA:1080. Still it showing above memory error.
I want to add one more information, for another project it is not showing any memory error message.
Posted: Mon Jun 15, 2009 3:28 am
by Vivek Vazarkar
ArndW wrote:Looks like a null pointer somewhere. Does it happen only with this job? ...
Hi ArndW.
Its happning only with this job.
Posted: Mon Jun 15, 2009 3:31 am
by Vivek Vazarkar
Vivek Vazarkar wrote:ray.wurlod wrote:Do you have at least 2GB of memory in the client machine? ...
yes 3.5 GB memory is free.
Ray,
What you think about Windows Service Pack 2. Does it creating any troubble for any datastage job?
Posted: Mon Jun 15, 2009 3:31 am
by ArndW
Can you do an export of that job from the client? Perhaps it is not the command line export that is broken, but the job itself.
Posted: Mon Jun 15, 2009 3:32 am
by Vivek Vazarkar
ArndW wrote:Can you do an export of that job from the client? Perhaps it is not the command line export that is broken, but the job itself. ...
ArndW,
I'm able to take export from datastage designer manually. When I tried to take backup from the command that time it creating problem.
Posted: Mon Jun 15, 2009 3:53 am
by priyadarshikunal
ArndW wrote:Looks like a null pointer somewhere. Does it happen only with this job? ...
dscmdexport is for complete project backup and since its a command line utility, any problem with jobs should not lead to a window saying
Click OK to terminate the program.
Probably the system is running out of RAM as well as Paging space.
or he is using dsexport.
Vivek,
For your information below is the formal syntax to run dscmdexport in verbose mode to get errors written to a file. every thing enclosed between '%' is a parameter and x is formatted date.
dscmdexport /D=%ServerIp%:9080 /H=%ServerIp%:31801 /U=%userName% /P=%Password% %ServerName%/%ProjectName% %BaseDir%\Project_Export_%x%\ProjectExport_%x%.dsx /v > %BaseDir%\Project_Export_%x%\ExportLog_%x%.log
Posted: Mon Jun 15, 2009 3:54 am
by ArndW
If you re-import the .dsx file into another project, can you then do a dscmdexport on it? If no, then you have a reproduceable test case to submit to IBM support (or to whomever you use for support). If yes, then something is wrong with the job's internals and you might as well import the .dsx file and overwrite the job.
Posted: Mon Jun 15, 2009 9:27 am
by Vivek Vazarkar
priyadarshikunal wrote:ArndW wrote:Looks like a null pointer somewhere. Does it happen only with this job? ...
dscmdexport is for complete project backup and since its a command line utility, any problem with jobs should not lead to a window saying
Click OK to terminate the program.
Probably the system is running out of RAM as well as Paging space.
or he is using dsexport.
Vivek,
For your information below is the formal syntax to run dscmdexport in verbose mode to get errors written to a file. every thing enclosed between '%' is a parameter and x is formatted date.
dscmdexport /D=%ServerIp%:9080 /H=%ServerIp%:31801 /U=%userName% /P=%Password% %ServerName%/%ProjectName% %BaseDir%\Project_Export_%x%\ProjectExport_%x%.dsx /v > %BaseDir%\Project_Export_%x%\ExportLog_%x%.log
Hi priyadarshikunal,
I used above syntax & executed the dscmdexport command. Still it showing the same memory error message.
Posted: Mon Jun 15, 2009 9:42 am
by priyadarshikunal
%BaseDir%\Project_Export_%x%\ExportLog_%x%.log
Do you have any error message in this file.
Can you please let us know how much RAM you have on client machine and whether client is running on server itself?
Posted: Mon Jun 15, 2009 10:00 am
by priyadarshikunal
Else go for Arnd's suggestions. Test it in another environment and if it doesn't work then send it to IBM.