Upgrade

This section describes the requirements and procedures for upgrading to SA 10.60.

• Upgrade paths
• SA core configurations supported for customer upgrade
• Windows patch database update
• Changes to Oracle initialization parameters
• Changes to the database jobs
• Changes to the database statistics job

Upgrade paths

You can upgrade to SA 10.60 from the following releases:

• SA 10.2x
• SA 10.5x

CORD patches are rolled back to nearest major release either automatically during the upgrade or manually, if necessary.

SA core configurations supported for customer upgrade

This section describes the SA Core configurations that are supported for customer upgrade.

HPE supports customer-performed upgrades to SA 10.x or later as long as your core configuration is one of the supported configurations. All other core configurations will continue to require the services of HPE Professional Services. If you are uncertain whether you can upgrade an existing SA Core yourself, contact HPE Technical Support.

These configurations include:

• SA Core with a local SA-supplied Oracle Database
• SA Core with a remote customer-supplied Oracle database
• SA Core with a remote model repository and SA-supplied Oracle database
• SA Core with a remote model repository and SA-supplied Oracle database and additional slice component bundle instances
• SA Core with a remote customer-supplied Oracle database and additional slice component bundles
• SA Core with a remote model repository and SA-supplied Oracle database, additional slice component bundle instances and satellites
• SA Core with a remote customer-supplied Oracle database, additional slice component bundles and satellites
• Advanced installation: SA First (Primary) Core with a Secondary Core (Multimaster Mesh)" - A set of two or more SA Cores that communicate through Management Gateways and that can perform synchronization of data about their respective Managed Servers

Using the screen utility for SA upgrades

The screen utility for Linux enables you to safely run the SA Installer and recover from interruptions such as a network disconnection. If, for some reason, you are disconnected from an installation session, you can log back into the machine and use screen to reattach to your installation session.

SA recommends that you invoke the SA Installer using the screen utility in order to minimize the impact of an installation problem due to a network failure.

Red Hat Enterprise Linux, SUSE Linux Enterprise Server and Oracle Enterprise Linux distributions include the screen package but you must explicitly install it (the screen package is not available by default).

Windows patch database update

In previous upgrades, SA could update the Windows patch database. As of SA 9.0 and later, you must update the patch database using the SA Client as described in Use or by using the populate-opsware-update-library script.

Changes to Oracle initialization parameters

During upgrade, SA makes the following changes to certain Oracle initialization parameters. These changes only occur if you have installed the SA-supplied Oracle database. If you are using a non-SA-supplied Oracle database, you must make these updates manually.

Oracle 11g Only

nls_length_semantics='CHAR' 

optimizer_mode=all_rows 

"_complex_view_merging"=false

event='12099 trace name context forever, level 1' 

remote_login_passwordfile=EXCLUSIVE 

if open_cursors < 1000 then the open_cursors is set to 1000

Oracle 12c Only

nls_length_semantics='CHAR'

optimizer_mode=all_rows

remote_login_passwordfile=EXCLUSIVE

if open_cursors < 1500 then the open_cursors is set to 1500

Changes to the database jobs

Oracle has introduced dba_scheduler_jobs scheduling which is more robust and fully-featured than dba_jobs scheduling used in previous SA versions. Oracle recommends the use of the dba_scheduler_jobs package for releases 11g and later since Oracle will not add new features to dba_jobs and its continued use could run into limitations. All SA jobs that were performed using the dba_jobs scheduler are ported to the new dba_scheduler_jobs package during upgrade to SA 10.0 or later.

To verify that existing jobs are executing correctly:

Enter the following commands in SQL*Plus:

# su - oracle

# sqlplus "/ as sysdba"

# sqlplus "/ as sysdba"

set line 200

col job_name format a50

col owner format a14

col last format a17

col next format a17

col state format a10

col job_action format a50

