Re: Database mismatch

Randy, the NT service for the shutdown databases is set to Manual and they are not started. Theoretically, they are down.

If I look at InitB.Ora, I see that the database name is "B" and I see the path for the control files, etc. It's the database B.

If I look at InitD.Ora, I see that the database name is "D" and I see the path for the control files, etc. It's the database D.

Using SvrMgrL I logon using: CONNECT internal/password_at_D If I then look at v$parameter the database name is "B". Looking at the control files, etc. I see the settings for database "B".

And then I scream.

I suspect that one of the configurations is out of whack though I have no idea how it could have happened. You may be right and it could be TNSNAMES.ORA. Is there a particular sequence that has to be maintained between two configuration files?

What is it that actually ties the components like Instance, Listener, Database together?

Thanks.

BJackson_at_BOSGmbH.Com (Basil Jackson) wrote in message news:<adec38b6.0108290821.234116cf_at_posting.google.com>...
> I have a problem. I have a computer (NT4) with 4 databases and one
> instance each. Two databases are only for test purposes (let's say
> database A and B). These two test databases are deactivated (Service
> set to Manual).
>
> Two of the databases are for production purposes (let's say database C
> and D).
>
> The problem is that when I try to access database D, I'm actually
> seeing B which isn't even supposed to be running.
>
> Does anyone have a clue as to how the databases may have gotten
> crossed and what I might do to get them straight again? I'd really
> appreciate it.
Received on Fri Aug 31 2001 - 04:51:11 CDT