• Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » After export job when running at command line

#1 2012-06-12 02:55:18

rinocm
New member
Registered: 2012-06-12
Posts: 7

After export job when running at command line

Tags: [error, export, odbc, run]

I have successfully built and ran a sync job in the TOS designer. After exporting the job to run via the .BAT I get the error shown on the screen shot. It appears to be because of the ODBC connection to MS SQL. I have not been able to get the native MS SQL connection to work properly but ODBC works fine in the TOS designer.

Any thoughts?


Uploaded Images

Offline

#2 2012-06-12 05:10:00

pedro
Member
Registered: 2011-11-17
Posts: 3682

Re: After export job when running at command line

Hi

The error indicates some insert data may be longer than the length of field you defined.
Where do you deploy this job? In the same machine where TOS installed?

Regards,
Pedro


Only Paranoid Survive.

Offline

#3 2012-06-12 21:41:12

rinocm
New member
Registered: 2012-06-12
Posts: 7

Re: After export job when running at command line

Yes this export job is running on the same machine that is was created and ran in the interface from.

When running from the interface there is no errors and the job runs perfectly.

any thoughts on where I should start trouble shooting?

thanks!

Offline

#4 2012-07-19 22:40:27

newmer
Member
Registered: 2012-07-18
Posts: 13

Re: After export job when running at command line

Any updates on this? I am experiencing the same issue. My job runs fine in TOS, but when I export and try running the batch I get the same error as above.

Offline

#5 2012-07-23 00:51:29

alevy
Member
Registered: 2009-11-20
Posts: 1488

Re: After export job when running at command line

It looks to me more like a 32-bit/64-bit mismatch between your Java version and your ODBC connection...

Offline

#6 2012-07-23 03:08:15

pedro
Member
Registered: 2011-11-17
Posts: 3682

Re: After export job when running at command line

Hi

Yes. I agree with Alevy. Usually this is caused by 64bit system.

Regards,
Pedro


Only Paranoid Survive.

Offline

#7 2012-07-23 14:47:24

newmer
Member
Registered: 2012-07-18
Posts: 13

Re: After export job when running at command line

Hi Pedro/Alevy,

Do you guys know how I could resolve this? I have been tring to find a way to get this to work but have been unable to.

Thanks!

Offline

#8 2012-07-24 04:10:38

pedro
Member
Registered: 2011-11-17
Posts: 3682

Re: After export job when running at command line

Hi

Usually I suggest user should use JDBC way of sql server.

Regards,
Pedro


Only Paranoid Survive.

Offline

#9 2012-07-24 07:54:24

alevy
Member
Registered: 2009-11-20
Posts: 1488

Re: After export job when running at command line

Presumably your system is 64-bit?  Have you installed both 32-bit and 64-bit Java?  Which Talend studio are you running?  Which Java are you running in the exported job (go to command line and type "java -version")?  Have you created your DSN under 32-bit or 64-bit?

Basically, make sure all are using the same.

Offline

#10 2012-07-24 07:55:29

alevy
Member
Registered: 2009-11-20
Posts: 1488

Re: After export job when running at command line

But Pedro is right.  JDBC is much faster than ODBC.

Offline

#11 2012-07-24 16:34:15

newmer
Member
Registered: 2012-07-18
Posts: 13

Re: After export job when running at command line

I have tried to use JDBC for my connection, but it is not working. I get the error "Connection failure. You must change the Database Settings.
  Impossible to initialize the connection !"

Note: Trying to connect to SQL Azure.

The ODBC connection works fine within talend and I am able to run the job just fine. The error is just when it is exported and tried to run. I am on a 64-bit machine. Using 64-bit Java, running Talend 5.1.1. I have tried creating DSN's in both 32-bit and 64-bit with no success. Getting the Invalid string or buffer length error.

Offline

#12 2012-07-25 03:12:43

alevy
Member
Registered: 2009-11-20
Posts: 1488

Re: After export job when running at command line

If it runs in the studio, it should run exported.  Which Talend studio exe are you running: 32-bit or 64-bit?  Go to command line and type "java -version": is it 32-bit or 64-bit?

Offline

#13 2012-09-10 05:21:13

jesa_l
Member
Registered: 2012-07-18
Posts: 16

Re: After export job when running at command line

I'm having the same problem.
I am using generic jdbc connections for database connectivity. The job runs fine in Talend Studio but doesn't run when exported.

java - version gives me:
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b05)
Java HotSpot(TM) Client VM (build 20.6-b01, mixed mode, sharing)

I'm running TOS DI 5.1.1 on Windows server standard SP2.
OS is 4 bit.

-Jesal

Last edited by jesa_l (2012-09-10 05:23:09)

Offline

  • Index
  •  » Talend Open Studio for Data Integration » Usage, Operation
  •  » After export job when running at command line

Board footer

Powered by FluxBB