Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!pd2nf1so.cg.shawcable.net!residential.shaw.ca!sjc70.webusenet.com!news.webusenet.com!cyclone.bc.net!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: hari_om@hotmail.com (Hari Om) Newsgroups: comp.databases.oracle.server Subject: Re: Creating DB Manually Date: 9 Sep 2003 13:20:25 -0700 Organization: http://groups.google.com/ Lines: 91 Message-ID: References: <3f5cee7c$0$28120$afc38c87@news.optusnet.com.au> NNTP-Posting-Host: 168.179.113.161 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1063138827 7951 127.0.0.1 (9 Sep 2003 20:20:27 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 9 Sep 2003 20:20:27 GMT Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:242724 Hi Howard, Thanks for your reply. I did some research on DBCA and creating DB Manually. I created the DB Manually using a "plain vanilla" script which ONLY mentions datafiles, loggroups and UNDO Tablespace. It then created "vanilla" DB for me. I then executed the scripts "CATALOG.SQL" and "CATPROC.SQL" to populate the data dictionary. Here is what I see: USING DBCA to Create Database: ------------------------------- SCHEMAS created are: CTXSYS, HR, MDSYS, ODM, ODM_MTR, OE, OLAPSYS, ORDPLUGINS, ORDSYS, OUTLN,PM,PUBLIC,QS,QS_ADM,QS_CBADM,QS_CS,QS_ES,QS_OS,SCOTT,SH,SYS, SYSTEM,WKSYS,XDB TABLESPACES Created are: CWMLITE,DRSYS,EXAMPLE,INDX,ODM,SYSTEM,TEMP,TOOLS,UNDOTBS1,USERS,XDB USERS CREATED ARE: DBCA CREATES AROUND 30 USERS. When I create DB Manually, here are my staticis: SCHEMAS Created are ONLY:OUTLN,PUBLIC,SYS,SYSTEM USERS Created are ONLY: DBSNMP,OUTLN,SYS,SYSTEM.PUBLIC TABLESPACES Created are ONLY: SYSTEM,UNDOTBS1 Also, using DBCA my SYSTEM TBLSPC holds around 400MB space and if I create DB Manually, it holds only 150MB If you compare the above staticis, you will notice a BIG Difference. So my question is if I create DB Manually, WILL I MISS ANYTHING....? Can I simply IGNORE the "extra" stuff which DBCA Created for me.... by creating DB Manually instead....? Any related informaiton on this is appreciated. "Howard J. Rogers" wrote in message news:<3f5cee7c$0$28120$afc38c87@news.optusnet.com.au>... > "Hari Om" wrote in message > news:d1d5ebe4.0309080810.5725427@posting.google.com... > > Creating DB Manually > > > > Hello, > > > > I wanted to create a Database Manually (without using DBCA) > > I already have a database running called "BILL" > > I want to creat a database manually called "GATES" > > > > Here is what I did: > > > > 1) Copied initBILL.ora file (/oracle/data1/admin/bill/pfile/) to > > initGATES.ora (/oracle/data1/admin/gates/pfile/) > > > > 2) Modified the following parametsrs in above file: > > DB_NAME = GATES > > background_dump_dest=/oracle/data1/admin/gates/bdump > > core_dump_dest=/oracle/data1/admin/gates/cdump > > user_dump_dest=/oracle/data1/admin/gates/udump > > control_files=("/oracle/data1/gates/control01.ctl", > > "/oracle/data1/gates/control02.ctl", > > "/oracle/data2/gates/control03.ctl") > > instance_name=gates > > This has nothing to do with your particular error, which arises simply > because you haven't logged on a privileged user, but you will run into some > other errors if you don't sort out a couple of other parameters. > > Specifically, your BILL database probably has rollback segments or an undo > tablespace. In which case, those things will be mentioned in the > initBILL.ora, and they won't be correct for the new database you're about to > create. You therefore need to comment out any parameter you see called > 'ROLLBACK_SEGMENTS=xxxx' or 'UNDO_TABLESPACE=xxxx'. > > (You will of course have to add in rollback segments to the new database > once it's been created, or an undo tablespace, and then you can uncomment > these lines). > > Also, watch out for REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE. If that's there, > you'll need a new password file created before you start. If you, the user > Hari, are a member of your Unix box's dba group, then you should change that > to read REMOTE_LOGIN_PASSWORDFILE=NONE. If you aren't a member of the dba > group, you will have to use the oradim executable to create a password file > from scratch, or copy the ''orapwBILL" file to something called > "orapwdGATES", and leave the parameter set to EXCLUSIVE. > > Regards > HJR