Cisco Cisco Prime Service Catalog 10.0 Referencia técnica
5-6
Cisco Prime Service Catalog 10.0 Configuration Guide
OL-31034-01
Chapter 5 System Administration
Ongoing Infrastructure Maintenance Tasks
Specific Recommendations for Service Catalog
•
For the OLTP database, create a primary tablespace named REQUESTCENTER. Allow for 10 MB
per user, with a minimum size of 500 MB, for the tablespace. Your database administrator should
choose an extent management strategy that fits well with the best practices of your organization.
per user, with a minimum size of 500 MB, for the tablespace. Your database administrator should
choose an extent management strategy that fits well with the best practices of your organization.
•
A very rough estimate of database storage required is 500 KB for each requisition completed. This
varies greatly with the complexity of the service form, the authorization structure, and the delivery
plan.
varies greatly with the complexity of the service form, the authorization structure, and the delivery
plan.
•
Sites with many Service Link tasks will notice significant growth in the database size, attributable
to storing Service Link messages. Recent versions of Service Catalog have included increasingly
effective compression algorithms for these messages, as well as a means to configure message
context. Additional details are available in the
to storing Service Link messages. Recent versions of Service Catalog have included increasingly
effective compression algorithms for these messages, as well as a means to configure message
context. Additional details are available in the
Database scripts for purging Service Link messages for completed tasks are available as stored
procedures in the RequestCenter database and can be executed either as a one-time job or on a
recurring basis.
procedures in the RequestCenter database and can be executed either as a one-time job or on a
recurring basis.
Tuning Oracle
•
Gather statistics on the OLTP database (both tables and indexes) on a regular basis. This can be
automated via Oracle Enterprise Manager (OEM).
automated via Oracle Enterprise Manager (OEM).
•
Perform column-level histogram analysis to further optimize the Service Manager indexes.
•
Gather statistics on the Service Catalog data marts after the data marts have been refreshed.
•
Review table allocation, tablespace fragmentation, and row chaining.
•
Grant access to the SELECT_CATALOG_ROLE for monitoring query performance.
•
For Oracle, apply settings similar to the following:
Gather Statistics on the Database
Use the DBMS_STATS.GATHER_SCHEMA_STATS command to gather statistics on all tables and
indexes in the RequestCenter database. In the example below, “RC User” is the schema owner.
indexes in the RequestCenter database. In the example below, “RC User” is the schema owner.
execute DBMS_STATS.GATHER_SCHEMA_STATS(ownname=>'RCUser',cascade=>TRUE);
Histogram Analysis
The Oracle Database Administration chapter on “Managing Optimizer Statistics” recommends:
Parameter
Value
perf.__large_pool_size
16777216
*.processes
300
*.pga_aggregate_target
1059145600
*.sga_max_size
716582400 #internally adjusted
*.sga_target
716582400
*.sort_area_size
500000000