Is it possible that the effects of running the
sql.bsq (and any other scripts that kick in
automatically after a create database)
would have generated enough UNDO to
cause the undo tablespace to grow ?
--
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
The educated person is not the person
who can answer the questions, but the
person who can question the answers -- T. Schick Jr
One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
____Denmark__May 21-23rd
____Sweden___June
____Finland__September
____Norway___September
Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK_(Manchester)_May x 2
____Estonia___June (provisional)
____Australia_June (provisional)
____USA_(CA, TX)_August
The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html
"Peter" <peter_at_nomorenewsspammin.ca> wrote in message
news:c5s8bvc9b8madc2ai387qu46spupsr4h0e_at_4ax.com...
> I had the OMF turned on which was supposed to create an undo
> tablespace 10m in size.
>
> I ran the following statement I did not set the undo_managemnt
> paramater. But what I got is an undo tablespace of 67m.
>
> create database db
> default temporary tablespace temptbs
> undo tablespace undotbs;
>
>
> If I ran the following statement instead and with the undo_managemnt
> paramater set to auto, then I got an undo tablespace of 10m
>
> create database db
> default temporary tablespace temptbs;
>
> Also, If I ran the following statement and with the undo_managemnt
> paramater set to auto, then I got an undo tablespace of 10m
>
> create database db
> default temporary tablespace temptbs
> undo tablespace undotbs;
>
>
> My question is why did the first statement give me an undo
tablespace
> of 67m?
>
Received on Tue May 06 2003 - 04:14:50 CDT
