Upgrade of Enterprise server

[Hrbek]

Hi,

we tried to upgrade your enterprise servers from Windows NT 4.0 to Windows 2000 and Oracle 8.0.5 to Oracle 8.1.7. We copied your environment to another servers a we made it working. Then we installed Oracle 8.1.7 and with it's migration utilities we migrated database. Everything was working. After that we upgraded servers to Windows 2000 (fresh install with old data). When we tried to start JDE services in jde.log appeared:

832/372 Thu Jul 01 13:39:20 2004 IPCPUB1921
process 832 <jdenet_k> registered in entry 1

832/372 Thu Jul 01 13:39:21 2004 sc_dsptc140
INITIALIZING SCHEDULER SERVER KERNEL

832/372 Thu Jul 01 13:39:21 2004 sc_dsptc163
Attempting to auto-start the Scheduler.

832/372 Thu Jul 01 13:39:21 2004 DBINITCN237
OCI0000064 - Unable to create database server connection

832/372 Thu Jul 01 13:39:21 2004 JDB_DRVM627
JDB9900164 - Failed to connect to jdeprod

832/372 Thu Jul 01 13:39:21 2004 JTP_CM282
JDB9909003 - Could not init connect.

832/372 Thu Jul 01 13:39:21 2004 JTP_TM950
JDB9909100 - Get connect info failed: Transaction ID =

832/372 Thu Jul 01 13:39:21 2004 JDB_RQ11777
JDB3100013 - Failed to get connectinfo

832/372 Thu Jul 01 13:39:21 2004 JDB_OMP1301
JDB9900240 - Failed to open F986101

832/372 Thu Jul 01 13:39:21 2004 JDB_CACH1123
JDB9900009 - Failed to load ObjectMap Cache

832/372 Thu Jul 01 13:39:21 2004 JDB_CTL2515
JDB1100016 - Failed to load Environment - PRD733

832/372 Thu Jul 01 13:39:21 2004 JDEKDISP1169
Initializing of static env. failed

832/372 Thu Jul 01 13:39:21 2004 sc_dsptc776
Unable to get an environment handle. Could not validate the Scheduler Name.

832/372 Thu Jul 01 13:39:21 2004 sc_dsptc195
This server will not start the Scheduler.

and in jdedebug.log

Jul 01 13:39:20 ** 832/372 **** jdeDebugInit -- output to file.
Jul 01 13:39:20 ** 832/372 process 832 <jdenet_k> registered in entry 1
Jul 01 13:39:21 ** 832/372 KERNEL type = KERNEL_NET
Jul 01 13:39:21 ** 832/372 INITIALIZING SCHEDULER SERVER KERNEL
Jul 01 13:39:21 ** 832/372 Attempting to auto-start the Scheduler.
Jul 01 13:39:21 ** 832/372 About to validate the Scheduler Server name with the control record.
Jul 01 13:39:21 ** 832/372 ONEWORLD Session started in ENV PRD733 for JDE
Jul 01 13:39:21 ** 832/372 Entering JDB_InitEnv
Jul 01 13:39:21 ** 832/372 Entering JDB_SetEnv
Jul 01 13:39:21 ** 832/372 Entering JDB_InitUser with commit mode 0.
Jul 01 13:39:21 ** 832/372 Entering JDB_BeginTransaction
Jul 01 13:39:21 ** 832/372 Entering JDB_InitUser with commit mode 0.
Jul 01 13:39:21 ** 832/372 Entering JDB_BeginTransaction
Jul 01 13:39:21 ** 832/372 Entering JDB_FreeUser
Jul 01 13:39:21 ** 832/372 Entering JDB_InitUser with commit mode 0.
Jul 01 13:39:21 ** 832/372 Entering JDB_BeginTransaction
Jul 01 13:39:21 ** 832/372 Entering JDB_OpenTable( Table = F986101)
Jul 01 13:39:21 ** 832/372 ORACLE DBInitDrv envr=016846B8
Jul 01 13:39:21 ** 832/372 ORACLE DBInitCon envr=016846B8 conn=017306A0 OWPROD2 A (JDE@jdeprod) V80 (srvrusers=0) 1
Jul 01 13:39:21 ** 832/372 Entering LoadUserProfileCache
Jul 01 13:39:21 ** 832/372 Leaving LoadUserProfileCache
Jul 01 13:39:21 ** 832/372 Entering JDB_FreeUser
Jul 01 13:39:21 ** 832/372 Entering JDB_FreeEnv
Jul 01 13:39:21 ** 832/372 ONEWORLD Session terminated in ENV PRD733 for JDE
Jul 01 13:39:21 ** 832/372 Entering JDB_FreeUser
Jul 01 13:39:21 ** 832/372 Entering jdeCacheDestryAllUserCaches
Jul 01 13:39:21 ** 832/372 ORACLE DBFreeDrv envr=016846B8
Jul 01 13:39:21 ** 832/372 Unable to get an environment handle. Could not validate the Scheduler Name.
Jul 01 13:39:21 ** 832/372 This server will not start the Scheduler.

Connection from FAT client or deployment server works well. Only difference is in row in jdedebug.log with connection where is V80 on enterprise servers and V81 on clients. All data sources is configured to use JDBOCI81.DLL.

Any suggestions? Thank's

Ludek Hrbek

OneWorld B7331, SP11.1
Windows NT 4.0, Oracle 8.0.5

 

[Soul Glo]

do you have you tnsnames.ora and you sqlnet.ora files on your server.

 

[Hrbek]

Of course I have. Oracle works and I can connect as a JDE users using SQLPLUS from enterprise server. And I can connect from deployment server or client station (without using security server).

Ludek Hrbek

OneWorld B7331, SP11.1
Windows NT 4.0, Oracle 8.0.5

 

[jean_driscoll]

Did you keep the same name for the new server? If not, did you use the Machine application to add the new name of the server and define environments for it?

 

[Hrbek]

Names are the same. I solved the problem with instaling Oracle 8.0.5 client on both enterprise servers, change default oracle home to 8.0.5, change oci library to JDBOCI80.DLL in JDE.INI and datasources. I think there is some problem with cooperation with 8.1.7 client and OCI library. Thank's for tips.

Ludek Hrbek

OneWorld B7331, SP11.1
Windows NT 4.0, Oracle 8.0.5