Oracle doesn't keep explicit data about the usage of the tables.
If you need this you can create triggers to monitor DML (DELETE, INSERT, UPDATE)
activities, but there is no possibility to monitor SELECT access.

There is Fine Grained Audit fature:

9i FGA provides support for SELECT statements only.
10g FGA extends in the following ways:

--> Support for DML statements :
A. INSERT
B. UPDATE
C. DELETE
Auditing is turned off by default in Oracle, so unless you (or some DBA at your organization in the past) has turned on auditing, your audit_trail will be empty!

The audit records can either be written to an ASCII log file on the server, or they can be written to the database where they are visible in the view: DBA_AUDIT_TRAIL. This is controlled by the init parameter: "AUDIT_TRAIL" that can be set or changed in your init*.ora file or spfile.

When you say you "have to monitor the table access/usage by monitoring the columns..." do you mean you need to identify when data changes in each column of every table?

If so then you could turn on auditing or build your own triggers to gather the required information about which columns have changed. Turning on auditing will be an overhead to the running of your database and will potentially generate lots more data that will need to be managed.

Using triggers is less desirable as it can affect the actual transactions if you have errors. Use FGA feature, thats what is for. You don't even need the normal auditing configured, but you do need to set "audit_trail" to db_extended:

Featured Post

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Note: this article covers simple compression. Oracle introduced in version 11g release 2 a new feature called Advanced Compression which is not covered here.
General principle of Oracle compression
Oracle compression is a way of reducing the d…

Introduction
A previously published article on Experts Exchange ("Joins in Oracle", http://www.experts-exchange.com/Database/Oracle/A_8249-Joins-in-Oracle.html) makes a statement about "Oracle proprietary" joins and mixes the join syntax with gen…