select job_name, owner, to_char(LAST_START_DATE, 'MM/DD/YY HH:MI:SS') last, to_char(next_run_date, 'MM/DD/YY HH:MI:SS') next, state, job_action from dba_scheduler_jobs where owner in ('OPSWARE_ADMIN', 'LCREP', 'GCADMIN');

In the output generated from the preceding statement, the value of the JOB_ACTION column indicates the type of job. The jobs owned by GCADMIN perform the garbage collection. The job owned by LCREP performs index statistics collection and the job owned by OPSWARE_ADMIN performs system statistics collection. Sample output will appear similar to this:

JOB_NAME	OWNER	LAST	NEXT	STATE	JOB_ACTION
------------------------	-------	-----------------	-----------------	-----------	-----------------------------
WLMPURGE_GC	GCADMIN	04/02/12 9:00:02	04/04/12 9:00:00	SCHEDULED	WLMPURGE.GC_JOBS
STORAGEINITIATORPURGE_GC	GCADMIN	04/02/12 09:47:30	04/03/12 10:47:30	SCHEDULED	STORAGEINITIATORPURGE.GC_ STORAGEINITIATORS
AUDITPURGE_GC	GCADMIN	04/02/12 09:00:02	04/04/12 09:00:00	SCHEDULED	AUDITPURGE.GC_AUDITLOGS
CHANGELOGPURGE_GC	GCADMIN	04/02/12 09:00:02	04/04/12 09:00:00	SCHEDULED	CHANGELOGPURGE.GC_CHANGELOGS
WAYPURGE_GC	GCADMIN	04/02/12 09:00:02	04/04/12 09:00:00	SCHEDULED	WAYPURGE.GC_SESSIONS
LCREP_INDEX_STATS	LCREP	04/02/12 11:00:00	04/03/12 11:00:00	SCHEDULED	gather_lcrep_stats
OPSWARE_ADMIN_SYSTEM_STATS	OPSWARE _ADMIN	04/02/12 06:00:00	04/03/12 06:00:00	SCHEDULED	gather_opsware_admin_ sys_stats

7 rows selected.

where:

JOB_NAME - name of the job

OWNER - the user who with permissions to run the job

LAST_DATE - last date-time when the job was run

NEXT_DATE - next date the job will run

STATE - The status of the scheduled job:

• disabled - The job is disabled
• scheduled - The job is scheduled to be executed

• running - The job is currently running

• completed - The job has completed, and is not scheduled to run again

• broken - The job is broken

• failed - The job was scheduled to run once and failed

• retry scheduled - The job has failed at least once and a retry has been scheduled to be executed

• succeeded - The job was scheduled to run once and completed successfully

• JOB_ACTION - The procedure that the job runs

Changes to the database statistics job

Oracle documentation advises that you enable Automatic Optimizer statistics collection. When you have the optimizer enabled, the database can automatically collect optimizer statistics for tables with absent or stale statistics. If fresh statistics are required for a table, the database collects them both for the table and its associated indexes.

Oracle claims that automatic statistics collection eliminates many manual tasks associated with managing the optimizer and significantly reduces the risks of generating poor execution plans because of missing or stale statistics.

The schema collection jobs of SA (performed in previous versions by the TRUTH, AAA and LCREP users) is now removed and SA now relies on Oracle’s Automatic Optimizer statistics collection to collect the schema statistics. By default Oracle’s Automatic Optimizer statistics collection is enabled.

To verify that the Oracle Automatic optimizer statistics collection is turned on:

Execute the following commands in SQL*Plus:

# su - oracle

# sqlplus "/ as sysdba"

set line 200

col status format a10

SELECT status FROM dba_autotask_client where client_name='auto optimizer stats collection';

The output from the above statement should be as follows:

STATUS

----------

ENABLED

If the status is not set to ENABLED, execute the following statement to enable Oracle’s Automatic Optimizer statistics collection.

EXEC DBMS_AUTO_TASK_ADMIN.ENABLE(client_name => 'auto optimizer stats collection',operation => NULL, window_name => NULL);