Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.60

Upgrade > Upgrade > Upgrade a single core with distributed components

Upgrade a single core with distributed components

If you are upgrading a Multimaster Mesh, use the instructions shown in Upgrade a multimaster mesh.

Ensure that all CORD patches have been uninstalled, see Uninstalling All CORD patches.

To exemplify the steps listed below, a core with the following custom layout is used:

Server	Core Components installed
192.168.100.111	Oracle database (provided by SA) and Model Repository Core Infrastructure Components
192.168.100.112	Software Repository Storage
192.168.100.113	Slice
192.168.100.114	OS Provisioning Media Server
192.168.100.115	OS Provisioning Boot Server

On the core’s Infrastructure Component bundle host, invoke the SA upgrade script as a user with root privileges.

/<distro>/opsware_installer/hpsa_upgrade.sh –c <full_path_to_CDF>

where <distro> is the full path to the distribution media. For example:

/<mountpoint>/hpsa-primary/disk001
If, for security reasons, you have stored your response files in a location other than the default location on the host being upgraded, copy the files to the Infrastructure host in the /var/opt/opsware/install_opsware/resp directory for the core to be upgraded. In addition, copy your CDF file on the same host in the /var/opt/opsware/install_opsware/cdf directory.
The Specify Hosts to Upgrade screen displays. It will look similar to the following:

Specify Hosts to Upgrade

========================

Currently specified hosts:

192.168.100.111 (oracle_sas, gateway_master, truth_mm_overlay)
192.168.100.112 (word_store, word_uploads)
192.168.100.113 (slice)
192.168.100.114 (osprov_media)
192.168.100.115 (osprov_boot_slice)

Please select one of the following options:

1. Add/edit host(s)

2. Delete host(s)

Enter the option number or one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit):

In case you have a remote database, the database host is NOT explicitly listed in this step, but only those servers that have SA components installed.

Note If you do not provide the CDF, all Core servers that are part of the Core being upgraded must be added in this step as shown below.

Enter 1, to Add/Edit hosts in the Currently Specified Hosts list.

You are prompted to specify the number of server addresses you want to add. Enter the number and press Enter.

You see a screen similar to the following:

Adding Hosts

============

Parameter 2 of 3

FQDN Hostname / IP []:

Enter the hostname or IP address of the first host to add and press enter. Repeat for all the hosts you are adding.

When you have added the specified number of hosts, you see this message:

All values are entered. Do you wish to continue (Y/N) [Y]:

Press Enter to accept the default (Y) or N to re-enter values.

When you are prompted to enter the credentials for each specified host, enter the username and password credentials and press Enter. You are asked to re-enter the password for confirmation. For each host, the interview will look like:
```
Host Passwords
```
```
==============
```
```
Parameter 1 of 2
```
```
192.168.100.112 user [user1]:
```
```
Validating user ....
```
```
Parameter 2 of 2
```
```
192.168.100.112 password []: **********
```
```
Validating password ....
```
When all passwords have been entered and verified, you see the message:

All values are entered. Do you wish to continue (Y/N) [Y]:

Press Enter to accept the default (Y) or N to re-enter values.

The SA Upgrade script determines the component layout of your core. A screen similar to the following is displayed:

Host/Component Layout

=====================

Installed Components

Oracle RDBMS for SA : 192.168.100.111

Model Repository, First Core : 192.168.100.111

Multimaster Infrastructure Component : 192.168.100.111

Software Repository Storage : 192.168.100.112

Slice : 192.168.100.113

OS Provisioning Media Server : 192.168.100.114

OS Provisioning Boot Server, Slice version : 192.168.100.115

Software Repository - Content (install once per mesh) : 192.168.100.112

Enter one of the following directives

(<c>continue, <p>revious, <h>elp, <q>uit):

Note In case you have a remote database, the database host is NOT explicitly listed in this step (that is, the Oracle RDBMS for SAS component), but only those servers that have SA components installed.

