Hi Ken,

Try connecting to a running instance of the v6 with the “isql” command line 
tool and run a “checkpoint;” followed immediately by “shutdown” and the trx 
file should then be  0 bytes:

Hughs-MBP:database hwilliams$ ../bin/isql 1111
Connected to OpenLink Virtuoso
Driver: 06.01.3127 OpenLink Virtuoso ODBC Driver
OpenLink Interactive SQL (Virtuoso), version 0.9849b.
Type HELP; for help and EXIT; to exit.
SQL> checkpoint;

Done. -- 64 msec.
SQL> shutdown;
Hughs-MBP:database hwilliams$ ls -ltr virtuoso.trx
-rw-r--r--@ 1 root  wheel  0 14 May 01:34 virtuoso.trx
Hughs-MBP:database hwilliams$ 

It seems the +checkpoint-only server option does not truncate the log to 0 
bytes:

Hughs-MBP:database hwilliams$ sudo ../bin/virtuoso-t +checkpoint-only
Hughs-MBP:database hwilliams$ ls -ltr virtuoso.trx
-rw-r--r--@ 1 root  wheel        155 14 May 01:33 virtuoso.trx
Hughs-MBP:database hwilliams$

Will have to get the option checked …

Best Regards
Hugh Williams
Professional Services
OpenLink Software, Inc.      //              http://www.openlinksw.com/
Weblog   -- http://www.openlinksw.com/blogs/
LinkedIn -- http://www.linkedin.com/company/openlink-software/
Twitter  -- http://twitter.com/OpenLink
Google+  -- http://plus.google.com/100570109519069333827/
Facebook -- http://www.facebook.com/OpenLinkSoftware
Universal Data Access, Integration, and Management Technology Providers

