OpenText Server Backup
Oracle Plug-in for Linux Agent (64-bit)
Version 9.40.1011
Release Notes, December 5, 2024
1 Overview
1.1  Release History
1.2  Compatibility
1.3  Supported Platforms
2 NEW FEATURE
3 INSTALLATION NOTES
3.1  Installation Requirements
3.2  Licensing
3.3  Installation
4 FIXES and KNOWN ISSUES
4.1  Fixes
4.2  Known Issues
5 PRODUCT SUPPORT
5.1  Technical Support
5.2  Product Updates
5.3  Documentation

© 2024 Open Text
The release notes are governed by the Terms of Service found here. The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
1 Overview
The Oracle Plug-in is installed with the Linux Agent on a system running Oracle. Using Portal, you can manage the Agent and Plug-in, back up Oracle databases to a vault, and restore databases from the vault.
Important: Beginning in version 9.20, only a 64-bit version of the Linux Agent and Oracle Plug-in is available. 
1.1  Release History
Version 9.40.1011, December 5, 2024
1.2  Compatibility
Portal	To manage this version of the Linux Agent and Oracle Plug-in, we recommend using Portal version 9.30 or later.
Important: This agent version checks the public key of the Portal certificate when it tries to connect to Portal. If users are hosting their own Portal, we recommend updating the Portal certificate before new agents are registered to Portal or existing agents are upgraded to version 8.71 or later.	
Windows CentralControl	We do not recommend managing agents using Windows CentralControl. To take advantage of new features and important security enhancements, we highly recommend using Portal to manage the Linux Agent. 
By default, the Linux Agent cannot connect to Windows CentralControl. If you must manage the Linux Agent using Windows CentralControl 9.40, please contact Support for assistance. 
Important: Changing job configurations using Portal and Windows CentralControl alternately is not supported. Do not manage the same Agent using both Portal and Windows CentralControl. 	
Director	This version of the Linux Agent and Oracle Plug-in is supported with Director version 8.72, 8.70 and 8.56.	
1.3  Supported Platforms
This Plug-in is supported with Oracle 19c (Non-CDB), Oracle 18c (Non-CDB) and Oracle 12c R2 (Non-CDB) on the following 64-bit Linux platforms:
•	Oracle Linux Server 8 (up to Update 10) 1
•	Oracle Linux Server 7 (up to Update 9)
•	Red Hat Enterprise Linux 8 (up to Update 10) 1
•	Red Hat Enterprise Linux 7 (up to Update 9)
•	SUSE Linux Enterprise Server 15 (up to Service Pack 5) 2
•	SUSE Linux Enterprise Server 12 (up to Service Pack 5) 2
1 When the Oracle Plug-in is installed on this platform, the libnsl package must also be installed or the agent will not start.
2 This platform is not supported when the BTRFS file system is used.	
2 NEW FEATURE
This plug-in version is compatible with Linux Agent version 9.40 (64-bit).
3 INSTALLATION NOTES
3.1  Installation Requirements
•	 Linux Agent version 9.40 must already be installed on the system.
•	The Agent and Oracle Plug-in must be installed on the system that has the Oracle database server.
3.2  Licensing
A vault-side Oracle Plug-in license is required. This allows the Agent and Plug-in to connect to the vault.
3.3  Installation
The file name of the Oracle Plug-in installation kit is: Oracle-Plugin-Linux-x64-9.40.1011.tar.gz
The Agent kit installs the following binary files:
Binary File	md5sum Value	
libclntsh.so.11.1	2c5b428a3bb045f0d7dbb66b21cfe4ff	
libnnz11.so	d539555cf0c6f2807c5435e9c61fc79f	
libociei.so	f4e6b48d3d827ba3abd51045d824886f	
oracle.so	ec279457919a28445321f4dfce0d5d9a	
oratool	74afa67bd0f5889a3f80869c61691fbf	
RegPlugins	304510919c21d66e5417710a97f0e642	
To obtain md5sum values, issue the following commands. These commands are examples based on an Agent that has been installed in the default location (i.e., /opt/BUAgent).
 cd /opt/BUAgent
 md5sum *
4 FIXES and KNOWN ISSUES
4.1  Fixes
There are no fixes in this version.
4.2  Known Issues
•	When the Oracle Plug-in is installed with the Linux Agent on Oracle Linux Server 8 or Red Hat Enterprise Linux 8, the agent will not start if the libnsl package is not installed on the system. 
WORKAROUND: Install the libnsl package on the Oracle Linux Server 8 or Red Hat Enterprise Linux 8 system. (2464184/EV-40383)
•	When an Oracle database is first backed up after the database is changed from NOARCHIVELOG mode to ARCHIVELOG mode, the database’s archived redo logs may not be backed up.
WORKAROUND: Run the Oracle database backup job a second time after the database is changed from NOARCHIVELOG mode to ARCHIVELOG mode to back up the archived redo logs. (2472719/EV-19604)
•	A duplicate error message may appear in the Oracle backup log for a failed job ("UTIL-F-8266 Fatal error in processing Job"). This is a cosmetic issue that may result from a StreamError exception that occurs in more than one location. (19344)
•	The Oracle Plug-in has been tested in several data recovery scenarios. In the case of a full disaster recovery (where the full database instance is being restored), some care must be exercised on recovery of the database as the Oracle Plug-in does not back up temporary tablespaces and the control file information kept in the trace file may not include any commands to add a temporary tablespace.
1. The database recovery may be initiated with an explicit PFILE or SPFILE reference:
SQL> STARTUP mount PFILE='path-to-pfile\initSIDNAME.ora'
2. It may be necessary to take the temporary tablespace datafiles offline:
SQL> ALTER DATABASE DATAFILE 'path-to-datafile' OFFLINE
3. The database may be recovered as normal, but when opening the database after recovery the command should be:
SQL> ALTER DATABASE OPEN NORESETLOGS
4. Temporary tablespaces may be dropped, the datafiles for the temporary tablespaces removed, and the temporary tablespaces may be recreated (this may include the default TEMP tablespace).
At this point in the recovery, the database can be closed normally and restarted with RESETLOGS if that is your organization's policy.
Note: These are not recovery steps, but guidelines for recovery.
5 PRODUCT SUPPORT
5.1  Technical Support
Contact information for your provider is available through the Need Help button in Portal.
5.2  Product Updates
Product updates are available through your provider.
5.3  Documentation
The following documentation is available for this product: 
•	Server Backup online help and knowledge base
•	Release notes (this document)
•	User Guide