Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Shared Memory Region on NT - HELP ME PLEASE!

8 posts in Windows NT Last posting was on 1999-12-07 11:31:23.0Z
Francisco Marquez Posted on 1999-11-29 22:44:04.0Z
From: "Francisco Marquez" <franciscoma@antar.com.mx>
Subject: Shared Memory Region on NT - HELP ME PLEASE!
Date: Mon, 29 Nov 1999 16:44:04 -0600
Lines: 27
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <#F7MBsrO$GA.186@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: na-155-3.na.avantel.net.mx 148.245.155.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2910
Article PK: 1090348

Hi all ,
I got this problem with an HP Net Server LH3. I have two 9GB disks mirrored
with a Net RAID card ( mirror by hardware ) so I only see one disk (C:) ,
1GB RAM . I installed Adaptive Server 11.9.2 and EBF 8671. The problem is
that I cannot increase the "total memory" configuration parameter beyond the
default (28 MB ) value. When I do that and reboot the ASE, the errorlog
shows these errors:

WARNING: shared memory segment is being held by another application
FATAL: shared memory region is being held at 30416896 bytes but 733005789
bytes are required
kbcreate: couldn't create kernel region.
kistartup: could not create shared memory

Prior to the instalation of the EBF 8671 , the error was "os_create_region:
MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping 'MYSERVER.krg'
failed." ,

I know ASE uses the file MYSERVER.krg to create the shared memory region, so
I suspect that the problem may recide on the mirrored disks.

Can anyone help me , please ?
---------------
Francisco Marquez


Tony Imbierski Posted on 1999-12-06 11:19:28.0Z
Message-ID: <384B9BC0.6FC4CAB@sybase.com>
Date: Mon, 06 Dec 1999 11:19:28 +0000
From: Tony Imbierski <tonyi@sybase.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
References: <#F7MBsrO$GA.186@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 59
NNTP-Posting-Host: chirico.sybase.com 158.76.102.96
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2883
Article PK: 1090320

Francisco,

The message is telling you exactly what the problem is:

>> WARNING: shared memory segment is being held by another application

This means you have some other program running that has mapped onto Sybase's
shared memory and is not letting it go. There is no easy way to tell what the
other program is. It could be monitor server, or it could be some 3rd party app.
System management tools are known to do this. Does your HP server come with any
such tools?

>> FATAL: shared memory region is being held at 30416896 bytes but 733005789

This means that not only is the shared memory being held, but it is being held
at a smaller size than we need. If it were held at the size we need, or larger
than we need, then we would be able to continue. However something has locked
the shared memory from the time it existed previously (before you increased
total memory) and we now need more. NT does not allow us to increase the size of
the shared memory while someone else is locking it.

>> kbcreate: couldn't create kernel region.
>> kistartup: could not create shared memory

These are just a consequence of the previous failures.


> Prior to the instalation of the EBF 8671 , the error was "os_create_region:
> MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping 'MYSERVER.krg'
> failed." ,
>

This has become such a common problem that we added the new messages to try and
make it clear what the problem is. I guess I need to write a short article on
this for the tech support site.


> I know ASE uses the file MYSERVER.krg to create the shared memory region, so
> I suspect that the problem may recide on the mirrored disks.
>

This is not correct. We create the .krg file for compatibility with unix
versions of ASE, but on NT we don't actually use it for anything. If you look at
the file you will see it is zero bytes. On NT the shared memory is mapped to the
page file.

The solution to this is to try and find out what other application is holding
the memory region, and close it. If you really can't find what is holding the
memory, then rebooting will clear the problem as (obviously) all applications
will be cycled. This *will* happen again, however, but it will only be a problem
when you increase the memory requirement.

cheers,

tonyi
ASE Engineering


Francisco Marquez Posted on 1999-12-07 00:49:34.0Z
From: "Francisco Marquez" <franciscoma@antar.com.mx>
References: <#F7MBsrO$GA.186@forums.sybase.com> <384B9BC0.6FC4CAB@sybase.com>
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
Date: Mon, 6 Dec 1999 18:49:34 -0600
Lines: 88
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <D9GD2yEQ$GA.88@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: na-155-3.na.avantel.net.mx 148.245.155.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2876
Article PK: 1090313

I stopped the mirroring on the server and now I can increase the "total
memory" parameter.

Thanks

