11-01-06, 08:50 #1Registered User
- Join Date
- Nov 2006
Unanswered: ASE 12.5.3 hang suddenly with no error message show in errorlog
Recenlty we found that the sybase will hang suddenly. However, there is no error message logged in errrorlog, just hang!!! This sybase is operated 24 x 7, after we patch it to 12.5.3 EBF 13332 and added physical memory, it hangs suddenly within 1-3 days. After restart, everything return to normal. Could anyone help to solve this problem. As there is no error message show in the log which make difficult to check the problem.
Here is the details information of our server
Intel(R) Xeon(TM) CPU 2.80GHz, ~2GB RAM, 80GB SCSI HD (RAID5)
Redhat Linux 7.3 with latest kernel 2.4.20-28.7
Shmmax: (1280 * 1024 * 1024) = 1342177280
12.5.3 EBF 13332
Only ONE database created: database full dump size: ~ 2GB
Meg. 2K Blks Bytes
Configured Memory: 1024.0000 524288 1073741824
Non Dynamic Structures: 2.8672 1469 3006480
Dynamic Structures: 37.5156 19208 39337984
Cache Memory: 694.4844 355576 728219648
Proc Cache Memory: 67.7383 34682 71028736
Unused Memory: 221.3320 113322 232083456
any sugguestion on how to check/solve the problem? At this stage, i still don't know the problem is caused by patching to latest EBF, miss configured memory or anything else. As there is no message show in errorlog when it comes to hang!
Last edited by halu; 11-01-06 at 09:01.
11-30-06, 06:42 #2Registered User
Originally Posted by halu
- Join Date
- Apr 2004
12-04-06, 01:13 #3Registered User
- Join Date
- Sep 2002
- Sydney, Australia
Of course it is not supposed to do that.
1 Open a case with Tech Support
2 ESD #7 (EBF 13332) was quite ok for me, although I do not run Linux. This binary may well have a bug. You should go through the Open Cases/Solved Cases.
3 It appears that you have just crossed the 2gb address space boundary (adding memory ...), so check that all the various settings/declarations are correctly set (o/s as well as Sybase).
4 For those of us running 24x7 shops, we NEVER put a binary (specific release) of ANY product in production without testing the hell out of it in test.
5 Run top or ps -ef continuously and try to figure out if the dataserver processes are doing anything and what.
6 Have you run out of /fs space on the /fs where sybase is installed and where the errorlog sits ? Do you have the reboot set up to clear the errorlog ?
7 I know it is difficult when hung, but you are seldom completely and totally hung, sotry to find out what was running within Sybase (isql/select * from sysprocesses if sp_who does not work), etc. Usually if you have an isql session that is open, you can still use it.
Senior Sybase DBA/Information Architect derekATsoftwaregemsDOTcomDOTau
Anything worth doing is worth doing Right The First Time
Spend your money on standards-compliant development or spend 10 times more fixing it