Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
You should have waited until the logs were cleared.
check onstat -Dr |grep <"chunks with logs">
and notice that a whole lot of i/o is done on those guys.
for now do a
-- Assume engine is offline
onbar -r -e -pfollowed by an onmode -m
you may be lucky.... and this time wait for clearing of the logs to be
complete.
if it hangs (onstat -Dr |grep <"chunks with logs"> does not show
increasing writes)
then phone TS.
may be they make you do the restore again. (i would...)
Superboer.
GemaVi schreef:
> Hello,
>
> after a cold recovery of Informix 9.40 UC2 the status remained in
> Fast-Recovery. Last line of the online.log during recovery was:
>
> 11:50:28 Maximum server connections 0
> 11:50:35 No logical log restore will be performed.
> 11:50:35 Preparing Physical Log for Fast Recovery ...
> 11:50:35 Clearing the physical and logical logs has started> (Nothing saying that the physical and logical logs had been cleared)
>
> I killed Informix with oninit -ky and try to start it again. But then I
> get the following error message:
>
> Checking database partition index.... FAILED.
>
> The complete startup sequence would be:
>
> Checking group membership to determine server run modesucceeded
> Reading configuration file '/usr/informix/etc/onconfig'...succeeded
> Creating /INFORMIXTMP/.infxdirs ... succeeded
> Creating infos file "/usr/informix/etc/.infos.online1" ...
> "/usr/informix/etc/.conf.online1" ... succeeded
> Writing to infos file ... succeeded
> Checking config parameters...succeeded
> Allocating and attaching to shared memory...
> succeeded
> Creating resident pool 22108 kbytes...succeeded
> Creating buffer pool 200002 kbytes...succeeded
> Initializing rhead structure...succeeded
> Initializing ASF ...succeeded
> Initializing Dictionary Cache and SPL Routine Cache...succeeded
> Bringing up ADM VP...succeeded
> Creating VP classes...succeeded
> Onlining 0 additional cpu vps...succeeded
> Onlining 6 IO vps...succeeded
> Initialization of Encryption...succeeded
> Forking main_loop thread...succeeded
> Initializing DR structures...succeeded
> Forking 1 'ipcshm' listener threads...succeeded
> Forking 4 'tlitcp' listener threads...succeeded
> Forking 0 'tlitcp' listener threads...succeeded
> Starting tracing...succeeded
> Initializing 127 flushers...succeeded
> Initializing log/checkpoint information...succeeded
> Opening primary chunks...succeeded
> Opening mirror chunks...succeeded
> Initializing dbspaces...succeeded
> Validating chunks...succeeded
> Initialize Async Log Flusher...succeeded
> Forking btree cleaner...succeeded
> Initializing DBSPACETEMP list
> Checking database partition index...FAILED
>
> Any idea of what this error might be?
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.