topic Re: nzload usage error in Talend Studio

nzload usage error

Anonymous — Sat, 16 Nov 2024 12:55:15 GMT

Hi,
I tried running a simple nzload from a file using the tNetezzaNzload component but am getting a usage error:nzload.exe .
I am using talend integration suite ver 4.1.2.r53516.
Is this a version problem of nzload.exe utility

Re: nzload usage error

Anonymous — Tue, 17 May 2011 07:37:20 GMT

Hi
It is a usage error, can you upload some screenshots of tNetezzaNzload? include the advanced settings.
Best regards
Shong

Re: nzload usage error

Anonymous — Tue, 17 May 2011 10:24:33 GMT

basic and advanced settings screeshot.

Re: nzload usage error

Anonymous — Tue, 17 May 2011 19:49:58 GMT

nzload can be picky, but the component also has a couple of issues that make development with it difficult. it does not print stderr to the console. nzload is giving you (somewhat) helpful error messages, you just dont see them. Run the command from the commandline to see them.
My advice is this: you can use injection to print the nzload command to your console, this will allow you to run the command from the command line to debug the issues your seeing.
in the advanced settings page define at least one option. this is from the -lf option but it can be used with any option as long as it is the LAST option in the list:

"/path/to/log/file.nzlog"}; for(String cmd : cmds) { System.out.println(cmd); } {

If you take a look at the generated code, it should be pretty clear what this does

Re: nzload usage error

Anonymous — Thu, 07 Jun 2012 03:51:33 GMT

Hi Sonu2562
The answer is YES.
Regards,
Pedro

Re: nzload usage error

Anonymous — Thu, 07 Jun 2012 06:18:53 GMT

Hi
Please show me the settings of this component.
Regards,
Pedro

Re: nzload usage error

Anonymous — Thu, 07 Jun 2012 06:33:56 GMT

Hi
I guess you have selected "Specify nzload path" option.
The full path you set is "C:/JDBC/" which is not correct.
It should be like this "C:/JDBC/nzload.exe".
Regards,
Pedro

Re: nzload usage error

Anonymous — Thu, 07 Jun 2012 09:07:39 GMT

any suggestion?