18
Monitor Test Reference

The following tests, described in this chapter, are available for monitoring and testing your eMail Server system:

• Configuration Tests

• Database Space Tests

• Directory Service Tests

• Message Flow Tests

• Process Tests

Configuration Tests

eMail Server provides configuration tests that check your system for configuration problems, such as the presence of two SCNs.

Note: Generally, when an error report is produced, you should contact your customer support representative.

Test Name	Condition for Which it Checks
BAD_CM_TO_CM	Pairs of communities that have no message delivery routes connecting them
BAD_CR_CONN	Message delivery routes that have invalid connect communities
BAD_CR_SRC	Message delivery routes that have invalid source communities
BAD_CR_TGT	Message delivery routes that have invalid target communities
BAD_DCNS	Domains with invalid DCN names
BAD_NODE_COMNTY	Nodes that subscribe to invalid communities
BAD_NODE_DOMAIN	Nodes that subscribe to invalid domains
BAD_PARENTS	Domains with invalid parent domains
BAD_PATH_CMNTY	Paths that refer to invalid communities
BAD_PATH_NODE	Paths that refer to invalid nodes
BAD_ROUTE_PATH	Routes with invalid path nodes
BAD_ROUTE_SRC	Routes with invalid source nodes
BAD_ROUTE_TGT	Routes with invalid target nodes
EMPTY_CMNTY	Communities to which no nodes subscribe
MULTIPLE_SCN	Nodes that are designated as the SCN if there are more than one
NO_NODE_TO_NODE	Missing routes from the local node to other nodes
NO_PATH_IN_CMNTY	Nodes that have no path to a community to which they subscribe

Sample Reports Created by Configuration Tests

The following are examples of reports created by the configuration tests.

BAD_CM_TO_CM

There are no community routing records with (source, target) = (COMM_1, COMM_2)

BAD_CR_CONN

Community Routing record 765432 references an invalid connect community 234765

BAD_CR_SRC

Community Routing record 765432 references an invalid source community 276543

BAD_CR_TGT

Community Routing record 765432 references an invalid target community 237654

BAD_DCNS

Domain DOM3.DOM2.DOM1 has an invalid confignode (654123)

BAD_NODE_COMNTY

Node NODE_6 (612345) is subscribed to the invalid community 126543

BAD_NODE_DOMAIN

Node NODE_6 (612345) is subscribed to the invalid domain 165432

BAD_PARENTS

Domain DOM3.DOM2.DOM1 has an invalid parent (123654)

BAD_PATH_CMNTY

Path = 615243 refers to the invalid community = 612354

BAD_PATH_NODE

Path = 615243 refers to the invalid node = 612543

BAD_ROUTE_PATH

Route = 345678 refers to an invalid path 876354

BAD_ROUTE_SRC

Route = 345678 refers to an invalid source node 876543

BAD_ROUTE_TGT

Route = 345678 refers to an invalid target node 876534

EMPTY_CMNTY

Community COMM_4 has no nodes subscribed to it

MULTIPLE_SCN

Node NODE_1 (651234) claims to be an SCN

Node NODE_6 (612345) claims to be an SCN

NO_NODE_TO_NODE

Current node has no route records with node NODE_2 (234567) as target

NO_PATH_IN_CMNTY

Node NODE_8 (987654) has no path for community = 456789

Database Space Tests

Database space tests look for fragmented tablespaces, full tables, and other potential table problems.

Test Name	Condition for Which it Checks
NEW_EXTENT	Segments that have had new extents added since the last report
NEXT_TOO_BIG	Segments for which the next extent is larger than the space available
NEXT_TOO_SMALL	Segments for which the NEXT_EXTENT size seems inappropriate
SEGMENT_FULL	High pairs of PCTUSED and PCTFREE values
TABLESPACE_FRAG	Fragmented tablespaces
TABLESPACE_FULL	Tablespaces that are more than 75% full
TOO_MANY_EXTENTS	Segments approaching the operating system-dependent limit on the number of extents used

Sample Reports Created by Database Space Tests

The following are examples of reports created by the database space tests.

NEW_EXTENT

Node:	Segment:	#:	Num added:	Report date:	Prior date:
OFFICE	OM_STAT_SEGMENT	2	1	27-JAN-93	12-AUG-92

NEXT_TOO_BIG

The following is a list of segments for which the next extent is larger than the space available. If the current extent fills, YOUR SYSTEM WILL STOP. To avoid this, add a file to the tablespace immediately. Then, compact the tablespace.
Node:	Tablespace:	Segment:	Last Extended:	K needed:	K avail.:
OASUN1	OFC_INDB	OM_BODY_K	22-JAN-93	2048	832
OASUN1	OM_EXT_PR	OM_EXT_PR	22-JAN-93	978	832
OASUN1	OFC_INDS	OM_INSTP_	21-JAN-93	1466	1300

NEXT_TOO_SMALL

The following is a list of segments growing by more than one extent every nine days or by fewer than one extent every fifty days. Change the NEXT_EXTENT parameter as suggested below. KEY: #=num extents; Last=date last extended; Curr=current size; Next=next extent size; Sugg=suggested next extent; Max=maximum size
Node:	Segment:	#:	Last:	Curr(K):	Next(K):	Sugg(K):	Max(K):
OFFICE	M_BODY	32	09-DEC-92	16524	600	1348	4532

