Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Oracle Administrator's Guide
  3. Appendix D. XML Archiver
  4. Troubleshooting XML export or XML import errors
NetBackup™ for Oracle Administrator's Guide

Troubleshooting XML export or XML import errors

An XML export or import error can originate from NetBackup or from Oracle, as follows:

  • On the NetBackup side, an error can be from the bporaexp or bporaimp programs, the NetBackup server or client, or Media Manager.

  • On the Oracle side, an error can be from the target database.

Use the following steps when troubleshooting a failed operation:

  • Check the logs to determine the source of the error.

  • Troubleshoot each stage of the XML export or XML import.

    The following sections describe these steps in detail.

    On UNIX and Linux, these sections describe the log files from the bporaexp and bporaimp commands. The logs are created in /usr/openv/netbackup/logs/bporaexp or /usr/openv/netbackup/logs/bporaimp.

Feedback

Was this page helpful?
Previous

Example - Using bporaimp for a redirected restore

Next

Checking the logs to determine the source of an error

Feedback

Was this page helpful?