How to enable Debugging for Oracle

book

Article ID: 100020851

calendar_today

Updated On:

Resolution

Debug Steps:
Set Debug on the Backup Exec (BE) server and the Oracle server: 
Open Debug Monitor on each server. For more detail on Debug Monitor see - https://www.veritas.com/support/en_US/article.000047836
  1. On the BE server:
    1. Select the following items from the main screen of Debug Monitor: Job Engine, RAWS, Agent Browser, Backup Exec Server, Device and Media, Catalog, Capture to File.
    2. Click Clear Log.
    3. Inside Debug Monitor, go to Tools\Settings. Select  Agents on the left side. Then select Oracle RMAN on the right and set it to Low
    4. Inside the Tools\Settings dialog, select Job Engine & Remote Agent on the left. Then select Enable Job Engine and Remote Agent Debug outside of SGMon. (Note this will remain in debug mode until this option is turned off)
  2. On the Oracle server:
    1. Oracle on Windows: 
      1. Select the following items from the main screen of Debug Monitor: RAWS, Capture to File.
      2. Click Clear Log.
      3. Inside Debug Monitor, go to Tools\Settings. Select  Agents on the left side. Then select Oracle RMAN on the right and set it to Low
      4. Inside the Tools\Settings dialog, select Job Engine & Remote Agent on the left. Then select Enable Job Engine and Remote Agent Debug outside of SGMon. (Note this will remain in debug mode until this option is turned off)
    2. Oracle on Linux
      1. Stop the Backup Exec Remote Agent for Linux Servers by using the command /opt/VRTSralus/bin/VRTSralus.init stop
      2. Edit the /etc/VRTSralus/ralus.cfg and add this to it: Software\veritas\Backup Exec For Windows\Backup Exec\Debug\VXBSALEVEL=5  
        1. Set the value to 5 unless directed by Tech Support to use a different value.
      3. Edit the /etc/VRTSralus/ralus.cfg and go to the line for: Software\veritas\Backup Exec For Windows\Backup Exec\Debug\AgentConfig=0  change 0 to 1
      4. Start the Backup Exec Remote Agent for Linux Server in debug mode by going to the Bin directory /opt/VRTSralus/bin/   and run the command ./beremote --log-file-auto &
        1. The vxbsa debug information is added to the normal debug log. The log is located here: /var/VRTSralus 
  3. Run the job and reproduce the issue. 
    1. Select the smallest job that will reproduce the problem.
    2. Run this while no other jobs are running, if possible.
    3. Wait for the error to occur.
  4. Collect and send the logs:
    1. Run the Veritas Quick Assist (VQA) on each server to collect and send logs. More detail on this tool can be found in https://www.veritas.com/support/en_US/vqa
    2. Be sure to select Full logs for support 
    3. For Linux - Manually collect the debug log located at:  /var/VRTSralus 
    4. After the Tool has completed the upload of logs from each server to the FTP site, Save and send the Job Log of the job by replying to the Veritas Technician Email or posting it to the case via the web portal.
  5. Debugs should be turned off after the issue is resolved and the logs can be deleted. Each step of the debugs mentioned above need to be undone. 

       
Notes about the logs:
The logs are created under -
BE Server - Program Files\veritas\Backup Exec\Logs
Remote Windows servers - Program Files\veritas\Backup Exec\RAWS\Logs
Remote Linux Servers - /var/VRTRalus   or    /var/log
The following logs create a new file each time BE services restart/debug is turned on:
ServerName-BEngine##.log      
ServerName-BERemote##.log  
ServerName-ralus-timestamp.log
ServerName-vxbsaXX.log 
stubtrac.pid=XXXX.tid=XXXXXX.XXXXXXXXXX.log
AgentntConfig-XXXXXXXXXXXXXXXX.log.txt
The following logs append (single log file):
ServerName-SGMon.log
Ralus.pid
Ralus.ver
TAOCli.log 
 
 

 

 

 

Issue/Introduction

How to enable Debugging to troubleshoot Oracle backup\restore
Powered by Wolken Software