Greetings,
I’m running the Liquibase Maven Plugin and am encountering the following error trying to run Liquibase against a remote server:
[INFO] [liquibase:update {execution: runDDL}]
[INFO] ------------------------------------------------------------------------
[INFO] Parsing Liquibase Properties File
[INFO] File: /Users/emorris/Documents/workspace-sts-2.6.1.RELEASE/project-db-config/src/main/resources/dev/liquibase.properties
[INFO] ‘classpath’ in properties file is not being used by this task.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error setting up or running Liquibase: java.sql.SQLException: Io exception: Oracle Error ORA-12650
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Sep 30 11:16:05 EDT 2011
[INFO] Final Memory: 10M/81M
[INFO] ------------------------------------------------------------------------
The full text of the Oracle error states the following:
$ oerr ora 12650
12650, 00000, “No common encryption or data integrity algorithm”
// *Cause: The client and server have no algorithm in common for
// either encryption or data integrity or both.
// *Action: Choose sets of algorithms that overlap. In other words,
// add one of the client’s algorithm choices to the server’s
// list or vice versa.
Does anybody know if there is any way to pass the data integrity or encryption information via the JDBC thin client connection string (url=jdbc:oracle:thin:@::) in the .properties file? I’ve not been able to find any examples of doing this through a connect string used in this manner.
As a work-around, we tried using the Oracle OCI; however, we ran into a totally different issue there (that’ll be another post).