Oracle connect failed 3.4 M011

[jruffsr]

I am trying to set up a new unix box with Intralink 3.4 so we can jump
to Wildfire 2.0. I have imported the dmp from our current 3.2
installation. I have run the required patches. Now when I attemp to
login i get the following error.



Oracle connect failed while loading Pro/INTRALINK schema.

The client has failed to connect to the Data Server.

1)Check that the Data Server/Host is running.

If this does not correct the issue, please consult the knowledge base

in the Customer Service Section of www.ptc.com and/or contact Technical

Support.



I have confirmed that the data server is running by trying to start the lisener using

lsnrctl start LISTENER

which tells me the listener is already running.



Any help would be appreciated.

Thanks

Jeff

MCAD Support

Tycoelectronics Power Systems

 

[mmead0ws]

Jeff,


Here are some ideas.


Optionallyyou can validate that the listener is running by checking your services. There are actually two services for Oracle. Try connecting to Oracle using SQLPlus. If you can't, its time to contact PTC technical support.


Does the new server have the same name as the original? How about the File Server? Are the file vaults in the same location as before? If any of these answers are "no", did you redirect them in the database using SQLPlus?


Also, is the new database the same size as the original database (i.e. Small, Medium, or Large)? If it was ever expanded beyond large, you have to resize the new database before migrating the data.Otherwise, unless you turned on autoextend inside Oracle, your migrationwon't complete successfully. I'm guessing you are fine here because you were able to apply the patches.


Finally, did you redirect your client to the new server or is it still pointing to the old server? I know this sounds like a dumb question, but I've done it before.


Please let us know if these ideas don't work.

 

[Bill Thomson]

A few questions.


1 When you do a 'ps -ef|grep oracle' what processes are running and can you


enter sqlplus and execute and sql scripts.


2 Have the semsys and shmsys options been added to the /etc/system


3 What version of Solaris are you running, if 9, have patches 113886, 113887, 113096 and 112785 been installed


4 Was ~oracle/product/9204/network/admin/sqlnet.ora rename to sqlnet.ora_oracle

 

[Guest]

<DIV>We had this problem as well.The startup & shutdown scripts are not starting the listerner properly. Here's the fix:</DIV>
<DIV>Edit the last statement in both of these files: dbstart_ilink & dbshut_ilink which are in <dataserver-install-point>/intralink/bin, and append this argument: </DIV>
<DIV>

 

[jruffsr]

Thanks for the responses. I will check each suggestion. One thing that
we have found is that I can run the client that I installed on the data
server [same machine as the file server]. I cannot run the client from
a windows machine. It appears that there is a conflict with a program
called Matrix that uses Oracle client. I plan on testing this when
I get back to work. I would appreciate if anyone else has
experienced this oracle conflict on a client to please let me know what
was done to resolve the issue.



Thanks to all.

Jeff Ruff

 

[rafalall]

Hello


I had similar problem with ProI 3.4 M011. During installation there was no possiblity to perform setup of database after installation of Data Server. PTC web page informs that release M011 works only with Oracle 9.2.0.5 (the latest version of Oracle). In the same time we received from PTC CDs with ProI, Oracle and Installation assistant and I could not run the installation since Installation Assistant did not find Java software installed.


In my opininion it is quite strange.


Best wishes


Rafal
Edited by: rafalall

 

[jruffsr]

To fix the problem, I uninstalled Intralink and oracle. A previous
reinstall of just intralink made matter worse. I then was able to login
as INTRALINK. Then once I sucessfuly migrated data from 3.2 to 3.4 I
had no issues.

Thanks to all for the suggestions and help.

Jeff Ruff