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 C. Script-based Block-Level Incremental (BLI) Backups without RMAN on UNIX and Linux systems
  4. Creating NetBackup policies for script-based BLI backup
  5. Creating notify scripts for BLI backups
  6. Oracle environment variables for BLI scripts
NetBackup™ for Oracle Administrator's Guide

Oracle environment variables for BLI scripts

If you create notify scripts, or if you run setup_bli_scripts, you need to provide values for the Oracle environment variables.

These variables are as follows:

ORACLE_DBA

User name of the Oracle database administrator. Typically, oracle.

ORACLE_BASE

$ORACLE_BASE of the Oracle database instance.

ORACLE_HOME

$ORACLE_HOME of the Oracle database instance.

ORACLE_SID

Oracle database instance ID ($ORACLE_SID) if it is different from the keyword.

ORACLE_LOGS

Directory in which the Oracle archive logs reside.

ORACLE_CNTRL

Location to which a copy of the Oracle control file is written so that it can be backed up.

SQLCMD

sqldba, svrmgrl, or sqlplus command to start up or shut down the database.

ORACLE_INIT

Path name for the Oracle startup parameter file (INIT.ORA). If you are using an Oracle SPFILE as your parameter file, do not set the ORACLE_INIT environment variable.

ORACLE_CONFIG

Path name for the Oracle configuration file (CONFIG.ORA). Some database configurations use the CONFIG.ORA file to specify values for the database parameters that usually do not change. The CONFIG.ORA file can be called by the INIT.ORA file using an include statement.

Feedback

Was this page helpful?
Previous

Identify the POLICY_IN_CONTROL for BLI backups

Next

About BLI notify scripts for other policies

Feedback

Was this page helpful?