What's New

Installation

Known Issues

Fixed Issues

Documentation Errata

HP Software Support

Legal Notices

7.8x (7.81, 7.82, etc.)

7.85

1. patch_database.sh
2. patch_opsware.sh
3. patch_contents.sh

1. prepatch.sh
2. patch_database.sh
3. patch_opsware.sh
4. patch_contents.sh

1. patch_database.sh
2. patch_opsware.sh
3. patch_contents.sh

1. prepatch.sh
2. patch_database.sh
3. patch_opsware.sh
4. patch_contents.sh

1. patch_database.sh
2. patch_opsware.sh
3. patch_contents.sh

1. prepatch.sh
2. patch_database.sh
3. patch_opsware.sh
4. patch_contents.sh

1. patch_database.sh
2. patch_opsware.sh
3. patch_contents.sh

1. patch_opsware.sh
2. patch_database.sh

--listmrls, -l

List all Windows Server 2008 x64 MRLs (ID, Name and Media Path)

--MRL=<MRL ID>

Migrate the MRL with the specified ID to the Windows Server 2008 R2 x64 platform.
Can be specified multiple times.

--help, -h

Display usage and help

All platforms where Unicode is used

Unicode directory names are not supported for the root level directory assigned to a synchronization service. ASCII characters only should be used for this folder/directory name.

During patch_contents installation, following a core recertification, the process may fail with this error:

Verifying OCC available: FAILURE (Certificate file /var/opt/opsware/crypto/word_uploads/wordbot.srv does not exist)

Linux,
Solaris

Use the following procedures to update the crypto for word_uploads, then restart the patch_contents script:

cp /var/opt/opsware/crypto/spin/admin-ca.crt /var/opt/opsware/crypto/word_uploads/
cp /var/opt/opsware/crypto/spin/opsware-ca.crt /var/opt/opsware/crypto/word_uploads/
cp /var/opt/opsware/crypto/spin/agent-ca.crt /var/opt/opsware/crypto/word_uploads/
cp /var/opt/opsware/crypto/wordbot/wordbot.srv /var/opt/opsware/crypto/word_uploads/

None

Note: There is an OEM bug about some tablespaces showing the incorrect used size. The Database Scanner for Oracle gets the tablespace used size directly from all of its data files, which avoid the OEM bug.

Install uudecode utility.

In order to monitor an Oracle 11G database with the SA Oracle Database Scanner, the XML DB and DBMS_NETWORK_ACL_ADMIN package must exist in the database.  The SA Oracle DB Scanner needs access to these objects in order to grant privileges and access for itself. If the objects do not exist, then the "pamuserprivilege.sql" will fail and the DB Scanner cannot be run.   An application may or may not install these objects in its Oracle 11G database.

The following error might be displayed under these circumstances:

"PLS-00905: object SYS.DBMS_NETWORK_ACL_ADMIN is invalid". 

Before executing the SA DB Scanner "pamuserprivilege.sql" in the Oracle database, first perform the following steps to install the XML DB and DBMS_NETWORK_ACL_ADMIN package in the Oracle 11G database.

1. cd $ORACLE_HOME/rdbms/admin
2. sqlplus /nolog
3. SQL> connect <sys_user>/<password> as sysdba
4. SQL> spool install_xml.log
5. SQL> @catqm xdb sysaux temp NO
6. SQL> @dbmsnacl.sql
7. SQL> spool off;

In the SA Web Client:

1. Log in as administrator (opsware admin user) and
   navigate to Environment -> Customer -> Opsware ->
   Custom Attributes -> CORD_OPSWwayscripts.
2. Identify the SA core server by checking the value field
   of the custom attribute CORD_OPSWway scripts.
3. Log in to the SA Core server you identified in step 1
   and execute the following commands:
   cd /var/opt/opsware/OPSWpatch/OPSWwayscripts
/scripts./post_after_startup.sh
4. Apply any required hotfixes to the wayscripts.

SA failed to reload Platforms UnitTypes list. An ocli.badParameters error is displayed.

To avoid this error:

1. Apply the patch.
2. Stop and restart SA
3. Upload content.

WinPatching MBSA patch database may import extra language-specific patch binaries for languages that are not relevant to your server’s locale. This issue is due to some patches being applicable to products that have a Multilingual Interface (MUI) that is different from the operating system's locale.

Run a Patch Compliance Scan after downloading the patch metadata and before downloading the patch binaries. This filters the patch metadata more granularly than the initial metadata import process, including evaluating the OS and MUI patch applicability on target servers.
                                             
Steps:

1. Import the Windows Patch metadata to the SA Model Repository.
2. Run a Patch Compliance Scan.
3. Download the Windows Patch binaries needed for your environment.

If the workstation service is not started on the managed server, the mbsacli.exe executable fails to run and the system returns a 997 error.

