| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: Cant Create Database
So, let me understand this correctly... you're saying that Oracle now provides support for configurations in which database file(s) are on file system(s) on remote machine(s), accessed via an NFS mount ?
<jsmelser_at_bigfoot.com> wrote in message news:Pine.LNX.4.10.10009052023490.10237-100000_at_server.smelser.org...
>
> Not so! :)
>
> I just spend 4 days. all I need is lockd running on both client and server
> and whala. Creation happened! :)
>
> Oh happy day.
> Thanks,
> Jeff
>
> On Mon, 4 Sep 2000, spencer wrote:
>
> > All of the files for the Oracle database need to be local to the
> > machine running the Oracle instance. Files on NFS mounts
> > are not supported.
> >
"Jeff Smelser" <tradergt_at_bigfoot.com> wrote in message news:39B2DF13.1E8DBD27_at_bigfoot.com...
> Sybrand Bakker wrote:
> >
> > IIRC startup nomount will start the processes. I'm cracking my brains on the
> > common causes there are for such an error. If there is no instance prior to
> > the command, you may want to verify the db_name parameter in
> > initorclrep.ora. When you use a database name in the create database command
> > that parameter should either be absent or set equal to the database name on
> > the command line. I never use a database name in the create database
> > command, because I always set db_name.
>
> Tried that, no go.
>
> I will include init with this, so you can see it. I will explain a
> little more about my setup, and I think it might be part of the
> problem..
>
> Right now, I have a machine running instance orcldb. Its been running
> 6months or more now. So, I decided I needed another instance so I could
> try replication, plus just see if I can do it! :)
>
> Here is what I did, its running of machine 1. I used linux nfs and
> mounted both oracle drives to machine 2. This way, I could save on
> diskspace. I did my oracle_home and whala. everything was exactly like
> machine 1, except for oracle_sid was orclrep.
>
> This is when I tried creating the database. I would think, this is done
> all the time and that it should work great. But its not. Or I am doing
> something minor wrong. I know its something small and stupid if its me..
> Or this doesn't work. I DID try installing oracle all over again on the
> new machine and got the same thing, so I just trashed it and went back.
> Seems like it wasn't the problem.
>
> BTW, I tried running orcldb on the new machine by changing listener.ora
> and tnsnames.ora and got, Can't mount database in exclusive mode. Can
> this be part of the same problem or something different?
>
> Yes the database was completely down when I tried to start it on machine
> two.
>
> Thanks,
> Jeff
>
> >
> > ----- Original Message -----
> > From: "Jeff Smelser" <tradergt_at_bigfoot.com>
> > To: "Sybrand Bakker" <postbus_at_sybrandb.demon.nl>
> > Sent: Saturday, September 02, 2000 6:17 PM
> > Subject: Re: Cant Create Database
> >
> > > On Sat, 2 Sep 2000, Sybrand Bakker wrote:
> > >
> > > Oracle Sid is set correctly.
> > >
> > > What database you want me to shutdown? When I do a ps -ef, there is
> > > nothing oracle before.
> > >
> > > I am curious, when a do a start nomount, and I can't remember if it starts
> > > a bunch of processes. I get the normal dbwtr and all those. Is that
> > > correct?
> > >
> > > Thanks,
> > > Jeff
> > >
> > >
> > > > Shutdown the database first and retry.
> > > > Another reason, IIRC, is the ORACLE_SID not being equal to the sid in
> > > > init<sid>.ora.
> > > >
> > > > Hth,
> > > >
> > > > Sybrand Bakker, Oracle DBA
> > > >
> > > > "Jeff Smelser" <tradergt_at_bigfoot.com> wrote in message
> > > > news:Pine.LNX.4.10.10009020921380.2326-100000_at_server.smelser.org...
> > > > > I get this when I try to create a database:
> > > > >
> > > > > Oracle Server Manager Release 3.1.6.0.0 - Production
> > > > >
> > > > > Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
> > > > >
> > > > > Oracle8i Enterprise Edition Release 8.1.6.1.0 - Production
> > > > > With the Partitioning option
> > > > > JServer Release 8.1.6.0.0 - Production
> > > > >
> > > > > SVRMGR> SVRMGR> Connected.
> > > > > SVRMGR> ORACLE instance started.
> > > > > Total System Global Area 116068336 bytes
> > > > > Fixed Size 69616 bytes
> > > > > Variable Size 99049472 bytes
> > > > > Database Buffers 16777216 bytes
> > > > > Redo Buffers 172032 bytes
> > > > > SVRMGR> 2> 3> 4> 5> 6> 7> 8>
9>> > > > > ORA-01501: CREATE DATABASE failed
> > > > > 10> CREATE DATABASE "orclrep"
> > > > > *
> #
> # Copyright (c) 1991, 1998 by Oracle Corporation
> #
> ##############################################################################
> # Example INIT.ORA file
> #
> # This file is provided by Oracle Corporation to help you customize
> # your RDBMS installation for your site. Important system parameters
> # are discussed, and example settings given.
> #
> # Some parameter settings are generic to any size installation.
> # For parameters that require different values in different size
> # installations, three scenarios have been provided: SMALL, MEDIUM
> # and LARGE. Any parameter that needs to be tuned according to
> # installation size will have three settings, each one commented
> # according to installation size.
> #
> # Use the following table to approximate the SGA size needed for the
> # three scenarious provided in this file:
> #
> # -------Installation/Database Size------
> # SMALL MEDIUM LARGE
> # Block 2K 4500K 6800K 17000K
> # Size 4K 5500K 8800K 21000K
> #
> # To set up a database that multiple instances will be using, place
> # all instance-specific parameters in one file, and then have all
> # of these files point to a master file using the IFILE command.
> # This way, when you change a public
> # parameter, it will automatically change on all instances. This is
> # necessary, since all instances must run with the same value for many
> # parameters. For example, if you choose to use private rollback' segments,
> # these must be specified in different files, but since all gc_*
> # parameters must be the same on all instances, they should be in one file.
> #
> # INSTRUCTIONS: Edit this file and the other INIT files it calls for
> # your site, either by using the values provided here or by providing
> # your own. Then place an IFILE= line into each instance-specific
> # INIT file that points at this file.
> #
> # NOTE: Parameter values suggested in this file are based on conservative
> # estimates for computer memory availability. You should adjust values upward
> # for modern machines.
> #
> ###############################################################################
>
> db_name = orclrep
> instance_name = orclrep
>
> service_names = orclrep
>
>
> control_files = ("/o01/app/oracle/oradata/orclrep/control01.ctl",
> "/o02/app/oracle/oradata/orclrep/control02.ctl",
> "/o03/app/oracle/oradata/orclrep/control03.ctl")
>
> open_cursors = 100
> max_enabled_roles = 30
> db_block_buffers = 4096
>
> shared_pool_size = 52428800
>
> large_pool_size = 23592960
> java_pool_size = 20971520
>
> log_checkpoint_interval = 10000
> log_checkpoint_timeout = 1800
>
> processes = 50
>
> log_buffer = 163840
>
> # audit_trail = false # if you want auditing
> # timed_statistics = false # if you want timed statistics
> # max_dump_file_size = 10000 # limit trace file size to 5M each
>
>
> ##### For archiving if enabled #####
> log_archive_start = true
> log_archive_dest_1 = "location=/o03/app/oracle/admin/orclrep/arch"
> log_archive_format = arch_%t_%s.arc
>
> # If using private rollback segments, place lines of the following
> # form in each of your instance-specific init.ora files:
> #rollback_segments = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6 )
>
> # Global Naming -- enforce that a dblink has same name as the db it connects to
> # global_names = false
>
> # Uncomment the following line if you wish to enable the Oracle Trace product
> # to trace server activity. This enables scheduling of server collections
> # from the Oracle Enterprise Manager Console.
> # Also, if the oracle_trace_collection_name parameter is non-null,
> # every session will write to the named collection, as well as enabling you
> # to schedule future collections from the console.
> # oracle_trace_enable = true
>
> # define directories to store trace and alert files
> background_dump_dest = /o03/app/oracle/admin/orclrep/bdump
> core_dump_dest = /o03/app/oracle/admin/orclrep/cdump
> #Uncomment this parameter to enable resource management for your database.
> #The SYSTEM_PLAN is provided by default with the database.
> #Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
> user_dump_dest = /o03/app/oracle/admin/orclrep/udump
>
> db_block_size = 4096
>
> remote_login_passwordfile = exclusive
>
> os_authent_prefix = ""
>
> # The following parameters are needed for the Advanced Replication Option
> job_queue_processes = 4
> job_queue_interval = 60
> distributed_transactions = 10
> open_links = 4
>
> mts_dispatchers = "(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)"
> # Uncomment the following line when your listener is configured for SSL
> # (listener.ora and sqlnet.ora)
> # mts_dispatchers = "(PROTOCOL=TCPS)(PRE=oracle.aurora.server.SGiopServer)"
>
> mts_dispatchers = "(protocol=TCP)"
>
> compatible = "8.1.0"
> sort_area_size = 65536
> sort_area_retained_size = 65536
>
Received on Fri Sep 08 2000 - 00:40:44 CDT
 |
 |