SAP Note

Header Data

Symptom

The enhanced backup functions delivered with BR*Tools 4.5 (for example, incremental backups) require the use of one of the following backup libraries: * The SAP backup library of the BR*Tools (libsbt), or * The LSM backup library of the Legato Storage Manager (liblsm), or * The backup library of the saving tool of a third-party supplier that also implements the saving interface SBT of the Oracle Recovery Manager (RMAN). The use of such a library is optional. However, you can install it at any time after the Oracle migration or the Oracle upgrade to Release 8.1 or higher. The enhancement of the saving functionsby using a backup library is described in detail in the BR*Tools online documentation ("SAP Database Guide: Oracle" of SAP Release 6.20 or higher"). Information about the Legato Storage Manager (LSM) can be found in the Oracle documentation. The Legato Storage Manager that is delivered free of charge on the Oracle 8.1 (or higher) upgrade CD is a restricted version of the Legato NetWorker, which permits backups on up to four local tape units. In addition to the LSM backup software, the implementation of the BACKINT interface of the company Legato is also supplied free of charge. As a result, two methods are available for incremental backups: * using the SAP backup library or * using the LSM backup library with backint Of course, in addition to the native BR*Tools with cpio or dd, you can also use the backint program from Legato for normal (non-incremental) backups. Caution: As of Oracle 9.2, the Legator NetWorker software is no longer on the Oracle CD.However, you can still use the software delivered with Oracle 8.1, or you can download a trial version from www.legato.com. This note describes the installation of the SAP backup library and of the Legato Storage Manager including the LSM backup library. You can find guidelines for installating relevant products from third-party suppliers in the respective supplier documentation. After you have successfully installed the backup library of a third-party supplier and before you restart BR*Tools, test the installation with a test call of the Recovery Manager: rman nocatalog RMAN> connect target system/ RMAN> RMAN> run { allocate channel sbt type 'sbt_tape'; RMAN> backup full tag abcdefgh format 'abcdefgh.1' datafile 1; RMAN> release channel sbt; } RMAN> exit A successful test backup is confirmed by the following RMAN messages: ... RMAN-08010: channel sbt: including datafile 1 in backupset RMAN-08011: channel sbt: including current controlfile in backupset RMAN-08013: channel sbt: piece 1 created ... If, at this point, the system displays messages indicating that an error has occurred, contact the backup library supplier. Caution: -------- This test should NOT be executed for the SAP backup library - only for the backup library of a third-party supplier. To test the SAP backup library, use the following call: brbackup -u / -c -d rman_prep -t online -m all Accordingly, this call must NOT be used for third-party backup libraries. The backup_dev_type = rman_prep call is only permitted in connection with the SAP backup library.

Other Terms

Recovery Manager, RMAN

Reason and Prerequisites

Additional information for the installation.

142635 - Installation of a backup library for Oracle

Version 47 Validity: 19.07.2011 - active Language English

Released On 19.07.2011 15:40:37 Release Status Released for Customer Component BC-DB-ORA-DBA Database Administration with Oracle Priority Recommendations / Additional Info Category Installation information

A preinstallation of the Legato Storage Manager and the corresponding backup libraries is performed during the Oracle database upgrade to Version 8.1 or higher. Therefore, this version is required to use the LSM backup software free-of-charge.

Solution

1. Preparation --------------- Make the following changes before installing the backup library: * On UNIX platforms, unpack the LSM Software: Logon as Unix user ora Check whether the environment variable STAGING_AREA is set. It normally points to directory /oracle/stage/stage_805. Start shell script $STAGING_AREA/install_lsm.csh Change to directory $ORACLE_HOME/orainst Sart the Oracle installation program orainst Accept all the default proposals and confirm all of them but set directory ORACLE_BASE to $ORACLE_HOME. Once orainst is complete, execute the script root.sh that is generated by orainst in the actual directory under the root user Follow the instructions in the Readme file $ORACLE_HOME/rdbms/doc/READMELSM.doc that refers to the installation of backint program and the backint parameter file. * Check whether the init.ora profile parameter control_file_record_keep_time is set. It must be set to a value that is no smaller than 30. * Record the operating system user adm into the dba (UNIX) or record the SAPService in the ORA__DBA group (NT). You can only perform backups with RMAN under this user (for example, from the CCMS transaction DB13) if the user has SYSDBA authorization. This is a precondition of Oracle. 2. Installation of the SAP Backup Library -------------------------------------------- This installation is heavily dependent on the operating system and is, therefore, described separately for each platform. Read the additional information (postprocessing, known problems) at the end of this section. Logon as the user ora (Unix) or adm (Windows NT) and execute the following commands: 2.1. HP-UX 11 ------------- * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib/libobk.a $ORACLE_HOME/lib/libobk.a.ora and/or mv $ORACLE_HOME/lib/libobk.sl $ORACLE_HOME/lib/libobk.sl.ora * Activate the SAP backup library: ln -s /usr/sap//SYS/exe/run/libsbt.sl $ORACLE_HOME/lib/libobk.sl 2.2. TRU64 ---------- * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib/libobk.a $ORACLE_HOME/lib/libobk.a.ora and/or mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.ora * Activate the SAP backup library: ln -s /usr/sap//SYS/exe/run/libsbt.so $ORACLE_HOME/lib/libobk.so 2.3. AIX 4.3 ------------ * Rename the Oracle executable for fall back purposes to: mv $ORACLE_HOME/bin/oracle $ORACLE_HOME/bin/oracle.ora * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib64/libobk.a $ORACLE_HOME/lib64/libobk.a.ora * Activate the SAP backup library: ln -s /usr/sap//SYS/exe/run/libsbt.o $ORACLE_HOME/lib64/libobk.a * Relink the Oracle executable: cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ioracle LLIBOBK=-lobk 2.4. AIX 5.X / 6.X ------------------ * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib/libobk.a $ORACLE_HOME/lib/libobk.a.ora * Activate the SAP backup library: cp /usr/sap//SYS/exe/run/libsbt.o $ORACLE_HOME/lib/shr.o ar -X64 -crv libobk.a shr.o 2.5. SOLARIS ------------ * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib/libobk.a $ORACLE_HOME/lib/libobk.a.ora and/or mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.ora * Activate the SAP backup library: ln -s /usr/sap//SYS/exe/run/libsbt.so $ORACLE_HOME/lib/libobk.so

2.6. LINUX/INTEL ---------------- * Rename the default Oracle backup library for fall back purposes (if available) to: mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.ora * Activate the SAP backup library: ln -s /usr/sap//SYS/exe/run/libsbt.so $ORACLE_HOME/lib/libobk.so 2.7. Windows NT ---------------- * Copy the SAP backup library to the Oracle-bin directory to activate it: copy :\usr\sap\\exe\run\libsbt.dll %ORACLE_HOME%\bin\orasbt.dll * Rename the LSM backup library (if available) to: ren %WINDIR%\system32\orasbt.dll orasbt.dll.lsm * Set the following system variables (Control Panel -> System -> Advanced -> Environment Variables -> System variables): SAPDATA_HOME = SAPEXE = If you operate other Oracle databases on the same computer, set additional variables for them: _SAPDATA_HOME = If you do not find the directories saparch, sapbackup or sapreorg under Sapdata Home, you must set seperate variables for them: SAPARCH, SAPBACKUP, SAPREORG _SAPARCH, _SAPBACKUP, _SAPREORG You must then restart the computer. 2.8. Postprocessing after the installation of SAP Backup Library ----------------------------------------------------------------------- To enable you to to use all of the SAP backup library functions, execute a preparation run after the installation (not necessarily directly afterwards): brbackup -u / -c -d rman_prep -t online -m all This process replaces the compression run (brbackup -k only), and should be performed regularly (for instance once a month) or after major database changes (reorganization, upgrade, migration, mass data transfer). 3. Installation of Legato Storage Manager and LSM Backup Library ----------------------------------------------------------------------- Caution: For more detailed information about Legato software, see http://www.legato.com/lssv. 3.1. Installation of LSM Software on Unix ------------------------------------------- This software is only available for the following platforms: HP UX 10.20, DEC UNIX, AIX 32 bits and SOLARIS 32 bits Proceed as user ora as follows: * Stop the database with svrmgrl: > shutdown immediate * Execute a shell script with: $STAGING_AREA/install_lsm.csh * Start the orainst with: cd $ORACLE_HOME/orainst_sap ./orainst * Confirm all screens by choosing ENTER. * Change to the user root with the following IC command, so that the environment ora is retained: su root * Call the script root.sh: cd $ORACLE_HOME/orainst ./root.sh 3.2. Installation of LSM Software on Windows NT ------------------------------------------------- Caution: The LSM software is only available for Intel platforms. Install the LSM software with the Oracle installer: * Mount the 4.5B RDBMS CD Oracle 8.1 or higher. * Start the program SETUP.EXE from the directory: :\NT\I386\LEGATO Documentation about the LSM software can be found in PDF format in the directory: :\NT\I386\LEGATO\DOC 3.3. Postprocessing after the installation of LSM software ----------------------------------------------------------- Postprocessing is required on some platforms, so as to activate LSM software. 3.3.1. TRU64 ------------ * Rename the soft link on the LSM backup library to:

mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.lsm * Activate the LSM backup library: su root ln -s $ORACLE_HOME/lib/liblsm.so /usr/lib/libobk.so exit The soft link in /usr/lib is required due to the security precautions of DEC UNIX in connection with the S-bit of the Oracle executable. You find the network executable in the directory: /usr/opt/networker/bin. If required, enhance your PATH variable. 3.3.2. Windows NT ----------------- * Copy the LSM backup library to the Oracle-bin- directory to activate it: copy %WINDIR%\system32\orasbt.dll %ORACLE_HOME%\bin\orasbt.dll * Rename the LSM backup library to: ren %WINDIR%\system32\orasbt.dll orasbt.dll.lsm * Add the following LSM-bin directory to the dir PATH variable: :\win32app\nsr\bin Control panel -> System -> Environment -> System variables Yyou must then restart your computer. 4. Activate the BACKINT program from Legato ---------------------------------------------- * Copy the backint executable from the LSM-bin directory (the directory, where the network executable is located) into the SAP-exe directory: UNIX: cp /backint /usr/sap//SYS/exe/run NT: copy :\win32app\nsr\bin\backint.exe :\usr\sap\\SYS\exe\run * Copy the backint model profile from the LSM-bin directory into the Oracle profile directory: UNIX: cp /init.utl $ORACLE_HOME/dbs/init.utl NT: copy :\win32app\nsr\bin\init.utl %ORACLE_HOME%\database\init.utl * Adjust the init.utl profile according to the specifications from the LSM literature. 5. Notes and Known Problems -------------------------------- 5.1. Required Oracle version ------------------------------ Due to some important corrections, Oracle Version 8.0.5.1.0 or higher is required for the use of the Recovery Manager. 5.2. Change from SAP to the LSM backup library --------------------------------------------------- At any time, you can change from SAP to the LSM backup library, if you have installed both libraries. Of course, only one backup library can be active at a certain time. To do this, proceed as follows: * Stop the database with svrmgrl (Unix) or svrmgr30 (NT): > shutdown immediate * NT: Stop the Oracle service: Control Panel -> Services -> OracleService * Unix: Rename the soft link to the SAP backup library for fall back purposes, to for example: mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.sap * NT: Rename the LSM backup library for fallback purposes to: ren %ORACLE_HOME%\bin\orasbt.dll orasbt.dll.sap * Unix: Reactivate the LSM backup library: ln -s $ORACLE_HOME/lib/liblsm.so $ORACLE_HOME/lib/libobk.so or mv $ORACLE_HOME/lib/libobk.so.lsm $ORACLE_HOME/lib/libobk.so * NT: Copy the SAP backup library into the Oracle-bin directory to reactivate it: copy %WINDIR%\system32\orasbt.dll.lsm %ORACLE_HOME%\bin\orasbt.dll or ren %ORACLE_HOME%\bin\orasbt.dll.lsm orasbt.dll * NT: Start the Oracle service: Control Panel -> Services -> OracleService * Start the database with svrmgrl (Unix) or svrmgr30 (NT): > startup Caution: -------- On the AIX-4.3 platform, you must relink the Oracle executable before the database is started. The reason for this is that the LSM backup library is available in archive format and not in the shared format: cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ioracle LLIBMM=-lobk 5.3. Changing from LSM to SAP Backup Library

--------------------------------------------------- At any time, you can change from LSM to the SAP backup library, if you have installed both libraries. Of course, only one backup library can be active at a certain time. To do this, proceed as follows: * Stop the database with svrmgrl (Unix) or svrmgr30 (NT): > shutdown immediate * NT: Stop the Oracle service: Control Panel -> Services -> OracleService * Unix: Rename the soft link to the LSM backup library for fall back purposes to, for example: mv $ORACLE_HOME/lib/libobk.so $ORACLE_HOME/lib/libobk.so.lsm * NT: Rename the LSM backup library for fallback purposes to: ren %ORACLE_HOME%\bin\orasbt.dll orasbt.dll.lsm * Unix: Reactivate the SAP backup library, for example: ln -s /usr/sap//SYS/exe/run/libsbt.so $ORACLE_HOME/lib/libobk.so or mv $ORACLE_HOME/lib/libobk.so.sap $ORACLE_HOME/lib/libobk.so * NT: Copy the SAP backup library into the Oracle-bin directory to reactivate it: copy :\usr\sap\\exe\run\libsbt.dll %ORACLE_HOME%\bin\orasbt.dll or ren %ORACLE_HOME%\bin\orasbt.dll.sap orasbt.dll * NT: Start the Oracle service: Control Panel -> Services -> OracleService * Start the database with svrmgrl (Unix) or svrmgr30 (NT): > startup Caution: -------- On the AIX platform, you must relink the Oracle executable before the database is started. The reason for this is that the LSM backup library is available in archive format and not in the shared format: cd $ORACLE_HOME/rdbms/lib make -f ins_rdbms.mk ioracle LLIBMM=-lobk

Other Attributes

Validity

This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (7)

ORACLE

636847 Composite SAP note ORA-19511 505630 Composite SAP Note ORA-12547 409253 Deactivation of the Legato Storage Manager 353289 Difference between Legato Storage Manager and Legato Network 307737 libobk.* missing in installation of LSM for MCNF 187677 BRBACKUP fails with error in function WriteFile 171085 High utilization of file cache by BRBACKUP

505630 Composite SAP Note ORA-12547 187677 BRBACKUP fails with error in function WriteFile 171085 High utilization of file cache by BRBACKUP 409253 Deactivation of the Legato Storage Manager 353289 Difference between Legato Storage Manager and Legato Network 307737 libobk.* missing in installation of LSM for MCNF 636847 Composite SAP note ORA-19511

Database System