
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
RetCod: SQL ERROR SqlState: 42601 NativeError 3167
Receiving an error "RetCod: SQL ERROR SqlState: 42601 NativeError 3167 " during execution of the job and not able to connect to the target.
Any help would be appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Team,
Thanks for reaching Qlik community!!
Please can you provide us with the full error line info!!
Regards,
shivananda

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @nithin_seeni ,
Would you please share the target DB types and DB version information?
Thanks,
John.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @nithin_seeni
Hello Team,
Thanks for reaching out to Qlik via Qlik Community Support page. Such issue require through analysis of Settings, hence request you to reach out to technical Support via a case and provide Diagnostics package .
Please refer to Replicate https://community.qlik.com/t5/Knowledge/How-to-collect-Diagnostics-Package-from-Qlik-Replicate/ta-p/...
Regards,
Sushil Kumar

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The SQL error you're encountering is related to syntax issues in your SQL query or statement. The SqlState: 42601 indicates a syntax error, and the NativeError 3167 provides additional details specific to the SQL database you’re using. This error commonly occurs when there is a problem with the SQL syntax, such as a missing keyword, incorrect placement of commas, or an improperly formatted query.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello @nithin_seeni
The SQL error code 42601
indicates a syntax error. SQLSTATE error codes are standardized, and 42601
is used to denote syntax issues across various SQL databases.
Regards,
Suresh
