Re: CPU April 2005 patching madness
- From: Wolfgang Breitling <breitliw@xxxxxxxxxxxxx>
- To: jkstill@xxxxxxxxx
- Date: Mon, 23 May 2005 13:32:51 -0600
Jared,
do you set the correct path before starting, or rather trying to, the dev
and qa instances. I am not operating any production databases on Windows,
but I know that Windows can get easily confused with multiple Oracle
homes/bin directories in the path. What I always do is remove any oracle
directories from the path - and with 10g also clear the perl environment
variable - and then I have an oraenv.cmd that prepends the the OH/bin and
java directories before starting an instance - just like oraenv on unix.
What happens when you try that. Not necessarily the whole setup, just
removing all oracle references from the path in a command shell and then
only prepend the OH/bin for the database you want to start.
>All environment variables are correct.
>ORACLE_HOME=D:\oracle\ora92\dev
>ORACLE_SID=DEV
>PATH contains Oracle paths from only one ORACLE_HOME, DEV.
I overlooked that until I removed stuff to avoid overquoting. But I am not
sure how to take this. Does that mean that "PATH contains Oracle paths from
only one ORACLE_HOME, DEV" only when you try to start dev, or does PATH
contains Oracle paths from only one ORACLE_HOME, DEV all the time,
particularly when you ran OPatch to patch prod?
Regards
Wolfgang Breitling
Centrex Consulting Corporation
www.centrexcc.com
--
http://www.freelists.org/webpage/oracle-l
- References:
- CPU April 2005 patching madness
- From: Jared Still
Other related posts:
- » CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » RE: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- » Re: CPU April 2005 patching madness
- CPU April 2005 patching madness
- From: Jared Still