1. Stop the Inventory service.

   • On a NetWare Inventory server at the server console prompt, enter:

     sys:\system\invstop.ncf
     

     NOTE:If you do not want the Sybase database to be stopped automatically when you stop the Inventory services, comment the Unload dbsrv8.nlmline in the sys:\system\invstop.ncf file.

   • On a Windows 2000/2003 Inventory server in the Control Panel, double-click Administrative Tools, double-click Services, right-click Novell Inventory Service, then click Stop.

2. Stop the Inventory database.

   To stop the Sybase Inventory database:

   • On NetWare at the Sybase console prompt, press the q key.

   • On Windows 2000/2003 in the Control Panel, double-click Administrative Tools, double-click Services, right-click Novell Database - Sybase, then click Stop.

3. Stop the Novell ZENworks Service Manager service.

   • On Windows 2000 Server in the Control Panel, double-click Administrative Tools, double-click Services, right-click Novell ZENworks Service Manager, then click Stop.

4. If Java has not been unloaded on the target NetWare servers, unload java.nlm (at the server console, enter java -exit).

   IMPORTANT:This command stops all Java processes running on the server. Verify that all Java processes can be stopped while you are installing Server Management.

5. On the target Windows servers, close the Services window.

6. Make sure that you have archived a reliable backup of the ZENworks 6.5 Server Management or ZENworks 6.5 SP1/SP2 Server Management database.

7. Before upgrading the Inventory server, make sure that you have upgraded its associated database server.

8. Make sure that the ZENworks 6.5 Server Management or ZENworks 6.5 SP1/SP2 Server Management database is not accessed from ConsoleOne.

9. Make sure that the recommended ZENworks 7 with SP1 Server Inventory system requirements are met. For more information, see Section 5.0, Server Requirements.

10. If ZENworks_installation_path\zenworks\inv\server\wminv\ properties\inventoryremoval.properties has been modified after the ZENworks 6.5 Server Management or ZENworks 6.5 SP1/SP2 Server Management installation, take a reliable backup of inventoryremoval.properties.

11. Make sure that the Policy and Distribution Services have been upgraded to ZENworks 7 with SP1.

    For more information on how to upgrade Policy and Distribution Services to ZENworks 7 with SP1, see Section 12.0, Version 3.0.2 Policy and Distribution Services.

12. Make sure that the schema is migrated to ZENworks 7 with SP1.

    You can migrate the schema by using the ZENworks 7 Server Management with SP1 installation program. For more information on how to migrate the schema, see Extending the Schema.

13. If you have a ZENworks 6.5 Server Management or ZENworks 6.5 SP1/SP2 Server Management Oracle Inventory database, you must perform the following tasks before the migration:

    1. Ensure that the Oracle’s version is 9.2.0.6 or later.

    2. In inventory_database_installation_path\init.ora_path\init.ora, set the values of the following parameters as shown:

       • db_cache_size=192M
       • sort_area_size=10000000
       • shared_pool_size = 157286400
       • open_cursors = 2048
       • log_buffer = 1024000
       • session_cached_cursors=2048
       • compatible=9.2.0

       You can increase the cache size and shared pool to have Shared Global Area (SGA) to 30-40% physical RAM size.!!!

    3. Ensure that the Inventory database is up and running.

    4. You must have a larger rollback segment because the database migration and the storage of further data cannot succeed because of ORA-01555 and other rollback segment-related issues.

       To increase the value of the rollback segment, execute the following SQL script to add an additional data file to the rollback segment (RBS) and to add a Redo log group:

       connect / as sysdba;
       

       alter tablespace rbs add datafile ’Inventory_database_installation_path\rbs2.ora’ size 40M autoextend on next 50K maxsize 60M;
       

       alter rollback segment rb0 storage (maxextents unlimited);
       

       alter rollback segment rb1 storage (maxextents unlimited); 
       

       ALTER DATABASE ADD LOGFILE GROUP 3 (’Inventory_database_installation_path\log3.ora’) SIZE 50M;
       

    5. Stop the Inventory database.

    6. Ensure that the value of the compatible parameter in inventory_database_installation_path\path_to_init.ora\init.ora is set to 9.2.0 or later.

    7. If the size of any data file is about to exceed 4096 MB, you must add extra data files to the corresponding tablespace.

    8. Extract the appropriate platform-specific atlasperf_altertablespace.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip to C:.

       If Oracle is running on Windows, extract atlasperf_altertablespace.sql from the oracle\winntspecific directory within sql.zip.

       If Oracle is running on UNIX, extract atlasperf_altertablespace.sql from the oracle\unixspecific directory within sql.zip.

    9. Edit atlasperf_altertablespace.sql to set the value of MAXSIZE for all data files to the nearest multiple of 4 GB.

       For example, if the size of CIM8.ora is 5 GB, then set the value of MAXSIZE to 8192 MB.

    10. Ensure that the file path of all data files listed in atlasperf_altertablespace.sql is correct.

    11. Restart the Inventory database.

    12. Execute altaslperf_altertablespace.sql.

1. Stop the Inventory service.

