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

bluelake

Active Member
We have ojdbc8.jar placed in MISC folder. Could you provide details what mismatch is?
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.
 

bluelake

Active Member
New issue: when we try to apply BSFN ESU for 64-bit using Change Assistant, the baseline ESU JN10023 failed to apply. Any idea? Some other ESU can be applied successfully in same way. Thanks.
 

johnd

Well Known Member
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.
 

bluelake

Active Member
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.
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.
 

bluelake

Active Member
New 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.
 

ice_cube210

VIP Member
New 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.
Check your database data source definitions in your planner environment. Perhaps a wrong definition somewhere
 
Top