Shulou(Shulou.com)06/01 Report--

When inspecting the database, we found that the installation directory of grid was very large, so we carried out further inspection and found that many * .l10 logs had been deleted, but not released. You can see them by using the lsof command.

Lsof | grep delete

[smisa@smidb11 oraagent_grid] $sudo lsof | grep delete | grep-E "oraagent | audit" oracle 18375 grid 33w REG 253 18 10549871 1715713 / oracle/app/11.2.0/grid_1/log/smidb11/agent/crsd/oraagent_grid/oraagent_grid.l10 (deleted) oracle 25466 grid 4w REG 253 10576898 1704191 / oracle/app/11.2.0/grid_1/log/smidb11/agent/ohasd/ Oraagent_grid/oraagent_grid.l10 (deleted) oracle 25468 grid 4w REG 253 18 10576898 1704191 / oracle/app/11.2.0/grid_1/log/smidb11/agent/ohasd/oraagent_grid/oraagent_grid.l10 (deleted). Oracle 25603 grid 4w REG 253 18 10576898 1704191 / oracle/app/11.2.0/grid_1/log/smidb11/agent/ohasd/oraagent_grid/oraagent_grid.l10 (deleted) oracle 28628 grid 4w REG 253 18 10511009 1704519 / oracle/app/11.2.0/grid_1/log/smidb11/agent/crsd/oraagent_grid/oraagent_grid.l10 (deleted) two nodes: [smisa @ smidb12 ~] $sudo lsof | grep delete | grep-E "oraagent | audit" oracle 15647 grid 4w REG 253 18 10574076 3150129 / oracle/app/11.2.0/grid_1/log/smidb12/agent/ohasd/oraagent_grid/oraagent_grid.l10 (deleted) oracle 15649 grid 4w REG 253 18 10574076 3150129 / oracle/app/11.2.0/grid_1/log/smidb12/agent/ohasd/oraagent_grid/ Oraagent_grid.l10 (deleted). Oracle 15887 grid 4w REG 253 18 10543680 3150126 / oracle/app/11.2.0/grid_1/log/smidb12/agent/crsd/oraagent_grid/oraagent_grid.l10 (deleted)

As grid runs, this log will increase and eventually run out of memory. Find the problem through MOS and find the name Bug17034444

However, it is found that there is no patch for this Bug and you need to apply for development, so you can write your own scripts to avoid it. The ideas are as follows:

Scan the directory at regular intervals to see if an oraagent_grid.l10 file is generated

If this file is found to be generated, delete it in advance before grid automatically deletes the file, to avoid that grid will not release the bug of the file.

The script is as follows:

Source / home/grid/.bash_profileHOSTNAME= `hostname`LOGFILE1 = / oracle/app/11.2.0/grid_1/log/$ {HOSTNAME} / agent/crsd/oraagent_grid/oraagent_grid.l10LOGFILE2=/oracle/app/11.2.0/grid_1/log/$ {HOSTNAME} / agent/ohasd/oraagent_grid/oraagent_grid.l10LISTENER_XML_LOG=/oracle/app/grid/diag/tnslsnr/$ {HOSTNAME} / listener/alert/log_*.xmlLISTENER_TRACE_FILE=/oracle/app/grid/ Diag/tnslsnr/$ {HOSTNAME} / listener/trace/listener.logDATETIME= `date +% Y% m% d% H% M% S`echo "${DATETIME} Is Run!" > > / home/grid/script/clearlog.logif [- e ${LOGFILE1}] Then rm-rf ${LOGFILE1} echo "${LOGFILE1} Deleted!" > / home/grid/script/clearlog.logfiif [- e ${LOGFILE2}]; then rm-rf ${LOGFILE2} echo "${LOGFILE2} Deleted!" > > / home/grid/script/clearlog.logfiFILE_CNT= `ls-l / oracle/app/grid/diag/tnslsnr/$ {HOSTNAME} / listener/alert/ | wc-l`if [${FILE_CNT}-gt 100] Then ls-lrt ${LISTENER_XML_LOG} > > / home/grid/script/clearlog.log rm-rf ${LISTENER_XML_LOG} fiif [`Clearing-sk | awk'{print $1}'`- gt 1073741824]; then echo "${LISTENER_TRACE_FILE} fiexit!" > > / home/grid/script/clearlog.log > ${LISTENER_TRACE_FILE} fiexit 0

When using, you need to modify the previous variables to the corresponding values of the current server. This script will not only delete the log file of * .l10, but also automatically clear the listening log.

Oracle official description:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.