oraasmaudit Oracle ASM

Applies To

All Users

Summary

  • In a 2-node RAC environment, one node consistently generated frequent audit records in the OS message log, while the other node had none in OS message log. May 11 03:39:21 <HOST> journal: Oracle Audit3552: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

    May 11 03:39:29 <HOST> journal: Oracle Audit3756: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

    May 11 03:39:33 <HOST> journal: Oracle Audit3775: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

    May 11 03:39:34 <HOST> journal: Oracle Audit3783: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

    May 11 03:39:35 <HOST> journal: Oracle Audit3794: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

    May 11 03:39:38 <HOST> journal: Oracle Audit3826: LENGTH : '244' ACTION :7 'CONNECT' DATABASE USER:1 '/' PRIVILEGE :6 'SYSDBA' CLIENT USER:6 'oracle' CLIENT TERMINAL:0 '' STATUS:1 '0' DBID:0 '' SESSIONID:10 '4294967295' USERHOST:[

    10] '<HOST>' CLIENT ADDRESS:0 '' ACTION NUMBER:3 '100'

  • Both nodes had the same audit setting, and ASM instances set audit_syslog_level=LOCAL0.INFO. ASM Instances:

    NAME TYPE VALUE


    audit_file_dest string /u01/app/19.3/grid/rdbms/audit

    audit_sys_operations boolean TRUE

    audit_syslog_level string LOCAL0.INFO <<<<<<<<--

    audit_trail string NONE

    unified_audit_sga_queue_size integer 1048576

    DB Instances:

    NAME TYPE VALUE


    audit_file_dest string /u01/app/oracle/admin/<DB_NAME>/adump

    audit_sys_operations boolean TRUE

    audit_syslog_level string

    audit_trail string DB

    unified_audit_common_systemlog string

    unified_audit_sga_queue_size integer 1048576

    unified_audit_systemlog string

Solution

  • To redirect these audit logs, add the corresponding configuration entries to /etc/rsyslog.conf and restart the rsyslog service. For example:

    vi /etc/rsyslog.conf

    -- add redirect setting

    local0.info /var/log/oraasmaudit.log

    local1.info /var/log/oraiosaudit.log

    local2.info /var/log/oraapxaudit.log

    systemctl restart rsyslog

  • To prevent the generation of traditional audit logs, enable Unified Auditing. For example:

    --On all nodes

    crsctl stop crs

    su - grid

    cd GI_HOME/rdbms/lib

    $ make -f ins_rdbms.mk uniaud_on ioracle

    $ su - root

    crsctl start crs

Attachments :

Cause

Applied GIRU 19.22.

Due to Bug 28400367, the following configuration entries were not updated in /etc/rsyslog.conf on the affected node during the GIRU patching. As a result, audit logs were written to the default messages file instead of their redirected log files:

local0.info /var/log/oraasmaudit.log

local1.info /var/log/oraiosaudit.log

local2.info /var/log/oraapxaudit.log

These audit records were generated by traditional auditing, as mandatory audit logs when agents connected to the ASM instance as SYSDBA, triggered by the CHECK_INTERVAL setting in the GI resource properties.

相关推荐
OceanRoy11 小时前
数据库表的设计
数据库·内连接·外连接·er图·表的约束·三大范式·多表连接
Pniubi11 小时前
怎么排查慢SQL,怎么解决?
java·数据库·sql
Decay__15 小时前
VMware 安装 SQL Server 双节点 AlwaysOn 可用性组教程 —— WSFC、AG 与侦听器完整部署(系列核心篇)
运维·数据库·sql·mysql·架构
茶栀(*´I`*)16 小时前
SQL 性能分析:从慢查询日志到执行计划的完整定位方法
数据库·sql
艺杯羹16 小时前
1Panel 装好后 ufw 仍是 inactive:一次服务器安全盲区复盘
服务器·数据库·安全·网络安全·系统架构·实战·1panel
code2cat17 小时前
【随笔】MCP工具重试:任务已经创建,响应丢了怎么办
数据库·mcp
wuyk55519 小时前
Spider-第10讲-SQLite持久化与去重
数据库·爬虫·sqlite
乌暮21 小时前
Spring AOP 与 Spring 事务:用大白话彻底理解原理与实践
java·数据库·spring boot·后端·sql·学习·spring
小此方21 小时前
Re:Mysql数据库基础篇(十二):什么是事务、事务解决了什么问题、事务的四大属性、事务的操作方式
数据库·mysql
flash俊杰1 天前
v0.5-01 让桌面 AI 助手记得住:预算组装、递归摘要、长期记忆与评估基线
数据库·安全·架构