The solpatch_import –filter option does not display recommended and/or security patches if they had previously been marked obsolete. This became an issue on June 4, 2010 when Oracle changed the criteria for recommended and security patches (described here: http://blogs.sun.com/patch/entry/merging_the_solaris_recommended_and).

Users with an existing metadata database (solpatchdb) must delete the solpatchdb.zip, solpatchdb-old.zip and solpatchdb_supplement.zip files and run create_db to have support for recommended obsolete patches.

You must recreate the Solaris patch metadata database (solpatchdb) if the following are true:

• You use the solpatch_import –filter option.
• You have run solpatch_import –update_db on June 4, 2010 or later.
  

After you have installed the patch, perform these tasks to recreate the metadata database (solpatchdb):

1. Log in to the SA Client.
2. Select Library in the Navigation pane.
3. Select By Folder.
   
4. Navigate to /Opsware/Tools/Solaris Patching.
5. Delete the following files:
   

   solpatchdb.zip
solpatchdb-old.zip
solpatchdb_supplement.zip
   

6. Follow the steps to create a new metadata database (solpatchdb) as described in the SA User Guide: Application Automation, Patch Management for Solaris.

For upgrades only:
Due to Oracle's acquisition of Sun Microsystems, if you were previously accessing the SunSolve website and you migrated your Sun account to an Oracle account instead, your solpatch_import.conf file is out of date and must be updated to reflect that change.

To update your solpatch_import.conf file:

• URL changes: Log on to the core and make the following changes to the solpatch_import.conf file for the lines that begin with patch_url, patch_readme_url, patchdiag_xref_src, cluster_url, cluster_readme_url, bundle_url, and bundle_readme_url:
  

patch_url=https://getupdates.oracle.com/all_unsigned/${patch_name}.zip
patch_readme_url=https://getupdates.oracle.com/readme/${patch_name}
patchdiag_xref_src=https://getupdates.oracle.com/reports/patchdiag.xref
cluster_url=https://getupdates.oracle.com/patch_cluster/${cluster_filename}
cluster_readme_url=https://getupdates.oracle.com/patch_cluster/${cluster_basename}.README
bundle_url=https://getupdates.oracle.com/patch_cluster/${chunk_filename}
bundle_readme_url=https://getupdates.oracle.com/patch_cluster/${chunk_basename}.README

• User name and password changes: Update the following lines with your new Oracle account user name and password:

download_user=xxxxx
download_pass=xxxxx

After rolling back the SA 7.88 patch, the contents of /etc/opt/opsware/dhcpd/dhcpd_subnets.conf may not reflect the latest modifications done with dhcpdtool while SA 7.88 was installed.

Note: This workaround will not work if SA 7.88 has already been rolled back.

Before rolling back SA 7.88, perform the following tasks:

1. Remove /etc/opt/opsware/dhcpd/dhcpd_subnets.conf.CORD_BACKUP.
2. Issue the following command to replace range dynamic-bootp with range in /etc/opt/opsware/dhcpd/dhcpd_subnets:
   perl -pi -e 's/range dynamic-bootp/range/g' /etc/opt/opsware/dhcpd/dhcpd_subnets.conf
   

When a managed server on which SE Connector is running is directly deactivated and deleted, stale entries of storage scanners will display in the Storage Scanner panel. The stale entries count will increase, depending on how many times the managed server is deactivated and deleted from the SA core.

An EMC Symmetrix array that is discovered through SE Connector can report more than one storage volume with the same LUN number presented to a managed server.

Running the storage snapshot specification on the managed server will succeed; however, the Inventory > Storage > File Systems and Inventory > Storage > Managed Software panels will be empty.

Also, some host volumes with a LUN service type will not be displayed in the Storage > Inventory > Volumes panel. For the EMC storage array in the Relationships > Storage Initiators panel for this managed server, there will be more than one volume that has the same LUN number.

When you open Access Controls from Storage Scanner SE Scanner, the following error is displayed:
"The new Java plugin requires Firefox 3 or later."

This error occurs whether or not Firefox is installed on the client. You can safely ignore the error.

Run level for services node under zSeries does not set or disable correctly

When you import the Software Repository (found in /var/opt/opsware/word/mmword_local/packages/any/nt/$OS_VER$) to the non-local disk, the import takes longer than expected to complete for all mounted binaries.

On Windows servers that have EMC PowerPath installed as the multipathing software, the SCSI Bus number provided by PowerPath (using the powermt command) does not match the bus number of the disks (LUNs). In these cases, LUNs are displayed as ROOT and display alongside LUNs that are correctly displayed in the Inventory > Storage > Volumes Panel.

Log on to the Windows server. Open the Disk Management panel and import the disks that are categorized as Foreign. Run the storage snapshot specification from the SA Web client for this server.

For more information on importing disks on Windows servers, see the relevant Microsoft documentation at: http://www.microsoft.com.

The Storage File systems panel does not display root(/) and /boot mount points.

Server Automation: A host operating system may report a stale LUN as having a Root service type because the system could not detect storage changes.

When you add a mirror to concatenated or stripe, the volume display labels both as "Mirrored" and does not distinguish between concatenated or striped in the label. Note that "Mirrored Concatenated" and "Mirror Striped" are distinct on the volume manager on the host, such as on the Veritas Volume Manager.
The type of the volume manager might not match the native tool, such as the Veritas Volume Manager. The STORAGE_TYPE value is the immediate node in the supply graph, which is the storage type of the most decendent volume.

None

The file system is not shown on the server storage file system panel when the partition and format on the Windows server is mounted to an empty NTFS folder.

None

Note: The Storage Host Agent Extension does not report file systems that have non-drive letter mount points. The Storage Host Agent Extension does not report file systems that have multiple mount points.

After you remove a LUN mapping, the old LUN mapping information still displays in the SAN array volume view and in the server storage volume view. An additional access path is displayed in the SAN array volume view (Access Path subview) for the volume for which LUN mapping was removed. The access path that shows no initiator device and/or initiator port information is the correct one.

In the APX Logical Volume Manager (LVM) configuration wizard:
* Physical disks are not removed from the list after they come under LVM control.
* Unable to create volume groups from physical disks under LVM control.

RHEL6 (x32,x64)

On a Windows 2003 server with the SNIA library from QLogic, Fibre Channel Adapter and storage volume information might not be discovered by the Storage Host Agent Extension, causing fibreproxy.exe to stop responding.

For Windows Server 2003 and Microsoft Windows 2000 operating systems, use the native Microsoft SNIA library instead of the SNIA that is provided by the QLogic driver. Download the Fibre Channel Information Tool to add the Microsoft HBAAPI support to the operating system. For Windows 2003 SP1 or later, the Microsoft HBAAPI support is built in. If the SNIA's version of hbaapi.dll is installed on the operating system, remove it.

In APX to configure LVM, creation of multilevel RAID volumes (RAID10) is making the complete wizard unusable  "Error: Linux_LVM.vg3./dev/vg3/mrlv02  "

In the APX to configure LVM, if firewall is enabled on managed Server, none of the options operate. It throws error in the status fields.

Disable firewall and click Refresh .

In APX to configure LVM, if the user does not have permissions, then embedded browser does not display proper message in the pop up.

The PyTwist library contains some inconsistent attribute names with the attribute names of the objects returned from an API call.

The following attributes list contains the inconsistent attributes:

- class: "com.opsware.apx.APXVersionRef", attributes: "aPXType"
- class: "com.opsware.apx.APXVersionVO", attributes: "aPX"
- class: "com.opsware.apx.NoCurrentVersionException", attributes: "aPX"
- class: "com.opsware.apx.ProgramAPXJobInfoVO", attributes: "aPX"
- class: "com.opsware.apx.ProgramAPXVersionRef", attributes: "aPXType"
- class: "com.opsware.apx.UnApprovedVersionException", attributes: "aPX"
- class: "com.opsware.apx.UniqueVersionLabelException", attributes: "aPX"
- class: "com.opsware.apx.WebAPXVersionRef", attributes: "aPXType"
- class: "com.opsware.busapp.BusinessAppContact", attributes: "vCardData"
- class: "com.opsware.compliance.sco.policy.AppConfigRule", attributes: "cML"
- class: "com.opsware.compliance.sco.policy.FileCMLMapping", attributes: "cML"
- class: "com.opsware.compliance.sco.policy.SMORule", attributes: "cFL"
- class: "com.opsware.compliance.sco.AuditPolicy", attributes: "sCOPolicy"
- class: "com.opsware.fido.apx.APXAuthorizationDeniedException", attributes: "aPXId"
- class: "com.opsware.fido.apx.APXPermissionExistException", attributes: "aPXId", "aPXVersionId"
- class: "com.opsware.fido.apx.APXPermissionNotFoundException", attributes: "aPXId", "aPXVersionId"
- class: "com.opsware.fido.apx.APXSecurityException", attributes: "aPXContext"
- class: "com.opsware.fido.MissingPermissionsException", attributes: "sQL"
- class: "com.opsware.fido.TablePermissionsMissingException", attributes: "sQL"
- class: "com.opsware.nas.IPAddressInfo", attributes: "iPType"
- class: "com.opsware.nas.NetworkACLVO", attributes: "aCLId", "aCLType"
- class: "com.opsware.nas.NetworkDeviceVO", attributes: "nATIPAddress", "nATRealmName", "rOMVersion", "tFTPServerIPAddress"
- class: "com.opsware.osprov.AutomaticProvisioningRule", attributes: "oSSequence"
- class: "com.opsware.osprov.OSSequenceJobInfoVO", attributes: "oSSequenceJobParams"
- class: "com.opsware.osprov.OSSequenceJobParams", attributes: "oSSequence"
- class: "com.opsware.pkg.aix.BaseFilesetVO", attributes: "lPP"
- class: "com.opsware.pkg.aix.UpdateFilesetVO", attributes: "lPP"
- class: "com.opsware.pkg.RelocatableZIPVO", attributes: "zIP"
- class: "com.opsware.script.OGFSScriptJobArgs", attributes: "xArgs"
- class: "com.opsware.shared.TwistConsoleService", attributes: "aPIVersion", "aPIVersionLabel"
- class: "com.opsware.storage.DeviceInitiatorView", attributes: "mPIO", "mPIOVersion"
- class: "com.opsware.storage.LogicalVolumeTargetView", attributes: "mPIO", "mPIOVersion"
- class: "com.opsware.storage.StorageInitiatorSummary", attributes: "sANVolumeCapacity"
- class: "com.opsware.swmgmt.ismcontrol.ISMData", attributes: "iSMAppName"
- class: "com.opsware.swmgmt.ismcontrol.RunISMControlJobArgument", attributes: "iSMControl"
- class: "com.opsware.system.recert.CoreRecertPhaseArgument", attributes: "cADBPassword"
- class: "com.opsware.virtualization.microsoft.HyperVConfigDetailsVO", attributes: "bIOSBootOrder", "vMLocation"
- class: "com.opsware.virtualization.microsoft.HyperVHypervisorVO", attributes: "vMDefaultConfigLocation", "vMDefaultDiskLocation"
- class: "com.opsware.virtualization.microsoft.HyperVVMJobInfoVO", attributes: "vMConfigDetailsVO"
- class: "com.opsware.virtualization.vmware.VMJobElementProgress", attributes: "vMJobData"
- class: "com.opsware.virtualization.vmware.VMJobElementResult", attributes: "vMJobData"
- class: "com.opsware.virtualization.vmware.VMJobInfoVO", attributes: "vMConfigDetailsVO"
- class: "com.opsware.virtualization.vmware.VMJobProgress", attributes: "vMJobData"

If one of these object types is created on the client side, the attribute name will be displayed as shown in the inconsistent attribute list.
If one of the object types is returned from an API call, the attribute present in the inconsistent attribute list will have a slightly different name (same letters, but the first letter will be capitalized, for example: "APXType", "APX", "VCardData", "CML").

For example:
This inconsistent attribute issue affects the PyTwist's AuditPolicy class. When an AuditPolicy object is created on the client side using the PyTwist library, the object attribute name is "sCOPolicy", but when an AuditPolicy object is returned by an API call, the attribute name is "SCOPolicy" . This causes an AttributeError (on the object returned from the server) if the "getSCOPolicy()" method or the "sCOPolicy" attribute is invoked.

Due to a documentation error, AIX 5.2 was previously listed as a supported platform for the SSI feature. The SSI feature is not compatible with AIX 5.2.

Remove the following section:

Software Repository URL
https://theword.%3cdata_center%3e:1003/

The following steps are obsolete:

Step 1: An SA user launches ODAD from the SA Client and selects a scan location. The scan location
determines which Agent Deployment Helper will perform the scan. Each Gateway can act as an Agent
Deployment Helper.

Step 6a (under the heading "For Windows"): The Windows Agent Deployment Helper establishes a tunnel via the Gateway mesh to the server, then proceeds through the same steps as for Unix.

The permissions requirements should be:

-> Read access to facilities where you will scan for servers and manage servers.
-> Features > Managed Servers and Groups must be enabled.
-> Client Features > Unmanaged Servers > Allow Manage Server set to Yes.
-> Client Features > Unmanaged Servers > Allow Scan Network set to Yes.
-> Read access must be set to customer Opsware.

The last five Read permissions listed are no longer required.

Add the following bullet to Step 4:

• In the field CronbotMailAlertsEnabled specify the value 1 to enable cronbot email alerts. To disable cronbot email alerts, specify the value 0.
  

The following line:

c. In the command window, enter the following command on a single line:

set PATH=%PATH%;%SYSTEMDRIVE%\Program Files\Loudcloud\lcpython15

should read:

c. In the command window, enter the following command on a single line:

set PATH=%PATH%;%SYSTEMDRIVE%\Program Files\Opsware\Agent\lcpython15

In the list of parameters the following entries are not required:

query_rewrite_integrity=TRUSTED
query_rewrite_enabled=true

Replace path 1 (wrong) with path 2 (correct):

1. ./create_local_dc_table.sh <oracle_home> <oracle_sid>

REPLACE WITH:

2. ./truth_create_local_dc_table.sh <oracle_home> <oracle_sid>

Replace path 1 (wrong) with path 2 (correct):

1. ./create_local_dc_table_rollback.sh <oracle_home> <oracle_sid>

REPLACE WITH:

2. ./truth_create_local_dc_table_rollback.sh <oracle_home> <oracle_sid>

Replace entry 1 (wrong) with entry 2 (correct):

1.
%packages
@Base

REPLACE WITH:

2.
%packages --resolvedeps
@Base

The corrected entry ensures that all prerequisite packages are available for provisioning.

Chapter 1, section:
SA Core Component Bundling

First paragraph

Replace sentence 1 (wrong) with sentence 2 (correct):

1. During a Custom installation, certain components can be broken out of their bundles (such as the Command Engine, the OS Provisioning Boot Server and Media Server, among others) and installed on separate servers.

REPLACE WITH:

2. During a Custom installation, certain components can be broken out of their bundles (such as the Software Repository Store, Slice Component bundle, OS Provisioning Media Server, OS Provisioning Boot Server etc.) and installed on separate servers.

Chapter 2, section: Pre-Installation Requirements, sub-section: SUSE Linux Enterprise Server 10 Package Requirements

Add the following to the section:

The following packages must not be installed on a SUSE Linux Enterprise Server 10 hosting an SA Core:
yast2-dhcp-server
rsync
samba
samba-32bit
yast2-samba-server
yast2-tftp-server

These packages are reinstalled during an operating system upgrade from SP2 to SP3 and therefore must be removed for proper SA Core operation.

Chapter 3, section:
Solaris Requirements

Table 11: Packages Required for Solaris

Chapter 3, section:
Pre-Installation Requirements

Table 18: Pre-Installation Requirements

Add the following at the bottom of the table, under the heading: Firewall Considerations:

• Port 1521 is the default Oracle listener (listener.ora) port, but you can specify a different port in your Oracle configuration. In case your installation has been modified to use a port other than 1521, you should verify the port number from the Oracle listener status and ensure that your firewall is configured to allow the correct port to be open for the Oracle listener.
• SA's data access layers (infrastructure) use connection pooling to the database. The connections between the database and the infrastructure layer must be maintained as long as SA is up and running. Ensure that your firewall is configured so that these connections do not time out and terminate the connections between the database and the infrastructure layers.

Chapter 3, section:
SUSE Enterprise Server 10 Requirements

Add the following requirements to this section (Add the package requirements for SUSE Enterprise Server 10 64-bit x_86, an SA Core Server (Linux) to the section. All packages have the x86_64 architecture.):

binutils
cpp
desktop-file-utils
expat
gcc-c++
gcc
glibc
glibc-32bit
glibc-devel
glibc-devel-32bit
iptables
kernel-smp
kernel-source
libaio
libaio-32bit
libaio-devel
libcap
libcap-32bit
libelf
libgcc
libstdc++
libstdc++-devel
libpng
libpng-32bit
libxml2


libxml2-32bit
libxml2-python
make
mDNSResponder-lib
mkisofs
ncompress
nfs-utils
patch
popt
popt-32bit
readline
readline-32bit
rpm
sharutils
strace
sysstat
termcap
unzip
vim
xinetd
xntp
xorg-x11-libs
xorg-x11-libs-32bit
xorg-x11
xterm
zip
zlib
zlib-32bit

Chapter 3, section:
SUSE Enterprise Server 10 Requirements

Add the following table and its contents:
Packages that are Not Supported on SUSE Linux Enterprise Server 10 Core Hosts

rsync
samba
samba-32bit
yast2-dhcp-server
yast2-samba-server
yast2-tftp-server

These packages are reinstalled during an operating system upgrade from SUSE Enterprise Linux SP2 to SP3 and therefore must be removed for proper SA Core operation after upgrade.

Appendix A

Table 42: Supported Operating Systems and Oracle Versions

Replace the first entry with the second one:

SunOS 10 x86_64

REPLACE WITH:

SunOS 10 (SPARC)-64 bit.

In the bullet entry that reads:
"Free /tmp space should be 400MB or more.
You can use the following command to check /tmp space:"

INCORRECT COMMAND:
df -k /tmp | grep / | awk '{ print $3 }'

REPLACE WITH:
df -k /tmp | grep / | awk '{ print $4 }'

The following init.ora parameters should have the specified required values:

• Both Oracle 10g and 11g
  optimizer_mode=all_rows
  session_cached_cursors>=50
  
• Oracle 10g only
  open_cursors>=300
  remote_login_passwordfile=EXCLUSIVE
  
• Oracle 11g only
  open_cursors>=1000
  memory_target=1616M
  

Add the following note:

For Oracle 11g, the typical number of open file descriptors used under normal usage has increased. For larger systems, HP recommends that you increase the value of fs.file-max. The recommended value is fs.file-max = 681574.

Change the following entry in the Oracle parameter list:

fs.file-max=65536

REPLACE WITH:

fs.file-max = 681574

The following information is in addition to that found in the SA Planning and Installation Guide: Appendix A and the document, Oracle Setup for the Model Repository.

Concurrent with the SA 7.82 patch release, SA adds support for Oracle Real Application Clusters (RAC).

Note: Oracle RAC support requires a new installation of both Oracle and SA. Therefore, in order to enable Oracle RAC support in SA, you must first install SA 7.80 and Oracle 10.2.0.4 or 11.1.0.7 configured as described in the following sections.

Supported Oracle Versions Matrix

Supported Oracle Enterprise Edition Versions: 10.2.0.4, 11.1.0.7

Supported Operating Systems: Red Hat Enterprise Linux AS 4 x86_64 and 5 x86_64

Set up the Oracle RAC Database/Instances

SA supports any valid Oracle RAC configuration, such as any number of nodes, ASM or regular disks, and so on.
However, SA requires that the Oracle database be configured for use with SA. You will require your Oracle DBA's help to configure the Oracle RAC/instances, the required initialization parameters, the required tablespaces, the opsware_admin database user, and the listener.ora and tnsnames.ora files.
You can also run the truth_oracle_state_checker script to check if the initialization parameters are set correctly. The truth_oracle_state_checker file is located in the distribution /tools directory.

1. Create the Database with the Required Initialization Parameters.
   Before installing Oracle, the following scripts must be run and init.ora must have certain parameter values edited or added as shown in Required and Suggested Parameters for init.ora on page 143.
   • Create a database with the UTF8 character set (as required by SA), the data and index files, the default temporary tablespace, the undo tablespace, and the log files.
     
2. Create the required table spaces
   
   • Create the following tablespaces that are required by SA:
     LCREP_DATA
     LCREP_INDX
     TRUTH_DATA
     TRUTH_INDX
     AAA_DATA
     AAA_INDX
     AUDIT_DATA
     AUDIT_INDX
     STRG_DATA
     STRG_INDX
     

   See "Tablespace Sizes" in the SA Planning and Installation Guide for additional tablespace sizing information.

3. Required and Suggested Parameters for init.ora.
   • The file init.ora must be edited as follows:
     (Both Oracle 10g and 11g) For SA, the following init.ora entries are either suggested or required:

   log_buffer>=1048576
db_block_size>=8192
session_cached_cursors=>50
nls_length_semantics=CHAR
nls_sort=GENERIC_M
processes >=1024
undo_management=AUTO (Suggested)
undo_tablespace=UNDO (Suggested)
query_rewrite_integrity=TRUSTED
query_rewrite_enabled=true
optimizer_mode=all_rows
optimizer_index_cost_adj=20
optimizer_index_caching=80
cursor_sharing=SIMILAR (value can be set to SIMILAR(preferred) or EXACT, recommended only if you encounter an Oracle error)
recyclebin=OFF
event="12099 trace name context forever, level 1"
_complex_view_merging=false

   (Oracle 10g only) For SA, the following init.ora entries are either suggested or required:

   open_cursors >=300
sga_max_size >=1GB
db_cache_size>=629145600
shared_pool_size>=262144000
java_pool_size>=52428800
large_pool_size>=52428800
job_queue_processes>=10
sessions >=1152
pga_aggregate_target >=104857600
workarea_size_policy=auto
remote_login_passwordfile=EXCLUSIVE

   (Oracle 11g only) For SA, the following init.ora entries are either suggested or required:

   memory_target=1616M
job_queue_processes>=1000 (default)
remote_login_passwordfile=EXCLUSIVE
   

4. Create the User opsware_admin.

   You can use the script, CreateUserOpsware_Admin.sql, to create the opsware_admin database user and grant permissions (privileges) to the user (required by SA) or create the user manually.
   If you plan to create the opsware_admin user manually, follow the procedure below:
   

   Manual Creation of the User Opsware_Admin
   To create the opsware_admin user after a manual Oracle installation, log in to SQL*Plus and enter the following:
   # Su - oracle
   # Sqlplus "/ as sysdba"

   SQL> create user opsware_admin identified by opsware_admin
default tablespace truth_data
temporary tablespace temp
quota unlimited on truth_data;

   SQL> grant alter session to opsware_admin with admin option;
grant create procedure to opsware_admin with admin option;
grant create public synonym to opsware_admin with admin option;
grant create sequence to opsware_admin with admin option;
grant create session to opsware_admin with admin option;
grant create table to opsware_admin with admin option;
grant create trigger to opsware_admin with admin option;
grant create type to opsware_admin with admin option;
grant create view to opsware_admin with admin option;
grant delete any table to opsware_admin with admin option;
grant drop public synonym to opsware_admin with admin option;
grant select any table to opsware_admin with admin option;
grant select_catalog_role to opsware_admin with admin option;
grant query rewrite to opsware_admin with admin option;
grant restricted session to opsware_admin with admin option;

   grant execute on dbms_utility to opsware_admin with grant option;
grant analyze any to opsware_admin;
grant insert, update, delete, select on sys.aux_stats$ to opsware_admin;
grant gather_system_statistics to opsware_admin;
grant create job to opsware_admin;

   grant alter system to opsware_admin;
grant create role to opsware_admin;
grant create user to opsware_admin;
grant alter user to opsware_admin;
grant drop user to opsware_admin;
grant create profile to opsware_admin;
grant alter profile to opsware_admin;
grant drop profile to opsware_admin;
   

Installing the Model Repository

In most production environments with Oracle RAC, the Model Repository installation can be done from any SA server. The database server or RAC nodes in this case are considered to be remote.

The examples used in the following sections assume this configuration:

Two (active-active) Node RAC environment:

# Public Network
192.168.173.210 rac1pub rac1pub.dev.opsware.com (instance_name=truth1,
db name=truth)
192.168.173.211 rac2pub rac2pub.dev.opsware.com (instance_name=truth2,
db name=truth)

# Private network
172.16.1.100 rac1prv rac1prv.dev.opsware.com
172.16.1.101 rac2prv rac2prv.dev.opsware.com

# Public Virtual IP (VIP)
192.168.173.212 rac1-vip rac1-vip.dev.opsware.com
192.168.173.213 rac2-vip rac2-vip.dev.opsware.com

SA server:
192.168.173.214 rac1sa.dev.opsware.com

Model Repository Installation on a Remote Database (truth) RAC Server

In an Oracle RAC environment, only one of the RAC nodes is used during the SA installation/upgrade process. The SA Installer connects to only one Oracle RAC instance to install/modify the Model Repository. During the regular SA operations, all RAC nodes are used.
Perform the following tasks on the SA server on which you will run the SA Installer, for example rac1sa.dev.opsware.com.

1. Model Repository Hostname Resolution

   On the server where you will run the SA Installer, ensure that the Model Repository hostname truth resolves to the remote database server, not to the server on which you will be running the SA Installer:

   In /etc/hosts, enter the public IP address of one of the RAC nodes/instances. For example the
   /etc/hosts file on rac1sa.dev.opsware.com would have the following entry:

   192.168.173.210 truth rac1pub rac1pub.dev.opsware.com

2. Install the Oracle 11g Full Client on the SA server
   1. The SA Installer will use the Oracle Full Client to connect to the SA server and install the Model Repository. Below are sample commands for installing the Oracle full client.
      

      Create user oracle for the Oracle Full Client installation:
root@rac1sa ~]# mkdir -p /u01/app/oracle
root@rac1sa ~]# mkdir -p /u01/app/oraInventory
root@rac1sa ~]# groupadd oinstall
root@rac1sa ~]# groupadd dba
root@rac1sa ~]# useradd -c "Oracle Client software owner" -g oinstall -G
dba -d /u01/app/oracle -s /bin/bash oracle
root@rac1sa ~]# chown -R oracle:oinstall /u01/app
root@rac1sa ~]# chmod -R 775 /u01/app
root@rac1sa ~]#passwd oracle (change oracle user password )

   2. Create the .bash_profile file.
      In /u01/app/oracle create the .bash_profile file.

      Note: Temporarily comment out ORACLE_HOME and ORACLE_PATH. You will uncomment these entries after the Oracle client installation is complete.
      

      Sample .bash_profile file
