#1 Global Leader in Data Protection & Ransomware Recovery

How to Collect Logs for Cases Involving Oracle

KB ID: 2374
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2017-11-08
Last Modified: 2024-03-25
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

An issue with backing up of the Oracle database server and/or removal of Oracle archived logs is suspected. Veeam Technical Support would like to gather information from your servers and databases to investigate this issue.

Additional logs must be gathered manually from the guest OS on the VM in question because they are not captured by the Support Wizard automatically.

Solution

NOTE: If Application-Aware Image Processing is disabled, enable it and rerun the job to update the log files within the guest OS.
 
The following actions need to be performed within the guest OS of the VM in question. 

NOTE:
 All Veeam Backup and Replication tasks against the guest in question must be stopped during this collection process. Otherwise, the information's accuracy will be affected.

Expand the section below that matches the OS of the server where Oracle is running.

Microsoft Windows Server
  1. Connect to the Windows machine where Oracle is running.
  2. Collect the following files and folders from %programdata%\Veeam\Backup
    • File(s): VeeamGuestHelper*.log
    • File(s): VeeamLogShipper*.log
    • File(s): OracleLib*.log
    • Folder: <backup_job_name>_Oracle_Redo_Log_Backup/
    • Folder: OracleProxyLogs/
  3. Open an elevated command prompt and run the following commands:
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
  1. Export Windows Event Logs.
  2. Connect to your instance as sysdba:
sqlplus / as sysdba
and collect the output of the following queries:
select * from v$version;
select status from v$instance;
select log_mode from v$database;
select name from v$controlfile;
select username,sysdba from v$pwfile_users;
show parameter spfile;
show parameter pfile;
select instance from v$thread;
select name from v$database;

Save the output of the above queries in a text file for the support engineer.

  1. Collect the files from steps 2-5 and attach them to the case.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
Linux Server
  1. Login to the server shell with the user credentials specified in the 'Guest OS credentials' field.
  2. Collect files the following:

    Files named:
    • OracleAgent*.log
    • Agent.LogBackup_cli*.log
    Folder named:
    • ./OracleProxyLogs/
    These files and folder, if they exist, may be found in any of the following folders:
    • /tmp
    • /tmp/VeeamBackup
    • /var/log/VeeamBackup

The following command can be used to find the files and folder listed above:

find /tmp /tmp/VeeamBackup /var/log/VeeamBackup \( -type f \( -name 'OracleAgent*.log' -o -name 'Agent.LogBackup_cli*.log' \) -o -type d -name 'OracleProxyLogs' \) 2>/dev/null
  1. Collect basic environmental information using the following commands:
cat /etc/*release
uname -a
env
  1. If the Oracle is installed on a virtual machine, collect information about guest components installed:
  • For VMware VMs:
vmtoolsd -v
service vmtoolsd status
systemctl status vmtoolsd
  • For Hyper-V VMs:
lsmod | grep hv_utils
modinfo hv_vmbus
ps -ef | grep hv
  • Also, for Hyper-V VMs, run the following command on the Hyper-V host:
PS> Get-VMIntegrationService -VMName "<oracle-vm-name>"
  1. Connect to the Oracle instance as sysdba:
sqlplus / as sysdba
Collect the output from the following queries:
select * from v$version;
select status from v$instance;
select log_mode from v$database;
select name from v$controlfile;
select username,sysdba from v$pwfile_users;
show parameter spfile;
show parameter pfile;
select instance from v$thread;
select name from v$database;
  1. Collect the following files from the Oracle database installation:
    (ask your database administrator if you are not sure about the exact location of these files)
    • oratab
      by default, it's located in /etc
    • inventory.xml
      by default, it's located in $ORACLE_BASE/oraInventory
    • oraInst.loc
      by default, it's located in $ORACLE_HOME
  2. Collect the files and shell outputs from the 5 steps above, bundle them in a compressed file, and attach them to your case.
For information about attaching files to a support case, please review: https://www.veeam.com/kb4162
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.