Just downloaded SQLcl 18.1.1 today and can't get it to connect to my databases. The database is an Exadata cluster and I have production and development instances setup in tnsnames.ora. I'm consistently getting the following error.
SQL> conn u0363644@prod
Password? (**********?) **********
USER = u0363644
URL = jdbc:oracle:oci8:@prod
Error Message = Could not initialize class oracle.jdbc.OracleDriver
USER = u0363644
URL = jdbc:oracle:thin:@(DESCRIPTION = (ADDRESS_LIST = (LOAD_BALANCE = on) (ADDRESS = (PROTOCOL = TCP)(HOST = changed.to.fool.you.1)(PORT = 2080)) (ADDRESS = (PROTOCOL = TCP)(HOST = changed.to.fool.you.2)(PORT = 2080)) ) (CONNECT_DATA = (SERVICE_NAME = papr) ) )
Error Message = Could not initialize class oracle.jdbc.OracleDriver
Jun 01, 2018 2:35:10 PM oracle.dbtools.raptor.newscriptrunner.ScriptExecutor run
SEVERE: oracle.dbtools.raptor.scriptrunner.commands.NLSLANGListener.setLanguage(NLSLANGListener.java:86)
java.lang.NullPointerException
at oracle.dbtools.raptor.scriptrunner.commands.NLSLANGListener.setLanguage(NLSLANGListener.java:86)
at oracle.dbtools.raptor.scriptrunner.commands.NLSLANGListener.runOnConnect(NLSLANGListener.java:52)
at oracle.dbtools.raptor.scriptrunner.commands.NLSLANGListener.endEvent(NLSLANGListener.java:102)
at oracle.dbtools.raptor.newscriptrunner.CommandRegistry.fireEndListeners(CommandRegistry.java:564)
at oracle.dbtools.raptor.newscriptrunner.ScriptRunner.run(ScriptRunner.java:297)
at oracle.dbtools.raptor.newscriptrunner.ScriptExecutor.run(ScriptExecutor.java:342)
at oracle.dbtools.raptor.newscriptrunner.ScriptExecutor.run(ScriptExecutor.java:225)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.process(SqlCli.java:398)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.processLine(SqlCli.java:409)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.startSQLPlus(SqlCli.java:1235)
at oracle.dbtools.raptor.scriptrunner.cmdline.SqlCli.main(SqlCli.java:485)
Using the same TNS file and attempting to connect through SQLcl Release 4.2.0.16.049.0842 RC it works just fine. Anyone have any idea what might be going on here? Is this a bug in the new version?