Instance Tag Problem
Posted: Mon Apr 02, 2007 11:46 am
Hi All,
We're having a problem. We tried to change our DS itag to bcb, by changing the uvconfig and running DSEsettag.sh script (DSEsettag -itag bcb) but without root access. We had some error messages when DSEsettag was run, but the uv -admin -regen was fine. When we restarted uv -admin -start, it failed.
So we changed back the uvconfig, and rerun DSEsettag.sh -force -itag reset. The script ran okay, and we ran uv -admin -regen also no problem. We restarted the server also no problem and the user can connect and all jobs can run.
But, when we tried uv -admin -info, these warnings keep coming:
WARNING: The engine instance tag control files are not synchronized.
WARNING: Shut down the engine, and run the 'DSEsettag.sh' script.
When we checked the shared memory segments (ipcs -m -a) we could see that the memory still pointing to bcb tag instead of ade tag:
IPC status from /dev/mem as of Tue Apr 3 01:43:39 WAUST 2007
T ID KEY MODE OWNER GROUP
Shared Memory:
m 28 0xbcbc7521 --rw-rw-rw- root dsadm
m 30 0xbcbf0000 --rw-rw-rw- root dsadm
m 31 0xbcbf0001 --rw-rw-rw- root dsadm
m 19922978 0xbcbbbfd4 --rw-rw-rw- william dsadm
m 73400355 0xbcbbfd3e --rw-rw-rw- william dsadm
m 2097188 0xbcbbea82 --rw-rw-rw- william dsadm
m 56623147 0xbcbb8fda --rw-rw-rw- william dsadm
m 7340076 0xaaaa1111 --rw-rw-rw- dsadm dsadm
m 33554483 0xffffffff D-rw------- prdinst1 dba
m 2097234 0xaaaa3333 --rw-rw-rw- dsadm dsadm
m 84934742 0xbcbbbe0e --rw-rw-rw- william dsadm
m 3145820 0xaaaa2222 --rw-rw-rw- dsadm dsadm
m 66060392 0xbcbbdd46 --rw-rw-rw- william dsadm
How could this happen? Is there a way to create the shared memory segment with 0xadexxxxx instead?
Did we miss any steps?
Thanks...
Endy
We're having a problem. We tried to change our DS itag to bcb, by changing the uvconfig and running DSEsettag.sh script (DSEsettag -itag bcb) but without root access. We had some error messages when DSEsettag was run, but the uv -admin -regen was fine. When we restarted uv -admin -start, it failed.
So we changed back the uvconfig, and rerun DSEsettag.sh -force -itag reset. The script ran okay, and we ran uv -admin -regen also no problem. We restarted the server also no problem and the user can connect and all jobs can run.
But, when we tried uv -admin -info, these warnings keep coming:
WARNING: The engine instance tag control files are not synchronized.
WARNING: Shut down the engine, and run the 'DSEsettag.sh' script.
When we checked the shared memory segments (ipcs -m -a) we could see that the memory still pointing to bcb tag instead of ade tag:
IPC status from /dev/mem as of Tue Apr 3 01:43:39 WAUST 2007
T ID KEY MODE OWNER GROUP
Shared Memory:
m 28 0xbcbc7521 --rw-rw-rw- root dsadm
m 30 0xbcbf0000 --rw-rw-rw- root dsadm
m 31 0xbcbf0001 --rw-rw-rw- root dsadm
m 19922978 0xbcbbbfd4 --rw-rw-rw- william dsadm
m 73400355 0xbcbbfd3e --rw-rw-rw- william dsadm
m 2097188 0xbcbbea82 --rw-rw-rw- william dsadm
m 56623147 0xbcbb8fda --rw-rw-rw- william dsadm
m 7340076 0xaaaa1111 --rw-rw-rw- dsadm dsadm
m 33554483 0xffffffff D-rw------- prdinst1 dba
m 2097234 0xaaaa3333 --rw-rw-rw- dsadm dsadm
m 84934742 0xbcbbbe0e --rw-rw-rw- william dsadm
m 3145820 0xaaaa2222 --rw-rw-rw- dsadm dsadm
m 66060392 0xbcbbdd46 --rw-rw-rw- william dsadm
How could this happen? Is there a way to create the shared memory segment with 0xadexxxxx instead?
Did we miss any steps?
Thanks...
Endy