Kbase 41094: Basic Oracle requirements that can be applied to an Oracle connected to SonicMQ 4.02
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P11094
GOAL:
Is there a basic Oracle requirements that can be applied to an Oracle instance connected to SonicMQ 4.02 ?
FIX:
The amount of tablespace depends on how many messages will be stored to the
database. With durable subscriptions, estimate the number and size of messages that will be stored per disconnected durable subscriber.
(In cases where the same message is saved for multiple durable subscribers, Sonic
saves only one copy of the message).
If point to point messages are saved to the db, estimate the number and size of messages per queue.
The other tables are not that big compared to the tables that hold messages.
On top of the data size, add an overhead factor to account for space used by Oracle. The Oracle documentation recommends an overhead factor to use.
As to privileges, when running dbtool, the userid must have privileges for creating and deleting tables and indexes.
During runtime, the Broker performs only updates, deletes. and inserts of table rows.
The userid should have a generous amount of rollback segment space to accommodate a large transaction size. The transaction size is controlled by broker parameters SAVE_QUEUE_SIZE and DB_COMMIT_BATCH_SIZE. For example, The default DB_COMMIT_BATCH_SIZE is 1000, which means that up to 1000 messages can be deleted in a transaction. The most common issue I've seen come up with oracle is that the rollback seqment size is configured too small.