Moving Sybase to new server, segmentation fault

I have to migrate to new server due to old RedHat E3 isn't supported anymore from the end of this month. I have few problems moving Sybase.

I am using now Red Hat Enterprise 5 (32bit) and my Sybase is 11.9.2
What I did, I installed Sybase from RPM packages I had and copied files from old server to new one (databases and sybase settings).

The problem is when I run /etc/init.d/sybase start
Only one of the processes starts (backupserver process), the dataserver gives me segmentation fault everytime I try to run it. Same goes to srvbuild/srvbuildres (but I am not sure if I need to run srvbuild anymore as all is pretty much set up).

I tried setting up LD_POINTER_GUARD to 0 or 1 and that does nothing good. Check $SYBASE, it's set up properly.
I am attaching strace log.

Anyone got any ideas how to fix it ?
10521 execve("/opt/sybase-11.9.2/bin/dataserver", ["/opt/sybase-11.9.2/bin/dataserve"], [/* 23 vars */]) = 0
10521 brk(0)                            = 0xa4b1000
10521 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
10521 open("/etc/ld.so.cache", O_RDONLY) = 3
10521 fstat64(3, {st_mode=S_IFREG|0644, st_size=34194, ...}) = 0
10521 mmap2(NULL, 34194, PROT_READ, MAP_PRIVATE, 3, 0) = 0xba1000
10521 close(3)                          = 0
10521 open("/lib/libm.so.6", O_RDONLY)  = 3
10521 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\364\275\0004\0\0\0"..., 512) = 512
10521 fstat64(3, {st_mode=S_IFREG|0755, st_size=216544, ...}) = 0
10521 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x28c000
10521 mmap2(0xbdc000, 163952, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xbdc000
10521 mmap2(0xc03000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26) = 0xc03000
10521 close(3)                          = 0
10521 open("/lib/libdl.so.2", O_RDONLY) = 3
10521 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0pZ\275\0004\0\0\0"..., 512) = 512
10521 fstat64(3, {st_mode=S_IFREG|0755, st_size=20668, ...}) = 0
10521 mmap2(0xbd5000, 16504, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xbd5000
10521 mmap2(0xbd8000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2) = 0xbd8000
10521 close(3)                          = 0
10521 open("/lib/libc.so.6", O_RDONLY)  = 3
10521 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\377\250\0004\0\0\0"..., 512) = 512
10521 fstat64(3, {st_mode=S_IFREG|0755, st_size=1689640, ...}) = 0
10521 mmap2(0xa7a000, 1410500, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x110000
10521 mmap2(0x263000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x152) = 0x263000
10521 mmap2(0x266000, 9668, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x266000
10521 close(3)                          = 0
10521 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x844000
10521 set_thread_area({entry_number:-1 -> 6, base_addr:0x8446c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0
10521 mprotect(0x263000, 8192, PROT_READ) = 0
10521 mprotect(0xbd8000, 4096, PROT_READ) = 0
10521 mprotect(0xc03000, 4096, PROT_READ) = 0
10521 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
10521 +++ killed by SIGSEGV +++

Open in new window

LGDEAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joe WoodhousePrincipal ConsultantCommented:
Have you applied all the Red Hat kernel settings and packages listed in the Release Bulletin?

The problem may simply be that this combination doesn't work... there was of course no RHEL 5 when ASE 11.9.2 was still supported.

Perhaps a dumb question - why even bother upgrading RHEL? Lack of support for RHEL 3 can't be that serious a problem for you if you're still running ASE 11.9.2... which hasn't been supported for many years now. It's not as if upgrading to RHEL 5 will give you a supported environment.
LGDEAuthor Commented:
Server had been set up properly the problem seems to be incompatibility of ASE & RHE5.
Till migration from MySQL finish we've set up virtual machine on RHEL5 that's temporary running older version just with sybase

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
LGDEAuthor Commented:
No other acceptable solution was found. Done temporary workaround solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Sybase Database

From novice to tech pro — start learning today.