Configuring Installation Parameters in the obparameters File
Installing Oracle Secure Backup on Linux or UNIX 2-7
■ Enter yes to start the installob script. The steps for running installob
are described in "Installing Oracle Secure Backup on Linux or UNIX with
installob" on page 2-8.
Configuring Installation Parameters in the obparameters File
The setup script creates a file called obparameters in the install subdirectory of the
Oracle Secure Backup home. For example, if the Oracle Secure Backup home is in the
default location /usr/local/oracle/backup, then the obparameters file is
located at /usr/local/oracle/backup/install/.
During the installation process the setup script gives you the choice of accepting the
default settings in the obparameters file or customizing those settings. In most
cases, it is not necessary to change the defaults in the obparameters file. However,
you should review the parameters you can control in this file as part of planning your
installation, and determine whether any of them should be changed.
The obparameters file is plain text that can be edited using any standard text editor.
Reasons to change the parameters in the obparameters file include:
■ You can specify a different key size for enhanced security or performance
■ You can customize installation directories and symbolic links created during
installation on different platforms.
■ If you are using Oracle Secure Backup to back up Oracle Database files to tape,
then you can create an Oracle Secure Backup user named oracle for use in
RMAN backups. You can associate this user with Linux or UNIX operating system
credentials by setting parameters in obparameters.
See Also: "Installing Oracle Secure Backup on Linux or UNIX with
installob" on page 2-8 for instructions on starting installob
Note: If the setup script is interrupted, then some temporary files,
named OBnnnn or OBnnnn.Z, might remain in /usr/tmp. You can
safely delete these files.
See Also: "Setting the Key Size in obparameters" on page 6-18
Note:
■ You can also configure a preauthorized oracle user later. Before
electing to create an Oracle Secure Backup oracle user, be aware
that this choice involves a trade-off between convenience and
security.
■ If you intend to use Oracle Secure Backup to perform one-time,
RMAN-initiated, or unprivileged backup operations on Windows
clients, then you must modify the Oracle Secure Backup admin
and oracle users to assign them Windows credentials (a domain,
user name and password) that are valid at the client with
required privileges after you complete the Oracle Secure Backup
installation. Otherwise, Oracle Secure Backup cannot perform
these types of backup operations. This requirement applies
regardless of the platform that acts as the administrative server.
To Next Page
Loading...
Need help?
General