Aborting the discovery process. com.jdedwards.database.services.packagelookup.PackageLookupServiceException: PackageLookUpService

Issue
IBM WebSphere cast iron (or for that matter any integration tool) is not able to connect to JDE.
JAS.log contains below errors ...

Log Snippet
30 Sep 2014 08:35:54,313 [APP   ]  - [JDBJ]            SELECT EMPATHCD,EMDL01,EMMKEY,EMSERSHP,EMSTCE,EMMRGOPT,EMRLS,EMJDEDBTYP,EMDATS,EMINSPAR,EMUNCFLG,EMPID,EMUSER,EMUPMJ,EMUPMT,EMDBSY FROM SY910.F00942 WHERE (EMPATHCD = ? )
30 Sep 2014 08:35:54,314 [APP   ]  - [JDBJ]             SQL statement parameter marker values are :
30 Sep 2014 08:35:54,314 [APP   ]  - [JDBJ]             Param1 : DV910_Types.VARCHAR,
30 Sep 2014 08:35:54,330 [MANDATORY]  - [JDBJ]            This server is using Automatic Package discovery.
30 Sep 2014 08:35:54,330 [MANDATORY]  - [JDBJ]            The serialized object database will be maintained by the system.
30 Sep 2014 08:35:54,341 [APP   ]  - [JDBJ]            SELECT LMLL,LMRLS,LMPATHCD,LMENHV01 FROM SY910.F00941 WHERE (LMLL = ? )
30 Sep 2014 08:35:54,341 [APP   ]  - [JDBJ]             SQL statement parameter marker values are :
30 Sep 2014 08:35:54,342 [APP   ]  - [JDBJ]             Param1 : DV910_Types.VARCHAR,
30 Sep 2014 08:35:54,359 [APP   ]  - [JDBJ]            SELECT OMENHV,OMDATP,OMSRVR,OMDATB,OMOOWN,OMDLLNAME,OMLL,OMLIB,OMOMUI,OMOMTO,OMOMDS,OMOMJD,OMOMCC,OMDSTP,OMPID,OMDATUSE,OMUSER,OMOCM1,OMJOBN,OMOCM2,OMUPMJ,OMOCM3,OMUPMT,OMOCMA,OMOCMB,OMOCMC,OMOCMDSC,OMSVRPORT,OMDATB2,OMLOBFLG,OMUNICODE,OMDBINST FROM SY910.F98611 WHERE (OMDATP = ? )
30 Sep 2014 08:35:54,359 [APP   ]  - [JDBJ]             SQL statement parameter marker values are :
30 Sep 2014 08:35:54,360 [APP   ]  - [JDBJ]             Param1 : LOCAL_Types.VARCHAR,
30 Sep 2014 08:35:54,369 [APP   ]  - [JDBJ]            Discovered the enterprise server at host <LOCAL>, port <6016>.
30 Sep 2014 08:35:54,372 [APP   ]  - [JDBJ]            SELECT MDMCHRCDNM FROM SY910.F9651 WHERE ((MDMKEY = ?  AND MDPORTNUM = ?  AND MDMCHDETTYP = ? ))
30 Sep 2014 08:35:54,372 [APP   ]  - [JDBJ]             SQL statement parameter marker values are :
30 Sep 2014 08:35:54,373 [APP   ]  - [JDBJ]             Param1 : LOCAL_Types.VARCHAR,
30 Sep 2014 08:35:54,373 [APP   ]  - [JDBJ]             Param2 : 6016_Types.NUMERIC,
30 Sep 2014 08:35:54,374 [APP   ]  - [JDBJ]             Param3 : 32_Types.VARCHAR,
30 Sep 2014 08:35:54,384 [APP   ]  - [JDBJ]            Deployment status on the enterprise server is <UNDEFINED>.
30 Sep 2014 08:35:54,385 [WARN  ]  - [JDBJ]            Deployment status on the enterprise server is <UNDEFINED>. Assuming the package is functional.
30 Sep 2014 08:35:54,387 [APP   ]  - [JDBJ]            SELECT SKSERSHP FROM SY910.F96511 WHERE ((SKMKEY = ?  AND SKPORTNUM = ?  AND SKPATHCD = ?  AND SKMCHDETTYP = ? ))
30 Sep 2014 08:35:54,387 [APP   ]  - [JDBJ]             SQL statement parameter marker values are :
30 Sep 2014 08:35:54,388 [APP   ]  - [JDBJ]             Param1 : LOCAL_Types.VARCHAR,
30 Sep 2014 08:35:54,388 [APP   ]  - [JDBJ]             Param2 : 6016_Types.NUMERIC,
30 Sep 2014 08:35:54,389 [APP   ]  - [JDBJ]             Param3 : DV910_Types.VARCHAR,
30 Sep 2014 08:35:54,389 [APP   ]  - [JDBJ]             Param4 : 31_Types.VARCHAR,
30 Sep 2014 08:35:54,399 [SEVERE]  - [JDBJ]            For server <LOCAL>, port <6016>, pathcode <DV910>, failed to find the deployed package. Aborting the discovery process. com.jdedwards.database.services.packagelookup.PackageLookupServiceException: PackageLookUpService: Could not find attribute <31> in table F96511 for host <LOCAL>, port <6016>, pathcode <DV910>.

Analysis

The environment specified in the JDBj.ini is 'DV910'.

So, based on the DEFAULT OCM mappings for BSFN, LOCAL data source has been picked up and the subsequent logic expected entries for 'LOCAL' machine in F9651/F96511 tables

[JDBj-BOOTSTRAP SESSION]

environment=DV910

As there will not be any packages (type 31 record) for LOCAL machine, connectivity to JDE failed

Solution

Now, the environment in the JDBj.ini is changed to JDV910 and connection is successful

[JDBj-BOOTSTRAP SESSION]

environment=JDV910

If you come across this issue with JDV910 as well, perform a full package build and try again