Re: Different connect strings needed for RMAN and sqlplus?

Andy Kent wrote:
> Sorry, it does in fact execute 'sqlplus "sys/password_at_targbox as
> sysdba" '. What I can't understand is why that should cause the
> shutdown / startup not to complete cleanly, as though an incorrect
> environment is getting picked up, whereas doing it with both 'sqlplus /
> as sysdba' and through rman with the full connect string works fine.

Why don't you dot in the correct set of environment variables before attempting your connection.

Something like ...

#!/bin/ksh
. /whatever_place/directory/correct_env_vars.sh sqlplus /nolog << EOF
connect info ...

If you export the ORACLE_SID in the correct_env_vars.sh script that you want and are running in the dba group you can avoid containing a password.

>
> The root of the problem probably lies in having old, untidy DBA scripts
> on a box with multiple databases and Oracle versions installed. I am as
> surprised that the rman method *does* work than that the first sqlplus
> one *doesn't*! What I am trying to understand better is what kind of
> inherent differences there are in the three methods being tried as to
> how the connection gets established. I hope that makes some sense!
>

That's a strong argument for dotting in and supplying exactly the environment that you need to run. Often an approach is used that dot's in a file that is actually a symbolic link. Then you can change the contents of that "dotted in" file instead of making script changes. Received on Tue Dec 05 2006 - 08:34:06 CST