Re: Oracle Client Software Manager

From: <karniotiss_at_detroitedison.com>
Date: 1996/06/18
Message-ID: <4q6esg$8dk_at_news.deco.com>#1/1


  Larry:

     This is Steven Karniotis from Compuware. I had a similar situation at one of my client sites. They told us the same thing. Here is the problem with what they told you. When you install OCSM, it needs an ORAWIN directory on the server AND ON THE CLIENT. Thus, if you do not supply it another directory name, it will override anything you have in your local ORAWIN directory structure.

     We configured several PCs to have local ORAWIN directories and then used ORASHR as the Shared ORAWIN. We had two WIN.INI and ORACLE.INI files: one fore local and one for shared. Depending on which environment you needed, we copied, via a BAT file, the appropriate WIN.INI and ORACLE.INI files. This is the only way to accomplish this task as there will be conflict problems with the way you implemented it.

     Good Luck: Received on Tue Jun 18 1996 - 00:00:00 CEST

Original text of this message