java.sql.SQLException: S0022: Invalid column name 'ENCRYPTED_COL'.
at com.sybase.jdbc4.jdbc.ErrorMessage.raiseError(ErrorMessage.java:753)
at com.sybase.jdbc4.tds.TdsResultSet.findColumnByLabel(TdsResultSet.java:739)
at com.sybase.jdbc4.jdbc.SybResultSet.findColumn(SybResultSet.java:1186)
at com.sybase.jdbc4.jdbc.SybResultSet.getInt(SybResultSet.java:738)
at com.sybase.jdbc4.jdbc.SybBCP.addResults(SybBCP.java:443)
at com.sybase.jdbc4.jdbc.SybBCP.<init>(SybBCP.java:182)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.prepareBCP(SybPreparedStatement.java:3449)
at com.sybase.jdbc4.jdbc.SybPreparedStatement.<init>(SybPreparedStatement.java:209)
at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(SybConnection.java:1491)
at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(SybConnection.java:1392)
at com.sybase.jdbc4.jdbc.SybConnection.prepareStatement(SybConnection.java:1363)
at \\...\\ .\\हिñçêČάй語简??한\\.bꉤᢃꎧꄸ void.prepareStatement(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.dꀗꍼꀨ⣭.process(Unknown Source)
at \\...\\ .\\हिñçêČάй語简??한\\.dꀗꍼꀨ⣭.run(Unknown Source)
73 KB
442 B
The issue description doesn't give enough information to reproduce the problem.
- which database server
- which table
- data file
This error is only reproducible on the 11.57 server. I check the INSERT statement that we submit and ENCRYPTED_COL is not in there. Is there any special setting on this server?
When Connection.prepareStatement fails, we perform a regular batch import instead of BCP import.
This error doesn't occur on the 2.73 server with the "pubs3" database.
This error is only reproducible on the 11.57 server. I check the INSERT statement that we submit and ENCRYPTED_COL is not in there. Is there any special setting on this server?
When Connection.prepareStatement fails, we perform a regular batch import instead of BCP import.
This error doesn't occur on the 2.73 server with the "pubs3" database.
I can reproduce in different Sybase ASE Servers. See my attached screenshot with Sybase ASE 15 ending at 11.46 Sybase ASE /15.0.2/EBF 14332
I can reproduce in different Sybase ASE Servers. See my attached screenshot with Sybase ASE 15 ending at 11.46 Sybase ASE /15.0.2/EBF 14332
Tariq, can you reproduce it on 2.73? What is different between these servers?
11.46 is v15.0
11.57 is v15.5
2.73 is v15.7
For my development work, I used 11.82 (which is v15.7) and I didn't see this error (checked my log files).
Tariq, can you reproduce it on 2.73? What is different between these servers?
11.46 is v15.0
11.57 is v15.5
2.73 is v15.7
For my development work, I used 11.82 (which is v15.7) and I didn't see this error (checked my log files).
This error is caused by the latest Sybase jConnect Driver. It works with ASE v15.7, but it causes an error with ASE v15.5 or below that does not support new metadata like ENCRYPTED_COL. Sybase reports that this issue will be fixed in jConnect 7.0.7 SP110.
We've reverted the jConnect Driver to the same version bundled with ADS 13.0.
This error is caused by the latest Sybase jConnect Driver. It works with ASE v15.7, but it causes an error with ASE v15.5 or below that does not support new metadata like ENCRYPTED_COL. Sybase reports that this issue will be fixed in jConnect 7.0.7 SP110.
We've reverted the jConnect Driver to the same version bundled with ADS 13.0.
Reverted the jConnect Driver to the same version bundled with ADS 13.0. Verified in 14.0.0-beta-75
Reverted the jConnect Driver to the same version bundled with ADS 13.0. Verified in 14.0.0-beta-75
Issue #9684 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build ADS 14.0.0-beta-75 |
No time estimate |
The issue description doesn't give enough information to reproduce the problem.
- which database server
- which table
- data file