Collecting Diagnostic Information for Veeam Plugin for Oracle RMAN

KB ID:
2871
Product:
Veeam Plug-in for Oracle RMAN
Version:
Any
Published:
Last Modified:
2020-04-03

Challenge

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.

 

Solution

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:
    /tmp/veeam_plugin_logs
    Example:
    tar -czvf veeam_plugin_logs.tar.gz /tmp/veeam_plugin_logs
    File veeam_plugin_logs.tar.gz will contain the necessary logs.
  • For Windows:
    %ProgramData%\Veeam\Backup\RmanPluginLogs
    Example:
    User-added image

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:
%ProgramData%\Veeam\Backup\Endpoint
  • Veeam Plugin for Oracle RMAN 10:
%ProgramData%\Veeam\Backup\Plugin
 

3. RMAN operation logs

Save the information about failed RMAN operations. This can be done in different ways:

  • 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 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;
    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.

Rate the quality of this KB article: 
4 out of 5 based on 7 ratings

Couldn't find what you were looking for?

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

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!

Spelling error in text:

Submit