ARIS Community - We Love BPM

MashZone 9.8 and Oracle12c

Jos Ross's picture
by Jos Ross in MashZone posted on 2016-08-30

Hi,.

We are in the middle of the migration Aris7.2 to Aris9.8.
In the ist situation we have MashZone 2.3 and this works perfect with Oracle11g (when finally the right JDBC-Driver was found).

The MashZone 9.8 is now installed and I'm trying to get a connection to an Oracle12c database....(under administration/database connection etc).
I put (manually) the file ojdbc14.jar in the map jdbcdrivers then I stop/start the mashzone services... but the new driver does not pop-up in the JDBC driver selection bar (only the 2 default drivers).
The test-connetion answers to me "Unable to find JDBC driver class "sun.jdbc.odbc.JdbcOdbcDriver" connecting to database "AIAS2"

So I have some questions:
1. the documentation says that you 'have' to use ACC to upload the JDBC drivers, so does this mean that it can not be done manually ?
2. where on the server are the 2 default drivers installed (I can't seen these files in the map jdbcdrivers) 
3. is the ojdbc14.jar the right driver for oracle12c

Kind regards,

Jos

7036 Views
0 Likes
2 Comments
Sorry there are no tags
There are no attachments
Jiri Mares posted on 2016-09-01

Hi, try to follow the documentation as you mentioned, because if you do it via ACC you are at least sure the file is copied to the right destination where the particular runnable needs it. And you will see also error message if something goes wrong. In some cases there are more than one destination and that is why you should use "enhance" command in ACC. It´s not that easy in 9.X as it was in AMZ 2.3, but now almost every configuration could be done from one place = ACC.

BR,

Jiri

Bernd Ziegler posted on 2016-11-18

Hello,

in the online documentation http://documentation.softwareag.com/ibo_bigdata/aris/mashzone981e/MashZone_Online_Help.pdf you can find all information about upgrad vom Mashzone 2.3 to Mashzone 9.8. 

According your Oracle driver question, we used driver "ojdbc7.jar" with name "oracle.jdbc.OracleDriver" and URL "jdbc:oracle:thin:@..." to connect to a orcale database and it worked in our tests.

Maybe the issue based on the wrong driver you used.

BR,

Bernd