Re: QUESTION: Latest CPU thinks I have a db running

>So, it's not merely a check against the init.ora, it's a match for the
>processes running against the init.ora that belongs to it!

The way my server is set up, the init. file sits in an 'admin' directory specific to the db; instead of having the file in the /dbs directory, what is actually there is a symlink to the real file.

I have multiple homes, therefore multiple dbs directories, and therefore multiple symlinks pointing to one db's init file. I also do have oracle processes running, but not under _this_ home.

I talked to Oracle, and their guess is that there's some kind of file handle open against the init file, and that's what the code looks for. So the fact that we use symlinks was effectively a 'false positive'. I renamed my symlinks in the dbs directory of the home I was patching, and the patch went in clean.

Turns out that was the tech's first guess before he called me - that I was using symlinks; and he was about to recommend just what I ended up doing.

I think next time I'll just trust my process, and if I am sure the home I'm patching is not active, I'll ignore those errors. ;) Received on Wed Mar 15 2006 - 12:25:43 CST