IBM Connections Content Manager (CCM) was no longer working for a customer although everything was ok a few days ago. While starting the CCMCluster the following error occurded in SystemOut.log:
|
1 2 3 |
FNRCD0002E - ERROR The database vendor cannot be determined from the JNDI data source or is an unsupported type. Check the data source and verify the database connection. com.filenet.api.exception.EngineRuntimeException: FNRCD0002E: DB_BAD_DATABASE_VENDOR: The database vendor cannot be determined from the JNDI data source or is an unsupported type. Check the data source and verify the database connection. at com.filenet.engine.dbpersist.DBContext.determineDatabaseType(DBContext.java:882) |
Solution:
The customer changed the Linux access rights for “/tmp” for whatever reason. The changed the owner and also removed the rights for writing for “Others”. Therefore DB2 was no longer able to write some files to “/tmp” as the user “db2inst1” has no right for writing anymore. Also the stickybit was no longer set for “/tmp”:
Rights before:
|
1 |
drwxrwxr-x. 20 wasuser wasuser 57344 Feb 28 03:48 tmp |
Rights after “chmod 1777 /tmp”:
|
1 |
drwxrwxrwt. 20 root root 57344 Feb 28 03:48 tmp |
Then, after restarting the whole envrionment including the DB2, everything worked again.
IBM Connections CCM – FNRCD0002E – ERROR The database vendor cannot be determined from the JNDI data source