Operating System - HP-UX
1748060 Members
5365 Online
108758 Solutions
New Discussion

Re: Unable to start Sybase after extending /va

 
sysad4
Occasional Contributor

Unable to start Sybase after extending /va

Hi Guru's,

 

I've been experiencing some issues starting up Sybase in HP-UX 11i v3 Superdome server. It has been working fine until I extended my /var from 5GB to 8GB. Since I didn't have OnlineJFS to do it, I went into single user mode to extend my /var.

I was able to extend it successfully and booted up my machine to normal mode. There are two noticeable weird things occured after bootup.

 

1. Most of the sybase owned related files changed its permission from "sybase:sybase" to "sybase:106"

2. I can no longer start-up my Sybase database and have the following error:

   

     $ startserver -f RUN_CCBDB_SDS
   $ 00:0000:00000:00000:2012/05/25 10:56:44.22 kernel  SySAM: Using licenses from:

     /home/appl/sybase/server1570    

     /SYSAM-2_0/licenses/CCBDPD02_201109090334.lic:/home/appl/sybase/server1570/SYSAM-2_0/license 

     /SYBASE_ASE_DE.lic
     00:0000:00000:00000:2012/05/25 10:56:44.31 kernel  SySAM: Checked out license for 12  

     ASE_CORE 

     (2012.03310/permanent/16C4 B52E 13F3 857C).

     00:0000:00000:00000:2012/05/25 10:56:44.31 kernel  This product is licensed to: GLOBE TELECOM

     INC.

     00:0000:00000:00000:2012/05/25 10:56:44.31 kernel  Checked out license ASE_CORE

     00:0000:00000:00000:2012/05/25 10:56:44.31 kernel  Adaptive Server Enterprise (Enterprise

     Edition)

     00:0000:00000:00000:2012/05/25 10:56:44.32 kernel  Using config area from primary master  

     device.

     00:0000:00000:00000:2012/05/25 10:56:44.36 kernel  os_create_region: can't allocate

     32275791872 bytes

     00:0000:00000:00000:2012/05/25 10:56:44.36 kernel  kbcreate: couldn't create kernel region.

     00:0000:00000:00000:2012/05/25 10:56:44.36 kernel  kistartup: could not create shared memory


I already changed the permissions of all sybase related files back to "sybase:sybase" but this very same error occurs each and every time I am attempting to startup my Sybase database.

 

I dont know why all of a sudden that my Sybae database can't get a hold of the memory it needs to start since it can previously.

I am also not sure how extending a /var filesystem would affect it.

 

I have basically done my research. Some are suggesting that I should edit my /etc/setprivgrp file and set the privelege for sybase. However prior to my miseries I was able to startup sybase without this file being configured.

 

Currently here's the swapinfo output from my server

 

# swapinfo -tam
             Mb      Mb      Mb   PCT  START/      Mb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev       18432       0   18432    0%       0       -    1  /dev/vg00/lvol2
reserve       -     874    -874
memory    34007    4086   29921   12%
total     52439    4960   47479    9%       -       0    -
#

# ipcs -a
IPC status from /dev/kmem as of Fri May 25 11:30:43 2012
Message Queue facility not in system.
T         ID     KEY        MODE        OWNER     GROUP   CREATOR    CGROUP NATTCH      SEGSZ  CPID  LPID   ATIME    DTIME    CTIME
Shared Memory:
m          0 0x411c06cb --rw-rw-rw-      root      root      root      root      0        348  1863  1863  9:57:19  9:57:19  9:57:14
m          1 0x4e0c0002 --rw-rw-rw-      root      root      root      root      2      61760  1863 27943 11:03:25 11:16:31  9:57:14
m          2 0x41207b21 --rw-rw-rw-      root      root      root      root      1       8192  1863  1875  9:57:17  9:57:14  9:57:14
m          3 0x00a5c581 --rw-------     sfmdb     users     sfmdb     users      9   10469376  2704  2704  9:57:43 no-entry  9:57:43
m          4 0x411c14fa --rw-------      root      root      root      root      1       4096  2911  3529  9:58:35 no-entry  9:58:35
m          5 0x4914b784 --rw-r--r--      root      root      root      root      0      22912  2991  2992  9:58:19  9:58:19  9:58:19
m          7 0x0000cace --rw-rw-rw-      root      root      root      root      0          2  3509  3509 11:30:38 11:30:38  9:58:34


Top output (memory part)

 

System Page Size: 16Kbytes
Memory: 416400K (209216K) real, 835824K (383152K) virtual, 30142176K free  Page# 1/547

Kernel Param Values:

shmmax = 51539607552
semmni = 8192

semmns =16000

 

 

Need your urgent advice on this and badly need your help. :)

Thanks in advance.

 

2 REPLIES 2
rariasn
Honored Contributor

Re: Unable to start Sybase after extending /va

Hi:

 

Mount FS with "largefile" option.

 

mount /dev/vgxxx/lvyyyyyyyyy -o largefiles /var/zzzzzzzzzz

 

rgs,

Patrick Wallek
Honored Contributor

Re: Unable to start Sybase after extending /va

How much RAM do you have in this server? 

 

Have you changed the amount that Sybase is trying to allocate?  According to this message:

 

kernel  os_create_region: can't allocate 32275791872 bytes

 

You are trying to allocate 32 GB.  Do you have enough free RAM for that?