Re: Confused path

Howard,

Thank you for your response. We have a small (<1GB) Oracle 8.0.5 on a Win NT server. What happened was after the Oracle server was moved from H drive to D drive on a company server on Win NT, I tried to change parameter file to direct it to look for controlfile at D drive (from NT server side) or I drive from client side on XP, and it didn't recognize any of them. Then I did

  1.. Copy INITORCL.ORA file from server to client machine
  2.. SVRMGR30
  3.. Connect sys/password_at_mydata as sysdba
  4.. startup pfile=C:\orant\database\init.ora
  5.. rename master files:

alter database rename file 'H:\orant\database\sys1orcl.ora' to 'D:\orant\database\sys1orcl.ora'

alter database rename file 'H:\orant\database\usr1orcl.ora' to 'D:\orant\database\usr1orcl.ora'

alter database rename file 'H:\orant\database\rbs1orcl.ora' to 'D:\orant\database\rbs1orcl.ora'

alter database rename file 'H:\orant\database\tmp1orcl.ora' to 'D:\orant\database\tmp1orcl.ora'

alter database rename file 'H:\orant\database\log2orcl.ora' to 'D:\orant\database\log2orcl.ora'

alter database rename file 'H:\orant\database\log4orcl.ora' to 'D:\orant\database\log4orcl.ora'

alter database rename file 'H:\orant\database\log3orcl.ora' to 'D:\orant\database\log3orcl.ora'

alter database rename file 'H:\orant\database\log1orcl.ora' to 'D:\orant\database\log1orcl.ora'

The system was up and running. Several days after, I shutdown the database with abort option

(Don't laugh at me, I did this hundred times because the supported Integraph GIS system lost connection).

Then when I try to start with startup command I got ORA-01102 - Cannot mount in EXCLUSIVE MODE. We tried to bring up the database from either server side or client side, none of the effort worked. I searched some Oracle related sites and found some suggestions:

1. Mount the database in parallel mode.
2. Shutdown all other instances before mounting the database in exclusive mode.
3. Cause: Some other instance has the database mounted exclusive or shared. Action: Shutdown other instance or mount in a compatible mode.

However, I don't really understand what they mean. Finally we (I and system admin) stopped OracleService on the NT server, reboot the computer, then start the system, the database got connected fine. Actually, the system admin said he tried the samething a day before and it didn't work. The database is running OK now, but I still don't understand what caused the problem and how to prevent the problem.

Thanks again!

Al

"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:41d368d0$0$23531$afc38c87_at_news.optusnet.com.au...
> Al wrote:
> > I'm new to Oracle and just start learning, slowly. We recently moved our
> > Oracle 8 server which was on H drive of a NT server. I mapped in as H
drive
> > as control file location. After the the Oracle was moved to D drive of
the
> > NT server, I had trouble to access it from a client machine. Because the
> > client machine already has a D drive, I cannot map the Oracle server as
D
> > drive on my client machine. I end up with had to start Oracle from
server
> > machine and I looked at Alert file, the location of controlfile is on a
'D'
> > drive. Or I can copy the control file to my client machine and direct
Oracle
> > to find it from my local drive. What is the best way to resolve this
drive
> > label confusion?
>
>
> I'm a bit confused about your situation. Let's see if I understand at
> least part of it correctly.
>
> You had Oracle installed on Server1, and its database was on an H:
> drive. You've now copied the database over to Server2, and its database
> files were put onto a D: drive.
>
> That much I think is clear, though I'm not entirely convinced that H:
> and D: are actually the drive letters that the servers concerned knew
> the hard disks as. Which brings me on to my other problem. What I'm not
> clear on is why you were mapping drives on your client PC in order to
> access the database. Normally, one uses a program such as SQL Plus to
> connect to the database over the network, via a Listener process, and
> there is never a need to actually make physical mappings to the server
> drives which are storing the database. Can you explain what you were
> doing and why?
>
> I also can't work out whether the database is actually running
> succesfully on the new server or not. That your alert log mentions a D:
> drive for the location of the control files is good, because it
> presumably means someone correctly remembered to alter the initSID.ora
> to point to the new drive letter. Did they/you also do lots of "alter
> database rename file 'H:\something' to 'D:\something'" commands, too? In
> fact, do you actually have a problem with *the database* at all (as
> opposed to you and your client PC)?
>
> Have you read the concepts manual at http://tahiti.oracle.com ? I think
> you might need to. Otherwise, write back with a clearer description of
> what is going on. And don't forget to let us know whether you are
> running the Enterprise, Standard or Personal edition of Oracle or
> something else entirely.
>
>
> > One more question - for Oracle 8, if I use EXP80 utility to export a
> > database without specifying the distination, what is the default
directiory
> > (Win NT) is the dmp file going to be stored?
>
> Wherever you are when you invoke the export program.
>
> Regards
> HJR
>
Received on Thu Dec 30 2004 - 09:15:55 CST