Clients Cannot Connect To Enterprise Server

Aiming4theFoot

Active Member
We recently upgraded our database from Oracle 8.1.7 to Oracle 9.2.0.5.0. Our database server box changed in the process. Now our Oracle clients have no trouble connecting, but our One World clients cannot connect to the Enterprise server. We get the message: "Could not load environment - PY7334." In the client JDE log, it says: "Unable to execute - SELECT OMENHV, OMAPPLID, OMOBNM, OMDATP, OMDATS, OMUGRP, OMOAPP, OMDATM, OMOVRE, OMSY, OMSTSO, OMFUNO, OMOCM2 FROM SYS7334.F986101 WHERE ( OMENHV = :KEY1 AND OMSTSO = :KEY2 AND OMFUNO = :KEY3 AND OMOBNM = :KEY4 AND OMUGRP = :KEY5 ) ORDER BY OMSTSO ASC,OMAPPLID ASC" "OCI0000179 - Error - ORA-00942: table or view does not exist" We made all the appropriate changes in the jde.ini. What else do we need to do? Is there anywhere else we need to point One World to Oracle?
 

Attachments

  • 83283-Log.zip
    2.6 KB · Views: 110
Check your TNSNAMES.ORA files to make sure that they are pointing to the correct servers and DB names.
 
Did you change your database name when you upgraded? Make sure you go through the datasources and change the connect string to reflect new database name. Since you can connect to oracle via client, sign into the SY9 schema, and do a desc F986101; it should tell you if that table exist in that schema or not. If it doesn't, then you will need to restore the table from your dmp file or backup.
Hope that helps.
Regards,
Nyasha
 
No the db name was not changed in the upgrade. Yes, F986101 table exists.
 
You mentioned your database server changed in the process. did the servername change? Can you at least log onto your deployment server?

log onto the deployment server, in the gh9011 menu, select database datsources. check your system datasource and make sure that the server name and connect string name is correct. check your OCM mapping for F986101 as well.
 
Yes, the server name changed. Yes we can login through the deployment server. All the datasources are there. Where do I check the OCM mappings? Our CNC person isnt here right now.
 
Are the clients that can't connect FAT clients or Citrix clients? Either way, are the TNSNAMES.ORA files on those servers/machines correct?
 
when you go into the datasource application, you select the system datasource, do a find. Scroll down to the systen datasource and verify that the servername column has the name of your new server. If it is not, doubleclick on it and edit databse servername to reflect the proper servername.

to get to OCM, use the Fastpath on the main menu , type ocm hit enter. select the system datasource. In the object name column type F986101 do a find. This should point to the system - whateveryour release. i.e system - B9
 
Set the servername to your enterprise server name instead of db server name and you'll never have to worry about that as being a potential issue again. Yes, this does work. We are doing this now.
 
Jason,

Since your database has changed from Oracle 8 to 9, I think you would have to change your DLL name in the Database Source.

Currently, your DLL name would be JDBOCI80.DLL. You should change it to ORAOCI90.DLL.

Hope this helps.

Thanks
Yogesh
 
Additionally, in the JDE.INI on client and server, there is a section called [DB SYSTEM SETTINGS]. change the value for
Load Library=JDBOCI80.DLL to JDBOCI90.DLL.

Thanks
Yogesh
 
Those changes are not necessary for connectivity to the DB. However, it's still a good idea to do that at some point.
 
Yes, they are all FAT clients. Yes, the tnsnames.ora files are correct on both clients and servers; we have connected successfully to the new db through SQL*Plus.
 
Check if your workstations´ Windows environment variables are set correctly. There should a PATH pointing to your NEW Oracle client´s bin directory.

Gerd
 
Right now, our production db is up; its our test server (DV & PY) we are having problems w/. We had a consultant come into to do this for us since the CNC Admin and myself have been given no training and have never done anything like this before. After talking w/ Peoplesoft it looks like he (the consultant) added the server plan for the production servers in Production instead of the planning environment. Peoplesoft has been good about guiding us through setting this up, so hopefully we will have this resolved soon.

There are no entries in the OCM application or Database Datasources for either the production or test database servers.
 
Yes, we have changed the dll name in all the server and client jde.ini files as well as in F98611 in SYS7334 and the planning db.
 
Update: we can now connect to the test server! Some settings in our jde.ini file were off. However, we cannot run reports. The reports wait In Queue(S), but immediately error after that. Thumbing through the debug logs, it appears that One World is looking on the test enterprise server for the control tables, central objects, etc. instead of looking on the test database server like it should be. Anyone know where change the reference?
 
I would double check your datasources using P986115. Check system and server maps. Just a thought.

Patty
 
Back
Top