# 22. Virtuoso Functions Guide - repl_purge

Chapter Contents | Prev | Next
Keyword Search:
www.openlinksw.com
docs.openlinksw.com
Book Home
Contents
Preface
Virtuoso Functions Guide
Administration
Aggregate Functions
Array Manipulation
BPEL APIs
Backup
Compression
Cursor
Date & Time Manipulation
Debug
Dictionary Manipulation
Encoding & Decoding
File Manipulation
Free Text
Hashing / Cryptographic
LDAP
Locale
Mail
Miscellaneous
Number
Remote SQL Data Source
Replication
repl_add_cr
repl_add_dav_cr
repl_add_snapshot_cr
repl_create_snapshot...
repl_create_snapshot...
repl_drop_snapshot_p...
repl_drop_snapshot_s...
repl_grant
repl_init_copy
repl_init_snapshot
repl_publish
repl_pub_add
repl_pub_init_image
repl_pub_remove
repl_revoke
repl_sched_init
repl_server
repl_server_name
repl_snp_server
repl_stat
repl_subscribe
repl_unpublish
repl_unsubscribe
repl_update_snapshot
repl_disconnect
repl_new_log
repl_purge
repl_server_rename
repl_status
repl_sync
repl_sync_all
repl_text
repl_this_server
sub_schedule
SOAP
SQL
String
Transaction
Type Mapping
UDDI
User Defined Types & The CLR
Virtuoso Java PL API
Virtuoso Server Extension Interface (VSEI)
Web Server & Internet
XML
XPATH & XQUERY
Functions Index

## repl_purge

purges transactional replication logs for specified account
repl_purge (in server varchar, in account varchar);
Description

This procedure purges transactional replication logs for specified account. Logs whose start replication level lags more than REPL_MAX_DELTA (1000000000) transactions behind current replication level of a specified account are removed. After repl_purge() is finished next repl_purge() run is scheduled using SYS_SCHEDULED_EVENT facility.

Account sync requests from subscribers are delayed while repl_purge() is running for this account.

Parameters
server – The server name of the publisher.
account – The name assigned to the publication.
Example
Purging transactional replication logs

The following shows purging transactional replication logs for pushback account for updateable subscription 'demopub' from 'demoserver':

    SQL> repl_purge ('demoserver', '!demopub');

See Also

repl_publish()

repl_subscribe()

repl_unpublish()

repl_unsubscribe()