Menu
▾
▴
Re: [Virtuoso-users] Migrate database from Virtuoso v6 to v7
|
From: Hugh W. <hwi...@op...> - 2015-05-09 01:36:21
|
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 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 8 May 2015, at 19:26, Ken Weiss <ken...@uc...> 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...@uc... <mailto:ken...@uc...> > 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...@uc... <mailto:ken...@uc...>> > Date: Friday, May 8, 2015 11:19 AM > To: "vir...@li... <mailto:vir...@li...>" <vir...@li... <mailto:vir...@li...>> > 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...@uc... <mailto:ken...@uc...> > 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_______________________________________________ > Virtuoso-users mailing list > Vir...@li... > https://lists.sourceforge.net/lists/listinfo/virtuoso-users |
