E9.2 Question about 64-bit upgrade and TR 9.2.6 upgrade

glen7x

Well Known Member
There is also an ASI that you need to run before the upgrade. It does change for example ODBC datasources that are 32bit to 64 bit among other things.
And there is a gotcha as well. If you have applied an ASU / ESU while being in 32bit environment to say DV. it will be tricky to apply the same ESU to PY once you have upgraded PY to 64bit because the ESU was originally installed to 32bit foundation. So you will have to remove / uninstall the ESU and then reinstall this.
 

TFZ

Well Known Member
Glen - I think you can get around that if you resync the registry (and you may need to do the Update section there as well to match whichever Update you install). Last time I did this, I had to manually update the registry manually for UN6 64 bit because it wasn't there at all even though it was applied in 64 bit - which is why I'm guessing that may be what you faced.
 

bluelake

Active Member
New issue is found. We installed Server Manager 9.2.6 on Linux and SM agent on Deployment server. But when we launch Server Manger console, deployment server is not found in SM console. The SM agent log shows failed to connect server manager using JMX. Is there any step we missed? We didn't have issue in the last tool release upgrade where we installed Server Manager on Windows 2012. Thx.
 

glen7x

Well Known Member
are you using TLS ? Else configure the java.security file, jdk.tls.disabledAlgorithms parameter. you may have to remove the values here.
 

TFZ

Well Known Member
There's a fairly extensive support doc on Oracle about the issue -
E1: SVM: Server Manager Console and Agent Issues With Oracle Java 1.8 Update 171 or Higher and IBM Java 8.0.4.1 or Higher (Doc ID 2621953.1)
 

bluelake

Active Member
are you using TLS ? Else configure the java.security file, jdk.tls.disabledAlgorithms parameter. you may have to remove the values here.
Sorry, the change you motioned works now. In the first change, we changed wrong java.security file in the wrong location.
 

bluelake

Active Member
Another issue: after deployment server is registered, the server status shows stopped. It cannot be started successfully. An error is found in log. Any suggestion?

SEVERE: Error in getting j2eeServer Name for DEP_SERVER '( Cannot find attribute j2eeServer)
 

tblancett

Member
No JDE B9 Client Network is created at this point. We are on 9.2.4.3 currently.
The deployment server "service" was introduced in tools 9.2.5 (for the web package builds). Your tools release does not currently support it, so you can ignore it. It will not impact any activities on the deployment server.
 

bluelake

Active Member
The deployment server "service" was introduced in tools 9.2.5 (for the web package builds). Your tools release does not currently support it, so you can ignore it. It will not impact any activities on the deployment server.
Sounds good. Our next step is to Change deployment server component to 9.2.6.1 in Server Manager. Will it work? We can try it.
 

bluelake

Active Member
The deployment server "service" was introduced in tools 9.2.5 (for the web package builds). Your tools release does not currently support it, so you can ignore it. It will not impact any activities on the deployment server.
You are right. It can be ignored. We upgrade deployment server to 9.2.6 from 9.2.4.3 successfully. After the upgrade, a new Windows service - JDE B9 Network Client is created. The deployment server status shows Running in Server Manager Console as long as JDE B9 service is running. Everything looks good.
 

bluelake

Active Member
New issue: After Planner ESU 64-bit is installed successfully, we received error msg window when run app - Electronic Software Updates (P96470):
an error has occured while preparing software for deployment. Please review the log files and correct any errors before proceeding

We also find in jde log:
JdeJvm::CheckForExceptions() - Stack Trace for Exception : java.lang.Exception: A JDBException occured.
at oracle.e1.database.copytablexml.StandAloneCopyTableXML.initColumnInfo(Unknown Source)
at oracle.e1.database.copytablexml.StandAloneCopyTableXML.<init>(Unknown Source)
Caused by: com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource System Local.


Anyone has any idea about this problem? Thanks.
 

tblancett

Member
New issue: After Planner ESU 64-bit is installed successfully, we received error msg window when run app - Electronic Software Updates (P96470):
an error has occured while preparing software for deployment. Please review the log files and correct any errors before proceeding

We also find in jde log:
JdeJvm::CheckForExceptions() - Stack Trace for Exception : java.lang.Exception: A JDBException occured.
at oracle.e1.database.copytablexml.StandAloneCopyTableXML.initColumnInfo(Unknown Source)
at oracle.e1.database.copytablexml.StandAloneCopyTableXML.<init>(Unknown Source)
Caused by: com.jdedwards.database.base.JDBException: [DATABASE_CONNECT_FAILED] Database Connection failed for DataSource System Local.


Anyone has any idea about this problem? Thanks.
If this is occurring on the deploying server, it could be referring to the Oracle local db (E1Local). Are the paths pointing to the 32 bit client for the Oracle DB? You can test to see if they are by simply opening up a command prompt window and typing "tnsping" without any arguments--it should show in the output whether it is the 64 or 32 bit version of the utility. If it's pointing to the 32 bit version of the DB client, you need to make sure the path references the 64 bit version (which is usually the /bin directory of the E1Local installation).
 

bluelake

Active Member
If this is occurring on the deploying server, it could be referring to the Oracle local db (E1Local). Are the paths pointing to the 32 bit client for the Oracle DB? You can test to see if they are by simply opening up a command prompt window and typing "tnsping" without any arguments--it should show in the output whether it is the 64 or 32 bit version of the utility. If it's pointing to the 32 bit version of the DB client, you need to make sure the path references the 64 bit version (which is usually the /bin directory of the E1Local installation).
This is confirmed that JDE points to Oracle 64-bit client (19c). We run TNSPING. It shows correct path. We can login JDE/Planner and run other app successfully. Only this ESU app does not work.
 

bluelake

Active Member
Most likely a mismatch between the jdk and the oracle jdbc driver you have in the MISC folder.
Oracle 19c JDBC driver (ojdbc8.jar, ucp.jar, ons.jar) are copied to MISC folder manually. It does not resolve the problem. We didn't have this problem in the last Planner ESU installation when upgrade TR from 9.2.1 to 9.2.4.
 
Top