Creating XML export scripts manually
When the database agent was initially installed, the installation software wrote example scripts to the following locations:
For export:
Windows:
install_path\NetBackup\dbext\Oracle\samples\bporaexp
UNIX:
/usr/openv/netbackup/ext/db_ext/oracle/samples/bporaexp
For import:
Windows:
install_path\NetBackup\dbext\Oracle\samples\bporaimp
UNIX:
/usr/openv/netbackup/ext/db_ext/oracle/samples/bporaimp
The example export scripts that are installed in bporaexp are as follows:
Windows:
data_archiver_export.cmd
UNIX:
data_archiver_export.sh
data_archiver_export64.sh
bporaexp_help.param bporaexp_partitions.param bporaexp_table_to_files.param bporaexp_tables.param bporaexp_tables_rows.param
The example import scripts that are installed in bporaimp are as follows:
Windows:
data_archiver_import.cmd
UNIX:
data_archiver_import.sh
data_archiver_import64.sh
bporaimp_archive.param bporaimp_archive_schema_to_files.param bporaimp_archive_to_users.param bporaimp_bfile_table.param bporaimp_help.param bporaimp_ignore_rows_table.param bporaimp_large_table.param bporaimp_list.param bporaimp_old_archive.param bporaimp_partitions.pram bporaimp_table_from_files.param bporaimp_table_to_files.param bporaimp_table_to_user.param bporaimp_tables.param
To use the example scripts
- Copy the example scripts to a different directory on your client. Oracle scripts can be located anywhere on the client.
- Modify each script for your environment.
- On UNIX, make sure that the su command logs into the correct user.
If you do not include an su - user (user is Oracle administrator account) in your Oracle scripts, they do not run with the proper permissions and environment variables. The result is problems with your database backups and restores.