Source:Oracle Requirements and Configuration
Copyright © SEP AG 1999-2024. All rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.
Overview
The procedures and features explained herein provide only information about the SEP sesam-specific parts of Oracle configuration. For detailed information on Oracle-specific backup and recovery, see Oracle database documentation. 4 4 3:Oracle Backup/en
System requirements
- Check the list of supported versions. It is recommended to upgrade the SEP sesam Server and client components to the latest version during the regular upgrade process.
- Check the SEP sesam ORACLE Licensing Whitepaper for details on the licenses required.
- Make sure that an installed Oracle server with a running Oracle application and database is available.
- Install the SEP sesam Client package on the Oracle server. You can download it from SEP Download Center. For details, see SEP Sesam Quick Install Guide.
Installation settings
The following are Oracle default installation settings. You can adjust the paths and variables according to your needs.
ORACLE SID=mydb ORACLE BASE=/opt/oracle ORACLE HOME=/opt/oracle/product/oracle $ORACLE HOME/bin is in the search path
Note | |
The library file libobk.so (Linux) or orasbt (Windows) is installed in the <sesam_install>/bin/sesam directory as a part of the SEP sesam Client package. |
Configuring Oracle
You have to configure the Oracle extension on the target Oracle server. Depending on your operating system (Linux/Unix or Windows), proceed to the relevant section below.
Linux/Unix configuration
- Login as Oracle user.
- Create a new directory sob in $ORACLE HOME.
- Create a symbolic link in $ORACLE HOME/lib to the library file libobk.so, which resides in <sesam_install>/bin/sesam. If the file already exists, you must rename it.
oracle@oraclesrv:/> cd $ORACLE_HOME oracle@oraclesrv:/product/oracle> mkdir sob oracle@oraclesrv:/product/oracle> ln -s /opt/sesam/bin/sesam/libobk.so sob/ oracle@oraclesrv:/product/oracle> ln -s /opt/sesam/bin/sesam/libobk.so lib/
Windows configuration
As of SEP sesam Jaglion, OpenSSL 1.1.1 is also used for Oracle orasbt.dll on Windows. The following procedure describes version-specific steps.
≥ SEP sesam Jaglion (5.0)
- Go to the <ORACLE HOME>\bin directory and rename the file orasbt.dll, if it exists.
- This step is only required for v. < Oracle 19c : Copy vcruntime140.dll from the <sesam_install>/bin/sesam directory to the <ORACLE HOME>\bin directory.
≤ SEP sesam Beefalo V2 (4.4.3.xx)
- Go to the <ORACLE HOME>\bin directory and rename the file orasbt.dll, if it exists.
- Copy the SEP sesam file orasbt.dll from the <sesam_install>/bin/sesam directory to the <ORACLE HOME>\bin directory.
- Encryption is enabled as of SEP sesam version 4.4.2. Copy msvcr90.dll, msvcr100.dll, cm_crypt.dll, libeay32.dll, ssleay32.dll and md5.dll from the <sesam_install>/bin/sesam directory to the <ORACLE HOME>\bin directory.
Add the Oracle client to SEP sesam environment
Configure a new client by adding it to the SEP sesam environment: Main selection -> Components -> Topology -> New client -> add your Oracle client. For details, see Configuring Clients.
Setting remote command permissions
By default, the SEP sesam Server has no rights to execute commands remotely on a SEP sesam Client, e.g., on an Oracle server. You have to specify a user in the sesam_cmdusers.allow file to run a command. For details on Windows-specific configuration of command events, see Creating a Command Event.
- To assign the proper permissions for executing commands, copy the file sesam_cmdusers_allow from the template directory on the SEP sesam Client to the /etc directory on the Oracle server. Example: cp /opt/sesam/skel/templates/sesam_cmdusers.allow /etc
- Edit the file to set the appropriate values. You will have to define the user that will execute the command, followed by the respective command. Example (referencing the example above): oracle /opt/oracle/product/10.2/db_1/sob/sbc_oracle_rman.sh