alter fragment on table <table name> init in <dbspace>
Posted in 2000
Topics: Storage & Space Management, Transactions, Locking & Isolation
I'm trying to eliminate multiple extents on a table by issuing a "alter fragment on table <table name> init in <dbspace>". I'm getting the error 875: -875 Incompatible Access Mode and Isolation Level. If you set the access mode to READ-WRITE, you cannot set the isolation level to READ-UNCOMMITTED. Here the thing, the database I'm using has "no logging" so I can't set isolation levels. I turned off logging temporarily so that I could get around the long transaction. I know I could always just drop and recreate the table, but I was trying to avoid that. What can I do to get past this?
In article <88hbvm$6pm$1@nnrp03.primenet.com>, Top Cat
<cstefanick@ocsmgmt.com> writes
>I'm trying to eliminate multiple extents on a table by issuing a "alter
>fragment on table <table name> init in <dbspace>". I'm getting the error
>875:
>
>-875 Incompatible Access Mode and Isolation Level.
>
>If you set the access mode to READ-WRITE, you cannot set the isolation
>level to READ-UNCOMMITTED.
>
>Here the thing, the database I'm using has "no logging" so I can't set
>isolation levels. I turned off logging temporarily so that I could get
>around the long transaction. I know I could always just drop and recreate
>the table, but I was trying to avoid that. What can I do to get past this?
>
>
Known bug with IDS 7.30. Run oncheck -pe and you should find that the
alter fragment has completed OK!!! From memory dbaccess produces the
error,isql does not!
Move to 7.31.UC4...
--
David Williams