SEGMENT_FULL

The following is a list of segments for which the PCT_USED plus PCT_FREE totals more than 85. To maximize performance, reduce one or both values.
Node:	Segment:	% Used:	% Free:	Total %:
OASUN1	OM_BODY_K	60	30	90

TABLESPACE_FRAG

The following is a list of tablespaces that contain more than 75 non-contiguous fragments after garbage collection. The number of compacted fragments counts each group of contiguous fragments as one fragment. Within each tablespace, identify the problem tables by their high number of extents. Move them into a separate tablespace, or compact the existing tablespace.
Node:	Tablespace:	Compacted fragments:	Total fragments:
OFFICE	OFFICE	293	554
OASUN1	OFC_INDS	1388	96.49

TABLESPACE_FULL

The following is a list of tablespaces that are more than 75% full. Add new files, or compact the tablespaces.
Node:	Tablespace:	K used:	K available:	% full:
OASUN1	OFC_INDB	58876	1280	97.87
OASUN1	OFC_INDS	38180	1388	96.49

TOO_MANY_EXTENTS

The following is a list of segments for which the number of extents is approaching the system-dependent limit. If this number reaches the limit, YOUR SYSTEM WILL STOP. To avoid this, compact the problem segments. Or, use the MAX_EXTENTS parameter to override the limit on a table-by-table basis.
Node:	Segment:	Last Extended:	Num extents:	Max extents:	Extents/wk:
OASUN1	OM_BODY_K	21-JAN-93	70	99	.197
OASUN1	OM_INST_R	21-JAN-93	89	99	.251

Directory Service Tests

eMail Server provides directory service tests that check your system for configuration problems, such as empty distribution lists.

Test Name	Condition for Which it Checks
CLASSID_CHECK	Class IDs that have no global ID
DSSALL_CHECK	Whether ALL has a global ID
EMPTY_LISTS	Empty distribution lists
MISSING_OBJECTS	Missing eMail Server tables, views, synonyms, sequences, or indexes
REPLOG_TOO_BIG	Whether the number of entries in the replicator log is more than four times the number set in logScanSize
REPL_UNACKED	The number of unacknowledged packages if there is more than one

Sample Reports Created by Directory Service Tests

The following are examples of reports created by the directory service tests.

CLASSID_CHECK

Missing GlobalID for class 123456

DSSALL_CHECK

Missing GlobalID for "All"

EMPTY_LISTS

Distribution List LIST_3 (654321) has no elements

MISSING_OBJECTS

Missing SCHEDULE from schema: OAGRP.VACATION_TIME

REPLOG_TOO_BIG

Too many unpackaged rows in the replog 400

REPL_UNACKED

Package outstanding for DOMAIN_7 to DOMAIN_5 package no. 721

Message Flow Tests

eMail Server provides message flow tests that check your system for configuration problems, such as nodes with long distribution times.

Test Name	Condition for Which it Checks
DELIV_NODE	Nodes with long delivery times to the local node
DELIV_TOTAL_REC	Long delivery times for all messages received by the local node
QUEUE_STATUS	Oldest queued message

Sample Reports Created by Message Flow Tests

The following are examples of reports created by the message flow tests.

DELIV_NODE

The following is a list of delivery statistics for nodes from which this node has received less than 90% of sent messages in under 5 minutes.
Source Node:	Average (min):	Tot. msgs:	% 15 min:	% 5 min:	% 1 min:	% 30 sec
Bob	100	865	94.5	85.3	71.4	58.6

DELIV_TOTAL_REC

This node has received less than 90% of its messages in under 5 minutes.
Average (min):	Tot. msgs:	% 15 min:	% 5 min:	% 1 min:	% 30 sec
100	865	94.5	85.3	71.4	58.6

QUEUE_STATUS

Queue Status:

Node: OASUN1 Oldest of 10 SUBMISSION msgs was 10 hours old on 28-JAN-98 10:34

Gateway: INTEROFFICE on node INTEROFFICE backed up delivering 4 msgs since 27-JAN-98 23:26

Summary: Node INTEROFFICE Backed up sending 4 msgs to INTEROFFICE since 27-JAN-98 23:26

Process Tests

eMail Server provides process tests that check your system for process problems, such as missing data accounts.

Test Name	Condition for Which it Checks
NO_REPL	Missing database account for the replicator
NO_SCHED	Missing database account for the scheduler
PROCESS_TIME	Last wake and sleep times for server processes

Sample Reports Created by Process Tests

The following are examples of reports created by the process tests.

NO_REPL

Replicator account does not exist or is not an Oracle account

NO_SCHED

Scheduler account does not exist or is not an Oracle account

PROCESS_TIME

Last wake and sleep times for server processes.
Process:	Instance:	Last Wake:	Last Sleep:	Current Time:
Postman	1	23-JAN-98 18:30	23-JAN-93 19:30	23-JAN-98 20:00
Postman	2	NOT ACTIVE	NOT ACTIVE	23-JAN-98 20:00
Collector	1	23-JAN-98 00:30	23-JAN-98 06:30	23-JAN-98 20:00