Re: ORA-25150: ALTERING of extent parameters not permitted

IIRC (If I Recall Correctly) this was Winblows. Hence NO oerr

OP is Original Poster.

Regards

--
Sybrand Bakker
Senior Oracle DBA

to reply remove '-verwijderdit' from my e-mail address

"Alun Liggins" <liggs_at_hotmail.com> wrote in message
news:acqv9g$pa$1_at_paris.btinternet.com...


> Okay, but perhaps you could teach them how to look up errors quickly with

a


> "oerr ora 25150" etc.

>

> I should ask what does the "OP" stands for?

>

> Alun

>

> "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message

> news:uf1m2lq71n18d5_at_corp.supernews.com...

> > The OP failed to look up the error message in his error manual and/or

the


> > documentation site.

> > This group requires when you want assistance you do the preliminary

steps


> > yourself, and you don't leave to the group to be done what you could

have


> > easily done yourself.

> > Looking up an error message is a perfect example.

> > Usenet is a volunteer business. If you don't want to make any effort you

> > should better address your request with Oracle Technical Support, as

they


> > are getting paid for it.

> >

> >

> > Regards

> >

> >

> > --

> > Sybrand Bakker

> > Senior Oracle DBA

> >

> > to reply remove '-verwijderdit' from my e-mail address

> >

> > "Alun Liggins" <a.liggins_at_btinternet.com> wrote in message

> > news:acqeo2$c66$1_at_helle.btinternet.com...

> > > A little harsh Sybrand!

> > >

> > > What Oracle is saying is that the object when into a 'managed'

> tablespace,

> > > so you dont need to worry

> > > (so much...) about initial and next extents as Oracle will look after

> > that.

> > >

> > > Check out what the current tablespace extent allocation sizes are :-

> > >

> > > select * from dba_tablespaces should reveal what the default extent

> sizes

> > > are.

> > >

> > > Alun

> > >

> > > "Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message

> > > news:uev1k0eqqh2904_at_corp.supernews.com...

> > > >

> > > > "Brandon" <brandon_oh_at_yahoo.com> wrote in message

> > > > news:a03c2125.0205242154.231b2e2a_at_posting.google.com...

> > > > > Hi,

> > > > >

> > > > > I had just migrated my production database from Oracle 7.3.3 to

> Oracle

> > > > > 8.1.7

> > > > > by using exporting and importing by user.

> > > > >

> > > > > I noticed after the import, the storage parameter (NEXT_EXTENT) of

> the

> > > > > tables being imported was zero. But when i tried to alter this

> > > > > parameter by using the following sql command "alter table

user.table


> > > > > storage (NEXT 20K);", it gives

> > > > > me an error message an error message of "ORA-25150: ALTERING of

> extent

> > > > > parameters not permitted".

> > > > >

> > > > > Have anyone encounter this problem before ??

> > > > > And how do you solve it ? Thanks for helping : )

> > > > >

> > > > > rgds,

> > > > > Brandon

> > > >

> > > >

> > > > A simple search on the error message in the docs resulted in

> > > >

> > > >

> > > >

> > > > ORA-25150 ALTERING of extent parameters not permitted

> > > >

> > > > Cause: An attempt was made to alter the extent parameters for a

> segment

> > in

> > > a

> > > > tablespace with autoallocate or uniform extent allocation policy.

> > > >

> > > > Action: Remove the appropriate extent parameters from the command.

> > > >

> > > >

> > > > Next time, please try to research the error manual before posting

> > > >

> > > > Regards

> > > >

> > > >

> > > > --

> > > > Sybrand Bakker

> > > > Senior Oracle DBA

> > > >

> > > > to reply remove '-verwijderdit' from my e-mail address

> > > >

> > > >

> > > >

> > >

> > >

> >

> >

>

>