We recommend you to set the database cache size as follows by configuring the -c parameter in the Sybase startup:
Table M-1 Recommended total system memory and Sybase cache memory
|
Inventoried Workstations in the Database (in thousands) |
Total Memory of the System |
Sybase Cache Memory |
|---|---|---|
|
less than 1 |
384 MB |
128 MB |
|
1 - 5 |
512 MB |
128 MB |
|
5 - 10 |
512 MB - 768 MB |
128 MB - 256 MB |
|
10 - 25 |
768 MB - 1 GB |
256 MB - 400 MB |
|
greater than 25 |
1 - 2 GB |
30 - 40% of RAM |
If you have more than 5,000 workstations, we recommend that you use multiprocessors for servers hosting the database and span the data files.
If you have more than 10,000 workstations, we recommend that you use a dedicated server for the database.
The following table lists the free hard disk space recommendations:
Table M-2 Recommended free hard disk space
|
Inventoried Workstations in the Database (thousands) |
Free Hard Disk Space (GB) |
|---|---|
|
Up to 5 |
1 |
|
Up to 10 |
2 |
|
Up to 15 |
3 |
|
Up to 20 |
5 |
|
Up to 25 |
6 |
|
Up to 30 |
7 |
|
Up to 35 |
8 |
|
Up to 40 |
9 |
|
Up to 45 |
11 |
IMPORTANT:Make sure that the drives in which the database files are located have sufficient additional free disk space for storing the temporary files generated during the operations of Inventory ConsoleOne utilities.
If the Storer is taking significant time to store the inventory information in the following scenarios, you can run the Sybindex utility to improve the Storer performance:
Many Inventory agents are simultaneously upgraded to ZENworks 7 and subsequently, all these agents send the full scans for the time to the Inventory server.
The administrator manually triggers full scan from the Inventory Service object resulting in all Inventory agents send the full scan to the Inventory server.
The Inventory database is either re-installed or changed and then the administrator manually triggers full scan from the Inventory Service object resulting in all Inventory agents sending the full scan to the Inventory server.
Before running the Sybindex utility, make sure that the Sybase Inventory database is up and running, and then stop the Storer.
If you have ZENworks 7 Desktop Management installed, do the following to run the Sybindex utility. If you have ZENworks 7 Desktop Management with Support Pack 1 installed, see Section M.3, Performance Tips for the Inventory Server ( Support Pack 1) to run the Sybindex utility.
On a NetWare server: At the server console prompt, enter sybindex.
On a Windows server: At the server command prompt, go to inventory_server_installation_path\zenworks\inv\server\wminv\ bin and enter sybindex.
On a Linux server: At the server command prompt, go to /opt/novell/bin and enter sybindex.
NOTE:If the Sybase Inventory database is either not hosted on the current Inventory server or is running on a port other than 2638, edit the sybindex.ncf (on NetWare), sybindex.bat (on Windows), or sybindex (on Linux) to change the host and port before running sybindex.
Stop the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
Close all connections to the Inventory database.
Quit the Sybase server.
Open the mgmtdbs.ncf file in the sys:\system directory.
Modify the -c parameter.
For example, -c 64M sets the cache size to 64 MB.
Save the file.
On the server console, load the Inventory database. Enter MGMTDBS.
Start the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
Stop the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
Stop the Sybase service.
On Windows 2000/2003, in the Control Panel, double-click , double-click , select , then click .
On the database server, run the ntdbconfig.exe file from the inventory_database_installation_path\zenworks\database\dbengine directory.
Ntdbconfig.exe is a ZENworks database configuration utility for the ZENworks database using Sybase on Windows servers. This utility enables you to reconfigure the Sybase service. For the list of parameters recommended by Sybase, see Understanding the Sybase Database Startup Parameters.
Modify the -c parameter.
Click .
Restart the Sybase service.
On Windows 2000/2003, in the Control Panel, double-click , double-click , select , then click .
Stop the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
Stop the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
Close all connections to the Inventory database.
Quit the Sybase server.
Open the mgmtdbs.sh file in the /opt/novell/zenworks/bin/ directory.
Modify the -c parameter.
For example, -c 64M sets the cache size to 64 MB.
Save the file.
On the server console, load the Inventory database. Enter MGMTDBS.
Start the Inventory service. For more information, see Section 73.1.5, Starting and Stopping the Inventory Service.
For more information on Performance tips, see Section M.1, Database Parameter Tuning Tips.
Use the following memory recommendations:
Table M-3 Recommended total system memory and Oracle SGA memory
|
Inventoried Workstations in the Database (in thousands) |
Total Memory of the System |
Oracle SGA Memory |
|---|---|---|
|
less than 1 |
512 MB |
128 MB |
|
1 - 5 |
768 MB |
256 MB |
|
5 - 10 |
1 GB |
400 MB |
|
10 - 100 |
1 GB - 2 GB |
40% of the total memory |
Use the following disk space recommendations:
Table M-4 Recommended free hard disk space
|
Inventoried Workstations in the Database (thousands) |
Free Hard Disk Space (GB) |
|---|---|
|
Up to 5 |
3 |
|
Up to 10 |
6 |
|
Up to 15 |
9 |
|
Up to 20 |
11 |
|
Up to 25 |
12 |
|
Up to 30 |
13 |
|
Up to 35 |
15 |
|
Up to 40 |
20 |
|
Up to 45 |
25 |
IMPORTANT:Make sure that the drives in which the database files are located have sufficient additional free disk space for storing the temporary files generated during the operations of Inventory ConsoleOne utilities.
Stop unnecessary services and applications running on the server to enable a background service such as Oracle server to run.
We recommend that you use a dedicated server to host the Oracle database.
Span the data files across multiple physical disks if you have more than 10,000 workstations.
Set the virtual memory value between 2 - 4 times the RAM.
We recommend that you use multiprocessors for servers hosting the database.
Refer to the Oracle performance tuning documentation and other general recommendations that are listed in the Section M.5, References section.
Reduce the priority of the foreground application.
Reduce the file cache value and maximize data for network applications.
Modify the init.ora file for specific organizational requirements.
For example, to obtain about 260 MB of Oracle SGA with db_block_size=4096, modify the init.ora file with the following values:
Invoke and append lines to the _ start.sql file. The _start.sql file is invoked by the mgmtdbo.ncf or the mgmtdbo.bat file when you start the Inventory database instance. Append the following lines to the existing _start.sql file:
connect mw_dba;alter table cim.t$product cache;
If you run the Inventory database on Oracle9i, you can set db_cache_size instead of db_block_buffers * db_block_size.
Refer to the Oracle Administration guide or Performance guide for more information.
If you have an Inventory database on Oracle, you can improve the performance of the database when you generate the inventory reports or query the database.
You use the database buffer cache to store the most recently used data blocks. The database cache is determined as db_block_buffers * db_block_size. These parameters are specified in the zenworks\database\init.ora file on the database server.
DB_BLOCK_BUFFERS specifies the number of database buffers. DB_BLOCK_SIZE specifies the size of each database buffer in bytes.
The size of each buffer in the buffer cache is equal to the size of the data block.
If there is additional memory, you configure the database cache size by increasing the DB_BLOCK_BUFFERS parameter in the init.ora file. If you run Inventory database on Oracle9i, you can set db_cache_size instead of db_block_buffers * db_block_size
For more information for Performing tips, see Section M.1, Database Parameter Tuning Tips.
We recommend that you use a dedicated server for MS SQL.
On the MS SQL server, make sure that the tempdb system database is located on the drive having sufficient disk space.
Boost the MS SQL server priority.
Enable optimization for background services.
Use the configuration in the following table:
Table M-5 Recommended total system memory, processor speed and MS SQL cache memory
|
Inventoried Workstations in the Database (thousands) |
Total Memory of the System |
MS SQL Cache Memory |
Processor Speed |
|---|---|---|---|
|
less than 10 |
512 MB |
256 MB |
Pentium III: 450 M Hz |
|
10 - 20 |
512 MB - 1 GB |
256 MB - 384 MB |
Pentium 4: 1.8 G Hz |
|
20 - 50 |
1 GB - 1.5 GB |
512 MB - 768 MB |
Pentium 4: 1.8 G Hz |
Use the following disk space recommendations:
Table M-6 Recommended free hard disk space
|
Inventoried Workstations in the Database (thousands) |
Free Hard Disk Space (GB) |
|---|---|
|
Up to 5 |
5 |
|
Up to 10 |
10 |
|
Up to 15 |
15 |
|
Up to 20 |
20 |
|
Up to 25 |
26 |
|
Up to 30 |
31 |
|
Up to 35 |
36 |
|
Up to 40 |
41 |
|
Up to 45 |
46 |
Span the data files across the multiple physical disks if you have more than 5,000 workstations.
We recommend that you use multiprocessors for servers hosting the database.
For additional tips on MS SQL, refer to the MS SQL Server documentation.