The mystery of the disappearing dbspaces ...
On IDS 10.00.FC8 under RHEL 5, Neil Truby built a new instance with six dbspaces (rootdbs, physdbs, llogdbs, tempdbs1-3), added logical logs to llogdbs, then stopped and restarted the server to move the physical log. After restart only rootdbs and physdbs remained; the temp dbspaces were reported invalid in DBSPACETEMP and the logical-log dbspace was gone. Replies noted the 'scan_eh_frame(): bad CIE reference' message is unrelated (libc symbol-table loading), suggested an old workaround of using a small chunk offset where the OS writes to header bytes, and asked whether the online log from when the dbspaces were created showed errors, possibly ownership/permission problems. No resolution is recorded in the thread.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
IDS 10.0FC8 on RHEL 5.
Here's a funny old thing!
I'm just building a new database server.
I have 6 dbspaces so far: root, physdbs, llogdbs, and tempdbs1-3
You can see that I'm adding the logs to llogdbs. Then I shut down Informix
and restart it to move the PHYSDBS.
What do you know? 4 of my dbspaces have disappeared into thin air!
Including the one "DBspace 3" that you can referenced in the log as having
logical logs added to it.
Don't know if
00:44:25 pid 26739: scan_eh_frame(): bad CIE referencehas anything to do with it.
But it's spooky!
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com
00:42:58 Maximum server connections 1
00:42:59 Log file 409 added to DBspace 3.
00:42:59 Checkpoint Completed: duration was 0 seconds.
00:42:59 Checkpoint loguniq 9, logpos 0xdf128, timestamp: 0x1053b
00:42:59 Maximum server connections 1
00:44:06 Log file 410 added to DBspace 3.
00:44:06 Checkpoint Completed: duration was 0 seconds.
00:44:06 Checkpoint loguniq 9, logpos 0xe1128, timestamp: 0x10f57
00:44:06 Maximum server connections 1
00:44:14 Checkpoint Completed: duration was 0 seconds.
00:44:14 Checkpoint loguniq 9, logpos 0xe3018, timestamp: 0x10f64
00:44:14 Maximum server connections 1
00:44:15 IBM Informix Dynamic Server Stopped.
00:44:24 IBM Informix Dynamic Server Started.
00:44:24 Segment locked: addr=0x44000000, size=3370373120
00:44:24 Segment locked: addr=0x10ce3d000, size=2621440000
Mon Mar 3 00:44:25 2008
00:44:25 pid 26739: scan_eh_frame(): bad CIE reference
00:44:26 Event alarms enabled. ALARMPROG =
'/opt/informix/10.0/etc/alarmprogram.sh'
00:44:26 Booting Language <c> from module <>
00:44:26 Loading Module <CNULL>
00:44:26 Booting Language <builtin> from module <>
00:44:26 Loading Module <BUILTINNULL>
00:44:31 DR: DRAUTO is 0 (Off)
00:44:31 IBM Informix Dynamic Server Version 10.00.FC8 Software SerialNumber AAA#B000000
00:44:31 IBM Informix Dynamic Server Initialized -- Shared MemoryInitialized.
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs1'
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs2'
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs3'
00:44:31 Physical Recovery Started at Page (1:1026).
00:44:31 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
00:44:31 Logical Recovery Started.
00:44:31 10 recovery worker threads will be started.
00:44:32 Fast Recovery Switching to Log 4
IBM Informix Dynamic Server Version 10.00.FC8 -- On-Line -- Up
00:08:10 -- 5851924 Kbytes
Dbspaces
address number flags fchunk nchunks pgsize flags
owner name
10d275e78 1 0x60001 1 1 2048 N B
informix rootdbs
10f20a1c8 2 0x60001 2 1 2048 N B
informix physdbs
2 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages
flags pathname
10d276028 1 1 0 51200 45411
PO-B /opt/informix/dbspaces1/rootdbs_1
10f20a028 2 2 0 512000 0
PO-B /opt/informix/dbspaces1/physdbs_1
2 active, 32766 maximum
NOTE: The values in the "size" and "free" columns for DBspace chunks are
displayed in terms of "pgsize" of the DBspace to which they belong.
Expanded chunk capacity mode: always
Neil Truby wrote:
> IDS 10.0FC8 on RHEL 5.
>
> Here's a funny old thing!
> I'm just building a new database server.
> I have 6 dbspaces so far: root, physdbs, llogdbs, and tempdbs1-3
>
> You can see that I'm adding the logs to llogdbs. Then I shut down Informix
> and restart it to move the PHYSDBS.
>
> What do you know? 4 of my dbspaces have disappeared into thin air!
> Including the one "DBspace 3" that you can referenced in the log as having
> logical logs added to it.
>
> Don't know if
> 00:44:25 pid 26739: scan_eh_frame(): bad CIE reference> has anything to do with it.
>
> But it's spooky!
Apparently not... This message seems to be related to the loading of the symbol
table in libc... It will probably affect the ability to print accurate stack
traces, but shouldn't be responsible for anything similar to what you're
referring...
You'll need further investigation...
--
Fernando Nunes
Portugal
http://informix-technology.blogspot.com
My email works... but I don't check it frequently...
Neil Truby wrote: > IDS 10.0FC8 on RHEL 5. > > Here's a funny old thing! > I'm just building a new database server. > I have 6 dbspaces so far: root, physdbs, llogdbs, and tempdbs1-3 > > You can see that I'm adding the logs to llogdbs. Then I shut down Informix > and restart it to move the PHYSDBS. > > What do you know? 4 of my dbspaces have disappeared into thin air! > Including the one "DBspace 3" that you can referenced in the log as having > logical logs added to it. > I don't know if this might be valid here, but I remember that many, many moons ago this problem used to occur on certain operating systems because the OS wanted to stick stuff into the header bytes of each space. The workaround was to use a small offset.
Neil,
Do you still have the IDS log when the dbspaces were added? I have seen
something similar when the dbspaces were added correctly according to
onmonitor but when we looked in the log it showed errors.
But that was on a training course and I can't remember why the dbspaces
weren't added but I think it might have been ownership or permissions.
Regards
Malcolm
-----Original Message-----
From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org]
On Behalf Of Neil Truby
Sent: 02 March 2008 23:57
To: informix-list@iiug.org
Subject: The mystery of the disappearing dbspaces ...
IDS 10.0FC8 on RHEL 5.
Here's a funny old thing!
I'm just building a new database server.
I have 6 dbspaces so far: root, physdbs, llogdbs, and tempdbs1-3
You can see that I'm adding the logs to llogdbs. Then I shut down Informix
and restart it to move the PHYSDBS.
What do you know? 4 of my dbspaces have disappeared into thin air!
Including the one "DBspace 3" that you can referenced in the log as having
logical logs added to it.
Don't know if
00:44:25 pid 26739: scan_eh_frame(): bad CIE referencehas anything to do with it.
But it's spooky!
--
Neil Truby t:01932 724027
Director m:07798 811708
Ardenta Limited e:neil.truby@ardenta.com
00:42:58 Maximum server connections 1
00:42:59 Log file 409 added to DBspace 3.
00:42:59 Checkpoint Completed: duration was 0 seconds.
00:42:59 Checkpoint loguniq 9, logpos 0xdf128, timestamp: 0x1053b
00:42:59 Maximum server connections 1
00:44:06 Log file 410 added to DBspace 3.
00:44:06 Checkpoint Completed: duration was 0 seconds.
00:44:06 Checkpoint loguniq 9, logpos 0xe1128, timestamp: 0x10f57
00:44:06 Maximum server connections 1
00:44:14 Checkpoint Completed: duration was 0 seconds.
00:44:14 Checkpoint loguniq 9, logpos 0xe3018, timestamp: 0x10f64
00:44:14 Maximum server connections 1
00:44:15 IBM Informix Dynamic Server Stopped.
00:44:24 IBM Informix Dynamic Server Started.
00:44:24 Segment locked: addr=0x44000000, size=3370373120
00:44:24 Segment locked: addr=0x10ce3d000, size=2621440000
Mon Mar 3 00:44:25 2008
00:44:25 pid 26739: scan_eh_frame(): bad CIE reference
00:44:26 Event alarms enabled. ALARMPROG =
'/opt/informix/10.0/etc/alarmprogram.sh'
00:44:26 Booting Language <c> from module <>
00:44:26 Loading Module <CNULL>
00:44:26 Booting Language <builtin> from module <>
00:44:26 Loading Module <BUILTINNULL>
00:44:31 DR: DRAUTO is 0 (Off)
00:44:31 IBM Informix Dynamic Server Version 10.00.FC8 Software SerialNumber AAA#B000000
00:44:31 IBM Informix Dynamic Server Initialized -- Shared MemoryInitialized.
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs1'
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs2'
00:44:31 Warning: Invalid (non-existent/blobspace/disabled) dbspace listed
in DBSPACETEMP: 'tempdbs3'
00:44:31 Physical Recovery Started at Page (1:1026).
00:44:31 Physical Recovery Complete: 0 Pages Examined, 0 Pages Restored.
00:44:31 Logical Recovery Started.
00:44:31 10 recovery worker threads will be started.
00:44:32 Fast Recovery Switching to Log 4
IBM Informix Dynamic Server Version 10.00.FC8 -- On-Line -- Up
00:08:10 -- 5851924 Kbytes
Dbspaces
address number flags fchunk nchunks pgsize flags
owner name
10d275e78 1 0x60001 1 1 2048 N B
informix rootdbs
10f20a1c8 2 0x60001 2 1 2048 N B
informix physdbs
2 active, 2047 maximum
Chunks
address chunk/dbs offset size free bpages
flags pathname
10d276028 1 1 0 51200 45411
PO-B /opt/informix/dbspaces1/rootdbs_1
10f20a028 2 2 0 512000 0
PO-B /opt/informix/dbspaces1/physdbs_1
2 active, 32766 maximum
NOTE: The values in the "size" and "free" columns for DBspace chunks are
displayed in terms of "pgsize" of the DBspace to which they belong.
Expanded chunk capacity mode: always
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list