EnterpriseOne – Install/Upgrade

ESU Cleanup

Since our installations of EnterpriseOne were installed and the data upgraded we have applied and installed thousands of ESUs. On 4 of the 7, we neglected to apply the ESUs to the Pristine pathcode (PS900/PS910). This made researching code changes a bit of a challenge.

So, the other day, I decided to rectify that and apply the many, many ESUs to Pristine. Because there were some very old ESUs and not all of them were registered with Change Assistant, it was a very time consuming. After I had finished, I noticed that there were several ESUs that had only been applied to PS & PD and others that had only been applied to PS, DV & PY. Rather than look through every ESU and risk missing some, I connected to E1LOCAL and wrote a SQL statement to get every ESU that had been applied to the system that was not in every pathcode.

Please see “Use Oracle SQL Developer To Modify The JDE LOCAL Database” for connection instructions.

SELECT * FROM (
	SELECT A.SDPKGNAME AS ESUNAME, 
		A.SDSUDFUT2 AS SYS, 
		PS.SDSUDFUT2 AS PS910, 
		DV.SDSUDFUT2 AS DV910, 
		PY.SDSUDFUT2 AS PY910, 
		PD.SDSUDFUT2 AS PD910 
	FROM F9671 A
	LEFT JOIN F9671 PS 
		ON A.SDPKGNAME = PS.SDPKGNAME 
		AND PS.SDSUDFUT2='PS910' 
		AND PS.SDSUDET = '90'
	LEFT JOIN F9671 DV 
		ON A.SDPKGNAME = DV.SDPKGNAME 
		AND DV.SDSUDFUT2='DV910' 
		AND DV.SDSUDET = '90'
	LEFT JOIN F9671 PY 
		ON A.SDPKGNAME = PY.SDPKGNAME 
		AND PY.SDSUDFUT2='PY910' 
		AND PY.SDSUDET = '90'
	LEFT JOIN F9671 PD 
		ON A.SDPKGNAME = PD.SDPKGNAME 
		AND PD.SDSUDFUT2='PD910' 
		AND PD.SDSUDET = '90'
	WHERE A.SDSUDFUT2='ALL' 
		AND A.SDSUDET ='10'
	ORDER BY A.SDPKGNAME DESC
)
WHERE PS910 IS NULL
	OR DV910 IS NULL
	OR PY910 IS NULL
	OR PD910 IS NULL

How To Redeploy A Package To A Development Client (Fat Client)

I needed to redeploy a full package and all the update packages associated with the pathcode.  So, I used the SQL below to do the job:

 update sy900.f98825 set upinpkst=20 where upmkey='<DEV CLIENT NAME>' and uppathcd='<PATHCODE>' and upjdepkgnm <> '<PACKAGE NAME>' 

Error Installing An Update Package On An E1 Development Client

image thumb Error Installing An Update Package On An E1 Development ClientEvery once in a while we get errors when installing update packages on our E1 Development Clients.

An error occurred during the interview for this component. EnterpriseOne Development Client 1.0.0.0.5. The selected package is not valid. Please see log…

So, we go check the log and we see entries like the following that refer to an old full package:

INFO: 01/23/14 10:10:13.731 Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00
INFO: 01/23/14 10:10:13.731 Cannot get information about the database.  Reason: Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00
INFO: 01/23/14 10:10:13.731 Cannot get information about the database from file E:\E910\package.inf. Cannot get information about the database.  Reason: Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00
INFO: 01/23/14 10:10:13.732 Cannot get information about the package’s database. Cannot get information about the database from file E:\E910\package.inf. Cannot get information about the database.  Reason: Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00
INFO: 01/23/14 10:10:13.732 Package validation failed. An existing package is installed, but we cannot get information about it from the file E:\E910\package.inf. Cannot get information about the package’s database. Cannot get information about the database from file E:\E910\package.inf. Cannot get information about the database.  Reason: Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00
INFO: 01/23/14 10:10:13.733 Validation of package in file \\WC-CORP-VMDEPLY\E910\package_inf\PD910E00.inf failed!!! Package validation failed. An existing package is installed, but we cannot get information about it from the file E:\E910\package.inf. Cannot get information about the package’s database. Cannot get information about the database from file E:\E910\package.inf. Cannot get information about the database.  Reason: Cannot get information about the database from file E:\E910\package.inf. Empty file name for DataFileDestDirSPEC_DV910D00

The errors continually reference the package.inf file, so we go check that out.  There is only one reference to our old full package (DV910D00). It is in the following stanza:

[Oracle Databases]
SPEC_DV910D00=ORACLE
JDELocal_DV910=ORACLE
SPEC_DV910G00=ORACLE
JDELocal_PY910=ORACLE
SPEC_PY910G00=ORACLE
JDELocal_PD910=ORACLE
SPEC_PD910E00=ORACLE

So, it looks like the old package was not completely removed.  We delete that line from the package.inf file and everything works perfectly.

E1 Development Clients can really be a pain in the butt!

Use Oracle SQL Developer To Modify The JDE LOCAL Database

During our upgrade process, we apply all of the ESUs to become “code current” before mirroring the upgraded code to the other pathcodes.

The process of doing this does not automatically update the Electronic Software Updates application to reflect that all of the ESUs are in all the pathcodes.

There a couple of different way to update the grid:

  1. Apply the ESUs to the other environments.  This can be a very long and tedious endeavor because there could be thousands of ESUs to apply.
  2. Update the JDE LOCAL database.

I have done option 1 in the past but found it kind of a pain and since I knew that I didn’t really want the process to really do anything except update the table, I chose to come up with a process to do option 2.

Here is what I did:

  1. Install and configure Oracle SQL Developer.  This is really the hardest part, but really not much of an issue.
  2. Create a connection to the JDESY910 database.  Remember, not only is JDESY910 the name of the database, but by default it is also the UserID and Password.
    image thumb Use Oracle SQL Developer To Modify The JDE LOCAL Database
  3. Run the following SQL
     INSERT INTO F9671 (SDPKGNAME,SDSUDET,SDSUDS,SDSUDATE, SDSUTIME,SDSUDFUT1,SDSUDFUT2,SDSUDFUT3,SDUSER,SDPID, SDUPMJ,SDUPMT,SDJOBN) SELECT SDPKGNAME,90,15,113284,111111,' ','DV910',0, 'JDE','SQL',113284,111111,'&lt;deployment name server&gt;' FROM F9671 WHERE SDSUDET=90 AND SDSUDFUT2='PD910' 
    • In this SQL, we upgraded PD910 and then moved the code to DV & PY.
    • We only need the “status 90” records because those are the ones that the grid uses.

Hope this helps.