Re: stale dbspace info

In article <64v5ht$ffl@cssun.mathcs.emory.edu>, chris@dvs1.informatik.th-darmstadt.de writes > >Hi ! > >Recently we had a power loss which caused a hard disk damage in turn. >The disk contained several primary chunks as cooked file space for >dbspaces. > >Although the dbspaces are lost, informix still carries the configuration >infos about the now physically lost dbspaces (e.g. onstat -d lists >them). > >On my way to reestablish this dbspaces I tried first to drop them. >This was not possible, onspaces would report an "internal ISAM error". >I went on recreating the dbspace files with exactly the same path as >before >(of course, the i-nodes will be different). >This did not help much, onspaces gives me the same error as above. > >My question: how can I delete the stale info on dbspaces that no more >exists, e.g. is there some system table to edit ? > >TIA, > >Chris > > > 1. dbexport all databases 2. shudown online 3. Edit onconfig file and remove any references to dbspaces other then you root dbspace. (check PHYSDBS,LOGDBS,DBSPACETEMP) 4. Note the dbspaces and chunks you wish to keep. (pathnames,sizes and offsets). 4. oninit -i NOTE: YOU LOSE EVERYTHGING AND GET AN EMPTY ROOT DBSPACE NOTE: YOU LOSE EVERYTHGING AND GET AN EMPTY ROOT DBSPACE NOTE: YOU LOSE EVERYTHGING AND GET AN EMPTY ROOT DBSPACE 5. Add required dbspaces/chunks. 6. dbimport all your databases. Of course if this was a live system just restore a level 0 archive and feed Online logical log tapes when it asks for them.. -- David Williams