Patch Name: PHSS_14853 Patch Description: s700_800 10.X OV OB2.55 patch - CS packet Creation Date: 98/04/16 Post Date: 98/06/02 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-CS OMNIBACK-II.OMNI-SAP-P OMNIBACK-II.OMNI-SYB-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_14853 Symptoms: PHSS_14853: 1. Id = NSMex01158 Parallel restore failed with an error: Error accessing the Media Management daemon, in line 208, file rcheck.c. Media Management daemon subsystem reports: "Medium not found." 2. Id = NSMex01085 Debug.log contained message: "position linked to medium , but has no OVer connected". The problem was partly solved with PHSS_14233. 3. Id = NSMex01075 Rds deamon died if the OmniBack II DB load was very heavy and if there were running lots of Oracle backups. 4. Id = NSMex01244 After installing the PHSS_14233 omnimm -repository showed two lines for each slot. 5. Id = NSMex01220 The omnidbutil -readascii from files created with omniwrtieascii_old failed with an error reported that field #2 is invalid. PHSS_14233: 6. Id = NSMex01029 Informix logs were not backed up to the right device. 7. Id = NSMex01085 Debug.log contained message: "position linked to medium , but has no OVer connected". 8. Id = NSMex01072 Oracle, Sybase, SAP or Informix backup hanged if they were started via omnitrig. 9. Id = NSMex01043 OmniBack II reported that some of the devices were used by another session, although they were not. 10. Id = NSMex01094 The media info has been lost by barcode-rescanning. PHSS_13630: 11. Id = NSMex00949 Omniwriteascii_old program failed with "Memory fault". 12. Id = NSMex00958 The online backup of Oracle, SAP, Informix, MSSQL and Sybase failed with 'Unknown internal error'. 13. Id = NSMex00940 OmniBack II mount prompt did not show Label and Location in a mount prompt for a given medium id. Defect Description: PHSS_14853: 1. Id = NSMex01158 If there was performed filesystem, Oracle or SAP or any other parallel restore, then it could happen that OmniBack II did not find in OmniBack II DB the right medium for one of objects that needed to be restored. Because of that the parallel restore failed with an error "Medium not found". Part of SSP255_29. 2. Id = NSMex01085 Detail catalogs that were stripped by command omnidb -strip were not removed by purge session. Accessing of records after they were stripped reported "warning" in the debug.log. The problem was partly fixed with PHSS_14233. It could still happen that the "warning" message appeared if the detail catalog was stripped but not yet purged. Part of SSP255_32. 3. 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 happen if there were running lots of Oracle backups. Part of SSP255_38. 4. Id = NSMex01244 After installing the PHSS_14233 omnimm -repository showed two lines for each slot, if "Modify ..." for the library was performed before. Part of SSP255_41. 5. Id = NSMex01220 The omnidbutil -readascii from files created with omniwrtieascii_old failed with an error that field #2 is invalid. The problem happen if there was the full backup object with the start time newer than the incremental backup, which was created later than full. This can be possible, if the machine time is changed manually. Part of SSP255_42. PHSS_14233: 6. Id = MSMex01029 The first Informix log was always backed up to the first device in the barlist. Part of SSP255_08. 7. Id = NSMex01085 Detail catalogs that were stripped by command omnidb -strip were not removed by purge session. Accessing of records after they were stripped reported "warning" in the debug.log. Part of SSP255_17. 8. Id = NSMex01072 Oracle, Sybase, SAP or Informix backup hanged if they were started via omnitrig. The problem was that omnitrig did not start bar-backups with option "-no_monitor" and instead of "-no_monitor" bsm got trash ant this caused bsm to hang. Part of SSP255_18. 9. Id = NSMex01043 OmniBack II reported that some of the devices were used by another session, although they were not. The problem could occur for datalists using many devices. Part of SSP255_21. 10. Id = NSMex01094 The media info has been lost by barcode-rescanning after the library modification. Part of SSP255_23. PHSS_13630: 11. Id = NSMex00949 Omniwriteascii_old program failed with "Memory fault" during upgrade from A.02.10 if there were more than 100 media in magazine pools. Part of SSP255_02. 12. Id = NSMex00958 On database integration (SAP, Oracle, Informix, MSSQL, and Sybase ) client systems, running an online backup to multiple devices, more database streams could try to connect to the same MA as the MA's concurrency was. This would eventually lead to 'Unknown internal error'. Filesystem and raw-disk backup are not affected in this problem. Part of SSP255_04. 13. Id = NSMex00940 Medium label and location were shown as blank, if mount prompt for a specific medium in the tape library or autoloader was issued during a backup session. Part of SSP255_03. SR: 0000000000 Patch Files: /opt/omni/lbin/bsm /opt/omni/lbin/msm /opt/omni/lbin/rsm /opt/omni/lbin/rds /opt/omni/sbin/install/omniwriteascii_old /opt/omni/sbin/omnitrig /opt/omni/lib/libob2emmdb.sl /opt/omni/lib/libob2eadm.sl /opt/omni/lib/libob2ecdb.sl /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/ require.dat /opt/omni/databases/vendor/sybase/hp/s800/hp-ux-10/ require.dat what(1) Output: /opt/omni/lbin/bsm: [TZ=GMT0 /opt/omni/lbin/bsm -version] HP OpenView OmniBack II A.02.55: BSM, internal build 207, built on Mon Feb 23 12:17:03 1998 /opt/omni/lbin/msm: [TZ=GMT0 /opt/omni/lbin/msm -version] HP OpenView OmniBack II A.02.55: MSM, internal build 207, built on Mon Mar 9 09:00:46 1998 /opt/omni/lbin/rsm: [TZ=GMT0 /opt/omni/lbin/rsm -version] HP OpenView OmniBack II A.02.55: RSM, internal build 207, built on Tue Mar 10 16:02:22 1998 /opt/omni/lbin/rds: None /opt/omni/sbin/install/omniwriteascii_old: [TZ=GMT0 /opt/omni/sbin/install/omniwriteascii_old -version] HP OpenView OmniBack II A.02.55: WRITEASCIIOLD, inte rnal build 207, built on Thu Apr 9 15:19:35 1998 /opt/omni/sbin/omnitrig: [TZ=GMT0 /opt/omni/sbin/omnitrig -version] HP OpenView OmniBack II A.02.55: OMNITRIG, internal build 180, built on Wed Feb 18 10:46:39 1998 /opt/omni/lib/libob2emmdb.sl: None /opt/omni/lib/libob2eadm.sl: None /opt/omni/lib/libob2ecdb.sl: None /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/ require.dat: None /opt/omni/databases/vendor/sybase/hp/s800/hp-ux-10/ require.dat: None cksum(1) Output: 2775849178 928587 /opt/omni/lbin/bsm 2113390556 571378 /opt/omni/lbin/msm 3173832802 735739 /opt/omni/lbin/rsm 2312707329 65356 /opt/omni/lbin/rds 3191948363 1137103 /opt/omni/sbin/install/omniwriteascii_old 2437276577 337070 /opt/omni/sbin/omnitrig 2904401640 611007 /opt/omni/lib/libob2emmdb.sl 1315009172 463293 /opt/omni/lib/libob2eadm.sl 3295280144 688798 /opt/omni/lib/libob2ecdb.sl 3884124185 29 /opt/omni/databases/vendor/sap/hp/s800/ hp-ux-1020/require.dat 3203514191 21 /opt/omni/databases/vendor/sybase/hp/s800/ hp-ux-10/require.dat Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_13630 PHSS_14233 Equivalent Patches: PHSS_14854: s700: 11.00 s800: 11.00 Patch Package Size: 5490 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_14853 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_14853.depot 5b. For a homogeneous NFS Diskless cluster run swcluster on the server to install the patch on the server and the clients: swcluster -i -b This will invoke swcluster in the interactive mode and force all clients to be shut down. WARNING: All cluster clients must be shut down prior to the patch installation. Installing the patch while the clients are booted is unsupported and can lead to serious problems. The swcluster command will invoke an swinstall session in which you must specify: alternate root path - default is /export/shared_root/OS_700 source depot path - /tmp/PHSS_14853.depot To complete the installation, select the patch by choosing "Actions -> Match What Target Has" and then "Actions -> Install" from the Menubar. 5c. For a heterogeneous NFS Diskless cluster: - run swinstall on the server as in step 5a to install the patch on the cluster server. - run swcluster on the server as in step 5b to install the patch on the cluster clients. By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_14853. 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_14853.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_14853.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: NOTE! Patch has to be installed on the Cell Server host. "/opt/omni/sbin/omnisv.sh stop" must be executed on the cell server before swinstall is run. After the swinstall completes, restart OmniBackII using "/opt/omni/sbin/omnisv.sh start". NOTE! If the customer is using Oracle integration then in order to resolve Defect Number 3 (NSMex01075), also the OMNIBACK II A.02.55 ORACLE packet patch has to be installed. This is currently PHSS_14345, but may be superseded by a newer version in the future. From PHSS_14853 patch OmniBack II officially supports OmniBack/Sybase integration on HP-UX 11.x. From PHSS_14853 patch OmniBack II officially supports OmniBack/SAP-R/3 integration on HP-UX 11.x. Patch includes the following Site Specific Patches: - SSP255_02 - SSP255_03 - SSP255_04 - SSP255_08 - SSP255_17 - SSP255_18 - SSP255_21 - SSP255_23 - SSP255_26 - SSP255_29 - SSP255_32 - SSP255_38 - SSP255_41 - SSP255_42