Monitoring database tables
Many different database tables and indexes are involved
in the processing of messages, but some merely hold state data or
are used infrequently, and so do not normally need to be monitored.
Database tables
contains a complete list of these tables and
indexes. To determine the health of your system, check at least those
tables listed in Table 1 that
correspond to services that you use.
| Service | Table name | Description |
|---|---|---|
| (all services) | schema.DNI_EVENT | FTM SWIFT events are stored into this table. If this table is in danger of becoming full, delete or archive the data it contains. How to do this is described in Managing FTM SWIFT data. |
| Audit | schema.DNI_A_MSG_ou | If auditing is enabled for an OU, FTM SWIFT stores audit entries in its audit table. The number of entries depends on the number of audit points enabled and the number of messages processed. If this table is in danger of becoming full, archive the data it contains. |
| Message warehouse | schema.DNIMWH_PTou
schema.DNFMWHFIN_ou schema.DNFMWHEIA_ou schema.DNFMWHOEM_ou schema.DNFMWHOEF_ou schema.DNFMWHENI_ou |
If message warehousing is enabled, FTM SWIFT stores each FIN, InterAct, and FileAct message in the message warehouse tables of the corresponding OU. The number of entries depends on the number of message warehouse settings enabled and the number of messages processed. If the tables are in danger of becoming full, archive the data they contain. |
| SIPN FIN | schema.DNF_OAMS | This table holds FIN messages that are about to be sent, and those that were already sent. Once processed, the entries are deleted. If, in spite of this, the table is in danger of becoming full, increase its size. |
| schema.DNF_IAMS | This table holds FIN messages that were received. Once processed, the entries are deleted. If, in spite of this, the table is in danger of becoming full, increase its size. | |
| schema.DNF_MSGS | This table holds SWIFTNet FIN messages that are awaiting delivery notification. If this table is in danger of becoming full, increase its size. Regularly clean up this table as described in Cleaning up MessageGroup store data (FIN only). | |
| schema.DNFV_REQUEST | This table holds signature verification requests to be processed by the DNF_V_REQ service. If this table is in danger of becoming full, increase its size. | |
| SIPN FIN or MSIF | schema.DNF_RMRL
schema.DNF_RMAD schema.DNF_RMAL schema.DNF_RMAP |
These tables hold RM data (authorisations and permissions) as required for RM checks during SIPN FIN and MSIF processing. The data can result from importing from an RMA distribution file, or from maintaining RM relationships using the FTM SWIFT RMA. If the tables are in danger of becoming full, increase their size. |
schema.DNF_RMAH
schema.DNF_RMQS schema.DNF_RMQH schema.DNF_RMSS |
These tables hold data related to managing relationships with the FTM SWIFT RMA (queries, answers, change history, and network states). If the tables are in danger of becoming full, increase their size. | |
| MER Facility | schema.DNQE_MESSAGE | This table holds an entry for each message that is to be processed by the Message Entry and Repair (MER) Facility |
| Printing | schema.DNQP_CONTENT | This table holds an entry for each message that is to be printed. |