# .bash_profile

      # Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

      # User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH

      #SA-OracleRAC parameters begin
#unset USERNAME
export ORACLE_BASE=/u01/app/oracle
#export ORACLE_HOME=$ORACLE_BASE/product/11.1.0/client_1
#PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
export PATH

      if [ -t ]; then
stty intr ^C
fi

      umask 022
#SA-OracleRAC parameters end
   3. Install the Oracle Full Client
      Install the Oracle Full Client as described in your Oracle documentation. You can create a share to access the Oracle Full Client binaries.
   4. Set Up Terminals
      You will need two X window terminals to install the Oracle Full Client:

      Terminal 1: log in as root and enter the commands:

      Terminal 1> xhost +
Terminal 2: ssh –X oracle@<new_oracle_full_client_host>

   5. Start Oracle Full Client installation
      From Terminal 2 run the Oracle Universal Installer (OUI) installer. The Oracle Full Client is installed in:

      /u01/app/oracle/product/11.1.0/client_1

   6. Run the Oracle Universal Installer to install Oracle Full Client. The directories in this example assume an Oracle 11g Full Client on Linux.

      1. cd /location_of_oracle_full_client
      2. /runInstaller
      3. At the Welcome Screen, click Next.
      4. Specify the Inventory Directory and Credentials (/u01/app/oraInventory and /u01/app/oinstall)
      5. For Select Installation Type, choose Administrator, click Next.
      6. For ORACLE_BASE select: /u01/app/oracle, click Next.
      7. The Oracle Universal Installer performs some checks. If the checks are not successful, fix the issue and re-run this step. If the checks are successful the click Next.
      8. Oracle OUI will list of products that will be installed. Click Install.
      9. OUI will show the progress bar when installing.
      10. In the 'Welcome to Oracle Net Configuration Assistant' window click Next.
      11. Click Finish once the installation is complete.
      12. The following two configuration scripts need to be executed as "root" when the installation is complete:
          /u01/app/oraInventory/orainstRoot.sh
