Oracle Database Cloud Service能否配置Syslog并指定日志接收地址？

Great questions! Let's break down each one and walk through how to replicate your on-prem Oracle log setup in DBaaS:

1. Can database logs be sent to Syslog? #

Absolutely. Oracle Database Cloud Service supports forwarding various database logs (including audit logs, alert logs, and trace logs) to Syslog, regardless of whether you're using a VM-based deployment or Exadata Cloud Service (though exact steps might vary slightly by deployment type).

2. Can you specify the Syslog host and port? #

Yes, you have full control over the target Syslog server's hostname/IP and port number. This works for both Syslog servers within your Cloud VCN and external centralized Syslog systems (as long as network connectivity is allowed via security lists/NSGs).

How to implement log redirection (matching on-prem Oracle behavior) #

ODBaaS VM instances give you SSH access to the underlying OS, so you can use many of the same techniques you'd use on a local Oracle server. Here's how to handle both scenarios:

Redirect logs to a non-default directory #

1. First, create your target directory and set proper permissions for the Oracle user (usually oracle or grid):

   sudo mkdir -p /u02/custom_oracle_logs
   sudo chown oracle:oinstall /u02/custom_oracle_logs
   

2. Update the relevant database initialization parameters via SQL*Plus (connect as SYSDBA):
   • For alert and background trace logs:

     ALTER SYSTEM SET background_dump_dest='/u02/custom_oracle_logs' SCOPE=SPFILE;
     

   • For audit logs (if using unified audit):

     ALTER SYSTEM SET audit_file_dest='/u02/custom_oracle_logs/audit' SCOPE=SPFILE;
     

3. Restart the database to apply the changes:

   sudo systemctl stop oracle-xe.service # Adjust service name based on your DB version
   sudo systemctl start oracle-xe.service
   

Send logs to a centralized Syslog server #

You have two reliable methods to do this:

Method 1: Configure rsyslog on the DBaaS VM

Most ODBaaS deployments use Oracle Linux with rsyslog. Use this method to forward any log file to your Syslog server:

1. SSH into your DBaaS VM and switch to root:

   sudo su -
   

2. Create a custom rsyslog config file (e.g., /etc/rsyslog.d/oracle-logs.conf) to monitor your database logs:

   # Forward alert logs to Syslog
   $InputFileName /u01/app/oracle/diag/rdbms/mydb/mydb/trace/alert_mydb.log
   $InputFileTag oracle-alert:
   $InputFileStateFile stat-oracle-alert
   $InputFileSeverity info
   $InputFileFacility local0
   $InputRunFileMonitor
   
   # Forward audit logs to Syslog
   $InputFileName /u02/custom_oracle_logs/audit/*.log
   $InputFileTag oracle-audit:
   $InputFileStateFile stat-oracle-audit
   $InputFileSeverity info
   $InputFileFacility local0
   $InputRunFileMonitor
   
   # Send all local0 logs to your centralized Syslog server
   # Use @ for UDP, @@ for TCP
   local0.* @your-syslog-server:514
   

   Replace mydb with your database unique name, and your-syslog-server:514 with your target host/port.
3. Restart rsyslog to apply the changes:

   systemctl restart rsyslog
   

Method 2: Use Oracle's built-in Syslog integration (12c+)

If you're running Oracle 12c or later, you can configure the database to send audit logs directly to the local Syslog, which you can then forward to your centralized server:

1. Enable unified audit (if not already enabled):

   ALTER SYSTEM SET audit_trail=UNIFIED SCOPE=SPFILE;
   SHUTDOWN IMMEDIATE;
   STARTUP;
   

2. Configure the database to send audit logs to Syslog:

   ALTER SYSTEM SET audit_syslog_level='local0.info' SCOPE=SPFILE;
   ALTER SYSTEM SET audit_syslog_ident='oracle-cloud-audit' SCOPE=SPFILE;
   SHUTDOWN IMMEDIATE;
   STARTUP;
   

3. Follow the steps in Method 1 to configure rsyslog to forward local0 logs to your centralized Syslog server.

Key reminders #

• Network connectivity: Ensure your DBaaS VM's security lists and network security groups allow outbound traffic to your Syslog server's port (typically UDP 514 or TCP 514).
• Testing: Verify logs are forwarding correctly by checking your centralized Syslog server, or send a test message from the DBaaS VM:

  logger -p local0.info "Test log from ODBaaS VM"
  

• Exadata considerations: For Exadata Cloud Service, some steps may require using the Exadata Cloud Service console or specific CLI commands, but the core log forwarding logic remains the same.

内容的提问来源于stack exchange，提问作者boardrider