Re: rman connection authorization

EdStevens wrote:
> hpuxrac wrote:
> > 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.
>
> Their final explanation was the obvious, that rman "may" have been
> calling some dynamic libraries that, due to the PATH, were located in
> the agent's bin directory in stead of the database's. Well, yeah, but
> I'm surprised that it would have an impact on how connection
> authentication is handled.. that the agent install would have an
> 'authentication' library that behaves differently.

Ok fine either you are satisfied with the explanation or not. That's why you and I pay oracle for support.

If you are not satisfied then continue testing or have the support item re-opened. Received on Thu Jul 06 2006 - 08:31:03 CDT