Re: COMPATIBLE parameter not being read...why?

I agree with thomas. I commented out the compatible clause in my initsid.ora and I got the same result as you got "empty string for compatible" and when I put it back, it shows "7.3.3"

The simplest way to verify if you are modifing the right init file is to rename it and see if you can start db.

Good luck, kurt

In article <Mg4s3.606$P36.33695_at_dfiatx1-snr1.gtei.net>,   "Christopher Allen" <progplusSPAMBEGONE_at_gte.net> wrote:
> I changed the COMPATIBLE string in intiORCL.ora to 7.3.4.0.1 (the
version
> that shows when you log in with SQL*Plus), bounced the database, and
the
> COMPATIBLE parameter still isn't "taking".
>
> As noted in another message in this thread, when I go into SVRMGRL and
enter
> the command "show parameter compatible", the two entries that display
> ("compatible" and "compatible_no_recovery"), both have blank values.
>
> The check-constraint example I gave was accurate but silly. Far more
> importantly, I'm not able to do necessary work with the database. For
> instance, the rocket scientist who set this database up gave the USERS
> datafile a size of 1MB. I want to expand this, but cannot, because
the
> Storage Manager tells me my Compatible parameter is not sufficient.
>
> Any thoughts what could be causing this behavior?
>
> Thanks.
>
> Sybrand Bakker <postmaster_at_sybrandb.demon.nl> wrote in message
> news:934305532.14577.0.pluto.d4ee154e_at_news.demon.nl...
> > Could it be your string is too short
> > 7.3.4.0
> > against
> > 7.3.0.0.0
> > Sometimes Oracle can be very stupid.
> > I'm not sure why you want to create a check(c1 is not null)
constraint on
> a
> > column, which is already mandatory.
> > Just asking...
> >
> > Hth,
> >
> > Sybrand Bakker, Oracle DBA
> >
> > Christopher Allen <progplusSPAMBEGONE_at_gte.net> wrote in message
> > news:zIYr3.242$P36.11560_at_dfiatx1-snr1.gtei.net...
> > > I'm trying to perform a simple DDL operation that my Solaris
Oracle
> > > 7.3.4.0.1 server is refusing to run, citing a problem with its
> COMPATIBLE
> > > parameter. The thing is: its COMPATIBLE parameter is actually
fine.
> > >
> > > The problem appears when I run this command:
> > > CREATE TABLE T2
> > >
> > > C1 NUMBER NOT NULL,
> > > C2 VARCHAR2(30) NULL,
> > > C3 DATE NULL,
> > > CHECK (C1 IS NOT NULL)
> > > )
> > > PCTFREE 10
> > > PCTUSED 40
> > > INITRANS 1
> > > MAXTRANS 255
> > > STORAGE (
> > > INITIAL 1024K
> > > NEXT 1024K
> > > MINEXTENTS 1
> > > MAXEXTENTS 2147483645
> > > PCTINCREASE 1)
> > > ;
> > >
> > > The response is:
> > > CHECK (C1 IS NOT NULL)
> > > *
> > > ERROR at line 5:
> > > ORA-00406: COMPATIBLE parameter needs to be 7.3.0.0.0 or greater
> > >
> > > The COMPATIBLE parameter *is* greater than 7.3.0.0.0. Here is the
line
> > from
> > > the initORCL.ORA file:
> > > compatible = 7.3.4.0
> > >
> > > I would appreciate ANY ideas about what could be causing this
problem.
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Wed Aug 11 1999 - 11:25:39 CDT