The ODB0000164 subscription typically sends an email alert when there is an issue with the security kernel. But there are several situations where this may occur.
A new full package was deployed to path code
Review the logged details when you start services. For example:
[SQL Server]Invalid object name 'JDE_PD910.F98710PD910FE'.
[SQL Server]Statement(s) could not be prepared.
SQLNumResultsCols failed. Table F98710PD910FE, ODBC DSN Central Objects - PD910
In this case, a "failed" error is pointing to the datasource in Central Objects. To resolve the issue, you need to change the Use Table Owner flag in the definition.
Check out My Oracle Support for detailed steps.
The ODBC datasource is incorrect
An ODB0000164 error can occur if a 64-bit odbcad32 executable is used to create the datasource and your JD Edwards application only supports 32-bit.
Use the 32-bit executable to fix the error.
Central Objects are missing the runtime spec tables
You will also see an ODB0000164 error if Central Objects in a deployed package are missing the runtime spec tables. There are two possible solutions:
- Rename the runtime tables and restart services.
- Build a new full package.