Database Reference
In-Depth Information
5.
To set up a logging and diagnostics directory where logs are written, recon-
nect to the database as SYSDBA again, specify the directory location, and
grant read/write permission to the [PREFIX]_SOAINFRA user. You can also
optionally execute the script to turn debugging on by executing the de-
bug_on.sql script from the common directory. <DIAG_LOCATION> should
be replaced with a directory of your choice:
SQL> CREATE OR REPLACE DIRECTORY SOA_PURGE_DIR AS '<DIAG_LOCATION>/purge_logs' ;
SQL> GRANT READ, WRITE ON DIRECTORY SOA_PURGE_DIR TO [PREFIX]_SOAINFRA;
SQL>@common/debug_on.sql;
6.
By default, the command line does not read what a query program has writ-
ten with dbms_output . You have to enable the serveroutput by setting
it to on , to change the default behavior. Additionally, if the output needs to
be captured, a spool file needs to be configured in the logging directory:
SQL> SET SERVEROUTPUT ON;
SQL> SPOOL '<DIAG_LOCATION>/purge_logs/spool.log'
7.
After the scripts are run, you can choose to set it to off , when no longer
needed:
SQL> SPOOL OFF
Selective purging from Enterprise Manager
If there are only a few composites deployed to the service infrastructure that
in turn have only a limited number of instances being processed, the database
footprint is not expected to grow by much. In these cases you can rely on the
use of available out-of-the-box purging scripts and run either the multithreaded
looped or single-threaded looped purge procedure to take care of database
space management. Alternatively, Oracle Fusion Middleware Enterprise Man-
ager Control can also be used for selective or bulk deletion of instances. For
Search WWH ::




Custom Search