online.log中的錯(cuò)誤信息

wantfly

今天在看online.log時(shí)發(fā)現(xiàn)以下信息,不知道是為什麼.請(qǐng)大家?guī)兔��?huì)診一下.
目前數(shù)據(jù)庫(kù)運(yùn)行正常,昨天備份也正常.

03:55:51  Checkpoint loguniq 280608, logpos 0x32018, timestamp: 1692764495

03:55:51  Maximum server connections 527
04:02:25  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:12:06  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:12:16  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:12:24  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:06  檢查點(diǎn)完成:  期間為 424 秒.
04:13:06  Checkpoint loguniq 280608, logpos 0x45018, timestamp: 1692766267

04:13:06  Maximum server connections 527
04:13:07  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:09  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:13  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:17  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:21  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:13:25  listener-thread: err = -25587: oserr = 0: errstr = : 網(wǎng)絡(luò)接收失敗.

04:23:28  檢查點(diǎn)完成:  期間為 17 秒.
04:23:28  Checkpoint loguniq 280608, logpos 0x580c8, timestamp: 1692770041

mwao

我也碰到過(guò)這個(gè)問(wèn)題,經(jīng)判斷是連接用戶數(shù)太多,CPU反映不過(guò)來(lái),不夠用原因.如果CPU<=2個(gè),沒(méi)什么辦法,如>2個(gè),配置更改一下,綁定CPU就行.

wantfly

TO mwao:
    這個(gè)情況我認(rèn)為應(yīng)該是不可能的,因?yàn)闀r(shí)間段是在半夜.不是在白天.
白天用戶多時(shí)也沒(méi)有這種錯(cuò)誤呀,我們半夜基本上沒(méi)有用戶在用的.

mydb

可能是客戶端設(shè)置的問(wèn)題.
客戶斷和服務(wù)器的連接參數(shù)不匹配(可能是客戶端,也可能是數(shù)據(jù)庫(kù)的通訊參數(shù)被修改),數(shù)據(jù)庫(kù)再收到這些來(lái)自客戶端的連接請(qǐng)求后,被丟掉,并記錄錯(cuò)誤信息

IFMXDBA

another possibility, there was a long check point around 8 minutes.  During the checkpoint, the engine is in critical seciton which is flushing logical/phyiscal log buffers to the physical files.  Check if your system have a big job is progressing at that time.  You can also try to adjust the LRU_MIN_DIRTY, LRU_MAX_DIRTY and CKPTINTRVL for checkpoint duration.  Also, you might need check your SAN or disk array log to verify if there is any potential problems.