Tony Imbierski <tonyi@sybase.com> wrote in message
news:384B9BC0.6FC4CAB@sybase.com...
> Francisco,
>
> The message is telling you exactly what the problem is:
>
> >> WARNING: shared memory segment is being held by another application
>
> This means you have some other program running that has mapped onto
Sybase's
> shared memory and is not letting it go. There is no easy way to tell what
the
> other program is. It could be monitor server, or it could be some 3rd
party app.
> System management tools are known to do this. Does your HP server come
with any
> such tools?
>
> >> FATAL: shared memory region is being held at 30416896 bytes but
733005789
>
> This means that not only is the shared memory being held, but it is being
held
> at a smaller size than we need. If it were held at the size we need, or
larger
> than we need, then we would be able to continue. However something has
locked
> the shared memory from the time it existed previously (before you
increased
> total memory) and we now need more. NT does not allow us to increase the
size of
> the shared memory while someone else is locking it.
>
> >> kbcreate: couldn't create kernel region.
> >> kistartup: could not create shared memory
>
> These are just a consequence of the previous failures.
>
>
> > Prior to the instalation of the EBF 8671 , the error was
"os_create_region:
> > MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping
'MYSERVER.krg'
> > failed." ,
> >
>
> This has become such a common problem that we added the new messages to
try and
> make it clear what the problem is. I guess I need to write a short article
on
> this for the tech support site.
>
>
> > I know ASE uses the file MYSERVER.krg to create the shared memory
region, so
> > I suspect that the problem may recide on the mirrored disks.
> >
>
> This is not correct. We create the .krg file for compatibility with unix
> versions of ASE, but on NT we don't actually use it for anything. If you
look at
> the file you will see it is zero bytes. On NT the shared memory is mapped
to the
> page file.
>
> The solution to this is to try and find out what other application is
holding
> the memory region, and close it. If you really can't find what is holding
the
> memory, then rebooting will clear the problem as (obviously) all
applications
> will be cycled. This *will* happen again, however, but it will only be a
problem
> when you increase the memory requirement.
>
> cheers,
>
> tonyi
> ASE Engineering
>
>


Tony Imbierski Posted on 1999-12-07 11:31:23.0Z
Message-ID: <384CF00B.BEEBE351@sybase.com>
Date: Tue, 07 Dec 1999 11:31:23 +0000
From: Tony Imbierski <tonyi@sybase.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
References: <#F7MBsrO$GA.186@forums.sybase.com> <384B9BC0.6FC4CAB@sybase.com> <D9GD2yEQ$GA.88@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 83
NNTP-Posting-Host: chirico.sybase.com 158.76.102.96
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2873
Article PK: 1090310

Francisco,

Did you reboot when you reconfigured the mirroring? If so then it is the reboot
that fixed your problem. There is no way that having the disk mirrored would
cause this, UNLESS the use of mirroring is associated with running some system
management app that maps onto the ASE shared memory. Even then it would be the
app causing the problem not the fact that the disk is mirrored.

cheers,
tonyi
ASE Engineering

Francisco Marquez wrote:

> I stopped the mirroring on the server and now I can increase the "total
> memory" parameter.
>
> Thanks
>
> Tony Imbierski <tonyi@sybase.com> wrote in message
> news:384B9BC0.6FC4CAB@sybase.com...
> > Francisco,
> >
> > The message is telling you exactly what the problem is:
> >
> > >> WARNING: shared memory segment is being held by another application
> >
> > This means you have some other program running that has mapped onto
> Sybase's
> > shared memory and is not letting it go. There is no easy way to tell what
> the
> > other program is. It could be monitor server, or it could be some 3rd
> party app.
> > System management tools are known to do this. Does your HP server come
> with any
> > such tools?
> >
> > >> FATAL: shared memory region is being held at 30416896 bytes but
> 733005789
> >
> > This means that not only is the shared memory being held, but it is being
> held
> > at a smaller size than we need. If it were held at the size we need, or
> larger
> > than we need, then we would be able to continue. However something has
> locked
> > the shared memory from the time it existed previously (before you
> increased
> > total memory) and we now need more. NT does not allow us to increase the
> size of
> > the shared memory while someone else is locking it.
> >
> > >> kbcreate: couldn't create kernel region.
> > >> kistartup: could not create shared memory
> >
> > These are just a consequence of the previous failures.
> >
> >
> > > Prior to the instalation of the EBF 8671 , the error was
> "os_create_region:
> > > MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping
> 'MYSERVER.krg'
> > > failed." ,
> > >
> >
> > This has become such a common problem that we added the new messages to
> try and
> > make it clear what the problem is. I guess I need to write a short article
> on
> > this for the tech support site.
> >
> >
> > > I know ASE uses the file MYSERVER.krg to create the shared memory
> region, so
> > > I suspect that the problem may recide on the mirrored disks.
> > >
> >
> > This is not correct. We create the .krg file for compatibility with unix
> > versions of ASE, but on NT we don't actually use it for anything. If you
> look at
> > the file you will see it is zero bytes. On NT the shared memory is mapped
> to the
> > page file.
> >
> > The solution to this is to try and find out what other application is
> holding
> > the memory region, and close it. If you really can't find what is holding
> the
> > memory, then rebooting will clear the problem as (obviously) all
> applications
> > will be cycled. This *will* happen again, however, but it will only be a
> problem
> > when you increase the memory requirement.
> >
> > cheers,
> >
> > tonyi
> > ASE Engineering
> >
> >


