Startup of informix 7.2 database fails - Physical log
When I start up a legacy 7.2 database using 'oninit -v' I get the
following error:
<successful startup messages snipped>
Checking location of physical log...FAILED
oninit: Fatal error in shared memory initialization
My onconfig file has the following:
# Physical Log Configuration
PHYSDBS plogdbs # Location (dbspace) of physical log
PHYSFILE 100000 # Physical log file size (Kbytes)
# Logical Log Configuration
LOGFILES 8 # Number of logical log files
LOGSIZE 20000 # Logical log size (Kbytes)
There is a /dev/prod_plogdbs which is a symbolic link to
/dev/vg05/rlvol1.
This is on an HP-UX 10.20 system and the database is accessed about
once every two weeks and those accesses are queries, not updates.
So, besides the "Would anyone be so kind as to offer information to
help make this thing work?" question, here are the other questions
this situation raises.
1) How does oninit know to use /dev/prod_plogdbs (does it assume
/dev/prod_ as a prefix)?
2) Will replacing 'plogdbs' with 'rootdbs' in my config file fix or
completely destroy my database? I've been told by one source to just
specify rootdbs as the location of the physical logs -- to paraphrase:
"I always just put the physical logs on rootdbs". I don't know what
that'll do to an existing database (being unfamiliar with Informix, I
don't want to trash anything by "trying" stuff).
3) Can I destroy and create a new plogdbs? Or simply re-initialize
the existing plogdbs?
Any help would be appreciated!
GW
oncheck-pr and check for messages
Cold potatoe
1.21 Giga Watts wrote:
> When I start up a legacy 7.2 database using 'oninit -v' I get the
> following error:
> <successful startup messages snipped>
> Checking location of physical log...FAILED
> oninit: Fatal error in shared memory initialization
>
> My onconfig file has the following:
> # Physical Log Configuration
>
> PHYSDBS plogdbs # Location (dbspace) of physical log
> PHYSFILE 100000 # Physical log file size (Kbytes)>
> # Logical Log Configuration
>
> LOGFILES 8 # Number of logical log files
> LOGSIZE 20000 # Logical log size (Kbytes)>
> There is a /dev/prod_plogdbs which is a symbolic link to
> /dev/vg05/rlvol1.
> This is on an HP-UX 10.20 system and the database is accessed about
> once every two weeks and those accesses are queries, not updates.
>
> So, besides the "Would anyone be so kind as to offer information to
> help make this thing work?" question, here are the other questions
> this situation raises.
>
> 1) How does oninit know to use /dev/prod_plogdbs (does it assume
> /dev/prod_ as a prefix)?
>
> 2) Will replacing 'plogdbs' with 'rootdbs' in my config file fix or
> completely destroy my database? I've been told by one source to just
> specify rootdbs as the location of the physical logs -- to paraphrase:
> "I always just put the physical logs on rootdbs". I don't know what
> that'll do to an existing database (being unfamiliar with Informix, I
> don't want to trash anything by "trying" stuff).
>
> 3) Can I destroy and create a new plogdbs? Or simply re-initialize
> the existing plogdbs?
>
> Any help would be appreciated!
>
> GW
The Big Potatoe <JJ@Nospam.Notthere.Co.Uk> wrote in message news:<3ECE943E.9040204@Nospam.Notthere.Co.Uk>...
> oncheck-pr and check for messages
I get the following (long):
shared memory not initialized for INFORMIXSERVER 'online_prod'
Validating INFORMIX-OnLine reserved pages - PAGE_PZERO
Identity INFORMIX-OnLine Copyright(C)
1986-1995 Infor
Database system state 0
Database system flags 0
Page Size 2048
Date/Time created 05/20/10 15:16:00
Version number of creator 4
Last modified time stamp 0
Validating INFORMIX-OnLine reserved pages - PAGE_CONFIG
Validating INFORMIX-OnLine reserved pages - PAGE_1CKPT & PAGE_2CKPT
Using check point page PAGE_2CKPT.
Time stamp of checkpoint 76
Time of checkpoint 05/20/10 15:18:47
Physical log begin address 10003f
Physical log size 50000
Physical log position at Ckpt 0
Logical log unique identifier 1
Logical log position at Ckpt 88
DBspace descriptor page 100005
Chunk descriptor page 100007
Mirror chunk descriptor page 100009
Log file number 1
Log file flags 3 Log file in use
Current log file
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 1
Physical location 10c38f
Log size 10000
Number pages used 1
Log file number 2
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 10ea9f
Log size 10000
Number pages used 0
Log file number 3
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 1111af
Log size 10000
Number pages used 0
Log file number 4
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 1138bf
Log size 10000
Number pages used 0
Log file number 5
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 115fcf
Log size 10000
Number pages used 0
Log file number 6
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 1186df
Log size 10000
Number pages used 0
Log file number 7
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 11adef
Log size 10000
Number pages used 0
Log file number 8
Log file flags 0
Time stamp 0
Date/Time file filled 12/31/69 17:00:00
Unique identifier 0
Physical location 11d4ff
Log size 10000
Number pages used 0
Validating INFORMIX-OnLine reserved pages - PAGE_1DBSP & PAGE_2DBSP
Using DBspace page PAGE_2DBSP.
DBspace number 1
Flags 2 DBspace uses mirror
chunks
First chunk 1
Number of chunks 1
Date/Time created 05/20/10 15:16:00
DBspace name rootdbs
DBspace owner informix
Validating INFORMIX-OnLine reserved pages - PAGE_1PCHUNK &
PAGE_2PCHUNK
Using primary chunk page PAGE_2PCHUNK.
Chunk number 1
Next chunk in DBspace 0
Chunk offset 0
Chunk size 250000
Number of free pages 119933
DBspace number 1
Overhead 0
Flags 40 Chunk is online
Chunk name length 21
Chunk path /dev/prod_pri_rootdbs
Validating INFORMIX-OnLine reserved pages - PAGE_1MCHUNK &
PAGE_2MCHUNK
Using mirror chunk page PAGE_2MCHUNK.
Chunk number 1
Next chunk in DBspace 0
Chunk offset 0
Chunk size 250000
Number of free pages 0
DBspace number 1
Overhead 0
Flags 50 Mirror chunk
Chunk is online
Chunk name length 21
Chunk path /dev/prod_sec_rootdbs
Validating INFORMIX-OnLine reserved pages - PAGE_1ARCH & PAGE_2ARCH
Using archive page PAGE_1ARCH.
No archives have occurred.
DR has not been initialized.
I don't see anything glaring -- I would expect the shared memory
segment to not be initialized since the database isn't up. Of course,
I'm not completely sure what I'd be looking for (I'm more of a Sybase
[gasp] guy.). OTOH, the date stamps of 12/31/69, for example, seem a
bit odd, but nothing that would cause the thing to not start up...
Thanks,
GW
>
> Cold potatoe
>
> 1.21 Giga Watts wrote:
> > When I start up a legacy 7.2 database using 'oninit -v' I get the
> > following error:
> > <successful startup messages snipped>
> > Checking location of physical log...FAILED
> > oninit: Fatal error in shared memory initialization
<original post snipped for brevity>
"1.21 Giga Watts" <giga_watts@yahoo.com> wrote in message
news:79fd1939.0305241114.39b594c3@posting.google.com...
> The Big Potatoe <JJ@Nospam.Notthere.Co.Uk> wrote in message
news:<3ECE943E.9040204@Nospam.Notthere.Co.Uk>...
> > oncheck-pr and check for messages
>
oncheck -cR
oncheck -ce
oncheck -cc
Oh dear, I think that someone did an oninit -i on this system.
See embedded :
1.21 Giga Watts wrote:
> The Big Potatoe <JJ@Nospam.Notthere.Co.Uk> wrote in message news:<3ECE943E.9040204@Nospam.Notthere.Co.Uk>...
>
>>oncheck-pr and check for messages
>
>
> I get the following (long):
> shared memory not initialized for INFORMIXSERVER 'online_prod'
>
> Validating INFORMIX-OnLine reserved pages - PAGE_PZERO
>
> Identity INFORMIX-OnLine Copyright(C)
> 1986-1995 Infor
> Database system state 0
> Database system flags 0
> Page Size 2048
> Date/Time created 05/20/10 15:16:00
> Version number of creator 4
> Last modified time stamp 0
>
> Validating INFORMIX-OnLine reserved pages - PAGE_CONFIG
>
Seems odd that there are no ONCONFIG entries
> Validating INFORMIX-OnLine reserved pages - PAGE_1CKPT & PAGE_2CKPT
> Using check point page PAGE_2CKPT.
>
> Time stamp of checkpoint 76
> Time of checkpoint 05/20/10 15:18:47
> Physical log begin address 10003f
> Physical log size 50000
> Physical log position at Ckpt 0
> Logical log unique identifier 1
> Logical log position at Ckpt 88
> DBspace descriptor page 100005
> Chunk descriptor page 100007
> Mirror chunk descriptor page 100009
>
Old product therefore the date is "wrong diddly wrong" - 05/20/10 should
be 05/20/03.
Physical log begin address is 10003f which is ... in chunk 1 .... i.e.
the rootdbs.
However, let's "look through the keyhole" at some of the timestamps here ...
> Log file number 1
> Log file flags 3 Log file in use
> Current log file
> Time stamp 0
> Date/Time file filled 12/31/69 17:00:00
> Unique identifier 1
> Physical location 10c38f
> Log size 10000
> Number pages used 1
>
Log 1 is the current log.
> Validating INFORMIX-OnLine reserved pages - PAGE_1DBSP & PAGE_2DBSP
> Using DBspace page PAGE_2DBSP.
>
> DBspace number 1
> Flags 2 DBspace uses mirror
> chunks
> First chunk 1
> Number of chunks 1
> Date/Time created 05/20/10 15:16:00
> DBspace name rootdbs
> DBspace owner informix
>
Rootdbs was created at 05/20/10 15:16:00 and the last checkpoint entry
was at
> Time of checkpoint 05/20/10 15:18:47
i.e. 2 minutes after the creation of the rootdbs.
Only one chunk and a mirror.
So there is not other dbspace, and yet the ONCONFIG thinks there should
be a physdbs.
oninit -i would explain the current state.
I would suggest you go through the online.log (i.e. MSGPATH) and look
for the entries between 15:15 and 15:20 on the 20th of May and see if
you can find "Complete disk initialised" anywhere there.
Then go to the cupboard with the backup tapes in.
Mashed matey.
> Validating INFORMIX-OnLine reserved pages - PAGE_1PCHUNK &
> PAGE_2PCHUNK
> Using primary chunk page PAGE_2PCHUNK.
>
> Chunk number 1
> Next chunk in DBspace 0
> Chunk offset 0
> Chunk size 250000
> Number of free pages 119933
> DBspace number 1
> Overhead 0
> Flags 40 Chunk is online
> Chunk name length 21
> Chunk path /dev/prod_pri_rootdbs
>
> Validating INFORMIX-OnLine reserved pages - PAGE_1MCHUNK &
> PAGE_2MCHUNK
> Using mirror chunk page PAGE_2MCHUNK.
>
> Chunk number 1
> Next chunk in DBspace 0
> Chunk offset 0
> Chunk size 250000
> Number of free pages 0
> DBspace number 1
> Overhead 0
> Flags 50 Mirror chunk
> Chunk is online
> Chunk name length 21
> Chunk path /dev/prod_sec_rootdbs
>
> Validating INFORMIX-OnLine reserved pages - PAGE_1ARCH & PAGE_2ARCH
> Using archive page PAGE_1ARCH.
>
> No archives have occurred.
>
>
> DR has not been initialized.
>
> I don't see anything glaring -- I would expect the shared memory
> segment to not be initialized since the database isn't up. Of course,
> I'm not completely sure what I'd be looking for (I'm more of a Sybase
> [gasp] guy.). OTOH, the date stamps of 12/31/69, for example, seem a
> bit odd, but nothing that would cause the thing to not start up...
>
> Thanks,
> GW
>
>
>>Cold potatoe
>>
>>1.21 Giga Watts wrote:
>>
>>>When I start up a legacy 7.2 database using 'oninit -v' I get the
>>>following error:
>>><successful startup messages snipped>
>>>Checking location of physical log...FAILED
>>>oninit: Fatal error in shared memory initialization
>>
> <original post snipped for brevity>