Re: [Virtuoso-users] Migrate database from Virtuoso v6 to v7

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi Ken

To be getting the messages:

> 15:20:08 PL LOG: This database may contain RDF data that could cause indexing problems on previous versions of the server.
> 15:20:08 PL LOG: The content of the DB.DBA.RDF_QUAD table will be checked and an update may automatically be performed if
> 15:20:08 PL LOG: such data is found.
> 15:20:08 PL LOG: This check will take some time but is made only once.
> 15:20:08 PL LOG: No need to update DB.DBA.RDF_QUAD.

in the log you must have had a pre 6.1.4 database in which case you need to perform the operations detailed in the following link to check and repair the possible index problem indicated:

 	http://virtuoso.openlinksw.com/dataspace/doc/dav/wiki/Main/UpgradingToVOS610#Upgrading%20from%20Release%206.1.3%20or%20earlier,%20to%20Release%206.1.4%20or%20later

The “No Column N.RES_SIZE” messages as you found can be resolved as you found by altering the table:

	alter table WS.WS.SYS_DAV_RES add RES_SIZE integer

The other messages can be ignored …

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 23:29, Ken Weiss <ken...@uc...> wrote:
> 
> Hugh,
> 
> OK, that got me a zero-byte .trx file. And I was able to start the Virtuoso server, and it does appear that my database is intact and accessible. So that's all good.
> 
> However...
> 
> I'm seeing a lot of errors in the log when the server starts up:
> 
> 15:20:07 built-in procedure "repl_undot_name" overruled by the RDBMS
> 15:20:08 Error compiling stored procedure: 42S22: SQ062: No column N.RES_SIZE. -- #line 4636 "[executable]/dav.sql"
> create trigger SYS_DAV_RE
> 15:20:08 Error compiling stored procedure: 42S22: SQ062: No column O.RES_SIZE. -- #line 4728 "[executable]/dav.sql"
> create trigger SYS_DAV_RE
> 15:20:08 Error compiling stored procedure: 42S22: SQ063: No column RES_SIZE. -- #line 5185 "[executable]/dav.sql"
> create trigger SYS_DAV_RE
> 15:20:08 built-in procedure "adm_lt_make_dsn_part" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_next_checkbox" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_lt_dsn_options" overruled by the RDBMS
> 15:20:08 built-in procedure "vector_print" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_get_file_dsn" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_get_init_name" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_make_option_list" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_is_hosted" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_get_uid" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_user_can_read_col_p" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_user_can_read_res_p" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_uid_to_user" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_uid_to_group" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_fmt_perm" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_list_error" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_map_icon" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_fmt_col" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_fmt_res" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_path_normalize" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_file_like" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_os_br_gen_col_c_listing" overruled by the RDBMS
> 15:20:08 built-in procedure "adm_dav_br_gen_col_c_listing" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.__GET_KEYWORD" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.URLIFY_STRING" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.__GET_TEMPORARY" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.DBPUMP_START_COMPONENT" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.DBPUMP_RUN_COMPONENT" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.HTML_RETRIEVE_TABLES" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.HTML_RETRIEVE_QUALIFIERS_VIA_PLSQL" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.DUMP_TABLES_AND_PARS_RETRIEVE" overruled by the RDBMS
> 15:20:08 built-in procedure "PUMP.DBA.RESTORE_TABLES_AND_PARS_RETRIEVE" overruled by the RDBMS
> 15:20:08 built-in procedure "DB.DBA.RESTORE_DBPUMP'S_FOLDER" overruled by the RDBMS
> 15:20:08 Roll forward started
> 15:20:08 Roll forward complete
> 15:20:08 PL LOG: This database may contain RDF data that could cause indexing problems on previous versions of the server.
> 15:20:08 PL LOG: The content of the DB.DBA.RDF_QUAD table will be checked and an update may automatically be performed if
> 15:20:08 PL LOG: such data is found.
> 15:20:08 PL LOG: This check will take some time but is made only once.
> 15:20:08 PL LOG: No need to update DB.DBA.RDF_QUAD.
> 15:20:08 Checkpoint started
> 15:20:08 Checkpoint finished, log reused
> 15:20:08 Checkpoint started
> 15:20:08 Checkpoint finished, log reused
> 15:20:08 Checkpoint started
> 15:20:08 Checkpoint finished, log reused
> 15:20:08 HTTP/WebDAV server online at 8890
> 15:20:08 Server online at 1111 (pid 3377)
> 
> I searched for related issues, and the only things I found referred to seeing similar errors when running older versions of Virtuoso. The recommended fix was to update to version 7. So that's not very helpful.
> 
> https://www.mail-archive.com/vir...@li.../msg06289.html <https://www.mail-archive.com/vir...@li.../msg06289.html>
> 
> Any thoughts? Or is this just something you see with a database that was upgraded 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: Hugh Williams <hwi...@op... <mailto:hwi...@op...>>
> Date: Wednesday, May 13, 2015 5:49 PM
> To: Ken Weiss <ken...@uc... <mailto:ken...@uc...>>
> Cc: "vir...@li... <mailto:vir...@li...>" <vir...@li... <mailto:vir...@li...>>
> Subject: Re: [Virtuoso-users] Migrate database from Virtuoso v6 to v7
> 
> 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:
> 
> 
> ------------------------------------------------------------------------------
> 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