- Veeam Support Knowledge Base
- How to collect logs for cases involving Oracle
How to Collect Logs for Cases Involving Oracle
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
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
- Connect to the Windows machine where Oracle is running.
- 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/
- Open an elevated command prompt and run the following commands:
vssadmin list writers > C:\vsswriters.txt
vssadmin list providers > C:\vssproviders.txt
- Export Windows Event Logs.
- Connect to your instance as sysdba:
sqlplus / as sysdbaselect * 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.
- Collect the files from steps 2-5 and attach them to the case.
Linux Server
- Login to the server shell with the user credentials specified in the 'Guest OS credentials' field.
- Collect files the following:
Files named:- OracleAgent*.log
- Agent.LogBackup_cli*.log
- ./OracleProxyLogs/
- /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- Collect basic environmental information using the following commands:
cat /etc/*release
uname -a
env- 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>"- Connect to the Oracle instance as sysdba:
sqlplus / as sysdbaselect * 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;- 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
- oratab
- Collect the files and shell outputs from the 5 steps above, bundle them in a compressed file, and attach them to your case.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
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
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.