mystery server in HDR
On IDS 10.00.FC5/AIX 5.3 with HACMP, a restarted HDR secondary logged that it was trying to connect to a non-existent primary (ol_tmsdb02) instead of the real primary (ol_tmsdb01), and the name couldn't be found anywhere in configuration or system tables. Suggestions: check DRNAME in 'oncheck -pr' (PAGE_CONFIG section), which showed the correct name; Madison Pruet said the stale name lives in the archive reserved pages not shown by oncheck, and can be dumped with dd/od (adjusting page size and chunk offset for AIX); others suggested the HACMP setup may have overwritten the instance via shared disks, or a ROOTDBS path mismatch after a dd copy. The poster had not reported results, so no resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello all,
upon bouncing our secondary server, the log shows it is trying to
connect to a primary server that does not exist!
we have searched the secondary server itself, system tables, etc and
cannot find a reference to this mystery server
we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
from the log of the secondary server :
23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
23:41:45 DR: Cannot connect to primary server
the primary server name is ol_tmsdb01 - which is a failover cluster
using HACMP
Thanks for any insight.
Tom
tomcaml@yahoo.com wrote:
> Hello all,
>
> upon bouncing our secondary server, the log shows it is trying to
> connect to a primary server that does not exist!
> we have searched the secondary server itself, system tables, etc and
> cannot find a reference to this mystery server
>
>
> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
>
>
>
> from the log of the secondary server :
> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> 23:41:45 DR: Cannot connect to primary server
It's in the reserved pages. do oncheck -pr
>
>
> the primary server name is ol_tmsdb01 - which is a failover cluster
> using HACMP
>
>
> Thanks for any insight.
>
> Tom
>
i did an oncheck -pr and wrote it to a file for both primary and
secondary.
it could not find the string "ol_tmsdb02"
Madison Pruet wrote:
> tomcaml@yahoo.com wrote:
> > Hello all,
> >
> > upon bouncing our secondary server, the log shows it is trying to
> > connect to a primary server that does not exist!
> > we have searched the secondary server itself, system tables, etc and
> > cannot find a reference to this mystery server
> >
> >
> > we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> >
> >
> >
> > from the log of the secondary server :
> > 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> > 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> > 23:41:45 DR: Cannot connect to primary server>
> It's in the reserved pages. do oncheck -pr
>
>
> >
> >
> > the primary server name is ol_tmsdb01 - which is a failover cluster
> > using HACMP
> >
> >
> > Thanks for any insight.
> >
> > Tom
> >
Hi,
On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
instance can be found at the DRNAME parameter under the section
"Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
the Secondary.
RoB
tomcaml@yahoo.com wrote:
> i did an oncheck -pr and wrote it to a file for both primary and
> secondary.
> it could not find the string "ol_tmsdb02"
>
>
>
> Madison Pruet wrote:
> > tomcaml@yahoo.com wrote:
> > > Hello all,
> > >
> > > upon bouncing our secondary server, the log shows it is trying to
> > > connect to a primary server that does not exist!
> > > we have searched the secondary server itself, system tables, etc and
> > > cannot find a reference to this mystery server
> > >
> > >
> > > we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> > >
> > >
> > >
> > > from the log of the secondary server :
> > > 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> > > 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> > > 23:41:45 DR: Cannot connect to primary server> >
> > It's in the reserved pages. do oncheck -pr
> >
> >
> > >
> > >
> > > the primary server name is ol_tmsdb01 - which is a failover cluster
> > > using HACMP
> > >
> > >
> > > Thanks for any insight.
> > >
> > > Tom
> > >
yep - that section lists the correct server name as being the primary,
ol_tmsdb01
we have searched everywhere we can look to find the name "ol_tmsdb02"
but cannot find it.
i don't know much about "profiles" for the servers that sysadmins
control ( we have changed the profiles several times for changes in
resource usage), if it could possibly be hidden there or possibly in
some networking place.
Thank you.
Tom
RoB wrote:
> Hi,
>
> On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
> instance can be found at the DRNAME parameter under the section
> "Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
> the Secondary.
>
> RoB
>
> tomcaml@yahoo.com wrote:
> > i did an oncheck -pr and wrote it to a file for both primary and
> > secondary.
> > it could not find the string "ol_tmsdb02"
> >
> >
> >
> > Madison Pruet wrote:
> > > tomcaml@yahoo.com wrote:
> > > > Hello all,
> > > >
> > > > upon bouncing our secondary server, the log shows it is trying to
> > > > connect to a primary server that does not exist!
> > > > we have searched the secondary server itself, system tables, etc and
> > > > cannot find a reference to this mystery server
> > > >
> > > >
> > > > we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> > > >
> > > >
> > > >
> > > > from the log of the secondary server :
> > > > 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> > > > 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> > > > 23:41:45 DR: Cannot connect to primary server> > >
> > > It's in the reserved pages. do oncheck -pr
> > >
> > >
> > > >
> > > >
> > > > the primary server name is ol_tmsdb01 - which is a failover cluster
> > > > using HACMP
> > > >
> > > >
> > > > Thanks for any insight.
> > > >
> > > > Tom
> > > >
tomcaml@yahoo.com wrote:
> yep - that section lists the correct server name as being the primary,
> ol_tmsdb01
>
> we have searched everywhere we can look to find the name "ol_tmsdb02"
> but cannot find it.
It's actually in the archive reserved pages. Unfortunately it seems that
the information is not displayed in oncheck -pr.
If you really want to see where it is coming from, you can use the "dd"
and "od" utilities to dump the raw page. In my case (Linux) the command
would be
dd if=rootchk bs=2048 skip=10 count=2 | od -c
I have this instance pointing to a server called 'serv2' The output is
0000000 \\n \\0 \\0 \\0 001 \\0 266 262 002 \\0 \\0 030 344 \\0 020 \\a
0000020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 } 213 257 E 222 262 001 \\0
0000040 004 \\0 \\0 \\0 030 300 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
0000060 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
0000100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
0000120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
0000140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
0000160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
*
0003760 \\0 \\0 \\0 \\0 H \\0 234 \\0 030 \\0 0 \\0 274 262 001 \\0
0004000 \\v \\0 \\0 \\0 001 \\0 003 262 002 \\0 \\0 030 344 \\0 020 \\a
0004020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
*
0004100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
0004120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
0004140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
0004160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>
> i don't know much about "profiles" for the servers that sysadmins
> control ( we have changed the profiles several times for changes in
> resource usage), if it could possibly be hidden there or possibly in
> some networking place.
>
> Thank you.
>
> Tom
>
>
>
> RoB wrote:
>> Hi,
>>
>> On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
>> instance can be found at the DRNAME parameter under the section
>> "Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
>> the Secondary.
>>
>> RoB
>>
>> tomcaml@yahoo.com wrote:
>>> i did an oncheck -pr and wrote it to a file for both primary and
>>> secondary.
>>> it could not find the string "ol_tmsdb02"
>>>
>>>
>>>
>>> Madison Pruet wrote:
>>>> tomcaml@yahoo.com wrote:
>>>>> Hello all,
>>>>>
>>>>> upon bouncing our secondary server, the log shows it is trying to
>>>>> connect to a primary server that does not exist!
>>>>> we have searched the secondary server itself, system tables, etc and
>>>>> cannot find a reference to this mystery server
>>>>>
>>>>>
>>>>> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
>>>>>
>>>>>
>>>>>
>>>>> from the log of the secondary server :
>>>>> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
>>>>> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
>>>>> 23:41:45 DR: Cannot connect to primary server>>>> It's in the reserved pages. do oncheck -pr
>>>>
>>>>
>>>>>
>>>>> the primary server name is ol_tmsdb01 - which is a failover cluster
>>>>> using HACMP
>>>>>
>>>>>
>>>>> Thanks for any insight.
>>>>>
>>>>> Tom
>>>>>
>
tomcaml@yahoo.com wrote:
> Hello all,
>
> upon bouncing our secondary server, the log shows it is trying to
> connect to a primary server that does not exist!
> we have searched the secondary server itself, system tables, etc and
> cannot find a reference to this mystery server
>
>
> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
>
>
>
> from the log of the secondary server :
> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> 23:41:45 DR: Cannot connect to primary server>
>
> the primary server name is ol_tmsdb01 - which is a failover cluster
> using HACMP
>
>
> Thanks for any insight.
>
> Tom
hi,
check with your hacmp installer, may be he had connected the 2 servers
on the same group of disk and
rewrite the first instance with the second when hacmp switch from one
server to another. i had similar
problem.
tomcaml@yahoo.com wrote:
> yep - that section lists the correct server name as being the primary,
> ol_tmsdb01
>
> we have searched everywhere we can look to find the name "ol_tmsdb02"
> but cannot find it.
>
> i don't know much about "profiles" for the servers that sysadmins
> control ( we have changed the profiles several times for changes in
> resource usage), if it could possibly be hidden there or possibly in
> some networking place.
Is it possible that the device/file specified in the ONCONFIG file for
ROOTDBS is not the same as the path of the first chunk on the chunk reserved
page on disk in that file? This can happen if you try to move the root
chunk by dd'ing the contents of the old one to the new one and then just
changing the ROOTDBS in the onconfig file. Use Madison's dd & od method on
pages 5 & 6 (the chunk table pages - one is the current the other the
previous or backup copy - oncheck -pr will tell you which is current) to see
if the path of the first chunk is the same as the path in ROOTDBS (which is
presumably the one you pointed dd at).
Art S. Kagel
thanks vomaringo
call you provide any other details?
thank you
Tom
vomaringo@yahoo.com wrote:
> tomcaml@yahoo.com wrote:
> > Hello all,
> >
> > upon bouncing our secondary server, the log shows it is trying to
> > connect to a primary server that does not exist!
> > we have searched the secondary server itself, system tables, etc and
> > cannot find a reference to this mystery server
> >
> >
> > we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> >
> >
> >
> > from the log of the secondary server :
> > 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> > 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> > 23:41:45 DR: Cannot connect to primary server> >
> >
> > the primary server name is ol_tmsdb01 - which is a failover cluster
> > using HACMP
> >
> >
> > Thanks for any insight.
> >
> > Tom
>
> hi,
> check with your hacmp installer, may be he had connected the 2 servers
> on the same group of disk and
> rewrite the first instance with the second when hacmp switch from one
> server to another. i had similar
> problem.
we tried Madison -
we ran this command :dd if=/home/informix/chunk_links/rootdbs bs=2048
skip=10 count=20 | od -c
and this was our output - ?
0000000 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
\\0
*
0120000
20+0 records in.
20+0 records out.
Thanks.
Madison Pruet wrote:
> tomcaml@yahoo.com wrote:
> > yep - that section lists the correct server name as being the primary,
> > ol_tmsdb01
> >
> > we have searched everywhere we can look to find the name "ol_tmsdb02"
> > but cannot find it.
>
> It's actually in the archive reserved pages. Unfortunately it seems that
> the information is not displayed in oncheck -pr.
>
> If you really want to see where it is coming from, you can use the "dd"
> and "od" utilities to dump the raw page. In my case (Linux) the command
> would be
>
> dd if=rootchk bs=2048 skip=10 count=2 | od -c
>
> I have this instance pointing to a server called 'serv2' The output is
>
> 0000000 \\n \\0 \\0 \\0 001 \\0 266 262 002 \\0 \\0 030 344 \\0 020 \\a
> 0000020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 } 213 257 E 222 262 001 \\0
> 0000040 004 \\0 \\0 \\0 030 300 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> 0000060 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> 0000100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
> 0000120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
> 0000140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> 0000160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> *
> 0003760 \\0 \\0 \\0 \\0 H \\0 234 \\0 030 \\0 0 \\0 274 262 001 \\0
> 0004000 \\v \\0 \\0 \\0 001 \\0 003 262 002 \\0 \\0 030 344 \\0 020 \\a
> 0004020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> *
> 0004100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
> 0004120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
> 0004140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> 0004160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>
>
> >
> > i don't know much about "profiles" for the servers that sysadmins
> > control ( we have changed the profiles several times for changes in
> > resource usage), if it could possibly be hidden there or possibly in
> > some networking place.
> >
> > Thank you.
> >
> > Tom
> >
> >
> >
> > RoB wrote:
> >> Hi,
> >>
> >> On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
> >> instance can be found at the DRNAME parameter under the section
> >> "Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
> >> the Secondary.
> >>
> >> RoB
> >>
> >> tomcaml@yahoo.com wrote:
> >>> i did an oncheck -pr and wrote it to a file for both primary and
> >>> secondary.
> >>> it could not find the string "ol_tmsdb02"
> >>>
> >>>
> >>>
> >>> Madison Pruet wrote:
> >>>> tomcaml@yahoo.com wrote:
> >>>>> Hello all,
> >>>>>
> >>>>> upon bouncing our secondary server, the log shows it is trying to
> >>>>> connect to a primary server that does not exist!
> >>>>> we have searched the secondary server itself, system tables, etc and
> >>>>> cannot find a reference to this mystery server
> >>>>>
> >>>>>
> >>>>> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> >>>>>
> >>>>>
> >>>>>
> >>>>> from the log of the secondary server :
> >>>>> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> >>>>> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> >>>>> 23:41:45 DR: Cannot connect to primary server> >>>> It's in the reserved pages. do oncheck -pr
> >>>>
> >>>>
> >>>>>
> >>>>> the primary server name is ol_tmsdb01 - which is a failover cluster
> >>>>> using HACMP
> >>>>>
> >>>>>
> >>>>> Thanks for any insight.
> >>>>>
> >>>>> Tom
> >>>>>
> >
tomcaml@yahoo.com wrote:
> we tried Madison -
>
> we ran this command :dd if=/home/informix/chunk_links/rootdbs bs=2048
> skip=10 count=20 | od -c
>
> and this was our output - ?
1) Does AIX use 2K pages? If not, then the bs must be changed to the
correct size.
Also, you may need to use a different offset based on the offset in the
chunk.
M.P.
>
> 0000000 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> \\0
> *
> 0120000
> 20+0 records in.
> 20+0 records out.
>
>
> Thanks.
>
>
>
>
>
>
>
> Madison Pruet wrote:
>> tomcaml@yahoo.com wrote:
>>> yep - that section lists the correct server name as being the primary,
>>> ol_tmsdb01
>>>
>>> we have searched everywhere we can look to find the name "ol_tmsdb02"
>>> but cannot find it.
>> It's actually in the archive reserved pages. Unfortunately it seems that
>> the information is not displayed in oncheck -pr.
>>
>> If you really want to see where it is coming from, you can use the "dd"
>> and "od" utilities to dump the raw page. In my case (Linux) the command
>> would be
>>
>> dd if=rootchk bs=2048 skip=10 count=2 | od -c
>>
>> I have this instance pointing to a server called 'serv2' The output is
>>
>> 0000000 \\n \\0 \\0 \\0 001 \\0 266 262 002 \\0 \\0 030 344 \\0 020 \\a
>> 0000020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 } 213 257 E 222 262 001 \\0
>> 0000040 004 \\0 \\0 \\0 030 300 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> 0000060 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> 0000100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
>> 0000120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
>> 0000140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> 0000160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> *
>> 0003760 \\0 \\0 \\0 \\0 H \\0 234 \\0 030 \\0 0 \\0 274 262 001 \\0
>> 0004000 \\v \\0 \\0 \\0 001 \\0 003 262 002 \\0 \\0 030 344 \\0 020 \\a
>> 0004020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> *
>> 0004100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
>> 0004120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
>> 0004140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>> 0004160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
>>
>>
>>> i don't know much about "profiles" for the servers that sysadmins
>>> control ( we have changed the profiles several times for changes in
>>> resource usage), if it could possibly be hidden there or possibly in
>>> some networking place.
>>>
>>> Thank you.
>>>
>>> Tom
>>>
>>>
>>>
>>> RoB wrote:
>>>> Hi,
>>>>
>>>> On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
>>>> instance can be found at the DRNAME parameter under the section
>>>> "Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
>>>> the Secondary.
>>>>
>>>> RoB
>>>>
>>>> tomcaml@yahoo.com wrote:
>>>>> i did an oncheck -pr and wrote it to a file for both primary and
>>>>> secondary.
>>>>> it could not find the string "ol_tmsdb02"
>>>>>
>>>>>
>>>>>
>>>>> Madison Pruet wrote:
>>>>>> tomcaml@yahoo.com wrote:
>>>>>>> Hello all,
>>>>>>>
>>>>>>> upon bouncing our secondary server, the log shows it is trying to
>>>>>>> connect to a primary server that does not exist!
>>>>>>> we have searched the secondary server itself, system tables, etc and
>>>>>>> cannot find a reference to this mystery server
>>>>>>>
>>>>>>>
>>>>>>> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> from the log of the secondary server :
>>>>>>> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
>>>>>>> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
>>>>>>> 23:41:45 DR: Cannot connect to primary server>>>>>> It's in the reserved pages. do oncheck -pr
>>>>>>
>>>>>>
>>>>>>> the primary server name is ol_tmsdb01 - which is a failover cluster
>>>>>>> using HACMP
>>>>>>>
>>>>>>>
>>>>>>> Thanks for any insight.
>>>>>>>
>>>>>>> Tom
>>>>>>>
>
Thanks - we will try that -
Madison Pruet wrote:
> tomcaml@yahoo.com wrote:
> > we tried Madison -
> >
> > we ran this command :dd if=/home/informix/chunk_links/rootdbs bs=2048
> > skip=10 count=20 | od -c
> >
> > and this was our output - ?
>
> 1) Does AIX use 2K pages? If not, then the bs must be changed to the
> correct size.
>
> Also, you may need to use a different offset based on the offset in the
> chunk.
>
> M.P.
>
> >
> > 0000000 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> > \\0
> > *
> > 0120000
> > 20+0 records in.
> > 20+0 records out.
> >
> >
> > Thanks.
> >
> >
> >
> >
> >
> >
> >
> > Madison Pruet wrote:
> >> tomcaml@yahoo.com wrote:
> >>> yep - that section lists the correct server name as being the primary,
> >>> ol_tmsdb01
> >>>
> >>> we have searched everywhere we can look to find the name "ol_tmsdb02"
> >>> but cannot find it.
> >> It's actually in the archive reserved pages. Unfortunately it seems that
> >> the information is not displayed in oncheck -pr.
> >>
> >> If you really want to see where it is coming from, you can use the "dd"
> >> and "od" utilities to dump the raw page. In my case (Linux) the command
> >> would be
> >>
> >> dd if=rootchk bs=2048 skip=10 count=2 | od -c
> >>
> >> I have this instance pointing to a server called 'serv2' The output is
> >>
> >> 0000000 \\n \\0 \\0 \\0 001 \\0 266 262 002 \\0 \\0 030 344 \\0 020 \\a
> >> 0000020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 } 213 257 E 222 262 001 \\0
> >> 0000040 004 \\0 \\0 \\0 030 300 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> 0000060 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> 0000100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
> >> 0000120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
> >> 0000140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> 0000160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> *
> >> 0003760 \\0 \\0 \\0 \\0 H \\0 234 \\0 030 \\0 0 \\0 274 262 001 \\0
> >> 0004000 \\v \\0 \\0 \\0 001 \\0 003 262 002 \\0 \\0 030 344 \\0 020 \\a
> >> 0004020 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> *
> >> 0004100 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 377 377 377 377 377 377 377 377
> >> 0004120 377 377 377 377 377 377 377 377 001 \\0 \\0 \\0 002 \\0 \\0 \\0
> >> 0004140 s e r v 2 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >> 0004160 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0 \\0
> >>
> >>
> >>> i don't know much about "profiles" for the servers that sysadmins
> >>> control ( we have changed the profiles several times for changes in
> >>> resource usage), if it could possibly be hidden there or possibly in
> >>> some networking place.
> >>>
> >>> Thank you.
> >>>
> >>> Tom
> >>>
> >>>
> >>>
> >>> RoB wrote:
> >>>> Hi,
> >>>>
> >>>> On IDS 10.00.FC5/AIX 5.3 the servername of the other participating
> >>>> instance can be found at the DRNAME parameter under the section
> >>>> "Validating PAGE_CONFIG..." from oncheck -pr on both the Primary and
> >>>> the Secondary.
> >>>>
> >>>> RoB
> >>>>
> >>>> tomcaml@yahoo.com wrote:
> >>>>> i did an oncheck -pr and wrote it to a file for both primary and
> >>>>> secondary.
> >>>>> it could not find the string "ol_tmsdb02"
> >>>>>
> >>>>>
> >>>>>
> >>>>> Madison Pruet wrote:
> >>>>>> tomcaml@yahoo.com wrote:
> >>>>>>> Hello all,
> >>>>>>>
> >>>>>>> upon bouncing our secondary server, the log shows it is trying to
> >>>>>>> connect to a primary server that does not exist!
> >>>>>>> we have searched the secondary server itself, system tables, etc and
> >>>>>>> cannot find a reference to this mystery server
> >>>>>>>
> >>>>>>>
> >>>>>>> we are on ids 10 fc5 on AIX 5.3 using LPARs on a i595 machine
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> from the log of the secondary server :
> >>>>>>> 23:41:45 DR: new type = secondary, primary server name = ol_tmsdb02
> >>>>>>> 23:41:45 DR: Trying to connect to primary server = ol_tmsdb02
> >>>>>>> 23:41:45 DR: Cannot connect to primary server> >>>>>> It's in the reserved pages. do oncheck -pr
> >>>>>>
> >>>>>>
> >>>>>>> the primary server name is ol_tmsdb01 - which is a failover cluster
> >>>>>>> using HACMP
> >>>>>>>
> >>>>>>>
> >>>>>>> Thanks for any insight.
> >>>>>>>
> >>>>>>> Tom
> >>>>>>>
> >