Re: creating an instance with command line tools

Two minor comments:

1. Connect internal will be de-suppported in Oracle 9i. Please use "connect / as sysdba" instead.
2. Environment variables can be used as shorthand in sqlplus and svrmgrl. For example, you can specify UNIX: startup nomount pfile=${ORACLE_HOME}/init${ORACLE_SID}.ora_file NT: startup nomount pfile=%ORACLE_HOME%\init%ORACLE_SID%.ora_file

                                         Rick

"John Theunis" <john.theunis_at_advalvas.be> writes:

> hi Christoph,
>
> here's how I do it:
>
> First check your initSID.ora file. Set the stuff you want (or accept the
> defaults, to start with)
> Make sure that your control file locations point to existing directories and
> that you rollback segments are commented out.
> You can already set the database name here and the db_blocksize, then its
> there for future restarts.
> Also verify that you .profile containts the necessary variables like
> ORACLE_HOME, ORACLE_SID, ...
> Then startup svrmgrl. Use 'connect internal'. Then 'startup nomount'. If
> your initSID.ora is somewhere else than in $ORACLE_HOME/dbs/ then use
> 'startup nomount pfile=<full_path_to_initSID.ora_file>'. Nomount means that
> only the initSID.ora file is read. Control files are not processed yet.
> From there on, you can use the CREATE DATABASE command. Sample below.
> If this is successful, the instance should be mounted and opened.
> Finally, you should create the data dictionary by running de
> $ORACLE_HOME/rdbms/admin/catalog.sql script and then the supplied packages
> with $ORACLE_HOME/rdbms/admin/catproc.sql script.
> Et voila, you should have a running Oracle instance!
>
> here's a sample create database statement:
>
> create database <SID>
> controlfile reuse (existing controlfile of initSID is used)
> logfile group <int> ('<file opts>','<file opts>',...) size <size>M,
> group <int> ('<file opts>','<file opts>',...) size <size>M
> datafile '<file opts>' size <size>M autoextend on
> character set <charset> eg. WE8ISO8859P1
> maxlogfiles <maxredologfile groups>
> maxlogmembers <max redologmembers>
> maxdatafiles <integer>
> archivelog | noarchivelog
>
> EXAMPLE:
> create database ORA1
> controlfile reuse
> logfile group 1
> ('/dsk2/oradata/redolog1a.rdo','/dsk3/oradata/redolog1b.rdo') size 10M,
> group 2 ('/dsk2/oradata/redolog2a.rdo','/dsk3/oradata/redolog2b.rdo') size
> 10M,
> group 3 ('/dsk2/oradata/redolog3a.rdo','/dsk3/oradata/redolog3b.rdo') size
> 10M
> datafile '/dsk2/oradata/system01.dbf' size 1000M autoextend on
> character set WE8ISO8859P1
> maxlogfiles 3
> maxlogmembers 3
> archivelog
>
>
> kind regards
> john
>
>
> "Christoph Kukulies" <kuku_at_gil.physik.rwth-aachen.de> wrote in message
> news:9g2me4$3su$1_at_nets3.rz.RWTH-Aachen.DE...
> > Jan Dinger <gateway_at_oor2.de> wrote:
> > : Hallo Christoph!
 

> > : Antwort auf eine Message von Christoph Kukulies an All:
 

> > : CK> From: Christoph Kukulies <kuku_at_gil.physik.rwth-aachen.de>
 

> > : CK> I need to know a way to create a database using solely
> > : CK> batch tools, i.e. SRVMGR or something to create an Oracle
> > : CK> DB instance after the customer has installed the server from the
 CD.  

> > : Der einfachste Weg ist es, den dbassist zu starten, die Fragen zur
> Datenbank zu beantworten/bearbeiten und am Schluss die Datenbank nicht
> erstellen, sondern die Einstellung als Script abspeichern. Dieses Skript, 1
> Mastersript und vier andere Skripte erstellen die Datenbank ohne GUI.
> > : Das kannst du auch selbstverstaendlich auf einer anderen Datenbank mit
 einem gleichem Release machen.
> > : Damit ersparst du dir das manuelle Erstellen der DB , bzw. das das
 Suchen nach den richtigen Befehlen :-)
> >
> > Thanks for answering in german but I think this is an english list.
> >
> > I wouldn't mind receiving followups in direct mail in german.
> >
> > Anyway, you wrote that I should start dbassist and generate the script
 file(s).
> > I ran the script files and so many bad things happened like
> > running out of virtual memory and such. And a bunch of javavm stuff
> > was executed or entered in the database which I didn't want anyway.
> >
> > : Tschüß, Jan!
> >
> > --
> > Chris Christoph P. U. Kukulies kuku_at_gil.physik.rwth-aachen.de
>
>
 

-- 
                                Rick Wessman
                                Security Assessment Group
                                Oracle Corporation
                                Rick.Wessman_at_oracle.com

     The opinions expressed above are mine and do not necessarily reflect
                         those of Oracle Corporation.