Our tape archive is run by ontape -c but last night the logs kept filling up and saying a new archive tape needed to be started. I need to know if there is a way to go back 24 hours and find out who or what was making the inquiries and what tables were being access to create havoc on my system
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Do you know how to get history on tables accessed?
- Thread starter womp
- Start date
The Monitor database is designed to hold historical data on the state of all
tables in every Informix database found in a particular RDBMS configuration.
The design has been enhanced to include performance statistics.
Data is collected using shell scripts run at predetermined intervals to extract
the necessary statistical information from the database catalog tables for
storing within the monitor database. An 'UPDATE STATISTICS' must have been run
before running the monitor script to ensure the latest information is available
in the database catalog tables.
The collected data will provide an historical representation of table and
dbspace utilisation. The performance statistics will give an indication of how
each table is being accessed. The accumulated data can be used to provide
supporting evidence for any proposed application or database change.
Monitor Database
The database consists of 5 main tables:
1. Tabhist - History of table data
2. Dbshist - History of dbspace information
3. Svrhist - History of Informix server data
4. Syshist - History of Unix system data
5. Profhist - History of individual table access profiles
A 6th table called tabsumm is a monthly summary of tabhist data to avoid
excessive amounts of table history data. This table is not critical to the
operation of Monitor and can be ignored (the script mon_summ.ksh should not
be run).
Dodge20
tables in every Informix database found in a particular RDBMS configuration.
The design has been enhanced to include performance statistics.
Data is collected using shell scripts run at predetermined intervals to extract
the necessary statistical information from the database catalog tables for
storing within the monitor database. An 'UPDATE STATISTICS' must have been run
before running the monitor script to ensure the latest information is available
in the database catalog tables.
The collected data will provide an historical representation of table and
dbspace utilisation. The performance statistics will give an indication of how
each table is being accessed. The accumulated data can be used to provide
supporting evidence for any proposed application or database change.
Monitor Database
The database consists of 5 main tables:
1. Tabhist - History of table data
2. Dbshist - History of dbspace information
3. Svrhist - History of Informix server data
4. Syshist - History of Unix system data
5. Profhist - History of individual table access profiles
A 6th table called tabsumm is a monthly summary of tabhist data to avoid
excessive amounts of table history data. This table is not critical to the
operation of Monitor and can be ignored (the script mon_summ.ksh should not
be run).
Dodge20
- Status
Similar threads
- Locked
- Question