Oracle Database Discussions

There would be no logs for normal transactions. All other transactions like adding tablespace/dropping tablespaces will be recored in alert_SID.log and it would be in DIAGNOSTIC_DEST directory.

regards

Pravin

2841596 wrote:

I'm learning about oracle database and I created a user and started creating tables, doing queries on Oracle Database 12c. I would like to know where can I see the transaction log, so I can see what's happening, the access and stuff. I can't find the log file anywhere. Where is it located?

does  not exist.

why do you think it should exist?

maybe it's a question of terminology: Oracle has redo log files with information on data changes und undo tablespaces containing undo records to undo changes that were made to the database by the uncommitted transaction. Some other databases (for example MS SQL Server) use a transaction log file to store these information.

To actually read through a redo log you'll need to use DBMS_LOGMNR.  Read here:

https://dfitzjarrell.wordpress.com/2008/10/31/workin-in-the-mines/

David Fitzjarrell

As said earlier about the actual block level changes  are recorded into redo logs and undo data go to undo tablespace.

You can monitor live queries under v$transaction, and what you see there is sql queries submitted by the users.

sol.beach wrote:


2841596 wrote:

I'm learning about oracle database and I created a user and started creating tables, doing queries on Oracle Database 12c. I would like to know where can I see the transaction log, so I can see what's happening, the access and stuff. I can't find the log file anywhere. Where is it located?

does  not exist.

why do you think it should exist?

I remember looking for this too when I first came to Oracle. It really should exist even if only as an optional opt-in parameter.

Fastfwd75 wrote:



I remember looking for this too when I first came to Oracle. It really should exist even if only as an optional opt-in parameter.

Have YOU submitted Enhancement Request for this?

How is this different from enabling SQL_TRACE?

sol.beach wrote:


Fastfwd75 wrote:



I remember looking for this too when I first came to Oracle. It really should exist even if only as an optional opt-in parameter.




Have YOU submitted Enhancement Request for this?
How is this different from enabling SQL_TRACE?

Be Zen sol.beach; this is not an attack on Oracle or on you

This is different from SQL_TRACE because simply logging the SQL statements has much less overhead. I have not submitted it an an enhancement request but it's really not a novel idea. Must be a reason why Oracle does not do it but I don't know what it is.

Look up MySQL general query log to see what I mean.