|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback
us-support.external.hp.com)Date: Sun Jan 27 2002 - 09:15:06 CST
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
http://www.itresourcecenter.hp.com/
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 800 10.X patch digest
Created: Sun Jan 27 3:05:07 PST 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_25952 s700_800 10.X OV OB3.10 patch - CC packet
PHSS_25946 s700_800 10.20 OV OB4.00 patch - CS packet
PHSS_25819 s700_800 10.X OV OB3.50 patch - CORE packet
PHSS_25817 s700_800 10.X OV OB3.50 patch - SSEA packet
PHSS_21873 s700_800 10.X OV OB3.00 patch - INFORMIX packet
PHSS_25988 s700_800 10.20 OV SAPSPI7.X Monitor bin.s A.07.23
PHSS_25370 s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_25952
Date Loaded: 20020125
Title: s700_800 10.X OV OB3.10 patch - CC packet
Patch Name: PHSS_25952
Patch Description: s700_800 10.X OV OB3.10 patch - CC packet
Creation Date: 02/01/23
Post Date: 02/01/25
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.03.10
Filesets:
OMNIBACK-II.OMNI-HPUX-P,A.03.10
OMNIBACK-II.OMNI-OTHUX-P,A.03.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25952
Symptoms:
PHSS_25952:
Id = HSLco28793 SR: H555006144
Omnir command starts multiple Database Session
Managers.
Id = HSLco23050 SR: H555003736
"-ssea" entry is removed from the cell_info file
after updating the cell from GUI.
Id = HSLco28027 SR: H555005845
omnib command ignores "-encode" option.
PHSS_23109:
Id = JAGad01472
Exit code of omnimm is incorrect.
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI.
Id = NSMex03475, NSMex03808
Restore GUI does not display SAP objects if two
SAP instances with the same name are backed up on
different hosts.
Id = NSMex03505
a) When selecting restore of SAP object, message
"Cannot browse from root" appears.
b) Performing tasks in a certain sequence on the File
System Restore dialog window can cause GUI to core
dump.
Id = NSMex03658
Exit code of omniminit is incorrect.
Id = NSMex03806
Omnir cannot be started with "-r -l" or "-r -p"
options.
Id = NSMex03833
The options under Edit button are not accessible even
if user has the appropriate rights.
Id = NSMex03922
Listing of Oracle objects on GUI fails.
Id = NSMex03986
Omnir core dumps.
Id = NSMbb39907, JAGad48886
Any attempt to change object format in Oracle8 RMAN
script using OmniBack II GUI fails with the following
error:
"[12:1645] Format of RMAN channel names is not
correct.".
Id = HSLco20414
Device maintenance from command line is not sufficient.
PHSS_21644:
Id = NSMbb34280
When saving a backup specification template in MoM
environment, it is always saved on the Cell Manager,
where the xomnibackup GUI has been started from
instead of being saved on the MoM server.
Id = NSMex02757
Xomnirestore incorrectly reports the file size.
Id = NSMex02989
Xomnimonitor core dumps when printing all sessions.
Id = NSMex02991
GUI hangs when initializing media.
Id = NSMex03042
Xomnimm dies when configuring 9710 device details.
Id = NSMex03216
If two SAP databases are configured on different hosts,
restore GUI doesn't show both host objects for restore.
Id = NSMex03250
Media Management window shows garbage in media
location string.
Id = NSMex03262
Scheduling breaks after 12 months have passed.
Id = NSMex03306
Xomnirestore core dumps if Option button is clicked
by non-root user.
Id = NSMex02911
Removing a volser results in error message, although
the volser has been successfully removed from the
database:
"Cannot erase in this pool!"
Id = NSMex02954
Clicking the "..." button in Oracle 7 restore window
results in listing all sessions for all Databases,
including the failed ones, even if the instance name
has been provided.
Id = NSMex03419
After importing 2.55 tapes, some SAP files cannot be
restored.
Id = NSMex03503
Users with only "Start Backup" privilege can delete
datalists.
Id = NSMex03511
"Send external" method always executes external script
on Cell Manager system.
Id = NSMex03238
Backup scheduler shows incorrect dates.
Defect Description:
PHSS_25952:
Id = HSLco28793
New Database Session Manager instance is started
every time when omnir is trying to retrieve object
information from the database.
Resolution:
Omnir reuses existing connections.
Part of SSPUX310_061.
Id = HSLco23050
Parser does not recognize "-ssea" option in
cell_info file.
Resolution:
Parser now recognizes "-ssea" entry.
Id = HSLco28027
omnib command ignores "-encode" option.
Resolution:
omnib command properly recognizes "-encode" option.
PHSS_23109:
Id = JAGad01472
Exit code of omnimm is reported as successful when
the operation itself is not successful.
Resolution:
Omnimm returns correct exit codes.
Part of SSPUX310_041.
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI, unless
the "-emc" option is manually added to the cell_info
file for the Cell Manager.
Resolution:
xomnibackup correctly parses cell_info file and
recognizes EMC clients properly.
Id = NSMex03475, NSMex03808
Restore GUI does not show all SAP objects for hosts if
two SAP instances are backed up with the same name on
two different hosts.
Resolution:
xomnirestore has been improved to shows all object
correctly.
Id = NSMex03505
a) When selecting restore of SAP object, message
"Cannot browse from root" appears.
b) Two different structures with the same name
are defined.
Resolution:
xomnirestore has been improved.
Id = NSMex03658
Exit code 0 is returned when the medium initialization
fails with error:
"This medium can be initialized only with force option
specified."
Resolution:
Exit code of omniminit for failed operation is
redefined.
Id = NSMex03806
Incorrect parsing of appname and bararg arguments.
Resolution:
Omnir has been modified.
Id = NSMex03833
User rights are not properly interpreted.
Resolution:
User right permissions are properly interpreted.
Id = NSMex03922
Incorrect memory usage causes GUI to core dump
whilst listing Oracle sessions.
Resolution:
Memory usage is improved.
Id = NSMex03986
The omnir command causes a memory fault and core dumps
if it is run with a long list of objects.
Resolution:
Omnir can handle long list of objects.
Id = NSMbb39907, JAGad48886
It is impossible to define the object format in an
Oracle8 RMAN script using the Omniback II GUI.
Resolution:
It is possible to change object format in Oracle8 RMAN
script using OmniBack II GUI.
Part of SSPUX310_051.
Id = HSLco20414
Device enabling, disabling and status report can not be
performed using OmniBack II command line.
Resolution:
New options "-disable_device", "-enable_device" and
"-device" are added to omnimm, omniupload and
omnidownload.
Please see Special Installation Instructions for details
about the usage of mentioned options.
Part of SSPUX310_055.
PHSS_21644:
Id = NSMbb34280
The xomnibackup GUI is not aware of the fact that the
Cell Manager system is a part of the MoM environment,
and saves the backup specification template locally
instead of contacting the MoM server.
Resolution:
Xomnibackup now contacts the MoM server for saving
the template.
Id = NSMex02757
When trying to restore files bigger than 2 Gb,
xomnirestore reports the file size less than 2Gb.
Resolution
Xomnirestore now correctly reports the file size.
Id = NSMex02989
Xomnimonitor core dumps when printing all sessions if
there is a backup host with a hostname longer than 80
characters to be printed.
Resolution:
Hostname can now be up to 120 character long.
Id = NSMex02991
When initializing media from the CM console, the
system hangs if the Actions menu is left open, and
the confirmation dialog box is clicked.
Resolution:
Xomnimm has been fixed.
Id = NSMex03042
Uninitialized variable causes the GUI to occasionally
coredump when configuring libraries.
Resolution:
All variables are now initialized before displaying.
Id = NSMex03216
Motif GUI does not show two or more SAP hostnames in
restore GUI.
Resolution:
Xomnirestore has been improved.
Id = NSMex03250
Dialog window displays a non-initialized string.
Resolution:
Now all strings are correctly initialized before
displaying in the GUI.
Id = NSMex03262
Scheduling breaks after 12 months have passed since
the configuration.
Resolution:
Scheduler has been improved.
Id = NSMex03306
If the user does not have admin permissions, the target
host text field is not displayed properly, and the
xomnirestore GUI coredumps.
Resolution:
Xomnirestore behaviour has been improved.
Id = NSMex02911
An error is reported no matter if the volser remove
operation fails or succeeds.
Resolution:
If the remove operation is successful, the error
message is not reported.
Part of SSPUX310_003.
Id = NSMex02954
List of the Oracle7 backup sessions has not been
filtered properly.
Resolution:
Xomnirestore has been fixed.
Part of SSPUX310_016.
Id = NSMex03419
In pre-3.0 versions file names were stored on the tape
in the original upper and lower case letters. Version
OBII 3.0 and later store file names always in lower
case. At restore time it is assumed that all file names
on tape are in lower case. This introduces problems
when, for example, a tape from 2.55 system is imported
into 3.10 system and a restore is run from such tape.
Resolution:
When comparing names of files which were backed
up on the tape, all file names are now converted to
lower case, so this doesn't have any effect on new
backups (they are already in lower case) but enables
restores from pre-3.0 backups.
Part of SSPUX310_028.
See Special Installation Instructions.
Id = NSMex03503
User rights are not properly checked.
Resolution:
User rights checking is properly improved.
Id = NSMex03511
Execution of external script can not be prevented.
Resolution:
Omnirpt is changed so that the execution of "Send
external" method can be controlled by adding a line
ExternalScriptMode=<number>
in Global Options file, where <number> means:
- 0, no checking is performed
- 1, script can be executed only in bin directory
- 2, executing of external scripts is not allowed.
Id = NSMex03238
Backup scheduler loses months prior to January, 2001.
Resolution:
Scheduler optimization improved.
SR:
H555005845 B554000841 H555006144 H555003134 8606132323
8606161034 8606179663 B554000606 B554000634 B554000788
Patch Files:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.10/packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.10/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.10/
packet.Z
what(1) Output:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.10/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.10/
packet.Z:
None
cksum(1) Output:
713196952 13696637 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-1020/A.03.10/packet.Z
3307596699 11073037 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-10/A.03.10/packet.Z
3623887959 4137735 /opt/omni/databases/vendor/cc/ncr/i386/
mp-ras/A.03.10/packet.Z
3686810282 4884033 /opt/omni/databases/vendor/cc/dec/alpha/
osf1-4/A.03.10/packet.Z
1708139102 6803031 /opt/omni/databases/vendor/cc/gpl/i386/
linux/A.03.10/packet.Z
2905213007 4190638 /opt/omni/databases/vendor/cc/ibm/rs6000/
aix-42/A.03.10/packet.Z
362485764 3984997 /opt/omni/databases/vendor/cc/sco/i386/
sco_sv/A.03.10/packet.Z
1775699626 4061892 /opt/omni/databases/vendor/cc/sequent/
i386/dynix/A.03.10/packet.Z
2197560232 5000053 /opt/omni/databases/vendor/cc/sgi/mips/
irix/A.03.10/packet.Z
1517664742 5794393 /opt/omni/databases/vendor/cc/sgi/mips/
irix-62/A.03.10/packet.Z
2560096133 4848917 /opt/omni/databases/vendor/cc/siemens/
r400/sinix/A.03.10/packet.Z
34330540 4540075 /opt/omni/databases/vendor/cc/sun/sparc/
solaris/A.03.10/packet.Z
3926178454 4605117 /opt/omni/databases/vendor/cc/sun/sparc/
solaris-26/A.03.10/packet.Z
3190671227 6952546 /opt/omni/databases/vendor/cc/sun/sparc/
sunos/A.03.10/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_21644 PHSS_23109
Equivalent Patches:
PHSS_25953:
s700: 11.00
s800: 11.00
Patch Package Size: 82670 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_25952
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25952.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25952. 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_25952.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_25952.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_25952:
NOTE!
This Patch has to be installed on the Installation
Server host.
The User Interface must be redistributed to the client
system(s) after the installation of the patch in order
to get the fixes into effect.
For distribution of the User Interface, refer to the
OmnibackII Installation guide.
NOTE!
Fix for HSLco20414 introduces new options for device
maintenance. The usage of new options is listed below:
To disable/enable specific device and all other devices
with the same lockname, run:
omnimm -disable_device {device name}
omnimm -enable_device {device name}
To disable/enable all devices with the same lockname, run:
omnimm -disable_lockname {lock name}
omnimm -enable_lockname {lock name}
To check if specific device is enabled/disabled, run:
omnidownload -device {device name}
To obtain complete functionality one has to install
PHSS_24423/PHSS_24424 (CORE) and PHSS_23689/PHSS_23690
(Cell Server) or later patches as well.
NOTE!
Fix NSMex03419 is also part of the Windows NT
(OMNIBACK_00014) and Cell Server (PHSS_22166/PHSS_22167)
general release patch. Its functionality will be fully
available when the mentioned patches that include this
fix are released.
Patch includes the following Site Specific Patches:
SSPUX310_003
SSPUX310_016
SSPUX310_028
SSPUX310_041
SSPUX310_051
SSPUX310_055
SSPUX310_061
-----End of Document ID: PHSS_25952------------------------------------------
Document ID: PHSS_25946
Date Loaded: 20020125
Title: s700_800 10.20 OV OB4.00 patch - CS packet
Patch Name: PHSS_25946
Patch Description: s700_800 10.20 OV OB4.00 patch - CS packet
Creation Date: 02/01/22
Post Date: 02/01/25
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OmniBackII A.04.00
Filesets:
OMNIBACK-II.OMNI-CS,A.04.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25946
Symptoms:
PHSS_25946:
Id = HSLco30019 SR: H555006532
RDS abnormally ends with "segmentation violation"
error after exporting tapes.
Id = HSLco31142 SR: H555006771
Load balancing is not working properly.
Id = HSLco31145 SR: H555006772
Omniback database suddenly stops reporting any
details about sessions.
Id = HSLco31265 SR: H555006788
After the execution of a session with load balacing
used, devices remain locked and cannot be used for
later sessions.
Id = HSLco30776 SR: H555006705
Omniback transactions cannot be measured with ARM.
Id = HSLco31067 SR: H555006757
"End of Session" e-mail notification does not specify
datalist name for which it was created.
Id = HSLco31329 SR: H555006811
PHSS_24996/PHSS_24997 contains global file in incorrect
format.
Id = HSLco31359 SR: H555006819
Forced ownership in datalist does not function
properly.
NOTE: Please check the Special Installation
Instructions part for the details about known issues.
PHSS_24996:
Id = HSLco27250 SR: H555005624
Import of session fails.
Id = HSLco27465 SR: H555005680
Post-exec script specified for a virtual hostname does
not start if pre-exec script fails.
Id = HSLco27522 SR: H555005697
Adding OmniBack II licenses in MC/ServiceGuard
environment fails with an error:
"Cell Server host IP is not in IP range.".
Id = HSLco27577 SR: H555005710
Clean drive request does not report an error
when cleaning tape is not available.
Id = HSLco27801 SR: H555005769
Restore of EMC integration session hangs.
Id = HSLco27848 SR: H555005792
Multiple "Trees not found." error messages are
reported during filesystem restore.
Id = HSLco27897 SR: H555005805
Omniback II continues with the backup session
although Oracle Recovery Manager ended abnormally.
Id = HSLco28271 SR: H555005973
Restore session fails with error:
"Can not load exchanger medium.".
Id = HSLco29824 SR: H555006482
Omnir ignores "-into" option when one of the needed
media is missing and no medium catalog data exists.
Id = JAGad48558 SR: 8606179334
OmniBack II creates duplicated tape labels.
Id = JAGad64442 SR: 8606195237
OmniBack II internal database owner is not set
properly after configuring OmniBack II in
MC/ServiceGuard environment.
Id = JAGad86475 SR: 8606217323
Cell Request Server and session managers frequently
abort.
Id = NSMbb41837 SR: B555011167
Media Agent takes 4 hours to abort the session.
Id = NSMbb42348 SR: B555011595
NDMP password stored in cell_info file is not
encrypted.
Id = NSMbb42370 SR: H555006525
Listing from media with "log files" selected results
in an internal error.
Id = NSMbb42426 SR: H555006152
omnidbinit command does not remove binary files.
Id = NSMex04465 SR: H555005922
Backup is waiting for all pre/post-exec scripts to
finish before proceeding.
Id = NSMex04520 SR: H555005999
Even though the Load Balancing is set min to 1
and max to 1, more than one Media Agent is started.
Id = NSMex04549 SR: H555006047
SSEA Integration needs both SSEA and EMC
licenses in order to run backup.
Id = NSMex04472 SR: H555006595
Performing an upgrade of Omniback II internal
database from 3.x to 4.0 version takes very long
time.
Id = NSMbb43127 SR: H555006592
Omnidbcheck does not work correctly in centralized
media management environment.
Defect Description:
PHSS_25946:
Id = HSLco30019
RDS disregards exit code from the first query which
causes a problem when trying to switch restore session
that has been on an already recycled medium.
Resolution:
Exit code handling is improved.
Id = HSLco31142
There is no warning reported when one creates a datalist
or a barlist with load balancing enabled and minimum
number of devices greater than number of configured
logical devices.
Resolution:
Comparison of minimum and configured devices number
is implemented.
Id = HSLco31145
Aborting an import session corrupts Omniback internal
database.
Resolution:
Aborting an import session is properly handled and it
does not corrupt internal database.
Part of SSPUX400_014.
Please see Special Installation Instructions.
Id = HSLco31265
Device lock counter is not working correctly.
Resolution:
Device lock counter is working properly and the
devices are unlocked after the session ends.
Id = HSLco30776
ARM library is not initialized.
Resolution:
ARM library is properly initialized.
Id = HSLco31067
Datalist name is not exported into environment.
Resolution:
Datalist name is exported into environment.
Id = HSLco31329
File /opt/omni/newconfig/etc/opt/omni/options/global
has incorrect format after the installation of
PHSS_24996/PHSS_24997 general release patch.
Resolution:
global file is in correct format.
Part of SSPUX400_016.
Id = HSLco31359
Object ownership is incorrectly set if it is specified
in the datalist.
Resolution:
Object ownership is correctly set.
PHSS_24996:
Id = HSLco27250
Import of integration session fails if the session is
spanned over two or more media.
Resolution:
Checking for object description is changed.
Id = HSLco27465
OmniBack II improperly recognizes post-exec script as a
start request if pre-exec script fails in cluster
environment.
Resolution:
OB2FORCEPOSTEXEC environment variable is added.
Setting its value to 1 in the .omnirc file causes
post-exec scripts to be started regardless of pre-exec
script exit code.
Id = HSLco27522
OmniBack II is not able to list all interfaces in cells
with more than 20 LAN cards because the buffer is too
small.
Resolution:
Buffer for storing interfaces is increased.
Id = HSLco27577
Backup Session Manager does not retry checking
for the cleaning tape after clean drive request is
generated.
Resolution:
Backup Session Manager waits until cleaning tape
is specified.
Id = HSLco27801
Even though volume groups resolving or
mounting fails for some reason during an EMC
integration restore, Restore Session Manager loads
the tape for restore and hangs.
Resolution:
Error handling is improved.
Id = HSLco27848
Restoring a filesystem from GUI takes full backup
session instead of proper incremental session.
Resolution:
Message "Trees not found" is reported only once.
Id = HSLco27897
Omniback II does not check ob2rman's exit code.
Resolution:
Error handling is improved.
Id = HSLco28271
After the mount request during restore from SCSI-II
library, Omniback tries to load "" medium into drive.
Resolution:
Restore session manager rechecks the configuration
after the mount request is confirmed.
Id = HSLco29824
Exporting one of the needed media results in
omitting "-into" option when backup session with
"-no_log" option spans over multiple media.
Resolution:
Restore Session Manager error handling is improved.
Id = JAGad48558
Initializition with "Autolabel" option creates
duplicated tape labels.
Resolution:
Medium initialization does not create duplicated tape
labels.
Id = JAGad64442
OmniBack II internal database ownership belongs to
primary node instead of floating hostname in
MC/ServiceGuard environment.
Resolution:
Database ownership is set to floating hostname.
Id = JAGad86475
Cell Request Server and session managers abort
because of an accept() command failure on some
HP-UX 11.x systems.
Resolution:
accept() command is re-executed in case of
ENOBUFS failure.
Id = NSMbb41837
Aborting of a restore session is incorrectly detected.
Resolution:
Aborting detection is correctly implemented.
Id = NSMbb42348
NDMP password token does not have encryption
flag set.
Resolution:
Encryption flag is set on NDMP password token.
Id = NSMbb42370
"Log Files" option is not properly implemented.
Resolution:
"Log Files" option is properly implemented.
Id = NSMbb42426
omnidbinit command does not remove binary files
on HP-UX systems.
Resolution:
omnidbinit command removes binary files on
HP-UX systems.
Id = NSMex04465
Backup session is in sleep mode during the
pre/post-exec scripts execution. This can cause
the session to last a long time.
Resolution:
New global option is introduced. Details:
name: PrePostExecOnEveryVolumeForHostBackup
format:
PrePostExecOnEveryVolumeForHostBackup=<0 or 1>
default: 0
If this option is set (=1), Backup Disk Agent
(BDA) will execute pre/post-exec scripts for
every volume of host object specified.
If this option is not set (=0), Backup Session
Manager (BSM) will execute pre-exec script prior
to starting first volume BDA and post-exec
script after last volume BDA. During the
execution of these scripts, the BSM will sleep.
Id = NSMex04520
Backup Session Manager incorrectly handles load
balancing option by using the default settings.
Resolution:
Backup Session Manager balance routine handling
is modified to correctly use balancing options.
Part of SSPUX400_001.
Id = NSMex04549
Omniback is incorrectly checking the licenses.
Resolution:
Omniback checks the licenses correctly.
Id = NSMex04472
Internal database upgrade performance is very poor
in environments with a large number of files (>1000000)
within single directory.
Resolution:
Performance of the upgrade is increased using the
additional memory. In order to achieve this, two
variables have to be set in /etc/opt/omni/options/global
file:
DcFbCdCacheTreshold=150
DcFbCdCacheMaxHoleSize=10
Id = NSMbb43127
If Cell Manager system is client for centalized media
management database, omnidbcheck does not handle
log files properly.
Resolution:
Log files handling is improved.
SR:
H555006757 H555006705 H555006788 H555006771 H555006772
H555006819 H555006811 H555006532 H555006595 H555005769
H555005697 8606217323 H555005999 8606195237 8606179334
B555011167 H555005710 H555006152 B555011595 H555006047
H555005624 H555005922 H555005805 H555006525 H555005680
H555006482 H555006592 H555005792 H555005973
Patch Files:
/etc/opt/omni/cell/cell_format
/etc/opt/omni/dltemplates/lists/oracle8/Archive
/etc/opt/omni/dltemplates/lists/oracle8/Archive_Delete
/etc/opt/omni/dltemplates/lists/oracle8/Whole_Online
/etc/opt/omni/dltemplates/lists/oracle8/Whole_Online_Delete
/etc/opt/omni/dltemplates/lists/oracle8/Database_Archive
/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_Archive
/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_ArchiveDel
/opt/omni/sbin/omnitrig
/opt/omni/sbin/install/omniforsg.ksh
/opt/omni/sbin/omnidbinit
/opt/omni/sbin/omnidbcheck
/opt/omni/sbin/omnidbutil
/opt/omni/lbin/bsm
/opt/omni/lbin/rsm
/opt/omni/lbin/msm
/opt/omni/lbin/dbsm
/opt/omni/lbin/asm
/opt/omni/lbin/crs
/opt/omni/lbin/mmd
/opt/omni/.CII_CS
/opt/omni/lib/libob2emmdb.sl
/opt/omni/lib/libob2eadm.sl
/opt/omni/lib/libob2ecdb.sl
/opt/omni/lib/libob2ecmn.sl
/opt/omni/newconfig/etc/opt/omni/cell/cell_format
/opt/omni/newconfig/etc/opt/omni/options/global
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Archive
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Archive_Delete
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Archive
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_Archive
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_ArchiveDel
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online_Delete
what(1) Output:
/etc/opt/omni/cell/cell_format:
None
/etc/opt/omni/dltemplates/lists/oracle8/Archive:
None
/etc/opt/omni/dltemplates/lists/oracle8/Archive_Delete:
None
/etc/opt/omni/dltemplates/lists/oracle8/Whole_Online:
None
/etc/opt/omni/dltemplates/lists/oracle8/Whole_Online_Delete:
None
/etc/opt/omni/dltemplates/lists/oracle8/Database_Archive:
None
/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_Archive:
None
/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_ArchiveDel:
None
/opt/omni/sbin/omnitrig:
[TZ=GMT0 /opt/omni/sbin/omnitrig -version]
HP OpenView OmniBack II A.04.00: OMNITRIG, internal
build PHSS_25946/PHSS_25947, built on Thu De
c 20 08:51:25 2001
/opt/omni/sbin/install/omniforsg.ksh:
None
/opt/omni/sbin/omnidbinit:
[TZ=GMT0 /opt/omni/sbin/omnidbinit -version]
HP OpenView OmniBack II A.04.00: OMNIDBINIT, interna
l build PHSS_24996/PHSS_24997, built on Wed
Nov 7 11:29:05 2001
/opt/omni/sbin/omnidbcheck:
[TZ=GMT0 /opt/omni/sbin/omnidbcheck -version]
HP OpenView OmniBack II A.04.00: OMNIDBCHECK, intern
al build PHSS_24996/PHSS_24997, built on Mon
Nov 12 12:52:55 2001
/opt/omni/sbin/omnidbutil:
[TZ=GMT0 /opt/omni/sbin/omnidbutil -version]
HP OpenView OmniBack II A.04.00: OMNIDBUTIL, interna
l build PHSS_25946/PHSS_25947, built on Thu
Jan 17 15:09:33 2002
/opt/omni/lbin/bsm:
[TZ=GMT0 /opt/omni/lbin/bsm -version]
HP OpenView OmniBack II A.04.00: BSM, internal build
PHSS_25946/PHSS_25947, built on Wed Dec 19
15:34:13 2001
/opt/omni/lbin/rsm:
[TZ=GMT0 /opt/omni/lbin/rsm -version]
HP OpenView OmniBack II A.04.00: RSM, internal build
PHSS_25946/PHSS_25947, built on Wed Dec 19
15:35:22 2001
/opt/omni/lbin/msm:
[TZ=GMT0 /opt/omni/lbin/msm -version]
HP OpenView OmniBack II A.04.00: MSM, internal build
PHSS_24996/PHSS_24997, built on Thu Nov 15
11:06:26 2001
/opt/omni/lbin/dbsm:
[TZ=GMT0 /opt/omni/lbin/dbsm -version]
HP OpenView OmniBack II A.04.00: DBSM, internal buil
d PHSS_25946/PHSS_25947, built on Fri Jan 4
09:30:43 2002
/opt/omni/lbin/asm:
[TZ=GMT0 /opt/omni/lbin/asm -version]
HP OpenView OmniBack II A.04.00: ASM, internal build
PHSS_24996/PHSS_24997, built on Thu Nov 15
10:17:48 2001
/opt/omni/lbin/crs:
[TZ=GMT0 /opt/omni/lbin/crs -version]
HP OpenView OmniBack II A.04.00: CRS, internal build
PHSS_24996/PHSS_24997, built on Thu Nov 15
11:18:14 2001
/opt/omni/lbin/mmd:
[TZ=GMT0 /opt/omni/lbin/mmd -version]
HP OpenView OmniBack II A.04.00: MMD, internal build
PHSS_24996/PHSS_24997, built on Thu Nov 15
10:55:11 2001
/opt/omni/.CII_CS:
None
/opt/omni/lib/libob2emmdb.sl:
None
/opt/omni/lib/libob2eadm.sl:
None
/opt/omni/lib/libob2ecdb.sl:
None
/opt/omni/lib/libob2ecmn.sl:
None
/opt/omni/newconfig/etc/opt/omni/cell/cell_format:
None
/opt/omni/newconfig/etc/opt/omni/options/global:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Archive:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Archive_Delete:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Archive:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_Archive:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_ArchiveDel:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online:
None
/opt/omni/newconfig/etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online_Delete:
None
cksum(1) Output:
3793704502 3338 /etc/opt/omni/cell/cell_format
216099702 465 /etc/opt/omni/dltemplates/lists/oracle8/
Archive
1054187261 524 /etc/opt/omni/dltemplates/lists/oracle8/
Archive_Delete
3115011229 538 /etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online
1284758894 599 /etc/opt/omni/dltemplates/lists/oracle8/
Whole_Online_Delete
3614152794 662 /etc/opt/omni/dltemplates/lists/oracle8/
Database_Archive
2861451592 766 /etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_Archive
2432391300 821 /etc/opt/omni/dltemplates/lists/oracle8/
Database_Switch_ArchiveDel
1528550680 513407 /opt/omni/sbin/omnitrig
3309028381 5145 /opt/omni/sbin/install/omniforsg.ksh
2959395246 669266 /opt/omni/sbin/omnidbinit
1936702332 755444 /opt/omni/sbin/omnidbcheck
2329449776 866202 /opt/omni/sbin/omnidbutil
3584110779 1469882 /opt/omni/lbin/bsm
3951402814 1116927 /opt/omni/lbin/rsm
1765737651 858335 /opt/omni/lbin/msm
500160241 1477402 /opt/omni/lbin/dbsm
2716186134 755579 /opt/omni/lbin/asm
1876330946 751521 /opt/omni/lbin/crs
42229200 571066 /opt/omni/lbin/mmd
3490443903 10768 /opt/omni/.CII_CS
3302700991 733848 /opt/omni/lib/libob2emmdb.sl
1912347980 873294 /opt/omni/lib/libob2eadm.sl
2669725610 901959 /opt/omni/lib/libob2ecdb.sl
544131192 878032 /opt/omni/lib/libob2ecmn.sl
3793704502 3338 /opt/omni/newconfig/etc/opt/omni/cell/
cell_format
367446921 28304 /opt/omni/newconfig/etc/opt/omni/options/
global
216099702 465 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Archive
1054187261 524 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Archive_Delete
3614152794 662 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Database_Archive
2861451592 766 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Database_Switch_Archive
2432391300 821 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Database_Switch_ArchiveDel
3115011229 538 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Whole_Online
1284758894 599 /opt/omni/newconfig/etc/opt/omni/dltemplates/
lists/oracle8/Whole_Online_Delete
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_24996
Equivalent Patches:
PHSS_25947:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 13050 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_25946
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25946.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25946. 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_25946.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_25946.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_25946:
NOTE!
This Patch has to be installed on the Cell Manager host.
OmniBack II server must be shutdown before installing
the patch. Use the following command for shutting down
the server:
"/opt/omni/sbin/omnisv.sh stop".
After the installation is complete, restart OmniBack II
server using "/opt/omni/sbin/omnisv.sh start".
PHSS_25946/PHSS_25947:
IMPORTANT NOTE!
If one of the below Problem descriptions applies to your
Omniback environment, then you must perform the actions
provided in the respective Solution descriptions.
1. Problem description:
-----------------------
The upgrade of the OmniBack II internal database from
A.03.x to A.04.00 format takes very long time in
environments with:
- lots of files in directories (more than 100000)
- files with similar filenames and filenames longer than
20 characters
This problem was reported in defect Id = NSMex04472.
Solution:
---------
Install the latest Cell Server patch before the upgrade of
the database is started. Currently the latest CS patch is
this PHSS_25946 (HP-UX 10.20) or PHSS_25947 (HP-UX 11.X).
With this patch, the performance of the OmniBack II
internal database upgrade process is increased by using
additional memory. In order to achieve this, after the
patch is installed, these actions have to be performed
before the upgrade starts:
- two global option variables have to be set in the
/etc/opt/omni/options/global file:
DcFbCdCacheTreshold=150
DcFbCdCacheMaxHoleSize=10
Then the OmniBack II services must be restarted!
2. Problem description:
-----------------------
Upgrade of the OmniBack internal database from A.03.x to
A.04.00 format fails or is incorrect if the A.03.x
database had filenames extension files.
There are two problems:
1. The filename extension files (fnames.datX) that you
created for A.03.x, have not been correctly registered
during the upgrade.
2. Additional new filename extensions cannot be added
to the A.04.00 database.
The registration can be checked by running
"omnidbutil -extendinfo". If the registration was
successful, then you will see the same files fnames.datX
in A.04.00 as they existed in A.03.x too.
In this case you need not to run the corrective steps
described in 'Solution'.
Solution:
---------
How to fix the DB:
1. If no error was encountered during the upgrade from
A.03.x, then perform these steps:
- Stop OmniBack II services:
omnisv -stop
- Save all the 'old' database files from A.03.x as well
as the new ones - in order not to lose the data
in case of any problem. They are located in the following
directories:
/var/opt/omni/db
/var/opt/omni/db40
You may use 'cp -r' or tar command to perform this task.
- Install the latest Cell Server patch
(currently PHSS_25946/25947)
- Restart OmniBack II services:
omnisv -start
- Write the OBDB tablespaces out in ascii code
for both mmdb and cdb part:
omnidbutil -writedb
- Stop OmniBack II services:
omnisv -stop
- Move old datafiles files:
mv /var/opt/omni/db40/datafiles \
/var/opt/omni/db40/datafiles.orig
- Copy new datafiles files:
cp -r /opt/omni/newconfig/var/opt/omni/db40/datafiles \
/var/opt/omni/db40/datafiles
- Restart OmniBack II services:
omnisv -start
- Initialize database:
omnidbinit -force
- Add extension files for filenames, as required:
omnidbutil -extendfnames
- Rebuild the OBDB for both mmdb and cdb part:
omnidbutil -readdb
- Recheck that extension file was properly added:
omnidbutil -extendinfo
2. If during the upgrade of the detail part of the DB the
db40/fnames.dat becomes full and therefore the upgrade
fails, then follow these steps:
- Stop OmniBack II services:
omnisv -stop
- Save all the 'old' database files from A.03.x as well
as the new ones - in order not to lose the data
in case of any problem. They are located in the following
directories:
/var/opt/omni/db
/var/opt/omni/db40
You may use 'cp -r' or tar commands to perform this task.
- Install the latest Cell Server patch
(currently PHSS_25946/25947)
- Move old datafiles files:
mv /var/opt/omni/db40/datafiles \
/var/opt/omni/db40/datafiles.orig
- Copy new datafiles files:
cp -r /opt/omni/newconfig/var/opt/omni/db40/datafiles \
/var/opt/omni/db40/datafiles
- Restart OmniBack II services:
omnisv -start
- Initialize database:
omnidbinit -force
- Add extension files for filenames, as required:
omnidbutil -extendfnames
- Upgrade the core and detail part of the database:
omnidbupgrade -ucp
omnidbupgrade -udp
- If any backup was made on A.04.00 then finally import
all the tapes made with A.04.00 backup into the correct
pool.
omnimm -import BackupDevice [ -slot SlotID ] \
[ -pool PoolName ]
- Recheck that extension file was properly added:
omnidbutil -extendinfo
NOTE!
Defect HSLco31145: If a database corruption has been
experienced because of this defect, then after installation
of this patch, the corruption can be removed and the import
of Omniback II 3.x tapes be enabled as follows:
1. step:
--------
Import the problematic tape. The import itself will fail,
complaining about catalog and media management database
not being in sync. But internally it will remove
the suspective media position from the database which
makes second step possible.
2. step:
--------
Import the problematic tape again. This succeeds and
results in imported medium and fixed database.
NOTE!
Problem HSLco31142: The complete solution will be
available after CORE patch PHSS_25948/PHSS_25949 is
released and installed.
Patch includes the following Site Specific Patches:
SSPUX400_001
SSPUX400_014
SSPUX400_016
-----End of Document ID: PHSS_25946------------------------------------------
Document ID: PHSS_25819
Date Loaded: 20020125
Title: s700_800 10.X OV OB3.50 patch - CORE packet
Patch Name: PHSS_25819
Patch Description: s700_800 10.X OV OB3.50 patch - CORE packet
Creation Date: 02/01/22
Post Date: 02/01/25
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.03.50
Filesets:
OMNIBACK-II.OMNI-CORE-IS,A.03.50
OMNIBACK-II.OMNI-CORE,A.03.50
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25819
Symptoms:
PHSS_25819:
Id = HSLco20414 SR: H555003134
Device maintenance from command line is not sufficient.
Id = HSLco27521 SR: H555005696
During scheduled purge error message is displayed:
"Bad catalog access for message #3137 in set 11".
Id = HSLco27649 SR: H555005721
Upgrade of AIX client fails with error:
"Unexpected untar problem".
Id = HSLco31142 SR: H555006771
Load balancing is not working properly.
Id = JAGad96899 SR: 8606227839
Omniback II does not support Ext3 filesystem on
Linux systems.
PHSS_24429:
Id = HSLco27823
OmniBack II does not recognize Reiser filesystem on
Linux.
Id = HSLco26064
Installation of OmniBack II clients on Linux 7.x
systems does not complete.
PHSS_23687:
Id = NSMbb37117
util_oracle8.exe complains that Oracle is not linked
with OmniBack II for backup.
Id = NSMex03956
".util ISINFO" returns corrupted bytes_to_be_received
size.
Id = HSLco23481
Installation on HP-UX 11.20 systems does not complete.
PHSS_22914:
Id = NSMex03937
User can gain an unauthorized access to an OmniBack
client.
Id = NSMex03757, NSMex03667
Backup of one object fails with:
"IPC Read Error. Connection reset by peer".
PHSS_22434:
Id = NSMex03372
A backup of 129 Sybase databases fails with
"[61:1005] Got unexpected close from INET on
<hostname>.".
Id = NSMex03638
Omnidbutil's option "-change_objname" does not work
properly.
"[61:1005] Got unexpected close from INET on
<hostname>.".
Defect Description:
PHSS_25819:
Id = HSLco20414
Device enabling, disabling and status report can not be
performed using OmniBack II command line.
Reslution:
New options "-disable_device", "-enable_device" and
"-device" are added to omnimm, omniupload and
omnidownload. The appropriate messages are added to
catalog.
Part of SSPUX350_038.
Id = HSLco27521
The message 3137 is not defined in the catalog.
Resolution:
The appropriate message is added to catalog.
Id = HSLco27649
Shared libraries libdc and libde have to be removed
before upgrade of AIX clients. Due to changes in
OmniBack II linking process, extensions for the
libraries are changed, so the libraries are not
removed during the installation.
Resolution:
Correct shared libraries are removed during the
upgrade process.
Id = HSLco31142
There is no warning reported when one creates a datalist
or a barlist with load balancing enabled and minimum
number of devices greater than number of configured
logical devices.
Resolution:
Comparison of minimum and configured devices number
is implemented and appropriate warning message is added
to catalog.
Id = JAGad96899
Omniback II does not support Ext3 filesystem on
Linux systems.
Resolution:
Omniback II supports Ext3 filesystem on Linux systems.
Part of SSPUX350_065.
PHSS_24429:
Id = HSLco27823
OmniBack II does not recognize Reiser filesystem om
Linux systems.
Resolution:
OmniBack II recognizes Reiser filesystem.
Id = HSLco26064
OmniBack II client installation on Linux 7.x does not
complete because of missing entries in /etc/xinetd.conf
file.
Resolution:
Proper entries are added to /etc/xinetd.conf file
during the installation of OmniBack II client on a
Linux 7.x system.
PHSS_23687:
Id = NSMbb37117
Library $ORACLE_HOME/lib/libobk.so is not properly
linked and the error message is incorrect.
Resolution:
A proper message is added to message catalog.
Id = NSMex03956
Logging messages redirection does not work properly.
Resolution:
Exporting VUE variable is added.
Id = HSLco23481
Installation on HP-UX 11.20 systems does not complete.
Resolution:
Installation on HP-UX 11.20 systems completes.
Please see Special Installation Instructions.
PHSS_22914:
Id = NSMex03937
User can gain an unauthorized access to an OmniBack
client.
Resolution:
Code was changed to avoid unauthorised access.
To preserve the previous behaviour, a variable must
be set in the /opt/omni/.omnirc file (not recommended):
OB2INETSECUEREXEC = 1
Part of SSPUX350_022.
Id = NSMex03757, NSMex03667
Inet times out during the export of variables.
Resolution:
Environment variable OB2INETTIMEOUT is introduced. It
should be set in /opt/omni/.omnirc file in form
OB2INETTIMEOUT=<time_in_seconds>
where time_in_seconds is timeout period for inet.
Recommended value is 150.
Part of SSPUX350_023.
PHSS_22434:
Id = NSMex03372
Backup fails if there are more than 256 objects in a
single barlist.
Resolution:
Number of objects in a barlist increased to 1024.
Id = NSMex03638
Omnidbutil's option "-change_objname" should not be a
part of OmniBack II A.03.50.
Resolution:
Option "-change_objname" is removed.
SR:
H555005696 H555003134 8606227839 H555006771 H555005721
H555005779 H555005136 H555003879 H555004628 B555007579
B554000503 B554000768
Patch Files:
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-1020/
A.03.50/packet.Z
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-10/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-11/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/dec/alpha/osf1-4/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/gpl/i386/linux/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/ibm/rs6000/aix-42/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/ncr/i386/mp-ras/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/sco/i386/sco_sv/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/sco/i386/unixware/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/sequent/i386/dynix/
A.03.50/packet.Z
/opt/omni/databases/vendor/omnicf/sgi/mips/irix/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/sgi/mips/irix-62/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/siemens/r400/sinix/
A.03.50/packet.Z
/opt/omni/databases/vendor/omnicf/sun/sparc/solaris/A.03.50/
packet.Z
/opt/omni/databases/vendor/omnicf/sun/sparc/solaris-26/
A.03.50/packet.Z
/opt/omni/databases/vendor/omnicf/sun/sparc/sunos/A.03.50/
packet.Z
/opt/omni/databases/utils/sun/sparc/solaris-26/utils.tar
/opt/omni/databases/utils/ibm/rs6000/aix-42/utils.tar
/opt/omni/databases/utils/gpl/i386/linux-60/utils.tar
/opt/omni/lbin/bmsetup
/opt/omni/lbin/.util
what(1) Output:
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-1020/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-10/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/hp/s800/hp-ux-11/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/dec/alpha/osf1-4/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/gpl/i386/linux/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/ibm/rs6000/aix-42/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/ncr/i386/mp-ras/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/sco/i386/sco_sv/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/sco/i386/unixware/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/sequent/i386/dynix/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/omnicf/sgi/mips/irix/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/sgi/mips/irix-62/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/siemens/r400/sinix/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/omnicf/sun/sparc/solaris/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/omnicf/sun/sparc/solaris-26/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/omnicf/sun/sparc/sunos/A.03.50/
packet.Z:
None
/opt/omni/databases/utils/sun/sparc/solaris-26/utils.tar:
None
/opt/omni/databases/utils/ibm/rs6000/aix-42/utils.tar:
None
/opt/omni/databases/utils/gpl/i386/linux-60/utils.tar:
None
/opt/omni/lbin/bmsetup:
[TZ=GMT0 /opt/omni/lbin/bmsetup -version]
HP OpenView OmniBack II A.03.50: BMSETUP, internal b
uild PHSS_24429/PHSS_24430, built on Tue Jul
17 11:25:39 2001
/opt/omni/lbin/.util:
[TZ=GMT0 /opt/omni/lbin/.util -version]
cksum(1) Output:
1703559280 2626411 /opt/omni/databases/vendor/omnicf/hp/
s800/hp-ux-1020/A.03.50/packet.Z
495002276 1984219 /opt/omni/databases/vendor/omnicf/hp/s800/
hp-ux-10/A.03.50/packet.Z
3798778432 2626859 /opt/omni/databases/vendor/omnicf/hp/
s800/hp-ux-11/A.03.50/packet.Z
434274107 1258481 /opt/omni/databases/vendor/omnicf/dec/
alpha/osf1-4/A.03.50/packet.Z
801163073 4282513 /opt/omni/databases/vendor/omnicf/gpl/
i386/linux/A.03.50/packet.Z
4163216157 1692663 /opt/omni/databases/vendor/omnicf/ibm/
rs6000/aix-42/A.03.50/packet.Z
3908708612 1083593 /opt/omni/databases/vendor/omnicf/ncr/
i386/mp-ras/A.03.50/packet.Z
577011677 1076097 /opt/omni/databases/vendor/omnicf/sco/
i386/sco_sv/A.03.50/packet.Z
3709460102 1036359 /opt/omni/databases/vendor/omnicf/sco/
i386/unixware/A.03.50/packet.Z
1394750966 1077726 /opt/omni/databases/vendor/omnicf/
sequent/i386/dynix/A.03.50/packet.Z
4193110334 1432255 /opt/omni/databases/vendor/omnicf/sgi/
mips/irix/A.03.50/packet.Z
1141233400 1849286 /opt/omni/databases/vendor/omnicf/sgi/
mips/irix-62/A.03.50/packet.Z
1071768526 1552653 /opt/omni/databases/vendor/omnicf/
siemens/r400/sinix/A.03.50/packet.Z
973019656 1902287 /opt/omni/databases/vendor/omnicf/sun/
sparc/solaris/A.03.50/packet.Z
3828723652 1952417 /opt/omni/databases/vendor/omnicf/sun/
sparc/solaris-26/A.03.50/packet.Z
4114716555 2179067 /opt/omni/databases/vendor/omnicf/sun/
sparc/sunos/A.03.50/packet.Z
2034876432 51200 /opt/omni/databases/utils/sun/sparc/
solaris-26/utils.tar
3409612757 51200 /opt/omni/databases/utils/ibm/rs6000/
aix-42/utils.tar
1801935366 51200 /opt/omni/databases/utils/gpl/i386/
linux-60/utils.tar
1522261724 414960 /opt/omni/lbin/bmsetup
2326092121 25035 /opt/omni/lbin/.util
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22434 PHSS_22914 PHSS_23687 PHSS_24429
Equivalent Patches:
PHSS_25820:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 29590 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_25819
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25819.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25819. 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_25819.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_25819.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_25819:
NOTE!
This Patch has to be installed on all Installation
server hosts.
Because the Core package is a part of all agents, all
client packages need to be redistributed after this patch
was installed on the installation server in order to
enable the changes (Disk Agents, Media Agents, ...).
NOTE!
From patch PHSS_23687/PHSS_23688 on, OmniBack II A.03.50 is
supported on HP-UX 11.20 operating system. This (or later)
patch has to be installed on Installation Server system
before distributing client packages to any HP-UX 11.20
system.
If your HP-UX 11.20 system is going to be a Cell Manager
and Installation Server, please follow these steps in
order to properly complete the installation:
1. Install OmniBackII A.03.50 software on your system.
2. Install PHSS_23688.
3. Run
"/opt/omni/bin/omnicc -update_host <hostname>"
where <hostname> is name of your HP-UX 11.20 system.
4. Configure the Installation Server from OmniBack GUI.
In cases where HP-UX 11.20 systems are clients in OmniBack
cell and/or Installation Server is not a HP-UX 11.20 system,
the installation procedure is the same as it is for other
HP-UX systems.
NOTE!
From patch PHSS_22434/PHSS_22435 on, OmniBack II supports
clients on Sun Solaris 8.
NOTE!
From patch PHSS_25819/PHSS_25820 on, OmniBack II supports
ext3 filesystem on Linux systems.
NOTE!
Complete functionality of defect fix HSLco20414 will be
available when patches PHSS_24660/PHSS_24661 (Cell Console)
and PHSS_24658/PHSS_24659 (Cell Server) are installed - or
successors of them.
Patch includes the following Site Specific Patches:
SSPUX350_022
SSPUX350_023
SSPUX350_038
SSPUX350_065
-----End of Document ID: PHSS_25819------------------------------------------
Document ID: PHSS_25817
Date Loaded: 20020124
Title: s700_800 10.X OV OB3.50 patch - SSEA packet
Patch Name: PHSS_25817
Patch Description: s700_800 10.X OV OB3.50 patch - SSEA packet
Creation Date: 02/01/17
Post Date: 02/01/24
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.03.50
Filesets:
OMNIBACK-II.OMNI-SSEA-P,A.03.50
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25817
Symptoms:
PHSS_25817:
Id = JAGad48627 SR:8606179403
If preexec script fails OmniBack II by default just
aborts the agent and exits. It does not run post-exec
script or clean up.
Id = NSMex04226
Restore fails with:
"[Major] From: SYMA<hostname> "" Time: <time>
[223:325] Could not activate volume group
/dev/sg_sap.
[Major] From: SYMA<hostname> "" Time: <time>
[223:363] Could not prepare mirror disks of object
/sg_sap for backup.
(Activation of volume group failed.)".
Id = HSLco30300 SR:H555006603
Split mirror backup fails with:
"[Critical] From: SSEA<host> "" Time: <time>
Command "/etc/horcmgr" failed with exit code 3.
For details please check log directories:
Log file directory in operation:
/var/opt/omni/log/yyyy-mm-dd-xx/curlogxx
Log file directory for automatic storing:
/var/opt/omni/log/yyyy-mm-dd-xx/tmpxx".
Id = HSLco31032 SR:H555006753
Split mirror backup session fails with:
"[Critical] From: SSEA<host> "" Time: <time>
Failed to find T-VOL/R-Vol of LDEVs.
[SseMapLdevToRdsk] Unable to found /dev/rdsks
file for LDEV = <number>".
Id = HSLco31434 SR:H555006835
Unexpected close reading message from the agent on the
Backup System (SSEA abnormally ends on R2).
Id = HSLco30701 SR:H555006685
Resolving fails on the Application host. The spt inq
structure returns corrupted results.
Id = HSLco31490 SR:H555006844
SSEA integration backup fails with:
"[Critical] From: SSEA<host_name> "" Time: <time>
Command "/etc/horcmgr" failed with exit code 3.
[Critical] From: SSEA<host_name> "" Time: <time>
Failed to start RAID Manager instance.
(Command /etc/horcmgr failed.)".
PHSS_24425:
Id = NSMex04086
Session status is "Completed/Failures" although there
is no any indication of errors.
Id = NSMex04209
SSEA Integration backup fails with an error:
"[Critical] From: SSEA<hostname> "" Time: <time>
Failed to find <volume/volume No.> of LDEVs.".
Id = NSMex04216
SSEA Integration backup reports the following warning:
"[Warning] Cascading structure of BC pairs found
(THIS IS UNSUPPORTED).".
Id = NSMex04392
SSEA Integration backup fails with an error:
"Filesystem <path> could not be mounted.".
Id = NSMex04267
SSEA Integration backup fails with an error:
"[61:1005] Got unexpected close from Split Mirror
Agent.".
Id = HSLco23886
LVM Mirror (XP Campus Cluster) is not supported
within OmniBack II SSEA Integration.
PHSS_22436:
Id = NSMex03360
SSEA Integration split does not appear to mount some
filesystems.
Id = NSMex03700
Disk resolving failed on Backup Host.
Id = NSMex03717
a) SSEA integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
[224:106] Resolving of object "filename" has failed.
(Cannot find block device path name of a logical
volume)"
b) SSEA Integration backup fails with an error:
"[Major] From: SSEA<hostname> "" Time: <time>
File system <filesystem> could
not be mounted to . (Invalid filesystem type.)"
Id = NSMex03482
Disk synchronization messages are incorrect.
Id = HSLco22201
OmniBack II SSEA integration is not supported on Sun
Solaris operating system.
Id = NSMex03651
Disk synchronization fails with:
"[Critical] From: SSEA<hostname> "" Time: <time>
[225:110] Mapping from LDEV to character device
file or disk failed for LDEV <dev> on
array <array>. (Unable to find character device
file for SureStoreE XP256 disk (LDEV))."
Id = NSMex03673
Backup fails with the following message:
"[Critical] From: SSEA<hostname> "" Time: <time>
Command "/usr/bin/pairdisplay -g" failed with
exit code 242.".
Id = NSMbb39679
OmniBack II aborts Business Copy split mirror
backup because one of the disks in a pair is in
status COPY.
Id = NSMex03547
SSEA Agent intermittently fails to resolve objects.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status.
Id = NSMex03913
SSEA backup fails with the following message:
"[Critical] From: SSEA<hostname> "" Time: <time>
Command "/usr/bin/pairdisplay -g" failed with
exit code 221.".
Id = NSMex03960
SSEA backup fails with the following error:
"Failed to start RAID Manager instance.
(Unable to find SureStoreE XP256 COMMAND device
file.)".
Id = NSMex03850
Sometimes volumes cannot be mounted on JFS 3.3
filesystem.
Id = NSMex03749
Mount function does not restore mount options.
Id = NSMex03563
Mounting of a filesystem fails.
Id = NSMex03931
OmniBack II SSEA Integration does not work on XP 512
for LDEVs with XP LUN addresses above 128.
Defect Description:
PHSS_25817:
Id = JAGad48627
If pre-exec script fails, cleanup does not start
post-exec script.
Resolution:
New environment variable is introduced. When
SSEA_ALWAYS_POST_SCRIPT in .omnirc file on
application host is set to 1, post-exec script
is always executed.
Id = NSMex04226
Backup is made in SSEA/split mirror backup environment
with the Application host in the cluster. When
restoring object on the Backup host (R2), which is not
in the cluster the cluster tag (-c y) from the
Application host is also restored, so the volume group
can not be activated properly.
Resolution:
By default the cluster tag on the Backup host (R2) is
disabled with the "vgchange -q n -c n" command. To
enable the cluster tag on Backup host, set the new
environment variable SMB_CLUS_DEACT=1 in the
/opt/omni/.omnirc file.
Id = HSLco30300
The command /etc/horcmgr fails if the command
device is used by another split mirror session.
Resolution:
New environment variables are introduced
SSEA_RM_RETRY and SSEA_RM_SLEEP.
SSEA_RM_RETRY defines the number of retries.
SSEA_RM_SLEE defines sleeping time in seconds,
before new retry is started.
Id = HSLco31032
The resolving from LDEVs to rdsks on the backup host
fails due to incorrect reporting of LDEVs to rdsks.
Resolution:
The resolving from LDEVs to rdsks is corrected.
Id = HSLco31434
SSEA agent on R2 does not read the number of rdsk
from the R1. Bug is produced while fixing the
NSMex04787 case on NT platform, but affected the
SSEA agent on the HP-UX platform.
Resolution:
The correct number of strings is read from the SSEA
agent on the R2 side.
Id = HSLco30701
The SCTL_InquiryDisk function returns empty or
corrupted inq structure.
Resolution:
The ioctl system function writes its output directly
to the inq structure. The "mapping from rdsks to LDEVs"
and the ScsiInquiry are enhanced.
Part of SSPUX350_057.
Id = HSLco31490
SSEA can not start the selected HORCMINST instance
number. It is already started by another RaidManager
process.
Resolution:
SSEA tries to start the instance with different
instance number up to five times.
PHSS_24425:
Id = NSMex04086
Message level of a resolving failure in XP environment
is set to "Normal" instead of "Major".
Resolution:
Message level is corrected.
Id = NSMex04209
If backup devices are exported to more than one port
and original devices have more than two mirrors, when
session is started and two of these ports are used for
that session, SSEA Integration detects more mirrors
than it is allowed.
Resolution:
Parsing of raidscan() output is improved.
Id = NSMex04216
If there are two or three mirror disks to source
disk, OmniBack II reports that cascading structure is
found although cascading structure is present only
when there are mirror disks to targer disk.
Resolution:
Searching for cascading structure is excluded as
this feature is not supported with OmniBack II
A.03.50 version.
Id = NSMex04392
Incorrect filesystem options are sent to R2 side.
For HFS filesystems the entries in the mnttab file
are not updated promptly.
Resolution:
Correct filesystem options are sent to R2 side.
/etc/mnttab is promptly updated for HFS filesystem.
Id = NSMex04267
SSEA API fails after 60 seconds during the change of
volume groups. SMB_TIMEOUT is hardcoded to 60 seconds.
Resolution:
SMB_TIMEOUT can be configured in .omnirc file for
situations where the changing of volume groups takes
more than one minute.
Part of SSPUX350_037.
Id = HSLco23886
LVM Mirror (XP Campus Cluster) is not supported within
OmniBack II SSEA Integration.
Resolution:
LVM Mirror (XP Campus Cluster) is supported within
OmniBack II SSEA Integration.
Please see Special Installation Instructions for more
details.
PHSS_22436:
Id = NSMex03360
XP256 Raid Manager's pairdisplay command returns
invalid status which causes some raw disks to fail
during resolving.
Resolution:
Status checking changed to ignore invalid status from
pairdisplay command.
Id = NSMex03700
If there is a lot of backup objects (usually case with
SAP databases) and these objects are placed in volume
group with a lot of stripped disks, then the size of
the internal message sent from SSEA-R1 to SSEA-R2 can
overflow hardcoded 100k limit.
Resolution:
New message format reduces message size significantly.
Part of the SSPUX350_007.
Id = NSMex03717
a) OmniBack II does not handle soft links correctly.
b) SSEA integration backup does not work properly in
case that a single session contains both filesystem
and rawdisk objects.
Resolution:
Fixes are implemented in ssea.
Part of the SSPUX350_007.
Id = NSMex03482
Disk synchronization failure reported as "Normal".
Resolution:
Message statuses are properly reported.
Id = HSLco22201
OmniBack II SSEA integration is not supported on Sun
Solaris operating system.
Resolution:
OmniBack II SSEA integration is supported on Sun
Solaris 7 and 8 operating systems.
Please find the integration manual in the
/usr/omni/bin/utilns directory after the patch is
installed.
Id = NSMex03651
IPC buffer for communication between SSEA Agents on
backup and application host is too small.
Resolution:
IPC buffer increased.
Id = NSMex03673
Pairdisplay command fails in ServiceGuard environment.
Resolution:
Hostname resolving is improved.
Id = NSMbb39679
OmniBack II does not treat status COPY as a valid
status.
Resolution:
OmniBack II waits (for configurable timeout) for the
second disk to change the status to PAIR.
Environment variables are:
SSEA_SYNC_SLEEP_TIME = <time in seconds>
SSEA_SYNC_RETRY = <number of retries>
Default values are 5 for SSEA_SYNC_SLEEP_TIME and
10 for SSEA_SYNC_RETRY.
Id = NSMex03547
Resolving of objects fails if stat() function reports
error for any entry in /etc/mnttab.
Resolution:
Irrelevant errors are skipped during the resolving.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status
because of timing problem.
Resolution:
Environment variable OB2EXECTIMEOUT is introduced.
Variable represents timeout (in seconds) after the end
of pre- and post-exec script. Default value is 0.
Recommended value is between 5 and 10 seconds.
Id = NSMex03913
Pairdisplay command fails if two session are started
at the same time.
Resolution:
SSEA Agent correctly detects service port numbers
availability.
Id = NSMex03960
SSEA Agent uses only those disks for which ioscan
reports state CLAIMED. Backup fails due to a fact that
some of the disks needed for session are in state SCAN.
Resolution:
Disks in state SCAN are reported as well as those in
state CLAIMED.
Id = NSMex03850
Changes made for JFS 3.3 support cause mount problems
on HP-UX 10.20 platform.
Resolution:
Code now properly works also for the HP-UX 10.20
platform.
Part of SSPUX350_016.
Id = NSMex03749
Filesystem is not mounted with the options that were
used before split mirror backup was performed.
Resolution:
Command line mount command is used instead of mount
function for vxfs filesystem.
Id = NSMex03563
Mount operation does not work properly on systems
with Online JFS 3.3 installed.
Resolution:
Mount API uses proper arguments.
Id = NSMex03931
Invalid configuration files are created for LDEVs
exported to LUN addresses above 128.
Resolution:
New environment variable SSEA_XP_PORTS is introduced.
Its value has to be set to "FC" when using Fibre channel
and LUN addresses greater than 128.
Part of SSPUX350_032.
SR:
H555006685 H555006753 8606179403 H555006844 H555006835
H555006603 H555005488 H555005717 H555005689 H555005681
H555004065 H555005289 H555003697 B554000781 B554000676
B554000847 B554000829 H555004533 H555004741 H555003490
H555003716 B554000521 B554000612 H555003817 H555004474
B554000803 B554000491 H555004919
Patch Files:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.03.50/
packet.Z
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.03.50/
packet.Z
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/packet.Z
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/require.dat
what(1) Output:
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-1020/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/ssea/hp/s800/hp-ux-11/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/packet.Z:
None
/opt/omni/databases/vendor/ssea/sun/sparc/solaris-26/
A.03.50/require.dat:
None
cksum(1) Output:
2870582339 2032349 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-1020/A.03.50/packet.Z
680922197 2032867 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-11/A.03.50/packet.Z
118923842 1546105 /opt/omni/databases/vendor/ssea/sun/sparc/
solaris-26/A.03.50/packet.Z
1830950196 19 /opt/omni/databases/vendor/ssea/sun/sparc/
solaris-26/A.03.50/require.dat
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_22436 PHSS_24425
Equivalent Patches:
PHSS_25818:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Patch Package Size: 5540 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_25817
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25817.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25817. 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_25817.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_25817.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_25817:
NOTE!
This patch has to be installed on the Installation
Server host.
The OB2 SSEA agent must be redistributed to the SSEA
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SSEA agent, refer to
the OmniBackII Installation guide.
NOTE!
PHSS_24425/PHSS_24426 introduces support for LVM Mirror
(XP Campus Cluster) with OmniBack II SSEA Integration.
More information about configuring LVM Mirror together
with OmniBack II A.03.50 can be found in files
/opt/omni/bin/utilns/CampusClusterConf.txt
/opt/omni/bin/utilns/SureStoreAdmin.pdf
after the patch is installed and SSEA Agent redistributed to
clients.
NOTE!
Patch PHSS_22436/PHSS_22437 introduces OmniBack II
HP SureStoreE Disk Array XP integration (SSEA) on Sun
Solaris.
In order to complete installation successfully, CORE patch
PHSS_22914/PHSS_22915 (or later) must be installed.
After installation of this patch, the manual
"HP OpenView OmniBack II, HP SureStore E Disk Array XP
Configuration Guide" will be available in file
/<OMNIBACK_HOME>/bin/utilns/surestore_sun.pdf.
In Chapter 2, it describes how to configure
the XP Disk Array in the Solaris Environment.
Patch includes the following Site Specific Patches:
SSPUX350_007
SSPUX350_016
SSPUX350_032
SSPUX350_037
SSPUX350_057
-----End of Document ID: PHSS_25817------------------------------------------
Document ID: PHSS_21873
Date Loaded: 20020124
Title: s700_800 10.X OV OB3.00 patch - INFORMIX packet
Patch Name: PHSS_21873
Patch Description: s700_800 10.X OV OB3.00 patch - INFORMIX packet
Creation Date: 02/01/23
Post Date: 02/01/24
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.03.00
Filesets:
OMNIBACK-II.OMNI-INF-P,A.03.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_21873
Symptoms:
PHSS_21873:
Id = JAGad00529
/opt/omni/lbin/util_informix.exe has ORA_SID where it
should be INF_SID.
Id = NSMex02676
Informix integration fails with the error:
"ERR_INF_DBACCESS_FAILED=8800"
Id = NSMex02868
Path for the util_informix.exe on Sinix systems is
wrong.
Id = HSLco15114
OmniBack II 3.00 does not support 64-bit version of
Informix 7.30.
Id = NSMex03006
Informix process cannot attach to the shared memory.
PHSS_18703:
Id = NSMex02125
The configuration script util_informix.exe fails with
the error code "*RETVAL*8813".
Defect Description:
PHSS_21873:
Id = JAGad00529
OmniBack II is not able to start Informix integration
if there is a Informix server profile file defined in
/etc/opt/omni/informix directory.
Resolution:
Fix is implemented in util_informix.exe.
Id = NSMex02676
util_informix.exe does not export some environment
variables because of using /bin/sh instead of /bin/ksh.
Resolution:
/bin/sh changed to /bin/ksh in util_informix.exe.
Id = NSMex02868
util_informix.exe on Sinix systems should reside in
/usr/omni/bin directory and not in the /opt/omni/lbin
directory.
Resolution:
ob2onbar.exe contains the correct path.
Id = HSLco15114
OmniBack II 3.00 does not support 64-bit version of
Informix 7.30.
Resolution:
OmniBack II 3.00 supports 64-bit version of
Informix 7.30.
Part of the SSPUX300_077.
Id = NSMex03006
When an Informix process and a Media Agent are started
on the same HP-UX 11.x host, Informix process aborts
because it can not attach to the Media Agent's shared
memory. The following error message is reported:
"IPC Can not Allocate Shared Memory Segment
System error: [22] Invalid argument => aborting."
Resolution:
HP-UX parameter NULL is used instead of pointer to
the beggining of the shared memory for attaching to
shared memory.
Part of the SSPUX300_104.
PHSS_18703:
Id = NSMex02125
The script util_informix.exe searches for the
executable onbar_b, which is not present on the
Informix system. Correct name of the executable
is onbar_d.
Resolution:
Changed onbar_b to onbar_d in the util_informix.exe
script.
SR:
B554000134 B555004741 8606131379 B555004657 5003453555
Patch Files:
/opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/
A.03.00/packet.Z
/opt/omni/databases/vendor/informix/hp/s800/hp-ux-1020/
A.03.00/packet.Z
/opt/omni/databases/vendor/informix/siemens/r400/sinix/
A.03.00/packet.Z
what(1) Output:
/opt/omni/databases/vendor/informix/hp/s800/hp-ux-10/
A.03.00/packet.Z:
None
/opt/omni/databases/vendor/informix/hp/s800/hp-ux-1020/
A.03.00/packet.Z:
None
/opt/omni/databases/vendor/informix/siemens/r400/sinix/
A.03.00/packet.Z:
None
cksum(1) Output:
1090435538 1082384 /opt/omni/databases/vendor/informix/hp/
s800/hp-ux-10/A.03.00/packet.Z
2496572268 1929961 /opt/omni/databases/vendor/informix/hp/
s800/hp-ux-1020/A.03.00/packet.Z
3540193908 871239 /opt/omni/databases/vendor/informix/
siemens/r400/sinix/A.03.00/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_18703
Equivalent Patches:
PHSS_21874:
s700: 11.00
s800: 11.00
Patch Package Size: 3850 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_21873
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_21873.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_21873. 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_21873.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_21873.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_21873:
NOTE!
Patch has to be installed on the Installation Server host.
The Informix packets must be redistributed to the Informix
client system(s) afterwards to get the fixes into effect.
Patch includes the following Site Specific Patches:
SSPUX300_077
SSPUX300_104
-----End of Document ID: PHSS_21873------------------------------------------
Document ID: PHSS_25988
Date Loaded: 20020122
Title: s700_800 10.20 OV SAPSPI7.X Monitor bin.s A.07.23
Patch Name: PHSS_25988
Patch Description: s700_800 10.20 OV SAPSPI7.X Monitor bin.s A.07.23
Creation Date: 02/01/16
Post Date: 02/01/22
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
OpenView Smart PlugIn for SAP 7.1
Filesets:
SPI-SAP-ITO.SAPSPI-SOL,A.07.10
SPI-SAP-ITO.SAPSPI-AIX,A.07.10
SPI-SAP-ITO.SAPSPI-HP-UX,A.07.10
SPI-SAP-ITO.SAPSPI-WINNT,A.07.10
SPI-SAP-ITO.SAPSPI-TRA,A.07.10
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25988
Symptoms:
PHSS_25988:
- r3moncol coredumps on all supported platforms
under certain configurations
- importing A.07.22 transports into SAP 31I
system does not work correctly
Defect Description:
PHSS_25988:
- r3moncol coredumps with certain configurations.
There are some combinations of messages that
make r3moncol coredump. In SAP there is a SAP
SPI table containing the actual message and
a table containing message details.
r3moncol assumes that for each message there
are also message details and tries to read
the message details table. But sometimes
this is not the case. => r3moncol accesses a
non-initialized pointer to a non-existent table
entry. => coredump.
- Function Module SAPLZSPB, Program LZSPB$18
The field "ZHPSPI30" is unknown, but there
are the following fields with similar names:
"ZHPSPI05", "ZHPSPI06A" and "ZHPSPI08L".
This is the error during the transport.
Resolution:
- since the information in the details table
is not used anymore,the function call to
read the message details was removed.
- Built delta transport which fixes this error.
This transport is dependent on the A.07.22
transport.
THIS TRANSPORT IS FOR SAP 31 ONLY!!!
SR:
B555012978 B555012858
Patch Files:
/opt/hpitosap/install/C/EXECUTABLES/ibm/rs6000/aix/monitor/
r3moncol32.Z
/opt/hpitosap/install/C/EXECUTABLES/ibm/rs6000/aix/monitor/
r3moncol64.Z
/opt/hpitosap/install/C/EXECUTABLES/hp/s700/hp-ux10/monitor/
r3moncol.Z
/opt/hpitosap/install/C/EXECUTABLES/hp/pa-risc/hp-ux11/
monitor/r3moncol32.Z
/opt/hpitosap/install/C/EXECUTABLES/hp/pa-risc/hp-ux11/
monitor/r3moncol64.Z
/opt/hpitosap/install/C/EXECUTABLES/sun/sparc/solaris/
monitor/r3moncol32.Z
/opt/hpitosap/install/C/EXECUTABLES/sun/sparc/solaris/
monitor/r3moncol64.Z
/opt/hpitosap/install/C/EXECUTABLES/ms/intel/nt/monitor/
r3moncol.exe
/opt/hpitosap/install/C/EXECUTABLES/ms/intel/nt/monitor/
OvSpiASER3.dll
/opt/hpitosap/trans/R3Trans.7.23.tar
what(1) Output:
/opt/hpitosap/install/C/EXECUTABLES/sun/sparc/solaris/
monitor/r3moncol32.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/sun/sparc/solaris/
monitor/r3moncol64.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/ibm/rs6000/aix/monitor/
r3moncol32.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/ibm/rs6000/aix/monitor/
r3moncol64.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/hp/s700/hp-ux10/monitor/
r3moncol.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/hp/pa-risc/hp-ux11/
monitor/r3moncol32.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/hp/pa-risc/hp-ux11/
monitor/r3moncol64.Z:
None
/opt/hpitosap/install/C/EXECUTABLES/ms/intel/nt/monitor/
r3moncol.exe:
OvCTrace.h 0.27 (05 Jun 2000) Utilities
OvMFCCString.h 0.11 (24 Feb 2000) Utilities
/opt/hpitosap/install/C/EXECUTABLES/ms/intel/nt/monitor/
OvSpiASER3.dll:
OvCTrace.h 0.27 (05 Jun 2000) Utilities
OvMFCCString.h 0.11 (24 Feb 2000) Utilities
/opt/hpitosap/trans/R3Trans.7.23.tar:
None
cksum(1) Output:
2636532024 1032347 /opt/hpitosap/install/C/EXECUTABLES/sun/
sparc/solaris/monitor/r3moncol32.Z
1226709311 1405741 /opt/hpitosap/install/C/EXECUTABLES/sun/
sparc/solaris/monitor/r3moncol64.Z
3289931806 939097 /opt/hpitosap/install/C/EXECUTABLES/ibm/
rs6000/aix/monitor/r3moncol32.Z
1342684360 989519 /opt/hpitosap/install/C/EXECUTABLES/ibm/
rs6000/aix/monitor/r3moncol64.Z
2088059672 1184977 /opt/hpitosap/install/C/EXECUTABLES/hp/
s700/hp-ux10/monitor/r3moncol.Z
2221868074 1212645 /opt/hpitosap/install/C/EXECUTABLES/hp/
pa-risc/hp-ux11/monitor/r3moncol32.Z
3156170396 1543599 /opt/hpitosap/install/C/EXECUTABLES/hp/
pa-risc/hp-ux11/monitor/r3moncol64.Z
3658298953 73728 /opt/hpitosap/install/C/EXECUTABLES/ms/
intel/nt/monitor/r3moncol.exe
997714394 139264 /opt/hpitosap/install/C/EXECUTABLES/ms/
intel/nt/monitor/OvSpiASER3.dll
3566547879 2201600 /opt/hpitosap/trans/R3Trans.7.23.tar
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHSS_25219
s800: 10.20: PHSS_25219
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
ITOSOL_00134:
sparcSOL: 2.6 2.7 2.8
PHSS_25989:
s700: 11.00
s800: 11.00
Patch Package Size: 10540 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_25988
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25988.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25988. 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_25988.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_25988.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
Install the patch on the
management server using SD.
HOW TO INSTALL THE NEW BINARIES
ON THE MANAGED NODES:
1)
execute the following commands:
cd /opt/hpitosap/install
./r3itoins
r3itoins propmts you with
"Do you want to upload the SAPSPI
VPO UI integration (opccfgupld)?
<y,n>"
Answer with n
The patched binaries will be
uploaded into the ITO distribution
directory.
2)
Redistribute ONLY the monitors
to the managed node with the
"Force Update" option enabeled.
NOTE: Steps 2 & 3 are required
ALSO after REMOVING the patch to
put back the original binaries
into the ITO distribution
directories and to the managed
nodes.
3) To import the transports
refer to p. 67 in the Admin
Ref Guide. Use the option U26
to import the transports
unconditionally. To use the
A.07.23 transports it is absolutely
required to have the A.07.22 imported
properly.
-----End of Document ID: PHSS_25988------------------------------------------
Document ID: PHSS_25370
Date Loaded: 20020122
Title: s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
Patch Name: PHSS_25370
Patch Description: s700_800 10.20 OV OST3.0 Cumulative A.03.00 patch
Creation Date: 17/01/02
Post Date: 02/01/22
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
HP OpenView OmniStorage A.03.00.00
Filesets:
OMS.f_server,A.03.00.00 OMS.f_client,A.03.00.00
OMS.common,A.03.00.00 OMS.f_gui,A.03.00.00
OMS.f_fs,A.03.00.00 OMS.manpages,A.03.00.00
OMS.documents,A.03.00.00
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHSS_25370
Symptoms:
PHSS_25370:
1. Id = NSMex04098
'par' command fails when the source platter
has more blocks than the destination platter.
2. Id = NSMex04227
'listp -B' shows wrong number of rawblocks for
tape device after migration is started.
'listp' man page needs rework to specify full
detail for '-B' and '-S' options.
3. Id = NSMex04140
The system hangs/panics when a big number
of files, migrated to MOs, are deleted.
4. Id = NSMbb38043
After about 307,000 files, further migration
(migout) to a 5.2GB MO was not possible.
The 'ager' was able to run and to find migration
candidates, but the physical 'migout' failed.
5. Id = NSMbb41618
The 'qqr' output does not have any request in
the queue, although some of the requests in the
truncation lists
(from /var/opt/omnistorage/data/qr directory)
are not completed yet. If we restart the 'qr',
it checks if there are some truncation requests
left and starts with their processing.
6. Id = HSLco27922
'par' attempts to assign guest IDs to platters.
After it fails, it displays an error message:
'Unable to set guest flag for volume fa11.
JMD error: Volume belongs to a volume set'
7. Id = NSMex04573
'listp' always shows the wrong free space for
Worm media after migration and after
performing an 'exportp/importp' command.
8. Id = NSMex04421
'listp' always shows less space on the mirror
platter, after 'sync_media' finished.
9. Id = NSMex03489
'sync_media' does not work when media is hpufs
and it is write protected.
10.Id = HSLco28605
SIDF API fails to write file set and volume
trailer.
11.Id = JAGad49998
There was no logging during the manual execution
of the 'exportp/importp' commands.
12.Id = NSMbb29315
Logging not resumed after space was freed in
'/var'.
13.Id = NSMbb29275
Keep track or warn user if a platter is manually
mounted/loaded.
14.Id = NSMbb29271
'vsbind' allows to bind foreign volume sets to
a MFS.
15.Id = NSMbb41726
If the 'jmd' is killed while the 'qr' queue is
filled up, the used platter volume remains mounted.
16.Id = NSMex04451
'qr' fails to mount platters file system through
NFS.
Error reported in qr log:
"jmountv() failed, jerrno 'Can't mount volume's
filesystem'"
"The qr could not mount/load the volumes and the
jmd is remote. Fix: Check jmd's remote database."
17.Id = NSMbb29294
Lack of media caused a filled file system and core
dump.
18.Id = HSLco30178
man page for 'consolidate' command should be
changed
19.Id = HSLco23197
In /etc/opt/omnistorage/ directory there is
no 'agercfg' file. Some configuration files
need update of documentation.
PHSS_22743:
1. Id = NSMex03222
The device files created by installchanger for DLT
devices are incorrect.
2. Id = NSMex03959
zls showing 100% magnetic while only last block of
chunk on magnetic.
3. Id = NSMex03925
Free space on sidf media is not very well
managed/calculated.
4. Id = NSMex04140
Ager and other OMS commands are just hanging while
going through the list of mounted file systems.
5. Id = NSMex03844
Second tape is never loaded in stacker mode.
6. Id = NSMex04154
migout -m switch didn't work as described in man
page.
7. Id = NSMex04098
Write a par archive to MO volume exits with error
"Can't erase the remaining media start = ..."
PHSS_21065:
1. Id = HSLco20318
Consolidate: purify reports FNH error
2. Id = HSLco19774
jmd dumps core if jukebox is not connected
3. Id = NSMex03366
jmdbackup/jmdrestore fails in case of Grau or
barcode-name boxes
4. Id = NSMex03260
Free space on mirror smaller then original
5. Id = HSLco18392
zstartup and zshutdown scripts don't work correctly
in case that OMS server and client are on different
machines
6. Id = NSMex03037
An attempt to get id of other side of media 10000
failed
7. Id = NSMex03020
Last volume from GRAU didn't pass to jmd database
8. Id = NSMex02823
The migin performance dropped significantly after an
upgrade to 3.0. This problem appears in case of
WORM media
9. Id = JAGab76149, NSMex02958
rpc number problem
10. Id = NSMex02745, NSMex03270
Migout from the client system doesn't work.
The behavior we see is that the request is just
staying in the queue forever and there is no error
message logged anywhere.
11. Id = JOSqa00342
problem with add_vol man page and some errors in log
files
12. Id = NSMex02672
The qr hangs on trying to migrate zero length files
13. Id = NSMex02653
Confusing messages on CLEANUP
14. Id = NSMex02636
wt-check hangs when processing files with size 0
15. Id = NSMex02627
The man page has no list of supported JB devices
16. Id = NSMex0262
Massive migouts failing
17. Id = HSLco20623
Installchanger doesn't show us possible HW address
18. Id = HSLco20331
Purified jmd reports free memory read error.
After reviewing code found out that license removal
was completely wrong.
19. Id = NSMex03270
qr can't start because jmd can't give license to
qr. Reports an error message that there is no
license for that machine.
20. Id = JOSqa0034
Consolidate coredump, run out of memory
21. Id = NSMex03473
jmdrestore will never restore onsite volumes.
22. Id = NSMex03121
When ded check free space on /usr dir
(from /etc/fstab mount config file)
system panic occur.
23. Id = HSLco21464
Fibre Channel data transfer not supported
24. Id = HSLco21524
mediaset and mediaformat tools not available
for OmniStorage 3.0.
25. Id = NSMex03537
Rebuild doesn't work properly if both paths
in the dual path mount point have an
underscore.
An extra path appears when we have a dual
path mount point.
26. Id = NSMbb37517
OMS delete guest media from database (DB)
while inventory is performed.
27. Id = HSLco21556
what(1) command of some OMS binaries still
shows OmniStorage_0210
28. Id = NSMex03564
starting jmdrestore command, message 'not fully
implemented' was shown
29. Id = NSMex03588
hsm_session -ka doesn't work as documented
PHSS_19038:
1. Id = NSMex02262
ager writes annoying "logging started/stopped"
messages into agerlog
2. Id = JOSqa00325
resid man page is not understandable
3. Id = JOSqa00324
rebuild man page examples have old syntax
4. Id = NSMex02367
multi level migration doesn't free space on
secondary layer
5. Id = JOSqa00327
zls -l shows wrong output
6. Id = NSMex02401
consolidate problems
7. Id = JOSqa00328
Consolidation of tapes - full until physical EOT
failed
8. Id = NSMex02450, NSMex02335, NSMex02478, NSMex0243
qr drops migout request for files in bulk mode
9. Id = NSMex02452
jmdrestore -f 99Jun01.1 fails if set of platters
is owner 10
10. Id = JOSqa00331
Bad format detected for JMD_MEDIA_IN_ERROR
and MIGIN_NO_SUCH_PLATTER
11. Id = NSMex02469
License problem when '0' in IP Address
12. Id = NSMex02508
Request to have a tool to read metadata from
nearline storage
13. Id = JOSqa00332
jlog and qrlog log messages incomplete
14. Id = JOSqa00336
license manager (jmd) gets confused if
license.use file remained on disk
15. Id = NSMex02483
A5711310 - Consolidate: Can't open file by inode :
Error 0 (0)
PHSS_17476:
1. Id = NSMex02018
man page for ager : AGER_MAXSIZE is 1.000.000,
should be 128.000.000
2. Id = NSMex02015, NSMex02016
hsm_session display format problem
3. Id = NSMex02026
Bulk ager complains about wrong process id
4. Id = JOSqa00314
Add detailed Info to iocfg for performance config
5. Id = JOSqa00313
Add detailed Info to brapicfg for performance config
6. Id = JOSqa00307, NSMex02253
copyp does NOT work in OMS 3.0
7. Id = JOSqa00298
qrlog ERROR - no space available
8. Id = JOSqa00309
5.2 GB MO Jukebox not supported
9. Id = JOSqa00312
wrong mail format FREEPOOLVS_PROBLEM_MAIL
10. Id = NSMex02038
hsm_admin -I additional information needed in
installation guide
11. Id = JOSqa00308
copyp - documentation change
12. Id = NSMbb21706
agerlog message logging is consuming disk space
(SR #1653276659, SR #1653276667)
13. Id = NSMex01976
Lack of information when using vsadm -l
14. Id = NSMex02088, NSMex02177
STK direct connect tape library, jmd core dump
15. Id = NSMex01992, NSMex01191
jmd: No drive number in jlog if media is set
to error state
16. Id = NSMex01975
Active mode ager continuously submitted migout
requests not stopping at ALWM
17. Id = NSMex01969
volsets not created if TMPDIR environment variable
is set
18. Id = NSMex00837, NSMex00371, NSMex01141
Rebuild fails to rebuild
(SR #5003409540)
19. Id = JOSqa00315
remigration of a file to a full platter fails
20. Id = NSMex02031
Enhancement request to disable timeout on bulk ager
21. Id = NSMex02099
ager in bulk mode runs longer than expected.
22. Id = JOSqa00320
creation of a<fsid>/b<fsid> file by ager needs
redesign
23. Id = JOSqa00318
forever licenses will not be granted
24. Id = JOSqa00316
migout large files to sidf tape failed
25. Id = JOSqa00319
jmdrestore does not restore large number of bytes
26. Id = NSMex0219
while performing an inventory jmd dies through
segmentation violation
27. Id = NSMex02328
Abnormally stop sync_media leaves media in
inconsistent state
28. Id = JOSqa00322
Migout request remains in Qr queue although file has
been migrated out
29. Id = NSMex02349
Migration to 8x WORM media does not access next
medium with available space
Defect Description:
PHSS_25370:
1. Id = NSMex04098
'par' command works with ioctl system call. Error
comes when source has more blocks than destination,
and in that case ioctl gets wrong parameters
(wrong number of blocks).
Resolution:
Add checking if destination space (blocks) is less
than source space.
2. Id = NSMex04227
When migration is started, 'listp -B' shows default
number of rawblocks, but not the number of rawblocks
of a formatted media.
Resolution:
Fixed 'listp' so now 'listp -B' shows correct number
of rawblocks, after migration is started for tape
device.
3. Id = NSMex04140
'rm' is handled as asynchronous request and the
dm event queue is filled up with requests, which
uses up all system resources and the system
hangs/panics.
Resolution:
'zrm' is created. 'zrm' is an OMS wrapper around the
standard 'rm' command which checks the number of
events for the 'OMS_QRASYNC' session in the kernel
outqueue ('qrasyninf' returns the number),
and pauses it if the number of events is higher
than 1000.
4. Id = NSMbb38043
The reason for wasted space on MOs (small files are
migrated) is the organization of the HFS file
systems.
If the size of a file is less than the logical
block size of the FS on MOs, then HFS includes
fragmentation for better file system space
utilization.
Small files are then able to utilize these
fragments with the following restrictions:
- The fragments are only used at the end of the
file
- All fragments are contiguous
- All fragments come from the same block
When the files are smaller or equal than half the
size of the logical blocks, then the last two rules
allow to have more than one file in one logical
block. If the files are larger than half the size of
the logical blocks, then the total number of small
files, which can be migrated to the MO media, is
equal to the total number of logical blocks in that
FS.
Resolution:
When this situation happens (number of logical block
is 0), do not consider this MO as candidate any more;
mark it as full instead. The free space will be set
to 0 (zero) for these media.
5. Id = NSMbb41618
The only time when the 'qr' checks if there are
unprocessed truncation lists, is after restarting.
If the 'qr' has to handle requests with a higher
priority (like 'migin/migout') while processing
truncations, truncation requests are left
unprocessed in the qr lists.
Resolution:
Added part of code where, after some other requests
are completed, 'qr' checks if there are unprocessed
truncation requests and starts with their
processing. We do not have to wait on restart of the
'qr' anymore.
6. Id = HSLco27922
During the restore process, 'par' is used to restore
platters. If restore goes to the same platter that
has been used as source in backup process, 'par' will
attempt to assign a guest ID to that platter. This
happens because the 'restore_vbfs' script doesn't set
'-g' flag on the par CLI.
Resolution:
Set '-g' flag so that the 'par' command can perform
copying without assigning of a guest ID flag to
the destination platter.
7. Id = NSMex04573
This problem is related to HSLco28479.
Updating of the free space after migration was
not calculated correct. But the free space
was correct after export/import of the media.
Resolution:
We added a call for updating the free space
after migration, like it is performed for
the 'importp' command.
8. Id = NSMex04421
This problem is related to HSLco29297.
The free space for mirrored media was not updated
correctly.
Resolution:
A call was added for updating the free space on
the mirror, like it is already performed for the
source media.
9. Id = NSMex03489
The handling of 'write protected' MO source media
(hpufs) was not fully implemented and 'sync_media'
failed though.
Resolution:
Some logic was added to the 'fstask' file to enable
the mounting of write-protected media.
10.Id = HSLco28605
The problem is caused by the SIDF data handling.
The additionally required space for the file set
header/trailer information was not taken into
account when choosing the target media for
migration; but only the required space for the
user data. The data migration then failed as the
meta data could not be written to the chosen
media.
Resolution:
The 'jmd' will ask for extra free space if it
detects that one of the potential candidates is
SIDF formatted.
The SIDF API was modified to perform an extra check
before attempting to write the buffer.
It will check for 1 free block in addition to the
size of the buffer.
11.Id = JAGad49998
During the exporting/importing of media (MO, WORM
and Tape), when 'jlog' is set to WARNING, nothing
was logged.
Resolution:
We added a logging, after the 'exportp/importp'
commands are performed.
12.Id = NSMbb29315
After the '/var' directory was filled to some high
value, and after space was freed, logging was not
resumed.
Resolution:
After performing some changes in the source code,
logging is stopped if '/var' is filled up more
than 90% until space is freed. After space is
freed, logs are adding regulary.
13.Id = NSMbb29275
After manually loading/mounting volumes, migration
will not finish until manually unloading/unmounting
the volumes again. These actions required adding
a warning in a log file.
Resolution:
We added a warning in a 'jlog' log file and some
variables to prevent messages from showing in the
log more than once.
14.Id = NSMbb29271
'vsbind' does not include checking for IDs of volume
sets and migrating file systems.
Resolution:
New function was added for checking of IDs for
migrating file systems and volume sets.
15.Id = NSMbb41726
To 'unmount' and then 'unload' platters with active
requests in the 'qr' queue, we should kill the
'io_server' first and in that way force the 'jmd'
to 'unmount' used platter.
Resolution:
Performing suspension of the MFSs and then killing
'jmd.'
16.Id = NSMex04451
The problem is caused by bad conversion of
filesystem IDs to string.
Resolution:
OmniStorage uses the 'statfs()' system call to
determine file system specific data.
According file system type string representation has
been copied into a field of the 'port_fs' structure.
This is replaced by the 'statvfs()' system call.
This system call already returns a string
representation of the file system type, so any
additional conversion is not necessary any more.
17.Id = NSMbb29294
When starting 'sync_media' from 'crontab' and the
mirror media wasn't in the library or when one of
the attributes (owner, group or state) was not set
properly for the mirror media, the '/var' directory
(from mail or from log file) was filled up
continually. This was the reasone that 'sync_media'
core dumps.
Resolution:
This error is now handled, so if this case happens,
mail will be shown only once and be time stamped.
In this case, execution of 'sync_media' will be
aborted.
18.Id = HSLco30178
Changing information about kernel parameters
('maxdsiz' or 'maxdsiz_64bit').
Resolution:
New info is added in the 'consolidate' man page.
19.Id = HSLco23197
Prototype of 'agercfg' file is not included
in packaging procedure.
Resolution:
'agercfg' file is included in packaging procedure.
Man pages and AdminGuide is updated with information
about configuration files.
PHSS_22743:
1. Id = NSMex03222
Minor numbers were ending on 4, that is
correct only for DLT2000. But what actually is
required is to have a 'best density' device file
for DLT2000/4000/7000, which means the minor
number needs to end on a 0.
Resolution:
Invoke DEN_M_BEST in installport.H file (value 0).
2. Id = NSMex03959
Problem was that 'zls' shows that the whole last
chunk is on magnetic.
Actually, only last block is on magnetic.
Resolution:
'zls' now shows the right percentage of magnetic
when the last block of chunk is there, and new filed
in output message is added.
3. Id = NSMex03925
Problem was that during migration out on sidf media
calculation of free space was not done correctly.
Actually, shown free space is much less than it is.
Resolution:
Changed file: QmigoutData.C
Free space is calculated correct.
4. Id = NSMex04140
Problem was that while the attribute inode of /usr is
locked, it needs to access a catalog file on this
file system to handle an error situation and this is
how it's getting into a deadlock situation.
Rresolution:
Exclude locking of attribute inode of /usr.
5. Id = NSMex03844
Problem was that in stacker mode first tape is never
unmounted, so second tape couldn't be mounted.
Resolution:
First tape is unmounted.
6. Id = HSLco26541
When started migration with -m switch if volume
doesn't exist or volume is full migration won't
start
Resolution:
Fixed migout to check if volume is full or volume
doesn't exist so migration will go to best platter
for migration
7. Id = NSMex04098
Par command fail when source platter has more blocks
then destination platter
Resolution:
Par command works with ioctl system call. Error comes
when source has more blocks than destination in that
case ioctl gets wrong parameters (wrong number of
blocks).
That problem is resolved.
PHSS_21065:
1. Id = HSLco20318
Tried to deallocate non-heap memory
Resolution:
Wrong source line commented out
2. Id = HSLco19774
If jukebox is not connected and you perform
migout command the jmd will core dump, because
it use a NULL pointer which is not tested.
Resolution:
Test NULL pointer.
3. Id = NSMex03366
First error
When jmdrestore restore volume data it tries
to restore names (aliases) too, and this is
perform by removing old names and setting new one.
The problem occurs if you have a box with
barcode-name, because the names can't be removed.
In GRAU SILO or STK are no slots information
and OMS use names for manipulating volumes.
Second error
"Cannot verify identity of volume: 2b (2a)"
This message occurs if you had some volumes
formatted for mirroring and had not properly
configured yet (if owner was not 10).
Resolution:
If we avoid removing/restoring names for
bar-coded boxes then command must work.
Do not read media by Real ID.
4. Id = NSMex03260
There is no free space problem at the time of
sync_media, but the original media have wrong free
space calculated. How this could happen?
By the time of exportp importp or full inventory
the media's attributes are completely reread.
The free space of media too, but after first miguot
new free space of media became, as is only file
from last migout on media. Why?
OMS use one variable for storing free space and
another for space and another for storing used
space, and in our case the used space was not
recalculate by the time of importp.
This happened only on MO sidf formatted media.
Resolution:
Set variable which contain used media space on
proper value.
5. Id = HSLco18392
It is not correct to check if qr and ded are running
on server side of OMS.
Also, on server side mfs shouldn't be checked.
At the other hand, on client side it is not correct
to check if jmd is running.
This will be changed.
Resolution:
Change scripts to check if it is running on server
or client side and then show appropriate message.
6. Id = NSMex03037
Intention of this fix is wrong mapping a system
set ID into a box and slots Ids with GRAU
SILO box. This happened only with double-sided
media in GRAU SILO box when sync_media
command is performed.
Where was the bug:
------------------
The problem lay in function, which transform
system set ID into box and slot ID, but GRAU
SILO box doesn't have a slot IDs and a slot
ID is set to -2.
Unfortunately transformation function was not
prepared to this situation.
Algorithm for decode sys ID was wrong, because
it didn't consider that slot could be negative.
So, at decode time box ID became one less then
proper.
There was another error cause of wrong type
conversion from signed to unsigned integer.
The reason was negative slot number again.
Resolution:
Check if slot became negative then increase
box ID by one.
Customize unsigned int type to signed.
7. Id = NSMex03020
Jmd couldn't access to other side of last platter
in box, because the last media was not set to
database at full inventory.
Resolution:
Bug was in file top/src/lm/lib/lm_sl/lm_grau.c
function volIterate.
The last iteration doesn't return appropriate value
from volserinfoP variable.
Actually, the variable volserinfoP is set to right
value, but in the same sentence counter myvolcount
is incremented and after that it was checked again
if it was exceeded the nActualCount.
This last check is always true and procedure return
NULL_VOLINF_PTR instead of volserinfoP.
8. Id = NSMex02823
After upgrading to OMS 3.0 (from OMS 2.2) the migin
performance for WORM's dropped remarkable. The
reason was a function, which was introduced when
the migout has been redesigned. One part of the
function was really necessary for migout but was
even executed for migin requests.
Resolution:
SeqMediaService: PrepareMigoutContexts only necessary
for migout
9. Id = JAGab76149, NSMex02958
ONC RPC Program number for rpc.kill was not reserved
program number but it was from user-defined range.
The same program number was used by some other
applications.
Resolution:
Implement rpc.kill that uses reserved ONC RPC program
number.
10. Id = NSMex02745,NSMex03270
Problem is in doing migout from client with 2 LAN
cards. Communication Server/Client doesn't work.
All OMS executables do not support 2 LAN cards on
a host. Until now OMS called the function
gethostname() to determine the IP address for
communication between executables.
If the customer has 2 LAN cards on one machine there
is no possibility to take the other one.
Resolution:
A new config file /etc/omslancfg was introduced. It's
content looks like this:
OMS_HOSTNAME=myhostname
Next steps have to be done on server and client
machines:
server:
add the name of oms client in file
/etc/opt/omnistorage/jhosts
client:
add jmcfg entry of the server machine
JMD_MACHINE=myserverhostname
11. Id = JOSqa00342
add_vol -v option: from man page user could conclude
that -v option is used for mirroring by default.
There was fatal error message in jlog file:
FATAL (19561):
08/30/1999 10:33:31 Bad format detected for
JMD_NO_OPEN_HD.
Resolution:
man page for add_vol command was changed
log entries were corrected
12. Id = NSMex02672
The migmv command 'migmv -R ...' traverses the
directories and creates qr-requests for each file.
The qr hangs when files of size=0 occurs.
Resolution:
The migmv checks the file size and avoids to
create a qr requests when file size is zero.
13. Id = NSMex02653
Former OMS cleanup utility is cleanp from 3.0 on
because there is a HP-UX command cleanup.
Some error messages still use CLEANUP.
Resolution:
Change the error messages from cleanup to cleanp
14. Id = NSMex02636
wt-check hangs and didn't come to end when processing
files with zero length.
The qrlog shows:
WARNING (13787):
07/27/1999 17:32:03 QmigoutIoC.C[368] ASSERT(3)
FAILED
Resolution:
Since the wt-check simply uses a system call for
'zfind' it is easy to insert the '! -size 0' into
the source file of 'wt-check'.
15. Id = NSMex02627
There could not be found details on the new
configurations in the jmcfg man page.
E.g. What is HP_ODL, HP_ODL_DUAL_PICKER ...
The manual says: Run jmd -c, but this is not
updated neither.
Resolution:
Entries have been made within the explanation of the
parameter JMD_BOX in the man page of jmcfg.
The part dealing with Boxtypes now reads like:
Boxtype is the box type number or name.
For a list of boxes supported by a specific server,
run jmd -c.
To inform about all supported MO disk and Tape
library types please refer to the "HP OpenView
OmniStorage Version A.03.00 Software Release Notes
& Installation Guide", chapter 4, "Configuring
OmniStorage Devices".
16. Id = NSMex0262
There is a wrong call to the function 'jsetvolsize'
in `the source 'QmigoutSupport.jmd.C' where the
qrlog message points to.
One of the parameters of 'jsetvolsize' is a 64bit
value but should be only a 32int value.
This was changed.
Resolution:
There is a wrong call to the function 'jsetvolsize'
in the source 'QmigoutSupport.jmd.C' where the
qrlog message points to.
One of the parameters of 'jsetvolsize' is a 64bit
value but should be only a 32int value.
This was changed.
17. Id = HSLco20623
Installchanger doesn't show HW path for robotic in
case that machine is 800 and robotic driver is sctl.
Resolution:
Currently, installchanger determines name of robotic
driver, regarding machine model. If machine is 800,
it set robotic driver to spt, and if is 700,it set
robotic driver to sctl. This is wrong. It is
possible to have 800 machine and sctl driver (for
D, R or K). I have changed installchanger to grep
output of ioscan and if there is a line like:
ctl 0 8/16/5.7.0 sctl CLAIMED DEVICE Initiator
robotic driver is set to sctl. Otherwise, it is set
to spt.
18. Id = HSLco20331
License removal was completely wrong.
Resolution:
Change was made in function jmrelclicense().
Algorithm for removal of node license info was
wrong. Pointer of deleted node was used.
Current status: if node with license info is
found it will be deleted.
But after that traversing will be stopped.
19. Id = NSMex03270
When OMS server and/or client has two lan cards,
it is not just problem with licenses.
All OMS executables do not support 2 lan cards
on a host.
Resolution:
The new configuration file /etc/omslancfg was
introduced on machine that has two LAN cards.
In this file, OMS_HOSTNAME variable
should be set to name that we want to use
in OMS. Than on server, we need to add license for
IP address of the name that we want to use in OMS,
the same as value of OMS_HOSTNAME variable.
20. Id = JOSqa0034
Memory was used without checking. Memory wasn't
deallocated.
Resolution:
Checking memory before using. Deallocating memory
that is not used any more.
21. Id = NSMex03473
I believe that jmdrestore is supposed to restore
volume and volume set information in case the
media database got corrupted for one or another
reason. Now, the behavior is a little strange,
because volumes have to be available in
the media database as a prerequisite to be restored
by jmdrestore. This means that jmdrestore is only
able to restore attributes like state and ownership
to volumes which are already current in the media
database.
The functionality which seems to be missing is a
restore of volumes which are currently not in the
database. Let's suppose the following scenario.
Several volumes are in state onsite while a
jmdbackup is created. Then the database gets
corrupted or we are loosing it. After an inventory,
the onsite volumes are not listed anymore. That's
normal. But why can't we restore them in the
database with jmdrestore?
Resolution:
Add new option to force restoring missing media in
database. Improve searching media.
22. Id = NSMex03121
When ded check free space on mount point first make
a lock on that mount point, then check if mount point
is MFS, if it is then ded get attributes from MFS and
after release lock. Ded never check if lock is really
released.
Resolution:
Ded have to check just MFS mount points, not all
mount points.
23. Id = HSLco21464
Fibre Channel data transfer not supported
Resolution:
intallchanger changed to correctly handle Fibre
Channel hardware path
24. Id = HSLco21524
mediaset and mediaformat tools not available for
OmniStorage 3.0.
Resolution:
Include mediaset, mediaformat and their man pages to
OmniStorage 3.0.
25. Id = NSMex03537
An extra path rebuilds since the mount path is not
stripped off correctly.
Problem with double underscores was a problem with
length of mount point.
In case that size of mount point was greater than
size of defined arrays, rebuild failed.
Resolution:
Mount path is stripped off correctly.
Size of arrays that are used to store name of mount
point and additional information were increased.
26. Id = NSMbb37517
This behavior come from old versions because importp
or inventory hadn't been able to manage such a media.
It could happen that you had more than one record in
DB for one media, cause importp didn't find proper
record in DB, which was stored as ONSITE.
It just used new id. New version can manage this
problem quite well. Some forgotten-copied media in
box could still make problem, but in normal use is
all managed.
Resolution:
Add new global variable into
/etc/opt/omnistorage/jmcfg file to allow or not
allow delete guest media from DB while inventory.
The JMD_NO_DELETE_GUEST_MEDIA_ON_INVENTORY let it be
a variable name.
If is set to TRUE then inventory set guest media as
ONSITE instead of delete guest media from DB.
27. Id = HSLco21556
what(1) command output shows wrong information about
OmniStorage version
Resolution:
Source files were changed so that information about
OmniStorage version is correct.
28. Id = NSMex03564
message 'not fully implemented' was shown when we
start jmdrestore in case we have GRAU library
Resolution:
in case we have GRAU library and start jmdrestore,
only in case we set verbose mode,
message 'not fully implemented' should be shown
29. Id = NSMex03588
hsm_session -ka doesn't kill all mortal sessions.
Only mortal zombie sessions are killed with this
command.
Resolution:
Change man pages for hsm_session.
File hsm_session.8.mif has been changed.
PHSS_19038:
1. Id = NSMex02262
When starting up the ager in active as well as in
bulk mode dumps lots of "Logging started" /
"Logging stopped" messages into agerlog.
This is redundant and is caused by an incomplete
implementation to realize a MFS specific logging.
Resolution:
Remove redundant calls of the Logging() function
and introduce a separate config file -agercfg-
to be able to modify ager logging behavior
without modifying the qr logging facility.
2. Id = JOSqa00325
The man page of the resid command is
not understandable. The resid usage differs from
the resid man page and has to be conform.
Resolution:
The man page of resid has been changed by
removing the effects which led to misunderstanding.
At the beginning of section OPTIONS an explanation
concerning indications in SYNOPSIS has been added.
The USAGE of resid has been conformed to the
SYNOPSIS in the man page.
3. Id = JOSqa00324
The examples in the man page are still in the old
syntax of rebuild. Option -d is not implemented
any longer.
Resolution:
Man page of rebuild has been changed by removal
of option -d and the EXAMPLES have been corrected.
4. Id = NSMex02367
Performing a volumeset bulk aging or running
'migmv' correctly copies files from second to
third layer, but doesn't free space on second
layer. The created orphaned chunks on second
layer can only be removed with 'cleanp'.
Resolution:
Remove the orphaned chunks on second layer if a
multi level migration request finished
successfully and the extended attributes have
been attributes have been updated correctly.
5. Id = JOSqa00327
zls -l shows 0 blocks on secondary media for
chunks in bulk mode (migrated, not modified and
have a copy on magnetic).
These chunks don't have the DM_REGION_READ managed
region flag set, which causes extent_check_region()
function to return 0 as the number of blocks that
reside on secondary media.
Resolution:
Print the number of magnetic blocks as the number
of nearline blocks for chunks in bulk mode in the
zls -l output.
6. Id = NSMex02401
ERROR messages in consollog appear for each
deleted file on tape.
Resolution:
A source code change was done. A handle was freed
twice in this case.
The ERROR messages do not appear any more.
7. Id = JOSqa00328
When the outward migration had bumped at EOT-a
rest of a chunk resides on this tape. This leads
to an error.
Resolution:
Log a warning in this case and handle the
situation there are no more images to copy.
8. Id = NSMex02450, NSMex02335, NSMex02478, NSMex0243
While trying to free space on disk the ager
submits migout requests to the qr. If a request
references a chunk in bulk mode (migrated,
not dirty and has a copy on magnetic) and this
chunk resides on a full secondary media the qr
drops the migout request because it recognizes
that the corresponding secondary volume has no
free space for migration, but it doesn't
recognize that it only needs to erase the
magnetic copy of that chunk.
Resolution:
Let the bulk ager free the magnetic portion of
that chunk itself as implemented in the active
ager or the migout command.
This prevents network communication and improves
performance.
9. Id = NSMex02452
jmdrestore fails for mirror volumes which are
guests and have the same real Id as their
sources. The volume was opened by its real Id
until now.
Resolution:
jmdrestore opens mirror volumes by the id now.
10. Id = JOSqa00331
If media is set to ERROR state, no volume and
drive appears in the JMD_MEDIA_IN_ERROR and
MIGIN_NO_SUCH_PLATTER message
Resolution:
Place jmdmsg.Eng and qrmsgs.Eng into
/opt/omnistorage/lib/Eng
11. Id = NSMex02469
The jmd failed to decode a valid license string
for a system that has a '0' in its IP-address
due to a bug in the ovkey API.
Resolution:
Use latest ovkey API version which has the
corresponding fix in it.
12. Id = NSMex02508
Currently OmniStorage doesn't offer a tool that
can be used to determine which data images reside
on secondary storage by reading not extended
attribute information, but the metadata as
written to secondary media.
Resolution:
Support some kind of preview mode for the 'rebuild'
command, that only traverses the secondary media
and displays the found metadata information.
13. Id = JOSqa00332
While verifying customer qrlog file some of the
messages appeared incompletely, caused by
existing line feeds in the message text.
The used *.m to *.c/*.h compiler 'msgproc'
considers a line feed to be the end of a message
text. This leads to incomplete log message,
especially debug messages which makes it often
more difficult to determine the root cause of a
problem.
Resolution:
The qrmsgs.m and jmdmsg.m files were checked to
remove needless <CR>'s from the contents of the
$English parts responsible for the entries in
log messages.
14. Id = JOSqa00336
Stopping the jmd abnormally can leave the license
usage cash file '/var/opt/omnistorage/license.use'
on disk. This will cause the jmd to get confused
about available and used licenses which might
cause license requests to fail.
Resolution:
Remove the license usage cash file at jmd startup.
Correct its location to
/var/opt/omnistorage/data/jmd/license.use.
15. Id = NSMex02483
After consolidate the temporary files .omst**
created by pvlib were not deleted.
A customer had set the TMPDIR environment variable.
Resolution:
The c standard function tempnam was replaced by
tmpnam. The hpux manpage of tempnam is wrong.
The new consolidate works now.
PHSS_17476:
1. Id = NSMex02018
ager(1) and netcfg(4) man pages are inconsistent
regarding an explanation for the AGER_MAXSIZE
parameter.
Resolution:
update ager(1) man page
2. Id = NSMex02015, NSMex02016
o hsm_session output contains a message about a
non decodable session.
o the output is not aligned due to very long session
names
Resolution:
fix session name length
3. Id = NSMex02026
Running the ager in bulk mode causes the following
ERROR message in the agerlog file:
ager ERROR (26557): 01/28/1999 08:49:11
pvro_inlines.h(35) wrong process id for
session pid=67bd, created by 67bb
This ERROR message occurs by calling a pv* service
routine in an ager child process which doesn't have
the pv* services initialized.
Resolution:
Initialize pv* services in ager child process
4. Id = JOSqa00314
Make migration options
IOS_TAPE_MAX_FILES_PER_FILESET and
IOS_TAPE_MAX_DATA_PER_FILESET for better
performance configuration.
Resolution:
add comments to iocfg file
5. Id = JOSqa00313
The backup options IOS_BUFFER_SIZE and
IOS_WAIT_FOR_CLOSE need more description for better
performance configuration.
Resolution:
add comments to brapicfg file
6. Id = JOSqa00307, NSMex02253
The cause of the copyp failure is a "Large File"
problem. The system command "lseek" now using the
64 bit type of off_t for the offset value goes
wrong.
Resolution:
The solution is the right cast of the offset value.
The concerned function which uses the lseek system
call is retry_lseek().
7. Id = JOSqa00298
When migrating big files (>40% of disk cache) to
tape all but the first chunk would fail because
the jmd could not find space in the volume set
although there is enough space in the volume set.
Resolution:
The qr now calls MigOutReqVS() instead of
MigOutReq() which takes care of volumesets
bound to a certain MFS to correctly determine
available space for migration.
8. Id = JOSqa00309
Trying to migrate a chunk bigger than 2 GB to a MO
fails (the cache disk must be bigger than 5 GB for
that to occur).
Resolution:
Inserted new check for maximum possible chunk size
on nearline volume.
This restricts chunk size to 2GB-8k on MO hfs
formatted volumes.
9. Id = JOSqa00312
If a freepool is specified , but does not exist the
following mail appears:
Bad format detected for FREEPOOLVS_PROBLEM_MAIL.
Resolution:
Now the correct message [CHSM410514] appears in the
mail output.
10. Id = NSMex02038
When enabling migration with hsm_admin on an already
existing file system, the manual should document the
extra space used to do this, also that this can take
several hours on large file systems.
Resolution:
Additional entries into the concerning man page and
the Release Notes have been performed.
11. Id = JOSqa00308
After using of copyp, the listp command shows the
same size like before.
So the customer could assume the copyp command
didn't affect in any way. The right size for
mirror_volume will be shown after the first mount
of the mirror_volume.
The mirror_volume will be mounted during a full
inventory, or if the mirror_volume is replaced with
the source_volume.
Resolution:
An entry into the man page of copyp was made
accordingly.
12. Id = NSMbb21706
Every time the ager was started in active mode, but
aging was disabled, the qrlog was filled with
constantly repeated log messages like:
qr WARNING (26410): 01/12/1999 14:07:03
[CHSM410544]
The ager could not start in active mode for
FS_ID(0xc100) because aging is disabled in the
netcfg file. Please fix the netcfg file and restart
the ager.
Without (re)enabling aging this message occurred
every 30s which caused a space wasting log file.
Resolution:
Two flags, bAgerDisabledLogged and
bAgerEnabledLogged, were added to control the
logging to only write one log message for a
corresponding switch from disabled to enabled
or vice versa.
13. Id = NSMex01976
vsadm does not offer an option to print all
volumesets along with their members in one step.
Resolution:
A new option -L was added.
14. Id = NSMex02088, NSMex02177
Coredump of the jmd with STK9710 and BARCODE_NAMES
The STK9710 uses a different length for barcodes in
its SCSI-read-element-page.
Resolution:
STK9710 SCSI connection works now with barcodes.
15. Id = NSMex01992, NSMex01191
If a media was set to state 'Error' due to access
problems the corresponding ERROR log message only
shows the volume ID, but no drive number.
The drive number is helpful when searching the
root cause of the problem, i.e. is either the
media itself or the drive causing the problem
Resolution:
The drive number was added to the log message.
16. Id = NSMex01975
The ager running in active mode did not stop to
submit migout requests at the AGER_ALWM.
Additionally the agerlog showed an error
message like:
ager WARNING ( 2329): 01/08/1999 18:46:55
[CHSM310090]
The active mode ager was unable to move the file
system /test down to the ALWM (76%).
The current level is 5%.
This was caused by a wrong calculation due to
a data range overflow.
Resolution:
Use larger data types for calculation.
17. Id = NSMex01969
Defining TMPDIR env variable might cause the jmd
to fail when reading the volume set database at
startup. The jmd renames the original volsets
file into a temporary name.
The temporary file name is created using the
tempnam() HP-UX library routine.
Unlike tempnam(3S) man page this routine always
uses TMPDIR env variable if it's defined and has
a valid value. If the temporary name points to a
volume different from /var renaming the original
volsets file into a temporary name fails and all
volumeset information is missing.
Resolution:
The tmpnam() library routine is used instead.
18. Id = NSMex00837, NSMex00371, NSMex01141
o rebuild dumps core on 21st volume
o rebuild leaks memory
o rebuild output doesn't reflect progress
Resolution:
A progress indicator was implemented and memory
leaks removed.
19. Id = JOSqa00315
If you have a file migrated out on MO and you
change the file, you will get a partially
resident file. If now the volume is full and
you try to migrate out this file it will fail.
Resolution:
Now the request fails but is requeued to
another volume.
20. Id = NSMex02031
Ager -bulk should have a no timeout option of
zero the same as does the rebuild command.
Resolution:
Treat a given timeout of 0 as MAX_ALARM which
is at least 31 days.
21. Id = NSMex02099
While the ager was running in bulk mode it
didn't recognize the given timeout at the
correct time.
Resolution:
Implement timeout handling based on SIGALRM.
22. Id = JOSqa00320
The way the bulk mode ager filled a- and
b<fsid> lists didn't fulfill the requirement
of establishing lists containing migration
candidates to allow the active ager to fast
free space without walking the file tree to
determine migration candidates.
Resolution:
Redesign and implement a- and b<fsid> list
creation
23. Id = JOSqa00318
Permanent license will not be granted by the
jmd because it will not be checked if the
expiration date as encrypted in the license
key corresponds to the so called forever date.
Resolution:
Call OVLICisForever() to verify if a license
never expires by handling license requests.
24. Id = JOSqa00316
While migrating out files to sequential
(SIDF-) media (tape, WORM) the free space
would not be updated correctly.
When the end of tape is reached (either because
the free space was updated incorrectly or
because the tape had been formatted with a too
high capacity or both) the capacity of the tape
would be set to a wrong value and the tape might
even be set into error state.
Resolution:
The updating of used space was fixed and the
treatment of I/O-errors (especially EOT) was
changed completely.
Due to the asynchronous handling of write
requests the error condition 'end of tape' is
not always detected at the same spot, so the
finally detected size of a tape (after we hit
EOT) might differ from each other and also
from the capacity given by the manufacturer
(but this may also result from the really
different lengths of tapes).
25. Id = JOSqa00319
jmdrestore does not restore large number of
bytes for BlocksUsed and BlocksStale,
e.g. for DLT tapes 20GB
Resolution:
It now restores large numbers of bytes for
BlocksUsed and BlocksStale int64 data type
is used
26. Id = NSMex0219
During the inventory of a jukebox
"odetics_acl_452" the jmd dies.
Resolution:
The jmd now uses a more flexible method to
read the element status of library elements
(slots).
27. Id = NSMex02328
Abnormally stop a running 'sync_media',
e.g. by Ctrl-C, will leave platters in maintenance
and the original media keep flagged as being
sync'ed.
Resolution:
Improve sync_media's signal handling to ignore INT,
QUIT and TERM signals, but receipt the received
signal in an entry in synclog.
28. Id = JOSqa00322
Migrating a chunk which has all of its blocks on
nearline, but also some of its blocks modified on
magnetic causes the qr migout child process to
terminate abnormally with an assertion. This will
leave a kdm_user_thread process in memory.
The migout request will be requeued, but fails again
for the same reason, leaving a kdm_user_thread in
memory and so on until the system cannot fork
further processes.
The problem is caused by the wrong assumption that
and whole chunk will always be migrated. In fact the
reused space on nearline is smaller than the chunk
which leads to a wrong calculation of the real used
space on nearline before and after the migration.
Resolution:
Correct the number of bytes that will really be
reused on nearline.
29. Id = NSMex02349
When hitting end of media while migrating a file to
8x WORM media the media capacity as well as the free
space was wrongly calculated because the media
dependent sector size of 2048 bytes was not noticed.
This caused the qr parent to requeue the request
always to the same, already full media.
Resolution:
Use the media dependent sector size to calculate the
number of used media blocks when updating the jmd
database.
SR:
1653276659 1653276667 5003409540 1653299552 B554000693
H555003104 H555002918 B554000497 B554000387 H555003385
B555005764 B555005800 B555005755 B555005704 8606106767
B555005725 B555005649 B555005722 B555005758 B555005749
B555005829 H555003202 H555003108 B554000398 B554000604
B555005801 B555005748 B555005770 H555003366 H555003381
B555007915 B554000666 B554000717 H555003919 H555004409
H555005055 H555005024 H555005030 H555005379 H555005380
H555005380 H555005676 H555005774 B555008509 B555011027
H555005817 H555006318 H555006036 H555006049 H555006075
8606180777 1653294041 1653236059 1653224865 B555011105
H555006531 1653275834 H555006570 H555003786
Patch Files:
/etc/opt/omnistorage/brapicfg
/opt/omnistorage/bin/aliasp
/opt/omnistorage/bin/chgowner
/opt/omnistorage/bin/chgstate
/opt/omnistorage/bin/cleanp
/opt/omnistorage/bin/consolidate
/opt/omnistorage/bin/convert_media
/opt/omnistorage/bin/copyp
/opt/omnistorage/bin/exportp
/opt/omnistorage/bin/formatp
/opt/omnistorage/bin/fsckp
/opt/omnistorage/bin/getfsid
/opt/omnistorage/bin/importp
/opt/omnistorage/bin/inventory
/opt/omnistorage/bin/jmdbackup
/opt/omnistorage/bin/jmdrestore
/opt/omnistorage/bin/listp
/opt/omnistorage/bin/loadp
/opt/omnistorage/bin/mediaformat
/opt/omnistorage/bin/mediaset
/opt/omnistorage/bin/migin
/opt/omnistorage/bin/migmv
/opt/omnistorage/bin/migout
/opt/omnistorage/bin/migsever
/opt/omnistorage/bin/mountp
/opt/omnistorage/bin/omslic
/opt/omnistorage/bin/par
/opt/omnistorage/bin/qjmd
/opt/omnistorage/bin/qqr
/opt/omnistorage/bin/qrasyninf
/opt/omnistorage/bin/rebuild
/opt/omnistorage/bin/resid
/opt/omnistorage/bin/restore_file
/opt/omnistorage/bin/restore_vbfs
/opt/omnistorage/bin/rkill
/opt/omnistorage/bin/rmplat
/opt/omnistorage/bin/setgrp
/opt/omnistorage/bin/unaliasp
/opt/omnistorage/bin/unloadp
/opt/omnistorage/bin/unmountp
/opt/omnistorage/bin/vsadm
/opt/omnistorage/bin/vsbind
/opt/omnistorage/bin/vsdbcheck
/opt/omnistorage/bin/wt-check
/opt/omnistorage/bin/xhsm
/opt/omnistorage/bin/xhsmbackup
/opt/omnistorage/bin/xhsmmgr
/opt/omnistorage/bin/xhsmmonitor
/opt/omnistorage/bin/zb
/opt/omnistorage/bin/zdf
/opt/omnistorage/bin/zerrmsg
/opt/omnistorage/bin/zfind
/opt/omnistorage/bin/zls
/opt/omnistorage/bin/zmdump
/opt/omnistorage/bin/zmrestore
/opt/omnistorage/bin/zrm
/opt/omnistorage/bin/zshutdown
/opt/omnistorage/bin/zstartup
/opt/omnistorage/doc/AdminGuideA4.ps
/opt/omnistorage/doc/AdminGuideUS.ps
/opt/omnistorage/doc/ReleaseNotesA4.ps
/opt/omnistorage/doc/ReleaseNotesUS.ps
/opt/omnistorage/lbin/vsclose
/opt/omnistorage/lbin/vshdr
/opt/omnistorage/lbin/vsopen
/opt/omnistorage/lbin/vsread
/opt/omnistorage/lbin/vswrite
/opt/omnistorage/lib/Eng/agermsgs.Eng
/opt/omnistorage/lib/Eng/jmdmsg.Eng
/opt/omnistorage/lib/Eng/qrmsgs.Eng
/opt/omnistorage/lib/libcheyhsm.sl
/opt/omnistorage/lib/liblmgrau.sl
/opt/omnistorage/man/man1/ager.1
/opt/omnistorage/man/man1/listp.1
/opt/omnistorage/man/man1/mediaset.1
/opt/omnistorage/man/man1/qjmd.1
/opt/omnistorage/man/man1/qqr.1
/opt/omnistorage/man/man1/rebuild.1
/opt/omnistorage/man/man1/resid.1
/opt/omnistorage/man/man1m/add_vol.1m
/opt/omnistorage/man/man1m/consolidate.1m
/opt/omnistorage/man/man1m/copyp.1m
/opt/omnistorage/man/man1m/hsm_admin.1m
/opt/omnistorage/man/man1m/hsm_session.1m
/opt/omnistorage/man/man1m/mediaformat.1m
/opt/omnistorage/man/man1m/vsadm.1m
/opt/omnistorage/man/man4/VScfg.4
/opt/omnistorage/man/man4/agercfg.4
/opt/omnistorage/man/man4/agerconfig.4
/opt/omnistorage/man/man4/brapicfg.4
/opt/omnistorage/man/man4/consolcfg.4
/opt/omnistorage/man/man4/dedcfg.4
/opt/omnistorage/man/man4/iocfg.4
/opt/omnistorage/man/man4/jhosts.4
/opt/omnistorage/man/man4/jmcaps.4
/opt/omnistorage/man/man4/jmcfg.4
/opt/omnistorage/man/man4/logcfg.4
/opt/omnistorage/man/man4/massmediacfg.4
/opt/omnistorage/man/man4/netcfg.4
/opt/omnistorage/man/man4/synccfg.4
/opt/omnistorage/newconfig/agercfg.proto
/opt/omnistorage/newconfig/io_server.inetd
/opt/omnistorage/newconfig/iocfg.proto
/opt/omnistorage/newconfig/jmcaps.proto
/opt/omnistorage/newconfig/massmediacfg.proto
/opt/omnistorage/newconfig/rpc.kill.txt
/opt/omnistorage/newconfig/rpc.niod.txt
/opt/omnistorage/sbin/ager
/opt/omnistorage/sbin/installchanger
/opt/omnistorage/sbin/io_server
/opt/omnistorage/sbin/jconvert
/opt/omnistorage/sbin/jmd
/opt/omnistorage/sbin/qr
/opt/omnistorage/sbin/removechanger
/opt/omnistorage/sbin/rpc.kill
/opt/omnistorage/sbin/rpc.niod
/opt/omnistorage/sbin/sync_media
/sbin/ded
what(1) Output:
/etc/opt/omnistorage/brapicfg:
None
/opt/omnistorage/bin/aliasp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/chgowner:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/chgstate:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/cleanp:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/consolidate:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/convert_media:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/copyp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/exportp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/formatp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/fsckp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/getfsid:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/importp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/inventory:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/jmdbackup:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/jmdrestore:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/listp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/loadp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/mediaformat:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/mediaset:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/migin:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/migmv:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/migout:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/migsever:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/mountp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/omslic:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/par:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/qjmd:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/qqr:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/qrasyninf:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/rebuild:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/resid:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/restore_file:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/restore_vbfs:
None
/opt/omnistorage/bin/rkill:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/rmplat:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/setgrp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/unaliasp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/unloadp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/unmountp:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/vsadm:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/vsbind:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/vsdbcheck:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/wt-check:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/xhsm:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/xhsmbackup:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
OSF/Motif Version 1.2.5
/opt/omnistorage/bin/xhsmmgr:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
$Id: gui/lib/widgets/cheytreeelem.c/main/oms_2.2_d
ev_uid/1 97/08/12 14:57:38 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
OSF/Motif Version 1.2.5
/opt/omnistorage/bin/xhsmmonitor:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
OSF/Motif Version 1.2.5
/opt/omnistorage/bin/zb:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/zdf:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/zerrmsg:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/zfind:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
$Revision: 59.1 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/zls:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/bin/zmdump:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/zmrestore:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/bin/zrm:
None
/opt/omnistorage/bin/zshutdown:
$Id: etc/zshutdown.sh/main/oms_2.2_dev_uid/3 97/07
/01 14:12:14 $
$Release: OMS.02.20.00 $
/opt/omnistorage/bin/zstartup:
$Id: etc/zstartup.sh/main/oms_2.2_dev_uid/4 97/08/
12 17:20:10 $
$Release: zstartup.sh OMS.02.20.00 $
/opt/omnistorage/doc/AdminGuideA4.ps:
None
/opt/omnistorage/doc/AdminGuideUS.ps:
None
/opt/omnistorage/doc/ReleaseNotesA4.ps:
None
/opt/omnistorage/doc/ReleaseNotesUS.ps:
None
/opt/omnistorage/lbin/vsclose:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/lbin/vshdr:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/lbin/vsopen:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/lbin/vsread:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/lbin/vswrite:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/lib/Eng/agermsgs.Eng:
None
/opt/omnistorage/lib/Eng/jmdmsg.Eng:
None
/opt/omnistorage/lib/Eng/qrmsgs.Eng:
None
/opt/omnistorage/lib/libcheyhsm.sl:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
$Id: mm/lib/misc/portamap.c/main/oms_2.2_dev_uid/1
97/08/12 15:38:50 $
/opt/omnistorage/lib/liblmgrau.sl:
None
/opt/omnistorage/man/man1/ager.1:
None
/opt/omnistorage/man/man1/listp.1:
None
/opt/omnistorage/man/man1/mediaset.1:
None
/opt/omnistorage/man/man1/qjmd.1:
None
/opt/omnistorage/man/man1/qqr.1:
None
/opt/omnistorage/man/man1/rebuild.1:
None
/opt/omnistorage/man/man1/resid.1:
None
/opt/omnistorage/man/man1m/add_vol.1m:
None
/opt/omnistorage/man/man1m/consolidate.1m:
None
/opt/omnistorage/man/man1m/copyp.1m:
None
/opt/omnistorage/man/man1m/hsm_admin.1m:
None
/opt/omnistorage/man/man1m/hsm_session.1m:
None
/opt/omnistorage/man/man1m/mediaformat.1m:
None
/opt/omnistorage/man/man1m/vsadm.1m:
None
/opt/omnistorage/man/man4/VScfg.4:
None
/opt/omnistorage/man/man4/agercfg.4:
None
/opt/omnistorage/man/man4/agerconfig.4:
None
/opt/omnistorage/man/man4/brapicfg.4:
None
/opt/omnistorage/man/man4/consolcfg.4:
None
/opt/omnistorage/man/man4/dedcfg.4:
None
/opt/omnistorage/man/man4/iocfg.4:
None
/opt/omnistorage/man/man4/jhosts.4:
None
/opt/omnistorage/man/man4/jmcaps.4:
None
/opt/omnistorage/man/man4/jmcfg.4:
None
/opt/omnistorage/man/man4/logcfg.4:
None
/opt/omnistorage/man/man4/massmediacfg.4:
None
/opt/omnistorage/man/man4/netcfg.4:
None
/opt/omnistorage/man/man4/synccfg.4:
None
/opt/omnistorage/newconfig/agercfg.proto:
None
/opt/omnistorage/newconfig/io_server.inetd:
None
/opt/omnistorage/newconfig/iocfg.proto:
None
/opt/omnistorage/newconfig/jmcaps.proto:
$Release: jmcaps.proto OMS.02.11.00$
/opt/omnistorage/newconfig/massmediacfg.proto:
None
/opt/omnistorage/newconfig/rpc.kill.txt:
None
/opt/omnistorage/newconfig/rpc.niod.txt:
None
/opt/omnistorage/sbin/ager:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
$Id: mm/lib/misc/portamap.c/main/oms_2.2_dev_uid/1
97/08/12 15:38:50 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/sbin/installchanger:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/sbin/io_server:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/sbin/jconvert:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/sbin/jmd:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
$Release: lm_acs.c,v: OMS_Silo - OMS.02.11.03$
$Id: lm/lib/port/lm_acs.c/main/1 97/11/13 14:44:30
$
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_eject/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_lock_dr/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_query_ac/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_query_ca/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_query_dr/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_query_mo/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_query_vo/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_response/2.1.2 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_status/2.0A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_set_access/2.1.1 % %rel
ease: % %date_created: Mon Aug 1 10:03:45
1994 % (c) 1994 StorageTek
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsapi/csrc/acs_unlock_dr/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsutl/csrc/acs_get_resp/2.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: acsutl/csrc/acs_send_req/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: acsutl/csrc/acs_vary_res/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsutl/csrc/acs_query_res/2.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsutl/csrc/acs_resp_audf/2.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A %
%full_name: acsutl/csrc/acs_cvt_v2_v3/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A %
%full_name: acsutl/csrc/acs_cvt_v3_v4/2.01A %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 %
%full_name: acsutl/csrc/acs_cvt_v4_v3/2.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A %
%full_name: acsutl/csrc/acs_cvt_v3_v2/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acslm/cdk2.1 %
%full_name: acsapi/csrc/acs_get_pktver/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
acs_ipc_read.c 2.1.3 1/3/95 (c) 1994 STK
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsipc/csrc/acs_error/2.1 %
%full_name: acsipc/csrc/acs_ipc_write/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsipc/csrc/acs_sel_input/2.1 %
%full_name: acsipc/csrc/acs_verify_ssi/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
%full_name: acsipc/csrc/acs_get_sock/2.01A %
%full_name: h/incl/acsapi/2.1.1 %
%full_name: h/incl/apidef/2.1.2 %
%full_name: h/incl/apipro/2.1.1 %
%full_name: h/incl/acsapi_pvt/2.1.1 %
cl_ipc_read.c 5.5 2/7/94 (c) 1994 STK
cl_ipc_creat.c 1.1 1/10/94 (c) 1989-1994 STK
cl_ipc_write.c 1.1 1/10/94 (c) 1989-1994 STK
cl_defs.c 1.1 1/10/94 (c) 1989-1994 STK
ml_api.c 1.1 1/10/94 (c) 1989-1994 STK
cl_status.c 1.2 1/13/94 (c) 1994 StorageTek
cl_el_log_register.c 1.1 1/10/94 (c) 1989-1994 STK
cl_el_log.c 1.1 1/10/94 (c) 1989-1994 STK
cl_log.c 1.1 1/10/94 (c) 1993-1994 StorageTek
cl_trace.c 1.1 1/10/94 (c) 1989-1994 STK
cl_ipc_send.c 1.1 1/10/94 (c) 1989-1994 STK
cl_ipc_open.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_init.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_qcreat.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_qdelet.c 1.1 1/10/94 (c) 1989-1994 STK
dv_api.c 1.1 1/10/94 (c) 1989-1994 STK
cl_inform.c 1.1 1/10/94 (c) 1989-1994 STK
cl_chk_input.c 1.1 1/10/94 (c) 1989-1994 STK
cl_ipc_xmit.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_macces.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_mcreat.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_mdelet.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_mlocat.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_data.c 1.1 1/10/94 (c) 1989-1994 STK
cl_type.c 1.2 1/11/94 (c) 1994 StorageTek
cl_qm_create.c 1.1 1/10/94 (c) 1989-1994 STK
cl_qm_find.c 1.1 1/10/94 (c) 1989-1994 STK
cl_select_in.c 1.1 1/10/94 (c) 1989-1994 STK
/opt/omnistorage/sbin/qr:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/opt/omnistorage/sbin/removechanger:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/sbin/rpc.kill:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/sbin/rpc.niod:
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
/opt/omnistorage/sbin/sync_media:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
/sbin/ded:
HP92453-02A.10.00 HP-UX SYMBOLIC DEBUGGER (END.O) $R
evision: 74.03 $
HP aC++ B3910B A.01.21 Classic Iostream Library
HP aC++ B3910B A.01.21 Language Support Library
HP OmniStorage $Release: A.03.00.05 PHSS_25370 $
HP OmniStorage $Date: Mon Nov 26 10:19:38 MET 2001$
libovsnmp
PATCH-PHCO_17381 for 10.20; for 10.30, 11.x compatib
ility libc.a_ID/main/r10dav/libc_dav/15
/ux/core/libs/libc/archive_pa1/libc.a_ID
Mar 9 1999 13:52:37
cksum(1) Output:
1493699325 1038 /etc/opt/omnistorage/brapicfg
1996559264 144871 /opt/omnistorage/bin/aliasp
2573337300 144865 /opt/omnistorage/bin/chgowner
749937061 144867 /opt/omnistorage/bin/chgstate
3097789890 367963 /opt/omnistorage/bin/cleanp
3445573610 812338 /opt/omnistorage/bin/consolidate
2659278317 367697 /opt/omnistorage/bin/convert_media
2539581822 190299 /opt/omnistorage/bin/copyp
1024148804 144868 /opt/omnistorage/bin/exportp
699240596 148962 /opt/omnistorage/bin/formatp
2036513896 144868 /opt/omnistorage/bin/fsckp
3180240463 177617 /opt/omnistorage/bin/getfsid
3206272189 144868 /opt/omnistorage/bin/importp
3865542755 161397 /opt/omnistorage/bin/inventory
3701778853 252465 /opt/omnistorage/bin/jmdbackup
2066689320 248358 /opt/omnistorage/bin/jmdrestore
3483801913 161309 /opt/omnistorage/bin/listp
4121957556 144869 /opt/omnistorage/bin/loadp
1446251030 1203576 /opt/omnistorage/bin/mediaformat
641538223 1196880 /opt/omnistorage/bin/mediaset
899126693 243820 /opt/omnistorage/bin/migin
548422245 384483 /opt/omnistorage/bin/migmv
49295815 421746 /opt/omnistorage/bin/migout
2759691631 239737 /opt/omnistorage/bin/migsever
3142956232 144868 /opt/omnistorage/bin/mountp
1868264236 70069 /opt/omnistorage/bin/omslic
3644752865 190331 /opt/omnistorage/bin/par
436598252 169685 /opt/omnistorage/bin/qjmd
3813809537 157379 /opt/omnistorage/bin/qqr
500806525 53614 /opt/omnistorage/bin/qrasyninf
2380748409 895507 /opt/omnistorage/bin/rebuild
2397897361 185847 /opt/omnistorage/bin/resid
719120791 758462 /opt/omnistorage/bin/restore_file
2559345953 33551 /opt/omnistorage/bin/restore_vbfs
151383073 24698 /opt/omnistorage/bin/rkill
753874224 144867 /opt/omnistorage/bin/rmplat
1667854085 144867 /opt/omnistorage/bin/setgrp
92290456 144867 /opt/omnistorage/bin/unaliasp
4047329730 144881 /opt/omnistorage/bin/unloadp
3622356766 144868 /opt/omnistorage/bin/unmountp
1599831771 177737 /opt/omnistorage/bin/vsadm
1729699143 392683 /opt/omnistorage/bin/vsbind
2690047399 380382 /opt/omnistorage/bin/vsdbcheck
2006203733 190044 /opt/omnistorage/bin/wt-check
3787072647 512144 /opt/omnistorage/bin/xhsm
2452939025 2757540 /opt/omnistorage/bin/xhsmbackup
1298228017 3568909 /opt/omnistorage/bin/xhsmmgr
10208756 2547222 /opt/omnistorage/bin/xhsmmonitor
3584784565 911187 /opt/omnistorage/bin/zb
4236175 264622 /opt/omnistorage/bin/zdf
3642543899 24706 /opt/omnistorage/bin/zerrmsg
1365070809 446727 /opt/omnistorage/bin/zfind
2063331849 202410 /opt/omnistorage/bin/zls
3584784565 911187 /opt/omnistorage/bin/zmdump
3584784565 911187 /opt/omnistorage/bin/zmrestore
207355970 1941 /opt/omnistorage/bin/zrm
3083265485 7535 /opt/omnistorage/bin/zshutdown
1975454536 8159 /opt/omnistorage/bin/zstartup
4208646760 3009488 /opt/omnistorage/doc/AdminGuideA4.ps
2437582521 2965991 /opt/omnistorage/doc/AdminGuideUS.ps
2482106487 529351 /opt/omnistorage/doc/ReleaseNotesA4.ps
1951452555 513765 /opt/omnistorage/doc/ReleaseNotesUS.ps
60844062 215076 /opt/omnistorage/lbin/vsclose
233606869 215077 /opt/omnistorage/lbin/vshdr
2256190049 219176 /opt/omnistorage/lbin/vsopen
1169540482 215076 /opt/omnistorage/lbin/vsread
4239213917 215079 /opt/omnistorage/lbin/vswrite
1372942154 8673 /opt/omnistorage/lib/Eng/agermsgs.Eng
4208681737 37839 /opt/omnistorage/lib/Eng/jmdmsg.Eng
1662104295 75319 /opt/omnistorage/lib/Eng/qrmsgs.Eng
2869572798 1299860 /opt/omnistorage/lib/libcheyhsm.sl
1008775037 53426 /opt/omnistorage/lib/liblmgrau.sl
300348249 13128 /opt/omnistorage/man/man1/ager.1
968589587 9891 /opt/omnistorage/man/man1/listp.1
1035280907 6678 /opt/omnistorage/man/man1/mediaset.1
1999080253 3143 /opt/omnistorage/man/man1/qjmd.1
3752066247 4916 /opt/omnistorage/man/man1/qqr.1
1990998109 5659 /opt/omnistorage/man/man1/rebuild.1
78451485 9598 /opt/omnistorage/man/man1/resid.1
4133577231 5663 /opt/omnistorage/man/man1m/add_vol.1m
3817423328 3492 /opt/omnistorage/man/man1m/consolidate.1m
1603428761 4039 /opt/omnistorage/man/man1m/copyp.1m
2013184783 3900 /opt/omnistorage/man/man1m/hsm_admin.1m
1951007000 3072 /opt/omnistorage/man/man1m/hsm_session.1m
612297124 8021 /opt/omnistorage/man/man1m/mediaformat.1m
2306588393 6784 /opt/omnistorage/man/man1m/vsadm.1m
947712447 4678 /opt/omnistorage/man/man4/VScfg.4
2857300603 1149 /opt/omnistorage/man/man4/agercfg.4
2086203876 1122 /opt/omnistorage/man/man4/agerconfig.4
1085833323 1234 /opt/omnistorage/man/man4/brapicfg.4
3234179563 696 /opt/omnistorage/man/man4/consolcfg.4
4028711401 734 /opt/omnistorage/man/man4/dedcfg.4
613684390 1498 /opt/omnistorage/man/man4/iocfg.4
2851594121 2769 /opt/omnistorage/man/man4/jhosts.4
1810448857 11228 /opt/omnistorage/man/man4/jmcaps.4
1453484254 10985 /opt/omnistorage/man/man4/jmcfg.4
2311896509 4308 /opt/omnistorage/man/man4/logcfg.4
1314356960 747 /opt/omnistorage/man/man4/massmediacfg.4
268087052 15742 /opt/omnistorage/man/man4/netcfg.4
762911741 696 /opt/omnistorage/man/man4/synccfg.4
4022074553 159 /opt/omnistorage/newconfig/agercfg.proto
3408806248 130 /opt/omnistorage/newconfig/io_server.inetd
3720023498 1611 /opt/omnistorage/newconfig/iocfg.proto
3641731285 6114 /opt/omnistorage/newconfig/jmcaps.proto
1072766274 87 /opt/omnistorage/newconfig/massmediacfg.proto
3222915936 241 /opt/omnistorage/newconfig/rpc.kill.txt
4029151925 160 /opt/omnistorage/newconfig/rpc.niod.txt
513677691 731684 /opt/omnistorage/sbin/ager
1976167585 82588 /opt/omnistorage/sbin/installchanger
1973012353 1115024 /opt/omnistorage/sbin/io_server
1578402355 73961 /opt/omnistorage/sbin/jconvert
832130013 1466470 /opt/omnistorage/sbin/jmd
3586308728 1377517 /opt/omnistorage/sbin/qr
1863675411 115884 /opt/omnistorage/sbin/removechanger
3801279852 24691 /opt/omnistorage/sbin/rpc.kill
3371942816 57833 /opt/omnistorage/sbin/rpc.niod
1647132413 754652 /opt/omnistorage/sbin/sync_media
3620220128 976776 /sbin/ded
Patch Conflicts: None
Patch Dependencies:
s700: 10.20: PHKL_20096
s800: 10.20: PHKL_20097
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_17476 PHSS_19038 PHSS_21065 PHSS_22743
Equivalent Patches: None
Patch Package Size: 39190 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_25370
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHSS_25370.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHSS_25370. 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_25370.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_25370.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch includes the following Site Specific Patches:
SSPOMS_29
SSPOMS_30
SSPOMS_32
SSPOMS_33
SSPOMS_34
SSPOMS_36
SSPOMS_37
SSPOMS_38
SSPOMS_39
SSPOMS_40
SSPOMS_41
SSPOMS_42
SSPOMS_43
SSPOMS_44
SSPOMS_45
SSPOMS_46
SSPOMS_47
SSPOMS_48
SSPOMS_49
SSPOMS_50
SSPOMS_51
SSPOMS_52
SSPOMS_53
SSPOMS_54
SSPOMS_55
This patch updates /etc/opt/omnistorage/iocfg and
/etc/opt/omnistorage/jmcaps. This might fail due to
merge conflicts. Please scan the log file
/var/adm/sw/swagent.log for corresponding WARNING
messages and follow the listed instructions.
Installation Instructions:
1> Become root user
2> Stop OmniStorage application with 'zshutdown(1M)'
OmniStorage command
3> Install this patch following the above outlined
Installation Instructions using 'swinstall(1M)'
4> Start OmniStorage application with 'zstartup(1M)'
OmniStorage command
Use 'zstartup -m all' to also mount of all MFS's
NOTE: To successfully kill the 'rpc.kill' processes
from the command line, you should first kill the
'inet daemon' with the 'inetd -k' command.
-----End of Document ID: PHSS_25370------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]