How dangerous is to update a sysmaster table (syschunks)?
Posted in 2000
dankami asked what would happen if he updated is_consistent in sysmaster:syschunks to clear a PI- inconsistent chunk flag. Pankaj, Madison Pruet and Jacob Salomon said sysmaster is read-only pseudo-tables and the column is derived from a flag. Art S. Kagel said it cannot and should not be done, it would only change memory, and support can fix the chunk page on disk. Advice was to call support.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Topics: Storage & Space Management
I have a chunk that is marked with PI- inconsistent. This chunk only contains one database that could be droped. This inconsistency flags comes from the is_consistent column found in the syschunks table of the sysmater database. It is equal to 1 when the chunk is inconsistent and 0 when is consistent. what will happen if I set is_consistent to 0 instead 1 by doing: update sysmaster:syschunks set is_consistent=0 where is_consistent=1 and fname=my_chun_file; Any body tried this update. Thanks. Sent via Deja.com http://www.deja.com/ Before you buy.
Hi , You cannot do an update you only have select permission on the sysmaster database. No Update , insert or delete permissions. The sysmaster contains SMI tables and ON-Archive Catalog tables. Hope this helps Cheers Pankaj dankami@my-deja.com wrote in message <8nej5d$857$1@nnrp1.deja.com>... |I have a chunk that is marked with PI- inconsistent. This chunk only |contains one database that could be droped. | |This inconsistency flags comes from the is_consistent column found in |the syschunks table of the sysmater database. It is equal to 1 when the |chunk is inconsistent and 0 when is consistent. | |what will happen if I set is_consistent to 0 instead 1 by doing: | |update sysmaster:syschunks |set is_consistent=0 |where is_consistent=1 |and fname=my_chun_file; | |Any body tried this update. | | |Thanks. | | |Sent via Deja.com http://www.deja.com/ |Before you buy.
One of the Informix documentation CDs includes a chapter on what *not* to do - and this sort of thing is included. In article <8nej5d$857$1@nnrp1.deja.com>, dankami@my-deja.com writes >I have a chunk that is marked with PI- inconsistent. This chunk only >contains one database that could be droped. > >This inconsistency flags comes from the is_consistent column found in >the syschunks table of the sysmater database. It is equal to 1 when the >chunk is inconsistent and 0 when is consistent. > >what will happen if I set is_consistent to 0 instead 1 by doing: > >update sysmaster:syschunks >set is_consistent=0 >where is_consistent=1 >and fname=my_chun_file; > >Any body tried this update. > > >Thanks. > > >Sent via Deja.com http://www.deja.com/ >Before you buy. -- Surfer!
sysmaster is a pseudo database. As such it is read only. (Or at least it'd better be. ;-) ) dankami@my-deja.com wrote: > I have a chunk that is marked with PI- inconsistent. This chunk only > contains one database that could be droped. > > This inconsistency flags comes from the is_consistent column found in > the syschunks table of the sysmater database. It is equal to 1 when the > chunk is inconsistent and 0 when is consistent. > > what will happen if I set is_consistent to 0 instead 1 by doing: > > update sysmaster:syschunks > set is_consistent=0 > where is_consistent=1 > and fname=my_chun_file; > > Any body tried this update. > > Thanks. > > Sent via Deja.com http://www.deja.com/ > Before you buy.
Dankami,
syschunks is a view of multiple [pseudo-] tables. You could not update
it if it were based on real tables. The "is_inconsistent" column of
syschunks is just a display-label name for a procedure call:
bitval(syschktab.flags, '0x1000')
You don't want to go there and, actually, you can't. If you need to
remove that flag, you may need to call advanced-support and have them
run their undocumented oncheck options (or download some nasty medicine)
to remove that flag.
--
+----- Jacob Salomon - DBA JSalomon@bn.com - --------------------------+
|------------------- Bulletin Board Announcement ----------------------|
| Congregants will please note that the bowl at the back of the church |
| bearing the sign "For the Sick" is for monetary contributions only. |
+----------------------------------------------------------------------+
In article <399BF41A.5EC31B84@home.com>,
Madison Pruet <mpruet@home.com>wrote:
>sysmaster is a pseudo database. As such it is read only. (Or at least
>it'd better be. ;-) )
>
>dankami@my-deja.com wrote:
>
>>I have a chunk that is marked with PI- inconsistent. This chunk only
>>contains one database that could be droped.
>>
>>This inconsistency flags comes from the is_consistent column found in
>>the syschunks table of the sysmater database. It is equal to 1 when
>>the chunk is inconsistent and 0 when is consistent.
>>
>>what will happen if I set is_consistent to 0 instead 1 by doing:
>>
>>update sysmaster:syschunks
>>set is_consistent=0
>>where is_consistent=1
>>and fname=my_chun_file;
>>
>>Any body tried this update.
>>
>>Thanks.
>>
>>Sent via Deja.com http://www.deja.com/
>>Before you buy.
Sent via Deja.com http://www.deja.com/
Before you buy.
You cannot. You don't want to. Don't do it. Even if you could, even if you wanted to, you would only be changing the flag in memory not on disk so the next startup the problem returns. You CAN shut the engine down and "correct" the chunks page(s) on disk, indeed that is what Tech support will do if you call them. This is not for the faint of heart, the inexperienced, or the careless and remember if you let support do it they are resposible if they F*^K up. There are so many ways to S*&^W this up it's not funny. Call it in. Art S. Kagel dankami@my-deja.com wrote: > > I have a chunk that is marked with PI- inconsistent. This chunk only > contains one database that could be droped. > > This inconsistency flags comes from the is_consistent column found in > the syschunks table of the sysmater database. It is equal to 1 when the > chunk is inconsistent and 0 when is consistent. > > what will happen if I set is_consistent to 0 instead 1 by doing: > > update sysmaster:syschunks > set is_consistent=0 > where is_consistent=1 > and fname=my_chun_file; > > Any body tried this update. > > Thanks. > > Sent via Deja.com http://www.deja.com/ > Before you buy.