This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Plugin for Oracle RMAN support case.
Gather logs according to sections below.
Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed, please notify the Veeam Support engineer.
If you need to use a secure FTP, KB1661 contains secure FTP instructions.
1. Veeam Plugin source logs
This step should be done on the source Oracle server. Navigate to and archive the contents of this folder:
- For Linux and Oracle Solaris:
tar -czvf veeam_plugin_logs.tar.gz /tmp/veeam_plugin_logsFile veeam_plugin_logs.tar.gz will contain the necessary logs.
- For Windows:
Send resulted archive to Veeam Support.
2. Veeam Plugin target logs This step should be done on both Veeam Backup and Veeam Repository servers.
Navigate to and archive the contents of this folder:
- Veeam Plugin for Oracle RMAN 9.5 U4:
- Veeam Plugin for Oracle RMAN 10:
3. RMAN operation logs
Save the information about failed RMAN operations. This can be done in different ways:
- Using SPOOL clause
RMAN> SPOOL LOG TO '/tmp/rman.log'; RMAN> … Actual client commands … RMAN> SPOOL LOG OFF;(Note: https://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta046.htm#RCMRF156)
- Using LOG argument when connecting to the target
$ rman TARGET / LOG=/tmp/rman.log APPEND RMAN> … Actual client commands … RMAN> EXIT(Note: https://docs.oracle.com/database/121/BRADV/rcmcnctg.htm#BRADV8122)
- Using redirection to a file:
$ rman target / | tee -a /tmp/rman.log
Please discuss the appropriate way with your system administrator. It’s important for a support engineer to see RMAN client output for the failed operation. Save the output of RMAN client operations in a text file for Veeam Support.
4. RMAN information
Run the following queries from an RMAN client command prompt:
RMAN> LIST BACKUP; RMAN> LIST ARCHIVELOG ALL; RMAN> SHOW ALL;
Save the output of above queries in a text file for Veeam Support.
5. Database information
- Connect to your instance as sysdba using sqlplus utility:
$ sqlplus / as sysdbaand 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; SQL> SELECT USERNAME,SYSDBA FROM V$PWFILE_USERS; SQL> SHOW PARAMETER SPFILE; SQL> SHOW PARAMETER PFILE;Save the output of above queries in a text file for Veeam Support.
- 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):
- For Linux:
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)
- For Oracle Solaris:
oratab (by default it's located in /var/opt/oracle) inventory.xml (by default it's located in $ORACLE_BASE/oraInventory) oraInst.log (by default it's located in /var/opt/oracle)
- For Windows:
Export contents of HKEY_LOCAL_MACHINE\SOFTWARE\Oracle registry key. This will give support engineer overall information about the software installation on your server.
- For Linux: