Hello everyone,

we are having a strange problem for quite some time now.
One of our databases is behaving normally for between 1 and 2 days.
Then suddenly 1 core is at 100% while the other avaiable 7 cores do
nothing.
Everyone connected to the database can't get any response anymore.

Logging on via Sybase Central as DBA produces the error:
'Found server but connection error occurred'
after waiting about 10 Minutes.

Shutting down the database produces no response.
Killing it via the shell command kill produces a: Shutting down
database because of a TERM Signal but does not close the database
service.
We have to use kill -9 to ultimatly close it.

After starting the database again it will continue running for about 2
days before producing the same problem.

We have been profiling and logging but none of the SQL Statements
looked suspicous.
Logging with -z showed nothing special except that the database still
receives incoming logins and gives them an connection id but nothing
else happens afterwards.

Informations:
ASA 11.01.2519
running on Linux 2.6.26-2-686-bigmem
running in High Avaiability Mode with a hardware identical mirror
Database Size is about 57GB
Start parameters
-dt /tmp -c 2500M -n "servername" -x TCPIP(port=49235) -xf /hao/
server1state.txt @/etc/init.d/dbconfig "Path to DB File" -sn "alt
servername" -xp partner=(ENG="mirror
servername";LINKS=TCPIP(HOST=49235;TIMEOUT=10));au th=***;

Can anyone give any hints to whats going on?