/u01/app/oracle/product/11.1.0/client_1/root.sh
   7. Verify that the .bash_profile file for user oracle is correct.
   8. Uncomment $ORACLE_HOME and $ORACLE_PATH.
      
3. Making changes to tnsnames.ora on SA server
   By default the tnsnames.ora file is located in /var/opt/oracle.
   
   1. Login as root on the SA Server.
   2. Enter the command:

      mkdir -p /var/opt/oracle

   3. Copy tnsnames.ora from the remote database server to the directory you created above. For the RAC environment, copy it from RAC Node 1 (for example, rac1pub.dev.opsware.com).

      The SA Installer puts the database in a restricted mode during the Model Repository installation. The database is removed from the restricted mode after successful installation/upgrade of the Model Repository. When the database is in restricted mode, only certain privileged users are allowed to connect to the database.

      To accommodate the remote Model Repository installation process, two sets of tnsnames.ora are required on the SA server.

      • tnsnames.ora-install_upgrade – this copy of tnsnames.ora is used during SA installation/upgrade. The file can be renamed.
      • tnsnames.ora-operational – this copy of tnsnames.ora is used during normal SA operation. The file can be renamed.
        

        You can use softlinks to point tnsnames.ora to either tnsnames.ora-install_upgrade or tnsnames.ora-operational.

      ln –s tnsnames.ora-install_upgrade tnsnames.ora

