ORA-609: Suspected memory_target setting is too large to cause downtime
Source: Internet
Author: User
ORA-609: Suspected memory_target setting is too large to cause downtime
Phenomenon:
The customer's database has recently occurred several sudden downtime events, view alert log:
Thu OCT 10 10:47:50 2013
ORA-609:OPIODR aborting process unknown ospid (834_47932399713424)
Thu OCT 10 10:47:50 2013
ORA-609:OPIODR aborting process unknown ospid (740_47613956914320)
Thu OCT 10 10:47:53 2013
ORA-609:OPIODR aborting process unknown ospid (755_47556191542416)
Thu OCT 10 10:47:53 2013
ORA-609:OPIODR aborting process unknown ospid (761_47545590688912)
Thu OCT 10 10:47:54 2013
ORA-609:OPIODR aborting process unknown ospid (859_47653507185808)
Thu OCT 10 10:47:58 2013
ORA-609:OPIODR aborting process unknown ospid (904_47121713061008)
Thu OCT 10 10:48:08 2013
ORA-609:OPIODR aborting process unknown ospid (918_47924605709456)
Thu OCT 10 10:48:16 2013
ORA-609:OPIODR aborting process unknown ospid (965_46996288695440)
Thu OCT 10 10:48:16 2013
ORA-609:OPIODR aborting process unknown ospid (984_47202090368144)
Thu OCT 10 10:49:06 2013
ORA-609:OPIODR aborting process unknown ospid (1103_47027913133200)
Thu OCT 10 10:49:08 2013
Thu OCT 10 10:49:08 2013
ORA-609:OPIODR aborting process unknown ospid (1064_47991325715600)
ORA-609:OPIODR aborting process unknown ospid (1150_47885260754064)
Thu OCT 10 10:50:02 2013
Process W000 died, and its trace file
Thu OCT 10 10:50:17 2013
Process W001 died, and its trace file
Thu OCT 10 10:54:19 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:54:31 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:54:43 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:54:55 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:55:07 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:55:19 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 10:55:31 2013
Process W000 died, and its trace file
Process W000 died, and its trace file
Process W000 died, and its trace file
Thu OCT 10 11:02:06 2013
Thread 2 advanced to log sequence 18269
Current log# seq# 18269 mem# 0: +unidg/uni/onlinelog/group_15.295.796513629
Thu OCT 10 11:02:08 2013
Success:diskgroup UNIDG was mounted
Thu OCT 10 11:02:18 2013
Success:diskgroup UNIDG was dismounted
Thu OCT 10 11:03:40 2013
Process M001 died, and its trace file
Thu OCT 10 11:04:23 2013
Process M001 died, and its trace file
Analysis:
To view the parameter settings at startup, discover that the customer's system has automatic memory management enabled:
Memory_target = 21G <-------------Automatic memory Management feature is used.
Free-g View memory as 23G
It is recommended that customer Memory_target be set to 16-18g if the host resource depletion is suspected to cause system downtime.
After the small memort_target, the previous automatic downtime disappeared.
Attached: Analysis of the following log.
$CRS _home/log/<nodename>/*.log
$CRS _home/log/<nodename>/crsd/*.log
$CRS _home/log/<nodename>/cssd/*.log
/etc/oracle/oprocd/*.log.* or/var/opt/oracle/oprocd/*.log.*
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.
