|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
HP-UX series 700 11.X patch digest
From: IT Resource Center (support_feedback
us-support2-mail.external.hp.com)
Date: Mon Apr 07 2003 - 04:32:26 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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://support.itrc.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://support.itrc.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 700 11.X patch digest
Created: Sun Apr 6 6:05:53 EDT 2003
Table of Contents:
Document ID Title
--------------- -----------
PHSS_28933 s700_800 11.X OV ITO7.1X JavaGUI client A.07.13
PHSS_28728 s700_800 11.X OV OB3.50 patch - CS packet
PHSS_28726 s700_800 11.X OV OB3.50 patch - CC packet
PHSS_28724 s700_800 11.X OV OB4.10 patch - SAP packet
PHSS_28579 s700_800 11.X OV OB3.50 patch - SSEA packet
PHNE_28882 s700_800 11.04 (VVOS) ONC/NFS General Release/Perf Patch
PHSS_26651 s700_800 11.22 Graphics3D cumulative patch
PHSS_28571 s700_800 11.X OV OB3.50 patch - CORE packet
PHSS_28330 s700_800 11.X OV DP5.00 patch - SSEA packet
PHKL_28766 s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,PDC,CLK
PHKL_28765 s700_800 11.11 VM panic with shared libs and large pages
PHCO_28124 s700_800 11.22 cumulative SAM patch
PHSS_28912 s700_800 11.X OV SIP3.0 Allow GET method in form
PHSS_28891 s700_800 11.X OV SIP3.1 OVIS gauges do not show up
PHSS_28706 s700_800 11.X ANSI C compiler B.11.11.06 cumulative patch
PHSS_28594 s700_800 11.X +O4/PBO Compiler B.11.11.06 cumulative patch
PHCO_28425 s700_800 11.00 libc cumulative patch
PHCO_28009 s700_800 11.00 bdiff(1) patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_28933
Date Loaded: 20030404
Title: s700_800 11.X OV ITO7.1X JavaGUI client A.07.13
Patch Name: PHSS_28933
Patch Description: s700_800 11.X OV ITO7.1X JavaGUI client A.07.13
Creation Date: 03/04/01
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Operations 7.1
Filesets:
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28933
Symptoms:
PHSS_28933:
- SR: 8606301629
The bundled JRE 1.4.1 for Windows does not support an
input locale other than english.
PHSS_28201:
- SR: 8606297429
The JavaGUI does not support the JRE 1.4.1 version.
- SR: B555014127
Even if applications and/or nodes are already selected
while an application wizard is started, the related
selection steps are offered again so that you have to
press "Next" some times.
- SR: 8606270802
When opening the annotations for a message in the Java
GUI, the first (oldest) annotation is opened instead of
the latest one, which is usually of more interest.
- SR: B555015121
The JavaGUI may show the message property information
with a black background because it uses the wrong
color resource.
- SR: 8606291636
Big pulldown menues are running off the screen so you
can not access all their entries.
- SR: B555015323
The JavaGUI should be able to load services on demand
in order to handle large service trees in a reasonable
time.
- SR: B555014780
If you select a saved filter in the JavaGUI you still
have to press OK to make it active. It should be possible
to just doubleclick on the filter to make it active.
- SR: B555015192
The toolbar icons to expand and collapse service trees
have misleading '+' and '-' signs in them.
PHSS_27914:
- SR: B555014709
The JavaGUI installation package for UNIX
(ito_op_install.tar) is packaged with the absolute path
prefix /opt/OV/www/htdocs/ito_op so that you can not
install different versions in parallel.
- SR: R555003344
The JavaGUI does not resolve $OPC_ENV(..) variables
in application calls.
- SR: B555014590
The JavaGUI applet download page forces you to use a
java plugin version 1.3.1.0 for Internet Explorer,
even if all 1.3 versions are supported.
- SR: H553001650
Service status propagation does not work any more after
"Log Off" and login again.
- SR: B555013246
Clicking in a browser in the result pane does not select
a message, it only activates the browser.
In the workspaces, a click both activates the browser
and selects the message you have clicked on.
- SR: B555014176
The JavaGUI freezes if the network is down. You'll get
an hourglass cursor and can't do anything any more,
even File->Exit can not be called before the network
is up again.
- SR: B555012633
The JavaGUI does not replace the $OPC_SERVICE_VALUE[]
variable in customized applications started from a
service submap popup menu.
- SR: B555014663
The JavaGUI download page on the server does not show
the version of the JavaGUI download package.
This is inconvenient, especially if the server has been
patches to a higher version and you do not know whether
the JavaGUI client has been patched as well or is still
the same as from a previous patch.
- SR: B555012609
In some environments the text fields in the JavaGUI
message properties window are all black due to a wrong
background color selection.
- SR: B555014658
If you start an application in the JavaGUI by selecting
a message and then double-click one application, the
$OPC_MSG_NODES variable is not passed to the application.
- SR: B555014707
The JavaGUI error window has no username and servername
in its title, so if you run more than one JavaGUI on the
same system, you don't know which JavaGUI is related to
which error window.
- SR: B555014587
The annotation box in the JavaGUI does no word wrapping.
- SR: 8606256435
The month value in the JavaGUI Filter Summary window
show a wrong value: one too low.
Defect Description:
PHSS_28933:
- SR: 8606301629
The bundled JRE 1.4.1 was the english version
and not the international version.
This patch replaces just the JRE inside the InstallShield
package, so the JavaGUI client version stays A.07.12.
PHSS_28201:
- SR: 8606297429
With the A.07.12 JavaGUI patch version the Service Load
on Demand feature has been merged from the next major
release into the OVO 7.1X code. This feature requires
a JRE version of at least 1.4 so all necessary adaptions
have been made to the code.
- SR: B555014127
If applications and/or nodes are already selected while
an application wizard is started, the related selection
steps are now bypassed to make the startup easier.
You can still use "Back" to change the previously
selected values.
- SR: B555015121
Even after the fix for NSMbb43705 we still didn't use
the proper color resource for the background of the
message property information. We used the font color of
"Selected Items" (ControlPanel->Display->Appearance)
instead of the usual "Window" background color.
- SR: B555015323
The 'Service Load on Demand' feature was merged back
from the code implemented for the next major OVO release.
You can only use this while connected to a server which
has this feature, otherwise the
Edit->Preferences->Services tab will be greyed out.
- SR: B555015192
The toolbar icons to expand and collapse service trees
have misleading '+' and '-' signs in them.
The '+' has to be moved to the expand icon and the '-'
has to be moved to the collapse icon.
PHSS_27914:
- SR: R555003344
The variable resolving was missing in the JavaGUI client.
- SR: H553001650
Service status propagation does not work any more after
"Log Off" and login again because the "Log Off" does no
full shutdown of the client. As a workaround you had to
use "Exit" or run a "Reload Configuration" after the
login.
- SR: B555014176
As soon as it tries to reconnect, the main thread
blocks and the reconnection loops (until the network
is up again). The reconnection has to be handled
in a separate thread.
- SR: B555012609
The background was set to System.inactiveCaptionText
instead of System.textHighlightText
- SR: B555014658
Launching URL shortcuts or application in the object pane
(tree) with a doubleclick did not take a previously
selected message as a parameter.
This application launch method has been removed from the
A.07.10 release to make the selection model consistent
(only active selections should be taken as an argument,
so you would have to press CTRL before doubleclicking
to keep the message selection active) however there are
customers who would like to keep this inconsistent but
nice feature.
Enhancement:
No (superseded patches contained enhancements)
PHSS_28201:
This patch enables the 'Service Load on Demand' feature
on the JavaGUI client. In order to use this feature you
need an OVO server which has this feature implemented
(i.e. you need an OVO server patch A.07.13 or above).
SR:
R555003344 H553001650 H553001582 B555015323 B555015192
B555015121 B555014780 B555014709 B555014707 B555014663
B555014658 B555014590 B555014587 B555014176 B555014127
B555013246 B555012633 B555012609 8606301629 8606297429
8606291636 8606270802 8606256435
Patch Files:
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ITO_JAVA.exe
/opt/OV/www/htdocs/ito_op/ito_op.jar
/opt/OV/www/htdocs/ito_op/ito_op_addon.jar
/opt/OV/www/htdocs/ito_op/ito_op_install.tar
/opt/OV/www/htdocs/ito_op/ito_op
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html.ja
/opt/OV/www/htdocs/ito_op/contents.htm.ja
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html.es
/opt/OV/www/htdocs/ito_op/contents.htm.es
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.11_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html
/opt/OV/www/htdocs/ito_op/contents.htm
/opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_Preferences_Dialog_Box.htm
/opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_itooprc_Resource_File.htm
what(1) Output:
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ITO_JAVA.exe:
None
/opt/OV/www/htdocs/ito_op/ito_op.jar:
None
/opt/OV/www/htdocs/ito_op/ito_op_addon.jar:
None
/opt/OV/www/htdocs/ito_op/ito_op_install.tar:
None
/opt/OV/www/htdocs/ito_op/ito_op:
None
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html.ja:
None
/opt/OV/www/htdocs/ito_op/contents.htm.ja:
None
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html.es:
None
/opt/OV/www/htdocs/ito_op/contents.htm.es:
None
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ito_for_activator.html:
None
/opt/OV/www/htdocs/ito_op/contents.htm:
None
/opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_Preferences_Dialog_Box.htm:
None
/opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_itooprc_Resource_File.htm:
None
cksum(1) Output:
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
1061594698 21070940 /opt/OV/www/htdocs/ito_op/ITO_JAVA.exe
515357654 2010068 /opt/OV/www/htdocs/ito_op/ito_op.jar
3749842889 3033161 /opt/OV/www/htdocs/ito_op/
ito_op_addon.jar
1427138091 5109760 /opt/OV/www/htdocs/ito_op/
ito_op_install.tar
1864280885 5455 /opt/OV/www/htdocs/ito_op/ito_op
OVOPC-WWW.OVOPC-WWW-JPN,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
2097469399 3448 /opt/OV/www/htdocs/ito_op/
ito_for_activator.html.ja
3945557710 6486 /opt/OV/www/htdocs/ito_op/contents.htm.ja
OVOPC-WWW.OVOPC-WWW-SPA,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
1746972643 3435 /opt/OV/www/htdocs/ito_op/
ito_for_activator.html.es
3184554300 9185 /opt/OV/www/htdocs/ito_op/contents.htm.es
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.07.10,fa=HP-UX_B.11.00_32/64,
v=HP:
2108598396 3380 /opt/OV/www/htdocs/ito_op/
ito_for_activator.html
801129690 9014 /opt/OV/www/htdocs/ito_op/contents.htm
2463250795 12791 /opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_Preferences_Dialog_Box.htm
1231954507 28288 /opt/OV/www/htdocs/ito_op/help/en/ovo/html/
re_About_the_itooprc_Resource_File.htm
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_28201 PHSS_27914
Equivalent Patches: None
Patch Package Size: 30620 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_28933
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28933.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28933. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28933.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28933.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28933.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch introduces the 'Service Load on Demand' feature
on the JavaGUI client. In order to use this feature you
need an OVO server which has this feature implemented
(i.e. you need an OVO server patch A.07.13 or above).
This will give you an additional tab "Services" in
the Edit->Preferences menu. See the online help for
details.
This JavaGUI client requires a JRE 1.4 or above.
For Windows it is packaged into the InstallShield package
but for UNIX you have to install it on your own.
In order to retain your UNIX client on the management
server working, the unpacked ito_op.jar file will not be
patched to A.07.12 but keep the A.07.11 patchlevel.
To get the features and fixes from the A.07.12 patch
level, install a JRE 1.4 or above (1.4.1 is recommended)
and unpack the ito_op_install.tar file as described in
the JavaGUI download page on your OVO management server.
-----End of Document ID: PHSS_28933------------------------------------------
Document ID: PHSS_28728
Date Loaded: 20030404
Title: s700_800 11.X OV OB3.50 patch - CS packet
Patch Name: PHSS_28728
Patch Description: s700_800 11.X OV OB3.50 patch - CS packet
Creation Date: 03/03/27
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.03.50
Filesets:
OMNIBACK-II.OMNI-CS,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28728
Symptoms:
PHSS_28728:
Id = HSLco39169 SR:H555009297
After aborting host backup the object post exec script
does not execute.
Id = HSLco39878 SR:H555009560
Backup run twice when daylight saving time is changed.
Id = HSLco40494 SR:H555009843
While backup with reconnect option is in progress and
BSM loses connection to monitor the message appears:
"[Warning] From: BSM<host> "<device>" Time: <time>
[61:2013] Some of the backup devices are occupied.
Session is waiting for all the devices to get free.
[Major] From: BSM<host> "<device>" Time: <time>
[61:3003] Lost connection to Monitor named "noname"
on host <host>.
Ipc subsystem reports: "IPC Read Error
System error: [232] Connection reset by peer"
Id = HSLco40537 SR:H555009863
When backing up very large SAP databases with SSEA
split mirror, backups can fail with error:
"BR280I Time stamp <time>
BR296I Split of mirror disks successful
BR274E File /<sapdata_path>/system.data1 not found"
PHSS_28022:
Id = HSLco35783 SR: H555008533
Informix backup hangs if a resource type is backed up
to a different device than the other resource types.
Id = HSLco36721 SR: H555008690
If a Manager-of-Managers Server is also a
MC/ServiceGuard virtual node, then the command:
"omnirpt -report list_sessions -timeframe
<start_hours_ago><hours_duration>
-multicell -no_multiple"
lists the matching sessions from this node twice.
Id = HSLco37099 SR: H555008780
Queries from client Cell Server in MoM environment
with CMMDB fail with:
"[12:1012] Cannot access the file."
Id = HSLco37193 SR: H555008807
When backing up SAP integration with EMC split mirror
functionality, not all the SAP files are backed up.
Id = HSLco37276 SR: H555008832
OmniBack internal database backup fails with an error:
"[Major] From: BSM<computer> "<object>" Time: <time>
[61:3003] Lost connection to VBDA named <object>
on host <host>.
Ipc subsystem reports: "IPC Read Error
System error: [232] Connection reset by peer"
Id = HSLco37939 SR: H555008927
While configuring OmniBack II reports using GUI, only
datalists are listed (barlists are missing).
Id = HSLco37723 SR: H555008892
When performing omnimlist -catalog on media, the
program exits and debug.log contains this
Interprocess Communication error:
08/06/02 11:13:15 OMNIMLIST.1224.0
["/src/lib/ipc/ipc.c /main/r31_split/16":3434]
A.03.50 b216
[ipc_receiveDataEx] buffer 102400 bytes to
small to receive data 258487 bytes => ignored
PHSS_26890:
Id = HSLco35076 SR: H555008261
Backup fails with an error:
"Internal error. Allocation from library failed.
The Media Management daemon reports:
Internal error: DbaXXXX functions."
Id = HSLco35364 SR: H555008410
The earlier Patch PHSS_26348 introduced behavior
that can cause database integration
(for example Oracle or SAP) backups to fail.
With PHSS_26348 installed, OmniBack does not properly
lock the logical devices to prevent concurrent access
by multiple sessions. As a result, database integration
backups may fail instead of waiting for the device
to become free.
Id = HSLco35515 SR: H555008452
Backup Session Manager does not terminate after
the time specified in the SmDaIdleTimeout variable
when connection to Disk Agent and Media Agent is lost.
Id = JAGae27169 SR: 8606262839
Configuration report shows an incorrect list of
scheduled backups.
PHSS_26348:
Id = HSLco20414 SR: H555003134
Device maintenance from command line is not sufficient.
Id = HSLco31865 SR: H555006924
The message for the mount request is not in proper
format when forwarded to ITO.
Id = HSLco32789 SR: H555007191
If pre-exec script does not complete in
ScriptOutputTimeout time (default 15 minutes), Backup
Session Manager lopps and can not be aborted.
Id = JAGad90905 SR: 8606221771
Case sensitive search does not work.
Id = JAGae05208 SR: 8606236143
Not all session manager processes are correctly stopped
using csailover.ksh script.
Id = HSLco33360 SR: H555007428
Backup fails with error:
"[Major] From: BMA<HOST> Time:<TIME>
[90:64] Can not unload exchanger medium
(Storage slot is occupied.)".
Id = JAGae14881 SR: 8606248483
Address of a Cell Console client is incorrectly
handled.
Id = HSLco34255 SR: H555007796
omnirpt failes after the installation of
PHSS_25002/25003.
PHSS_25003:
Id = HSLco24755 SR: B555011718
OmniBack II issues a mount request for tape during
the restore session.
Id = HSLco28232 SR: H555005922
Backup is waiting for all pre/post-exec scripts to
finish before proceeding.
Id = HSLco28279 SR: H555005975
Purge of filenames aborts daily.
Id = HSLco29098 SR: H555006248
Restore session fails with error:
"Can not load exchanger medium.".
Id = HSLco30814 SR: H555006710
Session ends as 'Failed' because OmniBack II tries
to back up non existent SAP redo logs.
Id = HSLco31142 SR: H555006771
Load balancing is not working properly.
Id = HSLco31295 SR: H555006799
OmniBack reports that medium copy session finished
successfully although it failed.
Id = HSLco31325 SR: H555006810
When OmniBack II Integration backup is aborted,
another complete sesson starts and finishes backup of
remaining database objects.
Id = JAGad86475 SR: 8606217323
Cell Request Server and session managers frequently
abort.
PHSS_24659:
Id = JAGad48558
OmniBack II creates duplicated tape labels.
Id = JAGad64442
OmniBack II internal database owner is not
properly set after configuring OmniBack II in
MC/ServiceGuard environment.
Id = NSMex03907
Browsing of a filesystem in Restore GUI sometimes
fails with an error:
"Cannot browse from root. Please specify
starting point.".
Id = NSMex04086
Session status is "Completed/Failures" although there
is no indication of errors.
Id = NSMex04149
If Cell Request Service (CRS) is restarted in cluster
aware mode, error:
"-2 starting omnidbutil -clear!"
occurs in cluster.log file.
Id = NSMex04164
Omnitrig fails with an error:
"Error parsing schedule purge_schedule.".
Id = NSMex04283
Adding OmniBack II licenses in MC/ServiceGuard
environment fails with an error:
"Cell Server host IP is not in IP range.".
Id = NSMex04287
Load balancing uses less devices than expected.
Id = NSMex04319
OmniBack II issues mount request, but it can not be
confirmed because the tape drive is busy.
Id = NSMex04311
Post-exec script specified for a virtual hostname does
not start if pre-exec script fails.
Id = NSMex04403
Tape import is reported successful although it is not.
Id = NSMex04540
Restore session fails with error:
"Can not load exchanger medium.".
PHSS_23471:
Id = JAGad36093
Session status indicates "Completed" although one of the
agents failed.
Id = NSMbb37729
Devbra reports:
"[90:11] Unrecognized option "/" => ignored".
Id = NSMex03425
Backup of SAP archive logs fails with:
"[Major] From: OB2BAR<hostname> <ORASID> Time:<time>
Can not read BSM message (IPC Read Error
System error: [232] Connection reset by peer.)".
Id = NSMex03621
Restore does not work correctly after the mount
request confirmation.
Id = NSMex03701
OmniBack Session Report contains many
"[Warning] From: BSM<hostname> <DBNAME> Time:<time>
Received connect from BAR Backup DA on host <host>
that is not specified in CLIENT statement in the
barlist."
warning messages.
Id = NSMex03711
Error:
"Hostname is not in IP range."
is reported after service guard fails over to a
secondary host.
Id = NSMex03739
Pre- and post-exec scripts return invalid exit status.
Id = NSMex03847
After upgrade to OmniBack II 3.50, backup to STK 9840
device fails with an error:
"Invalid physical device type => aborting."
Id = NSMex03894
Host backup fails if host has more than 600
mountpoints.
Id = NSMex03910
If Sybase backup fails before OB2BAR is started,
a Major message is reported in the session output,
but session status is "Completed".
Id = NSMex03917
Objects are lost from OmniBack II internal database
after the execution of "omnidbutil -cdbsync" command.
Id = NSMex03991
Full Oracle backup can be appended to a medium in a
pool with "append incremental only" property.
Id = NSMbb38972
MS Exchange 2000 scheduled backups do not start.
Id = NSMex03246
Backup Session Manager is sending wrong SNMP messages to
ITO Management server.
Id = NSMex04159
When restarting failed sessions multiple sessions are
created.
Id = NSMex04261
Import of session fails.
PHSS_23106:
Id = NSMex03757
Bad backup performance after upgrade from OmniBack II
2.55 or 3.00.
Id = NSMex03977
Execution of command
"omnirpt -report used_media -timeframe <t1> <t2>"
results in the following error message:
"DB[4] internal error [-16] record not connected
to set".
"DB[4] internal error [-16] record not connected
to set".
PHSS_22370:
Id = JAGad13634
Informix barlists are not converted into a OmniBack II
3.50 format after an upgrade from OmniBack II 2.55.
Id = JAGad17029
"List from media" ignores "See private objects" option.
Id = NSMex03356
Permanent license shows up as out of IP range.
Id = NSMex03365
Backup session is not logged in the database if file
pattern search is performed in parallel.
Id = NSMex03419
After importing a tape from 2.55 to 3.x cell some of
the files can not be restored.
Id = NSMex03466
After the upgrade from OmniBack II 3.00 to 3.50, a
warning
"Received connect from BAR backup DA on host
<hostname> that is not specified in CLIENT statement
in barlist."
appears on a client with multiple lan cards.
Id = NSMex03481
A backup of MC/SG can not be aborted after the switch.
Id = NSMex03491, JAGad28516
Directories are backed up even if excluded in host
backup.
Id = NSMex03493
Omnitrig does not pass debugging parameters to omnirpt.
Id = NSMex03583, NSMex03631
OmniBack II ignores the tape loaded after the mount
request for SCSI-II changer device.
Id = NSMex03638 SR: B554000768
Option "-change_objname" does not work properly.
Id = NSMex03501
List of media fails with an error:
"Medium details not available.
Medium owned by Cell Manager: <hostname>."
Id = NSMex03683
Copy session of write-protected tape is aborted and
cleaning tape is requested in the source tape drive.
Id = NSMex02584
Internal database server (RDS) abnormally ends due to
lack of memory.
Id = NSMex03702
Internal database server (RDS) abnormally ends during
a SAP restore.
Id = NSMex03289
Sessions are disappearing from OmniBack II database.
Id = NSMex03521
OmniBack II database gets corrupted.
Id = NSMex03737
Sessions are disappearing from OmniBack II database.
Id = NSMex03758, NSMex03759, NSMex03646
Execution of commands "omnidb -session <sess_id>" and
"omnirpt -report used_media -timeframe <n> <n>"
reports that the database is corrupt, but omnidbcheck
reports no problem.
Defect Description:
PHSS_28728:
Id = HSLco39169 SR:H555009297
Before executing the object post-exec script,
OmniBack II checks if session is aborting.
If it is, then script does not execute.
Resolution:
Global variable PostExecOnAbortHostBackup was added.
If this global variable is set to 1, the post-exec
script will execute even if the session is aborting.
Id = HSLco39878 SR:H555009560
The algorithm, that handles the daylight saving time
changes is incomplete.
Resolution:
The algorithm is changed for both time changes:
02h->03h and 03h->02h.
Id = HSLco40494 SR:H555009843
If BSM loses connection to monitor message appears.
The problem (reconnect) should only be reported
for agents (DA, MA...).
Resolution:
The function is modified to check if the connection
with the agent (DA, MA ...) is broken. If BSM loses
connection to monitor, no messages are displayed.
Part of SSPUX350_089.
Id = HSLco40537 SR:H555009863
In split mirror environment with very large SAP
databases, it can happen that the size of the message
buffer that OmniBack II uses is too small to fit in
for the complete list of SAP files to be backed up.
Resolution:
New environment variable is introduced: OB2IPCBUFSIZE.
In order to solve this problem, the buffer size can
be increased by setting the OB2IPCBUFSIZE environment
variable in the .omnirc file on CM, R1 and R2 hosts,
specifying the desired amount of memory to be used
for the buffer.
For determining buffer size please see the Resolution
of Id = HSLco37193 below.
Part of SSPUX350_088.
PHSS_28022:
Id = HSLco35783
With Informix integration backup, it is possible to
specify which resource type will be backed up by which
device. If most of the resource types are backed up to
n devices, but the L (Log) resource type is backed up
to a separate, additional device, and load balancing
is set to (max=n, min=n), then the session will hang
because it tries to lock n+1 devices for all the
resource type backups.
Resolution:
OmniBack now unlocks devices, if they were not used for
any backup for a certain amount of time. It also stops
media agents that have not had any backup agents
assigned to them for the timeout period. With both
changes (unlock device, stop media agent), it can start
new media agents, required by specific resource type
backup agents that have already contacted Backup Session
Manager.
Important note:
---------------
In order to get the session running, there are some
timeout parameters (global options) that have to be
properly set :
Global options
--------------
A - BackupDeviceIdle
B - SmPeerID
C - SmDaIdleTimeOut
D - SmMaIdleTimeOut
Conditions that have to be satisfied :
-----------
A<B
C<D
Example:
Default Suggested
value value
-----------------------------------
A 10min 4min
B 5min 5min
C 120min 120min
D 140min 140min
Explanation:
------------
[A<B]
After all BAR clients stop sending data to a device,
the BSM waits for either A or B timeout to happen for
the device. If the timeout A is reached, the backup
device will be stopped gracefully, if B timeout is
reached, it will be aborted. That's why it is important
that the condition A<B is fulfilled.
[C<D]
This is a general condition that must be met for all MA
and DA processes, and is stated in the global options
file.
It is important to keep the option BackupDeviceIdle
under 300 seconds (5 minutes). If 300 or higher, the
session behavior will be unpredictable (errors are
likely to appear).
Part of SSPUX350_087.
Id = HSLco36721
When running "omnirpt" command all the cell servers from
the "mom_info" and the local Cell Server are queried for
matching sessions. The virtual node and the local host
are actually the same machine, so the matching sessions
are listed twice.
Resolution:
The function gethostname() is not used any more to
determine if the inspected host is also the local host,
because in case of a Manager-of-Managers/ServiceGuard
environment it returns the physical node hostname and
not the virtual node hostname, making the virtual
hostname being seen as a non-local host. In this way
the virtual hostname is not queried for matching
sessions any more.
Id = HSLco37099
Format of messages is changed from buffer to pointer
but change is not implemented in all areas. Database
Session Manager gets message from MoM server in
improper format and closes the connection.
Resolution:
Size of message is dynamically changed, messages are
not send in fixed size anymore.
Id = HSLco37193
In split mirror environment with huge SAP databases
it can happen that the size of the message buffer
OmniBack II uses is too small to receive complete list
of SAP files to be backed up.
Resolution:
Setting the OB2IPCBUFSIZE environment variable in the
/opt/omni/.omnirc file on Cell Server, R1 and R2 hosts,
specifying the desired amount of memory to be used for
the buffer solves the described problem.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/[c0t1d1,lvol1])
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Known problems:
---------------
If the calculated variable OB2IPCBUFSIZE is correctly
set, but is still too small for the file list to fit
into the message buffer, the session will fail with
the following error seen in the report:
BR295I Splitting mirror disks...
BR280I Time stamp <time>
BR279E Return code from '/opt/omni/lbin/ob2smbsplit
/<sap_homedir_path>/.<filename>.lst': 2
BR299E Split/resynchronization of mirror disks failed
In this case the variable OB2IPCBUFSIZE must be
recalculated to appropriate value. See above how to
determine it.
Part of SSPUX350_080.
Id = HSLco37276
Last message from Disk Agent is sometimes lost. This
causes Disk Agent's status reported as "Failed".
Resolution:
New OmniBack II environment variable:
OB2VBDASLEEPBEFORECLOSE
is introduced.
Its default value is 0. Setting it to a positive
number, in /<OMNIBACK_HOME>/.omnirc file, it specifies
number of seconds to pass before Disk Agent completes
after sending the last block of data.
Sleep time insignificantly influences backup
performance.
Id = HSLco37939
Barlists are members of a group which is not displayed
under reporting group in GUI Reporting.
Resolution:
Barlists are moved to a group that is displayed in GUI.
Id = HSLco37723
Media handling results in IPC error when the buffer
size is increased and variable OB2IPCBUFSIZE is set as
described in above Resolution for problem HSLco37193.
Resolution:
Media Session Manager is rebuilt in order to properly
include the changes introduced with Resolution for
HSLco37193.
Part of SSPUX350_085.
PHSS_26890:
Id = HSLco35076
In case of Media Management Database corruption
backup can fail due to problems with the media
allocation.
Resolution:
Media allocation is improved.
Part of SSPUX350_066.
Id = HSLco35364
Two or more integration backup sessions using the same
device do not queue for backup, but they all try to use
this device at the same time. This results in media
agent failure. During integration backup device
should be locked for backup, but other sessions
can still use it.
Resolution:
Backup Session Manager correctly locks the device(s),
and other sessions wait in the queue for backup until
the device is free.
Part of SSPUX350_077.
Id = HSLco35515
In some cases because of incorrect agent exit code
Backup Session Manager does not terminate other agents
in correct order, which results in Backup Session
Manager hang.
Resolution:
The exit code is changed.
Part of SSPUX350_076.
Id = JAGae27169
Database session manager compares days, not taking
into account 15 minute units. Therefore report shows
some additional backups, which are scheduled past
the specified time frame.
Resolution:
Beside days Database Session Manager compares 15
minute units.
PHSS_26348:
Id = HSLco20414
Device enabling, disabling and status report cannot be
performed using OmniBack II command line.
Resolution:
New options "-disable_device", "-enable_device" and
"-device" are added to omnimm, omniupload and
omnidownload.
Part of SSPUX350_038.
Id = HSLco31865
The message is not properly filtered out.
Resolution:
The message is properly filtered before it is send
to ITO.
Id = HSLco32789
Improper implementation of object assigning to Media
Agent causes Backup Session Manager to loop forever.
Resolution:
Object assignment to Media Agent is corrected.
Id = JAGad90905
Flag for case sensitivity is not checked before
search session is executed.
Resolution:
Case sensitivity flag is always checked.
Id = JAGae05208
The regular expression that is parsed by the awk script
does not return the process ID (PID) which should be
killed.
Resolution:
Regular expression string in awk parse command is
changed.
Id = HSLco33360
Executing an "enter" operation for the slot being
used for backup results in backup failure.
Resolution:
New global option EnterEjectCheckLocking is
introduced. If this option is set, Media Management
operation checks if slot is locked and does not
use it.
Part of SSPUX350_072.
Id = JAGae14881
When a Cell Console client connects to the server,
user name, system name and domain are parsed
correctly, but IP address is not.
Resolution:
A new environment variable
'OB2CRSSTRICTHOSTNAMECHECKING'
is introduced. Setting its value to 1 is to enforce
the use of hostnames obtained from IP address.
Id = HSLco34255
Improperly built Database Session Manager causes
omnirpt to fail.
Resolution:
Properly built Database Session Manager in included
in patch.
PHSS_25003:
Id = HSLco24755
Rescan before backup option incorrectly deletes locked
slots information from OmniBack II database.
Resolution:
Locked slots are not updated during any rescan.
Id = HSLco28232
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 = HSLco28279
In some special cases it is possible for purge of
filenames to fail with error written in the debug.log:
"DB[9] internal error [-16]
record not connected to set."
Resolution:
Purge is improved in order to correctly remove
such records.
Id = HSLco29098
After the mount request during restore from SCSI-II
library, OmniBack II tries to load "" medium into drive.
Resolution:
Restore session manager rechecks the configuration
after the mount request is confirmed.
Part of SSPUX350_048.
Id = HSLco30814
By design, OmniBack II ends session as 'Failed' if
there are no objects to back up.
Resolution:
Two new global variables have been introduced:
1) SessSucessfullWhenNoObjectsBackedUp=0
By setting this variable to 1 user can change the
Omniback II behavior in order to end the session
as successful when there are no objects backed up.
2) TreatScriptReturnAsNormal=<script return>
Setting this variable to a certain number instructs
OmniBack II to treat all the script returns equal
to the specified number as normal.
Part of SSPUX350_062.
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 = HSLco31295
Media Session Manager does not send abort message to
Backup Media Agent started after Copy Media Agent
failed.
Resolution:
Media Session Manager properly handles abort message
from Copy Media Agent.
Id = HSLco31325
1) Error in Backup Session Manager.
When OmniBack II - Informix backup aborting,
another session starts and finishes the remaining
database spaces.
2) Informix wrong error handling.
Resolution:
1) Case BSM_STATE_ABORTING was changed in the order
that Backup Session Manager aborts session when
requested.
2) The way of translating OmniBack II errors into
Informix errors was changed with new condition
checking.
Part of SSPUX350_063.
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.
Part of SSPUX350_059.
PHSS_24659:
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 = NSMex03907
The data backed up with an older version of OmniBack II
and option "-encrypt" can not be selected from
Restore GUI.
Resolution:
It is possible to select objects backed up with an
older version of OmniBack II in Restore GUI.
Id = NSMex04086
Message level of a resuming failure in XP environment
is set to "Normal" instead of "Major".
Resolution:
Message level is corrected.
Id = NSMex04149
Cell Request Service (CRS) executes "omnidbutil -clear"
and returns incorrect exit code.
Resolution:
Correct exit code is returned.
Id = NSMex04164
The parser incorrectly enumerates schedule types.
Resolution:
Schedule types are properly enumerated.
Part of SSPUX350_039.
Id = NSMex04283
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 = NSMex04287
OmniBack II does not lock all available devices.
Resolution:
Load balancing locks enough available devices to be used
for a session.
Id = NSMex04319
When there is no more media available for the running
session, mount request is issued. This mount request can
not be confirmed because the drive is locked by Backup
Session Manager.
Resolution:
Media Session Manager ignores Backup Session Manager
lock making the slot free for mount request
confirmation.
Id = NSMex04311
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.
Part of SSPUX350_040.
Id = NSMex04403
Reporting functionality is missing in Media Session
Manager.
Resolution:
Reporting functionality is added to Media Session
Manager.
Part of SSPUX350_042.
Id = NSMex04540
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.
PHSS_23471:
Id = JAGad36093
If one of the agent fails session status should
indicate "Completed/Errors" instead of "Completed".
Resolution:
Session status is correct.
Part of SSPUX350_027.
Id = NSMbb37729
Database Session Manager starts Device Browser with
incorrect options.
Resolution:
Structure containing Device Browser options is
initialized before it is filled with the parameters.
Id = NSMex03425
Backup of SAP archive logs fails if a backup request
for next archive log comes when Backup Session Manager
is already exiting.
Resolution:
Datalist entries for BAR session are removed.
Id = NSMex03621
When restoring the data from STK or GRAU library,
wrong medium is loaded into drive after the mount
request confirmation.
Resolution:
Mount request is properly handled.
Id = NSMex03701
Backing up Informix Parallel Server with many
datafiles where request is coming from the node
that is not specified in Informix backup
specification results in many warning messages reported
during the session.
Resolution:
New global option InformixparallelBackupIgnoreWarning
is added. Warnings are ignored if this option is set
to 1. Default value is 0.
Id = NSMex03711
Licensing is not working properly for systems with
more than 20 lan cards, due to an OmniBack limitation.
Resolution:
Number of lan cards on a single system can be up to 100.
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 = NSMex03847
New Media Class, 9840, is introduced with A.03.50
release. This caused that some of previously created
devices did not work with OmniBack II 3.50.
Resolution:
New utility, mchange, changes media class for a pool
and for all devices that use the particular pool.
Usage of mchange is:
mchange -version | -help
mchange -pool PoolName -newtype NewMediaClass
Id = NSMex03894
OmniBack II has a 600 mountpoints limitation. Host
backup fails if there are more than 600 mountpoints.
Resolution:
Number of mountpoints per host increased to 50000.
Id = NSMex03910
Major messages are not checked by Backup Session
Manager.
Resolution:
Backup Session Manager checks all messages.
Id = NSMex03917
If "omnidbutil -cdbsync" command is started in
Service Guard environment, some objects disappear
from OmniBack II internal database.
Resolution:
omnidbutil works properly in Service Guard
environment.
Part of SSPUX350_026.
Id = NSMex03991
Backup Session Manager incorrectly appends full
Oracle backups.
Resolution:
Backup Session Manager correctly checks properties
of pool.
Id = NSMbb38972
omnitrig does not support MS Exchange 2000 integration.
Resolution:
Scheduled MS Exchange 2000 backups are properly
started.
Part of SSPUX350_020.
Id = NSMex03246
Normal, Warning and Minor messages can be seen on ITO
Management server even though OVfilter is set up to
forward only Critical messages.
Resolution:
Messages are forwarded according to OVfilter setup.
Id = NSMex04159
When Backup Session Manager waits for the next client it
disables new client connections.
Resolution:
Proper previously failed session is restarted.
Id = NSMex04261
Import of integration session fails if the session is
spanned over two or more media.
Resolution:
Checking for object description is changed.
PHSS_23106:
Id = NSMex03757
Performance degrated by up to 50% after upgrade from
OmniBack II 2.55 or 3.00.
Resolution:
Redundant update of the objects removed.
Part of SSPUX350_023.
Id = NSMex03977
Listing of objects failed for the objects that have
been purged from the database, because there is no
link between objects and object versions.
Resolution:
Fix is implemented in libob2ecbd.sl.
PHSS_22370:
Id = JAGad13634
File /opt/omni/sbin/nb_informix is missing.
Resolution:
File /opt/omni/sbin/nb_informix is added to OMNI-CS
fileset.
Id = JAGad17029
Using "List from media" option in restore context
ignores "See private objects" option. Objects that are
backed up as "Private" are not listed.
Resolution:
Option parsing in restore context is improved.
Id = NSMex03356
If there are more than 100 network interfaces, ioctl()
call fails.
Resolution:
Buffer for SIOCGIFCONF is increased to support up to
1000 network interfaces.
Id = NSMex03365
When backup and file search sessions are started in
parallel, file search session locks the database.
Backup Session Manager tries to write backup
information into locked database. Since this action can
not be performed, the following messages are logged
in the rds.log:
"11740 [10-Apr-00 17:37:07] error status=5
11741 [10-Apr-00 17:37:07] GROUPLOCK ELEMENT:
userID=4, LockType=6, LockMode= *, RecSetType=10002,
dba=[0:0], odnum=1"
Resolution:
File pattern search is optimized to minimize the
possibilities of group locks.
Id = NSMex03419
OmniBack II 3.50 objects are case insensitive which is
not true for the SAP objects backed up with 2.55
version. Object tape format is changed with 3.50 as
well. These changes caused some SAP objects not to be
displayed in the Restore GUI after importing the tape
with SAP objects from 2.55 to 3.50.
Resolution:
Object names from tape are converted into OmniBack II
3.50 format after tape import from 2.55.
Id = NSMex03466
System name checking is not performed for systems with
multiple LAN cards. Backup Session Manager is checking
the system names only when looking for clusters.
Resolution:
System name checking is performed when looking for
clusters and systems with multiple LAN cards.
Id = NSMex03481
Aborting backup session is not possible because
Backup Session Manager incorrectly aborts Disk Agents
after the package switch.
Resolution:
Disk Agents are properly aborted.
Id = NSMex03491, JAGad28516
In host backup only mount point directories can be
excluded. If a directory is not a mount point then it
cannot be excluded from the backup.
Resolution:
Non-mountpoint directories can now be excluded.
Id = NSMex03493
Scheduled reports are not started with "-debug" option
although omnitrig is.
Resolution:
Command line option passing is implemented for omnirpt.
Id = NSMex03583, NSMex03631
Mount request is not properly implemented for SCSI-II
changer devices.
Resolution:
OmniBack II properly handles mount requests.
Id = NSMex03638
Option "-change_objname" is not meant to be a part of
OmniBack II A.03.50.
Resolution:
Option "-change_objname" is removed.
Id = NSMex03501
After upgrading OmniBack ServiceGuard package from
3.00 to 3.50, it is not possible to list media due to
incorrect ownership of medium.
Resolution:
Virtual hostname is used for medium ownership.
Part of SSPUX350_001.
Id = NSMex03683
Copy session is aborted when copying a write-protected
tape. When write-protected tape in the source drive is
checked, the cleaning tape for that drive is requested
and the following message appears:
"Cleaning tape requested by device <device_name>.
Please clean the drive.".
Resolution:
The cleanme signal is now processed correctly.
Part of SSPUX350_004.
Id = NSMex02584
Execution of command
"omnidb -filesystem <FS_Object> -file <File_Name>"
causes a memory leak in RDS (approx. 300 bytes). If the
command is started more than 100000 times, it can cause
RDS to die due to a lack of memory.
Resolution:
Fix is implemented in libob2ecdb.sl.
Part of SSPUX350_006.
Id = NSMex03702
RDS dies during a large SAP restore due to memory leak
described in NSMex02584.
Resolution:
Fix is implemented in libob2ecbd.sl.
Part of SSPUX350_006.
Id = NSMex03289
Media sync does not work properly when table of
exported/recycled media gets too big (>3000 media).
Some new sessions dissapear from database. No error is
reported.
Resolution:
Improved error handling logs this event in debug.log.
Part of SSPUX350_003.
Id = NSMex03521
Database stays in the hot mode after issuing an
"omnidbcheck" command. If a large amount of data is
written before OmniBack II daemons are stopped, it can
happen that hot files are not properly flushed. This
causes corruption of database.
Resolution:
omnidbcheck flushes hot files immediately after
database check.
Part of SSPUX350_003.
Id = NSMex03737
Media Session Manager is incorrectly initializing media
in ServiceGuard environment. Owner of medium is set to
hostname of the active node. This results in wrong
medium handling and objects from such medium are
removed from the OmniBack II database each time Media
Session Manager is started.
Resolution:
Initialization of media in ServiceGuard environment
is improved.
Before applying the fix for NSMex03737 please run
following commands:
omnidbutil -change_cell_name <hostname1>
and
omnidbutil -change_cell_name <hostname2>
where <hostname1> and <hostname2> are names of
ServiceGuard nodes.
Part of SSPUX350_010.
Id = NSMex03758, NSMex03759, NSMex03646
OmniBack II reports an error:
"Database is probably corrupt."
for backup sessions that span over two or more media
if one of them is already overwritten/exported because
then some of the objects are already removed from the
database.
Resolution:
Removed objects are skipped during the database queries.
Part of SSPUX350_010.
Enhancement:
No
SR:
H555009863 H555009297 H555009560 H555009843 H555008927
H555008892 B554000611 B554000630 B554000712 B554000622
B554000550 B554000650 B554000623 B554000830 B554000831
B554000813 B554000418 B554000751 B554000761 B554000556
B554000487 B554000496 B554000776 B554000867 B554000597
B554000887 B554000888 B554000889 B555002886 H555008533
H555008832 H555004477 H555008807 H555008780 H555008690
H555008261 8606262839 H555008452 H555008410 B554000768
8606221771 8606248483 H555007191 H555003134 H555007796
H555007428 H555006924 8606236143 H555005975 H555005922
H555006248 B555011718 H555006771 H555006710 H555006799
H555006810 8606217323 H555005697 H555005402 H555005732
H555005680 H555005149 H555004871 H555005681 H555005583
H555005917 H555005973 8606179334 8606195237 H555004061
H555004026 H555004027 B555008272 H555005234 H555004452
H555003831 B554000869 H555005624 H555004364 H555004475
B554000372 B554000841 H555004021 8606166806 H555004350
8606159187 8606144294 8606147687
Patch Files:
OMNIBACK-II.OMNI-CS,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm
/opt/omni/lbin/crs
/opt/omni/lbin/dbsm
/opt/omni/lbin/mmd
/opt/omni/lbin/msm
/opt/omni/lbin/rsm
/opt/omni/lbin/psm
/opt/omni/lbin/dbbda
/opt/omni/sbin/omnidbcheck
/opt/omni/sbin/omnidbutil
/opt/omni/sbin/omnitrig
/opt/omni/sbin/nb_informix
/opt/omni/sbin/utilns/mchange
/opt/omni/sbin/install/omniforsg.ksh
/opt/omni/lib/libob2ecdb.sl
/opt/omni/lib/libob2ecmn.sl
/opt/omni/lib/libob2emmdb.sl
/opt/omni/lib/libob2eadm.sl
/opt/omni/newconfig/etc/opt/omni/options/global
/opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh
what(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/omni/lbin/bsm:
[TZ=GMT0 /opt/omni/lbin/bsm -version]
HP OpenView OmniBack II A.03.50: BSM, internal build
PHSS_28727/PHSS_28728, built on Wed Mar 26
11:11:09 2003
/opt/omni/lbin/crs:
[TZ=GMT0 /opt/omni/lbin/crs -version]
HP OpenView OmniBack II A.03.50: CRS, internal build
PHSS_28021/PHSS_28022, built on Wed Nov 20
13:11:01 2002
/opt/omni/lbin/dbsm:
[TZ=GMT0 /opt/omni/lbin/dbsm -version]
HP OpenView OmniBack II A.03.50: DBSM, internal buil
d PHSS_28021/PHSS_28022, built on Wed Nov 20
12:01:28 2002
/opt/omni/lbin/mmd:
[TZ=GMT0 /opt/omni/lbin/mmd -version]
HP OpenView OmniBack II A.03.50: MMD, internal build
PHSS_28021/PHSS_28022, built on Wed Nov 20
12:12:19 2002
/opt/omni/lbin/msm:
[TZ=GMT0 /opt/omni/lbin/msm -version]
HP OpenView OmniBack II A.03.50: MSM, internal build
PHSS_28021/PHSS_28022, built on Wed Nov 20
11:44:13 2002
/opt/omni/lbin/rsm:
[TZ=GMT0 /opt/omni/lbin/rsm -version]
HP OpenView OmniBack II A.03.50: RSM, internal build
PHSS_28021/PHSS_28022, built on Wed Nov 20
11:32:05 2002
/opt/omni/lbin/psm:
[TZ=GMT0 /opt/omni/lbin/psm -version]
HP OpenView OmniBack II A.03.50: PSM, internal build
PHSS_28021/PHSS_28022, built on Thu Nov 21
10:10:36 2002
/opt/omni/lbin/dbbda:
[TZ=GMT0 /opt/omni/lbin/dbbda -version]
HP OpenView OmniBack II A.03.50: DBBDA, internal bui
ld PHSS_28021/PHSS_28022, built on Thu Nov 2
1 09:47:19 2002
/opt/omni/sbin/omnidbcheck:
[TZ=GMT0 /opt/omni/sbin/omnidbcheck -version]
HP OpenView OmniBack II A.03.50: OMNIDBCHECK, intern
al build PHSS_28021/PHSS_28022, built on Thu
Nov 21 10:10:26 2002
/opt/omni/sbin/omnidbutil:
[TZ=GMT0 /opt/omni/sbin/omnidbutil -version]
HP OpenView OmniBack II A.03.50: OMNIDBUTIL, interna
l build PHSS_28021/PHSS_28022, built on Thu
Nov 21 10:10:16 2002
/opt/omni/sbin/omnitrig:
[TZ=GMT0 /opt/omni/sbin/omnitrig -version]
HP OpenView OmniBack II A.03.50: OMNITRIG, internal
build PHSS_28727/PHSS_28728, built on Tue Ma
r 25 10:08:42 2003
/opt/omni/sbin/nb_informix:
None
/opt/omni/sbin/utilns/mchange:
[TZ=GMT0 /opt/omni/sbin/utilns/mchange -version]
HP OpenView OmniBack II A.03.50: MCHANGE, internal b
uild PHSS_23470/PHSS_23471, built on Fri Mar
2 10:43:47 2001
/opt/omni/sbin/install/omniforsg.ksh:
None
/opt/omni/lib/libob2ecdb.sl:
None
/opt/omni/lib/libob2ecmn.sl:
None
/opt/omni/lib/libob2emmdb.sl:
None
/opt/omni/lib/libob2eadm.sl:
None
/opt/omni/newconfig/etc/opt/omni/options/global:
None
/opt/omni/newconfig/etc/opt/omni/sg/csfailover.ksh:
None
cksum(1) Output:
OMNIBACK-II.OMNI-CS,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP:
1218843371 1182707 /opt/omni/lbin/bsm
612034413 726899 /opt/omni/lbin/crs
1264986274 1239560 /opt/omni/lbin/dbsm
1499776461 530043 /opt/omni/lbin/mmd
3952351799 694260 /opt/omni/lbin/msm
3337452184 874939 /opt/omni/lbin/rsm
2483849962 435578 /opt/omni/lbin/psm
2181795817 365783 /opt/omni/lbin/dbbda
3950965868 472364 /opt/omni/sbin/omnidbcheck
2522875831 697971 /opt/omni/sbin/omnidbutil
50284200 406791 /opt/omni/sbin/omnitrig
2755861046 353611 /opt/omni/sbin/nb_informix
161435393 209564 /opt/omni/sbin/utilns/mchange
3275622251 5084 /opt/omni/sbin/install/omniforsg.ksh
1916829165 885460 /opt/omni/lib/libob2ecdb.sl
114168317 812458 /opt/omni/lib/libob2ecmn.sl
1619154841 651912 /opt/omni/lib/libob2emmdb.sl
3526392551 692720 /opt/omni/lib/libob2eadm.sl
2258981330 34415 /opt/omni/newconfig/etc/opt/omni/options/
global
1805127806 2350 /opt/omni/newconfig/etc/opt/omni/sg/
csfailover.ksh
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
If any newer SSP for the Cell Server is installed
on your system, you must re-apply the SSP after
installing this Cell Server patch.
PHSS_28726:
Release Date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco20414 SR:H555003134
Id = HSLco37193 SR:H555008807
PHSS_28726 is required for these defect fixes.
PHSS_28579:
Release Date: Available
Id = HSLco40537 SR:H555009863
PHSS_28579 is required for this defect fix.
PHSS_28571:
Release Date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco37193 SR:H555008807
Bad catalog access messages are displayed without
PHSS_28571.
PHSS_28020:
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28020 is required for this defect fix.
PHSS_28018:
Release date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco30814 SR:H555006710
Id = HSLco37193 SR:H555008807
PHSS_28018 is required for these defect fixes.
PHSS_27590:
Release date: Available
Id = HSLco20414 SR:H555003134
Id = NSMex03638 SR:B554000768
PHSS_27590 is required for these defect fixes.
PHSS_25951:
Release date: Available
Id = HSLco31325 SR:H555006810
PHSS_25951 is required for this defect fix.
Supersedes:
PHSS_28022 PHSS_26890 PHSS_26348 PHSS_25003 PHSS_24659 PHSS_23471
PHSS_23106 PHSS_22370
Equivalent Patches:
PHSS_28727:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Patch Package Size: 11090 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_28728
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28728.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28728. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28728.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28728.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28728.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28728:
NOTE!
This Patch has to be installed on the Cell Manager host.
OmniBack II Services must be shut down before the patch is
installed. Use the following command to shut down the
services:
"/opt/omni/sbin/omnisv.sh stop".
After the installation is complete, restart OmniBack II
Services using "/opt/omni/sbin/omnisv.sh start".
Patch includes the following Site Specific Patches:
SSPUX350_001
SSPUX350_003
SSPUX350_004
SSPUX350_006
SSPUX350_010
SSPUX350_020
SSPUX350_023
SSPUX350_026
SSPUX350_027
SSPUX350_038
SSPUX350_039
SSPUX350_040
SSPUX350_042
SSPUX350_048
SSPUX350_059
SSPUX350_062
SSPUX350_063
SSPUX350_066
SSPUX350_072
SSPUX350_076
SSPUX350_077
SSPUX350_080
SSPUX350_085
SSPUX350_087
SSPUX350_088
SSPUX350_089
-----End of Document ID: PHSS_28728------------------------------------------
Document ID: PHSS_28726
Date Loaded: 20030404
Title: s700_800 11.X OV OB3.50 patch - CC packet
Patch Name: PHSS_28726
Patch Description: s700_800 11.X OV OB3.50 patch - CC packet
Creation Date: 03/03/24
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.03.50
Filesets:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28726
Symptoms:
PHSS_28726:
Id = HSLco39486 SR:H555009404
GUI started with "xomni -restore -debug 1-99"
ends abnormally when Informix server option in
Restore context is selected.
Id = HSLco40532 SR:H555009862
When starting "omnir -mssql -barhost <host> -base
<basename>", restore ends with:
"Set '<basename>:0' not found. Most probably there
is a DNS configuration problem or one of the systems
is not in the same Cell Manager system."
Id = HSLco40537 SR:H555009863
When backing up very large SAP databases with SSEA
split mirror, backups can fail with error:
"BR280I Time stamp <time>
BR296I Split of mirror disks successful
BR274E File /<sapdata_path>/system.data1 not found"
PHSS_28223:
Id = HSLco37193 SR:H555008807
When backing up SAP integration with EMC split mirror
functionality, not all the SAP files are backed up.
Id = HSLco37723 SR: H555008892
If a Manager-of-Managers Server is also a
MC/ServiceGuard virtual node, then the command
"omnirpt -report list_sessions -timeframe
<start_hours_ago><hours_duration>
-multicell -no_multiple"
lists the matching sessions from this node twice.
PHSS_27596:
Id = HSLco31733 SR: H555006893
Additional dates added to periodic backup schedule
after 13 months.
Id = HSLco35611 SR: H555008476
Restore GUI can not handle two separate Oracle7
databases with the same SID. GUI does not display
all objects versions.
Id = HSLco35661 SR: H555008490
Filesystem restore summary displays incorrect version
of file selected for restore.
Id = HSLco36478 SR: H555008657
GUI ends abnormally when trying to perform Informix
restore.
Id = HSLco36904 SR: H555008730
xomnimm reports "Internal error" when trying to load
large media pool or device.
Id = JAGad97576 SR: 8606228519
Command Line (CLI) command omnimcopy does not provide
error codes.
Id = HSLco36916 SR: H555008732
HP-UX GUI corrupts barlists for SSEA backup created
using Windows GUI.
PHSS_25957:
Id = HSLco28793 SR: H555006144
Omnir command starts multiple Database Session
Managers.
Id = HSLco29971 SR: H555006524
Double-clicking an existing EMC datalist results in
the following error:
"Unknown object type encountered.".
Id = HSLco31433 SR: H555006834
omnir incorrectly parses "-srdf_smmf" option.
Id = HSLco31734 SR: H555006894
OmniBack does not select all the objects with the
same timestamp.
Id = JAGad57038 SR: 8606187829
"Omnidb -filesystem -detail" generates output in which
Object Name and Object Type files contents are
reversed.
PHSS_24661:
Id = NSMex03922
Listing of Oracle objects on GUI fails.
Id = NSMex03986
Omnir core dumps.
Id = NSMex04296
Backup scheduler shows incorrect dates.
Id = NSMex04323
Command "omnimm -enter [slot_range]" returns invalid
slot error.
Id = NSMex04347
Restore to a different host fails with an error:
"Can not stat script /usr/omni/bin/(null).".
Id = NSMbb39907
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.
Id = NSMex03989
Command
"omnirpt -report db_size -html -email <e-address>"
works improperly.
Id = NSMex04439
omnib command ignores "-encode" option.
Id = NSMbb38972
Exchange 2000 backup cannot be started from command
line.
PHSS_22851:
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI.
Id = JAGad35002
If database integration in a MC/ServiceGuard cluster is
backed up, the backup can report an error.
Id = NSMex03419
After importing a tape from 2.55 to 3.50 cell some of
the files can not be restored.
Id = NSMex03475
Restore GUI does not display SAP objects, if two
SAP instances with the same name are backed up on
different host.
Id = NSMex03505
a) When selecting restore of SAP object, message
"Cannot browse from root" appears.
b) When selecting restore from File System Restore
Dialog GUI might core dump.
Id = NSMex03658
Exit code of omniminit is incorrect.
Id = NSMex03833
The options under Edit button are not accessible even
if user has rights.
Id = JAGad29457
Ownership incorrectly displayed within restore GUI.
Id = JAGad33161
Datalists/barlists with EMC integration are incorrectly
created.
PHSS_22039:
Id = NSMex03503
Users with only "Start Backup" privilege can delete
datalists.
Id = NSMex03511
"Send external" method always executes external script
on Cell Manager system.
Defect Description:
PHSS_28726:
Id = HSLco39486
DbgPlain function is called with wrong string format.
Resolution:
String format for DbgPlain() is corrected.
Id = HSLco40532
The source of <basename> is not parsed.
Resolution:
The source of <basename> is parsed.
Id = HSLco40537
In split mirror environment with very large SAP
databases, it can happen that the size of the message
buffer that OmniBack II uses is too small to fit in
for the complete list of SAP files to be backed up.
Resolution:
New environment variable is introduced: OB2IPCBUFSIZE.
In order to solve this problem, the buffer size can
be increased by setting the OB2IPCBUFSIZE environment
variable in the .omnirc file on CM, R1 and R2 hosts,
specifying the desired amount of memory to be used
for the buffer.
For determining buffer size please see the Resolution
of Id = HSLco37193 below.
Part of SSPUX350_088.
PHSS_28223:
Id = HSLco37193 SR:H555008807
In split mirror environment with huge SAP databases
it can happen that the size of the message buffer
OmniBack II uses is too small to receive complete list
of SAP files to be backed up.
Resolution:
Setting the OB2IPCBUFSIZE environment variable in the
/opt/omni/.omnirc file on Cell Server, R1 and R2 hosts,
specifying the desired amount of memory to be used for
the buffer solves the described problem.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/[c0t1d1,lvol1])
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Known problems:
---------------
If the calculated variable OB2IPCBUFSIZE is correctly
set, but is still too small for the file list to fit
into the message buffer, the session will fail with
the following error seen in the report:
BR295I Splitting mirror disks...
BR280I Time stamp <time>
BR279E Return code from '/opt/omni/lbin/ob2smbsplit
/<sap_homedir_path>/.<filename>.lst': 2
BR299E Split/resynchronization of mirror disks failed
In this case the variable OB2IPCBUFSIZE must be
recalculated to appropriate value. See above how to
determine it.
Part of SSPUX350_080.
Id = HSLco37723
Media handling results in IPC error when the buffer
size is increased and variable OB2IPCBUFSIZE is set as
described in above Resolution for problem HSLco37193.
Resolution:
Media Session Manager is rebuilt in order to properly
include the changes introduced with Resolution for
HSLco37193.
Part of SSPUX350_085.
PHSS_27596:
Id = HSLco31733
In next year the same date is not the same day in
week. Scheduled dates after one year are just copied,
so backups are scheduled on wrong days.
Resolution:
Days are correctly moved to next year.
Id = HSLco35611
GUI does not check on which host Oracle7 database is
backed up and all backup versions are appended to
the first one found.
Resolution:
Host matching and object version adding to list is
improved.
Id = HSLco35661
Restore summary always displays the last version of
file selected for restore.
Resolution:
Restore summary displays file versions as they were
selected for restore.
Id = HSLco36478
Incorrect pointer handling causes GUI to end
ungracefully.
Resolution:
Pointers are properly handled.
Id = HSLco36904
A buffer sent to xomnimm after loading large media pool
or device is too big.
Resolution:
xomnimm reads the buffer size as specified in .omnirc
file with OB2IPCBUFSIZE variable.
Id = JAGad97576
Omniback II reports the same exit code regardless of
success or failure of the command omnimcopy.
Resolution:
When command omnimcopy fails Omniback II returns
exit code 3 = EX_ERR_INTERNAL.
Id = HSLco36916
Saving a SSEA barlist with HP-UX GUI corrupts barlist.
Resolution:
Saving a barlist with HP-UX GUI is not possible.
Part of SSPUX350_078.
PHSS_25957:
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 SSPUX350_051.
Id = HSLco29971
Displaying EMC datalists is disabled.
Resolution:
Displaying EMC datalists is enabled.
Part of SSPUX350_055.
Id = HSLco31433
When "-rawdisk" option is combined with "-srdf",
"-smmf" or "-srdf_smmf", it is recognized only after
latter options have been checked.
Resolution:
Option "-rawdisk" has higher priority.
Id = HSLco31734
Restore GUI incorrectly interprets the data obtained
from Database Session Manager.
Resolution:
Restore GUI properly displays the latest versions of
restore objects.
Id = JAGad57038
The order of putting Object Type and Object FileName
into output files is wrong.
Resolution:
Object Type and Object FileName are displayed in
correct order.
PHSS_24661:
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 = NSMex04296
Backup scheduler loses months prior to January, 2002.
Resolution:
Scheduler optimization improved.
Id = NSMex04323
When executing "omnimm -enter [slot_range]" command
a "0" is appended to slot range. This causes invalid
slot error.
Resolution:
"omnimm -enter [slot_range]" command works properly.
Id = NSMex04347
Restore GUI improperly sends empty pre- and post-exec
options to Restore Session Manager.
Resolution:
Fix is implemented in Restore GUI.
Id = NSMbb39907
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 SSPUX350_031.
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.
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}
Part of SSPUX350_038.
Id = NSMex03989
Command
"omnirpt -report db_size -html -email <e-address>"
returns HTML code instead of formatted report.
Resolution:
Missing header is added to HTML report.
Id = NSMex04439
omnib command ignores "-encode" option.
Resolution:
omnib command properly recognizes "-encode" option.
Id = NSMbb38972
Exchange 2000 backup cannot be started from command
line.
Resolution:
It is possible to start Exchange 2000 backup from
command line.
Part of SSPUX350_020.
PHSS_22851:
Id = JAGad30352
"EMC Support" tab is not available in
"Backup Specification - Options" GUI, unless the
cell_info entry for the Cell Manager has the
"-emc" option.
Resolution:
xomnibackup now correctly checks cell_info file
for "-emc" options.
Id = JAGad35002
a )Windows NT GUI supports cluster import which
creates additional attributes in the cell info
file to mark cluster nodes and virtual servers.
MC/SG clusters do not have such support yet.
b) Motif GUI does not have any way to import cluster
in the cell. Session Manager starts agent on certain
machine and expects that the connection will come
from that machine or a physical node on a cluster. If
additional attributes in the cell info are not set
then SM aborts the connection.
Resolution:
.util shell script has been enhanced to allow import
of the cluster using Windows GUI. The script handles
messages INFO_CLUS and INFO_CLUS1 which allow the
import to happen.
Id = NSMex03419
OmniBack II 3.50 objects are case insensitive which is
not true for the SAP objects backed up with 2.55
version. Object tape format is changed with 3.50 as
well. These changes caused some SAP objects not to be
displayed in the Restore GUI after importing the tape
with SAP objects from 2.55 to 3.50.
Resolution:
Names are tape format are converted into OmniBack II
3.50 format after tape import from 2.55.
Id = NSMex03475
Restore GUI does not display SAP objects, if two
SAP instances with the same name are backed up on
different host.
Resolution:
xomnirestore has been improved to show all object.
Id = NSMex03505
a) When selecting restore of SAP object, message
"Cannot browse from root" appears.
b) Two different structures with the same name
were 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 = NSMex03833
User rights are not properly interpreted.
Resolution:
User rights permissions has been modified.
Id = JAGad29457
xomnirestore shows user name and group name for backed
up objects. If users on different clients have
different UID and GID wrong user will be shown in
version browser.
Resolution:
New option GUIShowUID has to be set in file:
/etc/opt/omni/options/global on Cell Manager host.
GUIShowUID=<number>
where <number> means:
- 0, GUI converts UIDs and GIDs to strings
- 1, only UIDs and GIDs numbers will be showen
Part of SSPUX350_013.
Id = JAGad33161
Options for EMC integration are incorrectly saved when
datalist/barlist is created with Motif GUI.
Resolution:
EMC type resolving has been improved.
Part of SSPUX350_013.
PHSS_22039:
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.
Enhancement:
No
SR:
H555009862 H555009592 H555009404 H555009863 H555008927
H555008892 H555008803 H555008807 H555008476 H555008657
H555006893 H555008730 B554000640 B554000632 H555008732
H555008490 8606228519 H555006524 H555006894 H555006834
H555006144 8606187829 H555004942 H555003134 8606179663
H555005709 H555005547 H555005845 H555004369 H555004246
H555004381 8606160131 8606161034 8606163859 B554000788
8606165711 B554000550 H555003728 B554000606 B554000634
Patch Files:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.03.50/
packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sco/i386/unixware/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.50/packet.Z
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.50/
packet.Z
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.50/
packet.Z
what(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-1020/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-10/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/hp/s800/hp-ux-11/A.03.50/
packet.Z:
None
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/cc/dec/alpha/osf1-4/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/ncr/i386/mp-ras/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/gpl/i386/linux/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/ibm/rs6000/aix-42/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/sco_sv/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sco/i386/unixware/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sequent/i386/dynix/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sgi/mips/irix-62/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/siemens/r400/sinix/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/solaris-26/A.03.50/
packet.Z:
None
/opt/omni/databases/vendor/cc/sun/sparc/sunos/A.03.50/
packet.Z:
None
cksum(1) Output:
OMNIBACK-II.OMNI-HPUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
1535824785 11152455 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-1020/A.03.50/packet.Z
903497905 11208336 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-10/A.03.50/packet.Z
2271713999 11147314 /opt/omni/databases/vendor/cc/hp/s800/
hp-ux-11/A.03.50/packet.Z
OMNIBACK-II.OMNI-OTHUX-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
3047406478 4949573 /opt/omni/databases/vendor/cc/dec/alpha/
osf1-4/A.03.50/packet.Z
2055934160 4172467 /opt/omni/databases/vendor/cc/ncr/i386/
mp-ras/A.03.50/packet.Z
2143153229 8627390 /opt/omni/databases/vendor/cc/gpl/i386/
linux/A.03.50/packet.Z
723479229 4217255 /opt/omni/databases/vendor/cc/ibm/rs6000/
aix-42/A.03.50/packet.Z
3759737747 4028813 /opt/omni/databases/vendor/cc/sco/i386/
sco_sv/A.03.50/packet.Z
3343189653 3941384 /opt/omni/databases/vendor/cc/sco/i386/
unixware/A.03.50/packet.Z
3819542767 4126913 /opt/omni/databases/vendor/cc/sequent/
i386/dynix/A.03.50/packet.Z
1089219669 5022182 /opt/omni/databases/vendor/cc/sgi/mips/
irix/A.03.50/packet.Z
2371282407 5922365 /opt/omni/databases/vendor/cc/sgi/mips/
irix-62/A.03.50/packet.Z
3937653808 4878331 /opt/omni/databases/vendor/cc/siemens/
r400/sinix/A.03.50/packet.Z
1711704483 4578857 /opt/omni/databases/vendor/cc/sun/sparc/
solaris/A.03.50/packet.Z
3292819385 4661017 /opt/omni/databases/vendor/cc/sun/sparc/
solaris-26/A.03.50/packet.Z
2190727103 6980139 /opt/omni/databases/vendor/cc/sun/sparc/
sunos/A.03.50/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
If any newer SSP for the SSEA is installed
on your system, you must re-apply the SSP after
installing this SSEA patch.
PHSS_28728:
Release date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco37193 SR:H555008807
PHSS_28728 is required for these defect fixes.
PHSS_28579:
Release date: Available
Id = HSLco40537 SR:H555009863
PHSS_28579 is required for this defect fix.
PHSS_28571:
Release date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco37193 SR:H555008807
Bad catalog access messages are displayed without
PHSS_28571.
PHSS_28020:
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28020 is required for this defect fix.
PHSS_28018:
Release Date: Available
Id = HSLco40537 SR:H555009863
Id = HSLco37193 SR:H555008807
PHSS_28018 is required for these defect fixes.
Supersedes:
PHSS_28223 PHSS_27596 PHSS_25957 PHSS_24661 PHSS_22851 PHSS_22039
Equivalent Patches:
PHSS_28725:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Patch Package Size: 97340 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_28726
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28726.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28726. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28726.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28726.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28726.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28726:
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.
Patch includes the following Site Specific Patches:
SSPUX350_013
SSPUX350_020
SSPUX350_031
SSPUX350_038
SSPUX350_051
SSPUX350_055
SSPUX350_078
SSPUX350_080
SSPUX350_085
SSPUX350_088
-----End of Document ID: PHSS_28726------------------------------------------
Document ID: PHSS_28724
Date Loaded: 20030404
Title: s700_800 11.X OV OB4.10 patch - SAP packet
Patch Name: PHSS_28724
Patch Description: s700_800 11.X OV OB4.10 patch - SAP packet
Creation Date: 03/03/20
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.04.10
Filesets:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28724
Symptoms:
PHSS_28724:
Id = HSLco39882 SR: H555009563
Data Protector SAP R/3 integration does not work on
SAP R/3 system with Oracle 9i.
Id = HSLco40709 SR: H555009941
Restore of sap tablespace on raw disk bigger than the
one backed up falls into loop. Restore agent is then
aborted due to inactivity by session manager.
Id = HSLco40764 SR: H555009971
During a SAP backup session, debug.log file is being
filled with "Unknown state" messages.
PHSS_28344:
Id = HSLco36193 SR: H555008621
Errors are reported in debug.log for files of size 0 and
for missing function entry statements.
Id = HSLco36404 SR: H555008642
SAP BR tools 6.10 reports:
"BR247E No Backup utility ID or ID longer than 16
characters".
Id = HSLco37193 SR: H555008807
When backing up SAP integration with EMC split mirror
functionality, not all the SAP files are backed up.
Id = HSLco37210 SR: H555008812
During raw device SAP restore following error is
reported:
"|Minor| From: OB2BAR_SAPREST<host> "" Time:<time>
Error: Cannot open object <raw disk path>
|20| Not a directory)."
Id = HSLco37773 SR: H555008906
During some backint queries following error is reported:
"|Critical| From: OB2BAR<host> "" Time:<time>
Failed to allocate memory.
System error: |12| Not enough space"
Id = HSLco37783 SR: H555008908
When OmniBack II tries to backup nonexistent SAP redo
logs, session ends as failed.
Id = HSLco39552 SR: H555009439
SAP backup on Linux, reports the following error:
"Cannot get information on file
'/sapmnt/SID/exe/brarchive ...' Error: 22."
PHSS_27453:
Id = HSLco35628 SR: H555008480
Raw partition backup is not restored even though
OmniBack II states that restore session is completed
successfully.
Id = HSLco35646 SR: H555008483
Aborting SAP backup session results in executing new
session.
Id = JAGae25124 SR: 8606260802
Session log files contains improper information when
SAP backup fails.
Id = HSLco35966 SR: H555008565
"util_sap -APP" displays connection strings.
PHSS_26888:
Id = HSLco33261 SR: H555007380
SAP integration on UNIX clients automatically passes
"-u" option.
Id = HSLco33795 SR: H555007605
OmniBack II SAP integration is not supported on
Compaq Tru64 operating system.
Defect Description:
PHSS_28724:
Id = HSLco39882
Oracle Server Manager (svrmgrl) is obsoleted with
Oracle 9i. sqlplus needs to be used instead.
Resolution:
Data Protector SAP R/3 integration works on SAP R/3
system with Oracle 9i.
Part of SSPUX410_067.
Id = HSLco40709
Size of data to be restored is mistakenly overwritten
by disk size checking function.
Resolution:
Disk size checking function is changed in a manner that
it properly calculates destination directory properties.
Part of SSPUX410_064.
Id = HSLco40764
All information messages in switch.log, except #SUCCESS
and #ERROR, are being treated as serious error.
Resolution:
Status of information messages is lowered from "error"
to normal.
PHSS_28344:
Id = HSLco36193
CheckFile checks marked error if parameter is null.
Debugs are initialized after function entry is marked.
Resolution:
Error messages are not written to the debug.log file.
Id = HSLco36404
Set ID number searching is not strict enough and gets
confused by new SAP BR tools format.
Resolution:
Stricter checking is applied to see if it really is
backint ID.
Part of SSPUX410_036.
Id = HSLco37193
In split mirror environment with huge SAP databases
it can happen that the size of the message buffer
OmniBack II uses is too small to receive complete list
of SAP files to be backed up.
Resolution:
Setting the OB2IPCBUFSIZE environment variable in the
/opt/omni/.omnirc file on Cell Server, R1 and R2 hosts,
specifying the desired amount of memory to be used for
the buffer solves the described problem.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/|c0t1d1,lvol1|)
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Known problems:
---------------
If the calculated variable OB2IPCBUFSIZE is correctly
set, but is still too small for the file list to fit
into the message buffer, the session will fail with
the following error seen in the report:
BR295I Splitting mirror disks...
BR280I Time stamp <time>
BR279E Return code from '/opt/omni/lbin/ob2smbsplit
/<sap_homedir_path>/.<filename>.lst': 2
BR299E Split/resynchronization of mirror disks failed
In this case the variable OB2IPCBUFSIZE must be
recalculated to appropriate value. See above how to
determine it.
Part of SSPUX410_033.
Id = HSLco37210
OmniBack II ignores the following caution in the SAP
specification:
"Caution:By restoring raw partition to a different
one, the <dest_dir> means directly the new raw
partition, not the directory containing the special
file."
Resolution:
Destination directory forming procedure is changed.
Id = HSLco37773
Some parts of structures for query are allocated but
not released.
Resolution:
All allocated structures are released.
Id = HSLco37783
By design, whenever there are no objects backed up,
OmniBack II ends session as failed.
Resolution:
Two new global variables have been introduced:
a) SessSucessfullWhenNoObjectsBackedUp=0
By setting this variable to 1 user can change the
OmniBack II behavior in order to end the session as
successful when there are no objects backed up.
b) TreatScriptReturnAsNormal=<script return>
By setting this variable to a certain number instructs
OmniBack II to treat all the script returns equal to
the specified number as normal.
Id = HSLco39552
'brbackup' and 'brarchive' are called with wrong
parameters.
Resolution:
Parameters for 'brarchive' and 'brbackup' calls are
corrected.
Part of SSPUX410_050.
PHSS_27453:
Id = HSLco35628
Incorrect function is used for raw partition restore.
Resolution:
Raw partition restore uses proper function.
Part of SSPUX410_027.
Id = HSLco35646
Abort mechanism is implemented incorrectly.
Resolution:
Sapback aborts all the objects upon abort request from
OmniBack II user.
Id = JAGae25124
Session log files contains improper information when
SAP backup fails.
Resolution:
Log files contain proper information.
Part of SSPUX410_023.
Id = HSLco35966
Connection string in printed in plain text format.
Resolution:
Connection string is encrypted before it is passed
to GUI.
Part of SSPUX410_025.
PHSS_26888:
Id = HSLco33261
brbackup/brarchive is always started with "-u" option
which displays logon information.
Resolution:
brbackup/brarchive options are passed in a file.
Part of SSPUX410_014.
Id = HSLco33795 SR: H555007605
OmniBack II SAP integration is not supported on
Compaq Tru64 operating system.
Resolution:
OmniBack II SAP integration is supported on
Compaq Tru64 operating system.
Enhancement:
No (superseded patches contained enhancements)
PHSS_26888:
General release patch PHSS_26887/PHSS_26888
introduces OmniBack II 4.10 SAP integration on
Compaq Tru64 operating system.
Before installing OmniBack's SAP agent on
Compaq Tru64 client make sure that Core patch
patch PHSS_26349/PHSS_26350 (or later) is
installed on Installation server system.
SR:
H555009971 H555009941 H555009563 H555008908 H555009439
8606207021 H555008621 H555008812 H555008642 H555008643
H555008906 H555008807 H555008480 8606244527 8606260802
H555008483 H555008565 H555007605 H555007380
Patch Files:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/sap/gpl/i386/linux-60/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.10/
packet.Z
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
require.dat
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
packet.Z
what(1) Output:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/omni/databases/vendor/sap/gpl/i386/linux-60/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-1020/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/hp/s800/hp-ux-11/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/ibm/rs6000/aix-42/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/sun/sparc/solaris-26/A.04.10/
packet.Z:
None
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
require.dat:
None
/opt/omni/databases/vendor/sap/dec/alpha/osf1-4/A.04.10/
packet.Z:
None
cksum(1) Output:
OMNIBACK-II.OMNI-SAP-P,fr=A.04.10,fa=HP-UX_B.11.00_32/64,
v=HP:
2964783613 966776 /opt/omni/databases/vendor/sap/gpl/i386/
linux-60/A.04.10/packet.Z
33902731 1329979 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-1020/A.04.10/packet.Z
4249096554 1322505 /opt/omni/databases/vendor/sap/hp/s800/
hp-ux-11/A.04.10/packet.Z
3393402820 1188666 /opt/omni/databases/vendor/sap/ibm/
rs6000/aix-42/A.04.10/packet.Z
3871788517 1239699 /opt/omni/databases/vendor/sap/sun/sparc/
solaris-26/A.04.10/packet.Z
1650591381 18 /opt/omni/databases/vendor/sap/dec/alpha/
osf1-4/A.04.10/require.dat
3610240235 1872690 /opt/omni/databases/vendor/sap/dec/alpha/
osf1-4/A.04.10/packet.Z
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
If any newer SSP for the SAP is installed
on your system, you must re-apply the SSP after
installing this SAP patch.
PHSS_28332:
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28332 (or later) is required for this defect fix.
PHSS_28233:
Release Date: Available
Id = HSLco37193 SR:H555008807
Bad catalog access message is displayed without PHSS_28233
(or later).
PHSS_28342:
Release Date: Available
Id = HSLco37193 SR:H555008807
PHSS_28342 (or later) is required for this defect fix.
PHSS_27603:
Release Date: Available
Id = HSLco37193 SR:H555008807
Id = HSLco37783 SR:H555008908
PHSS_27603 (or later) is required for these defect fixes.
PHSS_27457:
Release Date: Available
Id = HSLco33795 SR: H555007605
PHSS_27457 (or later) is required for this enhancement.
Supersedes:
PHSS_28344 PHSS_27453 PHSS_26888
Equivalent Patches:
PHSS_28723:
s700: 10.20
s800: 10.20
Patch Package Size: 7770 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_28724
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28724.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28724. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28724.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28724.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28724.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28724:
NOTE!
This Patch has to be installed on the Installation
Server host.
The OB2 SAP agent must be redistributed to the SAP
client system(s) after the installation of the patch
in order to get the fixes into effect.
For distribution of the SAP agent, refer to
the OmniBackII Installation guide.
Patch includes the following Site Specific Patches:
SSPUX410_014
SSPUX410_023
SSPUX410_025
SSPUX410_027
SSPUX410_033
SSPUX410_036
SSPUX410_050
SSPUX410_064
SSPUX410_067
-----End of Document ID: PHSS_28724------------------------------------------
Document ID: PHSS_28579
Date Loaded: 20030404
Title: s700_800 11.X OV OB3.50 patch - SSEA packet
Patch Name: PHSS_28579
Patch Description: s700_800 11.X OV OB3.50 patch - SSEA packet
Creation Date: 03/03/24
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.00 11.11 11.20
s800: 11.00 11.11 11.20
Products:
OmniBackII A.03.50
Filesets:
OMNIBACK-II.OMNI-SSEA-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_28579
Symptoms:
PHSS_28579:
Id = HSLco37090 SR:H555008776
SSEA LVM BC backup fails with:
"[Critical] From: SSEA<hostname> "" Time:<time>
Command "/usr/bin/raidscan -p <port>"
failed with exit code 238.
For details check the following log directories:
Log file directory in operation:
/var/opt/omni/log/<session_ID>/curlog<num>Log
file directory for automatic storing:
/var/opt/omni/log/<session_ID>/tmp<num>"
Id = HSLco37449 SR:H555008860
When resolving ssea reports all of its data for every
single object to be backed up.
Id = HSLco40537 SR:H555009863
When backing up very large SAP databases with SSEA
split mirror, backups can fail with error:
"BR280I Time stamp <time>
BR296I Split of mirror disks successful
BR274E File /<sapdata_path>/system.data1 not found"
PHSS_27592:
Id = HSLco32398 SR:H555007043
When there is a firewall between the application and
the backup host, the split mirror backup fails.
Id = HSLco32470 SR:H555007071
Resolving performance is poor.
Id = HSLco33214 SR:H555007361
SSEA backup fails with:
"[Major] From: SSEA<hostname> "" Time: <time>
[224:106] Resolving of object <object_path> has
failed. (Search for backup logical volume failed.)"
Id = HSLco35074 SR:H555008259
SSEA backup fails with:
"[Critical] From: SSEA<hostname> "" Time:<time>
Failed to get pair for LDEV <ldev#> in RAID <seq#>.
(Details unknown.)"
Id = HSLco36105 SR:H555008599
SSEA backup fails with:
"[Critical] From: SSEA<host> <mailto:SSEA<host>
"" Time:<time>
Command "/usr/bin/pairdisplay -g" failed with exit
code 242."
Id = HSLco36476 SR:H555008656
SSEA backup fails with:
"[Major] From: SSEA<hostname> "" Time:<time>
[224:106] Resolving of object <object_name> has
failed. (Search for backup logical volume failed.)"
Id = HSLco36975 SR:H555008750
The SSEA SMB session on the backup host abnormally ends
when trying to activate backup volume group after the
paired LDEVs have been split.
PHSS_26216:
Id = HSLco32218 SR: H555006986
Horc instance number is not configurable.
Id = HSLco32253 SR: H555006993
SSEA agent reports disks in SIMPLEX state although
they are in PAIR state in HORCM.
Id = HSLco32264 SR: H555006994
OmniBack II SSEA Integration does not work with
logical devices with XP LUN number greater than 128.
Id = HSLco32274 SR: H555006996
Performance of SSEA integration drastically decreases
after the installation of PHSS_25817/PHSS_25818.
PHSS_25818:
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_24426:
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_22437:
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_28579:
Id = HSLco37090
If the LVM mirroring is done between two XP boxes with
the BC configuration on the second XP box and the BC
license present only on the second XP box, the raidscan
command fails on the first XP box causing the session
to fail.
Resolution:
BC license on the first XP is not needed. When
executing the raidscan command, the SSEA session does
not fail if the raidscan command fails, but just marks
the rdsks and LDEVs from the first XP box with an
error. The marked rdsks and LDEVs are skipped later in
the session.
Id = HSLco37449
Extensive reporting is only needed in case of errors,
so reporting data for every object can mean a lot of
unwanted information, especially in big environments.
Resolution:
New environment variable is introduced:
SSEA_RESOLVING_DISPLAY. Its default value is 1. Set
it to 0 if you want to switch off extensive object
data reporting.
Id = HSLco40537
In split mirror environment with very large SAP
databases, it can happen that the size of the message
buffer that OmniBack II uses is too small to fit in
for the complete list of SAP files to be backed up.
Resolution:
New environment variable is introduced: OB2IPCBUFSIZE.
In order to solve this problem, the buffer size can
be increased by setting the OB2IPCBUFSIZE environment
variable in the .omnirc file on CM, R1 and R2 hosts,
specifying the desired amount of memory to be used
for the buffer.
Please read the following instructions and make sure
that the patches listed in "Other Dependencies" section
(see below) are installed and the environment
variable is set on Cell Server, R1 and R2 systems before
running the backup!
How to determine the buffer size?
---------------------------------
N_obj: number of objects (files)
N_fs: number of file systems
N_lvmvg: number of volume groups
N_dg: number of disk groups
N_rdsk: number of rawdisks
Obj: Object Name
ObjBack: Object Backup Name
MntPathLen: Path name on backup (R2) host
(example: /var/opt/omni/tmp/App_host)
fsmnt: File System Mount Point
fsdev: File System Device File
(example: /dev/dsk/[c0t1d1,lvol1])
vg: Volume group
(ex: /dev/vg01)
dg: Disk group (VxVM) - dependence on mapfile
which is required for creating disk group
(example:/dev/vx/dsk/dg01)
rdsk: Raw disk file name
(example: /dev/rdsk/c1t1d1)
AvgLen_<xxx> average length of <xxx>
There are two different buffers used:
1. BSM <-> R1
2. R1 <-> R2
Calculating the BSM <-> R1 buffer size
--------------------------------------
MsgSize_BSM_R1 = N_obj * (AvgLen_Obj + 1 + MntPathLen)
Calculating the R1 <-> R2 buffer size
-------------------------------------
MsgSize_R1_R2 =
N_obj*(AvgLen_Obj+1+AvgLen_ObjBack) +
N_fs*(AvgLen_fsmnt*2 + MntPathLen + AvgLen_fsdev*2)+
N_lvmvg*(AvgLen_vg*2) + N_dg*(AvgLen_dg*2) +
N_rdsk*(AvgLen_rdsk*2)
Calculating the OB2IPCBUFSIZE value
-----------------------------------
OB2IPCBUFSIZE > max (MsgSize_BSM_R1, MsgSize_R1_R2)
RESTORE NOTE:
-------------
If restore is started using the sapbda utility,
the variable OB2IPCBUFSIZE must be exported to
environment prior to starting sapbda.
Part of SSPUX350_088.
PHSS_27592:
Id = HSLco32398
OmniBack II selects by random the port to use and than
checks if it is free. When there is a firewall between
the application and the backup host, not all the ports
can be used, but just those in a specified range.
Resolution:
Two environment variables are added to set the port
range in .omnirc file that can be used by OmniBack II:
SSEA_RM_PORT_LOW
SSEA_RM_PORT_HIGH
Id = HSLco32470
In the resolving phase SSEA executes two ioscan
commands in the SseXIoScanRdsk and ScsiIquiry
functions. Since these two functions are called
several times the resolving performance decreases,
especially in big environments.
Resolution:
SSEA executes just one ioscan command in the
SseXIoScanRdsk and ScsiIquiry functions. The ioscan
output is cached into a buffer and parsed for
information twice.
Id = HSLco33214
In case of non-XP rdsk, SSEA can not find the volume
group belonging to this rdsk and resolving can not
be done.
Resolution:
SSEA finds and checks all the rdsks belonging to an LDEV
on the R2 side. Than it uses only those rdsks which are
included in a volume group, in this way skips the non-XP
rdsks.
Id = HSLco35074
When there are more than one smb sessions running
simultaneously, horcm instances could be attached to
the same command device.
Resolution:
SSEA retries the getldev() call for 10 times. The
timeout before calling the getldev() API again is
randomly set. From now on SSEA tries to attach up
to 5 command devices if necessary.
Id = HSLco36105
A time out occurs on remote communication, and HORC
manager fails to re-execute.
Resolution:
A new environment variable SSEA_RM_TIMEOUT is
introduced. Its default value is 6000 milliseconds.
Id = HSLco36476
When mapping the LDEVs to the appropriate rdsks,
rdsks statuses are not correctly updated.
Resolution:
Mapping is done correctly.
Part of SSPUX350_083.
Id = HSLco36975
When the LDEVs belonging to a volume group are in PAIR
status and the SSEA smb session is started on some of
these LDEVs, the vgchange command on this volume group
takes a long time. After splitting the disks on on the
R2 side, the LDEVs included in the SMB session are in
PSUS state, the rest of the LDEVs are still in PAIR
state and vgchange command can not proceed, which
causes the session to ends abnormally.
Resolution:
If the SMB_SPLIT_ENTIRE_VG environment variable is set
to 1 in the .omnirc file on both hosts, then all the
LDEV pairs included in the backup volume group are
synchronized and split.
Part of SSPUX350_084.
PHSS_26216:
Id = HSLco32218
Horc instance number is not configurable.
Resolution:
Horc instance number can be configured using new
environment variables, SSEA_RMINST_LOW and
SSEA_RMINST_HIGH. When set in ${OMNI_HOME}/.omnirc
file, these variables set instance number range. Default
values for SSEA_RMINST_LOW and SSEA_RMINST_HIGH
are 50 and 80, respectively.
Part of SSPUX350_070.
Id = HSLco32253
Incorrect comparison of the strings causes incorrect
state of the disks reported.
Resolution:
SSEA agent properly reports disk state.
Id = HSLco32264
SSEA agent creates invalid configuration files for
logical devices exported to LUN's above 128.
Resolution:
New environment variable is introduced: SSEA_XP_PORTS.
Setting the variable to the value "FC" in
${OMNI_HOME}/.omnirc file enables OmniBack II SSEA
Integration to work properly with logical devices
exported to XP LUN's greater than 128.
Id = HSLco32274
Multiple ioscan calls when extracting needed data
cause bad performance.
Resolution:
Scripts for obtaining data needed by OmniBack II SSEA
Integration are improved.
PHSS_25818:
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_24426:
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.
PHSS_22437:
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 sessions 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.
Enhancement:
No (superseded patches contained enhancements)
PHSS_27592:
OmniBack II A.03.50 (PHSS_24425) supports LVM
Mirror (XP Campus Cluster). More information
about configuring LVM Mirror can be found in:
/opt/omni/bin/utilns/CampusClusterConf.txt
/opt/omni/bin/utilns/SureStoreAdmin.pdf.
OmniBack II A.03.50 (PHSS_22914) supports HP
SureStoreE Disk Array XP integration (SSEA)
on Sun Solaris. Installation is described in:
/opt/omni/bin/utilns/surestore_sun.pdf.
SR:
H555009863 H555008776 H555008860 H555008656 B554000692
H555007043 H555008599 H555007071 B554000869 B554000879
H555007361 H555008750 H555008259 H555006993 H555006994
H555006986 H555006996 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:
OMNIBACK-II.OMNI-SSEA-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/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:
OMNIBACK-II.OMNI-SSEA-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
/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:
OMNIBACK-II.OMNI-SSEA-P,fr=A.03.50,fa=HP-UX_B.11.00_32/64,
v=HP:
1343273602 2050307 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-1020/A.03.50/packet.Z
3097561959 2059081 /opt/omni/databases/vendor/ssea/hp/s800/
hp-ux-11/A.03.50/packet.Z
3903783657 1550093 /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:
If any newer SSP for the SSEA is installed
on your system, you must re-apply the SSP after
installing this SSEA patch.
PHSS_28728:
Release date: Late April
Id = HSLco40537 SR:H555009863
PHSS_28728 is required for this defect fix.
PHSS_28726:
Release date: Late April
Id = HSLco40537 SR:H555009863
PHSS_28726 is required for this defect fix.
PHSS_28571:
Release date: Available
Id = HSLco40537 SR:H555009863
Bad catalog access message is displayed without PHSS_28571.
PHSS_28018:
Release Date: Available
Id = HSLco40537 SR:H555009863
PHSS_28018 is required for this defect fix.
Supersedes:
PHSS_27592 PHSS_26216 PHSS_25818 PHSS_24426 PHSS_22437
Equivalent Patches:
PHSS_28578:
s700: 10.00 10.01 10.10 10.20
s800: 10.00 10.01 10.10 10.20
Patch Package Size: 5580 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_28579
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_28579.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_28579. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_28579.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_28579.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_28579.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
PHSS_28579:
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.
Patch includes the following Site Specific Patches:
SSPUX350_007
SSPUX350_016
SSPUX350_032
SSPUX350_037
SSPUX350_057
SSPUX350_070
SSPUX350_083
SSPUX350_084
SSPUX350_088
-----End of Document ID: PHSS_28579------------------------------------------
Document ID: PHNE_28882
Date Loaded: 20030404
Title: s700_800 11.04 (VVOS) ONC/NFS General Release/Perf Patch
Patch Name: PHNE_28882
Patch Description: s700_800 11.04 (VVOS) ONC/NFS General Release/Perf Patch
Creation Date: 03/03/20
Post Date: 03/04/04
Hardware Platforms - OS Releases:
s700: 11.04
s800: 11.04
Products: N/A
Filesets:
NFS.NFS-CLIENT,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
NFS.NFS-CORE,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
NFS.NFS-SHLIBS,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
NFS.NFS-64SLIB,fr=B.11.04,fa=HP-UX_B.11.04_32/64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHNE_28882
Symptoms:
PHNE_28882:
CDE fails to start after performing a fresh install of
VVOS 11.04 and the Extension Software CD version B.11.04.03.
PHNE_25937:
rpcbind(1) fails during system startup
initialization, causing CDE to hang during
system login.
PHNE_25077:
Ported portions of HP-UX patch PHNE_24034 to VVOS
NOTE: Portions of this patch have been ported to
satisfy dependencies for rpcbind(1). VVOS does not
support NFS client or server.
NOTE: Only JAG and DTS numbers related to
NFS.NFS-CORE apply to this patch.
NOTE: Only documentation references to NFS.NFS-CORE
portions of this patch apply to VVOS.
Based on HP-UX patch PHNE_24034:
automountd
SR: 8606152534
DTS: JAGad21864
AutoFS can mishandle unmounts when a server is down,
which may appear as bdf command anomalies.
automountd
SR: 8606196567
DTS: JAGad65770
AutoFS cannot unmount a cachefs type file system.
automountd
SR: 8606160777
DTS: JAGad30096
AutoFS cannot unmount hfs or cdrom file system types.
libautofs.a
SR: 8606176017
DTS: JAGad45257
AutoFS directories are empty under heavy NFS load.
libautofs.a
SR: 8606193515
DTS: JAGad62727
Duplicate entries for direct AutoFS mounts show up in
the /etc/mnttab file.
libnfs.a
SR: 8606197003
DTS: JAGad66201
Walk through large size buffer cache causes file access
performance degradation.
libnfs.a
SR: 8606203242
DTS: JAGad72416
A process sequentially reading a large file across an
NFS mount runs extremely slow if, at the same time,
there is another process sequentially writing a large
file to an NFS mounted directory, and one or more biods
are running on the system.
libnfs.a
SR: 8606146332
DTS: JAGad15675
The I/O throughput on a locked file is low compared to
the throughput on an unlocked file.
libnsl.1/a
SR: 8606207461
DTS: JAGad76637
rpcbind crashes with signal 10, Bus error (SIGBUS).
librpc.a
SR: 8606197306
DTS: JAGad66499
An NFS client becomes hung while performing many lock
operations on files in NFS mounted directories. It
also receives "bindresvport: loop_twice port assigned
512" messages in the message buffer.
librpc.a
SR: 8606168123
DTS: JAGad37405
An NFS/TCP client operation receives "NFS server not
responding still trying" messages while attempting to
access the server, even though the server system is up.
In this case, NFS/TCP on the server shows many TCP
connections for local address port 2049 in a CLOSE_WAIT
state when performing a "netstat -an" command.
nfs.client
SR: 8606181688
DTS: JAGad50904
On a system with active lofs mounts managed by AutoFS,
the "/sbin/shutdown" command may hang when the file
systems are unmounted.
nis.client, ypbind, ypinit, ypinit.1m, ypserv.1m
SR: 8606201620
DTS: JAGad70794
On SUN's NIS clients, it is possible to specify a list
of available NIS Servers for a given domain. HP's NIS
clients do not provide this functionality.
rpc.lockd
SR: 8606184904
DTS: JAGad54106
rpc.lockd can cause a user process to hang, if a
loopback mount is specified with an alias hostname.
rpc.lockd
SR: 8606202370
DTS: JAGad71544
NFS locks remain when killing NFS loopback mounted
client applications.
rpc.statd
SR: 8606208446
DTS: JAGad77633
NFS file lock recovery fails because rpc.statd matches
the wrong hostname.
rpcbind
SR: 8606164889 8606173448
DTS: JAGad34186 JAGad42706
rpcbind core dumps with SIGBUS or SIGSERV.
Based on HP-UX patch PHNE_23833:
automount
SR: 8606175862
DTS: JAGad45102
Mount points of automounter directories are not
visible when executing the "ls" command.
automount
SR: 8606169011
DTS: JAGad38290
The automount process hangs, making automounter
mount points inaccessable.
automountd
SR: 8606160596
DTS: JAGad29916
The /var/adm/automount.log file fills up the /var
file system.
exportfs
SR: 8606171662
DTS: JAGad40926
exportfs sometimes does not work correctly when
invalid host names are present in a host list
in the /etc/exports file.
fsirand.1m
SR: 1653311530
DTS: JAGab46804
Unable to use fsirand() on JFS file system.
libnfs.a
SR: 8606178998
DTS: JAGad48223
Unnecessary NFS read before write is causing severe
decreases in write performance.
libnfs.a
SR: 8606165859
DTS: JAGad35150
Data page fault panic while copying a file using
NFS V3 between an HP-UX client and an NT InterDrive
server where the target filesystem is full.
libnfs.a
SR: 8606178618
DTS: JAGad47845
The rename() system call always fails when trying
to rename a directory in a cachefs-mounted file
system, if the target directory name exists.
'errno' gets set to EPERM ("Not Owner").
libnfs.a
SR: 8606175781
DTS: JAGad45021
The 'du' output is eight times higher over NFS
with an HP server / Sun Client configuration when
compared to an HP server / HP Client configuration.
libnsl.1/a
SR: 8606183171
DTS: JAGad52387
UDP packets sent by remote users can cause RPC
applications to abort.
libnsl.1/a
SR: 8606186548
DTS: JAGad55752
RPC server running in TCP multithreading
mode develops a file descriptor leak when
clients are on same machine as the server.
Eventually the server fails to process
clients' requests when the process limit
is attained.
libnss_nis.1
SR: 8606179951
DTS: JAGad49173
getservbyname() using NIS returns NULL when
trying to resolve service aliases.
libnss_nisplus.1
SR: 8606172747
DTS: JAGad42007
Changing an NIS+ user's password with nispasswd() or
passwd() while the system is in trusted mode without
specifying the dot "." notation (non fully qualified
domain) results in an incorrect sub-domain being
created.
nfsstat.1m
SR: 8606173363
DTS: JAGad42623
The "man nfsstat" command does not display all of the
statistical data fields.
rpc.lockd
SR: 8606180764 8606180765
DTS: JAGad49985 JAGad49986
rpc.lockd causes user process to hang.
rpc.lockd
SR: 8606174017
DTS: JAGad43270
rpc.lockd drops the lock request from same process
for a different file.
rpc.lockd
SR: 8606185238
DTS: JAGad54440
Partial record unlocking in NFS does not work
properly.
rpc.lockd
SR: 8606179200
DTS: JAGad48424
rpc.lockd core dumps when user process is
interrupted with "control-c".
rpc.mountd
SR: 8606176384
DTS: JAGad45622
The boot process of a Linux client fails due to
rpc.mountd not allowing AUTH_NULL authentication.
ypxfr
SR: 8606164133
DTS: JAGad33433
The ypxfr command fails with the error message:
"ypxfr: bind_to_server clntudp_create error:
RPC unknown host".
Based on HP-UX patch PHNE_23249:
libautofs.a, libnfs.a, librpc.a
SR: 8606103740 8606159451
DTS: JAGab70789 JAGad28779
A multithreaded process can hang when performing NFS
file operations and concurrently writing core, forking,
performing debugger attachment or undergoing job
control.
Based on HP-UX patch PHNE_23247:
{Site Specific Patch}
Based on HP-UX patch PHNE_22642:
automount
SR: 8606155592
DTS: JAGad24909
Automount (automounter) coredumps when sent SIGUSR1
to force it to update the automaps.
automountd
SR: 8606160808
DTS: JAGad30127
When using AutoFS, NFS mount points do not enforce
quotas.
libautofs.a
SR: 8606135856
DTS: JAGad04988
Panic occurs when trying to umount a ufs filesystem
which is still in the process of mounting.
libautofs.a
SR: 8606159736
DTS: JAGad29062
Unexpected delay in unmounting of Autofs mounts.
libnfs.a
SR: 8606179269
DTS: JAGad48493
Poor NFS pv3 performance on 64-bit (V-class) on 11.0.
libnfs.a
SR: 8606161701
DTS: JAGad31017
When reopening an NFS file right after closing it,
file attribute related inconsistencies can occur.
libnfs.a
SR: 8606158230
DTS: JAGad27560
Unmount of an nfs file system causes a panic.
libnfs.a
SR: 8606163247
DTS: JAGad32551
Unable to remove an NFS tmp file, .nfsXXXX after
failing to create or write a file which has exceeded
the disk quota limit.
libnfs.a
SR: 8606166314
DTS: JAGad35601
Process using NFS can not be killed or stopped by
sending the process a signal (SIGKILL or SIGSTOP).
libnsl.1/a
SR: 8606140609
DTS: JAGad09968
Core dump occurs when user belongs to more than
16 groups.
libnsl.1/a
SR: 8606160400
DTS: JAGad29722
On installing PHSS_20014 and PHSS_21947, 100% CPU
is used up by 2 processes - opcmsgrd and opcdistm.
librpc.a
SR: 8606169796
DTS: JAGad39062
Data page fault panic due to bad machine name
length in NFS request.
librpc.a,nfsd
SR: 8606167053
DTS: JAGad36339
An NFS/TCP client operation receives "NFS server
not responding still trying" messages while
attempting to access the server even though the
server system is up. In this case, NFS/TCP on
the server has become inoperable due to a hang.
newkey
SR: 8606157592
DTS: JAGad26923
Newkey does not recognize the root password of the
remote machine and returns an error, "ERROR,
passwd differs from login passwd".
Based on HP-UX patch PHNE_22125:
libautofs.a
SR: 8606143877
DTS: JAGad13210
Using autofs, mount points become inaccessible
after a series of mount/unmount cycles.
libnfs.a
SR: 8606128739
DTS: JAGac86286
File corruption over NFS when NFS file server is
TOC'ed.
libnfs.a
SR: 8606144881
DTS: JAGad14221
HP NFS client performance is degraded as shown by
"nfsstat -c", it makes unnecessary GETATTR calls
for each read or write on files opened with
synchronous I/O flags set; and synchronous I/O
mode remains in effect for subsequent opens on an
NFS file opened once with synchronous I/O flags
set.
libnfs.a
SR: 8606147198
DTS: JAGad16541
CPU time is wasted by unnecessary calls to
compare_cred function in NFS PV3 client code.
libnfs.a
SR: 8606145970
DTS: JAGad15306
The stat() system call on NFS directories
shows a non-existent ACL.
libnfs.a
SR: 8606128493
DTS: JAGac84458
System panic when running "du -s" or
"find -name" on a 64 bit machine.
libnfs.a, librpc.a
SR: 8606160097
DTS: JAGad29423
Mount an NFS file system with non-interruptible
options remains interruptible.
libnfs.a
SR: 8606144617
DTS: JAGad13957
Using NFS, a read-only file open by one
process causes a "Permission denied"
error in an on-going write operation on
the same file by another process.
libnfs.a, librpc.a, nfsd
SR: 8606145517
DTS: JAGad14853
If NFS is stopped and restarted, the nfsd
processes do not get re-registered with rpcbind,
and rpcinfo commands fail.
libnfs.a, nfsd
SR: 8606146885
DTS: JAGad16228
nfsd unregisters a running nfsd process on
startup.
librpc.a
SR: 8606155004
DTS: JAGad24321
When a server is down, an NFS/TCP client process
e.g. a bdf command can hang.
librpc.a
SR: 8606143872
DTS: JAGad13205
NFS/TCP mounting and unmounting eventually hangs.
librpc.a
SR: 8606144478
DTS: JAGad13818
NFS/TCP connections are not torn down when the
peer sends a FIN.
nfs.core
SR: 8606159847
DTS: JAGad29173
File permission change on /etc/services file.
rpc.lockd
SR: 8606145476
DTS: JAGad14812
Lockd/statd client crash recovery does not work.
rpc.mountd
SR: 8606127276
DTS: JAGac68822
A failing mount request may return a wrong error
code.
rpc.statd
SR: 8606143409
DTS: JAGad12739
A looping problem in rpc.statd occurs between the
server and SGI clients.
ypserv
SR: 8606155843
DTS: JAGad25155
YPSERV fails to return all groups for id/group
command when concurrent access is allowed to maps.
Based on HP-UX patch PHNE_21376:
automountd
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
exportfs
SR: 8606108804
DTS: JAGab78579
When a user attempts to mount an exported
filesystem which is a symbolic link to an
actual directory or filesystem on an NFS
server, a "Permission Denied" error occurs.
This occurs after installing patch PHNE_18221.
libautofs.a
SR: 8606128485
DTS: JAGac84450
Automountd not triggered for mounts
anymore when autonode has NULL flag.
libnsl.1/a
SR: 8606134593
DTS: JAGad03728
automountd coredumps in the NIS+ environment.
libnsl.1/a
SR: 8606143750
DTS: JAGad13073
When using the TCP loopback transport a
memory leak may occur.
libnsl.1/a, rpc.nisd
SR: 8606107751
DTS: JAGab78042
When using NIS+ with TCP, as the number of open
file descriptors increases, file table overflow
errors occur in the syslog.log file and user
information is not recognized.
rpc.lockd
SR: 8606131496
DTS: JAGad00646
Failover occurs with the serviceguard NFS package because
the rpc.lockd daemon fails (terminates) during periods of
high memory usage (running out of memory).
rpc.statd
SR: 8606131366
DTS: JAGad00517
The rpc.statd daemon core dumps during high memory
utilization (when available memory runs low).
rpc.statd
SR: 8606136063
DTS: JAGad05198
rpc.statd aborted with memory leak due to unresolved
host requests.
rpcbind
SR: 8606131978
DTS: JAGad01128
Rpcbind exhibits wrong behavior on shutdown.
ypserv
SR: 8606134296
DTS: JAGad03431
ypserv becomes unavailable for the local ypbind and
for the other yp clients.
Based on HP-UX patch PHNE_20627:
libnfs.a
SR: 8606134214
DTS: JAGad03354
Extremely slow performance of commands or utilities
operating on large directories over NFS.
SR:8606109663
DTS:JAGab82363
Removing an NFS file causes a file named ".nfsXXXX"
(where XXXX is a pid) to be created.
SR:8606135799
DTS:JAGad04931
The i-node for the ".." directory entry of a subdirectory
is not updated on an NFS client after that subdirectory
is moved up one directory level on the NFS client,
ie - moved to "..".
SR:8606135800
DTS:JAGad04932
Output from "tail -f" on an NFS file does not reflect any
appends made to the file on the NFS server if a "umount"
is performed on the NFS file system while the "tail -f"
is being executed.
Based on HP-UX patch PHNE_20371:
autofs/mount
SR: none
DTS: JAGab68200
Autofs/mount can fail when the system
hostname is longer than 8 characters.
automount
SR: none
DTS: JAGab68200
Autofs/automount can fail when the system
hostname is longer than 8 characters.
automount,automountd
SR: 8606106692
DTS: JAGab76019
automount with stalemounts causing duplicate
mnttab entries & lock problems.
symptoms of automount are: stale nfs handles are
seen in mnttab after an unmount and when the
mount is repeated (in this case a cdrom...) the
mnttab contains two entries for the device. One
of which is invalid. This second (stale) handle
causes subsequent locking problems.
automountd
SR: none
DTS: JAGab68200
Autofs/automountd can fail when the system
hostname is longer than 8 characters.
automountd
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
automountd
SR: 8606107274
DTS: JAGab77060
automount option -proto=udp causes mounts to fail
libautofs.a
SR: 8606107122
DTS: JAGab76805
autofs - shell gets intermittent "cannot execute"
libautofs.a
SR: 8606106938
DTS: JAGab76453
automounter hangs when trying to mount cachefs
filesystem (reported on HP-UX 10.20)
libnsl.1/a
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
libnsl.1/a
SR: none
DTS: JAGab68200
NIS and other ONC/NFS systems can fail when
libnsl does not provide support for a system
hostname longer than 8 characters.
libnsl.1/a
SR: 8606107366
DTS: JAGab77563
Autofs exhibits wrong behavior in processing
executable maps.
libstraddr.1
SR: none
DTS: JAGab68200
Libstraddr routines can fail when the system
hostname is longer than 8 characters.
make.script
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
mount
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs.core
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nfs/mount
SR: none
DTS: JAGab68200
Nfs/mount can fail when the system
hostname is longer than 8 characters.
nfsstat
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
nisplus/nisserver
SR: none
DTS: JAGab68200
Nisplus can fail when the system hostname
is longer than 8 characters.
rpcinfo
SR: none
DTS: JAGab68200
Rpcinfo can fail when the system hostname
is longer than 8 characters.
rpc.lockd
SR: 5003459362
DTS: JAGab12595
file locks hang when NFS server uses
fully-qualified hostname
rpc.lockd
SR: 8606113678
DTS: JAGac07192
Application hangs on client when obtaining NFS
lock on server
setoncenv
SR: none
DTS: JAGaa43721
When accessing remote files over NFS, the
NFS protocol on HP-UX only uses UDP.
ypmake
SR: 8606107068
DTS: JAGab76707
ypmake and Makefile failed
on some mail.aliases file and mail.aliases map
is corrupted.
Based on HP-UX patch PHNE_20344:
libnfs.a librpc.a nfs_iface.o
SR:N/A
DTS:JAGac42842
NFS version 3 only supports up to 8k read/write
transfer size.
libnfs.a
SR:8606110199
DTS:JAGab82902
Memory leak in NFS version 3 at rfs3_readdirplus().
libnfs.a
SR: 8606125471
DTS: JAGac40861
Poor NFS performance relative to SPECsfs97 benchmark.
libnfs.a
SR:8606107676 8606124555
DTS:JAGab77944 JAGac39938
NFS performance problems with NFS client
readdir cache.
libnfs.a
SR:8606126860
DTS:JAGac59701
"do_readdirplus" variable not available in the NFS
kernel.
Based on HP-UX patch PHNE_19759:
1.fuser -f on a file does not return pid of opener
2.compress command on a SUN client fails due to invalid
name length returned by NFS pathconf from HP Server
3.getmount_entry() returns down status for all hard
mounted NFS file systems
Based on HP-UX patch PHNE_19620:
automountd
DTS: JAGab72053
NFS - autofs (11.0) hangs when unmount from down server
SR: 8606103364
DTS: JAGab70009
replicated automounts fail if system parameter
maxfiles > 2048
libautofs.a
DTS: JAGab73529
autofs w/cachefs can panic in cachefs_root()
SR: 8606105077
DTS: JAGab72920
AutoFS failure with cdrom.
The failure occurs in two ways:
- Hangs if indirect mount
- Error if direct mount
libnsl.1/a
SR: 8606104454
DTS: JAGab41115
rpcinfo gets error "can't contact rpcbind: RPC:
Program not registered" from remote rpcbind on
RPCB_GETADDR/RPCB_DUMP request for list of services.
libnss_nis.1
SR: 5003465898
DTS: JAGab20796
getservbyname() is slow.
librpcsvc.a
SR: 8606103503
DTS: JAGab70329
rpc.mountd dies with SIGSEGV if rmtab is large and
showmount -a is done.
rpc.lockd
SR: 8606105833
DTS: JAGab74177
Virtual nfs servers have locking problems.
DTS: JAGab45462
rpc.lockd uses port numbers within reserved port
range, 600 to 1024.
DTS: JAGab15223
Processes waiting to lock an nfs file which has been
deleted do not get woken up, resulting in a hang.
DTS: JAGaa45544
Locks hang and rpc.lockd logs error messages about
the local and remote lock tables being inconsistent.
rpc.lockd causes lock queue corruption with loopback
mounts.
rpc.mountd
DTS: JAGab45462
rpc.mountd uses port numbers within reserved port
range, 600 to 1024.
rpc.statd
DTS: JAGab45462
rpc.statd uses port numbers within reserved port
range, 600 to 1024.
Based on HP-UX patch PHNE_18221:
libautofs.a
SR: 1653298828 5003458299 1653299826 5003462911
SR: 1653304972
DTS: JAGab00144 JAGab03833 JAGab11283 JAGab16597
DTS: JAGab18083
JAGab00144 - AutoFS is not triggering re-mount
JAGab03833 - AutoFS hangs even with PHNE_17200
JAGab11283 - cp(1) fails to inactive direct mount
JAGab16597 - mv command fails in AutoFS direct mnt
JAGab18083 - getcwd() fails with AutoFS filesys
libnsl.1/a
SR: 5003463992
DTS: JAGab17512
Applications fail to create a server side RPC
endpoint due to a failure to obtain a reserved port.
libnsl.1/a
SR: 5003465880
DTS: JAGab20797
A multi-threaded application which calls
getservbyname() failed.
libnss_compat.1
SR: none
DTS: JAGab03573
64-bit application using 'getgrent' fails if
nsswitch.conf uses group:compat
rpc.lockd
SR: 5003446203
DTS: JAGaa46687
rpc.lockd runs out of file descriptors
and returns the following error in
its log file:
RPC: Remote system error
rpc.mountd
SR: 5003439471 5003463331
DTS: JAGaa42795 JAGab17386
ER for share(1M) options and defect in "showmount -e"
rpc.mountd
SR: none
DTS: JAGaa44896 JAGaa24142
rpc.mountd - server allows mounts not on access list
rpc.pcnfsd
SR: 5003460030
DTS: JAGab13451
rpc.pcnfsd does not accept '~' for
file names.
rpc.statd
SR: 5003446195
DTS: JAGaa46688
rpc.statd fails on fopen when more than
260 entries are in /var/statmon/sm.
Based on HP-UX patch PHNE_17586:
1. Huge directory reads take too long and client system
performance degrades as NFS IO activity increases.
2. System panics with data page fault when 0 len UDP
pkt received by NFS server system.
3. Root users are denied access to valid root exported
file systems on 11.0 server.
4. Root users on NFS PV3 client who do not have file
permissions for read/write are allowed to open file
successfully but denied access when reading or
writing the file.This behaviour is inconsistent
with non-root users who are denied access at file
open time.
5. NFS requests from anonymous NT clients are rejected.
6. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
7. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
8. Buffering of data on NFS file is permanently
turned off by the client system even after releasing
all file locks and closing all file descriptors.
9. Exportfs prints debug messages in syslog.log.
10. When a file is opened with O_CREAT|O_TRUNC|O_EXCL
flags set and the file does not already exist,open is
expected to succeed but for NFS V3 files,open seems to
fail with EACCES.
11. When file has Mandatory lock mode set,HP NFS V3
allows file read/write access when no locks exist on
the file,but NFS V2 denies file read/write access.
Also,NFS V3 client hangs application when locks exist
on the file.This behaviour is inconsistent with SUN's,
where NFS V3 and V2 access is denied consistently at
file open time when file has mandatory lock mode set.
12. Data page fault panic in mvfs due to NFS server
initialization corrupting global memory at boot up.
Based on HP-UX patch PHNE_17247:
1. Data page fault panic due to NFS server
initialization corrupting global memory at boot up.
2. Large file reads on a 32 bit NFS client does not work,
file copy completes without errors but no data is copied
to the target file.
3. When copying large file from local disk to NFS
file system,more bytes than necessary are copied to
the file and the resulting file size is bigger.
Based on HP-UX patch PHNE_17200:
Makefile
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
automount
SR: 5003450916
DTS: JAGaa93190
automount loops using replicated server
automount
SR: 5003362707
DTS: JAGaa25720
automount fails to mount all exported
file systems.
automountd
SR: 1653267377
DTS: JAGaa24193
autofs holding lock on /etc/.mnttab.lock.
automountd
SR: none
DTS: JAGaa95626
Logging information is hard to
read.
automountd
SR: none
DTS: JAGaa40567
executable map processing may grant
caller additional privileges.
libautofs.a
SR: 5003445601
DTS: JAGaa46003
NFS - autofs hangs when manual unmounts used
nfs.core
SR: none
DTS: JAGaa43075
rexd does not start since it cannot find
/var/spool/rexd on system.
nis.server
SR: none
DTS: JAGaa94166
nis.server script won't run correctly unless the
new namesvrs is installed at the same time.
rpc.mountd
SR: 5003454371
DTS: JAGaa94274
rpc.mountd deadlock with automount
rpc.mountd
SR: 5003447003
DTS: JAGaa45940
NFS - rpc.mountd MOUNT performance is very slow
rpc.nispasswdd
SR: 1653286955
DTS: JAGaa44956
when rpc.nispasswdd is running with "-g"
option, it corrupts the credential of a
user who has a credential and changes
password.
rpc.pcnfsd
SR: 5003405118 5003336198
DTS: JAGaa26176 JAGaa25473
1) PC users fail to authenticate when trusted
system is enabled.
2) pcnfsd stops responding to all requests when
a request is made to printer that is down.
rpc.pcnfsd
SR: 1653293043
DTS: JAGaa93189
User authentication fails for users who
do not use a shell that ends with "sh".
rpc.rstatd
SR: 5003442574
DTS: none
The amount of memory associated with the
rpc.rstatd process continues to grow
without ever being returned to the system.
rpc.statd
SR: 5003445858
DTS: JAGaa45938
rpc.statd core dumps with SIGSEGV.
rpcbind
SR: none
DTS: JAGaa92935
rpcb_unset() does not remove all registration
entries from rpcbind.
rpcgen
SR: none
DTS: JAGaa57297
rpcgen generated makefiles fail to build targets
rpcgen
SR: 1653291484 1653291500
DTS: JAGaa57208 JAGaa57209
rpcgen generated file fails to compile.
stdhosts
SR: none
DTS: JAGaa94167
stdhosts command fails on lines longer
than 256 char.
ypinit
SR: none
DTS: JAGaa41361
ypinit has warning message.
ypmake
SR: none
DTS: JAGaa73221
When rpc.mountd tries to match a hostname
in netgroup, the given hostname has to be
the exact same as it is stored in the
netgroup.
ypserv
SR: 5003448159
DTS: JAGaa46689
ypserv is running out of file descriptors
due to not releasing them.
ypserv
SR: none
DTS: JAGaa41159
ypserv core in svc_freeargs ( a rpc routine)
after nslookup for a period of time.
ypxfr_1perday
SR: none
DTS: JAGaa43641
vhe_list should not be in the script.
Based on HP-UX patch PHNE_17101:
autofs
SR: none
DTS: none
Autofs fails to start on a 64-bit OS
unless PHNE_15638 has already been
installed.
nfsstat
SR: 5003444745
DTS: JAGaa44646
nfsstat -m exited with an error that it
could not open the mount table
Based on HP-UX patch PHNE_16599:
1. NFS server system panics with assertion failure
in vn_rele sometimes during NFS file locking/unlocking.
2. Too much rnode memory allocated resulting in gradual
shortage of free memory resource on the system.
3. NFS Version 3 mounted directories may appear to be
empty on the NFS client even though the directories exist
on the server file system.
4. A touch command to change the modification time stamp
of NFS file may cause system hang.
5. Some NFS clients may experience poor NFS Read
performance with HP servers when using NFS Version 3 mounts.
6. Invalid file system id returned to Statfs of
NFS Version 2 mounted file set.
Based on HP-UX patch PHNE_16470:
Makefile
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
automount
SR: none
DTS: JAGaa26320, JAGaa26354
Made debug logging change and checked
in the change for setmntent for read locks.
automount
SR: none
DTS: JAGaa40906
automount tries to remount already mounted directory
automount
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
automountd
SR: 5003431353, 5003434654
DTS: none
1. duplicate entries in /etc/mnttab error
message in syslog
2. AutoFS will not unmount LOFS mounts
exportfs
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libautofs.a
SR: none
DTS: JAGaa24180
1. HOME env set to autofs directory on 64-bit 9808
system hangs gpm help.
2. Autofs hangs when running Netscape.
3. Autofs hangs when remounting hierarchical mounts.
libnsl.1/a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
libnsl.1/a
SR: 5003429845
DTS: INDaa31432
Compile of application using archived libraries
files with duplicate symbol __nss2herrno
libnsl.1/a
SR: 5003429456
DTS: INDaa31422
rpc.mountd stops running
libnsl.1/a
SR: none
DTS: JAGaa24798
CDE logins fail when user belongs to more then
16 groups.
libnsl.1/a
SR: none
DTS: INDaa30681
The performance of a 64-bit application
slows down when it uses the 32-bit cache
information in the ypbind file.
libnss_nisplus.1
SR: none
DTS: JAGaa40026
getxxxent leaks memory when using NIS+
libnss_nisplus.1
SR: 5003418210
DTS: JAGaa24152
Module ngetprpwent is missing
from libnss_nisplus.
librpcd_util.a
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
librpcsoc.1
SR: none
DTS: INDaa30814
on command fails with the messages
on: failed to reach <host> at address <host address>
mknetid
SR: none
DTS: INDaa30115
mknetid cores when a user is in more that 20 groups
namesvrs
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
nfs.client
SR: none
DTS: JAGaa27109
Non-busy NFS mounts are frequently not
unmounted during nfs.client stop.
nfs.server
SR: none
DTS: JAGaa24199
local file systems are mounted when NFS client restarts
nfs_umount
SR: none
DTS: JAGaa27067
/sbin/fs/nfs/umount -aF nfs does not unmount
all NFS file systems.
nfsstat
SR: none
DTS: INDaa31388
Executable hangs.
nis.server
SR: none
DTS: INDaa30072
nis.server script fails if IBM is NIS master to
HP slave.
on
SR: 5003420992
DTS: INDaa30864
on fails when home directory is mounted via
autofs.
rpc.lockd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.lockd
SR: none
DTS: JAGaa40591
Lock failure caused data corruption
rpc.lockd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.lockd
SR: 1653254474, 5003417998
DTS: JAGaa26354, JAGaa26221, JAGaa26257
The rpc.lockd tracing was improper format.
Loss of UDP NFS file locking packets resulted
in a growing message queue. rpc.lockd processes
control C (NLM_CANCEL) incorrectly when the server is
a SUN system.
rpc.mountd
SR: none
DTS: JAGaa24186
Believes there is a problem
in the way the daemon checks to see if it is up.
rpc.mountd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.mountd
SR: 1653266148
DTS: INDaa31024
valid clients in the NFS server's export list
can not mount the NFS server.
rpc.pcnfsd
SR: 1653272484
DTS: JAGaa26373
Validity checks not performed on printer and
system name.
rpc.rexd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rquotad
SR: none
DTS: INDaa31358
Executable hangs.
rpc.rstatd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.rusersd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.sprayd
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.statd
SR: none
DTS: JAGaa26538
logged messages causes file system to fill
rpc.statd
SR: 4701392027
DTS: JAGaa26354, JAGaa26276
The debug logging needs change.
rpc.walld
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
rpc.yppasswdd
SR: none
DTS: INDaa31524
If a password contains a ":", it cannot be changed
via NIS.
rpc.yppasswdd
SR: none
DTS: INDaa31380
rpc.yppasswdd does not update NIS maps when ptmp
and maps on diff file system.
rpcbind
SR: 1653270413
DTS: INDaa31358
logging data is difficult to read.
ypbind
SR: none
DTS: INDaa31412
ypbind cache file sometimes is not created
due to the value in an uninitialized time
stamp. The performance of NIS degrades
when cache file is absent.
ypbind
SR: none
DTS: INDaa31381
ypbind cache file cannot be created
due to a missing compilation flag.
The performance of NIS degrades
when cache file is absent.
ypinit
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa30982
vhe_list is no longer supported by NIS.
It needs to be removed from ypinit,
ypmake and /var/yp/Makefile.
ypmake
SR: none
DTS: INDaa31440
When a new map is made on the Master with
NOPUSH=1 option, on the Slave, transferring
the new map fails sometimes.
ypserv
SR: none
DTS: INDaa29252
ypserv stops answering some queries for
entries outside domain on a slow system.
ypxfr
SR: 5003418160
DTS: JAGaa24144
ypmake on the YP master reports a failure
when contacting a slave server
ypxfr
SR: none
DTS: none
Incorrect parameter declaration for the
function ypxfrd_getdbm.
Based on HP-UX patch PHNE_16017:
1. The setting of NFS file/directory modification and access
time stamps is inconsistent.
2. An HP NFS server does not permit NFS file/directory time
stamps to be set from a non-HP NFS client.
3. Copying a file from a 64-bit client causes the file
timestamp to be incorrectly set to Dec 31, 1969.
4. Poor NFS performance over 100BT.
Based on HP-UX patch PHNE_15638:
automountd:
1. No autofs support on HP-UX.
mount:
1. No autofs support on HP-UX.
umount:
1. No autofs support on HP-UX.
rup:
error exit code incorrect
libnsl:
rpcbind has memory leak
bindreserveport fails
rpc.statd:
gethostbyname called incorrectly.
rpc.lockd:
No support for shares and non-monitored locks in NLM
version 4
automount:
Messages written to syslog file without verbose option
nfs.client:
rpc.lockd does not reclaim locks after a server reboots.
Based on HP-UX patch PHNE_14919:
1. NFS write performance may be slow, and may be
particularly poor when large files are being closed or
synchronized.
2. NFS Server files may be accessed and possibly destroyed
when their permissions should not allow access.
3. NFS Remounts may fail with a "device busy" error.
4. Locking large files (> 2 GBytes) may encounter errors.
Based on HP-UX patch PHNE_14800:
NFS Performance as measured by the SPECsfs benchmark
gives an inadequate number of IOPS on the initial 11.0
system release.
Based on HP-UX patch PHNE_14772:
N/A
Based on HP-UX patch PHNE_14746:
rpcgen:
1. rpcgen displays an incorrect usage string
2. C++ applications fail to compile due to non-existent
header file. <sysent.h>
nfs.core:
1. rpcbind cannot receive messages on ticotsord device
rpc.nisd:
1. NISPLUS server can not resolve hostname using DNS for
NIS client.
(SR/DTS: 5003-395731/INDaa28803)
2. NIS+ clients sometimes get "NIS+ unreachable" message
when in fact NIS+ server(rpc.nisd) is up and running.
(SR/DTS: 5003-395558/INDaa29132)
nisaddent:
1. nisaddent adds empty passwd fields on a trusted system.
(DTS: INDaa28982)
nisserver:
1. nisserver creates unnecessary environment variables -
NIS_MASTER and NIS_SLAVE, and adds them into
/etc/rc.config.d/namesvrs file.
(SR/DTS: 5003-395582/INDaa29138)
2. nisserver script does not set up NIS+ server correctly
if
- NIS compat mode is not set, and if,
- nisserver was previously executed with NIS
compat mode set.
(SR/DTS: 5003-395582/INDaa29138)
nisclient:
1. nisclient has illegal grep syntax for hp
(DTS: INDaa28804)
2. nisclient -u script reports success even when
chkey fails
(SR/DTS: 5003-397422/INDaa29242)
nispopulate:
1. nispopulate has illegal grep syntax for hp
(DTS: INDaa28804)
libnss_nisplus.1:
1. 64-bit gethostbyname() returns 0.0.0.0 for the IP
address of a valid host stored in the NISPLUS table
hosts.org_dir.
(DTS: INDaa29686)
nisdefaults:
1. nisdefaults does not indicate if a principal is not
authenticated.
(SR/DTS: 5003-396655/INDaa29212)
nisstat:
1. nisstat -H hostname does not work.
(SR/DTS: 5003-395541/INDaa29137)
automount:
1. Old automount daemon conflicts with New automount
command
2. Automount daemon does not use NIS master map
rpc:
1. no entry for rpc.nisd_resolv
2. no entry for automountd
nfsconf:
1. No support for AutoFS
nfs.client:
1. No support for AutoFS
libstraddr.1:
1. 64-bit application can not send request on loopback
transport.
2. 64-bit library does not exist
libnsl.1:
1. Can not generate new thread after the 65th has been
created.
2. Can not create RPC MT Servers.
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit Cannot use loopback transports over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
libnsl.a:
1. Can not generate new thread after 65th has been
created
2. Can not create RPC MT Servers
3. netdir_getbyname() returns different error message
for non-existent hosts.
4. 64-bit application cannot use loopback transports
over RPC.
5. Can not create 64-bit RPC MT Servers.
6. 64-bit netdir_getbyname() returns different
error message for non-existent hosts.
vhe_altlog:
1. Obsoleted product vhe is still available.
vhe_getlist:
1. obsoleted product vhe is still available.
vhe_list:
1. obsoleted product vhe is still available.
vhe_mounter:
1. obsoleted product vhe is still available.
vhe_script:
1. obsoleted product vhe is still available.
config:
1. Loopback transport configuration files not moved
to correct location
unconfig:
1. Loopback transport files left after deinstall.
netconfig:
1. Customer configured information lost in /etc/netconfig
hosts:
1. Customer configured information lost in
/etc/net/[ticlts|ticots|ticotsord]/hosts
services:
1. Customer configured information lost in file
/etc/net/[ticlts|ticots|ticotsord]/services
rpc.rstatd:
1. When run from the command line, rpc.rstatd dies after 10
minutes.
keyserv:
1. keyserv registers a UDP port with rpcbind
nis_cachemgr:
1. nis_cachemgr registers a UDP port with rpcbind
(DTS: INDaa29627)
rpcbind:
1. Can not send request over loopback transport devices
to rpcbind
rpc.mountd:
rpc.mountd denies access to valid netgroup.
Based on HP-UX patch PHNE_14620:
1. System panics with a data memory protection fault
2. NFS unmounts may take several minutes with large
memory systems
Based on HP-UX patch PHNE_13208:
1.Processes hung when doing NFS file IO
2.NFS sub-system failed to respond under 2 way NFS IO stress
3.Sometimes returned invalid error during NFS Read/Write
Defect Description:
PHNE_28882:
CDE doesn't work after a fresh installation of VVOS 11.04
with the Extension Software CD version B.11.04.03. as
the preinstall script of the earlier patch PHNE_25937
is corrupting the /etc/netconfig file.
Resolution:
Modified preinstall script to update /etc/netconfig
properly.
PHNE_25937:
rpcbind(1) fails during system startup
initialization, causing CDE to hang during
system login.
PHNE_25077:
Ported portions of HP-UX patch PHNE_24034 to VVOS
NOTE: Portions of this patch have been ported to
satisfy dependencies for rpcbind(1). VVOS does not
support NFS client or server.
NOTE: Only JAG and DTS numbers related to
NFS.NFS-CORE apply to this patch.
NOTE: Only documentation references to NFS.NFS-CORE
portions of this patch apply to VVOS.
Based on HP-UX patch PHNE_24034:
automountd
JAGad21864
During unmount operations, automountd incorrectly
returns a success error code to the kernel, which
causes the kernel to remove autonode data structures.
Subsequent events then cause autonodes to be created
with partial data, which results in the bdf command
anomaly.
Resolution:
Fix automountd so it returns the correct error code
to the kernel during unmount operations.
automountd
JAGad65770
The unmount command failed for a mounted cachefs type
file system when trying to unmount with AutoFS
automountd. The cachefs unmount command was missing
a parameter that unmount included.
Resolution:
Added the new parameter for the cachefs unmount command.
automountd
JAGad30096
The AutoFS automountd caused the unmount command to
fail for mounted hfs and cdrom type file systems.
Resolution:
Added a new parameter for the hfs and cdrom unmount
commands.
libautofs.a
JAGad45257
Due to a race condition in AutoFS, autonodes are
getting created with NULL mount flags. The affected
AutoFS mount points show empty directories. A system
reboot is required to clear the condition.
Resolution:
Modified the code to eliminate the race condition.
libautofs.a
JAGad62727
For direct mounts, AutoFS did not wait for mounts to
complete when the direct mount point was accessed.
This triggered a second mount, creating a duplicate
entry in the /etc/mnttab file.
Resolution:
Added code in AutoFS to wait for mounts in progress
for direct mount points.
libnfs.a
JAGad66201
File access performance is slow on systems with large
memory and buffer cache.
Resolution:
Restore the performance version of the NFS code to
walk through buffer cache. The problem described in
JAGad32551 is also fixed.
libnfs.a
JAGad72416
If there are biods running in the system, asynchronous
reads are done by the kernel on behalf of the reader
process, and asynchronous writes are done on behalf of
the writer process. The problem with this is that
asynchronous write requests will be enqueued faster
than asynchronous read requests, thus monopolizing the
biods, and hence causing starvation for the
asynchronous read requests.
Resolution:
Modified the NFS read logic to avoid doing read-ahead
(asynchronous reads) if the biods are "too busy".
However, this fix is disabled by default. In order to
enable it, the kernel parameter
'async_read_avoidance_enabled' must be set to one, by
patching the vmunix file and rebooting, or by patching
the kernel image in memory. To patch the vmunix file
(survives a reboot), use this command:
echo 'async_read_avoidance_enabled?W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
To patch the in-memory kernel (does not survive a
reboot), use this command:
echo 'async_read_avoidance_enabled/W 0d1' |
adb -w -k /stand/vmunix /dev/kmem
A kernel regeneration will require these steps to be
done again.
libnfs.a
JAGad15675
The code does synchronous I/O when the file is locked.
This means that the biods are bypassed and the I/O is
performed by the calling thread.
Resolution:
Do not set the RNOCACHE flag for a whole-file lock.
Also, flush the buffer cache for each lock/unlock
request. Thus, fresh data is read at lock time and
all data is written before releasing the lock. Note
that for partial locks, the behavior remains unchanged.
This fix is disabled by default. In order to enable
it, the kernel flag 'nfs_new_lock_code' needs to be
turned on, by either patching the vmunix file and
rebooting, or by patching the kernel image in memory.
To patch the vmunix file (survives a reboot), use the
&nb