4. Changes to the tnsnames.ora-install_upgrade sample file.

   Make a note of the text that is in BOLD letters. The tnames.ora file should contain the SID and not the service name. These examples have TRUTH as the truth.servicename. Ensure that the HOST references the same server as the truth entry in /etc/hosts file. truth.servicename is case sensitive.

   # Generated by Oracle configuration tools.

   TRUTH =
   (DESCRIPTION =
   (ADDRESS = (PROTOCOL = TCP)(HOST = rac1pub.dev.opsware.com)(PORT = 1521))
   (CONNECT_DATA =
   (SID = truth1)
   )
   )

   LISTENER_TRUTH =
   (ADDRESS_LIST =
   (ADDRESS = (PROTOCOL = TCP)(HOST = rac1pub.dev.opsware.com)(PORT = 1521))
   (CONNECT_DATA =
   (SID = truth1)
   )
   )

   Use softlinks to link the file to tnsnames.ora.ora file. Do this before you start the SA Model Repository installation or upgrade ln –s tnsnames.ora-install_upgrade tnsnames.ora.

   Note: During installation the SA Installer adds a SA Gateway entry into tnsnames.ora (linked to tnsnames.ora.install-upgrade) file on the primary SA Core. When installation completes, copy this entry into the tnsname.ora.operational file. If this entry is not present in tnsname.ora.operational, Multimaster Mesh transactions will not flow. Below is a sample gateway entry from tnsnames.ora:

   Rac2sa_truth=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)(PORT=20002)
