HELP! rootdbs corrupted!
Posted in 2008
Topics: Performance & Tuning, Installation, Setup & Upgrades, Storage & Space Management, Error Codes & Troubleshooting, Migration, Import/Export & Data Conversion, Platform-Specific Issues, Versions, Editions & End-of-Life
Hello everybody!
Please help me or my boss will kill me :(
What do we have:
HP-UX 11.11 (PA-RISC)
Informix IDS 9.3 FC6 with ~4TB database
And date of acceptance - 31/Mar/2008!!!
History:
Once customer decided to add some functionality to the system and
increase disk space. They have installed additional and more powerful
disk array and asked us to migrate the system to this array.
After successful migration everybody were happy with increased
performance and space. But the data was left as backup.
Today the nightmare became.
The old disk array became unstable and it was required to free some
space on it. When our disk array engineer asked us can he delete the
VDISK with old database from the old device we said "sure you can" and
he did it.
After that the server stopped responding. BTW online config.log does
not contain any strange messages.
When we try to oninit the serber it says (in online.log):
20:13:56 IBM Informix Dynamic Server Started.
20:14:11 Segment locked: addr=0xc00000000051e000, size=4294705152
20:14:11 Requested shared memory segment size rounded from 2285053KB
to 2285056KB
20:14:19 Segment locked: addr=0xc0000001004de000, size=2339897344
Wed Mar 26 20:14:23 2008
20:14:23 Event alarms enabled. ALARMPROG = '/apps/inst1/informix/ids.
93/etc/log_full.sh'
20:14:23 Booting Language <c> from module <>
20:14:23 Loading Module <CNULL>
20:14:23 Booting Language <builtin> from module <>
20:14:23 Loading Module <BUILTINNULL>
20:14:35 IBM Informix Dynamic Server Version 9.30.FC6X9 Software
Serial Number XXX#XXXXXXXXX
20:14:36 IBM Informix Dynamic Server Initialized -- Shared Memory
Initialized.
20:14:36 Physical Recovery Started at Page(3:144595).
20:14:38 Physical Recovery Complete: 29340 Pages Examined 29340 Pages
Restored.
20:14:38 Logical Recovery Started.
20:14:38 10 recovery worker threads will be started.
20:14:38 Assert Failed: Dynamic Server must abort
20:14:38 IBM Informix Dynamic Server Version 9.30.FC6X9
20:14:38 Who: Session(7, informix@mpmnw, 0, 335488200)
Thread(177, fast_rec, c000000113fb1088, 1)
File: rslog.c Line: 3383
20:14:38 Results: Dynamic Server must abort
20:14:38 Action: Reinitialize shared memory
20:14:38 stack trace for pid 4817 written to /apps/informix_dump/af.
499847e
20:14:38 See Also: /apps/informix_dump/af.499847e, shmem.499847e.0
20:14:49 Error writing '/apps/informix_dump/shmem.499847e.0' errno =
27
20:14:49 rslog.c, line 3383, thread 177, proc id 4817, Dynamic Server
must abort.
20:14:49 PANIC: Attempting to bring system down
After investigations it was identified that during the migration we
have made a serious mistake - the rootdbs was not relinked to the new
storage.
So currently we have 4TBs of data with old rootdbs and its mirror
(which were actual at the moment of migration).
And the question is: how to restore the rootdbs with all (or most part
of) data.
I believe it is possible. May be with manual writing lots of commands
or filling some tables in sysmaster ot something else.
Kind regards,
Pavel
Restore from backup?
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com
<pavel-lechenko@yandex.ru> wrote in message
news:98af696e-ba92-4bbf-a2af-829a038def24@s19g2000prg.googlegroups.com...
> Hello everybody!
>
> Please help me or my boss will kill me :(
>
> What do we have:
> HP-UX 11.11 (PA-RISC)
> Informix IDS 9.3 FC6 with ~4TB database
> And date of acceptance - 31/Mar/2008!!!
>
> History:
> Once customer decided to add some functionality to the system and
> increase disk space. They have installed additional and more powerful
> disk array and asked us to migrate the system to this array.
> After successful migration everybody were happy with increased
> performance and space. But the data was left as backup.
>
> Today the nightmare became.
>
> The old disk array became unstable and it was required to free some
> space on it. When our disk array engineer asked us can he delete the
> VDISK with old database from the old device we said "sure you can" and
> he did it.
>
> After that the server stopped responding. BTW online config.log does
> not contain any strange messages.
>
> When we try to oninit the serber it says (in online.log):
> 20:13:56 IBM Informix Dynamic Server Started.
> 20:14:11 Segment locked: addr=0xc00000000051e000, size=4294705152
> 20:14:11 Requested shared memory segment size rounded from 2285053KB
> to 2285056KB
> 20:14:19 Segment locked: addr=0xc0000001004de000, size=2339897344
>
> Wed Mar 26 20:14:23 2008
>
> 20:14:23 Event alarms enabled. ALARMPROG = '/apps/inst1/informix/ids.
> 93/etc/log_full.sh'
> 20:14:23 Booting Language <c> from module <>
> 20:14:23 Loading Module <CNULL>
> 20:14:23 Booting Language <builtin> from module <>
> 20:14:23 Loading Module <BUILTINNULL>
> 20:14:35 IBM Informix Dynamic Server Version 9.30.FC6X9 Software
> Serial Number XXX#XXXXXXXXX
> 20:14:36 IBM Informix Dynamic Server Initialized -- Shared Memory
> Initialized.
>
> 20:14:36 Physical Recovery Started at Page(3:144595).
> 20:14:38 Physical Recovery Complete: 29340 Pages Examined 29340 Pages
> Restored.
>
> 20:14:38 Logical Recovery Started.
> 20:14:38 10 recovery worker threads will be started.
> 20:14:38 Assert Failed: Dynamic Server must abort
> 20:14:38 IBM Informix Dynamic Server Version 9.30.FC6X9
> 20:14:38 Who: Session(7, informix@mpmnw, 0, 335488200)
> Thread(177, fast_rec, c000000113fb1088, 1)
> File: rslog.c Line: 3383
> 20:14:38 Results: Dynamic Server must abort
> 20:14:38 Action: Reinitialize shared memory
> 20:14:38 stack trace for pid 4817 written to /apps/informix_dump/af.
> 499847e
> 20:14:38 See Also: /apps/informix_dump/af.499847e, shmem.499847e.0
> 20:14:49 Error writing '/apps/informix_dump/shmem.499847e.0' errno =
> 27
> 20:14:49 rslog.c, line 3383, thread 177, proc id 4817, Dynamic Server
> must abort.
> 20:14:49 PANIC: Attempting to bring system down
>
> After investigations it was identified that during the migration we
> have made a serious mistake - the rootdbs was not relinked to the new
> storage.
>
> So currently we have 4TBs of data with old rootdbs and its mirror
> (which were actual at the moment of migration).
>
> And the question is: how to restore the rootdbs with all (or most part
> of) data.
>
> I believe it is possible. May be with manual writing lots of commands
> or filling some tables in sysmaster ot something else.
>
>
> Kind regards,
>
> Pavel