Build Ended in Error - R9621 (SPC0000502)


Reputable Poster
We are on E1 9.0, tools

Until today, we have had no issues in building and deploying packages to our Dev environment DV900.

However, today, when we attempt to build an update package we receive an error on the R9621 Package Build report that states 'Build Ended in Error'. Looking at jde.log there are multiple error messages with the first significant error being SPC0000502 - Could not determine database type for data source. The Server Package Build R9622 though shows Build Completed Successfully. Since we received the error on R9621 we did not proceed with the deploy.

So our questions are

1. what could cause this error and what do we need to do to resolve it.
2. even with the error on the Client package build, can we still proceed with the deploy or does this error need to be resolved first. Searching on the message SPC0000502 appears to show that this is perhaps an erroneous benign error, but would like confirmation.

The R9621 and R9622 are attached as well are the jde.log. The jde.log shows what appears to be the initial significant message SPC0000502 (Could not determine database type for data source).

Any ideas or insight would be appreciated.


  • R9621_XJDE001_D150305_T154220267.pdf
    64.8 KB · Views: 17
  • R9622_XJDE0001_D150305_T154240002.pdf
    65.7 KB · Views: 14
  • jde.log.txt
    6.4 KB · Views: 24

Where are you building the package (Fat Client or Deployment Server) and which environment are you building it in? From the log it looks like the build does not have access to the PLANNER pathcode.

Also, on the deployment server there are two files that may contain more information:


I am more of a JDE Jack-of-all-trades than a true CNC, but have done some minor package build troubleshooting.

There is (or was) a document on the Oracle Support website that detailed Package Build Troubleshooting.

Hopefully a true CNC will respond and offer assistance too.

Not sure if I would call myself a "true CNC", but the real error seems to be here:

UDI-31623: operation generated ORACLE error 31623
ORA-31623: a job is not attached to this session via the specified handle
ORA-06512: at "SYS.DBMS_DATAPUMP", line 3263
ORA-06512: at "SYS.DBMS_DATAPUMP", line 4488
ORA-06512: at line 1

Refer to Oracle Doc ID 754401.1. It has information on how to resolve it. The database in question is your local E1 database on the deployment server. Hope this helps.
Thanks Peter/Hari,

But I rebooted the deployment server (JDEDEPLOY) last evening and that fixed the problem. I can now build and deploy with no errors. Still not sure what happened but I guess first rule of support, reboot it.

I would have done that first thing yesterday but there is actually some production processes that use that server so could not during the day. Something went awry somehow and the reboot apparently put things back in order. Odd but now I can get back to actual work. Thanks for the input.
It looks like you were trying to do the build from the planner pathcode, rather than DEP900 (or DV900 on a fat)
A restart of the local oracle database service would have (probably) fixed the issue. Glad that the issue is now resolved.
It looks like you were trying to do the build from the planner pathcode, rather than DEP900 (or DV900 on a fat)

if u do submit the build from planner environment, u will find that error. just ensure it before submission, its DEP910/DEP900, whatever version u use .

Hi Jimmy,

This seems to be caused due to a timing issue during datasource cache load and refresh. These messages do not affect the package build process.
This is always reported during package build. Package Build creates and drops internal datasources during the build process. When a new datasource 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. This jde.log can be ignored .

JDEPLAN and DEP Environment share the same Pathcode i.e., PLANNER but the OCMs are different.
OCMs for JDEPLAN will point to Objects in E1Local Database whereas OCM for DEP Environment will point to Objects in Master Database(Oracle\SQL\DB2)

Generally DEP Enviornment is used to build the packages for other pathcodes (DV\PY\PD).