
| | | |
| Applies To | | |
| | | |
| Product(s): | Exor TMA API and Web Service | |
| Version(s): | 04.05.00.01 | |
| Environment: | N\A | |
| Area: | Other | |
| Subarea: | N\A | |
| Original Author: | Lee Jackson, Bentley Technical Support Group | |
| | | |
How to purge web service instance data from the SOA repository database
Background
When sending and receiving TMA transactions the web server records instance data of the transmission in the SOA repository database, also known as the dehydration store. This data is useful when debugging problems, but isn’t required by the TMA Manager product and can be purged/deleted from time to time if required.
Steps to Accomplish
There are 2 ways to delete the instance data:
The above instructions were taken from the following Oracle Administrators Guide, which gives detailed notes on each of the purge script parameters, as well as provide instructions on how to configure the purge script to be automatically run by a DBMS job:
http://docs.oracle.com/cd/E25054_01/admin.1111/e10226/soaadmin_partition.htm#CJHCBHEJ
See Also
How to Limit Log File Numbers and Sizes:
http://communities.bentley.com/products/assetwise/exor/w/wiki/11307.how-to-limit-log-file-numbers-and-sizes.aspx