> On 14 May 2015, at 00:04, Ken Weiss <ken.we...@ucop.edu> wrote:
> 
> Hugh,
> 
> Thanks for the suggestion, and for the link to the documentation. I tried 
> following that procedure, but I end up with a .trx file of 87 bytes, not zero.
> 
> First I made sure virtuoso was not running:
> udfr@uc3-udfr-prd:~/apps/virtuoso-opensource-version$ ps -ef | grep virtuoso
> udfr     25078 24905  0 15:55 pts/0    00:00:00 grep virtuoso
> 
> Then I started the server with the +checkpoint-only flag set. I also ran it 
> in foreground so I could see the log, but got the exact same result when I 
> tried running in background.
> 
> udfr@uc3-udfr-prd:~/apps/virtuoso-opensource-version$ ./bin/virtuoso-iodbc-t 
> -c ./var/lib/virtuoso/ontowiki/virtuoso.ini +checkpoint-only -f
> 
> Wed May 13 2015
> 15:56:12 { Loading plugin 1: Type `plain', file `wikiv' in 
> `/apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting'
> 15:56:12   WikiV version 0.6 from OpenLink Software
> 15:56:12   Support functions for WikiV collaboration tool
> 15:56:12   SUCCESS plugin 1: loaded from 
> /apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting/wikiv.so }
> 15:56:12 { Loading plugin 2: Type `plain', file `mediawiki' in 
> `/apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting'
> 15:56:12   MediaWiki version 0.1 from OpenLink Software
> 15:56:12   Support functions for MediaWiki collaboration tool
> 15:56:12   SUCCESS plugin 2: loaded from 
> /apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting/mediawiki.so 
> }
> 15:56:12 { Loading plugin 3: Type `plain', file `creolewiki' in 
> `/apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting'
> 15:56:12   CreoleWiki version 0.1 from OpenLink Software
> 15:56:12   Support functions for CreoleWiki collaboration tool
> 15:56:12   SUCCESS plugin 3: loaded from 
> /apps/udfr/apps/virtuoso-opensource-version/lib/virtuoso/hosting/creolewiki.so
>  }
> 15:56:12 OpenLink Virtuoso Universal Server
> 15:56:12 Version 06.01.3127-pthreads for Linux as of Jan 24 2012
> 15:56:12 uses parts of OpenSSL, PCRE, Html Tidy
> 15:56:12 Database version 3126
> 15:56:12 SQL Optimizer enabled (max 1000 layouts)
> 15:56:13 Compiler unit is timed at 0.000443 msec
> 15:56:13 Roll forward started
> 15:56:13     2 transactions, 87 bytes replayed (100 %)
> 15:56:13 Roll forward complete
> 15:56:14 Checkpoint started
> 15:56:14 Checkpoint finished, new log is 
> /apps/udfr/apps/virtuoso-opensource-version/var/lib/virtuoso/db/virtuoso20150513155614.trx
> 15:56:14 Server exiting
> 
> So far, so good. But when I look at that new log file 
> (virtuoso20150513155614.trx), it's 87 bytes, not zero:
> 
> udfr@uc3-udfr-prd:~/apps/virtuoso-opensource-version$ ls -l 
> var/lib/virtuoso/db/virtuoso20150513155614.trx
> -rw-r--r-- 1 udfr udfr 87 May 13 15:56 
> var/lib/virtuoso/db/virtuoso20150513155614.trx
> 
> The guide you pointed me to said, "If larger .trx files persist, contact 
> Technical Support 
> <http://support.openlinksw.com/support/online-support.vsp>.", so I guess 
> that's what I'll do.
> 
> --Ken
> 
> ------------------------------------------------------------
> Ken Weiss                                 ken.we...@ucop.edu 
> <mailto:ken.we...@ucop.edu>
> UC Office of the President              510-587-6311 (office)
> California Digital Library              916-905-6933 (mobile)
> UC Curation Center
> 415 20th Street, 4th Floor
> Oakland, CA 94612
> 
> 
> From: Hugh Williams <hwilli...@openlinksw.com 
> <mailto:hwilli...@openlinksw.com>>
> Date: Friday, May 8, 2015 6:36 PM
> To: Ken Weiss <ken.we...@ucop.edu <mailto:ken.we...@ucop.edu>>
> Cc: "virtuoso-users@lists.sourceforge.net 
> <mailto:virtuoso-users@lists.sourceforge.net>" 
> <virtuoso-users@lists.sourceforge.net 
> <mailto:virtuoso-users@lists.sourceforge.net>>
> Subject: Re: [Virtuoso-users] Migrate database from Virtuoso v6 to v7
> 
> Hi Ken,
> 
> You need to run the “checkpoint;” command from isql to commit all pending 
> transactions in the “virtuoso.trx” to the database file “virtuoos.db” , so 
> the trx file is 0 bytes, otherwise you get that transaction log version 
> mismatch error, see:
> 
> http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/UpgradingToVOS610#Upgrading%20from%20Release%206.x%20to%20Release%207.x
>  
> <http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/UpgradingToVOS610#Upgrading%20from%20Release%206.x%20to%20Release%207.x>
> 
> Best Regards
> Hugh Williams
> Professional Services
> OpenLink Software, Inc.      //              http://www.openlinksw.com/ 
> <http://www.openlinksw.com/>
> Weblog   -- http://www.openlinksw.com/blogs/ 
> <http://www.openlinksw.com/blogs/>
> LinkedIn -- http://www.linkedin.com/company/openlink-software/ 
> <http://www.linkedin.com/company/openlink-software/>
> Twitter  -- http://twitter.com/OpenLink <http://twitter.com/OpenLink>
> Google+  -- http://plus.google.com/100570109519069333827/ 
> <http://plus.google.com/100570109519069333827/>
> Facebook -- http://www.facebook.com/OpenLinkSoftware 
> <http://www.facebook.com/OpenLinkSoftware>
> Universal Data Access, Integration, and Management Technology Providers
> 
>> On 8 May 2015, at 19:26, Ken Weiss <ken.we...@ucop.edu 
>> <mailto:ken.we...@ucop.edu>> wrote:
>> 
>> I should have added that the 4-step process I described using +backup-dump 
>> and +restore-crash-dump works perfectly to move the database from one 
>> version 6 instance to another. It only fails when I try to move from version 
>> 6 to version 7.
>> 
>> --Ken
>> ------------------------------------------------------------
>> Ken Weiss                                 ken.we...@ucop.edu 
>> <mailto:ken.we...@ucop.edu>
>> UC Office of the President              510-587-6311 (office)
>> California Digital Library              916-905-6933 (mobile)
>> UC Curation Center
>> 415 20th Street, 4th Floor
>> Oakland, CA 94612
>> 
>> 
>> From: Ken Weiss <ken.we...@ucop.edu <mailto:ken.we...@ucop.edu>>
>> Date: Friday, May 8, 2015 11:19 AM
>> To: "virtuoso-users@lists.sourceforge.net 
>> <mailto:virtuoso-users@lists.sourceforge.net>" 
>> <virtuoso-users@lists.sourceforge.net 
>> <mailto:virtuoso-users@lists.sourceforge.net>>
>> Subject: Migrate database from Virtuoso v6 to v7
>> 
>> I am trying to migrate a database from Virtuoso version 6 to version 7, 
>> without success. Here is the procedure I tried:
>> 
>> 1) Shut down the version 6 database
>> 
>> 2) Make an offline dump of the version 6 database as follows:
>> ./virtuoso-iodbc-t -c ../var/lib/virtuoso/ontowiki/virtuoso.ini +backup-dump 
>> -f
>> 
>> 3) Copy the .trx files from the db directory for version 6 to the db 
>> directory for version 7
>> 
>> 4) Attempt to restore the offline dump as follows:
>> ./virtuoso-iodbc-t -c ../var/lib/virtuoso/ontowiki/virtuoso.ini 
>> +restore-crash-dump -f
>> 
>> I get the following error:
>> 
>> 11:03:05 OpenLink Virtuoso Universal Server
>> 11:03:05 Version 07.20.3212-pthreads for Linux as of May  8 2015
>> 11:03:05 uses parts of OpenSSL, PCRE, Html Tidy
>> 11:03:05 Database version 3126
>> 11:03:05 SQL Optimizer enabled (max 1000 layouts)
>> 11:03:05 Roll forward started
>> 11:03:05 The transaction log file has been produced by server version 
>> '06.01.3127'. The version of this server is '07.20.3212'. If the transaction 
>> log is empty or you do not want to replay it then delete it and start the 
>> server again. Otherwise replay the log using the server of version 
>> '06.01.3127' and make checkpoint and shutdown to ensure that the log is 
>> empty, then delete it and start using new version.
>> 
>> I also tried simply copying the virtuoso.db file from the version 6 
>> installation to a freshly built version 7, and got the exact same error when 
>> I start the version 7 instance, plus a bunch of errors that I assume are due 
>> to missing tables and schema elements:
>> 
>> 11:07:19 OpenLink Virtuoso Universal Server
>> 11:07:19 Version 07.20.3212-pthreads for Linux as of May  8 2015
>> 11:07:19 uses parts of OpenSSL, PCRE, Html Tidy
>> 11:07:19 Database version 3126
>> 11:07:19 SQL Optimizer enabled (max 1000 layouts)
>> 11:07:20 Compiler unit is timed at 0.000202 msec
>> 11:07:21 built-in procedure "repl_undot_name" overruled by the RDBMS
>> 11:07:21 Error compiling stored procedure: 42S22: SQ062: No column 
>> N.RES_SIZE. -- #line 4636 "[executable]/dav.sql"
>> create trigger SYS_DAV_RE
>> 11:07:21 Error compiling stored procedure: 42S22: SQ062: No column 
>> O.RES_SIZE. -- #line 4728 "[executable]/dav.sql"
>> create trigger SYS_DAV_RE
>> 11:07:21 Error compiling stored procedure: 42S22: SQ063: No column RES_SIZE. 
>> -- #line 5185 "[executable]/dav.sql"
>> create trigger SYS_DAV_RE
>> 11:07:21 built-in procedure "adm_lt_make_dsn_part" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_next_checkbox" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_lt_dsn_options" overruled by the RDBMS
>> 11:07:21 built-in procedure "vector_print" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_get_file_dsn" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_get_init_name" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_make_option_list" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_is_hosted" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_get_uid" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_user_can_read_col_p" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "adm_dav_user_can_read_res_p" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_uid_to_user" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_uid_to_group" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_fmt_perm" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_list_error" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_map_icon" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_fmt_col" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_fmt_res" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_path_normalize" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_file_like" overruled by the RDBMS
>> 11:07:21 built-in procedure "adm_os_br_gen_col_c_listing" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "adm_dav_br_gen_col_c_listing" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.__GET_KEYWORD" overruled by the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.URLIFY_STRING" overruled by the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.__GET_TEMPORARY" overruled by the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.DBPUMP_START_COMPONENT" overruled by 
>> the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.DBPUMP_RUN_COMPONENT" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.HTML_RETRIEVE_TABLES" overruled by the 
>> RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.HTML_RETRIEVE_QUALIFIERS_VIA_PLSQL" 
>> overruled by the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.DUMP_TABLES_AND_PARS_RETRIEVE" 
>> overruled by the RDBMS
>> 11:07:21 built-in procedure "PUMP.DBA.RESTORE_TABLES_AND_PARS_RETRIEVE" 
>> overruled by the RDBMS
>> 11:07:21 built-in procedure "DB.DBA.RESTORE_DBPUMP'S_FOLDER" overruled by 
>> the RDBMS
>> 11:07:21 Roll forward started
>> 11:07:21 The transaction log file has been produced by server version 
>> '06.01.3127'. The version of this server is '07.20.3212'. If the transaction 
>> log is empty or you do not want to replay it then delete it and start the 
>> server again. Otherwise replay the log using the server of version 
>> '06.01.3127' and make checkpoint and shutdown to ensure that the log is 
>> empty, then delete it and start using new version.
>> 11:07:21 Server exiting
>> 
>> Can anyone give me a procedure to migrate a version 6 database to version 7?
>> 
>> --Ken
>> 
>> ------------------------------------------------------------
>> Ken Weiss                                 ken.we...@ucop.edu 
>> <mailto:ken.we...@ucop.edu>
>> UC Office of the President              510-587-6311 (office)
>> California Digital Library              916-905-6933 (mobile)
>> UC Curation Center
>> 415 20th Street, 4th Floor
>> Oakland, CA 94612
>> 
>> ------------------------------------------------------------------------------
>> One dashboard for servers and applications across Physical-Virtual-Cloud 
>> Widest out-of-the-box monitoring support with 50+ applications
>> Performance metrics, stats and reports that give you Actionable Insights
>> Deep dive visibility with transaction tracing using APM Insight.
>> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
>>  
>> <http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________>
>> Virtuoso-users mailing list
>> Virtuoso-users@lists.sourceforge.net 
>> <mailto:Virtuoso-users@lists.sourceforge.net>
>> https://lists.sourceforge.net/lists/listinfo/virtuoso-users 
>> <https://lists.sourceforge.net/lists/listinfo/virtuoso-users>
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to