joel garry schreef:
> On Feb 28, 7:23 am, "BGT" <bgt0..._at_optonline.net> wrote:
>> I am no longer able to truncate tables in this 9.2.0.6.0 database.
>> When I do a "truncate table "tablename" drop storage" I get ORA-00904
>> "DROP SEGMENTS" INVALID IDENTIFIER.
>>
>> I've tried this on multiple tables as the schema owner and a SYSDBA
>> user with the same results. Any idea what is happening?
>>
>> Thanks
>> Barry
>
> Well, there was a bug in an earlier version, maybe somewhere along the
> line you ran the wrong catalog.sql or got an old sql.bsq.
>
> as sys,
> SQL> desc mon_mods$
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> OBJ# NUMBER
> INSERTS NUMBER
> UPDATES NUMBER
> DELETES NUMBER
> TIMESTAMP DATE
> FLAGS NUMBER
> DROP_SEGMENTS NUMBER
>
> If you don't have a field named drop_segments, you have this problem
> (which could potentially be a quite serious patching goof). Check
> sql.bsq to be sure it has a create statement that matches this table.
> Then try running catalog.sql.
>
> jg
> --
> @home.com is bogus.
> Are they still using Sybase? http://www.kstp.com/article/stories/S33513.shtml?cat=1
>
Sounds like a default installed database with patched software?
One time, a version downloadable was patched (9.2.0.4/Linux, iirc), but
the sample databases were *not*.
Is this the case here?
--
Regards,
Frank van Bortel
Top-posting is one way to shut me up...
Received on Wed Feb 28 2007 - 14:03:32 CST
