Information Management-History Runtime Index.
We have two IM servers. In one of ther IM server i.e IM1 Message Log stopped appearing from a week. Where as in other IM server, it is working fine.Configuration of Both IM servers are same.
As suggested in this forum, i have increase the size of History Runtime index for IM1. and the Message log of this IM server started working.
Now my question is with time, will the History Runtime index again reach maximum size? and stop working. Since over two days of observation i saw some increase in runtime history index current usage.
While creating IM server i have opted message log for 10million. and it calulates automatic storage space near about 46GB.
Then i executed the Sql query for msg count. i got max rows, overflow and log count detais, as 10million , above 10 million . attached the screenshots.
the message log count is around 6 million. will it increase in future? If it reached 10 million what happens?
Even though IM2 server same configuration for same number of logs, the message log appears 4 million? and Sql querry dont shows overflow details with message, table space not exist. But shown msg count aroung 4 million.
thanks in advance.
Voted best answer
The message Log should increase upto max capacity.
Looking at the Table space, following would be the suggesteion:-
History Runtime Data: auto extend 512Meg, max size 20000 meg
Oracle undo Rollback auto extend 512meg, max size 4000 meg
Also I hope you have archiving configured otherwis after reaching Max capacity, older entries will keep on overwriting with the New Entries.
It will be good if you can stagger the Oracle database and provide the report.
The Oracle Instance wizard's automatic calculation of required tablespace is only a recommendation based on a simple ruleset with approximated values.
The actual use of tablespace is influenced by factors the automatic calculation has no means to cover for, e.g. the amount of attributes per event and the length of descriptions and other attributes attached to the events.
The tablespace storage may change even after an event log has reached its capacity and the oldest events are overwritten by the most recent. E.g. additional tablespace will become required if the events become with longer strings and/or more attributes.
Bottomline: tablespace usage is only a prediction. The system administrator need to keep an eye on the usage as it may change over time, e.g. if the control system is changed to emit more dense data. If a tablespace run full, event storage may stop until additional space has been allocated (either manually, or via increase of auto-extend limit).
If two IM servers run with identical configuration and is connected to the same system and configured with the same IM Event Collection filter (yes, each IM may have a filter limiting what it is storing) they should, over time come to about the same amount of tablespace usage.
Always do the sizing for the oracle table space in such way that it can auto extend upto 32GB instance
Ensure you have enough storage space before going ahead.
Enable autoextend,limit and extend by else ex:if Oracle History table space for Index and Runtime is configured for min then the messages will be lost when these tables are reach their max values