(PROTOCOL=tcp))(CONNECT_DATA=(SERVICE_NAME=truth)))

5. Making changes to listener.ora on one of the RAC node server (instance)

   In an Oracle RAC environment, only one of the RAC nodes or instances is used during installation/upgrade process. The SA Installer connects to only one Oracle instance to modify the Model Repository. During the regular SA operations, all the RAC nodes are used.

   The SA Installer puts the database in a restricted mode during the Model Repository installation. The database is removed from the restricted mode after successful installation/upgrade of the Model Repository. When the database is in restricted mode, only certain privileged users are allowed to connect. To accommodate the remote truth installation process, two sets of listener.ora files are required on the SA server. The files can be given any name. By default the listener.ora files are located in $ORACLE_HOME/network/admin.

   • listener.ora-install_upgrade – this copy of listener.ora is used during SA install/upgrade
   • listener.ora-operational – this copy of listener.ora is used during normal SA operation.
     

   You can use softlinks to point listener.ora to either listener.ora.ora-install_upgrade or listener.ora.ora-operational:

   ln –s listener.ora-install_upgrade listener.ora

6. Changes to the sample listener.ora-install_upgrade.
   This file is used during the SA installation/upgrade process. Make a note of the text that is in BOLD letters. The listener.ora file should contain the SID_NAME and not the service name. The SID_NAME is case sensitive. Ensure that the listener.ora changes are made on the same server that is referenced in SA servers /etc/hosts file.
   

   This example uses LISTENER_RAC1PUB as the listener name.

   # Generated by Oracle configuration tools.
LISTENER_RAC1PUB =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521)(IP = FIRST))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.173.210)(PORT = 1521)(IP = FIRST))
)
)

   SID_LIST_LISTENER_RAC1PUB =
(SID_LIST =
(SID_DESC=
(SID_NAME=truth1)
(ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_2)
)
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.1.0/db_2)
(PROGRAM = extproc)
)
)
   You can use softlinks to link the file to listener.ora:

   ln –s listener.ora-install_upgrade listener.ora.ora

   Ensure that you start the listener as follows:

   > lsnrctl start LISTENER_RAC1PUB

7. Testing the connection from SA machine to database.

   Before starting the Model Repository installation/upgrade, you can perform the following tests to verify that your tnsnames.ora and listener.ora files are configured correctly and if the SA Installer can connect to the database in restricted mode.

   1. Verify that the SA server's /var/opt/oracle/tnsnames.ora file is configured correctly as described in Making changes to tnsnames.ora on SA server on page 147.
   2. Verify that the database servers or RAC node's $ORACLE_HOME/network/admin/listener.ora file is configured correctly as described in Making changes to listener.ora on one of the RAC node server (instance) on page 148.
   3. On the SA server:
      1. Login as oracle or root or su – twist/spin – if these users exist.
      2. Export ORACLE_HOME=/u01/app/oracle/product/11.1.0/client_1 (or where you installed the Oracle Full Client).
      3. Export LD_LIBRARY_PATH=$ORACLE_HOME/lib.
      4. Export TNS_ADMIN=/var/opt/oracle.
      5. Set $PATH $ORACLE_HOME/bin path.
      6. sqlplus sys/password@truth as sysdba;
         where truth is the service_name or entry from the tnsnames.ora file
      7. Select logins from v$instance;
      8. Alter system enable restricted session;
      9. Select logins from v$instance;
? db should be restricted.
      10. Connect opsware_admin/<password>@truth.

          If you are able to logon to the database then all files are configured correctly.

      11. sqlplus sys/password@truth as sysdba.

      12. Alter system disable restricted session;
          
8. Changes to SA Installer Response File
   You can now start the installation of the SA Model Repository. Ensure that you have the correct parameters values for the installation interview or that you have a previous response file.

   Verify the paths to the client's tnsnames.ora file (%truth.tnsdir), oracle client home (%truth.orahome), listener port (%truth.port), and so on.

   • %truth.tnsdir=/var/opt/oracle
   • %truth.orahome=/u01/app/oracle/product/11.1.0/client_1
   • %truth.port=1521

   You can now install the SA Core as described in the SA Planning and Installation Guide.
   

