Database Reference
In-Depth Information
however it gives a benchmark of how much a database may grow so that you
can provision a database suiting the need of business processes running on the
infrastructure. Depending upon the size and nature of your database you may
be required to schedule more frequent maintenance. In any case, you can fol-
low the recommendations given that cover three different kinds of database foot-
prints that you may have and ways to maintain them.
Purging prerequisites
Running the following maintenance scripts on the database requires certain priv-
ileges to be granted as it involves scheduling, creating jobs, deletion, and par-
titioning. An out-of-the-box purge package is already available with your Oracle
SOA Suite
11g
installation. Before you choose to purge component tables, it is
essential to specify a directory to log the output of the executed maintenance
scripts to assist in troubleshooting, should a problem arise. The following steps
set up all the necessary prerequisites to effectively begin purging your Dehydra-
tion Store:
1.
Connect to the database as SYSDBA to grant privileges to the SOAINFRA
schema user to execute the purging scripts:
SQL> GRANT EXECUTE ON DBMS_LOCK TO
[PREFIX]
_SOAINFRA;
SQL> GRANT CREATE ANY JOB TO
[PREFIX]
_SOAINFRA;
2.
On the command prompt, create an environment variable named
SQLPATH
and point it to the directory containing the scripts used to create the purge
packages:
export SQLPATH=
"$MW_HOME
/Oracle_SOA1/rcu/integration/soainfra/sql/soa_purge"
3.
Reconnect to the database but this time as the SOAINFRA user.
4.
Verify that the relevant SOA purge packages are available for the user.
Otherwise
manually
create
them
by
executing
the
soa_purge_scripts.sql
script:
SQL>@soa_purge_scripts.sql
