How to resolve an ODB0000164 alert

February 12th, 2025

1 min read

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.

Topics:

ERP Suites Clarity 23A

How to resolve an ODB0000164 alert

A new full package was deployed to path code

The ODBC datasource is incorrect

Central Objects are missing the runtime spec tables

Related Articles

How to resolve a Java Out of Memory alert

Clarity Dashboard

Log Monitor stopped collecting

Application Monitor

How to resolve a Server CPU Utilized per Instance alert

Log Monitor

Reinstalling/Updating the Clarity Collector

How to resolve a JDE Net Invalid Request Exception

Database Monitor stopped collecting

Batch Monitor stopped collecting

How to resolve an ORA-03113 alert

Installing the Clarity Collector

How to resolve a KNT000086 alert

How to resolve a Manual Open JDB Transactions alert

Exporting Reports in Clarity

Batch Monitor

Application Analytics

Finding expensive database queries

How to resolve a OCI0000064 alert

Maintenance Windows

Finding your slowest applications

How to resolve an ODB0000162 alert

How to resolve an ORA-03114 alert

How to resolve an OALL8 alert

How to resolve a [COULD NOT START SCHEDULER] alert