Collecting Additional Diagnostic Information for Oracle Processing Cases

KB ID: 2374
Product: Veeam Backup & Replication
Version: 8.x, 9.x
Published:
Last Modified: 2017-11-08

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 some information from your servers and databases in order to investigate this issue.

Cause

Additional logs have to 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 run the job again 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 accuracy of the information will be affected.
 
 
For Windows
 
1.  Navigate to the following directory:
 
 %programdata%\Veeam\Backup
  
2.  Collect files and folders matching the following Syntax:
 

VeeamGuestHelper_ddmmyyyy.log
VeeamLogShipper_ddmmyyyy.log
OracleLib.*.log
%backup job name%_Oracle_Redo_Log_Backup - entire folder
 
3.  Open an elevated command prompt and run the following commands:
 
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
 
4.  Export Windows Event Logs as shown here.

5. Connect to your instance as sysdba:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SSQL> select username from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select * from dba_role_privs where granted_role='DBA';
 
Save output of above queries in a text file for support engineer.

 
For Linux
 

1.  Navigate to the following directories:
 
/var/log/VeeamBackup
/tmp
 
get all the files with the following filename masks:
 
VeeamOracleAgent.*.log
Agent.LogBackup_cli.*.log
 
2. Login to the server shell with the user credentials specified in 'Guest OS credentials' field as shown here. After that issue the following commands to get basic environment information:
 
cat /etc/*release
uname -a
env
 
3. Collect information about guest components installed on your virtual machine:
 
a) In case of VMware
 
- Login to your Linux server
- Run the following commands
 
# vmtoolsd -v
# service vmtoolsd status
 
or
 
#  systemctl status vmtoolsd
 
b) In case of Hyper-V
 
- Login to your Linux server
- Run the following commands
 
# lsmod | grep hv_utils
# modinfo hv_vmbus
# ps -ef | grep hv
 
- Login to your Hyper-V host where this virtual machine is running
- Run the following command in PowerShell (replace VM with your actual virtual machine name)
 
PS> Get-VMIntegrationService -VMName "VM"
 
4. Connect to your instance as sysdba from same user in shell as it was in step 2:
 
sqlplus / as sysdba
 
and run the following queries:
 
SQL> select * from v$version;
SQL> select status from v$instance;
SQL> select log_mode from v$database;
SQL> select name from v$controlfile;
SSQL> select username from v$pwfile_users;
SQL> show parameter spfile;
SQL> show parameter pfile;
SQL> select * from dba_role_privs where granted_role='DBA';
 
Save the output of above queries in a text file for Veeam Support.
 
5. Get the following files from your 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 defaults it's located in $ORACLE_HOME)
 
Collect the logs and shell outputs from the steps above, bundle them in a compressed file, and share with Veeam Support. 
 

5 / 5 (20 votes cast)

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Orphus system