For example, Oracle Internet Directory (OID), one of the major components of Oracle Identity
Management, requires database tuning somewhat like tuning for an OLTP system, with many short
transactions from a large number of users with widely varying loads depending on the time of
day. But that is where the similarity ends! In Table 9-1 are some general guidelines for setting
various system-initialization parameters for the database that will be maintaining the Lightweight
Directory Access Protocol (LDAP) directory information.
It is assumed that this database??™s only job is to maintain OID directory information. In addition
to tuning basic database parameters, overall throughput will depend on factors such as network
bandwidth available between the server and the user community, the location of shared disk
resources, disk throughput, and so forth. A typical IM deployment with 500,000 directory entries
will require approximately 3GB of disk space, and how fast or how slow the entries can be written
to or read from disk can easily become the throughput bottleneck.
Database Parameter 500 Concurrent Users 2000 Concurrent Users
OPEN_CURSORS 200 200
SESSIONS 225 1200
DB_BLOCK_SIZE 8K 8K
DB_CACHE_SIZE 250MB 250MB
SHARED_POOL_SIZE 40MB 40MB
PROCESSES 400 1500
SORT_AREA_SIZE 256KB 256KB
LOG_BUFFER 512KB 512KB
TABLE 1-1 Database Initialization Parameter Sizing for OID
288 Oracle Database 11g DBA Handbook
User Accounts
In order to gain access to the database, a user must provide a username to access the resources
associated with that account.
Pages:
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486