2. On an Oracle Inventory database, do the following to improve the database performance:

   1. Extract atlasperf_alterfreelist.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip and execute it at the SQLPLUS prompt.

   2. Execute the oracle\common\oracle_perf.sql and oracle\common\oracle_perf2.sql files from Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip to add performance enhancing indexes to the database.

   3. Execute oracle_dbexport_perf.sql from the Novell ZENworks 7 with Support Pack 1 Companion 2 CD’s \database\oracle9i\common directory.

   4. (Conditional) If you are migrating from ZENworks 6.5 SP1 Server Management Hot Patch 1 or Hot Patch 2, or ZENworks 6.5 SP2 Server Management, extract \oralce\common\zfd65sp1hp1_65sp2_70.sql from ZENworks_installation_directory\zenworks\inv\server\wminv\properties\sql.zip and execute it at the SQLPLUS prompt.

      For more information on how to improve the performance of the Inventory database, see Performance Tips in the Novell ZENworks 7 Server Management Administration Guide.

3. On a MS SQL Inventory database, use the MS SQL Query Analyzer to execute the following scripts from Inventory_server_installation_path\zenworks\inv\server\wminv\properties\sql.zip using the appropriate user login:

   1. Log in as “CIM” and execute mssql_perf_cim.sql.

   2. Log in as “mw_dba” and execute mssql_perf_mw_dba.sql.

   3. Log in as “zenworks” and execute msswl_perf_zenworks.sql.

   4. (Conditional) If you are migrating from ZENworks 6.5 SP1 Server Management Hot Patch 1 or Hot Patch 2, or ZENworks 6.5 SP2 Server Management, log in as “CIM” and execute \mssql\zfd65sp1hp1_65sp2_70.sql.

      For more information on how to improve the performance of the Inventory database, see Performance Tips in the Novell ZENworks 7 Server Management Administration Guide

4. Start the Inventory services.

1. Review the Section 13.2.1, Pre-Upgrade Considerations.

2. Upgrade Policy and Distribution Services to ZENworks 7 with SP1.

   For more information on how to upgrade Policy and Distribution Services to ZENworks 7 with SP1, see Section 12.0, Version 3.0.2 Policy and Distribution Services.

3. If you plan to upgrade the Inventory Agent from ZENworks 6.5 SP1 Server Management Hot Patch 1, Hot Patch 2, or Hot Patch 3 to ZENworks 7 Server Management with SP1, you must apply the patch available with TID 103465 before installing the support pack. For more information, see TID 103465 in the Novell Support Knowledgebase.

To automatically install the Inventory Agent .cpk file:

1. Copy zsm7_inv_agnt.cpk from Novell ZENworks 7 with Support Pack 1 Compaion 3 CD’s \zenworks server management - software pkgs\invrm directory to a temporary directory on the Distributor server that you use to install the software package.

2. Set the Subscriber’s Extract schedule.

   If the schedule is set to Run Immediate, you might interrupt the sending of the Distribution to Subscribers, because the update process involves unloading Java. With Java unloaded, Distributions are temporarily halted until Java is reloaded and the Channel’s Send schedule fires.

   If the Subscriber is a parent that is sending the Distribution to subordinate Subscribers, it will be in the process of sending the Distribution when the software package tries to unload Java. However, the Distributions will continue from where they left off after Java is started again.

3. Create a Distribution for this software package.

   You can have only one software package per Distribution object. Although the software allows more than one software package to be selected in a single Distribution object, this is not permitted when distributing the ZENworks 7 Server Management with SP1 software packages. The reason is that installing a software package unloads and reloads Java, which can prevent the remaining software packages from being successfully processed from a single Distribution object.

   Make sure you set the Distribution’s Build schedule.

   The Distribution containing ZENworks 7 Server Management with SP1 must be built, sent, extracted, and installed before sending any other Distributions containing other ZENworks 7 Server Management with SP1 software packages.

   For detailed instructions on creating Distributions, see Tiered Electronic Distribution in the Novell ZENworks 7 Server Management Administration Guide.

4. Associate the Distribution with a Channel so that it is sent based on the Channel’s schedule.

   You might need to create the Channel. Be sure to set the Channel’s Send schedule.

   The ZENworks 7 Server Management with SP1 software packages unload and restart Java as part of the installation process. Therefore, you must process each software package individually. If you attempt to process multiple ZENworks 7 Server Management with SP1 software packages simultaneously (such as by processing them at the same time in a given Channel), it is probable that one or more of the Software Package Distributions fails on installation.

5. Associate the Subscribers that you want to receive this software package with the Channel.

6. Send the Distribution.

   For example, refresh the Distributor to build the Distribution so that it can be sent and extracted. For detailed information on sending distributions, see Tiered Electronic Distribution in the Novell ZENworks 7 Server Management Administration Guide.

   The Distribution is automatically created when the Distribution’s Build schedule starts. The Distribution is automatically be sent when the Channel’s Send schedule starts. It is extracted according to the Subscriber server’s Extract schedule.

7. Review the following log files to verify the success or failure of the Inventory Agent .cpk file installation:

   • On a NetWare server: sys:\etc\cpk7logs\cpk7_invagnt.log

   • On a Windows server: %windir%\cpk7logs\cpk7_invagnt.log

   If the .cpk file is successfully installed, the ZENworks service is automatically started.

   NOTE:During the NetWare Inventory agent upgrade, all of the Java services including the ZENworks service is automatically terminated. After the upgrade, only the ZENworks service is automatically started; you must manually start all other Java services.

1. Ensure that the value of InvAgentPath in sys:\system\zenworks.properties is volume_name:\zenworks\inv\agent.

2. Follow steps explained in Upgrading the Inventory Agent Using the Software Package.

   NOTE:During the NetWare Inventory agent upgrade, all of the Java services including the ZENworks service is automatically terminated. After the upgrade, only the ZENworks service is automatically started; you must manually start all other Java services.