# 22. Virtuoso Functions Guide - REPL_INIT_COPY

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_INIT_COPY

create initial subscription state
REPL_INIT_COPY (in server_name varchar, in publication varchar);
Description

This function is called on the subscriber to copy the current state of the elements of the publication from the publishing server. Copied data can include DAV collections, tables, procedures etc. Syncing the subscription using repl_sync will synchronize the subscription once it has been initialized with this function. The state copied corresponds to the state of the published data as of the last checkpoint completed on the publisher.

Parameters
server_name – target publisher server name.
account – publication account name.
Example
Loading of the initial data on subscriber

This shows setting on-line of the initial state of the subscription to 'demo_publication' from server 'demo-srv'. The data for items will be transferred thru the VDB connection. Note that on large publications this can take a lot of time.

    SQL> DB.DBA.REPL_INIT_COPY ('demo-srv', 'demo_publication');

See Also

sub_schedule()

repl_disconnect()

repl_grant()

repl_new_log()

repl_pub_add()

repl_pub_init_image()

repl_pub_remove()

repl_publish()

repl_revoke()

repl_sched_init()

repl_server()

repl_server_rename()

repl_stat()

repl_status()

repl_subscribe()

repl_sync()

repl_sync_all()

repl_text()

repl_this_server()

repl_unpublish()

repl_unsubscribe()