Applies to: 
Run the OPBackup utility to back up the IBM OpenPages® database.
About this task
Run the OPBackup utility with the dbonly parameter.
Note:
You can back up the databases by using other methods. Some examples of alternative methods
include:
- Doing a full physical backup by using RMAN
- Doing a combination of full and incremental backup by using RMAN
- Doing an Oracle data pump export.
If you want to use an alternative method, it is critical that you have the necessary skills
available within your organization to complete all aspects of the backup and restore activity.
For more information about backing up your environment, see the IBM OpenPages Administrator's Guide.
Procedure
-
Make sure that no OpenPages processes are
running, such as object reset jobs.
-
Shut down all OpenPages components:
application servers (admin and non-admin), reporting servers (active and standby), and the search
server.
-
Open a command or shell window on the admin application server.
-
Go to the
<OP_HOME>/aurora/bin
directory.
-
Do a full database backup of the OpenPages
schema by using OPBackup.
Windows:
OPBackup.cmd <backup_directory> dbonly
Linux®:
./OPBackup.sh <backup_directory> dbonly
The <backup_directory> is the full path to a directory on the database
server. This directory is where the log files are saved. If the file path is not specified, the
OPBackup command uses the location that is specified by the BACKUP_LOCATION
parameter in the
<OP_HOME>/aurora/bin/op-backup-restore.env file.
A dump file is created in the OP_DATAPUMP_DIRECTORY directory.
To find the
OP_DATAPUMP_DIRECTORY directory, run the following SQL as the
system
user:
select directory_name, directory_path from dba_directories
where directory_name = upper ('OP_DATAPUMP_DIRECTORY');
-
Examine the backup log and make note of the dump file name. The naming convention is
openpage_<timestamp>.dmp.