Path: text.usenetserver.com!out02a.usenetserver.com!news.usenetserver.com!in01.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!l42g2000hsc.googlegroups.com!not-for-mail From: joel garry Newsgroups: comp.databases.oracle.server Subject: Re: create database fatal error Date: Mon, 7 Jul 2008 11:10:48 -0700 (PDT) Organization: http://groups.google.com Lines: 47 Message-ID: <47a08bc7-b05e-47d3-a562-2fc83d0b1ed9@l42g2000hsc.googlegroups.com> References: NNTP-Posting-Host: 75.49.200.201 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1215454248 27067 127.0.0.1 (7 Jul 2008 18:10:48 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Mon, 7 Jul 2008 18:10:48 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: l42g2000hsc.googlegroups.com; posting-host=75.49.200.201; posting-account=tpQovAkAAABNoH5bwsZAiff2L0zxGwdv User-Agent: G2/1.0 X-HTTP-Via: 1.0 ISA2K4-OC1 X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1),gzip(gfe),gzip(gfe) Xref: usenetserver.com comp.databases.oracle.server:446318 X-Received-Date: Mon, 07 Jul 2008 14:10:49 EDT (text.usenetserver.com) On Jul 6, 11:30=A0am, Tommy Halsbrekk wrote: > Michael Austin wrote: > > > Were you able to get your problem solved? > > > Make sure your database directories are owned by oracle user. > > > Have a look athttp://www.fast-track.cc/10g_02.htm > > > - specifically these lines: > > DATAFILE '/usr/oracle/OraHome1/oradata/aultdb1/test/system01.dbf' SIZE > > 300M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED > > EXTENT MANAGEMENT LOCAL > > > AUTOEXTEND ON will automagically add space to the file as needed. > > Thanks that worked beautifully. I dont understand the line eniterly > though, because other examples I have seen dont have the autoextend > option, so I thought the extent management local was the clue. > > In any case thanks for all help > > regards > > tommy The problem arises when non-system things get put into the system tablespace. You can wind up extending the system tablespace until it is very large, in the disasterous case filling up the disk, crashing the database, and being unable to shrink the tablespace, etc. Whether that happens depends on the quality of the adminstrators and developers of the db. People who have no clue what they are doing are most likely to make such mistakes. Some things do change by version, and as everyone has advised you, you can use dbca to save a create database script that works. In any event, you should check if non-system objects are in the system tablespace. Doing a job about which you are unqualified and neither is management and then leaving for vacation - wouldn't give me the warm 'n fuzzies. I've cleaned up more than enough of those... jg -- @home.com is bogus. Weather underground is better. http://www.signonsandiego.com/uniontrib/200= 80707/news_1b7channel.html