Axis RightFax 8.5 Guía de instalación descargar pdf (Pagina 89)

13-13

Parameters

These parameters should be passed to the procedure in the order listed below:

 Start Date – this is the starting date from which the records are to be purged. % can be used

to imply all dates. Default value is NULL. The format for the field is DD-MON-YYYY.

 End Date – this date is to date till which the records are to be purged. % can be used to imply

all dates. Default value is NULL. The format for the field is DD-MON-YYYY.

 Domain Name – Domain name for which the records and files are to be purged. % indicates all

domains. Default value is NULL

 GL User – GL User ID for which the records and files are to be purged. ‘%’ can be used to

indicate all users. Default value is NULL

 Report GID – the Report GID for which the records and files are to be purged. % indicates all

the Report GIDs. Default value is NULL

 Job Number – the Job Number for which the records and files are to be purged. % indicates all

the job numbers. Default value is NULL

 DB User Name – the database user name

 DB Password – the database password

 Connect string – the database SID or the connect string. Default value is the value of the

environment variable $ORACLE_SID.

Manually Purging Transmissions from the Database

Manually purging is an alternative to truncating the partitioned tables. Learn more about the

scheduled jobs that truncate partitioned tables later in the chapter. Truncating data is much faster

than purging, but purging allows you to more exactly specify what data to purge.

Transmission_purge deletes data associated with xml blobs used for integrating Oracle Transportation

Management with external systems. In general, the xml blobs are temporary, so there is no downside

the getting rid of them.

Your DBA or System Administrator should set up a nightly or weekly background job to run purges as

described below.

Manually Purge Transmissions

To purge the transmission tables:

1. Log into sql*plus as glogowner. (glogowner/{password}@{tnsname})

2. sql>exec domainman.transmission_purge(<age_in days>, <total_minutes>, <batch

size>);

Note: The old procedure transmission purge “domainman.transmission_purge(<age_in

days>, <where clause>,<totalminutes>,<keep status clob flag>, <batch size);”

is deprecated.

Tender collaboration records (TENDER_COLLABORATION), which have their own partition,

are not able to be purged or truncated with this procedure. They can be purged with

associated shipments if the parameter PURGE_TENDER_TRANSACTION=TRUE or manually

purged with sql command “exec domainman.orphan_tender_purge(

<total_minutes>,<batch size>);”

Transmissions with shipment events (IE_SHIPMENT_STATUS) are purged just like other

elements.

1 2 ... 84 85 86 87 88 89 90 91 92 93 94 ... 105 106

Comentarios a estos manuales

Sin comentarios

Axis RightFax 8.5 Guía de instalación Pagina 89

Comentarios a estos manuales

Relacionado con productos y manuales para Software Axis RightFax 8.5