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. Restoring an XML export archive
  5. About bporaimp parameters
NetBackup™ for Oracle Administrator's Guide

About bporaimp parameters

Use the NetBackup parameters NB_ORA_SERV and NB_ORA_CLIENT to specify the NetBackup runtime configuration. Otherwise, the order of precedence for the runtime configuration variable settings is used.

Some parameters are valid only when writing to a storage unit. Other parameters are valid only when writing to a directory. In the following table, the right-most column contains either "Storage Unit" or "Directory" to indicate whether the parameter in that row is applicable for either writing to a storage unit or to a directory. Parameters that are recognized when writing to a directory are ignored when writing to a storage unit.

Table: bporaimp parameters and default values describes the bporaimp (bporaimp64 on some platforms) parameters and default values.

Table: bporaimp parameters and default values

Parameter

Required?

Default

Description

Target location

ARCHIVE_DATE_FROM

N

no default

Optionally specifies a start date for the archive to be imported. Used with ARCHIVE_DATE_TO to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss].

Storage Unit

ARCHIVE_DATE_TO

N

no default

Optionally specifies an end date for the archive to be imported. Used with ARCHIVE_DATE_FROM to specify a range. If not used, the most recent archive is imported. If the range used results in more than one archive, the most recent from the range is used. The date format is mm/dd/yyyy [hh:mm:ss].

Storage Unit

BFILE_DIRECTORY

Y (if any table being imported has BFILE columns)

no default

Specifies a directory for the output of any BFILE columns being imported. Oracle's CREATE DIRECTORY command can be used to create the DIRECTORY in Oracle, and the name should match the name used in the export file.

Directory

COMMIT

N

N

Specifies whether bporaimp should commit after each array insert. The size of the array is determined by ROW_BUFFER. By default, bporaimp commits only after loading each table, and performs a rollback when an error occurs, before continuing with the next object.

Directory

DIRECTORY

N

no default

Optionally specifies a directory for the input of the bporaimp utility.

Directory

FROMUSER

N

no default

Optionally specifies a comma-separated list of users to import from an archive containing multiple users' tables. If not specified, all of the tables are imported.

Directory

HELP

N

N

Displays a help message with descriptions of bporaimp parameters.

Directory

IGNORE_ROWS

N

N

Specifies whether or not rows should be inserted into a table that is not empty. The default is that the table already exists and that it is empty. If it is not empty, IGNORE_ROWS = N causes an error to be reported, and the table is skipped with no rows inserted. IGNORE_ROWS = Y causes rows to be inserted with errors reported in the log file.

If IGNORE_ROWS = Y and an error such as a primary key constraint violation occurs, no data is inserted if COMMIT = N. However, if COMMIT = Y, the array of rows (size determined by ROW_BUFFER) is not inserted, but bporaimp continues to process additional row arrays in the order in which they were exported. To cause all rows that do not violate a primary key constraint to be inserted, set COMMIT = Y, ROW_BUFFER = 1, and IGNORE_ROWS = Y.

Directory

KEYWORD

N

no default

Optionally specifies a keyword phrase for NetBackup to use when searching for archives from which to restore files.

Storage Unit

LIST

N

N

LIST = Y queries the NetBackup catalog and lists the archives available. Does not import the data if LIST = Y.

Storage Unit

LOG

N

no default

Optionally specifies a file name to receive informational and error messages. If this parameter is specified, messages are logged in the log file and not displayed to the terminal display.

Directory

NAME

Y

no default

The name of the master XML schema file. This parameter is required if LIST = N.

Directory

NB_ORA_SERV

N

default master server

Optionally specifies the name of the NetBackup master server.

Storage Unit

NB_ORA_CLIENT

N

default client

Optionally specifies the name of the NetBackup for Oracle client.

Storage Unit

RESTORE_SCHEMA_ONLY

N

N

Used with RESTORE_TO_DIRECTORY to restore the XML schema files only to a directory.

Storage Unit

RESTORE_TO_DIRECTORY

N

no default

Optionally specifies a directory for the output of the bporaimp utility. If used, the XML data is not parsed and inserted into Oracle.

Storage Unit

ROW_BUFFER

N

1000

Specifies the size, in rows, of the buffer used to insert rows. Tables with LONG or LOB columns are inserted one row at a time. The maximum value allowed is 32767.

Directory

TABLES

N

no default

Optionally specifies a list of table, view, and partition names to import. If not used, all objects in the archive are imported. The objects must already exist, and the USERID must have INSERT privilege on the objects. The object names cannot be qualified with owner names, and the FROMUSER parameter is used to specify a particular owner. If a partition name is specified, it indicates the exported partition only and the rows are inserted according to the partitioning scheme of the target table. If the export contains partitions, and the import does not specify them, all are inserted.

Directory

TOUSER

N

no default

Optionally specifies a comma-separated list of users to import to that can be used with the FROMUSER parameter to change the table owners. The TOUSER Oracle accounts must already exist, and the USERID must have INSERT privilege on the tables that must also exist.

Directory

USERID

Y

no default

Specifies the username/password (and optional connect string) of the user initiating the import. If a connect string is not provided, the ORACLE_SID environment variable is used.

Directory

Feedback

Was this page helpful?
Previous

Running bporaimp on the client

Next

About redirecting a restore of an XML export archive to a different client

Feedback

Was this page helpful?