I think this is a JDBC warning message since some isolation levels may not
be implemented in the actual (Oracle) implementation (e.g.:
READ_UNCOMMITTED).
May your issue be related to some transactions updating/inserting/deleting
records on your Oracle DB while trying to run DIH?
Regards,
Tommaso
2
Could any one shed a light please?
I saw in the log a message as below, but I don't think it's the root
cause, because my dataSrouce, the readOnly is true
Caused by: java.sql.SQLException: READ_COMMITTED and SERIALIZABLE are
the only valid transaction levels
A newbie Solr user
===
