Re: Root Space Full
Hi guy
The "prod_db:'root'. 3004_3466" means (to me) an index that was builted
when you create a foreign key.
Is usual IDS get the tableid of 2 tables (pk and fk) to give the name
of index.
Try to see:
Select * from sysindexes where idxname like "%3004_3466" ;and then look if it is an index for constraints.....
Regards. Ferronato
Ben escreveu:
> IDS 9.4 UC4
> Solaris 2.6
>
> We are having trouble with one of our instances - the root database space
> 'rootdbs' keeps filling up. The problem coincides with adding two tables to
> other dbspaces and then loading data (about 8m rows each) into the new
> tables. The problem appears to be a few objects beginning with the ' '
> character (see "prod_db:'root'. 3004_3466" below). What are these objects?
> My suspician is that the database 'prod_db' was created in the root space
> and this is metadata related to that database.
>
> Thanks in advance (and running for cover),
> Ben
>
>
> ---> Output of 'oncheck -pe' <---
>
> DBspace Usage Report: rootdbs Owner: informix Created:
> 11/11/2002
>
>
> Chunk Pathname Size Used
> Free
> 1 /dev/prim_rootdbs 500000 494315 5685
>
> Description Offset
> Size
> ------------------------------------------------------------- -------- --------
> RESERVED PAGES 0
> 12
> CHUNK FREELIST PAGE 12
> 1
> rootdbs:'informix'.TBLSpace 13
> 50
> prod_db:'informix'.systables 63
> 8
> prod_db:'informix'.syscolumns 71
> 16
> prod_db:'informix'.sysindices 87
> 16
> prod_db:'informix'.syscolauth 103
> 8
> prod_db:'informix'.sysviews 111
> 8
> prod_db:'informix'.sysusers 119
> 8
> prod_db:'informix'.sysdepend 127
> 8
> prod_db:'informix'.syssynonyms 135
> 8
> prod_db:'informix'.syssyntable 143
> 8
> prod_db:'informix'.syscolumns 151
> 8
> prod_db:'informix'.sysreferences 159
> 8
> prod_db:'informix'.syschecks 167
> 8
> prod_db:'informix'.sysindices 175
> 8
> prod_db:'informix'.syscoldepend 183
> 8
> prod_db:'informix'.sysindices 191
> 8
> prod_db:'informix'.sysprocbody 199
> 8
> prod_db:'informix'.sysprocplan 207
> 8
> prod_db:'informix'.sysprocauth 215
> 8
> prod_db:'informix'.sysblobs 223
> 8
> prod_db:'informix'.sysopclstr 231
> 8
> prod_db:'informix'.syscolumns 239
> 8
> prod_db:'informix'.systrigbody 247
> 8
> prod_db:'informix'.sysprocedures 255
> 8
> prod_db:'informix'.sysfragments 263
> 8
> prod_db:'informix'.sysfragauth 271
> 8
> prod_db:'informix'.sysroleauth 279
> 8
> prod_db:'informix'.sysobjstate 287
> 8
> prod_db:'informix'.sysviolations 295
> 8
> prod_db:'informix'.sysprocbody 303
> 8
> prod_db:'informix'.syscolumns 311
> 8
> prod_db:'informix'.systables 319
> 8
> prod_db:'informix'.syscolumns 327
> 8
> prod_db:'informix'.sysprocauth 335
> 8
> prod_db:'informix'.syscolumns 343
> 8
> prod_db:'informix'.sysobjstate 351
> 8
> FREE 359
> 8
> prod_db:'informix'.syscolumns 367
> 8
> prod_db:'informix'.sysfragments 375
> 8
> prod_db:'informix'.sysprocedures 383
> 40
> prod_db:'informix'.sysfragments 423
> 16
> prod_db:'informix'.sysobjstate 439
> 8
> prod_db:'informix'.sysprocedures 447
> 8
> prod_db:'informix'.sysprocbody 455
> 16
> prod_db:'informix'.sysprocplan 471
> 8
> prod_db:'informix'.sysprocbody 479
> 8
> prod_db:'informix'.sysprocplan 487
> 8
> prod_db:'informix'.sysprocbody 495
> 24
> prod_db:'informix'.sysprocplan 519
> 8
> prod_db:'informix'.sysprocbody 527
> 8
> prod_db:'informix'.sysprocplan 535
> 8
> prod_db:'informix'.sysprocbody 543
> 32
> prod_db:'informix'.sysprocplan 575
> 8
> prod_db:'informix'.sysprocbody 583
> 24
> prod_db:'informix'.sysprocplan 607
> 8
> prod_db:'informix'.sysprocbody 615
> 32
> prod_db:'informix'.sysprocplan 647
> 8
> prod_db:'informix'.sysprocbody 655
> 8
> prod_db:'informix'.sysprocplan 663
> 8
> prod_db:'informix'.sysprocbody 671
> 8
> prod_db:'informix'.sysprocplan 679
> 8
> prod_db:'informix'.sysprocbody 687
> 24
> prod_db:'informix'.sysprocplan 711
> 8
> prod_db:'informix'.sysprocbody 719
> 40
> prod_db:'informix'.sysprocplan 759
> 8
> prod_db:'informix'.sysprocbody 767
> 24
> prod_db:'informix'.sysprocplan 791
> 8
> prod_db:'informix'.sysprocbody