| Oracle® Secure Backup Readme Release 10.1.0.3 Part Number B32518-01 |
|
| View PDF |
| Oracle® Secure Backup Readme Release 10.1.0.3 Part Number B32518-01 |
|
| View PDF |
Readme
Release 10.1.0.3
B32518-01
January 2007
Purpose of this Readme
This Readme document applies only to Oracle Secure Backup Release 10.1.0.3. This Readme documents licensing, supported platforms and devices as well as known and fixed issues.
Documentation
For documentation, use your Web browser to access the Oracle Secure Backup documentation library. The library home page is named index.htm and is located in the doc directory of your CD-ROM image. You can also access the library online at the following URL:
http://www.oracle.com/technology/documentation/
Contents
Section 1, "CD-ROM Image Contents"
Section 2, "Release Components"
Section 3, "Licensing Information"
Section 4, "Upgrading Existing Oracle Secure Backup Installations to 10.1.0.3"
Section 5, "Bugs Fixed in Release 10.1.0.3"
Section 6, "Supported Tape Devices and Platforms"
Section 7, "Documentation Accessibility"
The CD-ROM image for each platform contains all necessary tools, documentation, and software to install and operate Oracle Secure Backup on the selected platform.
Note:
Each supported platform requires its own separate CD-ROM or installation Zip file. For example, if you are running an administrative domain using both Windows and Linux clients, you require separate installation media (CD-ROM or downloaded Zip file) for Windows and for Linux.You can access the installation files from a physical CD-ROM or through a Zip file downloaded from the following product site:
http://www.oracle.com/technology/products/secure-backup/
The contents of the CD-ROM and Zip file for a given platform are identical.
The only product in this release is Oracle Secure Backup.
Refer to Oracle Secure Backup Licensing Information for licensing terms.
In an upgrade installation, all information that is part of the administrative domain is retained, including backup catalogs, host data, user data, device configuration and scheduled jobs. This data is stored in the admin directory under the Oracle Secure Backup home on your administrative server.
Note:
Oracle recommends backing up the administrative server prior to any upgrade of Oracle Secure Backup.Before upgrading an existing Oracle Secure Backup administrative domain to 10.1.0.3, you must shut down Oracle Secure Backup-related drivers and background processes on all hosts. Upgrade the administrative server, host first, and then the other hosts in the domain.
Brief instructions on each step are described in the following sections.
Before performing an upgrade installation, you must stop the Oracle Secure Backup-related daemons and services on all hosts in your administrative domain.
On Linux or Unix, use the ps command to identify the Oracle Secure Backup daemon processes:
# /bin/ps -ef | grep ob
Use the kill -9 command to stop each process.
On Windows hosts, you must stop the Oracle Secure Backup Services service, and, on media servers, disable the Oracle Secure Backup device driver.
To disable the driver, in Device Manger, under Tape Drives, right-click Oracle Secure Backup Device Driver, and select Disable. Then reboot the system.
To stop the Oracle Secure Backup Services service, open the Services applet, right-click the Oracle Secure Backup Services service, and select Stop.
To upgrade a Windows installation of Oracle Secure Backup, follow the Windows installation process described in Oracle Secure Backup Installation Guide.
The Oracle Secure Backup installer takes all necessary steps to upgrade your existing installation. During the Windows upgrade process, the installer displays messages referring to uninstalling the previous version. Uninstalling the previous version of Oracle Secure Backup is part of the normal upgrade process.
Note:
On a Windows administrative server, the uninstaller program displays the following prompt:This system was configured as an Oracle Secure Backup Administrative Server. Oracle Secure Backup creates files specific to this administrative domain in the "admin" directory. Would you like to keep these files in case you reinstall Oracle Secure Backup? If you choose "Delete" all files related to Oracle Secure Backup will be removed from this system. If you choose "Keep" the files specific to this administrative domain will be retained.
Click Keep to upgrade and preserve your administrative domain data.
There are some special cases for upgrades which require attention, as described below:
Windows Installer Does Not Support Modify or Repair Installation Options
Upgrading Windows 64-Bit Systems: Manually Delete orasbt32.dll
Complete the rest of the installation process as described in Oracle Secure Backup Installation Guide.
Note:
Usually, you should specify the same host roles for each host as were used in the previous installation.When uninstalling Oracle Secure Backup on a Windows administrative server, the uninstaller allows you to click Keep, to keep files containing the record of your administrative domain and backups for use by a future installation of Oracle Secure Backup, or Delete, to delete these files and create a new administrative domain in a future installation.
However, the uninstaller from version 10.1.0.0 for Windows (32-bit and 64-bit platforms) does not correctly keep these files, if you run the uninstaller directly. The administrative domain configuration is deleted, even if you choose Keep.
To preserve the current Oracle Secure Backup configuration, just run the Windows installation program for the new version, without performing an explicit uninstall of version 10.1.0.0. Do not run the uninstaller for release 10.1.0.0 directly, and do not use the Add/Remove Programs option in the Windows Control Panel to uninstall release 10.1.0.0. The Oracle Secure Backup uninstaller takes all necessary steps to upgrade to the new version, including uninstalling the 10.1.0.0 installation and preserving your administrative domain.
If you run the installer for Oracle Secure Backup for Windows (all versions) on a system with the same version already installed, the installer displays the Modify, Repair and Remove options. Only the Remove option is correctly supported. Do not use the Modify or Repair options in the installer when installing in place over an existing installation.
When upgrading an existing Windows 64-bit installation of Oracle Secure Backup release 10.1.0.0 to release 10.1.0.2, the Microsoft Installer reports an internal error, if the file C:\Windows\system32\orasbt.dll is present when you run the Windows installer for Oracle Secure Backup release 10.1.0.2. Therefore, delete this file manually before running the installer for Oracle Secure Backup release 10.1.0.2.
Note:
If the Windows installation directory is stored in some location other than the defaultC:\Windows, then delete the file in the System32 subdirectory of the Windows installation directory.To upgrade a Linux or Unix installation of Oracle Secure Backup, follow the setup and installation process described in Oracle Secure Backup Installation Guide.
During the upgrade process, the installer displays the following prompt:
Oracle Secure Backup is already installed on this machine (myhostname-sun2). Would you like to re-install it preserving current configuration data[no]?
Enter yes to perform the upgrade installation, retaining your previous configuration.
The following tables list bugs addressed in releases of Oracle Secure Backup since the original 10.1 release.
Table 1 Bugs Fixed in Release 10.1.0.3
| Bug Number | Description |
|---|---|
|
5575021 |
Attach-Point Specification in a Device Restriction Is Not Being Honored The device restriction for a backup job can include an attach point specification, that can specify both a media device for the backup and a media server to which the tape device is attached. If a tape device had attach points to multiple media servers, then Oracle Secure Backup did not honor the media server specified in the device restriction. It was not possible to consistently predict which media server attached to the device was selected. |
|
5479541 |
Performance Improvement for Oracle Database Backups with Direct I/O in Linux The I/O buffers used for a database backup were not page aligned. This reduced the performance improvement in Linux with Direct I/O enabled. |
|
5474741 |
Cannot Browse Admin Catalogues from a Non-Admin Host The administrative service catalogues cannot be browsed from a non-admin host in an OSB domain. The Error: can't read backup section map record - wrong message type received |
|
5409398 |
Junk Characters Seen LSD -LG Output in SUSE 9 In SUSE 9, the output of |
|
5663666 |
NDMP Block Size Is Being Incorrectly Set During Backup When backing up a NAS using NDMP, the blockingfactor and the maxblockingfactor policies must be equal. If they are not equal, then the resulting volume cannot be restored. |
|
5668578 |
In Windows, Backup of File with Name Containing CTRL-Z Fails Backing up Windows files with names containing the CTRL-Z Windows end of file character are now supported correctly. |
Table 2 Bugs Fixed in Release 10.1.0.2
| Bug Number | Description |
|---|---|
|
4878473 |
Very Long Volume IDs Became Corrupted When a volume ID of 25 or more characters is used, the last six characters are required to be numeric. Previous versions of Oracle Secure Backup did not correctly enforce this requirement and generated Volume IDs that did not end with numeric characters. Oracle Secure Backup now replaces the last six characters of long volume IDs with numeric characters. |
|
5228264 |
"Device Already Opened By This Process" Error When testing whether a locally attached tape device was already in use, Oracle Secure Backup compared the SCSI channel, SCSI ID and SCSI LUN but did not compare the addresses of the SCSI adapters. This meant that a process could not simultaneously open two tape devices whose addresses differed only on adapter address. As a result, backups or other operations failed with a "Device already opened by this process" error if two media devices on different SCSI adapters had the same SCSI channel, SCSI ID and SCSI LUN values. |
|
5389348 |
Windows 2000 Client Host Database Backup Fails with Repeated Warning "unsupported message 0.0 received" A database backup from a Windows 2000 client could fail with repeated error messages sent to RMAN. The communication between RMAN and the Windows 2000 client was handled incorrectly, and caused repeated zero-length messages to be sent. In this case, the RMAN database backups no longer fail in this manner. |
|
5370286 |
"Page Not Found" Errors in Web Tool After Login Selecting a user password that was a multiple of eight characters long would make the Web tool inaccessible. |
|
5221340 |
Can Only Use Lower-Case Letters in Host Names on Windows Administrative Servers Windows administrative servers now support upper-case letters in host names. |
|
5211979 |
Tape Device Debug Logging Can Cause Backup Failures Restriction on enabling tape device-related debug logging has been removed. |
|
5207935 |
RMAN Backup Failed with RMAN-00600 Error An RMAN database backup could fail when a file system backup job was started by the scheduler during a long-running backup job. This failure no longer occurs. |
|
4398115 |
Restriction on Number of Hosts and Tape Drives with Windows Administrative Servers The previous limitation on the maximum number of hosts and tape drives supported when using a Windows host as administrative server has been removed. |
|
5149059 |
Restart Windows Media Servers and Clients When Changing Policy Parameters It is no longer necessary to restart Windows media servers when changing policy parameters. |
|
5040299 |
Database Backup Jobs Fail If Tape Device Becomes Temporarily Unavailable During Backup If the device becomes available again within the user-configured RMAN resource wait time, then the database backup job will now continue when the tape device becomes available again. |
|
5016065 |
Backup of Oracle Sparse Files Fails if Exclude Oracle Files Option is Specified The backup of a database sparse file of size greater than 2GB now succeeds on Linux when the backup excludes database temporary files. |
|
4924506 |
Device Restrictions Cannot Be Removed Via Web Browser Web tool can now remove device restrictions |
|
4736477 |
Obtool LSBU Command Not Handling '\' in Path Obtool now supports the backslash character |
|
5353546 |
Administrative Server Role Not Supported on Non-English Windows Installations Oracle Secure Backup can now be successfully configured as an administrative server on supported non-English versions of Windows. Previous limitations have been removed. |
Supported platforms, web browsers and NAS are listed on Certify on Metalink, at the following URL:
Tape drive and library matrixes are available at the following URL:
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
TTY Access to Oracle Support Services
Oracle provides dedicated Text Telephone (TTY) access to Oracle Support Services within the United States of America 24 hours a day, seven days a week. For TTY support, call 800.446.2398.
Oracle Secure Backup Readme, Release 10.1.0.3
B32518-01
Copyright © 2006, 2007, Oracle. All rights reserved.
The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited.
The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.
If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software—Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065
The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.