Note: If you are upgrading a secondary core, the Model Repository component will appear as: “Model Repository, Additional Core” in this screen.

The prompt to select the cryptographic protocol is displayed.

Cryptographic Protocol Selection for the Server Automation Components

[WARNING] Please make sure that all the cores and satellites from the mesh are at the same TLS level.

========================================================================

1. TLSv1

2. TLSv1.1

3. TLSv1.2

Enter the option number or one of the following directives

(<p>revious, <h>elp, <q>uit)[1]:

See SA Upgrade for details.

The parameter confirmation interview is displayed:

Interview Parameters

====================

Navigation keys:

Use <ctrl>p to go to the previous parameter.

Use <ctrl>n to go the next parameter.

Use <tab> to view help on the current parameter.

Use <ctrl>c to abort the interview.

Parameter 1 of 5 (windows_util_loc)

Please enter the directory path containing the Microsoft patching utilities. Press Control-I for a list of required files or enter "none" if you do not wish to upload the utilities at this time [none]:

Parameter 2 of 5 (truth.servicename)

Please enter the service name of the Model Repository instance in the facility where Opsware Installer is being run [truth.Core1]:

Parameter 3 of 5 (db.sid)

Please enter the SID of the Oracle instance containing the Model Repository [truth]:

Parameter 4 of 5 (db.port)

Please enter the port on which the database is listening. [1521]:

Parameter 5 of 5 (db.orahome)

Please enter the path of the ORACLE_HOME directory of your Model Repository (truth) server. [/u01/app/oracle/product/12.1.0/db_1]:

All values are entered.  Do you wish to continue? (Y/N) [Y]:

End of interview.

The Host Component Layout screen displays again.

Upgrade components

==================

Components to be Upgraded

-------------------------

Model Repository, First Core                         : 192.168.100.111

Multimaster Infrastructure Components                : 192.168.100.111

Software Repository Storage                          : 192.168.100.112

Slice                                                : 192.168.100.113

OS Provisioning Media Server                         : 192.168.100.114

OS Provisioning Boot Server, Slice version           : 192.168.100.115

Software Repository - Content (install once per mesh): 192.168.100.112

Up-to-date Components (will not upgrade)

----------------------------------------

Oracle RDBMS for SAS: 192.168.100.111

Enter one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit):

Press c to continue.

Note In case you have a remote database, the database host is NOT explicitly listed in this step (that is, the Oracle RDBMS for SAS component.

Note: If you are upgrading a secondary core, the Model Repository component will appear as “Model Repository, Additional Core” in this screen.

At this point, a prerequisite check is performed on each specified host to ensure the hosts meet certain basic SA requirements. You may see notifications similar to the following for each host:

Prerequisite Checks

===================

Results for <IP_address>

WARNING Insufficient swap space (2 GBytes).

4 GBytes is the recommended for core_inst.

File system '/' has XXXXX Mbytes available and XXXXXX is recommended.

Enter one of the following directives

(<c>continue, <p>revious, <h>elp, <q>uit):

You should attempt to meet the requirements specified in these warnings, however, you may be able to continue the upgrade if you are unable to meet the recommended settings. Press c to continue.

At this point the upgrade begins and you will see a series of informational messages displayed on the screen as the upgrade progresses. On completion of the upgrade, a success message is displayed.
Note For a Core upgrade with underlying database as Oracle 11g, if the upgrade fails after performing the Model Repository upgrade, the pre-check will prompt the following errors when you restart the upgrade process:
```
FAILURE Oracle optimizer_index_caching = 0 ; required to be = 80
```
```
FAILURE Oracle optimizer_index_cost_adj = 100 ; required to be = 20
```
These errors are the result of changes that were performed when you upgrade the Model Repository successfully. You can ignore this error and continue the upgrade process.

You should now upgrade the SA Agents installed on managed servers. See Post-upgrade task for details.

Send Help Center feedback