Post SA Installation Process

After you install the SA Core, perform the following tasks in order to use all the nodes in the Oracle RAC environment.

Making changes to tnsnames.ora on the SA server

After SA install is complete, the tnsnames.ora file should point/link to the tnsnames.ora-operational file.

The SA Installer puts the database in a restricted mode during the Model Repository installation. The database is removed from the restricted mode after successful installation/upgrade of the Model Repository. When the database is in restricted mode, only certain privileged users are allowed to connect to the database. To accommodate the remote truth installation process, two sets of tnsnames.ora are required on the SA server.

• tnsnames.ora-install_upgrade – this copy of tnsnames.ora is used during SA installation/upgrade. You can rename the file.
• tnsnames.ora-operational – this copy of tnames.ora is used during normal SA operation. You can rename the file.
  

You can use softlinks to point tnsnames.ora to either tnsnames.ora-install_upgrade or tnsnames.ora-operational:

ln –s tnsnames.ora-operational tnsnames.ora

tnsnames.ora-operational sample file
Make a note of the text that is in BOLD letters. This tnsnames.ora file is used during normal SA operation and contains the RAC parameters.

#This entry is for connecting to RAC virtual machines.
TRUTH =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))
(LOAD_BALANCE = yes)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(FAILOVER_MODE =
(TYPE = SELECT)
(METHOD = Preconnect)
(RETRIES = 180)
(DELAY = 5))
)
)

LISTENERS_TRUTH =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))
)

#This entry is for connecting to node2 via service_name. This entry is optional
TRUTH2 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(INSTANCE_NAME = truth2)
)
)
LISTENER_TRUTH2 =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac2-vip.dev.opsware.com)(PORT = 1521))

#This entry is for connecting to node1 via service_name. This entry is optional
TRUTH1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = truth)
(INSTANCE_NAME = truth1)
)
)
LISTENER_TRUTH1 =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521))

Use softlinks to link the file to tnsnames.ora.ora file after SA installation is complete and you are ready to start SA in operational mode.

ln –s tnsnames.ora- operational tnsnames.ora

Note: During installation the SA Installer adds an SA Gateway entry into tnsnames.ora (linked to tnsnames.ora.install-upgrade) file on the primary SA Core. When installation is complete, copy that entry into tnsname.ora.operational. If this entry is not present in the tnsname.ora.operational, Multimaster Mesh transactions will not flow. The following is a sample gateway entry from tnsnames.ora:

Rac2sa_truth=(DESCRIPTION=(ADDRESS=(HOST=192.168.173.214)(PORT=20002)(PROTOCOL=tcp))
(CONNECT_DATA=(SERVICE_NAME=truth)))

Making changes to listener.ora on one of the RAC node server (instance)

After SA installation is complete, the listener.ora file should point/link to the listener.ora-operational file.

In an Oracle RAC environment, only one of the RAC nodes or instances is used during installation/upgrade process. The SA Installer connects to only one Oracle instance to modify the Model Repository. During the normal SA operations, all the RAC nodes are used.

The SA Installer puts the database in a restricted mode during the Model Repository installation. The database is removed from the restricted mode after successful installation/upgrade of the Model Repository. When the database is in restricted mode, only certain privileged users are allowed to connect. To accommodate the remote truth installation process, two sets of listener.ora files are required on the SA server. The files can be given any name. By default the listener.ora files can be found in $ORACLE_HOME/network/admin.

Listener.ora-operational – this copy of tnames.ora is used during normal SA operation.

You can use softlinks to point listener.ora.ora to either listener.ora.ora-install_upgrade or listener.ora.ora-operational.

ln –s listener.ora-operational

listener.ora.ora (before SA regular operations)

listener.ora-operational - this file is used to start the listener when SA is running in normal operational mode. Make a note of the text that is in BOLD letters.

# listener.ora.rac1pub Network Configuration File: /u01/app/asm/product/11.1.0/db_1/network/admin/listener.ora.rac1pub
# Generated by Oracle configuration tools.

LISTENER_RAC1PUB =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521)(IP = FIRST))
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.173.210)(PORT = 1521)(IP = FIRST))
)
)

SID_LIST_LISTENER_RAC1PUB =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.1.0/db_2)
(PROGRAM = extproc)
)
)

Use softlink to link the file to listener.ora file.

ln –s listener.ora-operational listener.ora.ora

Ensure that you start the listener as follows:

> lsnrctl start LISTENER_RAC1PUB

Vault.conf File Changes

In an Oracle RAC environment, the vault.conf file must be modified after SA installation is complete. Modify /etc/opt/opsware/vault/vault.conf to specify the complete tnsname definition instead of the SID. For example:

• Before:

  truth.sid: truth

• After:

  truth.sid=(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = rac1-vip.dev.opsware.com)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)
(HOST = rac2-vip.dev.opsware.com)(PORT = 1521)) (LOAD_BALANCE = yes) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = truth)
(FAILOVER_MODE = (TYPE = SELECT) (METHOD = Preconnect) (RETRIES = 180) (DELAY = 5))))
truth.port: 1521

Restart the vaultdaemon:

/etc/init.d/opsware-sas restart vaultdaemon

Upgrading the Model Repository

To upgrade the Model Repository in an Oracle RAC environment, follow the same procedure as Installing the Model Repository on page 145. If you are doing a remote database installation, then make sure that you modify your listener.ora is on one of the RAC instances and tnsnames.ora on the server where the SA Installer is run. It is recommended that you test the connection as suggested in section Testing connection from SA machine to database on page 149.

The following sentence is not valid:
However, due to this change, any Satellites in an SA 7.80 Core must also be upgraded to release 7.80 in order to provision servers. In other words an SA 7.80 Satellite can perform OS Provisioning in an SA 7.80 Core but an SA 7.50 Satellite cannot.

You can perform OS Provisioning in a mixed version SA Core/Satellite environment.

Replace erroneous instructions:

INCORRECT INSTRUCTIONS:

To disable NFS v4 on an SLES 10 Boot Server host:

1. On the Boot Server host, create the following file:
   /etc/sysconfig/nfs
2. In the newly created NFS file, add the following lines:
   NFS4_SUPPORT="no"
   Restart NFS:
   /etc/init.d/nfs stop
   /etc/init.d/nfs start

REPLACE WITH THESE CORRECT INSTRUCTIONS:

To disable NFS v4 on an SLES 10 Boot Server host:

1. On the Boot Server host, create the following file:
   /etc/sysconfig/nfs
2. In the newly created NFS file, add the following lines:
   NFS4_SUPPORT="no"
   Restart NFS:
   /etc/init.d/nfsserver restart

Custom Attributes for Linux or VMware ESX, p 137

