This time we will monitor tablespace stats. I’d like to create one stats table per tablespace and use the same technique as in Part 1
Our customer runs Oracle database and my chief has given me a task to do for today.
I need to prepare prognosis of how much oracle database will grow in next 3 years. After short googling I’ve found interesting sripts :
select sum(bytes)/1024/1024 "Meg" from dba_data_files; select nvl(sum(bytes),0)/1024/1024 "Meg" from dba_temp_files; select sum(bytes)/1024/1024 "Meg" from sys.v_$log; select sum(BLOCK_SIZE*FILE_SIZE_BLKS/1024/1024) "MEG" from v$controlfile;
The main idea is to create oracle DBMS job which will fire each hour for let’s say 7 days (yeah, we’ve got only 7 days :() and outputs statistics about database size into some database table.
Now SyslogMessageMapper is completed so lets move on and take a look on Syslog itself.
Now when SyslogSessionMapper has been implemented, it time to finish SyslogMessageMapper. But before let’s remind us syslog use-case .
One thing that we will have to implement is retrieving syslog messages using different conditions. Here is preliminary list of conditions:
The list can be continued…
This is the best place to use Query Object pattern. For futher reading please refer to:
I’d like to take some time about base classes implementation, since we will use query object pattern in groupchat logger plugin. This plugin will store log of xmpp groupchat (conference) and we need to provide flexible OO mechanism for retrieving chat messages from log. So it would be nice to implement base classes for SyslogMessageMapper and reuse them later :)
I’ve implemented SyslogSessionMapper and associated unit tests. So far tests are passed and thats sweet. Not let’s time to continue