Software version: 9.16
Software Release Date: March 2014
Documentation Release Date: March 14, 2014
These Release Notes provide an overview of the changes made to HP Server Automation in this release. They contain important information not included in the manuals or in online help. Check the HP Self-solve documentation portal for the most current release notes.
Additionally, all SA 9.1x guides are compiled and catalogued for easy access in the SA 9.1x All Manuals downloadable zip file.
This site requires that you sign in with your HP Passport. If you do not have one, click the New users - please register link on the HP Passport login page to register.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details. Note the Document Release Date on the title page of your guide and see the Documentation Change Notes on page 3 of most documents for a list of any revisions. The release-notes change table is at the bottom of this document.
SA release notes contain information for users who are familiar with the installation and maintenance of SA, Storage Visibility and Automation, SE Connector, Application Deployment Manager, and DMA integration. The notes contain information that is not included in books or online Help.
This document contains the following information:
New in This Release |
Installation |
Known Issues |
Fixed Issues |
Deprecated Features |
Documentation Information |
HP Software Support |
Legal Notices |
This section describes new functionality and other relevant release-specific information.
For information about what was new in previous releases, see the corresponding release notes at:
http://support.openview.hp.com/selfsolve/manuals.
For complete SA support and compatibility information, see the HP Server Automation Support and Compatibility Matrix for this release at: http://support.openview.hp.com/sc/support_matrices.jsp.
For a list of supported operating systems and platforms for Storage Visibility and Automation Managed Servers, SE Connector, SAN Arrays, Fibre Channel Adapters, SAN Switches, File System Software, Database Support, and Storage Essentials Compatibility, see the Storage Visibility and Automation Support and Compatibility Matrix, also at: http://support.openview.hp.com/sc/support_matrices.jsp.
Check the HP Software Product Manuals portal for the most current matrices.
This table shows browser support information for this release.
Windows XP | Windows Vista | Windows 7 | Windows 2008 | Windows 8 | Windows 2K8 | |
---|---|---|---|---|---|---|
Chrome | x |
x |
x |
x |
x |
x |
Firefox | x |
x |
x |
x |
x |
x |
IE 6.0 | x |
x |
x |
x |
||
IE 7.0 | x |
x |
x |
x |
x |
|
IE 8.0 | x |
x |
x |
x |
x |
x |
IE 9.0 | x |
x |
x |
x |
||
IE 10.0 (Compatible Mode) |
x |
x |
x |
x |
Make sure you follow these steps before you install SA:
This section describes the installation procedure.
patch_opsware.sh
script is used
both for installing and for uninstalling SA 9.16. patch_opsware.sh
. patch_database.sh
script is used both for installing and rolling back database schema
changes required for SA 9.16. patch_database.sh
script on the First Core and all Secondary Cores. Note that the
Model Repository and Oracle database can exist on a different host than the SA
host. You must run the script on the machine that has the Model Repository installed.patch_database.sh
. If any installed SA components (other than a previously installed patch) have a different build ID, you will not be allowed to install SA 9.16.
/var/opt/opsware/install_opsware/inv/install.inv
and find the section beginning with
%basics_
. Under this line, find thebuild_id
.
For example:
%basics_linux
build_id: opsware_45.0.6790.0
When you install an SA patch, the patch installation updates the
install.inv
file to record the patch installation and the patch build ID.For example:
%opsware_patch
build_id: opsware_45.0.17090.0
/etc/init.d/opsware-sas status
command), the patch operation will terminate. If you must roll back the SA 9.16 patch in a Multi-master Mesh, HP recommends that you roll back the secondary cores and satellites first, then the primary core.
spog.pkcs8
certificate must exist under /var/opt/opsware/crypto
(typically the
certificate is installed with the Shell, SAS Web Client, or Build
Manager). If the certificate does not exist, the patch operation will fail
with the following error:
Could not find spog.pkcs8
/var/opt/opsware/crypto/occ
Copy the certificate from another core machine
(for example, occ ) to
/var/opt/opsware/crypto/occ
and
retry this operation.
/var/opt/opsware/crypto/spin
(typically the
certificate is installed with the Web Services Data Access Engine ( spin )). If the certificate does not exist, the patch
operation will fail with the following error:
Could not find spin.srv under
/var/opt/opsware/crypto/spin.
Copy the certificate from another core machine (such as occ) to
/var/opt/opsware/crypto/spin
and retry this operation.
You don't have permission to update the patch meta
database in HP SA.
Please re-run this command with a proper hpsa_user and
hpsa_pass.
The hpsa_user needs permission to write the folder
"/Opsware/Tools/Solaris Patching" and the Package Management
Client
Feature, "Manage Package" permission set "Read & Write".
There was a
problem with running update_supplements.
Please refer to section Patch
Management for Solaris of the Users Guide:
Application Automation manual
for details on how to set up Solaris
patching on your core.
You can safely disregard this error.
All SA installation DVDs require a DVD drive that supports dual layer.
The pre-patch, database update and patch install scripts must be run in the following order:
SA Script Running Order - Upgrade
Upgrade From |
To |
Script Running Order |
---|---|---|
9.10, 9.10.01, 9.10.02, 9.11, 9.12, 9.13, 9.14, 9.15 |
9.16 |
|
SA Script Running Order - Rollback
Roll back From |
To |
Script Running Order |
---|---|---|
9.16 |
9.10 |
|
When migrating from SA 7.8 to SA 9.1x:
When migrating from SA 9.0 to SA 9.1x:
Certain SA Client features (such as Run OS Build Plan or HP UX Provisioning) require the Adobe Flash Player. If you try to run these features, and you have not yet installed Adobe Flash Player, you will get an error.
To make sure Adobe Flash Player functions correctly and to avoid the error message, you should:
The error message should not display.
The script run during this procedure makes required changes to the Model Repository including adding required tables and objects.
patch_database.sh
on the Model Repository
host:
<distro>/opsware_installer/patch_database.sh --verbose -r <response file>
Where <
response file
> is the response file last used to install/upgrade the system.Usage:
patch_database.sh
[--
verbose
] -r <response file
>
patch_database.sh
automatically detects if a database update is already installed and presents a corresponding menu:
Welcome to the Opsware
Installer.
It appears that you do not have a database update
installed on this system.
Press 'i' to proceed with
patch installation.
Press 's' to show patch
contents.
Press 'q' to quit.
Selection:
i
Welcome to the Opsware Installer.
It appears
that you have installed or attempted
to install a previous version of
the database
update on this system.
Press 'u' to upgrade the patch
to the current version.
Press 'r' to remove this patch.
Press 's' to
show patch contents.
Press 'q' to quit.
Selection: u
You chose to
upgrade the patch. Continue? [y/n]: y
Enter u
at
the prompt then Y
to begin the database
update.
[timestamp] Done with component Opsware SQL
patches.
[timestamp]
########################################################
[timestamp] Opsware Installer ran
successfully.
[timestamp]
########################################################
Note: After running the
patch_database.sh
script, you may see the following error when running the System Diagnostic test on your core:
Test Name: Model Repository Schema
Description: Verifies that the Data Access Engine's version of the schema matches
the Model Repository's version.
Component device: Data Access Engine (spin)
Test Results: The following tables differ between the Data Access Engine and the
Model Repository: local_data_centers, role_class_bridge.
This error is invalid and you can disregard it.
SA 9.15, 9.16 and 10.01 provide an enhancement that improves performance and scalability for Linux remediation. Unintended deletion of certain jobs occurs when you upgrade to these versions (or rollback from these versions to certain previous versions) for jobs scheduled after the affected versions are installed.
The following types of jobs (both pending jobs and jobs that have already been run) are deleted if they are created after the affected version is installed:
The affected job information includes job state, job parameters, packages evaluated for the job, target servers, and values for subsequent phases, if only some of the phases were run (analyze, download, action). Server Automation stores this job information in the job history, and deletes it after 30 days by default.
To avoid losing your jobs and associated information, follow the instructions in the Server Automation Alert: Deploy the Remediation Job History Loss Fix SRVA 00176 at the following site: http://support.openview.hp.com/selfsolve/.
Perform the following tasks to install SA 9.16:
patch_opsware.sh
on every host in the core/satellite facility
:
<distro>/opsware_installer/patch_opsware.sh --verbose
Usage :
patch_opsware.sh [--verbose]
patch_opsware.sh
automatically detects whether or not there is a patch already installed and presents a corresponding menu:
Welcome to the Opsware Installer. It appears that
you do not have any patches installed on this system.
Press 'i' to
proceed with patch installation.
Press 's' to show patch contents.
Press 'q' to quit.
Selection: i
Enter i at the prompt to begin the installation.
patch_opsware.sh
is invoked from a newer patch Welcome to the Opsware
Installer.
It appears that you have
installed or attempted
to install a previous version of
the patch on this system.
Press 'u' to upgrade the patch to the current version.
Press 'r' to remove this patch.
Press 's'
to show patch contents.
Press 'q' to
quit.
Selection: u
Enter u
at the
prompt to begin the upgrade.
The installer displays the following upon completion:
[<timestamp>] Done with component Opsware
Patch.
[<timestamp>]
########################################################
[<timestamp>] Opsware Installer ran
successfully.
[<timestamp>]
########################################################
This section details upgrades to the software repository content on the upload distribution (such as agent packages to be reconciled to managed servers).
patch_opsware.sh
from the upload
distribution, but will only update those packages that have changed since
the last major version. word
store
). word
store
) host, invoke the upgrade script::<distro>/opsware_installer/patch_contents.sh
--verbose -r <response file>
where <response
file
> is the response file last used to install/upgrade the SA
Core.
The following menu is displayed:
Welcome to the Opsware Installer. Please select the
components
to install.
1 ( ) Software Repository - Content (install
once per mesh)
Enter a component number to toggle ('a' for all, 'n' for
none).
When ready, press 'c' to continue, or 'q' to
quit.
Enter either 1 or a, and press c to begin the installation.
[<timestamp>] There are no components to
upgrade.
[<timestamp>] Exiting Opsware Installer.
SA 9.15, 9.16 and 10.01 provide an enhancement that improves performance and scalability for Linux remediation. Unintended deletion of certain jobs occurs when you upgrade to these versions (or rollback from these versions to certain previous versions) for jobs scheduled after the affected versions are installed.
The following types of jobs (both pending jobs and jobs that have already been run) are deleted if they are created after the affected version is installed:
The affected job information includes job state, job parameters, packages evaluated for the job, target servers, and values for subsequent phases, if only some of the phases were run (analyze, download, action). Server Automation stores this job information in the job history, and deletes it after 30 days by default.
To avoid losing your jobs and associated information, follow the instructions in the Server Automation Alert: Deploy the Remediation Job History Loss Fix SRVA 00176 at the following site: http://support.openview.hp.com/selfsolve/.
To roll back SA 9.16 to SA 9.10, invoke the script:
<distro>/opsware_installer/patch_opsware.sh
--verbose
If this is a patched system, the following will be displayed:
Welcome to the Opsware Installer.
It
appears that you have previously
completed installation of this patch on
this system.
Press 'r' to remove this
patch.
Press 's' to show patch contents.
Press
'q' to quit.
Selection:
Enter r at the prompt to remove the patch.
<distro>/opsware_installer/patch_database.sh
--verbose -r <response file>
Where <response
file
> is the response file last used to install/upgrade the
system.
If the database has been updated, you see the following:
Welcome to the Opsware Installer. It appears that you have previously
completed the installation of this database update on this system.
Press 'r' to remove this patch.
Press 's' to show patch contents.
Press 'q' to quit.
Selection: r
Enter r at the prompt to begin the database schema update rollback.
This section lists the tasks that should be performed after you install SA 9.16. Some tasks might not be appropriate for your situation.
If SA 9.16 is installed on Red Hat EL 5.9, sporadic org.omg.CORBA.COMM_FAILURE exceptions will be displayed in the SA Client console.
To work around this issue:
Directive:
opswgw.SoReuseAddr=false
Redhat has a description of this issue on their website: https://access.redhat.com/site/solutions/357683
If you plan to install the SA Command-line Interface (OCLI) on a Windows Server after upgrading to SA 9.16, you must update the SA Agent on that server to the latest version. Errors occur during OCLI installation on Windows servers with earlier SA Agent versions.
If you install additional Slice Component bundle instances after patching the SA Core to version 9.1X, wayscript versions are set to version 9.10 rather than to the patch version. Use the following procedure to remedy the situation:
cd
/var/opt/opsware/OPSWpatch/OPSWwayscripts/scripts
Command #2:
./post_after_startup.sh
If you have customized such settings as Java heap settings, you must reapply your customizations after you install 9.16, as the settings are set to the SA default during installation or upgrade.
SA 9.15, 9.16 and 10.01 provide an enhancement that improves performance and scalability for Linux remediation. Unintended deletion of certain jobs occurs when you upgrade to these versions (or rollback from these versions to certain previous versions) for jobs scheduled after the affected versions are installed.
The following types of jobs (both pending jobs and jobs that have already been run) are deleted if they are created after the affected version is installed:
The affected job information includes job state, job parameters, packages evaluated for the job, target servers, and values for subsequent phases, if only some of the phases were run (analyze, download, action). Server Automation stores this job information in the job history, and deletes it after 30 days by default.
To avoid losing your jobs and associated information, follow the instructions in the Server Automation Alert: Deploy the Remediation Job History Loss Fix SRVA 00176 at the following site: http://support.openview.hp.com/selfsolve/.
Since 9.11, SA Agents have used Python 2.4.4.
After you upgrade to SA 9.16, you should also upgrade to the 9.16 SA Agents on each Managed Server in the facility. If you do not upgrade your agents, the new functionality will not be available.
Duplicate patches can be inadvertently created in the SA database if you import the Microsoft Patch Supplement (MPS) and then run the SA Patch Import process using the Microsoft Offline Patch Catalog (wsusscn2.cab). These duplicates can cause conflicts during remediation and compliance checks. SA provides a Windows patch de-duplication process that enables you to eliminate these duplicates and resolve this issue.
IMPORTANT: When to perform the de-duplication process:
The Windows patch de-duplication process is only required for SA upgrades, and is only required to be performed once:
How do I know if I have duplicates?
Starting in 9.14, the patch database has a new field, “Last Import Summary, which reports if any duplicates were found in your database. In the SA Client, navigate to Administration > Patch Settings > Patch Database to view this field. If it displays a warning message after performing a patch import, then there are duplicates in your database. If duplicates are found, these de-duplication steps are strongly recommended.
Resolving Duplicates
To resolve this, a one-time de-duplication procedure is available that enables you to remove the duplicates and eliminate the source of these conflicts to prevent future duplication.
Step-by-step instructions are provided in the whitepaper, Resolving Conflicts between SA Patching and the MS Patch Supplement, which is available on the HP Software Support Online site under the 9.16 Server Automation release.
IMPORTANT: The de-duplication procedure varies based on your version of SA. For this reason, there will be multiple versions of this whitepaper, each providing release-specific instructions. Be sure to use the version of the whitepaper recommended for this release.
To find the whitepaper:
You can also do the same search directly from the SSO Product Manuals site: http://support.openview.hp.com/selfsolve/manuals
Back to the Table of Contents
This section describes high severity issues from SA versions 9.10, 9.11, 9.12, 9.13, 9.14, 9.15, and 9.16. The table lists issues first alphabetically by Subsystem, then numerically within each subsystem.
Known Issues
QCCR1D | Subsystem | Platform | Symptom/Description | Workaround |
---|---|---|---|---|
Agent |
||||
QCCR1D156924/167887 | Agent | Linux; Solaris | Software policy remediation of multiple packages with reboot option fails at install stage with batchbot error: The operation to install or uninstall software failed. | Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue. |
QCCR1D159580 | Agent | Windows | The VMWare Virtual Network Adapters installed with VMWare Server on Windows uses the same MAC addresses by default, causing agent registration to fail with the following message: ERROR: spin.notUniqueInDatabase - SA was unable to locate the record for this server in the database because more than one record already exists with the MAC address. |
Use the --force_new_device option and pass it as a parameter to the agent installer. |
QCCR1D168321/168321 | Agent | Solaris | Fujitsu hardware running on Solaris servers reports a partial serial number if the gp-serial number is enclosed in single quotes. |
Contact HP Support for information on a hot fix that addresses this issue. |
Application Configuration Backend |
||||
QCCR1D160790 | Application Configuration | Linux | When loading the configuration data for the CML template containing two blocks, configuration data for the second block is loaded into the first block. | Set the delimiter="[" for the first block to instruct the CML parser that the first block ends when it reaches the start of the second block: @*firstfield;unordered-string-set;;delimiter="["@. |
Command Engine (Way) | QCCR1D177571 | Command Engine | Linux | SA installation on a core fails with the following error: Archive: /mnt/90/packages/././OPSWwayscripts-40.0.0.0.71.2.zip inflating: wayscripts.archive [Oct-11-2013 15:02:08] Running script wayscripts/post. Installing Wayscripts: ... Installing __global__.adt_deploy_agents.bat (version opsware.34.3) ... Traceback (most recent call last): File "./util/wayscript_installer.py", line 878, in ? ... self.append(_stringify(data)) ... timeticks: None waybot.verifyUpdateFailure Wayscript installation failed. Archive left in /var/tmp/oitmp/wayscripts.archive. [Oct-11-2013 15:02:14] Component installation script encountered an error (exit status 1) [Oct-11-2013 15:02:14] Exiting Opsware Installer. |
To install without this error: 1. Copy the following directories from a slice that is already recertified to the new slices you plan to add to the recertified mesh: /var/opt/opsware/crypto/waybot/archives/ /var/opt/opsware/crypto/wordbot/archives/ 2. Rerun the installer: |
Gateway |
||||
QCCR1D172459 | Gateway | Linux | During monitoring of Gateway flows from the SA Web Client, one or more connections remained in the ACK state with InFlight=-1 until the cgws is restarted. | Restart the core gateway service. |
Global File System (Spoke) |
||||
QCCR1D162289/162450 | Global Filesystem/Shell Backend | Independent | Deadlock errors occur when you run a storage snapshot ((Storage --> Inventory). | None. |
QCCR1D167608 | Global Filesystem/Shell Backend | Linux | Failures running OGSH commands in SA from OO. | Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue. |
Model Repository (Truth) |
||||
QCCR1D172195 | Model Repository | Independent | A secondary core created from a SA9.14/SA9.15 primary core creates 2 jobs for AAA user in dba_jobs table. | Run the following on the secondary core. If you have a RACed environment then run this on one of the RACed nodes. $ sqlplus "/ as sysdba" SQL> grant create session to aaa; SQL> connect aaa/<aaa_password> #You should see 2 rows in the result set for the SQL below SQL> select job, what from user_jobs; #below SQL will give you the job# of the duplicate job SQL>select job from user_jobs where what like 'gather%stats%' and job not in (select max(job) from user_jobs where what like 'gather%stats%' group by priv_user, what); #below SQL will delete the duplicate job. Replace the ‘insert_job_no_from_previous_sql_here’ with the value from previous step SQL> execute dbms_job.remove(insert_job_no_from_previous_sql_here); #You should see only 1 row in the result set for the SQL below SQL> select job, what from user_jobs; SQL> connect / as sysdba SQL> revoke create session from aaa; Check the SysDiag test. The error of incorrect job count should not be there. |
QCCR1D172371 | Model Repository | Independent | Secondary core creation on Oracle 11.2.0.3 RACed environment ran into ORA-01031: insufficient privileges: grant execute on dbms_utility to data_owner. | Apply Oracle PSU 11.2.0.3.7 and re-run the SA installer. |
OS Provisioning (Backend) | ||||
QCCR1D120072/161507 | OS Provisioning Backend | Independent | The Manage Boot Client (MBC) creates a record when both satellites are running , but if one of them is no longer running, the MBC fails with the following error: File "ServletStubImpl.java", line 292, in execute … Remote Traceback: File "OSSequenceServiceBean.java", line 171, in runOnServer |
None. |
QCCR1D159441 | OS Provisioning Backend | Linux | RHEL/SLES builds fail with the following error: RHEL : Agent installation failed with return code of: 1024 SLES: Agent installation failed with return code of: 32512 |
Contact HP Support for information on a 9.16 hot fix that addresses this issue. |
QCCR1D165440 | OS Provisioning Backend | Linux | Cannot install any Gen7 or Gen8 Servers that have AMD CPU's during the assisted installation process. The final line during the installation process is:Fixing recursive fault but reboot is needed! |
None. |
172963 | OS Provisioning Backend | Linux | OS Provisioning fails for Windows Server 2012 VMs during the specialized step if you specify more than one partition in an unattended file, and the first partition is too small for the OS to fit. | Ensure the partition layout will not change the %SystemDriver% environment value. |
QCCR1D174726 | OS Provisioning Backend | Windows | Winpe64-OGFS no longer contains drivers for BCM5709C NetXtreme II GigE (14e4:1639). | Use the 9.14 WIM image or update the current wim images with the needed drivers. For details see the KM1405856 knowledge article at http://support.openview.hp.com/selfsolve/document/KM1405856. |
QCCR1D177204 | OS Provisioning Backend | Windows | OS Provisioning of WinPE images will fail about 10% of the time when using a port channel or two bonded NICs. | Disable the second NIC in either the switch or WinPE image |
Patch Management (Backend) |
||||
QCCR1D102713 | Patch Management Backend | Independent | If a patch policy contains one or more superseded patches, the number of total rules counted after remediating or patch installation is incorrect. Note that the compliance state of the server is accurate before and after remediating. | None. |
QCCR1D137915/152933 | Patch Management Backend | Solaris | Import of Solaris Patch Supplement content may render a false failure error on Fujitsu servers that are missing the appropriate Fujitsu credentials in the solpatch_import.conf file. Sample error: live-network-connector:ERROR : Import of content Solaris Patch Supplement version 2.00.00-01 failed. Exception: [PostExecuteError] Non-zero exit (6) for post-execute command '/tmp/tmpgcTtsa/install.sh'. 2011-08-31 19:09:48,823 live-network-connector:DEBUG : Associated metadata: /content/sas/solaris_patching/dd78741ee8ea41718ca70bf0debf3f51.metadata.xml 2011-08-31 19:09:48,824 live-network-connector:DEBUG : { File "modules/lnc_client.py", line 584, in _importStreams File "modules/content-handlers/content_uncompress.py", line 87, in import_content File "modules/lnc_common/ContentType.py", line 111, in do_post_execute } |
You can usually ignore this error unless you are trying to import metadata for Fujitsu patches. If you are trying to import metadata for Fujitsu patches, then you need to enter the Fujitsu credentials into the solpatch_import.conf file located at /etc/opt/opsware/solpatch_import/solpatch_import.conf. Once the credentials are entered, this error message will go away. |
QCCR1D144269 | Patch Management Backend | Independent | The following patches fail to install: KB929300 and KB929300. | If performing an individual patch installation, the following patches must be installed as pairs in order for the job to succeed. KB929300 -- must be remediated along with 110806. KB2416400 -- must be remediated along with 2467659. For these pairs, if the patch installation job contains one of the patches in the pair but does not contain the other, the job will fail. |
QCCR1D157228 | Patch Management Backend | Independent | Installation of the Q2416400 patch fails with exit code 4 when you suppress reboot during a remediation job. However, the patch is actually installed. | Manually add KB2467659 to the patch policy. KB2416400 has a dependency on KB24676. |
QCCR1D157363 | Patch Management Backend | Windows | Occasionally, the following uninstall patch job message is displayed when you manually uninstall a patch using SA: "The Agent reports that this software is not uninstallable." However, the patch is actually uninstalled. When you uninstall the patch using the Control Panel > Add/Remove Programs method, the patch uninstalls correctly. | None |
QCCR1D157372 | Patch Management Backend | HP-UX | SA displays an incorrect message when it tries to remediate an HP-UX server if the following conditions are present: * The "hpuxpatch_dont_supersede" custom attribute is not set. * The patch being remediated has a superseding patch. * The superseding patch is not present in the SA repository. |
None. |
QCCR1D161643/168655 | Patch Management Backend | HP-UX | Cannot download swa_catalog.xml file by using import_hpux_metadata script. | Download the swa_catalog.xml file from HP Support site. Import the downloaded file: /opt/opsware/mm_wordbot/util/import_hpux_metadata -c swa_catalog.xml. |
QCCR1D174155 | Patch Management Backend | AIX | A master software policy with embedded child policies is remediated and displays the following error: "Install tivoli.tsm.client.oracle.aix.64bit-5.5.2.0 Will Not Install" the reason being "Fileset is missing requisite bos.rte v=5 r>0" |
Upgrade the tivoli.tsm.client.oracle.aix.64bit package to version 6.3 , which has vendor support for AIX 7.1. |
QCCR1D177309 | Patch Management Backend | Linux | Windows Patch compliance scans might fail with the following traceback: communication time-out error: read timeout |
A hotfix is available through HP Support. |
QCCR1D179631 | Patch Management Backend | Linux, Solaris, AIX | While patching approximately 100 Unix-based servers (Linux, Solaris and AIX), the environment becomes unresponsive and requires a restart. | A hotfix is available through HP Support. |
Patch Management UI |
||||
QCCR1D136931/137014 | Patch Management UI | Windows | When running Windows Server 2003 SP2, and when the target Server has Office Word Viewer 2003, Excel Office Viewer and Compatibility Pack for the 2007 Office System, installed, recommended patches (see below) are not being installed. Patches: MS08-052 KB954326 (Office 2007) MS09-062 KB972581 (Office 2007) MS10-038 KB982333 (Office 2007) MS11-023 KB2509488 (Office 2007) |
This defect is caused by a fault in the installation-detection logic of one of the patches, which can only fixed by a change in the Microsoft offline patch database. A case has been opened with Microsoft. |
QCCR1D148400/153334 | Patch Management UI | Windows | After a Windows Patch Metadata (MBSA) import completes, it takes a long time to update the patches in the library and database information in the Administration page. | None. |
QCCR1D176141 | Patch Management UI | Windows | Exporting the patch compliance for a group of servers to a CSV file from SA Client takes a long time. | None. |
Server Automation Client |
||||
QCCR1D168719 | SA Client | Windows | When you edit a package script, the user interface takes several seconds to display each keystroke. | Edit the script in a notepad buffer and then copy/paste the entire buffer into the PackagePropertiesPanel. |
Server Management (Backend) |
||||
QCCR1D179140 | Server Management (Backend) | Linux | Scheduling remediation jobs for a static device group of 240 servers fails, and the remediation job is not created. The following error is visible in the twist.log: #### <sho-p-hpsapp-01.company.com> <[ACTIVE] ExecuteThread: '22' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <[STUCK] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "719" seconds working on the request "com.opsware._gen.sejb.swmgmt.SoftwarePolicyService_hfpabb_EOImpl", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: |
Schedule a job for a smaller number of servers (less than 150). |
Server Module (Backend) |
QCCR1D156389 | Server Module (SMO) Backend | Windows 2012 | Users and Groups SMO will not report all the groups that are created on a Windows 2012 Essentials. If user properties are edited, these changes will not be reported by the SMO. This means that audits with U&G rules will not be relevant on a Windows 2012 Essentials. | None. |
Software Management (Backend) | QCCR1D164397 | Software Management Backend | Independent | RPM remediation fails if you update the SA Core to the latest SA version, but the associated satellite that the agent is connected to is an older version of SA. | Contact HP Support for information on a 9.16 rollup hot fix that addresses this issue. |
QCCR1D177166 | Software Management Backend | Linux | Preview mode can fail with Non-zero exit code (None) from dependency solve. | None. |
QCCR1D183132 | Software Management |
Independent | Unintended deletion of certain jobs occurs when you upgrade (or rollback) for jobs scheduled after you install SA 10.01. The following types of jobs (both pending jobs and jobs that have already been run) are deleted:
|
Follow the steps explained in the Server Automation Alert: Remediation Job Loss During Upgrade/Rollback SRVA 00176 |
Virtualization - HP-UX | QCCR1D157368 | HPUX Virtualization-HPVM Front End | HPUX | In the Add Virtual Servers HP-UX Virtualization Manager screen, if you enter a specific HP-UX machine name into the search field of the IP Address/Hostnames choice, no list of HP-UX machines is generated. | In the Add Virtual Servers HP-UX Virtualization Manager screen, click Explicit IPs/Hostnames, then choose All from the drop-down menu. A list of all the HP-UX machines is displayed. Select the machine you are looking for and click Add Server. |
Web Services Data Access Engine (Twist) |
||||
QCCR1D133589 | Web Services Data Access Engine | Red Hat Linux | Web Services Data Access Engine takes too long to start up. | None. |
QCCR1D179479 | Web Services Data Access Engine | Independent | The tokens used by recurring application configuration compliance jobs fail after a year because the tokens have a limited lifetime of one year. | Recreate the job. |
Additional Known Issues
The complete list of 9.1x known issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/documents.
Note: This site requires that you sign in with your HP Passport and have an SAID. If you do not have authorization, contact your HP sales representative for details.
Search for Product: Server Automation, Version: 9.10, Document Types: Known problems.
Back to the Table of Contents
The Fixed Issues table includes issues that:
The table lists issues first by subsystem, then numerically within each subsystem.
QCCR1D | Symptom/Description | Platform |
---|---|---|
AA |
||
QCCR1D167959 | /opt/opsware/twist/ldap_config.sh does not support multiple base DN searches. | Linux |
QCCR1D168463 | WRITE_PERSISTENCE_ERROR messages in the twist logs, such as: weblogic.ejb.OptimisticConcurrencyException: [EJB:010143]Optimistic concurrency violation. Instance of bean 'AaaUser' with primary key 'nnnnnnnn' was changed by another transaction. ... where 'nnnnnnnn' is a number. |
Linux |
QCCR1D171593 | Access Engine process is interrupted at the HashMap.get() call. |
Independent |
Access Engine |
||
QCCR1D165592 | Inherited custom attribute access does not scale well. | Independent |
QCCR1D165724/166328 | When audits are started manually, they do not run at the scheduled time, and the following error is displayed: RemoteExeption occurred in server thread; nested exception is : java.rmi.RemoteException: EJB Exception:;nested Exception is : java.lang.NullpointerExeption' |
Linux |
QCCR1D167739 | Audit execution fails with: Failed: Error Details: HPSA-1800 : Source snapshot copy failed An error occurred while copying the source snapshot from the source slice to another slice. |
Independent |
QCCR1D171685 | The AWR report shows a very high number of buffer returns from the ComplianceScanHelper.01 query. | Linux |
QCCR1D176240 | Web Services Data Access Engine encounters socket timeouts and other timeouts. Weblogic was upgraded to version 11g |
Linux |
QCCR1D176828/176835 | Copy and Paste of OS Build Plans within HP SA Client Library does not copy custom attributes. | Independent |
Agent |
||
QCCR1D169034 | Agent migration fails due to 'port in use' error for HPSA agent ports. | Windows |
QCCR1D171798/171954 | "Open with -> Remote PowerShell" on windows boxes will open a CMD shell instead of a PowerShell. | Independent |
QCCR1D174136 | Default working directory for agent installation can be changed by using SA Client Device->Manage Server-> Advanced -> Extra installer options. Agent installation ignores the --workdir option set from SA client. | Linux |
Data Access Engine |
||
QCCR1D166753 | DCML Exchange Utility (DET) is generating the following error message when importing an HP-UX Product depot/package that is attached to a software policy.: The object 'HPUXProductUnit' has no field named 'remove_flags' |
Independent |
QCCR1D169827 | Using Repo.restrict custom attribute throws ORA-01795 when using a parent folder with more than 1000 sub-folders. | Linux |
QCCR1D175131 | Software Registration errors with DBNotNullConstraintError on Windows server | Windows |
DCML Export Tool (DET) |
||
QCCR1D168103 | DCML Exchange Utility (DET) displays an import error when the target folder does not exist. Missing folders now exist. |
Linux |
Global Filesystem |
||
QCCR1D115140 | Solaris OS experiences kernel panic and seizes to function. | Solaris |
QCCR1D168310 | Audits fail and display the following error: Error Details: An internal exception of type com.loudcloud.opsware_common.errors.OpswareError with message OpswareError: Executing Audit failed [ module: com.opsware.acm.way, method: calculateAuditBasePath, line: 110, hostname: timestamp: 2013-06-17 18:52:19.6, messageKeyOrder: msg, msg: java.lang.NullPointerExceptionFound in: com.opsware.acm.way.SnapshotComplianceWayHandler ] was caught. The error message appeared because the "0" directory was missing: /var/opt/opsware/word/mmword_local/audits/0/ on core server. Directory is now created automatically. |
Linux |
QCCR1D171803 | Remote terminal to Linux server does not create home folder on first time logon. | Linux |
QCCR1D176048/176051 | SMO based audit throws "org.apache.noggit.NoggitException: invalid hex digit: char=\,position=1844" exception | Linux |
Installer |
QCCR1D168038/168040 | Too many world writable files under /opt/opsware. | Independent |
Jobs |
QCCR1D170782/170785 | Remediation jobs completed but missing details, some targets not acted upon | Linux |
OS Provisioning |
||
QCCR1D176374 | Reprovisioning jobs time out against any server with SAN attached | Independent |
Patch Management | ||
QCCR1D159560 | Windows patching job failed on first MS patch with error code : 2147024770, 'The specified module could not be found' | Independent |
QCCR1D162682 | Software Registration displays a DBNotNulConstraintError error. | Windows 2003 |
QCCR1D174991 | When you try to remediate a large number of servers, the remediate dialog box takes a long time to be displayed. | Windows |
QCCR1D175648 | Windows Patching Remediation Scheduling for a group of servers times out. | Linux |
Software Management |
||
QCCR1D165745 | The custom attribute (CA) queries from opsware.swprov.doer should be disabled by default, instead of enabled by default (except for repo.restrict.<name>). | Independent |
QCCR1D167731 | Require an efficient methodology to snapshot RHN channels. |
Independent |
QCCR1D168231 | During an upgrade, when you remediate and install jobs on servers that contain OPSWpackage_path custom attributes (CA), you receive this error: Start time: - End time: - Error Messages: The operation to download software failed.Execution error: Traceback (most recent call last): File ".\base\wayfuncs.py", line 136, in evaluator File " ", line 2940, in ? File " ", line 2934, in main File " ", line 2738, in stage File " ", line 1162, in download_packages UnboundLocalError: local variable 'client' referenced before assignment |
Linux |
QCCR1D168451 | Packages with response files fail to install. | Solaris |
Software Repository |
QCCR1D158353 | While running LNc import the following error is displayed: OSError: [Errno 31] Too many links: '/var/opt/opsware/word/mmword_local/vcols/Unit/5953440001' |
Linux |
Additional Fixed Issues
The complete list of 9.1x fixed issues reported by customers can be found on the SSO Portal at: http://support.openview.hp.com/selfsolve/documents.
Note: This site requires that you sign in with your HP Passport and have an SAID. If you do not have authorization, contact your HP sales representative for details.
Search for Product: Server Automation, Version: 9.10, Document Types: Known problems.
Back to the table of contents
When a feature or platform is identified as deprecated for a release, it means that you (the SA customer) are notified of its future removal. Deprecated features are still fully supported in the release they are deprecated in, unless specified otherwise. The intent is that deprecated features or platforms will have support removed in the next major or minor SA release; however, eventual removal is at the discretion of HP.
The following sections list features that were deprecated in the SA 7.80 release. Current and future availability of these features is also described here.
In SA 9.0, moving application configurations and configuration templates into folders changed the behavior of the associated classes and services.
Attributes folder and lifecycle of the VO-s are required for the following API calls:
com.opsware.acm.ConfigurationService#create
com.opsware.acm.ConfigurationService#update
com.opsware.acm.CMLService#create
com.opsware.acm.CMLService#update
The following methods have been deprecated, but they still perform as expected. Method
com.opsware.folder.FolderVO#getCustomers should be used instead.
com.opsware.acm.ConfigurationVO#getCustomers
com.opsware.acm.CMLVO#getCustomers
The following methods have been deprecated and they have a void implementation. Method
com.opsware.folder.FolderVO#setCustomers must be used instead.
com.opsware.acm.ConfigurationVO#setCustomers
com.opsware.acm.CMLVO#setCustomers
Code Deployment and Rollback (CDR) was deprecated in the SA 7.80 release, but is still supported in SA 9.0. In a future release, this feature will not be supported. The new Application Deployment Manager in SA 9.0 is intended to replace CDR. See Application Deployment Manager in the SA Application Deployment User Guide for more information.
If you upgrade to SA 9.16 and also upgrade to an SA 9.16 agent, you will no longer be able to use CDR because it is only supported if you are using SA 9.01 (or earlier) agents. However, you will be able to use CDR with SA 9.16 if you uninstall the SA 9.16 agent and reinstall an SA 9.01 (or earlier) agent (not recommended, as you will be unable to use other SA 9.16 features).
For more information about the deprecation of CDR, contact your HP Technical Support representative.
In SA 9.0, HP announced the deprecation of the Server Automation Agent for the following versions:
• Server Automation 7.01
• Server Automation 7.00
• Server Automation 6.xx
• Server Automation 5.xx
Although releases of HP Server Automation prior to 9.0 will continue to support these versions of the Agent, it is recommended that customers migrate to newer versions of the Agent on their managed platforms.
HP SA will stop supporting these versions of the Agent in an upcoming major or minor release. Agents from Server Automation 4.xx and earlier are not supported in this release.
DOS-based OS Provisioning was deprecated in the SA 7.80 release and is not supported in SA 9.0 or later. For more information, contact your HP Technical Support representative.
As of SA 7.80, the following scripts are no longer supported:
start_opsware.sh
stop_opsware.sh
In SA 9.0 and later you must use the unified start script:
/etc/init.d/opsware-sas
If you have any applications or scripts that depend on this script, you must rewrite them to use the unified start script.
The Open Console action (for VMware virtual machines of ESX agent-managed hypervisor) was removed in the SA 9.0 release.
The Open Web Access action (for ESX agent-managed hypervisors) was removed in the SA 9.0 release.
As of SA 9.0, virtualization actions for agent-managed ESX 3.0 hypervisors are no longer supported, unless the ESX 3.0 hypervisor is managed by a Virtualization Service. It cannot be directly added to the Virtual Servers view (through Add Hypervisor); it needs to be vCenter managed.
The following Virtual Server reports were deprecated in 9.14:
The following SMOs were deprecated in 9.14:
This section discusses documentation information for this release.
In addition to the SA 9.10 guides on the Self Solve website and the online help, the following white papers and guides are relevant to this release:
This section contains corrections for existing documentation.
Page 104, Recertifying SA Cores section - replace the entire section/steps with the following:
Recertifying SA Cores
Note: You must clear all backlogs and conflicts on your Multimaster Mesh before you start a core
recertification.To recertify SA Cores, perform the following tasks:
1. Ensure that you are classified as a Core Recertification User. If not, see your SA System
Administrator.2. Log on to an SA Core host.
3. Change directory to /opt/opsware/oi_util/OpswareCertTool/recert_utils/.
4. Edit corerecert.conf to ensure that the information is correct for your environment.
5. Run: corerecert --status to ensure Core Recertification is not currently in progress.
6. Run: discover_mesh -p to make sure the Core Recertification Tool can correctly detect your Mesh setup.
7. Run: corerecert --phase 1 from the command line to initialize Core Recertification.
8. Monitor the progress on screen by running: corerecert --status until it has indicated Phase 4 is in progress.
9. Run: corerecert --phase 4 from the command line to start Phase 4, which appends a new Agent CA to all the Agents.
10. Monitor the progress on screen by running: corerecert --status until all the Agents have successfully had a new agent CA appended.
Note: This step could take days depending on your maintenance windows and the Agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 9 on page 105. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recert job for the successful facilities.
11. Run: corerecert --phase 6 --doit from the command line to start Phase 6 of the core recertification.
12. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. At this point, you must work with the SA System Administrator to restart the mesh.
Note: This step could take days depending on your maintenance window. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 11.
13. After the mesh has successfully restarted, run: corerecert --phase 6 from the command line to continue phase 6.
14. Monitor the progress on screen by running: corerecert --status until phase 7 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 13 on page 106.
15. Run: corerecert --phase 7 from the command line to start phase 7.
16. Monitor the progress on screen by running: corerecert --status until phase 8 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 15.
17. Run: corerecert --phase 8 from the command line to start Phase 8, which recertifies all the Agents.
18. Monitor the progress on screen by running: corerecert --status until all Agents have successfully been recertified.
Note: This step could take days depending on a customer’s maintenance windows and the agent availability. There can be only one scheduled or active Agent Recertification job per facility at any given time. If you encounter any errors during this stage, resolve the errors and go back to step 17. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
19. Run: corerecert --phase 9 from the command line to start phase 9. The Core Recertification Tool prompts you to confirm that you want to begin phase 9. Press y to continue.
20. Monitor the progress on screen by running: corerecert --status until it has indicated mesh_restart_pending. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 19. At this point, you must work with your SA System Administrator to restart the mesh.
Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 19 on page 106. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
21. On the base Slice core server:
a) Issue the following commands:
touch /var/opt/opsware/crypto/twist/upgradeInProgress
/etc/init.d/opsware-sas restartb) Wait till the restart successfully finishes, then
c) Restart the rest of the mesh.
22. After the mesh has successfully restarted, the Recertification User must run: corerecert --phase 9 from the command line to continue phase 9.
23. Monitor the progress on screen by running: corerecert --status until Phase 12 should be started. If you encounter any errors during this stage, make sure you resolve the errors and go back to step 22
24. If you do not intend to remove the Agent CA, skip to step 26. Otherwise, run: corerecert --phase 12 from the command line to start phase 12, which removes the old Agent CA from all the Agents.
25. Monitor the progress on screen by running: corerecert --status until the old Agent CA has removed from all the Agents.
Note: This step could take days depending on customer’s maintenance windows and the agent availability. If you encounter any errors during this stage, resolve the errors and go back to step 24. You only need to reschedule the facilities that had errors. You do not need to reschedule the Agent Recertification job for the successful facilities.
26. Run: corerecert --phase 13 --doit from the command line to start phase 13. If you do not want to remove the old CAs, a Mesh restart is not required in this phase.
27. Monitor the progress on screen by running: corerecert --status until it indicates mesh_restart_pend. At this point, you must work with the SA System Administrator to restart the mesh.
Note: This step could take days depending on the customer’s maintenance window. If you encounter any errors during this stage, resolve the errors and go back to step 26.
28. After the mesh has successfully restarted, run: corerecert --phase 13 from the command line to continue phase 13.
29. Monitor the progress on screen by running: corerecert --status until it indicates that Core Recertification has completed successfully.
The core recertification procedure does not re-assign Model Repository data. During operation, both old, archived, and new custom attributes are loaded to validate the signatures.
When a new core is added to a recertified mesh, the old or archived custom attributes have to be manually copied to this new core.
Property Name | Required? | Description | Example |
---|---|---|---|
agent_recert.using_cdr=<0 | 1> |
Yes | Specifies that the Agent CA push will be required when the value is set to 1. Also, the old Agent CA cleanup phase will be skipped unless the agent_recert.cleanup_old_agent_ca property is set to 1.
Valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error. Default: 1.
Note: CDR refers to Code Deployment and Rollback which has been deprecated but may still be in use. |
agent_recert.using_cdr=1 |
agent_recert.cleanup |
No | Indicates whether to clean up the old AgentCA after Core Recertification.
Cleanup of old Agent CA phase is not necessary and can be disabled. The valid values are 1 (true) or 0 (false). Any other value will result in an invalid property error. This is an optional property. Default: 0. |
agent_recert.cleanup_old_agent_ca=0 |
Step 10 currently reads:
/opt/opsware/oi_util/OpswareCertTool/recert_utils/corerecert --phase 6 --doit
It should read:
/opt/opsware/oi_util/OpswareCertTool/recert_utils/corerecert --phase 6
In the Details: Start Order for SA Components list, item 16, opswgw-lb, should be removed. The opswgw-lb component was incorporated into the Core Gateway (opswgw-cgw) component.
Enter the following:
During SA Core patch and/or hotfix installation, several directories are created under the /var/opt/opsware directory to facilitate the patching. The diskspace requirements listed below have been increased to handle the patch media requirements
/opt/opsware 25 GB
/var/opt/opsware 20 GB
The section "CRP – Agent certificate mismatch" should read:
This result indicates that the SSL certificate that the Agent is using (cogbot.srv) does not match the SSL certificate that is registered with HP Server Automation for that Agent. Also, a server hosting a Slice Component bundle with the wrong time zone specified could cause a large number of servers with a CRP error during a communications test.
What Can I Do If I Get a Certificate CN Mismatch During a CRP Test?
If the mismatch is determined to be due to a time zone mismatch, synchronize the time zone specifications for the servers. If the error is due to a certificate mismatch, use the Recert Agent Custom Extension to issue a new certificate to the Agent.
In the Application Deployment Manager, context-sensitive online help is
provided for numerous dialogs, including the Manage Applications and Manage
Targets dialogs.
To view a context-sensitive help topic, click the question mark icon in the dialog.
Note: The F1 key does not open online help for the Application
Deployment Manager.
To view the portion of the SA online help that pertains to application
deployment, select Help -> Help in the Application
Deployment Manager.
Refer to the HP Server Automation Application Deployment Manager User Guide for additional information.
On page 25, Network Reports section, disregard the following reports:
The only reports available in SA are "Connections by Network Device" and "Connections by Server".
Under the heading "Network Requirements", the first bullet:
should be changed to:
Add to Table 15 an entry for Port 8081: agentcache component
As of SA 9.14, under the heading "Check for Sufficient Free Disk Space in the Tablespaces", the following SQL replaces the SQL in this section for checking free tablespace disk space:
SELECT
nvl(df.tablespace_name,'UNKOWN') name,
df.mbytes_alloc Mbytes,
df.mbytes_alloc-nvl(fs.mbytes_free,0) used,
nvl(fs.mbytes_free,0) free,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_alloc) * 100 pct_used,
nvl(df.largest,0) largest,
nvl(df.mbytes_max,df.mbytes_alloc) Max_Size,
((df.mbytes_alloc-nvl(fs.mbytes_free,0)) / df.mbytes_max) * 100 pct_max_used
FROM
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
max(bytes)/1024/1024 largest,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Mbytes_max
FROM
dba_data_files
GROUP BY tablespace_name
) df,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_free
FROM
dba_free_space
GROUP BY tablespace_name
) fs
WHERE df.tablespace_name = fs.tablespace_name(+)
UNION
SELECT
D.tablespace_name name,
D.mbytes_alloc Mbytes,
((ss.used_blocks * F.block_size) / 1024 / 1024) used,
D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024) free,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.mbytes_alloc) * 100 pct_used,
nvl(((G.max_blocks * F.block_size) / 1024 / 1024),0) largest,
Max_Mbytes Max_Size,
((D.mbytes_alloc-nvl((D.mbytes_alloc - ((ss.used_blocks * F.block_size) / 1024 / 1024)),0)) / D.Max_Mbytes) * 100 pct_pct_used
FROM
(
SELECT
tablespace_name,
used_blocks,
free_blocks,
max_size
FROM
v$sort_segment
) ss,
(
SELECT
tablespace_name,
sum(bytes)/1024/1024 Mbytes_alloc,
sum(decode(autoextensible,'YES',greatest(bytes,maxbytes),bytes))/1024/1024 Max_Mbytes
FROM
dba_temp_files
GROUP BY tablespace_name
) D,
(
SELECT
B.name,
C.block_size,
SUM (C.bytes) / 1024 / 1024 mb_total
FROM
v$tablespace B,
v$tempfile C
WHERE B.ts#= C.ts#
GROUP BY B.name, C.block_size
) F,
(
SELECT
B.name,
max(blocks) max_blocks,
sum(blocks) total_blocks
FROM
v$tablespace B,
v$tempfile C
WHERE
B.ts#= C.ts#
GROUP BY B.name
) G
WHERE
ss.tablespace_name = D.tablespace_name and
ss.tablespace_name = F.name and
ss.tablespace_name = G.name;
Under the heading "Required and Suggested Parameters for init.ora, Oracle 11.2.0", the following entry:
db_file_multiblock_read_count := required to be = 16
should read:
db_file_multiblock_read_count := required to be >= 16
Note: The required change is ">=" before the number "16"
Add the following required open port:
Step 4: The following bullet should be removed, as the truth_data.tar.gz is no longer a valid file:
Chapter 8: Satellite Installation
Remove the following bullet:
Under the heading "Uninstall a Single Core in a Multimaster Mesh", remove step 1a. This step is no longer required.
SA 9.10 User Guide: Application Configuration
typo in table 10, row 1. "... where the value will be stored in the value wet." It should say, "... where the value will be stored in the value set.”
For the RejectResponseUrl tag the range is wrong:
r'
(HTTP_URLSCAN_STATUS_HEADER)|(
HTTP_URLSCAN_ORIGINAL_VERB)|(H
TTP_URLSCAN_ORIGINAL_URL)';optional@
It should use double quotes instead of single:
r"
(HTTP_URLSCAN_STATUS_HEADER)|(
HTTP_URLSCAN_ORIGINAL_VERB)|(H
TTP_URLSCAN_ORIGINAL_URL)”;optional@
Delete [Options] and replace with [AllowExtensions]
Replace the sentence:
"The field delimiter used here will be an end of line element which instructs the parser stop reading an entry when it encounters the end of a line."
With the following sentence:
"The field delimiter used here will be an end of line element which instructs the parser to stop reading an entry when it encounters the end of a line."
Replace this in the Description column:
"sequence-delimiter=":"
Instructs the parser to read a colon ( : ) as part of the string and the point at which to move on to the next entry."
With the following:
"field-delimiter-is-eol
Instructs the parser to read the next entry up to the end of the line. "
Replace this sentence:
"Next type the following CML replace tags to define the three kay value."
With this sentence:
"Next type the following CML replace tags to define the three-key value."
Replace this sentence:
"The filename-key value is a pathname. It must start with a slash."
With this sentence:
"The filename-key value is a pathname. It does not have to begin with a slash."
Replace this range:
1024<=,<=2048
With this range:
1024<=&<=2048
Replace this sequence:
"/examples/namespace/ip"
With this one:
"/example/namespace/ipaddress = 192.168.0.1"
Replace this sentence:
"Source: The source attribute is the database key"
With this sentence:
"Source: The source attribute is the key."
Replace this sentence:
"The only required element in a replace tag is the source"
With this one:
"The only required element in a loop tag is the source"
Replace this sentence:
"The filename-key value is a pathname. It must start with a slash."
With this sentence:
"The filename-key value is a pathname. It can be written as a relative path and does not need to begin with a slash (/).""sequence-delimiter-iswhitespace"
With this one:
"sequence-delimiter-is-whitespace"
" sequence-delimiter-issemicolon "
With this one:
"sequence-delimiter-is-semicolon "
The delimiter Attribute
whitespace-delimited
comma-delimited
semicolon-delimited
tab-delimited
quote-delimited
delimiterInstruction Tag Syntax
@!whitespace-delimited@
@!comma-delimited@
@!semicolon-delimited@
@!tab-delimited@
@!quote-delimited@
@!delimiter={string}@
whitespace-delimited is the default behaviorOption Attribute Syntax
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;whitespace-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;comma-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;semicolon-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;tab-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;quote-delimited[;{option}]...]]]]@
@[{level}]{tag-type}[[{source}][;[{type}][;[{range}][;delimiter={string}[;{option}]...]]]]@whitespace-delimited is the default behavior.
Description
delimiter sets the default delimiter character. If not explicitly specified, sequence-delimiter and field-delimiter will inherit this value.
Valid for replace and sequence tags.
Complete HP-UX OS Provisioning instructions are provided in the SA HP-UX OS Provisioning Whitepaper, which can be downloaded for any relevant SA 9.x release from the HP Support Self-Solve website: http://support.openview.hp.com/selfsolve/manuals .
In chapter 4:
Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import -manual
With this statement:
Use the following command to display additional information about cluster commands:
/opt/opsware/solpatch_import/bin/solpatch_import --manual
When Agent uninstall is attempted on a core machine and the --force uninstall option is not provided, the following warning is prompted:
WARNING: The server is owned by the OPSWARE account. Probably it is a core machine.
Are you sure you want to uninstall the Opsware Agent? [y/n]:
If the 'n' option is selected, the Agent uninstall is aborted. Otherwise, the uninstall proceeds.
When installing the Agent on a core machine that already has the Agent installed and the --coreinstall installer option is not provided, the installation is aborted with the following error message:
You are trying to install the agent on a core machine without passing the --coreinstall argument.
Installing the opsh RPM places the OGFS shell and the Agent Upgrade Tool in the directory /opt/opsware/opsh/bin.
# cd /opt/opsware/opsh/bin
From an Open Firmware prompt, enter:
0 > boot net:,yaboot,,
This retrieves the yaboot boot loader and the boot menu is displayed:
"Choose a boot image by entering the appropriate label at the 'boot:' prompt.
linux5 - Linux Build Agent (RHEL 5.8-based)
linux6 - Linux Build Agent (RHEL 6.3-based)
Welcome to yaboot version 1.3.17
Enter "help" to get some basic usage information
boot:"
Please note the following documentation errors:
SA 9.1x support for BSAE 2.0, 2.01, and 9.12 was misstated in previous versions of the SA 9.1x Support and Compatibility Matrix.
In the HP BSA Essentials column in the Cross-Product Compatibility section, remove all references to the following: 2.0, 2.01, 9.12.
This section contains additions to existing documentation.
Enabling IBM POWER6 Provisioning with the DHCPD Tool
Due to hardware constraints, IBM POWER6 servers cannot be provisioned using the normal OS Provisioning procedures. However, you can enable provisioning for these servers using the dhcpdtool provided with SA.
This involves using the dhcpdtool to set a parameter in the initial subnet declaration which enables Linux OS provisioning on the IBM POWER6 server's hardware. This workaround also requires that SA be in Full DHCP Management mode.
Note: Setting this parameter prevents Solaris SPARC OS provisioning. You will see a warning message to this effect when you change the parameter.
Perform the following tasks to enable Linux OS Provisioning on IBM POWER6 hardware:
1. Start dhcpdtool.
/opt/opsware/dhcpd/sbin/dhcpdtool
2. Select Full DHCP Management.3. Select the network for which the workaround is to be applied. An editing menu is displayed:
Opsware DHCP Network Configuration
Editing DHCP information for 192.168.208.160/27 (255.255.255.224)
1) gateway : 192.168.208.161
2) DHCP range : 192.168.208.163 - 192.168.208.190
3) DNS servers: 192.168.194.4
4) DNS domain : dev.opsware.com
5) Power6 provisioning override: No
!!! WARNING: Option 5) breaks Solaris SPARC OS provisioning !!!
!!! Make sure to deactivate this option before trying to provision a Solaris SPARC machine !!!1..5 to edit option.
d)elete network and return to main menu.
k)eep network and return to main menu.Choice [1..5, d, k]:
4. Select option 5 and press ENTER
5. The message “Are you sure that you want to toggle POWER6 provisioning although it breaks Solaris SPARC provisioning (Enable/Disable)?” is displayed
6. Press E to Enable POWER6 provisioning, D to Disable, select K to keep the settings, then S to save them.
7. Exit the DHCPD tool. Upon exiting, the DHCPD server is restarted and the new setting takes effect.
Note: If you are not using the SA-provided DHCPD server, you must add the following line to the subnet in which POWER6 you will perform OS provisioning:
filename "yaboot";
Chapter 8: Satellite Installation
- word_tmp_dir: directory where Package Repository will temporarily place content during uploads
- word.store.host: the host name of the server where Software Repository content is stored.
- media_server.windows_share_name: the share name to use for the Windows media sharing server (note: share names that are longer than 8 characters may give errors while browsing or may not be accessible to some older clients.)
- media_server.windows_share_password: the password to write-protect the Windows media share. Import_media tool will prompt for this password each time it is run.
Satellite Free Disk Space Requirements
This section describes the free disk space (in addition to the operating files system) requirements for any SA Satellite.
Satellite Component Directory | Recommended Free Disk Space |
---|---|
/opt/opsware | 15 GB |
/var/log/opsware | 10 GB |
/var/opt/opsware | 20 GB
(dependent on caching plans and the core cache size) |
/osmedia | 15 GB
(dependent on OS Provisioning needs) |
The first bullet should read:
" The tnsnames.ora file must reside in the following locations:
The Audit Trail is housed in the AUDIT_DATA tablespace, and contains the following tables:
AUDIT_OBJTYPE_ATTR
AUDIT_OBJECT_TYPES
AUDIT_OBJECT_COLLECTORS
AUDIT_OBJECT_ATTR
AUDIT_FEATURES
AUDIT_EVENT_OBJECTS
AUDIT_EVENT_DETAIL_VALUES
AUDIT_EVENT_DETAILS
AUDIT_EVENTS
AUDIT_DATA_TYPES
AUDIT_DATA_OBJECTS
AUDIT_DATAOBJ_VALUES
AUDIT_CONFIG_PARAMS
AUDIT_COMPONENTS
AUDIT_ACTIONS
Add the following custom attribute to Table 9:
Timeout
Values: the number of minutes to wait for Linux provisioning to complete before timing out.
Default: 30 minutes
If Linux provisioning fails because the job takes too long to complete, you can specify a longer timeout period.
Back to the Table of Contents
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
To access the Self-Solve knowledge base, visit the Self-Solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP
Passport Registration.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
© Copyright 2000-2014 Hewlett-Packard Development Company, L.P.
Adobe® is a trademark of Adobe Systems Incorporated.
Intel® and Itanium®
are trademarks of Intel Corporation in the U.S. and other
countries.
Microsoft®, Windows®‚ Windows® XP are U.S. registered trademarks
of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle
and/or its affiliates.
UNIX® is a registered trademark of The Open
Group.
New Publication Date | Change |
March 26, 2014 | Added errata in the Administration Guide re: audit trails. |
May 10, 2014 | Added information about job loss during upgrade or rollback in the upgrade and rollback sections, and in the Known Issues Table, issue QCCR1D183132. |
To check for recent updates or to verify that you are using the most recent
edition of a document, go to:
http://support.openview.hp.com/selfsolve/manuals
This site
requires that you register for an HP Passport and sign in.
Or click the New
users - please register link on the HP Passport login page. You will also
receive updated or new editions if you subscribe to the appropriate product
support service.
Contact your HP sales representative for details.
Back to the Table of Contents