Upgrading to NMS v2.5.0.2
Prior to Oracle Utilities Network Management System 2.5.0.2, a single Oracle RDBMS schema was used for both Data Definition Language (DDL) and Data Manipulation Language (DML) purposes with a second (read-only) access schema used by Oracle NMS clients. Oracle Utilities Network Management System 2.5+ uses at least three Oracle RDBMS schemas.
1. An "admin" schema that that owns all relevant tables and views and allows DDL (for installations and patching).
2. At least one read-write schema that is essentially a list of synonyms that provide DML access to "admin" schema tables and views. If the dual environment setup is chosen - there will be two (parallel) read-write schemas that can be used for access during expedited patching.
3. A read-only schema that is used by WebLogic to provide read-only access to a subset of "admin" schema tables and views. Like the read-write schema - the read-only schema is strictly a set of synonyms (no actual tables or views in this schema). This schema has not fundamentally changed for the 2.5.0.2 release and is only listed for completeness.
The "admin" schema essentially equates to the DDL portion of the "primary" schema for releases of Oracle Utilities Network Management System prior to 2.5.0.2. The new read-write schema (or schemas) equate to the DML portion of the older (single) "primary" schema. This is an important transition that must be worked through for an Oracle Utilities Network Management System 2.5.0.2 upgrade.
Upgrading the Oracle Utilities Network Management System should be done on a test system prior to attempting an upgrade on a production system. Make a complete copy of the production system on a test system, including the file system and the database. Once the test system is running, follow the steps below to upgrade your test system to Oracle Utilities Network Management System Release 2.5.0.2.0. Follow the instructions based on what release you currently have implemented.
When satisfied with your test system, complete these same steps to upgrade your production system.
1. Log in as the administrative user (for example, nmsadmin).
2. Stop all services including Isis.
• For releases prior to NMS 2.5.0.0.0, use the following command:
sms_stop.ces –ai
• For systems running NMS 2.5.0.0.0, use the following command:
sms-stop -ai
Note: If your system does not support the sms_stop.ces or sms-stop script, use:
Action -force any.any stop
cmd shutdown
3. Make sure the Naming Service is not running.
ps -ef | grep tao_cosnaming
If the Naming Service is running, the output will be similar to the following:
nmsadmin 348204 1 0 Aug 11 - 0:46 /opt/oms-9.1/bin/Naming_Service -p /users/oms1/logs/Naming_Service.pid iiop://server.example.com:17821 –ORBEndpoint
If a process is running (user = nmsadmin), kill it:
kill [PID]
From the example output above, the command would be:
kill 348204
4. Stop the currently running WebLogic application server.
Note: This release uses new templates to help properly configure the software. Please pay careful attention to ensure you use the new templates and their settings.
6. Complete all steps in “Starting Isis”.
7. If your Oracle database version is supported by Oracle Utilities Network Management System 2.5.0.2.0, you can skip the Create Database Environment section. Otherwise, do the following:
• Backup your current Oracle Utilities Network Management System database.
• Install the new version of the Oracle RDBMS.
• Complete all steps in “Create Database Environment”, matching the configuration of your previous RDBMS instance.
• Import your current Oracle Utilities Network Management System database onto the new RDBMS installation.
8. If upgrading from a release prior to 2.5.0.0.0, drop the old read only schema and create new read only and read-write schemas based on $NMS_BASE/templates/nms.sql.template.
9. Complete setting up the project configuration directory and upgrading your model following the steps below:
• If you have not already done so, move your project configuration files into the $NMS_CONFIG directories as described in “Project Configuration Directory”.
• Execute the nms-install-config script, which will merge your project configuration with the product configuration and place the results in the runtime directory:
nms-install-config --nojava
11. Execute step 6 of “Validation Model Setup” to enable write permissions for the user that runs the Java Application Server
12. Complete all steps in “Web Application Configuration”.
13. Complete all steps in “Starting Services”.
14. Complete all steps in the “WebLogic Server Runtime Configuration”.
16. If you will be using the web client application installers, complete all steps in “Installing Web Clients”.