Patch Name: PHSS_18243 Patch Description: s700_800 10.X OV OB2.55 patch - ORACLE7 packet Creation Date: 99/11/04 Post Date: 99/11/12 Hardware Platforms - OS Releases: s700: 10.00 10.01 10.10 10.20 s800: 10.00 10.01 10.10 10.20 Products: OmniBackII A.02.55 Filesets: OMNIBACK-II.OMNI-ORA-P Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_18243 Symptoms: PHSS_18243: Id = NSMex01460, NSMex01819 EBU backup fails with the message "Unable to query OB2 database about set # OB2 API error is 4[0]" Id = NSMex01081 Oracle backup reports "BU-7094: Sbtinfo: System error". Id = NSMex01776 Oracle restore reports "[Error] Cannot find backup set. [ob2errno=4]". Id = NSMex01147 Oracle restore is not possible due to an error in obackup_.sh. Id = NSMex02293 Macros PANTMP, PANLIB, PANLOG, PANCFG and PANLBIN are not replaced by their effective values (absolute paths). PHSS_15425: Id = HSLco08519 OmniBack II/Oracle 7 Integration was not supported on HP-UX 11.X. PHSS_14345: Id = NSMex01071 Oracle backup session reported at the end of session several hundreds of lines with ":". Id = NSMex01163 Xomnirestore did not show all available Oracle backup sessions. Id = NSMex01075 The rds deamon died when lots of oracle backups were running at the same time causing a heavy Omniback II DB load. Id = NSMex01147 Oracle restore reports: "[Error] Cannot find backup set. [ob2errno=4]", and catalog database is not restored. Defect Description: PHSS_18243: Id = NSMex01460, NSMex01819 Backup of Oracle 7 fails with EBU error, because the database query is done for an incorrect object. Part of SSP255_070. Resolution: Database query done for the correct object. Id = NSMex01081 If the variable OB2OBK_BACKUP is set to 'no' in the obackup..sh script, OmniBack II ignores it and still runs a backup of the Oracle catalog database. Part of SSP255_110. Resolution: Obackup.sh.temp script fixed. Id = NSMex01776 An error in obackup.sh.temp caused oracle restore not to find some backup sets. If the user customized the shell script (obackup_.sh), the same error is causing the following error message: "[Error] Cannot find backup set. [ob2errno=4]". Part of SSP255_110. Resolution: Obackup.sh.temp script fixed. Id = NSMex01147 The part of the obackup_.sh script that should start the restore of the Oracle catalog database is never reached. Part of SSP255_110. Resolution: Obackup.sh.temp script fixed. Id = NSMex02293 The script obackup.sh.temp in the patch SSP255_110 was not correctly parsed and the macros were not replaced by their effective values. Part of SSP255_134. Resolution: Macros in the script obackup.sh.temp are parsed correctly. PHSS_15425: Id = HSLco08519 OmniBack II/Oracle 7 Integration was not supported on HP-UX 11.X. PHSS_14345: Id = NSMex01071 Oracle backup session reported at the end of session several hundred of lines with ":". The problem appeared if more than 350 archive logs were tried to be backed up. OmniBack II had a limit at 350. This limit is now increased up to 800 archive logs. Id = NSMex01163 Xomnirestore did not show all available Oracle backup sessions because /opt/omni/lbin/.util did not report all sessions from Oracle. The problem appeared only if Oracle EBU 2.0.12.x was used on Oracle Client host. Part of SSP255_35. Id = NSMex01075 The rds died if the session was aborted because it could not be logged to OmniBack II DB due to heavy load of the DB. This could happen if there were running lots of Oracle backups. The fix in ora_tool and libobk.sl improved query for Oracle sessions and because of that the load of the OB2DB has been decreased. Part of SSP255_38. Id = NSMex01147 A bug in obackup.sh.temp script causes the oracle restore not being able to restore oracle catalog database. SR: 1653265736 Patch Files: /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-10/A.02.55/ packet.Z /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/ A.02.55/packet.Z /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/ A.02.55/require.dat /opt/omni/databases/vendor/oracle/hp/s800/hp-ux/A.02.55/ packet.Z what(1) Output: /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-10/A.02.55/ packet.Z: None /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/ A.02.55/packet.Z: None /opt/omni/databases/vendor/oracle/hp/s800/hp-ux-1020/ A.02.55/require.dat: None /opt/omni/databases/vendor/oracle/hp/s800/hp-ux/A.02.55/ packet.Z: None cksum(1) Output: 2491254858 1011137 /opt/omni/databases/vendor/oracle/hp/ s800/hp-ux-10/A.02.55/packet.Z 349598199 1001199 /opt/omni/databases/vendor/oracle/hp/s800/ hp-ux-1020/A.02.55/packet.Z 1519165265 29 /opt/omni/databases/vendor/oracle/hp/s800/ hp-ux-1020/A.02.55/require.dat 583993342 949825 /opt/omni/databases/vendor/oracle/hp/s800/ hp-ux/A.02.55/packet.Z Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_14345 PHSS_15425 Equivalent Patches: PHSS_18244: s700: 11.00 s800: 11.00 Patch Package Size: 2960 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHSS_18243 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_18243.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_18243. If you do not wish to retain a copy of the original software, you can create an empty file named /var/adm/sw/patch/PATCH_NOSAVE. WARNING: If this file exists when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. It is recommended that you move the PHSS_18243.text file to /var/adm/sw/patch for future reference. To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_18243.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_18243: NOTE! Patch has to be installed on the Cell Server host. The Oracle7 packet needs to be redistributed to the appropriate systems, where the Oracle Clients are installed, from within the "Cell Administration - Install" window of the OmnibackII graphical user interface before the patch modifications take effect. NOTE! Shell environment variable OB2APPNAME has to be exported for the restore of database. This variable must have the same name as the ORACLE_SID of the target database, that is registered in catalog database. NOTE! Be sure that no Oracle backup or restore is running while you distribute the packet to the Oracle 7 client. NOTE! In order to resolve the Defect with the Id = NSMex01075, also the OMNIBACK II A.02.55 CS packet patch has to be installed. This is currently PHSS_16717/PHSS_16718, but may be superseded by a newer version in the future. The fix for the Defect with the Id = NSMex01163 includes the module /opt/omni/lbin/.util. This module is a part of the OMNI-CORE fileset, which is a part of every push packet. In case that any other packet is redistributed to the Oracle Client, the fixed .util will be replaced with the old .util from the OMNI-CORE of the installed packet and the fixed .util will be lost. All following OB II package patches will contain the new .util. (OB patches with a higher PHSS number) There are two workarounds to prevent overwriting the .util in the meantime: - Redistribute the Oracle packet after each redistribution of any OB2 packet to the oracle client. - or: - After patch installation, redistribute the Oracle packet to the appropriate systems, where the Oracle Clients are installed, - copy /opt/omni/lbin/.util to /opt/omni/lbin/.util.fixed. - after each redistribution of any OB2 packet copy /opt/omni/lbin/.util.fixed to /opt/omni/lbin/.util. NOTE! The support for the integration of OmniBackII / Oracle 7 with EBU 2.2 on HP-UX 10.20 is introduced with the patch PHSS_18243/PHSS_18244. The /opt/omni/lbin/.util script has also been changed. Therefore the instructions described above for the Defect with the Id = NSMex01163 have to be followed. NOTE! The support for the integration of OmniBackII / Oracle 7 on HP-UX 11.x is introduced with the patch PHSS_15425/PHSS_15426. After installing the Oracle 7 integration on the Oracle client, a new obackup.sh.temp is created in the directory /opt/omni/newconfig/etc/opt/omni/oracle/. User customized shell script must be recreated from the template file the way it has been created before (copy template file into /opt/omni/bin directory on the Oracle host, rename it into obackup_.sh, and apply customization by editing it and changing needed variables. Check Integration manual for details on this operation. The patch includes the following Site Specific Patches: SSP255_035 SSP255_038 SSP255_070 SSP255_110 SSP255_134