Error in JDE.LOG During Package Build: Could not determine database type for data source

When building a package for a new 9.1 installation, I noticed the following errors in the jde.log:

7032/7768 WRK:Starting jdeCallObject Wed Feb 27 06:26:15.517000 SpecPkgBld.c4280 
SPC0000502 - Could not determine database type for data source. Data source is probably invalid. (Datasource: Local - PLANNER Specs) 

7032/7768 WRK:Starting jdeCallObject Wed Feb 27 06:26:15.517001 SpecOpen.c2633 
jdeSpecOpenLocalOpt completed in error - JDESPECRESULT_FAILED.

That doesn’t really seem right. How could the “Local – PLANNER Specs” datasource be “invalid”? Well, not to worry. Here is what I found on Oracle Support:

E1: PKG: JDE.LOG Error Messages When Building Packages – SPC0000502 – Could Not Determine Database Type For Data Source [ID 651676.1]

These messages do NOT affect the package build process.
Development is aware and some SARs as Bug 8293709 has been entered to clean up the messages in the jde.log. This seems to be caused due to a timing issue during datasource cache load and refresh. This is always reported during package build. Package Build creates and drops internal datasources during the build process. When a new datasource(DS) is created, it calls JDB to refresh DS cache. At around the same time, Busbuild process is loading the DS cache – and it fails to get the DS type.
However, the jde.log messages are harmless and can be ignored.

Just more scary error messages that can be ignored :-/

Author

Stewart Schatz

Career: Principal CNC Consultant for Syntax Systems Limited specializing Oracle JD Edwards EnterpriseOne and the technology that supports it. Side Hustle: Owner/Operator of E1Tips.com Location: Lancaster, PA USA  What I like to do: Invest in Family, Explore Technology, Lead Teams, Share Knowledge/Experience, Hunt, Hike, etc.

stewart@9rains.com

http://stewartschatz.com

Happy

0

Sad

0

Excited

0

Sleepy

0

Angry

0

Surprise

0