NAC reports a "session has been killed" error. The NAC's nolio_dm_all.log files then capture the following errors:
WARN (org.hibernate.engine.jdbc.spi.SqlExceptionHelper:143) - SQL Error: 28, SQLState: 08006
ERROR (org.hibernate.engine.jdbc.spi.SqlExceptionHelper:144) - ORA-00028: your session has been killed
ERROR (com.nolio.platform.server.dataservices.services.hibernate.NolioHibernateTemplate:203) - Caught hibernate exception.org.hibernate.exception.JDBCConnectionException: ORA-00028: your session has been killed
The group of errors above occur when Oracle database generates an ORA-00028 error. There are several possible causes for Oracle to return this error to Release Automation. ORA-00028 usually indicates a privileged user (such as a DBA) has manually killed the session. This can happen if database maintenance tasks are being performed at the time of the error or if the database user has decided to identify and kill that session for some reason.
There are other possible causes for this error, including:
Any Release Automation environment running with Oracle database.
After identifying which of the possible causes above is at play, solutions follow, respectively:
For more information regarding ORA-00028, there are many online resources outside of CA worth consulting. Oracle provides their own Oracle Technology Network community that provides a number of resources for finding more detailed information on this and other ORA errors.