How to manually extend the ZCM 10.2 database schema

  • 7003450
  • 04-Jun-2009
  • 25-May-2016

Environment


Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2 Database

Situation

database schema was not extended properly during the upgrade process.

Resolution

The database can be extended manually with the following procedure:

Backup the ZCM database!
zman db <backup directory>  Backs up the embedded Sybase SQL Anywhere database and also allows you to schedule the backup operation. 
 <backup directory> - The local directory on the database server or the network location where the database files are backed up. Ensure that the parent directory already exists and has sufficient disk space.
Extending the Schema:
Extract the novell/zenworks/works/system-update/apply/UID/pre-global-actions-10.2.0.jar
on Windows:  C:\Program Files\Novell\ZENworks\work\system-update\apply\<guid>\pre-globalactions-10.2.0.jar
on Linux /var/opt/novell/zenworks/content-repo/system-update/<guid>/pre-globalactions-10.2.0.jar

Directory contents:
\com
\meta-inf
\oracle
\sql-anywhere
\sql-server
 
The bottom 3 folders contain the .sql files that get ran to extend the schema on a database. Use the named folder for the type of database respectively.  The .sql files have to be ran in a specific order.  This order is can be followed in the \meta-inf\system-update.properites file from the pre-globalactions extraction done earlier.
Each .sql is separated by a semicolon. Make sure each one completes before running the next..  If the sql file is not found in the extracted location, just move on to the next
 
ZCM install dbisql.exe with the embeded sybase database which can be used to run the .sql scripts. For authentication you will need to run the zman dgc command to get the login credentials.
 
If you get any errors on a .sql script, run it again as a table lock could be the cause and rerunning the script often proves to be successful.

reboot ZCM server
 

Additional Information

10.2 update shows that the installation was successful, but getting SQLException Errors in the loader-messages.log reading database information correctly.

Information could be missing in ZCC on different configuration pages.