title: Sybase initializes but does not run
body: <p>I am using Red Hat 5.5 and I am trying to run Sybase ASE 12.5.4.</p>
  
  <p>Yesterday I was trying to use the command "service sybase start" and the console showed sybase repeatedly trying to initialize, but failing, the main database server.</p>
  
  <p>UPDATE:</p>
  
  <p>I initialized a database at /ims_systemdb/master using the following commands:</p>
  
  <pre><code>dataserver -d /ims_systemdb/master -z 2k -b 51204 -c $SYBASE/ims.cfg -e db_error.log
  chmod a=rwx /ims_systemdb/master
  ls -al /ims_systemdb/master
  </code></pre>
  
  <p>And it gives me a nice database at /ims_systemdb/master with a size of 104865792 bytes (2048x51240).</p>
  
  <p>But when I run</p>
  
  <pre><code>service sybase start
  </code></pre>
  
  <p>The error log at /logs/sybase_error.log goes like this:</p>
  
  <pre><code>00:00000:00000:2013/04/26 16:11:45.18 kernel  Using config area from primary master device.
  00:00000:00000:2013/04/26 16:11:45.19 kernel  Detected 1 physical CPU
  00:00000:00000:2013/04/26 16:11:45.19 kernel  os_create_region: can't allocate 11534336000 bytes
  00:00000:00000:2013/04/26 16:11:45.19 kernel  kbcreate: couldn't create kernel region.
  00:00000:00000:2013/04/26 16:11:45.19 kernel  kistartup: could not create shared memory
  </code></pre>
  
  <p>I read "os_create_region" is normal if you don't set shmmax in sysctl high enough, so I set it to 16000000000000, but I still get this error.  And sometimes, when I'm playing around with the .cfg file, I get this error message instead:</p>
  
  <pre><code>00:00000:00000:2013/04/25 14:04:08.28 kernel  Using config area from primary master device.
  00:00000:00000:2013/04/25 14:04:08.29 kernel  Detected 1 physical CPU
  00:00000:00000:2013/04/25 14:04:08.85 server  The size of each partitioned pool must have atleast 512K. With the '16' partitions we cannot configure this value f
  </code></pre>
  
  <p>Why do these two errors appear and what can I do about them?</p>
  
  <p>UPDATE:</p>
  
  <p>Currently, I'm seeing the 1st error message (os cannot allocate bytes).  The contents of /etc/sysctl.conf are as follows: </p>
  
  <pre><code>kernel.shmmax = 4294967295
  kernel.shmall = 1048576
  kernel.shmmni = 4096
  </code></pre>
  
  <p>But the log statements earlier state that</p>
  
  <pre><code>os_create_region: can't allocate 11534336000 bytes
  </code></pre>
  
  <p>So why is the region it is trying to allocate so big, and where did that get set?</p>