Patch Name: PHSS_18235 Patch Description: s700_800 10.X OV OB2.55 patch - CS packet Creation Date: 99/10/01 Post Date: 99/10/21 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 OMNIBACK-II.OMNI-DA-P Automatic Reboot?: No Status: General Superseded Critical: No Path Name: /hp-ux_patches/s700_800/10.X/PHSS_18235 Symptoms: PHSS_18235: Id = NSMex02751 RBDA is not aborted by omniabort. Id = NSMex02098 Backup of OmniBack II database fails with an error: "Change log cycle timeout". Id = NSMbb23655 Writeascii does not work if one of the output files is bigger than 2GB. Id = NSMex01954 Multiple devices try to use the same medium. Id = NSMex02067 During the backup the following message appears: "Error accessing the database, in line 455, file bdata.c.". Database subsystem reports: "Filenames database is probably corrupted. Please run omnidbcheck!" Id = NSMex02229 Browsing of SAP objects in xomnirestore GUI fails with an error: "Cannot browse from root. Please specify starting point". Id = NSMex02440, NSMex02101 Oracle full backup appended in 'append incremental only' pool. Id = NSMex01842, HSLco12682 writeacsii and readascii not possible for a particular host in a cell. PHSS_16717: Id = NSMex01922 After installation of PHSS_16711/PHSS_16712 the following agents can not be pushed any more: SAP on HP-UX 11.x, Sybase on HP-UX 11.x and DA on AIX 4.3. Id = NSMex01318 "su -" in datalist pre exec or post exec is not supported. PHSS_16711: Id = NSMbb19824 Bma aborted with "Can not write to device (Error 0)", but session exit status is 0 (no errors). Id = HSLco10777 Media agent hangs, if a disk agent host is unreachable when backup session is started. Id = NSMex01624 'omnidbutil -change_cell_name old_host' fails if hostname resolution has been changed (from short to long, or v. v.). Id = HSLco10236 No information about initialized media in the media.log file. Id = HSLco10242 Backup session exit status is 11 (Completed/failures) if disk agent host is not reachable at session start, but it is backed up successfully when retried later. Id = NSMex01657 If there is specified more than 900 file or directory names for backup or restore then some files or directories are not backed up or restored and OmniBack II does not report anything. Id = NSMex01615 After OmniBack II internal database restore, some tapes cannot be imported because sessions already exist in the database. PHSS_15774: Id = NSMbb18903 omnimm -repository_update failed with an exit status 11 even if there were no errors. Id = HSLco09808 BSM dying with 'Not enough space'. Id = NSMex01539 Corrupted database after killing the dbbda agent. Killing the omnidbcheck command left database in hot backup mode. Database backup or omnidbcheck could also report 'Database check already running' after that. Id = NSMex01586 Wrong media listed in backup preview. Id = NSMex00941 Sybase backup hung. Id = NSMex01237 Rds deamon died with the following error reported in /var/opt/omni/log/RDS.log: "Specific problem: db_level less than zero" Id = HSLco09129 RDS deamon died with the following error reported in /var/opt/omni/log/RDS.log: "cannot extend database". Id = NSMex01199 Omnistat did not show session in mount prompt. Id = NSMex01210 Performances of Omniback II were worse if upgraded from A.02.10, or after running the omnidbutil -writeascii readascii procedure. Id = NSMex01188 Overwrite, initialization or export of tapes took very long. Id = NSMex01284 Slow restore of Informix Logical logs. Id = NSMbb18530 During backup of Informix dbspaces devices were locked even if they were not used. Id = NSMex01002 OmniBack II DB did not report any error indicating that the DB was full and there was not enough space for new record. Id = NSMex01420 If more than one tape was imported at once then the import failed with an error: "Can not lock database - currently unavailable." Id = NSMex01193 User did not see a backup even if he was the owner of it. PHSS_14853: 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." Id = NSMex01085 Debug.log contained message: "position linked to medium , but has no OVer connected". The problem was partly solved with PHSS_14233. Id = NSMex01075 Rds deamon died if the OmniBack II DB load was very heavy and if there were running lots of Oracle backups. Id = NSMex01244 After installing the PHSS_14233 omnimm -repository showed two lines for each slot. Id = NSMex01220 The omnidbutil -readascii from files created with omniwrtieascii_old failed with an error reported that field #2 is invalid. PHSS_14233: Id = NSMex01029 Informix logs were not backed up to the right device. Id = NSMex01085 Debug.log contained message: "position linked to medium , but has no OVer connected". Id = NSMex01072 Oracle, Sybase, SAP or Informix backup hanged if they were started via omnitrig. Id = NSMex01043 OmniBack II reported that some of the devices were used by another session, although they were not. Id = NSMex01094 The media info has been lost by barcode-rescanning. PHSS_13630: Id = NSMex00949 Omniwriteascii_old program failed with "Memory fault". Id = NSMex00958 The online backup of Oracle, SAP, Informix, MSSQL and Sybase failed with 'Unknown internal error'. Id = NSMex00940 OmniBack II mount prompt did not show Label and Location in a mount prompt for a given medium id. Defect Description: PHSS_18235: Id = NSMex02751 If reconnect option is used for backup and backup is aborted, Disk Agent processes are not terminated for another 30 minutes. Resolution: Fix is implemented in BSM. Id = NSMex02098 A change log cycle timed out while processing a call to start hot backup. The error message: "Change log cycle timeout" is reported. Part of the SSP255_126. Resolution: New OB2 variable OB2DBRETRY is added. Id = NSMbb23655 Omniback ascii write fails, with no warnings, when the ascii file reaches the 2Gb file limit. There are no errors generated when the limit is reached so when the customer reads in the ascii file, the ascii read aborts. Part of the SSP255_132. Resolution: Library for writeascii is compiled with special options in order to support files that exceed 2GB. Id = NSMex01954 If large number of media (>250) is in use at the same time, the table for media locking exceeds its limit and locking does not work properly anymore. Part of the SSP255_133. Resolution: The mechanism for locking the media is fixed. Id = NSMex02067 The database gets corrupted when 2000000 files in directory limitation is exceeded. Part of the SSP255_135. Resolution: When the limitation is reached, the warning message: "[CiFNameGetAndCmp] Maximum files per directory limit was reached! Change the global option DbMaxFilesInDir or try the-log_dirs option on backup" is printed into /var/opt/omni/log/debug.log file and the database is not corrupted. Id = NSMex02229 If the tape with SAP session is imported and the catalog of the session did not exist in the DB before, the browsing fails with an error: "Cannot browse from root. Please specify starting point". Part of the SSP255_139. Resolution: Fix implemented in libob2ecdb.sl. Id = NSMex02440, NSMex02101 BSM incorrectly appends Oracle full backup media. Resolution: Fix implemented in BSM. Id = NSMex01842, HSLco12682 It is not possible to do selective import or export of the OB database only for the hosts with problems within a cell. Resolution: New option '-read_hosts' added to omnidbutil. PHSS_16717: Id = NSMex01922 After installation of PHSS_16711/PHSS_16712 patch the push installation of SAP to HP-UX 11.x, Sybase to HP-UX 11.x and DA to AIX 4.3 fails with an error that it not supported on the particular operating system. Resolution: Id = NSMex01318 "su -" in datalist prer-exec or post-exec is not supported. PHSS_16711: Id = NSMbb19824 Session exit status 0 (no errors) in case of BMA aborting because of I/O error "Can not write to device (Error 0)" is misleading, and makes the user think there were no problems at backup time, although the data hasn't been saved at all. The new exit codes of the omnib command and Session Manager will be set as follows: exit code Meaning --------- ------------------------------------------- 0 All files were successfully backed up. 10 backup completed successfully with non-critical occurence. 11 Some Agents failed (at least one object succeeded), or there was a database error. 12 None of the Agents completed the operation. 13 Session was aborted. NOTE: Agent means any of OmniBack component as for example: Disk Agent, Media Agent, BAR Agent, etc. Id = HSLco10777 If a disk agent host (filesystem backup) is not accessible at the backup session start time, it will later cause hang of media agent, because other disk agents that have been started successfully at the session start (on accessible hosts) are not correctly disconnected. Id = NSMex01624 Changing hostname resolution on the Cell Server system causes problems to omnidbutil executable, because it uses default system hostname resolution. The effect is that 'omnidbutil -change_cell_name old_host' doesn't recognize objects with old hostname (before hostname resolution has been changed) and doesn't change the objects in the db. Part of SSP255_87. Id = HSLco10236 Information about media that has been initialized by OB2 is valuable if any problems with the internal database appear. Currently, /var/opt/omni/log/media.log doesn't contain this info. Id = HSLco10242 Backup session exit status should be 0 (completed successfully), if the disk agent host is not reachable at the session start, but can be reached later, when the session retries to connect to it. This way, all the objects are backed up successfully, and such session shouldn't have the exit status 11 (Completed/failures). Id = NSMex01657 If there is specified more than 900 file or directory names for backup or restore then some files or directories are not backed up or restored and OmniBack II does not report anything. With the patch OmniBack II will report an error and it will not start disk agent. In that case decrease number of filenames or directories and restart backup or restore. Id = NSMex01615 If there are some sessions started after OB2 internal database restore, the same session Ids are are assigned to them as for the sessions already on the tape, but not in the restored datbase yet. This causes old tapes not being able to be imported. PHSS_15774: Id = NSMbb18903 If a logical device has a "cleaning slot" defined then omnimm -repository_update failed with an exit code 11. Part of SSP255_82. Id = HSLco09808 Dynamic datalist backup of more than 500 objects more than one device caused MA queues to grow over memory limit. This caused BSM to die, and the backup session to fail. Part of SSP255_77. Id = NSMex01539 Killing the dbbda agent could corrupt the database because of bad signal handling. If omnidbcheck was killed, the database remained in hot backup mode until OmniBacK II deamons were restarted. This could lead to a database corruption because of the hot backup swap file growing over the limit. Killing the dbbda agent resulted also in the error message 'Database check already running' even if there was no database check process running. Part of SSP255_78. Id = NSMex01586 If there was some pre-allocated media for a backup device, this media was not listed when backup preview was started. Part of SSP255_79. Id = NSMex00941 Sybase backup hung if one database was backed to more than two logical devices. Part of SSP255_43. Id = NSMex01237 Rds deamon died with the following error reported in /var/opt/omni/log/RDS.log: "Specific problem: db_level less than zero". Part of SSP255_44. Id = HSLco09129 RDS deamon died with the following error reported in /var/opt/omni/log/RDS.log: "cannot extend database". Id = NSMex01199 If the CRS session table size was 200, the session came into mount prompt state, and after that more than 200 sessions were started, then the session could not be seen with omnistat command. Part of SSP255_51. Id = NSMex01210 Omniback II 2.55 performance of the DB and of the omnidbutil -writeascii readascii operation performed on the OmniBack II DB could be improved: 1. During the writeascii process the records are also purged now. In this way the DB can get significantly smaller than before. 2. The readascii process creates a less fragmented database now. The new option "-optimize" is now available for the writeascii process and for omniwriteascii_old. Part of SSP255_59. Id = NSMex01188 Overwrite, export and initialization of tapes with expired protection took very long if there were sessions with more than 3000 messages. In order to limit the number of messages per object the new global option SmMaxAgentMessages has been created. By this option the number of messages received from one agent can be limited. So the number of messages in the database can be significantly decreased. This reduces the time that is needed to export the medium from the database. Part of SSP255_61. Id = NSMex01284 During restore of each Informix logical log the tape was ejected and imported back. This caused very slow restore of Informix logs. Id = NSMbb18530 During backup of Informix dbspaces devices were locked even if they were not used at a particular time. Id = NSMex01002 OmniBack II DB did not report any error indicating that the DB was full and there was not enough space for new record. Now the following error message reported: "Database record limit per file has been reached." Id = NSMex01420 Parallel import of more than 3 tapes took very long. Id = NSMex01193 A user did not see a backup even if he was the owner of it. This problem only happened if the user had "." in his username, the user was not in the "Admin" class, the user did not have the Accees Right "Restore from other Users", and the backup was made as private. Part of SSP255_48. PHSS_14853: 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. 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. 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. Id = NSMex01244 After installing the PHSS_14233/PHSS_14234 patch omnimm -repository showed two lines for each slot, if "Modify ..." for the library was performed before. Part of SSP255_41. 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: Id = MSMex01029 The first Informix log was always backed up to the first device in the barlist. Part of SSP255_08. 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. 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. 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. Id = NSMex01094 The media info has been lost by barcode-rescanning after the library modification. Part of SSP255_23. PHSS_13630: 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. 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. 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: 5003456814 5003460691 1111111111 5003427716 5003429589 5003430231 5003428896 5003430215 5003417303 5003418053 1653256396 5003430199 Patch Files: /opt/omni/lbin/bsm /opt/omni/lbin/msm /opt/omni/lbin/rsm /opt/omni/lbin/rds /opt/omni/lbin/dbbda /opt/omni/lbin/psm /opt/omni/lbin/dbsm /opt/omni/lbin/mmd /opt/omni/lbin/crs /opt/omni/sbin/install/omniwriteascii_old /opt/omni/sbin/install/omni_inst.sh /opt/omni/sbin/omnitrig /opt/omni/sbin/utilns/rdsadm /opt/omni/sbin/utilns/dbcheck /opt/omni/sbin/utilns/dal /opt/omni/sbin/utilns/dbreplay /opt/omni/sbin/utilns/keybuild /opt/omni/sbin/utilns/dbrepair/dbrepair.tar /opt/omni/sbin/utilns/checkext.pl /opt/omni/sbin/omnidbutil /opt/omni/sbin/omnidbcheck /opt/omni/sbin/omnidbinit /opt/omni/lib/libob2emmdb.sl /opt/omni/lib/libob2eadm.sl /opt/omni/lib/libob2ecdb.sl /opt/omni/lib/libCadm.sl /opt/omni/lib/libCdict.sl /opt/omni/lib/libCenc.sl /opt/omni/lib/libCncp.sl /opt/omni/lib/libCrdbc.sl /opt/omni/lib/libCrdm.sl /opt/omni/lib/libCrm.sl /opt/omni/lib/libCrpc.sl /opt/omni/lib/libCuapi.sl /opt/omni/lib/lib_adm.sl /opt/omni/lib/lib_dbimp.sl /opt/omni/lib/lib_ddlp.sl /opt/omni/lib/lib_dict.sl /opt/omni/lib/lib_eadm.sl /opt/omni/lib/lib_edbc.sl /opt/omni/lib/lib_ekeyb.sl /opt/omni/lib/lib_enc.sl /opt/omni/lib/lib_erdm.sl /opt/omni/lib/lib_exif.sl /opt/omni/lib/lib_gw.sl /opt/omni/lib/lib_ncp.sl /opt/omni/lib/lib_rdbc.sl /opt/omni/lib/lib_rdm.sl /opt/omni/lib/lib_rm.sl /opt/omni/lib/lib_rpc.sl /opt/omni/lib/lib_sched.sl /opt/omni/lib/lib_sddlp.sl /opt/omni/lib/lib_sief.sl /opt/omni/lib/lib_sql.sl /opt/omni/lib/lib_sudf.sl /opt/omni/lib/lib_sudp.sl /opt/omni/lib/lib_uapi.sl /opt/omni/lib/libob2ecmn.sl /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.55/ require.dat /opt/omni/databases/vendor/sybase/hp/s800/hp-ux-10/A.02.55/ require.dat /opt/omni/databases/vendor/da/ibm/rs6000/aix-42/A.02.55/ 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 1000, built on Mon Sep 27 10:25:37 1999 /opt/omni/lbin/msm: [TZ=GMT0 /opt/omni/lbin/msm -version] HP OpenView OmniBack II A.02.55: MSM, internal build 1000, built on Mon Sep 27 11:23:47 1999 /opt/omni/lbin/rsm: [TZ=GMT0 /opt/omni/lbin/rsm -version] HP OpenView OmniBack II A.02.55: RSM, internal build 1000, built on Mon Sep 27 10:27:10 1999 /opt/omni/lbin/rds: None /opt/omni/lbin/dbbda: [TZ=GMT0 /opt/omni/lbin/dbbda -version] HP OpenView OmniBack II A.02.55: DBBDA, internal bui ld 1000, built on Mon Sep 27 14:30:16 1999 /opt/omni/lbin/psm: [TZ=GMT0 /opt/omni/lbin/psm -version] HP OpenView OmniBack II A.02.55: PSM, internal build 1000, built on Mon Sep 27 10:49:25 1999 /opt/omni/lbin/dbsm: [TZ=GMT0 /opt/omni/lbin/dbsm -version] HP OpenView OmniBack II A.02.55: DBSM, internal buil d 1000, built on Mon Sep 27 10:38:52 1999 /opt/omni/lbin/mmd: [TZ=GMT0 /opt/omni/lbin/mmd -version] HP OpenView OmniBack II A.02.55: MMD, internal build 1000, built on Mon Sep 27 11:30:36 1999 /opt/omni/lbin/crs: [TZ=GMT0 /opt/omni/lbin/crs -version] HP OpenView OmniBack II A.02.55: CRS, internal build 1000, built on Mon Sep 27 14:00:10 1999 /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 223, built on Mon Jul 6 14:56:50 1998 /opt/omni/sbin/install/omni_inst.sh: None /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/sbin/utilns/rdsadm: None /opt/omni/sbin/utilns/dbcheck: None /opt/omni/sbin/utilns/dal: None /opt/omni/sbin/utilns/dbreplay: None /opt/omni/sbin/utilns/keybuild: None /opt/omni/sbin/utilns/dbrepair/dbrepair.tar: None /opt/omni/sbin/utilns/checkext.pl: None /opt/omni/sbin/omnidbutil: [TZ=GMT0 /opt/omni/sbin/omnidbutil -version] HP OpenView OmniBack II A.02.55: OMNIDBUTIL, interna l build 1000, built on Tue Sep 28 10:17:46 1 999 /opt/omni/sbin/omnidbcheck: [TZ=GMT0 /opt/omni/sbin/omnidbcheck -version] HP OpenView OmniBack II A.02.55: OMNIDBCHECK, intern al build 1000, built on Tue Sep 28 10:17:54 1999 /opt/omni/sbin/omnidbinit: [TZ=GMT0 /opt/omni/sbin/omnidbinit -version] HP OpenView OmniBack II A.02.55: OMNIDBINIT, interna l build 1000, built on Tue Sep 28 10:17:29 1 999 /opt/omni/lib/libob2emmdb.sl: None /opt/omni/lib/libob2eadm.sl: None /opt/omni/lib/libob2ecdb.sl: None /opt/omni/lib/libCadm.sl: None /opt/omni/lib/libCdict.sl: None /opt/omni/lib/libCenc.sl: None /opt/omni/lib/libCncp.sl: None /opt/omni/lib/libCrdbc.sl: None /opt/omni/lib/libCrdm.sl: None /opt/omni/lib/libCrm.sl: None /opt/omni/lib/libCrpc.sl: None /opt/omni/lib/libCuapi.sl: None /opt/omni/lib/lib_adm.sl: None /opt/omni/lib/lib_dbimp.sl: None /opt/omni/lib/lib_ddlp.sl: None /opt/omni/lib/lib_dict.sl: None /opt/omni/lib/lib_eadm.sl: None /opt/omni/lib/lib_edbc.sl: None /opt/omni/lib/lib_ekeyb.sl: None /opt/omni/lib/lib_enc.sl: None /opt/omni/lib/lib_erdm.sl: None /opt/omni/lib/lib_exif.sl: None /opt/omni/lib/lib_gw.sl: None /opt/omni/lib/lib_ncp.sl: None /opt/omni/lib/lib_rdbc.sl: None /opt/omni/lib/lib_rdm.sl: None /opt/omni/lib/lib_rm.sl: None /opt/omni/lib/lib_rpc.sl: None /opt/omni/lib/lib_sched.sl: None /opt/omni/lib/lib_sddlp.sl: None /opt/omni/lib/lib_sief.sl: None /opt/omni/lib/lib_sql.sl: None /opt/omni/lib/lib_sudf.sl: None /opt/omni/lib/lib_sudp.sl: None /opt/omni/lib/lib_uapi.sl: None /opt/omni/lib/libob2ecmn.sl: None /opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.02.55/ require.dat: None /opt/omni/databases/vendor/sybase/hp/s800/hp-ux-10/A.02.55/ require.dat: None /opt/omni/databases/vendor/da/ibm/rs6000/aix-42/A.02.55/ require.dat: None cksum(1) Output: 1025828237 944054 /opt/omni/lbin/bsm 1530170538 574824 /opt/omni/lbin/msm 3006343435 747194 /opt/omni/lbin/rsm 2595521150 61628 /opt/omni/lbin/rds 2177894283 287457 /opt/omni/lbin/dbbda 4122357816 324416 /opt/omni/lbin/psm 170933457 537757 /opt/omni/lbin/dbsm 3890543458 390170 /opt/omni/lbin/mmd 1585123586 763803 /opt/omni/lbin/crs 447186708 973270 /opt/omni/sbin/install/omniwriteascii_old 2226509539 134268 /opt/omni/sbin/install/omni_inst.sh 2437276577 337070 /opt/omni/sbin/omnitrig 4052232741 102826 /opt/omni/sbin/utilns/rdsadm 1730758826 65756 /opt/omni/sbin/utilns/dbcheck 2673019983 135566 /opt/omni/sbin/utilns/dal 1170995233 65741 /opt/omni/sbin/utilns/dbreplay 2437681905 61664 /opt/omni/sbin/utilns/keybuild 1544380655 901120 /opt/omni/sbin/utilns/dbrepair/ dbrepair.tar 843974101 5691 /opt/omni/sbin/utilns/checkext.pl 2654275690 492514 /opt/omni/sbin/omnidbutil 3964146346 328428 /opt/omni/sbin/omnidbcheck 1509284677 344870 /opt/omni/sbin/omnidbinit 2744664747 614973 /opt/omni/lib/libob2emmdb.sl 397686407 500070 /opt/omni/lib/libob2eadm.sl 2771665522 713257 /opt/omni/lib/libob2ecdb.sl 2174708144 131404 /opt/omni/lib/libCadm.sl 1412299764 78161 /opt/omni/lib/libCdict.sl 2965434340 12323 /opt/omni/lib/libCenc.sl 418812920 69900 /opt/omni/lib/libCncp.sl 4204456602 303724 /opt/omni/lib/libCrdbc.sl 1289722776 147946 /opt/omni/lib/libCrdm.sl 3207749248 65739 /opt/omni/lib/libCrm.sl 2420168647 110933 /opt/omni/lib/libCrpc.sl 2749092630 12310 /opt/omni/lib/libCuapi.sl 2152943177 262690 /opt/omni/lib/lib_adm.sl 405549788 73842 /opt/omni/lib/lib_dbimp.sl 1503661844 192804 /opt/omni/lib/lib_ddlp.sl 3144958793 74055 /opt/omni/lib/lib_dict.sl 2138453587 110985 /opt/omni/lib/lib_eadm.sl 1094011087 209271 /opt/omni/lib/lib_edbc.sl 2594396229 41054 /opt/omni/lib/lib_ekeyb.sl 873320625 16443 /opt/omni/lib/lib_enc.sl 454838142 115256 /opt/omni/lib/lib_erdm.sl 3310124617 12304 /opt/omni/lib/lib_exif.sl 1973688181 20622 /opt/omni/lib/lib_gw.sl 2924323883 82182 /opt/omni/lib/lib_ncp.sl 1121454108 303726 /opt/omni/lib/lib_rdbc.sl 39150278 738999 /opt/omni/lib/lib_rdm.sl 544663819 209698 /opt/omni/lib/lib_rm.sl 1050384583 106861 /opt/omni/lib/lib_rpc.sl 2022357118 53397 /opt/omni/lib/lib_sched.sl 806643465 291170 /opt/omni/lib/lib_sddlp.sl 1093077333 41048 /opt/omni/lib/lib_sief.sl 3929381247 1136313 /opt/omni/lib/lib_sql.sl 2748570456 24638 /opt/omni/lib/lib_sudf.sl 2768892497 94316 /opt/omni/lib/lib_sudp.sl 3835820014 12310 /opt/omni/lib/lib_uapi.sl 3901524796 664505 /opt/omni/lib/libob2ecmn.sl 3884124185 29 /opt/omni/databases/vendor/sap/hp/s800/ hp-ux-1020/A.02.55/require.dat 3203514191 21 /opt/omni/databases/vendor/sybase/hp/s800/ hp-ux-10/A.02.55/require.dat 3074109166 21 /opt/omni/databases/vendor/da/ibm/rs6000/ aix-42/A.02.55/require.dat Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_13630 PHSS_14233 PHSS_14853 PHSS_15774 PHSS_16711 PHSS_16717 Equivalent Patches: PHSS_18236: s700: 11.00 s800: 11.00 Patch Package Size: 15980 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_18235 5a. For a standalone system, run swinstall to install the patch: swinstall -x autoreboot=true -x match_target=true \ -s /tmp/PHSS_18235.depot By default swinstall will archive the original software in /var/adm/sw/patch/PHSS_18235. 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_18235.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_18235.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHSS_18235: 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". NOTES! From PHSS_16711/PHSS_16712 patch OmniBack II includes new Velocis libraries - version 349. After installing the Cell Server patch, set the session ID counter to a value, higher than the last session created on the day when database restore took place. This will enable importing the backup tapes created after the database backup. The command for this operation is: /opt/omni/sbin/omnidbutil -set_session_counter . NOTE! If you are using the Oracle integration then in order to resolve Defect with Id NSMex01075, you must install also the OMNIBACK II A.02.55 ORACLE 7 packet patch. This is currently PHSS_15425, but may be superseded by a newer version in the future. PHSS_15774/PHSS_15775: From PHSS_15774/PHSS_15775 patch OmniBack II officially supports Disk Agents on IBM Aix 4.3. From PHSS_15774/PHSS_15775 on, OmniBack II includes new database libraries - version 340. These libraries fix problems associated with the 'RDS dying' mentioned above in the Symptoms and Defect Description. They also significantly improve Omniback II's performance when it backs up it's internal database or checks it with the omnidbcheck command. From PHSS_15774/PHSS_15775 on, the omnidbutil command offers an improved writeascii / readascii procedure. It is started by using the additional new -optimize option. With this new option, the writeascii procedure automatically purges obsolete data from the database. After the corresponding readascii was performed, the access to the database is much faster. This applies in particular to the omnidbutil -purge and omnidbcheck commands. Attention! A disadvantage of the modified writeascii / readascii procedure is that it needs much memory space. In order to avoid readascii failures like 'not enough memory', it is recommended to increase the maxdsize (Maximum Data Segment Size) kernel parameter to at least 128 MB. From PHSS_15774/PHSS_15775 on, it is possible to suspend purge while omnidbcheck is running. To do so, add the following global option to the /etc/opt/omni/options/global file: DBPurgeSuspensionDuringDBCheck=1 If this option is set (=1), purge session manager (PSM) will suspend its execution while database check is in progress. By default the option is set to 1. From PHSS_15774/PHSS_15775 patch it is possible to limit number of reported messages per object by adding the following global option to the /etc/opt/omni/options/global file: SmMaxAgentMessages By default this option is set to 3000. It specifies the maximum number of messages from a single Disk Agent that the Backup/Restore Session Manager will store in the internal database. When this limit is exceeded, a warning is displayed that no more messages from this particular agent will be stored. However, these additional messages are still visible in the Session Monitor while the session is alive. This limitation of stored messages speeds up exporting of media from the OmniBack II DB. The size of the database extension files should not be set to 2 GB. Please run the script: /opt/omni/sbin/utilns/checkext.pl to check the size of all extension files. Users who experience the following error during running the script checkext.pl: "The extension file will not be resized. Please check the patch installation instructions for info on resizing the extension files!" have sizes of OmniBack II database extension files set to 2GB. Sometimes it happens that OmniBack II cannot add records to a new extension file if an old one has a size of 2 GB. To avoid this problem, run the following script: /opt/omni/sbin/utilns/checkext.pl -force The script decreases the size of all extended DB files with a size of 2048 MB to the size of 2047 MB. If it cannot decrease the size to 2047 MB because the actual size of the extended file already exceeds 2047 MB, then please contact HP support in order to get instructions on how to decrease the size of extension files manually. PHSS_14853/PHSS_14854 From PHSS_14853/PHSS_14854 patch OmniBack II officially supports OmniBack/Sybase integration on HP-UX 11.x. From PHSS_14853/PHSS_14854 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 - SSP255_43 - SSP255_44 - SSP255_48 - SSP255_51 - SSP255_59 - SSP255_61 - SSP255_77 - SSP255_78 - SSP255_79 - SSP255_82 - SSP255_82 - SSP255_87