This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BMC Atrium CMDB Suite
BMC Atrium Core
AtriumCore 9.1.03 and later with Pentaho connection to Oracle database
Customer is trying to connect to an Oracle database with the Pentaho Spoon bundled with AR Server or installed as AtriumIntegrator Client.
Connection attempt gives an error:
Error connecting to database [SIRTRO] : org.pentaho.di.core.exception.KettleDatabaseException:
Error occurred while trying to connect to the database
Error connecting to database: (using class oracle.jdbc.driver.OracleDriver)
Caused by: java.lang.NoSuchMethodError: oracle.i18n.text.converter.CharacterConverterOGS.getInstance(I)Loracle/i18n/text/converter/CharacterConverter;
... 64 more
Oracle Java DataBase connection "ojdbc14. jar" file was missing from the \BMC Software\ARSystem\diserver\data-integration\lib folder.
Download the ojdbc14. jar file from the oracle website. It may also be available with the database install.
Put it in BMC Software\ARSystem\diserver\data-integration\lib folder and restart the AR Server.
Verify the connection from Spoon that is local to that AR Server and connect to the database.
For remote (client) Spoon installations, please make sure the same binary is found in the BMC Software\ARSystem\diserver\data-integration\lib folder.
These folder have the same path on all systems. Success of this call depends on where the Spoon client is launched from.
Please note that this will only work locally for each client. If you have users with their own Spoon client installed on their work station then they will need to have the same jar file in place.
Note 2: There can be only one Oracle JDBC driver in the \lib directory at a time. If you are replacing an existing Oracle JDBC driver from that directory, the old driver will need to be moved out of the \lib folder. If it is not removed, when the Pentaho Spoon is relaunched or Atrium Integrator server is restarted, it is possible that it will load the old Oracle JDBC driver instead of the one that replaces it. It may give you an issue where you see the JDBC connecting correctly in one installation but not in another.