In preparation of upgrading to ZCM 11.3, we applied updates to our SLES 11 servers. Those updates went off without a hitch except now sybase will not start. The error we get is:

Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): SQL Anywhere Network Server Version 12.0.0.2624
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): OEM Authenticated Edition, licensed only for use with authenticated OEM applications.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb):
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Copyright (c) 2001-2010, iAnywhere Solutions, Inc.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Portions copyright (c) 1988-2010, Sybase, Inc. All rights reserved.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Use of this software is governed by the Sybase License Agreement.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Refer to http://www.sybase.com/softwarelicenses.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb):
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Connection limit (licensed seats): 10000
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Processors detected: 1 (containing 8 logical processors)
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Maximum number of physical processors the server will use: 1
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): This server is licensed to:
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): ZENworks
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Novell, Inc.
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Running Linux 3.0.101-0.15-default #1 SMP Wed Jan 22 15:49:03 UTC 2014 (5c01f4e) on X86_64
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Server built for X86 processor architecture
Mar 14 16:00:03 zcmdb SQLAnywhere(zenworks_ourdb): Not enough memory

Also, when attempting to run dbsrv12, we get:

./dbsrv12: error while loading shared libraries: libdbserv12_r.so: cannot open shared object file: No such file or directory



So, since we're planning on upgrading this Monday, and the first step in that process is to unload the db and then upgrade sybase to 12.0.1-3873, what's the likelihood the upgrade will fix our issue? My guess is it's just a problem with the version of sybase we currently have installed doesn't like our new 3.0.101-0-15 kernel. That being said, I would appreciate any feedback out there as I don't want to try the upgrade of sybase if it will "break" things more.....

TIA!