When user A creates a procedure and grants execute permissions to user B, user B can execute the procedure (obviously), but he can also see the code (in ALL_SOURCE view).
When user A creates a procedure and grants execute permissions to user B, user B can execute the procedure (obviously), but he can also see the code (in ALL_SOURCE view).
If you are using Data Guard and standby databases, you probably need to do stuff based on the database role. For example, have some services start on the primary database,
Oracle database is a very complex software, and as we all know, has bugs. Oracle tries to address these bugs, and fixes a lot of them all the time. Except
Many of my clients use storage backup (snapshots, etc.) to backup their databases. The right and supported way to do that is like any hot backup: place the database in
As of Nov 2015, Oracle decided to change the naming method for PSU (Patch Set Update).
In Oracle 12c, when running DBMS_STATS to gather statistics on a partitioned table,we can (finally) gather statistics on all (or at least some) partitions at the same time.
I just found out an interesting information regarding Golden Gate license, it seems to include license to full use of Active Data Guard and XStream.
Over the years I ran into many Oracle bug related to the optimizer (the last one was yesterday with join push predicates). Many times this is related to Optimizer new
Database Identifiers are basically names of objects in the database, like tables, indexes, etc. There are restrictions about identifiers in Oracle, they can be up to 30 characters, must begin
Here is a new thing I found out about database processes. If you read my post about listener registration you know about the communication between the database and the listener