set jdbc path

Abdoulaye

Hello, I used Instance templates Setup actions. To install jdbc. I've installed first version which was not accepted by dss design as recent built. I chnaged the version then reprovisonned instances. When I try connect, it found the first jdbc not the second.

How to found the first by path?

DSS_DATA_DIR
├── bin
├── config
├── dss-version.json
├── install.ini
├── jobs
├── lib
│   ├── jdbc
│   │   └── ojdbcXX.jar
│   │   └── ojdbcYY.jar
│   ├── projects
│   ├── python
│   ├── R
│   └── user-data
└── run

Sarina

Hi @abdoulaye
,

Yes, you would need to modify this by SSH-ing into the DSS server. If you don't have access, you can add an SSH keypair task to your Fleet Manager template, which will allow you to SSH into the instance. On a Fleet Manager DSS instance the JDBC driver path will always be:

cd /data/dataiku/dss_data/lib/jdbc
rm <unwanted_jdbc_driver>

Thanks,
Sarina

Sarina

Hi @abdoulaye
,

If I understand correctly, you tried the Fleet Manager JDBC driver task twice, because the first driver you attempted didn't correctly read in your data. Now it seems that you have two JDBC drivers for the same SQL service in your DSS instance, is that correct? To resolve this, you should simply remove the JDBC driver that you no longer want to use (and is no longer in the Fleet Manager JDBC driver task) from your DSS data directory manually. For example, assuming the ojdbcYY.jar file is correct, then remove the alternate ojdbcXX.jar file:

cd DSS_DATA_DIR
rm lib/jdbc/ojdbcXX.jar

Unfortunately reprovisioning doesn't clear JDBC drivers that were created historically by JDBC tasks, so they should be removed manually from the data directory. Having multiple drivers fro the same database in place can cause issues, so this would be the recommended approach.

Thanks,
Sarina

Abdoulaye

Hi,

Is this DSS_DATA_DIR accessible only via ssh login to instances?