Feedback
Did this article resolve your question/issue?

   

Article

Connection error "invalid schema name" occurs when connecting to Cassandra with the Connect for JDBC Cassandra driver.

Information

 
TitleConnection error "invalid schema name" occurs when connecting to Cassandra with the Connect for JDBC Cassandra driver.
URL NameConnection-error-invalid-schema-name-occurs-when-connecting-to-Cassandra-with-the-Connect-for-JDBC-Cassandra-driver
Article Number000147494
EnvironmentProduct: Connect for JDBC Cassandra driver
Version: All supported versions
OS: JAVA
Database: Cassandra
Application: All supported applications
Question/Problem Description
Connection error "invalid schema name" occurs when connecting to Cassandra with the Connect for JDBC Cassandra driver.
Steps to Reproduce
Clarifying Information
The schema name referenced in the error message does exist.
Error Message[Cassandra]invalid schema name: XXXXXXXX
Defect Number
Enhancement Number
Cause
The schema referenced was created in Cassandra after the driver had created the local schema definition files.
Resolution
Recreate or update the local database files on the client.
There are 2 options:
1) Add createdb=forceNew to your connection URL.
2) Delete all local database files in the directory specified in the data source parameter "Schema Definition". A new database connection will rebuild those files.

Note if option 1 is chosen be sure to remove the connect option from the URL after the local files have been updated. Slower connect performance may be noted while using this connect option.
Workaround
Notes
Last Modified Date10/12/2015 11:59 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.