Explore >> Select a destination
|
You are here 
|
snapdba.com | ||
| | | | |
parvu.org
|
|
| | | | | To identify unused PL/SQL code in an Oracle database, several methods are recommended. Strategies include auditing PL/SQL execution, using DBA_DEPENDENCIES views to track dependencies, and analyzing execution data through DBMS_PROFILER. A process for safely removing unused code should be established, including renaming suspected units and ensuring backups before deletion. | |
| | | | |
dbtimewizard.com.br
|
|
| | | | | Neste artigo mostramos um exemplo prático de como podemos utilizar o DBMS_TRACE para identificar num PL/SQL qual é a consulta que está com baixo desempenho. | |
| | | | |
dbamarco.wordpress.com
|
|
| | | | | I just had some fun with Oracle 12c PDBs and snapshot clones. In the alert.log I found some unexpected errors "ORA-01157: cannot identify/lock data file XX". The file was part of a PDB which I used for testing. So I investigated that and found the file which was pretty small. So my assumption was that... | |
| | | | |
lisaapaul.home.blog
|
|
| | | The full moon in December is called the Cold Moon. It was a lovely moon. | ||
