Hi all,
I am new to database world and would like to know how following thing
can be achieved. I have oracle database and oc4j setup. I have one
closed source oc4j application which i run from browser which read and
writes to database. I would like to know what actually happens at back
end when i perform some operation in that application. What tables/
views/indexes are updated ? And what change happens to them ?

1: Is it possible to to track such information ?

2: Google search gave me some tool name but they were most likely :
start tracking, run your sql script , stop tracking. Here application
is run from browser and i do not have access to scripts it run.

-Rohit

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

On 08.12.2008 21:42, Rohit wrote:
First of all, it's called "tracing". Then, you can trace an Oracle
session even without access to the source code of the application.
Assuming you have a recent release of Oracle you can enable session
trace via Grid Control / Enterprise Manager or an PL/SQL package. You
could also write a login trigger which switches tracing on.

Note though, that you still should make yourself familiar with Oracle
first. Note also, that you should make yourself familiar with the
licensing terms of the application that you are trying to dissect - you
might face legal issues when trying to reverse engineer it.

Cheers

robert

Hey thanks for information. I agree that i need to get familiar with
Oracle but will you let me know if with this tracing option turned
on , can i get info about the actual tables touched , what update (if
possible actual row/column level change) happened to it. While i study
these things , just let me know if at all its possible to reverse
engineer whole schema that application is using.

-Rohit

Hey thanks for information. I agree that i need to get familiar with
Oracle but will you let me know if with this tracing option turned
on , can i get info about the actual tables touched , what update (if
possible actual row/column level change) happened to it. While i study
these things , just let me know if at all its possible to reverse
engineer whole schema that application is using.

-Rohit