This HTML5 document contains 31 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n18:this

foaf:made

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

Subject Item

n9:this

sioc:creator_of

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

Subject Item

n16:item

n17:services_of

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

Subject Item

n15:this

sioc:creator_of

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

Subject Item

n14:VOS

sioc:container_of

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

atom:entry

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

atom:contains

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

Subject Item

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

rdf:type

sioct:Comment atom:Entry

dcterms:created

2017-06-13T05:36:10.117586

dcterms:modified

2017-06-13T05:36:10.117586

rdfs:label

VirtTipsAndTricksGuideTablesAndIndexesRecover

foaf:maker

n11:this n18:this

dc:title

VirtTipsAndTricksGuideTablesAndIndexesRecover

opl:isDescribedUsing

n4:rdf

sioc:has_creator

n9:this n15:this

sioc:content

%META:TOPICPARENT{name="VirtTipsAndTricksGuide"}% ---+ Backing Up Individual Table(s) or Index(es) and Restoring Them to a Fresh DB ---++ What? Selectively dumping a database table or its schema, for reload into a separate instance, or for recovery in the original instance. <i><b>Note</b>: This is only possible with Virtuoso 6.0 and later.</i> ---++ Why? There are many reasons, ranging from system corruption to migration, why you might want to reconstitute data across database management system instances. ---++ How to Dump and Recover one or more SQL Table(s) 1 Create a function for dumping the key: <verbatim> SQL> CREATE PROCEDURE bkp_key ( IN f ANY , IN tb_name VARCHAR , IN key_name VARCHAR ) { backup_prepare ( f ) ; backup_index ( tb_name , key_name ); backup_flush (); backup_close (); }; </verbatim> <i><b>Note:</b> You can dump multiple tables by adding more calls to the <code>backup_index</code> function. 1 On the source DB, dump the <code>T1</code> table's primary key to a file named "<code>mylog.txn</code>", by executing: <verbatim> SQL> bkp_key ( 'mylog.txn' , 'DB.DBA.T1' , 'T1' ); </verbatim> 1 On the source DB host, stop the Virtuoso server, and dump only the schema tables (no data) into the <code>trx</code> file, by executing: <verbatim> % virtuoso +crash-dump +foreground +mode l ## ( lower case L ) </verbatim> 1 On the target DB host, make sure there is no existing <code>.db</code> file, and place the <code>.trx</code> file produced by previous step. Create a new DB with the schema from the source DB, by executing: <verbatim> % virtuoso +restore-crash-dump +foreground ; </verbatim> 1 Insert the PK data from the source DB dump into the new table in the new DB, by starting the new DB as normal, and executing: <verbatim> SQL> replay ('mylog.txn') ; </verbatim> <i><b>Note:</b> that this has only restored the Primary Key index. If there are multiple indexes on the table(s), the other indexes must be dropped and re-created, as they will be empty at this point.</i> ---++Related * [[VirtTipsAndTricksGuide][Virtuoso Tips and Tricks Collection]] * [[http://docs.openlinksw.com/virtuoso/databaseadmsrv.html#backup][Virtuoso Data Backup & Recovery]]

sioc:id

8289adfcfb9eb215db2e2b1935cde0e8

sioc:link

n2:VirtTipsAndTricksGuideTablesAndIndexesRecover

sioc:has_container

n14:VOS

n17:has_services

n16:item

atom:title

VirtTipsAndTricksGuideTablesAndIndexesRecover

sioc:links_to

n6:VirtTipsAndTricksGuide n20:backup

atom:source

n14:VOS

atom:author

n18:this

atom:published

2017-06-13T05:36:10Z

atom:updated

2017-06-13T05:36:10Z

sioc:topic

n14:VOS