TFZ
Well Known Member
Did you delete the ojdbc7.jar from the misc folder (or rename it?)
yes, move ojdbc7.jar into BAK folder. So ojdbc8.jar is in use.Did you delete the ojdbc7.jar from the misc folder (or rename it?)
We have ojdbc8.jar placed in MISC folder. Could you provide details what mismatch is?Most likely a mismatch between the jdk and the oracle jdbc driver you have in the MISC folder.
The issue is fixed. There are two things to attention: 1) place 3 files into MISC folder: ojdbc8.jar, ons.jar, ucp.jar 2) delete all other files under MISC folder. This is very important. If you have more jdbc driver files under MISC, it will cause problem too. Because multiple jdbc drivers will be loaded. You are expected to see error msg like : package oracle.jdbc.pool is sealed.We have ojdbc8.jar placed in MISC folder. Could you provide details what mismatch is?
This is a good point. Now the ESU deployment issue is fixed. We switch tools release back to 32-bit TR924 to deploy JN10023, it worked. Then switch tools release again to TR926.Don't you also need to take into account what other linked software you maybe using first?
We for example have to wait until we upgrade our Oracle database and wait for DSI to certify MEP with 9.2.6. all this before we take 9.2.6.
Check your database data source definitions in your planner environment. Perhaps a wrong definition somewhereNew issue: deploy BSFN ESU - JN17537 to DV920 failed. A database login shows asking for password. The user name TESTDTA is correct. The database name is wrong. The correct database name should be our non-prod database. Now it connects prod database. Why a wrong database name is used in this ESU deploy. Thx.
Data source in Planner is verified and it is correct. We successfully deploy all other BSFN ESU successfully. This is the only one with problem.Check your database data source definitions in your planner environment. Perhaps a wrong definition somewhere
Data source in Planner is verified and it is correct. We successfully deploy all other BSFN ESU successfully. This is the only one with problem.
We wouldn't be installing the ASU but the 64 bit ESUs that I know contain a few baselines. Still a lot less impact than UN6 when reviewing the items based on the modules we use. To answer your question though the latest ASU is UN2 with sporadic ESUs since thenThe major step would be installing the ASU. What is the latest ASU / Update installted to your machine?
Thanks. After i review the folder structure on JDE Enterprise server, I find sub folder is only created based on full package under bin64. I think you are right.The Zero Downtime deployment is for full packages only (so far). As of now, I believe that update packages will still lock the target server.
As others have said
We installed 9.2.5.5 as 32 bit first then upgraded it to 64bit using the supplied tools
Next step would be 9.2.6 if we needed it but that's going to wait a few months/years before we do (don't ask)
We use essential cookies to make this site work, and optional cookies to enhance your experience.