Hi,

I have an odd situation : the dataserver is running but there is
apparently no shared memory attached.

[sybase|srx-amarante] /home/sybase
Adaptive Server Enterprise/12.0.0.6/P/EBF 10628 ESD 1/Sun_svr4/OS
5.7/1918/64bit/FBO/Fri Oct 18 14:36:20 2002
Sybase Adaptive Server Enterprise Diagnostic Interface
Confidential property of Sybase, Inc.
Copyright 1987, 2002
Sybase, Inc. All rights reserved.
Unpublished rights reserved under U.S. copyright laws.

This software contains confidential and trade secret information of Sybase,
Inc. Use, duplication or disclosure of the software and documentation by
the U.S. Government is subject to restrictions set forth in a license
agreement between the Government and Sybase, Inc. or other written
agreement specifying the Government's rights to use the software and any
applicable FAR provisions, for example, FAR 52.227-19.
Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA

WARNING: For use by authorized personnel only.
If you are not an employee of Sybase, Inc., or
have not been authorized by a qualified employee
of Sybase, Inc., please terminate this program now.

Server dsr_amarante1 not accessable, status: Shared memory not found


Name Key Id Status
-----------------------------------------------------------------
dsr_amarante2 0x9a022147 2 Available
dsr_amarante1 0x9a02212c 0 Shared memory not found

T ID KEY MODE OWNER GROUP CREATOR CGROUP
NATTCH SEGSZ CPID LPID ATIME DTIME CTIME ISMATTCH
Shared Memory:
m 2 0x9a022147 --rw------- sybase sybase sybase sybase
2 1059979264 5544 5635 11:44:02 11:44:01 11:43:17 0
m 103 0x9a02243e --rw------- sybase sybase sybase sybase
1 224583680 7594 7594 11:51:00 no-entry 11:50:59 1



[sybase|srx-amarante] /srx-amarante/product/sybase/v12_0/ASE-12_0/install
sybase 3486 3483 0 19:13:33 pts/7 0:04
/srx-amarante/product/sybase/v12_5/ASE-12_5/bin/backupserver
-Sbsr_amarante3 -e
sybase 5213 5209 0 Nov 17 ? 317:39
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/dataserver -sdsr_amarante1
-d/d
sybase 5304 5300 0 Nov 17 ? 0:43
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/backupserver
-Sbsr_amarante1 -e
sybase 5266 5213 1 Nov 17 ? 272:02
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/dataserver
-ONLINE:1,0,0xffffff
sybase 5544 5540 0 Nov 17 ? 131:04
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/dataserver -sdsr_amarante2
-d/d
sybase 5720 5716 0 Nov 17 ? 0:05
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/backupserver
-Sbsr_amarante2 -e
sybase 7594 7590 0 Nov 17 ? 1489:54
/srx-amarante/product/sybase/v12_5/ASE-12_5/bin/dataserver -sdsr_amarante3
-d/d
sybase 5635 5544 0 Nov 17 ? 226:31
/srx-amarante/product/sybase/v12_0/ASE-12_0/bin/dataserver
-ONLINE:1,0,0xffffff


Any idea ?

Laurent,

Your conditions are very similar to CR#256710 "Shared memory
disappearing" when backupserver removes shared memory ID 0. It looks
like that dsr_amarante1 got ID 0 when it started (that's confirmed by
the "cat" output), then the backupserver was started which removed the
shared memory segment with this ID. The dataserver will keep running
but you won't be able to use any tool to attach to it since the
segment is not present. The other consequence might be a core dump
during shutdown (on Solaris 7 and 8 but not on 2.6). There are
several workarounds described in the document at:
http://www.sybase.com/detail?id=1016173

Mikhail

news (AT) nospammm (DOT) naitika.com (Laurent P.) wrote in message news:<3fc46e0c$0$2357$626a54ce (AT) news (DOT) free.fr>...

mikhail wrote:


Thanks Mikhail for your answer. The issue should have been solved above
12.0.0.4 (I'm using 12.0.0.6) . A case has been opened @ Sybase.