AnaMaria Stirbet Posted on 1999-12-03 15:39:03.0Z
Message-ID: <3847E417.1F5241D1@sybase.com.no.spam>
Date: Fri, 03 Dec 1999 10:39:03 -0500
From: AnaMaria Stirbet <astirbet@sybase.com.no.spam>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.5 [en]C-CCK-MCD (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
References: <#F7MBsrO$GA.186@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 35
NNTP-Posting-Host: 172.31.140.205
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2899
Article PK: 1090334

Hola Francisco,

First thing you want to do is to reboot the machine before the attempt to start
the server with more memory. That's not to say that you will do this from now
on. This is just to confirm the problem is what I suspect.

AnaMaria Stirbet
Sybase TS

Francisco Marquez wrote:

> Hi all ,
> I got this problem with an HP Net Server LH3. I have two 9GB disks mirrored
> with a Net RAID card ( mirror by hardware ) so I only see one disk (C:) ,
> 1GB RAM . I installed Adaptive Server 11.9.2 and EBF 8671. The problem is
> that I cannot increase the "total memory" configuration parameter beyond the
> default (28 MB ) value. When I do that and reboot the ASE, the errorlog
> shows these errors:
>
> WARNING: shared memory segment is being held by another application
> FATAL: shared memory region is being held at 30416896 bytes but 733005789
> bytes are required
> kbcreate: couldn't create kernel region.
> kistartup: could not create shared memory
>
> Prior to the instalation of the EBF 8671 , the error was "os_create_region:
> MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping 'MYSERVER.krg'
> failed." ,
>
> I know ASE uses the file MYSERVER.krg to create the shared memory region, so
> I suspect that the problem may recide on the mirrored disks.
>
> Can anyone help me , please ?
> ---------------
> Francisco Marquez


Arun Kamat Posted on 1999-11-30 05:58:36.0Z
Message-ID: <3843678C.DE47DB1@tkg.att.ne.jp>
Date: Tue, 30 Nov 1999 14:58:36 +0900
From: Arun Kamat <annarun@tkg.att.ne.jp>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
References: <#F7MBsrO$GA.186@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 37
NNTP-Posting-Host: 44.pool22.tokyo.att.ne.jp 165.76.227.59
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2908
Article PK: 1090340


Francisco Marquez wrote:

> Hi all ,
> I got this problem with an HP Net Server LH3. I have two 9GB disks mirrored
> with a Net RAID card ( mirror by hardware ) so I only see one disk (C:) ,
> 1GB RAM . I installed Adaptive Server 11.9.2 and EBF 8671. The problem is
> that I cannot increase the "total memory" configuration parameter beyond the
> default (28 MB ) value. When I do that and reboot the ASE, the errorlog
> shows these errors:
>
> WARNING: shared memory segment is being held by another application
> FATAL: shared memory region is being held at 30416896 bytes but 733005789

In MB these figures are 29 MB and 699MB respectively. Did you increase total mem
to 699 MB and try to reboot? Does the NT server have this much physical mem? I
suspect 'total mem' is > physical mem.

> bytes are required
> kbcreate: couldn't create kernel region.
> kistartup: could not create shared memory
>
> Prior to the instalation of the EBF 8671 , the error was "os_create_region:
> MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping 'MYSERVER.krg'
> failed." ,
>
> I know ASE uses the file MYSERVER.krg to create the shared memory region, so
> I suspect that the problem may recide on the mirrored disks.

Do you have monitor/historical server running on the server machine? If yes then
these also need to be rebooted when you reboot the ASE server. I dont think
setting up RAID 1 has got anything with above problems.

rgds,
arun


Francisco Marquez Posted on 1999-11-30 15:09:19.0Z
From: "Francisco Marquez" <franciscoma@antar.com.mx>
References: <#F7MBsrO$GA.186@forums.sybase.com> <3843678C.DE47DB1@tkg.att.ne.jp>
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
Date: Tue, 30 Nov 1999 09:09:19 -0600
Lines: 60
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <RZZ9lS0O$GA.186@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: na-155-3.na.avantel.net.mx 148.245.155.3
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2907
Article PK: 1090344

Server has 1GB RAM (Historical and Monitor servers are stopped), the numbers
shown in errorlog represents one of the many attempts that I have done to
increase the memory, but the same happens if you try to increase the "total
memory" parameter just 1MB above the default.

Thanks
-------------------
Francisco Marquez

Arun Kamat <annarun@tkg.att.ne.jp> wrote in message
news:3843678C.DE47DB1@tkg.att.ne.jp...
> Francisco Marquez wrote:
>
> > Hi all ,
> > I got this problem with an HP Net Server LH3. I have two 9GB disks
mirrored
> > with a Net RAID card ( mirror by hardware ) so I only see one disk (C:)
,
> > 1GB RAM . I installed Adaptive Server 11.9.2 and EBF 8671. The problem
is
> > that I cannot increase the "total memory" configuration parameter beyond
the
> > default (28 MB ) value. When I do that and reboot the ASE, the errorlog
> > shows these errors:
> >
> > WARNING: shared memory segment is being held by another application
> > FATAL: shared memory region is being held at 30416896 bytes but
733005789
>
> In MB these figures are 29 MB and 699MB respectively. Did you increase
total mem
> to 699 MB and try to reboot? Does the NT server have this much physical
mem? I
> suspect 'total mem' is > physical mem.
>
> > bytes are required
> > kbcreate: couldn't create kernel region.
> > kistartup: could not create shared memory
> >
> > Prior to the instalation of the EBF 8671 , the error was
"os_create_region:
> > MapViewOfFile for file 'C:\Sybase\MYSERVER.krg' on mapping
'MYSERVER.krg'
> > failed." ,
> >
> > I know ASE uses the file MYSERVER.krg to create the shared memory
region, so
> > I suspect that the problem may recide on the mirrored disks.
>
> Do you have monitor/historical server running on the server machine? If
yes then
> these also need to be rebooted when you reboot the ASE server. I dont
think
> setting up RAID 1 has got anything with above problems.
>
> rgds,
> arun
>


Arun Kamat Posted on 1999-12-01 15:59:12.0Z
Message-ID: <384545D0.F3422CC@tkg.att.ne.jp>
Date: Thu, 02 Dec 1999 00:59:12 +0900
From: Arun Kamat <annarun@tkg.att.ne.jp>
X-Mailer: Mozilla 4.05 [en] (Win95; I)
MIME-Version: 1.0
Subject: Re: Shared Memory Region on NT - HELP ME PLEASE!
References: <#F7MBsrO$GA.186@forums.sybase.com> <3843678C.DE47DB1@tkg.att.ne.jp> <RZZ9lS0O$GA.186@forums.sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 20
NNTP-Posting-Host: 71.pool22.tokyo.att.ne.jp 165.76.227.86
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:2903
Article PK: 1090339

1) The place (usually $SYBASE) where shared mem segment file is created should
have at least 18MB space.
2) You need to login as NT server administrator to start up ASE
3) Possibly ASE is not able to grab that much amount of shared mem. So you may
shutdown all ASE, monitor etc servers, delete any .krg files and reboot the NT
server. First thing you do is start up ASE.

regards,
Arun

Francisco Marquez wrote:

> Server has 1GB RAM (Historical and Monitor servers are stopped), the numbers
> shown in errorlog represents one of the many attempts that I have done to
> increase the memory, but the same happens if you try to increase the "total
> memory" parameter just 1MB above the default.
>
> Thanks
> -------------------
> Francisco Marquez