Add the following note above Table 11:

Note: Although custom attributes are provided with a default value, you must ensure that the values are valid for your system before proceeding. (QCCR1D 103293)

The following bullet is no longer valid:

The folder contains the tools required to install the Windows Agent Deployment Helper and upload ISMs to SA.

See the SA Planning and Installation Guide for more information about Windows Agent Deployment Helper. See the SA Content Utilities Guide for more information about ISMs.

This section (Prerequisite Setup for Discovery and Agent Deployment) is no longer required. ONLINE HELP

Replace the incorrect section below:

Edit the jboss_wrapper.conf File

Comment out (or delete) the following three lines in the server/ext/wrapper/conf/jboss_wrapper.conf file below:

#Following are added for bug 150387

#wrapper.java.additional.6=-Dorg.omg.CORBA.ORBClass=com.sun.corba.se.internal.Interceptors.PIORB

#wrapper.java.additional.7=-Dorg.omg.CORBA.ORBSingletonClass=com.sun.corba.se.internal.corba.ORBSingleton

#wrapper.java.additional.8=-Xbootclasspath/p:/opt/NA/server/ext/wrapper/lib/CORBA_1.4.2_13.jar

Since SA 7.80 does not use Java 1.4.2, these lines are no longer required.

REPLACE THE SECTION ABOVE WITH THIS SECTION:

You should adjust the values for wrapper.java.additional.x where x > 8 is consecutive.
For example:

Change this:
wrapper.java.additional.1=-DTCMgmtEngine=1
wrapper.java.additional.2=-Duser.dir=/opt/NA750/server/ext/jboss/bin
wrapper.java.additional.3=-Xmn170m
wrapper.java.additional.4=-Djava.awt.headless=true
wrapper.java.additional.5=-Dfile.encoding=UTF8

#Following are added for bug 150387
wrapper.java.additional.6=-Dorg.omg.CORBA.ORBClass=com.sun.corba.se.internal.Interceptors.PIORB
wrapper.java.additional.7=-Dorg.omg.CORBA.ORBSingletonClass=com.sun.corba.se.internal.corba.ORBSingleton
wrapper.java.additional.8=-Xbootclasspath/p:/opt/NA750/server/ext/wrapper/lib/CORBA_1.4.2_13.jar

#Add location of keystore. This is used to make SSL request.
wrapper.java.additional.9=-Djavax.net.ssl.trustStore=/opt/NA750/server/ext/jboss/server/default/conf/truecontrol.keystore

#Bug 171948 - Need more PermGen
wrapper.java.additional.10=-XX:MaxPermSize=80m

To this:
wrapper.java.additional.1=-DTCMgmtEngine=1
wrapper.java.additional.2=-Duser.dir=/opt/NA750/server/ext/jboss/bin
wrapper.java.additional.3=-Xmn170m
wrapper.java.additional.4=-Djava.awt.headless=true
wrapper.java.additional.5=-Dfile.encoding=UTF8

#Following are added for bug 150387
#wrapper.java.additional.6=-Dorg.omg.CORBA.ORBClass=com.sun.corba.se.internal.Interceptors.PIORB
#wrapper.java.additional.7=-Dorg.omg.CORBA.ORBSingletonClass=com.sun.corba.se.internal.corba.ORBSingleton
#wrapper.java.additional.8=-Xbootclasspath/p:/opt/NA750/server/ext/wrapper/lib/CORBA_1.4.2_13.jar

#Add location of keystore. This is used to make SSL request.
wrapper.java.additional.6=-Djavax.net.ssl.trustStore=/opt/NA750/server/ext/jboss/server/default/conf/truecontrol.keystore

# Bug 171948 - Need more PermGen
wrapper.java.additional.7=-XX:MaxPermSize=80m

To illustrate the new Unreplicated LUN Count storage audit rule, the following screens have been updated:

• Audit Browser
  The new screen shows an unreplicated LUN count choice in the Source list under Rules > Storage Compliance Checks. For more information on these screens, see the 7.84 Storage Release Notes.
• Select Server
  The new screen shows how you specify which servers are used as targets in the audit: In the Views tree, choose Targets. In the Source window, choose the Servers and Device Groups tag. In the Select Server window-Select Server tree, choose All Managed Servers.
• Audit Schedule
  The new screen shows the new Schedule option under the View tree.
• Audit Summary
  The new screen shows a summary of the audit results. Choose the Summary option under the View tree.
• Storage Compliance
  The new screen shows checks in an example audit. Choose Views > <managed server> > Storage Compliance Checks

A new Replication Pairs panel was added in the 7.82 release. This window provides the following information:

• Copy Type—The type of association between source and target, such as Async, Sync, UnSyncAssoc, UnSync,UnAssoc, and Migrate
• Replica Type—The type of replication, such as Full Copy, Before Delta, After Delta, Log, and Not specified.
• Source Device—The name of the source device.
• Source Volume—The name of the source volume.
• Status—The State of the association between source and target, such as Initialized, PrepareInProgress, Prepared, ResyncInProgress, Synchronized, FractureInProgress, QuiesceInProgress, Quiesced, RestoreInProgress, Idle, Broken, Fractured, Frozen, and CopyInProgress.
• Target Device—The name of the target device.
• Target Volume—The name of the target volume.

There is no online Help available for this new panel. When you press F1, an empty page displays.

The following replication functionality was added to SE Connector:

• A replication pair consists of the source volume and the target (or copy) volume, including properties that describe the type of replication used to back up or copy the source volume. Replication can be either local (where source and target volumes are on the same array) or remote (where source and target volumes are on different arrays.
  
• A new Replication tree control is available on the Inventory ‰ Storage panel. A replication pair consists of the source volume and the target (or copy) volume, along including properties that describe the type of replication used to back up or copy the source volume. To find detailed information on replication pairs, perform the following steps:

1. From the Navigation pane, select Devices > Storage > SAN Arrays.
   Or
   Select Devices > Storage > NAS Filers.
2. In the content pane, select a storage system and then open it.
3. In the San Array or NAS Filer browser, select Inventory > Storage > Replication.

The following table describes the storage array models and replication types that SE Replication supports with SE Connector.

Array	Model	Replication Pair Type	Replication Technology Name
EVA	6200/4100	Local	Business Copy (BC) Snapshots Snapclones
		Remote	Continuous Access (CA)
HP XP	XP24k/XP12K	Local	Business Copy (BC) Snapshots
		Remote	Continuous Access (CA) Continuous Access Journal (CA Journal)
HDS	HDS990V/USB	Local	Shadowimage C.O.W. Snapshot
		Remote	TrueCopy Universal Replicator
EMC Symmetrix	Symm48:3830 SymmDMX800	Local	Business Continuous Volumes (BCV)
		Remote	RDF
NetApp	FAS270	Local	Snapshot SyncMirror
		Remote	Snapshot