Re: rman connection authorization

EdStevens wrote:

> For the record, Oracle support finally came up with a solution, but it
> raises still more questions. The box had two Oracle homes on it, one
> for a single 10g datbase and one for the 10g oem agent. In the PATH
> environment variable, the agent home preceeded the db home. Flipping
> that -- putting the db home first -- solved the problem and allowed
> 'c:\rman / target' to connect as it is supposed to. Of course, that
> raises the question of why path ordering should matter in this
> particular issue ....

Ed this is a pretty basic thing here. You need to understand when installing oracle software how many products have already been installed, in what order, and why they were installed ... and then make some decisions about if they are all needed anymore, how the combination of products will affect various areas, etc.

Then depending if you are unix or windows based ( or other platforms ) one has to wrestle with configuration PATH's, setting environment variables, etc.

If you are still puzzled after working with oracle support then you can continue experimenting with a test environment or re-open the support item. Received on Wed Jul 05 2006 - 12:24:16 CDT