Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us to spark ideas for how to put the latest capabilities into action. Register here!
cancel
Showing results for 
Search instead for 
Did you mean: 
Alpha549
Creator II
Creator II

Access error (tDBOutput)

Hello everyone,

I have to create an Access database file, getting data from an Oracle database.

net.ucanaccess.jdbc.UcanaccessSQLException: unexpected token: , required: )

at net.ucanaccess.jdbc.UcanaccessStatement.execute(UcanaccessStatement.java:145)

I placed an Access component in my job. I had to download some jars : jackcess-2.1.0.jar and jackcess-encrypt-2.1.0.jar.

However, they couldn't be downloaded by Talend itself... I had to download them on the net manually :

Here http://www.java2s.com/example/jar/j/download-jackcess210jar-file.html and here http://www.java2s.com/example/jar/j/download-jackcessencrypt210jar-file.html and add them clicking on the jar icon, on the Windows showing that these jar are necessary.

I could connect to my Acess DB file. However, when I try to insert data, I have the above error.

Has anyone encountered this error ?

Thank you everyone,

Labels (3)
1 Solution

Accepted Solutions
Alpha549
Creator II
Creator II
Author

I found the solution :

 

FIRST : you have to check the index order type and set it on General or General - Legacy

 

SECOND : in the job, in the tAccessOutput schema, check if the database column is correctly set, because in my case, it was empty and in an orange color.

 

🙂

 

Thank you for your help !

View solution in original post

3 Replies
Anonymous
Not applicable

Hi

Check this error always occurs whatever data is inserted or only occurs on a certain row? If the latter, output the reject rows to see which data has the error?

..tDBOutput--reject--tLogRow.

 

Regards

Shong

 

Alpha549
Creator II
Creator II
Author

Hello @Shicong Hong​ 

 

I restarted Talend, and I saw that the error doesn't occur anymore.

 

HOWEVER, when I get the data from another Oracle table, the error get back...

The job dies in case of error, whereas die option is not activated on the tAccessOutput component...

Alpha549
Creator II
Creator II
Author

I found the solution :

 

FIRST : you have to check the index order type and set it on General or General - Legacy

 

SECOND : in the job, in the tAccessOutput schema, check if the database column is correctly set, because in my case, it was empty and in an orange color.

 

🙂

 

Thank you for your help !