You can upgrade to the latest version of Oracle Enterprise Manager Ops Center 12c if you are currently using Oracle Enterprise Manager Ops Center 12c, or upgrade to Oracle Enterprise Manager Ops Center 12c if you are currently using Oracle Enterprise Manager Ops Center 11g Release 1 Update 3.
The following features and topics are covered in this chapter:
You can upgrade to the latest version of Oracle Enterprise Manager Ops Center from Oracle Enterprise Manager Ops Center 12c. If you are using Oracle Enterprise Manager Ops Center 11g Update 3, you must upgrade to version 12.1.1.0.0 before upgrading to the latest version.
Some of the procedures described in this section use the ecadm, proxyadm, and agentadm commands. See the Oracle Enterprise Manager Ops Center Feature Reference Guide for more information about these commands.
On Oracle Solaris systems, these commands are in the /opt/SUNWxvmoc/bin/ directory.
On Linux systems, these commands are in the /opt/sun/xvmoc/bin/ directory.
Note:
If you are currently using Oracle Enterprise Manager Ops Center 11g, you must use thesatadm command in place of the ecadm command. These commands serve the same purpose and use the same syntax for the purposes of these procedures.Upgrading to a newer version of Oracle Enterprise Manager Ops Center can change the system requirements and affect existing settings and data. Take the following steps to plan your upgrade:
Review the Oracle Enterprise Manager Ops Center Release Notes for pre-installation requirements and known issues.
Verify that your system meets the system requirements outlined in the Oracle Enterprise Manager Ops Center Installation Guide for Oracle Solaris Operating System or Oracle Enterprise Manager Ops Center Installation Guide for Linux Operating Systems, since some system requirements have changed.
You can use the OCDoctor to check system requirements. See http://java.net/projects/oc-doctor for more information about the OCDoctor.
If you made changes to the uce.rc file, the upgrade erases your changes. Copy your changes to the .uce.rc file before beginning the upgrade.
If you replaced the self-signed web server certificate for the Enterprise Controller, the upgrade erases your web server configuration changes, and might erase the certificate. Copy the certificate to a safe location before beginning the upgrade. After the upgrade, reapply your configuration changes and copy the certificate to its original location.
If you are upgrading from version 11g to version 12c, changes to several features require you to make several changes to your environment:
Discovery criteria from version 11g are converted to discovery profiles, but you must create new credentials and associate them with the new discovery profiles before you can use them to discover assets.
Any assets that were discovered but not managed by a version 11g Enterprise Controller must be rediscovered in version 12c.
You must create and assign management credentials to assets if the credentials used by a Proxy Controller to reach them have changed.
Reports from version 11g must be re-run.
Solaris Update Compliance reports are no longer supported in version 12c, and Solaris Update Compliance report templates are not migrated.
Oracle Enterprise Manager Ops Center version 12c can use either an embedded database on the Enterprise Controller system or a customer-managed database. If you are upgrading from version 11g, you can switch to either database configuration. If you are upgrading from version 12c, you cannot change the existing database configuration during the upgrade.
The embedded database is configured and managed by Oracle Enterprise Manager Ops Center. The embedded database requires 10 GB of space, plus 240 MB per managed asset, 400 MB per UCE channel, and 20% of the space currently taken up by the /var/opt/sun/xvm/db/mgmt and var/opt/sun/xvm/db/report directories.
You must install and configure a compatible database to use a customer-managed database. Using a customer-managed database requires no additional space beyond that required by the Enterprise Controller.
You can perform upgrades through the user interface or from the command line. If you are upgrading from version 11g and intend to use the embedded Oracle database, you can perform the upgrade from the user interface or from the command line. If you are upgrading from version 11g and intend to use a customer-managed database, you can perform the upgrade from the command line.
Note:
The upgrade process creates a backup file for the Enterprise Controller. If the upgrade fails, the Enterprise Controller is uninstalled, the initial version of the Enterprise Controller is reinstalled, and the system is automatically restored from the backup file.Upgrade your systems in the following order.
Download the upgrade bundles for your environment.
Upgrade the Enterprise Controller. This also upgrades the co-located Proxy Controller.
If you have a High Availability configuration, upgrade your Enterprise Controllers as described in Upgrading the Enterprise Controllers in an HA Configuration.
Upgrade the separate Proxy Controllers.
Upgrade the Agent Controllers through the UI or manually.
If your data center is large, you can upgrade your Proxy Controllers one at a time. To do so, upgrade your systems in the following order.
Download the upgrade bundles for your environment.
Upgrade the Enterprise Controller.
If you have a High Availability configuration, upgrade your Enterprise Controllers as described in Upgrading the Enterprise Controllers in an HA Configuration.
Upgrade one Proxy Controller.
Upgrade the Agent Controllers managed by the upgraded Proxy Controller.
Upgrade the next Proxy Controller.
Upgrade the Agent Controllers managed by the upgraded Proxy Controller.
Repeat steps 5 and 6 for each Proxy Controller.
In either scenario, once you have begun the upgrade, complete it as soon as possible. Do not allow the Enterprise Controller or Proxy Controllers to be restarted before all systems have been upgraded.
You can download upgrades for Oracle Enterprise Manager Ops Center. This includes upgrades for the Enterprise Controller, Proxy Controllers, and Agent Controllers. Downloading an upgrade does not install it on managed assets.
You can download the upgrade bundles through the user interface, from the Oracle Technology Network, or from e-Delivery.
Each upgrade bundle contains the previous upgrade bundles, so you only need to download and apply the most recent upgrade in order to upgrade your system.
You can download upgrades for Oracle Enterprise Manager Ops Center through the user interface.
Upgrades are downloaded to these directories:
Enterprise Controller upgrades: /var/opt/sun/xvm/images/productUpdate
Proxy Controller upgrades: /var/opt/sun/xvm/images/productUpdate
Agent Controller upgrades: /var/opt/sun/xvm/images/agent
Click the Enterprise Controller in the Administration section of the Navigation pane.
Click Ops Center Downloads.
The Ops Center Downloads Wizard is displayed.
(Optional) Hover over the details icon for a download to view more information about it.
Select one or more downloads and click Next.
The View License page is displayed.
Read the license and click Accept.
The Download Status page is displayed.
Check I wish to download the remaining upgrades in the background, or wait for the downloads to complete.
Click Next.
The Summary page is displayed.
Click Finish.
The upgrades are now available.
You can download upgrade bundles for the Enterprise Controller and Proxy Controller from the Oracle Technology Network.
Log in to the Oracle Technology Network Oracle Enterprise Manager Ops Center page at http://www.oracle.com/technetwork/oem/ops-center/index.html.
Click Enterprise Manager Ops Center in the Enterprise Manager Downloads sidebar.
Select Accept License Agreement.
Download the appropriate bundle.
Click the Enterprise Controller bundle with the correct operating system and architecture to download the full bundle. This bundle contains the Enterprise Controller and Proxy Controller files for the selected architecture and operating system, and Agent Controller files for every supported operating system and architecture.
Click the Proxy Controller bundle with the correct operating system and architecture to download the Proxy Controller installation bundle. This bundle is used to manually install remote Proxy Controllers.
You can download upgrade bundles for the Enterprise Controller and Proxy Controller from e-Delivery.
To Download Upgrades From e-Delivery
Log in to the Oracle e-Delivery website at http://edelivery.oracle.com.
Read and accept the Software License Agreement and Export Restrictions, then click Continue.
Select the Oracle Enterprise Manager product pack and the correct platform for your environment, then click Go.
The list of download packs is displayed.
Select the Oracle Enterprise Manger Ops Center 12c Release 1 Media Pack and click Continue.
The list of available bundles is displayed.
Download the appropriate bundle.
Click download next to the Enterprise Controller bundle with the correct operating system and architecture to download the full bundle, then save the downloaded bundle locally. This bundle contains the Enterprise Controller and Proxy Controller files for the selected architecture and operating system, and Agent Controller files for every supported operating system and architecture.
Click download next to the Proxy Controller bundle with the correct operating system and architecture to download the Proxy Controller installation bundle, then save the downloaded bundle locally. This bundle is used to manually install remote Proxy Controllers.
Once you have downloaded an upgrade bundle, you can upgrade your Enterprise Controllers.
You can perform upgrades through the user interface or from the command line. If you are upgrading from version 11g and intend to use the embedded Oracle database, you can perform the upgrade from the user interface or from the command line. If you are upgrading from version 11g and intend to use a customer-managed database, you can perform the upgrade from the command line.
If you have multiple Enterprise Controllers in a high availability configuration, you can upgrade them together.
Perform the following tasks before you upgrade the Enterprise Controller:
Download the Enterprise Controller upgrade.
Review pending and scheduled jobs before updating the Enterprise Controller. The upgrade shuts down the Enterprise Controller, which causes running jobs to fail.
Use the OCDoctor to verify that there are no outstanding issues on the Enterprise Controller systems. Log in to each Enterprise Controller system, then run the OCDoctor with the --update option, then run the OCDoctor script with the --troubleshoot option. See the OCDoctor chapter for more information about the OCDoctor.
To Upgrade the Enterprise Controllers in an HA Configuration
If one of the Enterprise Controller nodes has a co-located Proxy Controller, make it the primary node using the ecadm command with the ha-relocate subcommand.
If multiple Enterprise Controller nodes have co-located Proxy Controllers, migrate all of the assets from these Proxy Controllers to a remote Proxy Controller or to the Proxy Controller of the primary node as described in Migrating Assets Between Proxy Controllers.
On each standby node, use the ecadm command with the ha-unconfigure-standby subcommand to unconfigure the standby nodes from the HA configuration.
Uninstall the Enterprise Controller software on the standby nodes as described in Uninstalling and Unconfiguring the Enterprise Controller, then reboot the systems.
Use the ecadm command with the ha-unconfigure-primary subcommand to unconfigure the Enterprise Controller as part of a High Availability configuration.
The active Enterprise Controller node is unconfigured as the active node.
On the remaining Enterprise Controller system, update the start/exec property in the the svc:/application/scn/satellite-enable SMF service.
Change the start/exec property for the svc:/application/scn/satellite-enable service to :true. For example:
# /usr/sbin/svccfg svc:> select svc:/application/scn/satellite-enable svc:/application/scn/satellite-enable> setprop start/exec = :true svc:/application/scn/satellite-enable> end
Refresh the svc:/application/scn/satellite-enable service. For example:
# /usr/sbin/svcadm refresh svc:/application/scn/satellite-enable:default
Confirm that the property has been changed. For example:
# svcprop -p start/exec svc:/application/scn/satellite-enable:default :true
Use the ecadm command with the start subcommand and the -w option to start the active node.
The Enterprise Controller is restarted.
Upgrade the active node using the Upgrading a Single Enterprise Controller from the User Interface procedure or the Upgrading a Single Enterprise Controller from the Command Line procedure.
Convert the upgraded standalone Enterprise Controller to an HA configuration as described in Converting a Single Enterprise Controller to High Availability. This procedure includes installing the latest Enterprise Controller version on the standby nodes.
The following procedure describes how to upgrade the Enterprise Controller. You can view and install upgrades from the user interface.
Upgrade log files are stored in the /var/opt/sun/xvm/update-saved-state directory on the Enterprise Controller.
Note:
If you are currently using Oracle Enterprise Manager Ops Center 11g, you must upgrade your systems from the command line.Perform the following tasks before you upgrade the Enterprise Controller:
Download the Enterprise Controller upgrade bundle.
Review pending and scheduled jobs before updating the Enterprise Controller. The upgrade shuts down the Enterprise Controller, which causes running jobs to fail.
Use the OCDoctor to verify that there are no outstanding issues on the Enterprise Controller system. Log in to the Enterprise Controller, then run the OCDoctor with the --update option, then run the OCDoctor script with the --troubleshoot option. See the OCDoctor chapter for more information about the OCDoctor.
When you are using an embedded database, verify that the Oracle Database 11g Enterprise Edition version 11.2.0.3 installation files used during the Oracle Enterprise Manager Ops Center installation are present in the /var/tmp/downloads directory on the Enterprise Controller system. Follow this procedure to download the installation files if they are missing:
Note:
The download procedure requires a valid My Oracle Support (MOS) account, which must be associated with a Customer Service Identifier (CSI) with a software contract.Create a /var/tmp/downloads directory on the Enterprise Controller system.
Navigate to http://support.oracle.com, click Sign In, and sign in with your MOS credentials.
Click the Patches & Updates tab.
Enter 10404530 in the field next to Patch Name or Number.
Click the Add Filter icon, then select your Enterprise Controller system's operating system and architecture in the drop-down menu next to Platform.
Click Search.
The Oracle Database 11g Enterprise Edition version 11.2.0.3 patch set is displayed.
Click Download.
The file download popup is displayed.
Download the first two files. For Oracle Solaris, these files end with _1of6.zip and _2of6.zip. For Linux, these files end with _1of7.zip and _2of7.zip
Copy or move the downloaded installation bundles to the /var/tmp/downloads directory on the Enterprise Controller system.
To Upgrade the Enterprise Controller
Click the Enterprise Controller in the Administration section of the Navigation pane.
Click Upgrade Enterprise Controller.
The Upgrade Enterprise Controller Wizard is displayed. All available Enterprise Controller upgrades are displayed.
(Optional) Mouse over the details icon for an upgrade to view more information about it.
Select an upgrade and click Next. If the current Oracle Enterprise Manager Ops Center installation file cannot be found, the Install Path Verification page is displayed. If the upgrade fails, the installation file is used for rollback.
If the Install Path Verification page is displayed, enter the path to the Oracle Enterprise Manager Ops Center installer and click Next. By default, the upgrade process uses the /var/opt/sun/xvm/update-saved-state/ directory to back out the changes if the upgrade fails. If this directory is not present, the installer for the previous version is used to reinstall the older version and restore the system.
The Job Details page is displayed. When the upgrade shuts down the Enterprise Controller, any jobs that are running fail. View the job details, then click Next. The Summary page is displayed.
Click Finish.
The upgrade is launched. The upgrade can take up to an hour, during which time the Enterprise Controller is not accessible. Reload the browser regularly, and the login page displays normally when the upgrade is complete.
If you are upgrading from version 12c to version 12c update 1, and your environment uses a customer-managed database, update the database privileges.
Copy the refactorOCPrivs_12.1.1.0.sql script, from the Enterprise Controller system to the customer-managed database system.
On Oracle Solaris systems, this script is in the /opt/ORCLsysman-db/sql/update/delta-update1/oracle/ directory.
On Linux systems, this script is in the /opt/orcl-sysman-db/sql/update/delta-update1/oracle/ directory.
Run the SQL script as the SYS User. When you are prompted, provide the schema names for the Ops Center database login and Read-Only Ops Center database login for the appropriate prompts. These parameters were provided when the inital Ops Center logins were created using the createOCSchema_remote.sql script. These parameters are visible in the /opt/sun/xvm/db.properties file as mgmtdb.appuser and mgmtdb.roappuser.
For example:
sqlplus / as sysdba @refactorOCPrivs_12.1.1.0.sql Enter username for Ops Center database login: OC Enter username for read only Ops Center database login: OC_RO
Clear the browser cache and refresh the browser before you log in to the newly upgraded Enterprise Controller.
Back up your Oracle Enterprise Manager Ops Center data using the ecadm command and the backup subcommand.
The following procedures describe how to upgrade the Enterprise Controller, with either an embedded database or a customer-managed database. If you are running Oracle Enterprise Manager Ops Center in Disconnected Mode, you must upgrade from the command line. The co-located Proxy Controller is upgraded as well, even if it is not enabled.
The Enterprise Controller upgrade log is saved locally as /var/opt/sun/xvm/update-saved-state/update_satellite_bundle_<version number>/updatelog.txt.
Upgrade log files are stored in the /var/opt/sun/xvm/update-saved-state directory on the Enterprise Controller.
If an error occurs during this process, the system is restored to the prior version.
Perform the following tasks before you upgrade the Enterprise Controller:
Verify that the Enterprise Controller has at least five (5) GB of free space for the upgrade bundle.
Acquire the upgrade bundle from Oracle and transfer it to the Enterprise Controller system.
Review pending and scheduled jobs before updating the Enterprise Controller. The upgrade shuts down the Enterprise Controller, which causes running jobs to fail. Scheduled jobs cannot be launched while the upgrade is being applied.
Use the OCDoctor to verify that there are no outstanding issues on the Enterprise Controller system. Log in to the Enterprise Controller, then run the OCDoctor with the --update option, then run the OCDoctor script with the --troubleshoot option. See the OCDoctor chapter for more information about the OCDoctor.
If you upgrading from Oracle Enterprise Manager Ops Center 11g and you plan to use a customer-managed database, you must identify a system with an Oracle Database Enterprise Edition database that serves as the Oracle Enterprise Manager Ops Center repository.
When you are using an embedded database, or are upgrading from Oracle Enterprise Manager Ops Center 11g and you plan to use an embedded database, verify that the Oracle Database 11g Enterprise Edition version 11.2.0.3 installation files are present in the /var/tmp/downloads directory on the Enterprise Controller system. Follow this procedure to download the installation files if they are missing:
Note:
This procedure requires a valid My Oracle Support (MOS) account, which must be associated with a Customer Service Identifier (CSI) with a software contract.Create a /var/tmp/downloads directory on the Enterprise Controller system.
Navigate to http://support.oracle.com, click Sign In, and sign in with your MOS credentials.
Click the Patches & Updates tab.
Enter 10404530 in the field next to Patch Name or Number.
Click the Add Filter icon, then select your Enterprise Controller system's operating system and architecture in the drop-down menu next to Platform.
Click Search.
The Oracle Database 11g Enterprise Edition version 11.2.0.3 patch set is displayed.
Click Download.
The file download popup is displayed.
Download the first two files. For Oracle Solaris, these files end with _1of6.zip and _2of6.zip. For Linux, these files end with _1of7.zip and _2of7.zip
Copy or move the downloaded installation bundles to the /var/tmp/downloads directory on the Enterprise Controller system.
This procedure describes how to upgrade an Enterprise Controller with an embedded database. If you are using version 11g, this procedure installs and configures the embedded database.
As root, log in to the Enterprise Controller.
Verify that the Enterprise Controller is online.
If you are currently using Oracle Enterprise Manager Ops Center 12c, use the ecadm command to verify that the Enterprise Controller is online. If necessary, use the ecadm start command to start the Enterprise Controller.
# /opt/SUNWxvmoc/bin/ecadm status online
If you are currently using Oracle Enterprise Manager Ops Center 11g, use the satadm command to verify that the Enterprise Controller is online. If necessary, use the satadm start command to start the Enterprise Controller.
# /opt/SUNWxvmoc/bin/satadm status online
Create a temporary directory within the directory where you installed Oracle Enterprise Manager Ops Center, then copy or move the upgrade bundle to the new directory. For example:
# mkdir /var/tmp/OC/update # cp enterprise-controller.Solaris.sparc.12.1.0.2001.tar.zip /var/tmp/OC/update
Change to the directory containing the upgrade bundle.
# cd /var/tmp/OC/update
Unzip and un-tar the bundle.
If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. For example:
# unzip enterprise-controller.Solaris.i386.12.1.0.2001.tar.zip | tar xf - # ls enterprise-controller.Solaris.i386.12.1.0.2001.tar.zip xvmoc_full_bundle #
If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:
# unzip enterprise-controller.Solaris.i386.12.1.0.2001.zip # ls enterprise-controller.Solaris.i386.12.1.0.2001.zip xvmoc_full_bundle #
Change to the xvmoc_full_bundle directory and run the install script.
# cd xvmoc_full_bundle # ./install
The following option can be used with the install script:
--verbose or -v: Increases verbosity of output from upgrade program. Without this option, non-verbose output is given.
When the upgrade is complete, the install script indicates that all Oracle Enterprise Manager Ops Center components have been upgraded to the latest version.
Clear your browser cache and refresh your browser before you log in to the newly upgraded Enterprise Controller.
Back up your Oracle Enterprise Manager Ops Center data using the ecadm command and the backup subcommand.
This procedure describes how to upgrade an Enterprise Controller with a customer-managed database. If you are using version 11g, this procedure configures Oracle Enterprise Manager Ops Center to use a customer-managed database.
As root, log in to the Enterprise Controller.
Verify that the Enterprise Controller is online.
If you are currently using Oracle Enterprise Manager Ops Center 12c, use the ecadm command to verify that the Enterprise Controller is online. If necessary, use the ecadm start command to start the Enterprise Controller.
# /opt/SUNWxvmoc/bin/ecadm status online
If you are currently using Oracle Enterprise Manager Ops Center 11g, use the satadm command to verify that the Enterprise Controller is online. If necessary, use the satadm start command to start the Enterprise Controller.
# /opt/SUNWxvmoc/bin/satadm status online
Create a temporary directory within the directory where you installed Oracle Enterprise Manager Ops Center, then copy or move the upgrade bundle to the new directory. For example:
# mkdir /var/tmp/OC/update # cp enterprise-controller.Solaris.sparc.12.1.0.2001.tar.zip /var/tmp/OC/update
Change to the directory containing the upgrade bundle.
# cd /var/tmp/OC/update
Unzip and un-tar the bundle.
If your installation archive has the .tar.zip extension, use the unzip and tar commands to uncompress and un-tar the archive, then list the contents of the temporary directory. The following command example retains the original compressed archive file. For example:
# unzip enterprise-controller.Solaris.i386.12.1.0.2001.tar.zip | tar xf - # ls enterprise-controller.Solaris.i386.12.1.0.2001.tar.zip xvmoc_full_bundle #
If your installation archive has the .zip extension, use the unzip command to uncompress the archive. For example:
# unzip enterprise-controller.Solaris.i386.12.1.0.2001.zip # ls enterprise-controller.Solaris.i386.12.1.0.2001.zip xvmoc_full_bundle #
If you are upgrading from version 11g, copy the createOCschema_remote.sql script from the /var/tmp/OC/xvmoc_full_bundle/<Enterprise Controller OS>/Product/installer/scripts directory on the Enterprise Controller to the customer-managed database server. As the customer-managed database administrator, run the script and enter the following information:
Oracle Enterprise Manager Ops Center user name: This is a database user that is created by the script, which Oracle Enterprise Manager Ops Center uses to access the database.
Oracle Enterprise Manager Ops Center password: This is the password for the database user.
Oracle Enterprise Manager Ops Center read-only user name: This is a read-only database user which Oracle Enterprise Manager Ops Center uses to view the database.
Oracle Enterprise Manager Ops Center read-only password: This is the password for the read-only database user.
Default tablespace: This is the default tablespace for the Oracle Enterprise Manager Ops Center user.
Temporary tablespace: This is the temporary tablespace for the Oracle Enterprise Manager Ops Center user.
Oracle Enterprise Manager Ops Center dump directory: This directory must exist and must be owned by the oracle user.
When you enter all of the required information, the createOCschema_remote.sql script indicates completion and exits.
For example:
$ sqlplus / as sysdba @createOCSchema_remote.sql SQL*Plus: Release 11.2.0.3.0 Production on Thu Dec 15 16:55:34 2011 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options Enter username for Ops Center database login: TESTSCHEMA Enter password for Ops Center database login: Enter username for read only Ops Center database login: TESTSCHEMA_RO Enter password for read only Ops Center database login: Enter default tablespace for Ops Center user: USERS Enter temporary tablespace for Ops Center user: TEMP Enter Oracle Data Pump destination directory: /var/tmp/ocdumpdir "Done creating OC_SYSTEM_ROLE and OC_RO_ROLE" "Done creating Schema 'TESTSCHEMA'. Roles and privileges have been granted." "Done creating Schema 'TESTSCHEMA_RO'. Roles and privileges have been granted." "Done creating OC_DUMP_DIR at /var/tmp/ocdumpdir" "Done granting privs to users and profiles" "Testing connectivity to the new schema: 'TESTSCHEMA'" Connected. "Testing connectivity to the new read only schema: 'TESTSCHEMA_RO'" Connected. "Create is Complete. OC can now be used with the new schema: 'TESTSCHEMA'" Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options $
If you are upgrading from version 11g, create a database properties file on the Enterprise Controller system. The database properties file must contain the location of the customer-managed database and the same user and read-only user credentials supplied in the schema creation script.
For example:
# vi /var/tmp/OC/DB/RemoteDBProps.txt mgmtdb.appuser=user mgmtdb.password=userpass mgmtdb.roappuser=user mgmtdb.ropassword=userpass mgmtdb.dburl=jdbc:oracle:thin:@<database host name>:<port>/<database service name>
Change to the xvmoc_full_bundle directory and run the install script. If you are upgrading from version 11g, use the -remoteDBprops=<credentials file> option.
The following option can be used with the install script:
--verbose or -v: Increases verbosity of output from upgrade program. Without this option, non-verbose output is given.
For example, to upgrade from version 12c to version 12c update 1:
# cd xvmoc_full_bundle # ./install
For example, to upgrade from version 11g to version 12c update 1:
# cd xvmoc_full_bundle # ./install -remoteDBprops=/var/tmp/OC/DB/RemoteDBProps.txt
When the upgrade is complete, the install script indicates that all Oracle Enterprise Manager Ops Center components have been upgraded to the latest version.
If you are upgrading from version 12c to version 12c update 1, and your environment uses a customer-managed database, update the database privileges for the OC system schema and OC_SYSTEM_ROLE.
Copy the refactorOCPrivs_12.1.1.0.sql script, from the Enterprise Controller system to the customer-managed database system.
On Oracle Solaris systems, this script is in the /opt/ORCLsysman-db/sql/update/delta-update1/oracle/ directory.
On Linux systems, this script is in the /opt/orcl-sysman-db/sql/update/delta-update1/oracle/ directory.
Run the SQL Script as the SYS User. When you are prompted, provide the schema names for the Ops Center database login, Read-Only Ops Center database login, and default tablespace for the appropriate prompts. These parameters were provided when the inital Ops Center logins were created using the createOCSchema_remote.sql script. The database login and read-only database login parameters are visible in the /opt/sun/xvm/db.properties file as mgmtdb.appuser and mgmtdb.roappuser. The default tablespace is visible in the /opt/ORCLsysman-db/etc/llocalOracleConfig.properties file as remote_default_ts.
For example:
sqlplus / as sysdba @refactorOCPrivs_12.1.1.0.sql Enter username for Ops Center database login: OC Enter username for read only Ops Center database login: OC_RO Enter default tablespace for the Ops Center database login: USERS
Clear your browser cache and refresh your browser before you log in to the newly upgraded Enterprise Controller.
Back up your Oracle Enterprise Manager Ops Center data using the ecadm command with the backup subcommand and the -r option.
Once you have downloaded an upgrade bundle, you can upgrade your Proxy Controllers.
You can remotely upgrade Proxy Controllers to the latest available version.
Proxy Controller files are stored in the /var/opt/sun/xvm/images/productUpdate directory. If you are using Connected Mode, use the Ops Center Downloads action to download Proxy Controller files. If you are using Disconnected Mode, you must add the Proxy Controller files to the /var/opt/sun/xvm/images/productUpdate directory before they can be used.
To upgrade a Proxy Controller through the UI, the Enterprise Controller must be able to reach the Proxy Controller with an SSH connection using port 22 during the upgrade process. This connection is used to transfer Proxy Controller bundles and execute commands on the Proxy Controller system. If your security restrictions do not allow this connection, upgrade the Proxy Controller from the command line.
Perform the following tasks before you upgrade the Proxy Controller:
Upgrade the Enterprise Controller.
Download the Proxy Controller upgrade.
Click the Enterprise Controller in the Administration section of the Navigation pane.
Click the Proxy Controllers tab.
Proxy Controller information is displayed.
Select one or more Proxy Controllers.
Click the Upgrade to Latest Available Version icon in the center pane.
The Upgrade Wizard is displayed.
Select a method for providing SSH credentials for the Proxy Controller or Proxy Controllers.
Re-use the SSH credentials used during discovery
Apply the same SSH credentials to all
Enter SSH credentials for each
Click Finish.
A job is launched to update the Proxy Controllers.
You can manually update Proxy Controllers to the latest available version to gain access to new and updated features.
The Proxy Controller upgrade log is saved locally as /var/opt/sun/xvm/update-saved-state/update_proxy_bundle_<version number>/updatelog.txt.
If an error occurs during this process, the system is restored to the prior version.
Note:
During the upgrade process, the Proxy Controller is shut down. However, the Proxy Controller must be online at the beginning of the process.Proxy Controller files are stored in the /var/opt/sun/xvm/images/productUpdate directory on the Enterprise Controller. If you are using Connected Mode, use the Ops Center Downloads action to download Proxy Controller files, then move them to the Proxy Controller system. If you are using Disconnected Mode, Proxy Controller files must be downloaded outside of Oracle Enterprise Manager Ops Center and moved to the Proxy Controller system.
As root, log in to the Proxy Controller system.
Back up the contents of the following directory:
/etc/opt/sun/cacao2/instances/scn-proxy/security/ on a Linux Proxy Controller
/etc/cacao/instances/scn-proxy/security/ on an Oracle Solaris Proxy Controller
Run the proxyadm command with the status subcommand to verify that the Proxy Controller is online. If the Proxy Controller is offline, start it using the proxyadm command with the start subcommand.
For example:
# ./proxyadm status online
Change to the directory containing the upgrade bundle.
Uncompress and un-tar the installation archive, then list the contents of the temporary directory.
For example, on a Linux Proxy Controller:
# unzip proxy-controller.Linux.i686.12.1.0.2001.tar.zip # tar xf proxy-controller.Linux.i686.12.1.0.2001.tar # ls xvmoc_full_bundle proxy-controller.Linux.i686.12.1.0.2001.tar #
On an Oracle Solaris Proxy Controller:
# gzcat proxy-controller.Solaris.i386.12.1.0.2001.tar.zip | tar xf - # ls xvmoc_full_bundle proxy-controller.Solaris.i386.12.1.0.2001.tar.zip
Change to the xvmoc_full_bundle directory.
Run the install script.
# ./install
The following options may be used with the install script:
--install <version 11g install bundle path>or-i <version 11g install bundle path>: If you removed the /var/opt/sun/xvm/update-saved-state/ directory, you must use this option to specify the location of the Oracle Enterprise Manager Ops Center 11g install bundle. If the directory is present, this option is unnecessary.
The upgrade is installed on the Proxy Controller. When the upgrade is complete, the install script indicates that all components have been upgraded.
Once you have upgraded your Enterprise Controllers and Proxy Controllers, you can upgrade your Agent Controllers.
You can remotely upgrade Agent Controllers to the latest available version.
Agent Controller files are stored in the /var/opt/sun/xvm/images/agent directory. If you are using disconnected mode, you must add Agent Controller files to the /var/opt/sun/xvm/images/agent directory before they can be used.
Select one or more assets with Agent Controllers.
Select an asset from the All Assets section of the Assets tab.
Select a group that contains operating systems.
Click Upgrade Agent Controller if you selected one asset, or Upgrade All Agent Controllers if you selected a group.
The Upgrade Agent Controllers page is displayed.
Select an upgrade option for the system or systems to be upgraded, then click Next.
The Automatic upgrade option lets you upgrade Agent Controllers without using SSH credentials. The Agent Controllers must be running for an automatic upgrade.
The SSH upgrade using one set of credentials for all targets option prompts you for a single set of SSH credentials for all systems to be upgraded.
The SSH upgrade using individual credentials for each target option prompts you for a separate set of credentials for each system to be upgraded.
The Summary page is displayed.
Click Finish.
The Agent Controller upgrade job is launched.
You can upgrade Agent Controllers manually. Before you upgrade an Agent Controller, you must upgrade the Proxy Controller that manages it.
If you are manually upgrading Agent Controllers running in non-global zones, complete these upgrade steps for any Agent Controller running in the global zone before upgrading all of the non-global zones. The global zone and the non-global zones must all use the same Agent Controller version.
This procedure requires root access.
Copy the new Agent Controller bundle from the Enterprise Controller to the client, remove the existing Agent Controller directory, and extract the new Agent Controller bundle.
For example, on Oracle Solaris Agent Controllers:
# scp <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/SunConnectionAgent.`uname -s`.`uname -p`.12.0.0.2001.zip /var/tmp # cd /var/tmp # rm -r SunConnectionAgent # unzip SunConnectionAgent.`uname -s`.`uname -p`.12.1.0.2001.zip
On Linux Agent Controllers:
# scp -p <IP of Enterprise Controller>:/var/opt/sun/xvm/images/agent/SunConnectionAgent.`uname -s`.i686.12.1.0.2001.zip /var/tmp # cd /var/tmp # rm -r SunConnectionAgent # unzip SunConnectionAgent.`uname -s`.i686.12.1.0.2001.zip
Use the agentadm command with the stop subcommand to stop the Agent Controller.
For example:
./agentadm stop
Install the Agent Controller upgrade.
# cd /var/tmp/SunConnectionAgent # ./install
Use the agentadm command with the configure subcommand and the --keep-connection option to configure the new Agent Controller.
For example:
# ./agentadm configure --keep-connection
This step also starts the Agent Controller.
Note:
The following errors may safely be ignored. These refer to the addition of two sysidcfg scripts, which are already present from a prioragentadm configure step, such as from the original version 11g agent installation and configuration. The correct sysidcfg scripts are called properly by sysidcfg.
Failed to add the zone configuration automation. Failed to add the service tags recreate script.
Verify the connection.
# sc-console list-connections scn-agent https://172.25.14.21:21165 urn:scn:clregid:1234567-aaaa-bbbb-cccc-123456789abc:YYYYMMDDHHMMSSss
You can remotely revert Agent Controllers to a previously installed version.
To Downgrade Agent Controllers
Select a group that contains operating systems with Agent Controllers, then click the Summary tab.
Click the Agent Controllers tab.
Agent Controller information is displayed.
Select one or more Agent Controllers.
Click the Downgrade to Previously Installed Version icon in the center pane.
The Downgrade Wizard is displayed.
Select an option for providing credentials.
Downgrade without requiring credentials
Use an existing set of credentials
Create a new set of credentials
Click Submit.
A job is launched to downgrade the Agent Controllers.