Chapter聽6.聽Administration

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"> <html lang="en" itemscope="itemscope" itemtype="http://schema.org/WebPage" itemid="http://docs.openlinksw.com/virtuoso/ch-server/" xmlns:n0="http://www.w3.org/2000/xmlns/" n0:og="http://ogp.me/ns#" n0:fb="http://ogp.me/ns/fb#" n0:xhv="http://www.w3.org/1999/xhtml/vocab#" xmlns:xh="http://www.w3.org/1999/xhtml" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:d="http://docbook.org/ns/docbook" xmlns:addthis="http://www.addthis.com/help/api-spec"> <head> <meta charset="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <title itemprop="name">Chapter聽6.聽Administration</title> <link rel="STYLESHEET" href="/skin/docs-v3/css/opl-style.css" /> <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png" /> <link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32" /> <link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16" /> <link rel="manifest" href="/manifest.json" /> <link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5" /> <meta name="theme-color" content="#ffffff" /> <title>Chapter聽6.聽Administration</title> <meta name="keywords" content="documentation , docs , openlink , openlink software , virtuoso , database , SQL , PL , RDBMS " /> <link rel="chapter" href="/virtuoso/ch-overview/" oldhref="ch-overview.html" title="Chapter聽1.聽Overview" /> <link rel="chapter" href="/virtuoso/ch-installation/" oldhref="ch-installation.html" title="Chapter聽2.聽Installation Guide" /> <link rel="chapter" href="/virtuoso/ch-quicktours/" oldhref="ch-quicktours.html" title="Chapter聽3.聽Quick Start & Tours" /> <link rel="chapter" href="/virtuoso/ch-sampleapps/" oldhref="ch-sampleapps.html" title="Chapter聽4.聽Sample ODBC & JDBC Applications" /> <link rel="chapter" href="/virtuoso/ch-concepts/" oldhref="ch-concepts.html" title="Chapter聽5.聽Conceptual Overview" /> <link rel="chapter" href="/virtuoso/ch-server/" oldhref="ch-server.html" title="Chapter聽6.聽Administration" /> <link rel="chapter" href="/virtuoso/ch-accessinterfaces/" oldhref="ch-accessinterfaces.html" title="Chapter聽7.聽Data Access Interfaces" /> <link rel="chapter" href="/virtuoso/ch-vdbengine/" oldhref="ch-vdbengine.html" title="Chapter聽8.聽Virtual Database Engine" /> <link rel="chapter" href="/virtuoso/ch-sqlreference/" oldhref="ch-sqlreference.html" title="Chapter聽9.聽SQL Reference" /> <link rel="chapter" href="/virtuoso/ch-clusterprogramming/" oldhref="ch-clusterprogramming.html" title="Chapter聽10.聽Virtuoso Cluster Programming" /> <link rel="chapter" href="/virtuoso/ch-sqlprocedures/" oldhref="ch-sqlprocedures.html" title="Chapter聽11.聽SQL Procedure Language Guide" /> <link rel="chapter" href="/virtuoso/ch-hooks/" oldhref="ch-hooks.html" title="Chapter聽12.聽Database Event Hooks" /> <link rel="chapter" href="/virtuoso/ch-repl/" oldhref="ch-repl.html" title="Chapter聽13.聽Data Replication, Synchronization and Transformation Services" /> <link rel="chapter" href="/virtuoso/ch-webappdevelopment/" oldhref="ch-webappdevelopment.html" title="Chapter聽14.聽Web Application Development" /> <link rel="refentry" href="/virtuoso/vc_type_calculateablevalue/" oldhref="vc_type_calculateablevalue.html" title="CalculateableValue" /> <link rel="refentry" href="/virtuoso/vc_type_forcedcalculateablevalue/" oldhref="vc_type_forcedcalculateablevalue.html" title="ForcedCalculateableValue" /> <link rel="refentry" href="/virtuoso/vc_type_sqlcode/" oldhref="vc_type_sqlcode.html" title="SqlCode" /> <link rel="refentry" href="/virtuoso/vc_type_sqlname/" oldhref="vc_type_sqlname.html" title="SqlName" /> <link rel="refentry" href="/virtuoso/vc_after_data_bind/" oldhref="vc_after_data_bind.html" title="after-data-bind" /> <link rel="refentry" href="/virtuoso/vc_after_data_bind_container/" oldhref="vc_after_data_bind_container.html" title="after-data-bind-container" /> <link rel="refentry" href="/virtuoso/vc_before_data_bind/" oldhref="vc_before_data_bind.html" title="before-data-bind" /> <link rel="refentry" href="/virtuoso/vc_before_data_bind_container/" oldhref="vc_before_data_bind_container.html" title="before-data-bind-container" /> <link rel="refentry" href="/virtuoso/vc_before_render/" oldhref="vc_before_render.html" title="before-render" /> <link rel="refentry" href="/virtuoso/vc_before_render_container/" oldhref="vc_before_render_container.html" title="before-render-container" /> <link rel="refentry" href="/virtuoso/vc_button/" oldhref="vc_button.html" title="button" /> <link rel="refentry" href="/virtuoso/vc_calendar/" oldhref="vc_calendar.html" title="calendar" /> <link rel="refentry" href="/virtuoso/vc_check_box/" oldhref="vc_check_box.html" title="check-box" /> <link rel="refentry" href="/virtuoso/vc_code_file/" oldhref="vc_code_file.html" title="code-file" /> <link rel="refentry" href="/virtuoso/vc_column/" oldhref="vc_column.html" title="column" /> <link rel="refentry" href="/virtuoso/vc_data_grid/" oldhref="vc_data_grid.html" title="data-grid" /> <link rel="refentry" href="/virtuoso/vc_data_list/" oldhref="vc_data_list.html" title="data-list" /> <link rel="refentry" href="/virtuoso/vc_data_set/" oldhref="vc_data_set.html" title="data-set" /> <link rel="refentry" href="/virtuoso/vc_data_source/" oldhref="vc_data_source.html" title="data-source" /> <link rel="refentry" href="/virtuoso/vc_error_summary/" oldhref="vc_error_summary.html" title="error-summary" /> <link rel="refentry" href="/virtuoso/vc_expression/" oldhref="vc_expression.html" title="expression" /> <link rel="refentry" href="/virtuoso/vc_field/" oldhref="vc_field.html" title="field" /> <link rel="refentry" href="/virtuoso/vc_form/" oldhref="vc_form.html" title="form" /> <link rel="refentry" href="/virtuoso/vc_hidden/" oldhref="vc_hidden.html" title="hidden" /> <link rel="refentry" href="/virtuoso/vc_horizontal_template/" oldhref="vc_horizontal_template.html" title="horizontal-template" /> <link rel="refentry" href="/virtuoso/vc_include/" oldhref="vc_include.html" title="include" /> <link rel="refentry" href="/virtuoso/vc_isql/" oldhref="vc_isql.html" title="isql" /> <link rel="refentry" href="/virtuoso/vc_item/" oldhref="vc_item.html" title="item" /> <link rel="refentry" href="/virtuoso/vc_key/" oldhref="vc_key.html" title="key" /> <link rel="refentry" href="/virtuoso/vc_label/" oldhref="vc_label.html" title="label" /> <link rel="refentry" href="/virtuoso/vc_leaf_template/" oldhref="vc_leaf_template.html" title="leaf-template" /> <link rel="refentry" href="/virtuoso/vc_local_variable/" oldhref="vc_local_variable.html" title="local-variable" /> <link rel="refentry" href="/virtuoso/vc_login/" oldhref="vc_login.html" title="login" /> <link rel="refentry" href="/virtuoso/vc_login_form/" oldhref="vc_login_form.html" title="login-form" /> <link rel="refentry" href="/virtuoso/vc_method/" oldhref="vc_method.html" title="method" /> <link rel="refentry" href="/virtuoso/vc_node/" oldhref="vc_node.html" title="node" /> <link rel="refentry" href="/virtuoso/vc_node_template/" oldhref="vc_node_template.html" title="node-template" /> <link rel="refentry" href="/virtuoso/vc_on_init/" oldhref="vc_on_init.html" title="on-init" /> <link rel="refentry" href="/virtuoso/vc_on_init_container/" oldhref="vc_on_init_container.html" title="on-init-container" /> <link rel="refentry" href="/virtuoso/vc_on_post/" oldhref="vc_on_post.html" title="on-post" /> <link rel="refentry" href="/virtuoso/vc_on_post_container/" oldhref="vc_on_post_container.html" title="on-post-container" /> <link rel="refentry" href="/virtuoso/vc_page/" oldhref="vc_page.html" title="page" /> <link rel="refentry" href="/virtuoso/vc_param/" oldhref="vc_param.html" title="param" /> <link rel="refentry" href="/virtuoso/vc_placeholder/" oldhref="vc_placeholder.html" title="placeholder" /> <link rel="refentry" href="/virtuoso/vc_radio_button/" oldhref="vc_radio_button.html" title="radio-button" /> <link rel="refentry" href="/virtuoso/vc_radio_group/" oldhref="vc_radio_group.html" title="radio-group" /> <link rel="refentry" href="/virtuoso/vc_script/" oldhref="vc_script.html" title="script" /> <link rel="refentry" href="/virtuoso/vc_select_list/" oldhref="vc_select_list.html" title="select-list" /> <link rel="refentry" href="/virtuoso/vc_style/" oldhref="vc_style.html" title="style" /> <link rel="refentry" href="/virtuoso/vc_tab/" oldhref="vc_tab.html" title="tab" /> <link rel="refentry" href="/virtuoso/vc_template/" oldhref="vc_template.html" title="template" /> <link rel="refentry" href="/virtuoso/vc_text/" oldhref="vc_text.html" title="text" /> <link rel="refentry" href="/virtuoso/vc_textarea/" oldhref="vc_textarea.html" title="textarea" /> <link rel="refentry" href="/virtuoso/vc_tree/" oldhref="vc_tree.html" title="tree" /> <link rel="refentry" href="/virtuoso/vc_url/" oldhref="vc_url.html" title="url" /> <link rel="refentry" href="/virtuoso/vc_validator/" oldhref="vc_validator.html" title="validator" /> <link rel="refentry" href="/virtuoso/vc_variable/" oldhref="vc_variable.html" title="variable" /> <link rel="refentry" href="/virtuoso/vc_vscx/" oldhref="vc_vscx.html" title="vscx" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub/" oldhref="vc_xsd_stub.html" title="xsd-stub" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub_script/" oldhref="vc_xsd_stub_script.html" title="xsd-stub-script" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub_top/" oldhref="vc_xsd_stub_top.html" title="xsd-stub-top" /> <link rel="chapter" href="/virtuoso/ch-webandxml/" oldhref="ch-webandxml.html" title="Chapter聽15.聽XML Support" /> <link rel="chapter" href="/virtuoso/ch-rdfandsparql/" oldhref="ch-rdfandsparql.html" title="Chapter聽16.聽RDF Data Access and Data Management" /> <link rel="chapter" href="/virtuoso/ch-webservices/" oldhref="ch-webservices.html" title="Chapter聽17.聽Web Services" /> <link rel="chapter" href="/virtuoso/ch-runtimehosting/" oldhref="ch-runtimehosting.html" title="Chapter聽18.聽Runtime Hosting" /> <link rel="chapter" href="/virtuoso/ch-internetservices/" oldhref="ch-internetservices.html" title="Chapter聽19.聽Internet Services" /> <link rel="chapter" href="/virtuoso/ch-freetext/" oldhref="ch-freetext.html" title="Chapter聽20.聽Free Text Search" /> <link rel="chapter" href="/virtuoso/ch-tpcc/" oldhref="ch-tpcc.html" title="Chapter聽21.聽TPC C Benchmark Kit" /> <link rel="chapter" href="/virtuoso/ch-xa/" oldhref="ch-xa.html" title="Chapter聽22.聽Using Virtuoso with Tuxedo" /> <link rel="chapter" href="/virtuoso/ch-appendixa/" oldhref="ch-appendixa.html" title="Chapter聽23.聽Appendix A" /> <link rel="chapter" href="/virtuoso/ch-functions/" oldhref="ch-functions.html" title="Chapter聽24.聽Virtuoso Functions Guide & Reference" /> <link rel="refentry" href="/virtuoso/fn_var/" oldhref="fn_var.html" title="VAR" /> <link rel="refentry" href="/virtuoso/fn_var_samp/" oldhref="fn_var_samp.html" title="VAR_SAMP" /> <link rel="refentry" href="/virtuoso/fn_var_pop/" oldhref="fn_var_pop.html" title="VAR_POP" /> <link rel="refentry" href="/virtuoso/fn_stddev/" oldhref="fn_stddev.html" title="STDDEV" /> <link rel="refentry" href="/virtuoso/fn_stddev_samp/" oldhref="fn_stddev_samp.html" title="STDDEV_SAMP" /> <link rel="refentry" href="/virtuoso/fn_stddev_pop/" oldhref="fn_stddev_pop.html" title="STDDEV_POP" /> <link rel="refentry" href="/virtuoso/fn_regr_syy/" oldhref="fn_regr_syy.html" title="REGR_SYY" /> <link rel="refentry" href="/virtuoso/fn_regr_sxx/" oldhref="fn_regr_sxx.html" title="REGR_SXX" /> <link rel="refentry" href="/virtuoso/fn_regr_sxy/" oldhref="fn_regr_sxy.html" title="REGR_SXY" /> <link rel="refentry" href="/virtuoso/fn_regr_avgx/" oldhref="fn_regr_avgx.html" title="REGR_AVGX" /> <link rel="refentry" href="/virtuoso/fn_regr_avgy/" oldhref="fn_regr_avgy.html" title="REGR_AVGY" /> <link rel="refentry" href="/virtuoso/fn_regr_r2/" oldhref="fn_regr_r2.html" title="REGR_R2" /> <link rel="refentry" href="/virtuoso/fn_regr_count/" oldhref="fn_regr_count.html" title="REGR_COUNT" /> <link rel="refentry" href="/virtuoso/fn_regr_intercept/" oldhref="fn_regr_intercept.html" title="REGR_INTERCEPT" /> <link rel="refentry" href="/virtuoso/fn_regr_slope/" oldhref="fn_regr_slope.html" title="REGR_SLOPE" /> <link rel="refentry" href="/virtuoso/fn_covar_samp/" oldhref="fn_covar_samp.html" title="COVAR_SAMP" /> <link rel="refentry" href="/virtuoso/fn_covar_pop/" oldhref="fn_covar_pop.html" title="COVAR_POP" /> <link rel="refentry" href="/virtuoso/fn_corr/" oldhref="fn_corr.html" title="CORR" /> <link rel="refentry" href="/virtuoso/fn_xq_sequence_agg/" oldhref="fn_xq_sequence_agg.html" title="DB.DBA.XQ_SEQUENCE_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_agg/" oldhref="fn_vector_agg.html" title="DB.DBA.VECTOR_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_of_nonnulls_agg/" oldhref="fn_vector_of_nonnulls_agg.html" title="DB.DBA.VECTOR_OF_NONNULLS_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_or_null_agg/" oldhref="fn_vector_or_null_agg.html" title="DB.DBA.VECTOR_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_of_nonnulls_or_null_agg/" oldhref="fn_vector_of_nonnulls_or_null_agg.html" title="DB.DBA.VECTOR_OF_NONNULLS_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_concat_agg/" oldhref="fn_vector_concat_agg.html" title="DB.DBA.VECTOR_CONCAT_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_agg/" oldhref="fn_bag_agg.html" title="DB.DBA.BAG_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_of_nonnulls_agg/" oldhref="fn_bag_of_nonnulls_agg.html" title="DB.DBA.BAG_OF_NONNULLS_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_or_null_agg/" oldhref="fn_bag_or_null_agg.html" title="DB.DBA.BAG_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_of_nonnulls_or_null_agg/" oldhref="fn_bag_of_nonnulls_or_null_agg.html" title="DB.DBA.BAG_OF_NONNULLS_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_concat_agg/" oldhref="fn_bag_concat_agg.html" title="DB.DBA.BAG_CONCAT_AGG" /> <link rel="refentry" href="/virtuoso/fn_abs/" oldhref="fn_abs.html" title="abs" /> <link rel="refentry" href="/virtuoso/fn___any_grants/" oldhref="fn___any_grants.html" title="__any_grants" /> <link rel="refentry" href="/virtuoso/fn_aref/" oldhref="fn_aref.html" title="aref" /> <link rel="refentry" href="/virtuoso/fn_ascii/" oldhref="fn_ascii.html" title="ascii" /> <link rel="refentry" href="/virtuoso/fn_aset/" oldhref="fn_aset.html" title="aset" /> <link rel="refentry" href="/virtuoso/fn_atof/" oldhref="fn_atof.html" title="atof" /> <link rel="refentry" href="/virtuoso/fn_atoi/" oldhref="fn_atoi.html" title="atoi" /> <link rel="refentry" href="/virtuoso/fn_att_local_name/" oldhref="fn_att_local_name.html" title="att_local_name" /> <link rel="refentry" href="/virtuoso/fn_backup/" oldhref="fn_backup.html" title="backup" /> <link rel="refentry" href="/virtuoso/fn_backup_online/" oldhref="fn_backup_online.html" title="backup_online" /> <link rel="refentry" href="/virtuoso/fn_backup_context_clear/" oldhref="fn_backup_context_clear.html" title="backup_context_clear" /> <link rel="refentry" href="/virtuoso/fn_bif_arg/" oldhref="fn_bif_arg.html" title="Virtuoso Server Extension Interface (VSEI) functions" /> <link rel="refentry" href="/virtuoso/fn_bit_and/" oldhref="fn_bit_and.html" title="bit_and" /> <link rel="refentry" href="/virtuoso/fn_bit_or/" oldhref="fn_bit_or.html" title="bit_or" /> <link rel="refentry" href="/virtuoso/fn_bit_not/" oldhref="fn_bit_not.html" title="bit_not" /> <link rel="refentry" href="/virtuoso/fn_bit_shift/" oldhref="fn_bit_shift.html" title="bit_shift" /> <link rel="refentry" href="/virtuoso/fn_bit_xor/" oldhref="fn_bit_xor.html" title="bit_xor" /> <link rel="refentry" href="/virtuoso/fn_blob_to_string/" oldhref="fn_blob_to_string.html" title="blob_to_string" /> <link rel="refentry" href="/virtuoso/fn_blob_to_string_output/" oldhref="fn_blob_to_string_output.html" title="blob_to_string_output" /> <link rel="refentry" href="/virtuoso/fn_bookmark/" oldhref="fn_bookmark.html" title="bookmark" /> <link rel="refentry" href="/virtuoso/fn_ceiling/" oldhref="fn_ceiling.html" title="ceiling" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_count/" oldhref="fn_cfg_item_count.html" title="cfg_item_count" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_name/" oldhref="fn_cfg_item_name.html" title="cfg_item_name" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_value/" oldhref="fn_cfg_item_value.html" title="cfg_item_value" /> <link rel="refentry" href="/virtuoso/fn_cfg_section_count/" oldhref="fn_cfg_section_count.html" title="cfg_section_count" /> <link rel="refentry" href="/virtuoso/fn_cfg_section_name/" oldhref="fn_cfg_section_name.html" title="cfg_section_name" /> <link rel="refentry" href="/virtuoso/fn_cfg_write/" oldhref="fn_cfg_write.html" title="cfg_write" /> <link rel="refentry" href="/virtuoso/fn_charset_define/" oldhref="fn_charset_define.html" title="charset_define" /> <link rel="refentry" href="/virtuoso/fn_charset_recode/" oldhref="fn_charset_recode.html" title="charset_recode" /> <link rel="refentry" href="/virtuoso/fn_charsets_list/" oldhref="fn_charsets_list.html" title="charsets_list" /> <link rel="refentry" href="/virtuoso/fn_checkpoint_interval/" oldhref="fn_checkpoint_interval.html" title="checkpoint_interval" /> <link rel="refentry" href="/virtuoso/fn_chr/" oldhref="fn_chr.html" title="chr" /> <link rel="refentry" href="/virtuoso/fn_client_attr/" oldhref="fn_client_attr.html" title="client_attr" /> <link rel="refentry" href="/virtuoso/fn_collation_define/" oldhref="fn_collation_define.html" title="collation_define" /> <link rel="refentry" href="/virtuoso/fn_complete_table_name/" oldhref="fn_complete_table_name.html" title="complete_table_name" /> <link rel="refentry" href="/virtuoso/fn_composite/" oldhref="fn_composite.html" title="composite" /> <link rel="refentry" href="/virtuoso/fn_composite_ref/" oldhref="fn_composite_ref.html" title="composite_ref" /> <link rel="refentry" href="/virtuoso/fn_concat/" oldhref="fn_concat.html" title="concat" /> <link rel="refentry" href="/virtuoso/fn_concatenate/" oldhref="fn_concatenate.html" title="concatenate" /> <link rel="refentry" href="/virtuoso/fn_connection_get/" oldhref="fn_connection_get.html" title="connection_get" /> <link rel="refentry" href="/virtuoso/fn_connection_id/" oldhref="fn_connection_id.html" title="connection_id" /> <link rel="refentry" href="/virtuoso/fn_connection_is_dirty/" oldhref="fn_connection_is_dirty.html" title="connection_is_dirty" /> <link rel="refentry" href="/virtuoso/fn_connection_set/" oldhref="fn_connection_set.html" title="connection_set" /> <link rel="refentry" href="/virtuoso/fn_connection_vars/" oldhref="fn_connection_vars.html" title="connection_vars" /> <link rel="refentry" href="/virtuoso/fn_connection_vars_set/" oldhref="fn_connection_vars_set.html" title="connection_vars_set" /> <link rel="refentry" href="/virtuoso/fn_contains/" oldhref="fn_contains.html" title="contains" /> <link rel="refentry" href="/virtuoso/fn_cov_load/" oldhref="fn_cov_load.html" title="cov_load" /> <link rel="refentry" href="/virtuoso/fn_cov_report/" oldhref="fn_cov_report.html" title="cov_report" /> <link rel="refentry" href="/virtuoso/fn_cov_store/" oldhref="fn_cov_store.html" title="cov_store" /> <link rel="refentry" href="/virtuoso/fn_createxml/" oldhref="fn_createxml.html" title="createXML" /> <link rel="refentry" href="/virtuoso/fn_curdate/" oldhref="fn_curdate.html" title="curdate" /> <link rel="refentry" href="/virtuoso/fn_forget_timezone/" oldhref="fn_forget_timezone.html" title="forget_timezone" /> <link rel="refentry" href="/virtuoso/fn_is_timezoneless/" oldhref="fn_is_timezoneless.html" title="is_timezoneless" /> <link rel="refentry" href="/virtuoso/fn_adjust_timezone/" oldhref="fn_adjust_timezone.html" title="adjust_timezone" /> <link rel="refentry" href="/virtuoso/fn_rdf_now_impl/" oldhref="fn_rdf_now_impl.html" title="rdf_now_impl" /> <link rel="refentry" href="/virtuoso/fn_current_timestamp/" oldhref="fn_current_timestamp.html" title="current_timestamp" /> <link rel="refentry" href="/virtuoso/fn_curdatetime/" oldhref="fn_curdatetime.html" title="curdatetime" /> <link rel="refentry" href="/virtuoso/fn_curdatetimeoffset/" oldhref="fn_curdatetimeoffset.html" title="curdatetimeoffset" /> <link rel="refentry" href="/virtuoso/fn_curutcdatetime/" oldhref="fn_curutcdatetime.html" title="curutcdatetime" /> <link rel="refentry" href="/virtuoso/fn_sysutcdatetime/" oldhref="fn_sysutcdatetime.html" title="sysutcdatetime" /> <link rel="refentry" href="/virtuoso/fn_current_charset/" oldhref="fn_current_charset.html" title="current_charset" /> <link rel="refentry" href="/virtuoso/fn_vacuum/" oldhref="fn_vacuum.html" title="DB.DBA.VACUUM" /> <link rel="refentry" href="/virtuoso/fn_sparql_to_sql_text/" oldhref="fn_sparql_to_sql_text.html" title="sparql_to_sql_text" /> <link rel="refentry" href="/virtuoso/fn_dateadd/" oldhref="fn_dateadd.html" title="dateadd" /> <link rel="refentry" href="/virtuoso/fn_datediff/" oldhref="fn_datediff.html" title="datediff" /> <link rel="refentry" href="/virtuoso/fn_datestring/" oldhref="fn_datestring.html" title="datestring , datestring_gmt ," /> <link rel="refentry" href="/virtuoso/fn_datestring_gmt/" oldhref="fn_datestring_gmt.html" title="datestring_GMT" /> <link rel="refentry" href="/virtuoso/fn_dav_api_add/" oldhref="fn_dav_api_add.html" title="DAV add & update functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_change/" oldhref="fn_dav_api_change.html" title="DAV manipulation functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_lock/" oldhref="fn_dav_api_lock.html" title="DAV lock manipulation functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_search/" oldhref="fn_dav_api_search.html" title="DAV search functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_user/" oldhref="fn_dav_api_user.html" title="WebDAV Users & Groups administration" /> <link rel="refentry" href="/virtuoso/fn_dav_exp/" oldhref="fn_dav_exp.html" title="DAV_EXP" /> <link rel="refentry" href="/virtuoso/fn_dayname/" oldhref="fn_dayname.html" title="dayname" /> <link rel="refentry" href="/virtuoso/fn_dayofmonth/" oldhref="fn_dayofmonth.html" title="dayofmonth" /> <link rel="refentry" href="/virtuoso/fn_dayofweek/" oldhref="fn_dayofweek.html" title="dayofweek" /> <link rel="refentry" href="/virtuoso/fn_dayofyear/" oldhref="fn_dayofyear.html" title="dayofyear" /> <link rel="refentry" href="/virtuoso/fn_dbg_obj_print/" oldhref="fn_dbg_obj_print.html" title="dbg_obj_print" /> <link rel="refentry" href="/virtuoso/fn_dbg_printf/" oldhref="fn_dbg_printf.html" title="dbg_printf" /> <link rel="refentry" href="/virtuoso/fn_dbname/" oldhref="fn_dbname.html" title="dbname" /> <link rel="refentry" href="/virtuoso/fn_delay/" oldhref="fn_delay.html" title="delay" /> <link rel="refentry" href="/virtuoso/fn_cl_exec/" oldhref="fn_cl_exec.html" title="cl_exec" /> <link rel="refentry" href="/virtuoso/fn_dict_dec_or_remove/" oldhref="fn_dict_dec_or_remove.html" title="dict_dec_or_remove" /> <link rel="refentry" href="/virtuoso/fn_dict_duplicate/" oldhref="fn_dict_duplicate.html" title="dict_duplicate" /> <link rel="refentry" href="/virtuoso/fn_dict_get/" oldhref="fn_dict_get.html" title="dict_get" /> <link rel="refentry" href="/virtuoso/fn_dict_inc_or_put/" oldhref="fn_dict_inc_or_put.html" title="dict_inc_or_put" /> <link rel="refentry" href="/virtuoso/fn_dict_iter_next/" oldhref="fn_dict_iter_next.html" title="dict_iter_next" /> <link rel="refentry" href="/virtuoso/fn_dict_iter_rewind/" oldhref="fn_dict_iter_rewind.html" title="dict_iter_rewind" /> <link rel="refentry" href="/virtuoso/fn_dict_list_keys/" oldhref="fn_dict_list_keys.html" title="dict_list_keys" /> <link rel="refentry" href="/virtuoso/fn_dict_destructive_list_rnd_keys/" oldhref="fn_dict_destructive_list_rnd_keys.html" title="dict_destructive_list_rnd_keys" /> <link rel="refentry" href="/virtuoso/fn_dict_new/" oldhref="fn_dict_new.html" title="dict_new" /> <link rel="refentry" href="/virtuoso/fn_dict_put/" oldhref="fn_dict_put.html" title="dict_put" /> <link rel="refentry" href="/virtuoso/fn_dict_remove/" oldhref="fn_dict_remove.html" title="dict_remove" /> <link rel="refentry" href="/virtuoso/fn_dict_size/" oldhref="fn_dict_size.html" title="dict_size" /> <link rel="refentry" href="/virtuoso/fn_dict_to_vector/" oldhref="fn_dict_to_vector.html" title="dict_to_vector" /> <link rel="refentry" href="/virtuoso/fn_dict_zap/" oldhref="fn_dict_zap.html" title="dict_zap" /> <link rel="refentry" href="/virtuoso/fn_disconnect_user/" oldhref="fn_disconnect_user.html" title="disconnect_user" /> <link rel="refentry" href="/virtuoso/fn_dt_set_tz/" oldhref="fn_dt_set_tz.html" title="dt_set_tz" /> <link rel="refentry" href="/virtuoso/fn_dvector/" oldhref="fn_dvector.html" title="dvector" /> <link rel="refentry" href="/virtuoso/fn_end_result/" oldhref="fn_end_result.html" title="end_result" /> <link rel="refentry" href="/virtuoso/fn_either/" oldhref="fn_either.html" title="either" /> <link rel="refentry" href="/virtuoso/fn_elh_get_handler/" oldhref="fn_elh_get_handler.html" title="elh_get_handler" /> <link rel="refentry" href="/virtuoso/fn_elh_load_handler/" oldhref="fn_elh_load_handler.html" title="elh_load_handler" /> <link rel="refentry" href="/virtuoso/fn_encode_base64/" oldhref="fn_encode_base64.html" title="encode_base64" /> <link rel="refentry" href="/virtuoso/fn_equ/" oldhref="fn_equ.html" title="equ" /> <link rel="refentry" href="/virtuoso/fn_exec/" oldhref="fn_exec.html" title="exec" /> <link rel="refentry" href="/virtuoso/fn_exec_close/" oldhref="fn_exec_close.html" title="close" /> <link rel="refentry" href="/virtuoso/fn_exec_next/" oldhref="fn_exec_next.html" title="exec_next" /> <link rel="refentry" href="/virtuoso/fn_exec_result/" oldhref="fn_exec_result.html" title="exec_result" /> <link rel="refentry" href="/virtuoso/fn_exec_result_names/" oldhref="fn_exec_result_names.html" title="exec_result_names" /> <link rel="refentry" href="/virtuoso/fn_exec_metadata/" oldhref="fn_exec_metadata.html" title="exec_metadata" /> <link rel="refentry" href="/virtuoso/fn_exec_score/" oldhref="fn_exec_score.html" title="exec_score" /> <link rel="refentry" href="/virtuoso/fn_exp/" oldhref="fn_exp.html" title="exp" /> <link rel="refentry" href="/virtuoso/fn_explain/" oldhref="fn_explain.html" title="explain" /> <link rel="refentry" href="/virtuoso/fn_file_delete/" oldhref="fn_file_delete.html" title="file_delete" /> <link rel="refentry" href="/virtuoso/fn_file_open/" oldhref="fn_file_open.html" title="file_open" /> <link rel="refentry" href="/virtuoso/fn_ft_set_file/" oldhref="fn_ft_set_file.html" title="ft_set_file" /> <link rel="refentry" href="/virtuoso/fn_file_dirlist/" oldhref="fn_file_dirlist.html" title="file_dirlist" /> <link rel="refentry" href="/virtuoso/fn_file_mkdir/" oldhref="fn_file_mkdir.html" title="file_mkdir" /> <link rel="refentry" href="/virtuoso/fn_file_mkpath/" oldhref="fn_file_mkpath.html" title="file_mkpath" /> <link rel="refentry" href="/virtuoso/fn_file_stat/" oldhref="fn_file_stat.html" title="file_stat" /> <link rel="refentry" href="/virtuoso/fn_file_to_string/" oldhref="fn_file_to_string.html" title="file_to_string" /> <link rel="refentry" href="/virtuoso/fn_file_to_string_output/" oldhref="fn_file_to_string_output.html" title="file_to_string_output" /> <link rel="refentry" href="/virtuoso/fn_file_unlink/" oldhref="fn_file_unlink.html" title="file_unlink" /> <link rel="refentry" href="/virtuoso/fn_fk_check_input_values/" oldhref="fn_fk_check_input_values.html" title="fk_check_input_values" /> <link rel="refentry" href="/virtuoso/fn_floor/" oldhref="fn_floor.html" title="floor" /> <link rel="refentry" href="/virtuoso/fn_ftp_get/" oldhref="fn_ftp_get.html" title="ftp_get" /> <link rel="refentry" href="/virtuoso/fn_ftp_ls/" oldhref="fn_ftp_ls.html" title="ftp_ls" /> <link rel="refentry" href="/virtuoso/fn_ftp_put/" oldhref="fn_ftp_put.html" title="ftp_put" /> <link rel="refentry" href="/virtuoso/fn_gz_file_open/" oldhref="fn_gz_file_open.html" title="gz_file_open" /> <link rel="refentry" href="/virtuoso/fn_get_csv_row/" oldhref="fn_get_csv_row.html" title="get_csv_row" /> <link rel="refentry" href="/virtuoso/fn_csv_load_file/" oldhref="fn_csv_load_file.html" title="csv_load_file" /> <link rel="refentry" href="/virtuoso/fn_attach_from_csv/" oldhref="fn_attach_from_csv.html" title="attach_from_csv" /> <link rel="refentry" href="/virtuoso/fn_csv_load/" oldhref="fn_csv_load.html" title="csv_load" /> <link rel="refentry" href="/virtuoso/fn_csv_parse/" oldhref="fn_csv_parse.html" title="csv_parse" /> <link rel="refentry" href="/virtuoso/fn_csv_cols_def/" oldhref="fn_csv_cols_def.html" title="csv_cols_def" /> <link rel="refentry" href="/virtuoso/fn_csv_table_def/" oldhref="fn_csv_table_def.html" title="csv_table_def" /> <link rel="refentry" href="/virtuoso/fn_get_certificate_info/" oldhref="fn_get_certificate_info.html" title="get_certificate_info" /> <link rel="refentry" href="/virtuoso/fn_get_keyword/" oldhref="fn_get_keyword.html" title="get_keyword" /> <link rel="refentry" href="/virtuoso/fn_get_keyword_ucase/" oldhref="fn_get_keyword_ucase.html" title="get_keyword_ucase" /> <link rel="refentry" href="/virtuoso/fn_get_timestamp/" oldhref="fn_get_timestamp.html" title="get_timestamp" /> <link rel="refentry" href="/virtuoso/fn_getdate/" oldhref="fn_getdate.html" title="getdate" /> <link rel="refentry" href="/virtuoso/fn_gvector_sort/" oldhref="fn_gvector_sort.html" title="gvector_sort" /> <link rel="refentry" href="/virtuoso/fn_gvector_digit_sort/" oldhref="fn_gvector_digit_sort.html" title="gvector_digit_sort" /> <link rel="refentry" href="/virtuoso/fn_gz_compress/" oldhref="fn_gz_compress.html" title="gz_compress" /> <link rel="refentry" href="/virtuoso/fn_gz_uncompress/" oldhref="fn_gz_uncompress.html" title="gz_uncompress" /> <link rel="refentry" href="/virtuoso/fn_st_affine/" oldhref="fn_st_affine.html" title="ST_Affine" /> <link rel="refentry" href="/virtuoso/fn_st_point/" oldhref="fn_st_point.html" title="st_point" /> <link rel="refentry" href="/virtuoso/fn_st_x/" oldhref="fn_st_x.html" title="st_x" /> <link rel="refentry" href="/virtuoso/fn_st_y/" oldhref="fn_st_y.html" title="st_y" /> <link rel="refentry" href="/virtuoso/fn_st_distance/" oldhref="fn_st_distance.html" title="st_distance" /> <link rel="refentry" href="/virtuoso/fn_st_srid/" oldhref="fn_st_srid.html" title="ST_SRID" /> <link rel="refentry" href="/virtuoso/fn_st_setsrid/" oldhref="fn_st_setsrid.html" title="ST_SetSRID" /> <link rel="refentry" href="/virtuoso/fn_st_astext/" oldhref="fn_st_astext.html" title="st_astext" /> <link rel="refentry" href="/virtuoso/fn_st_geomfromtext/" oldhref="fn_st_geomfromtext.html" title="st_geomfromtext" /> <link rel="refentry" href="/virtuoso/fn_st_intersects/" oldhref="fn_st_intersects.html" title="st_intersects" /> <link rel="refentry" href="/virtuoso/fn_st_contains/" oldhref="fn_st_contains.html" title="st_contains" /> <link rel="refentry" href="/virtuoso/fn_st_within/" oldhref="fn_st_within.html" title="st_within" /> <link rel="refentry" href="/virtuoso/fn_isgeometry/" oldhref="fn_isgeometry.html" title="isgeometry" /> <link rel="refentry" href="/virtuoso/fn_geo_insert/" oldhref="fn_geo_insert.html" title="geo_insert" /> <link rel="refentry" href="/virtuoso/fn_geo_delete/" oldhref="fn_geo_delete.html" title="geo_delete" /> <link rel="refentry" href="/virtuoso/fn_hour/" oldhref="fn_hour.html" title="hour" /> <link rel="refentry" href="/virtuoso/fn_http/" oldhref="fn_http.html" title="http" /> <link rel="refentry" href="/virtuoso/fn_http_lock/" oldhref="fn_http_lock.html" title="http_lock" /> <link rel="refentry" href="/virtuoso/fn_http_unlock/" oldhref="fn_http_unlock.html" title="http_unlock" /> <link rel="refentry" href="/virtuoso/fn_http_acl_set/" oldhref="fn_http_acl_set.html" title="http_acl_set" /> <link rel="refentry" href="/virtuoso/fn_http_acl_get/" oldhref="fn_http_acl_get.html" title="http_acl_get" /> <link rel="refentry" href="/virtuoso/fn_http_acl_remove/" oldhref="fn_http_acl_remove.html" title="http_acl_remove" /> <link rel="refentry" href="/virtuoso/fn_http_body_read/" oldhref="fn_http_body_read.html" title="http_body_read" /> <link rel="refentry" href="/virtuoso/fn_http_client/" oldhref="fn_http_client.html" title="http_client" /> <link rel="refentry" href="/virtuoso/fn_http_client_ext/" oldhref="fn_http_client_ext.html" title="http_client_ext" /> <link rel="refentry" href="/virtuoso/fn_http_client_ip/" oldhref="fn_http_client_ip.html" title="http_client_ip" /> <link rel="refentry" href="/virtuoso/fn_dns_txt_get/" oldhref="fn_dns_txt_get.html" title="dns_txt_get" /> <link rel="refentry" href="/virtuoso/fn_http_debug_log/" oldhref="fn_http_debug_log.html" title="http_debug_log" /> <link rel="refentry" href="/virtuoso/fn_http_enable_gz/" oldhref="fn_http_enable_gz.html" title="http_enable_gz" /> <link rel="refentry" href="/virtuoso/fn_http_file/" oldhref="fn_http_file.html" title="http_file" /> <link rel="refentry" href="/virtuoso/fn_http_flush/" oldhref="fn_http_flush.html" title="http_flush" /> <link rel="refentry" href="/virtuoso/fn_http_internal_redirect/" oldhref="fn_http_internal_redirect.html" title="http_internal_redirect" /> <link rel="refentry" href="/virtuoso/fn_http_get/" oldhref="fn_http_get.html" title="http_get" /> <link rel="refentry" href="/virtuoso/fn_http_header/" oldhref="fn_http_header.html" title="http_header" /> <link rel="refentry" href="/virtuoso/fn_http_header_get/" oldhref="fn_http_header_get.html" title="http_header_get" /> <link rel="refentry" href="/virtuoso/fn_http_kill/" oldhref="fn_http_kill.html" title="http_kill" /> <link rel="refentry" href="/virtuoso/fn_http_listen_host/" oldhref="fn_http_listen_host.html" title="http_listen_host" /> <link rel="refentry" href="/virtuoso/fn_http_map_table/" oldhref="fn_http_map_table.html" title="http_map_table" /> <link rel="refentry" href="/virtuoso/fn_http_map_get/" oldhref="fn_http_map_get.html" title="http_map_get" /> <link rel="refentry" href="/virtuoso/fn_http_param/" oldhref="fn_http_param.html" title="http_param" /> <link rel="refentry" href="/virtuoso/fn_http_path/" oldhref="fn_http_path.html" title="http_path" /> <link rel="refentry" href="/virtuoso/fn_http_pending_req/" oldhref="fn_http_pending_req.html" title="http_pending_req" /> <link rel="refentry" href="/virtuoso/fn_http_physical_path/" oldhref="fn_http_physical_path.html" title="http_physical_path" /> <link rel="refentry" href="/virtuoso/fn_http_proxy/" oldhref="fn_http_proxy.html" title="http_proxy" /> <link rel="refentry" href="/virtuoso/fn_http_request_header/" oldhref="fn_http_request_header.html" title="http_request_header" /> <link rel="refentry" href="/virtuoso/fn_http_request_header_full/" oldhref="fn_http_request_header_full.html" title="http_request_header_full" /> <link rel="refentry" href="/virtuoso/fn_http_request_status/" oldhref="fn_http_request_status.html" title="http_request_status" /> <link rel="refentry" href="/virtuoso/fn_http_request_get/" oldhref="fn_http_request_get.html" title="http_request_get" /> <link rel="refentry" href="/virtuoso/fn_http_rewrite/" oldhref="fn_http_rewrite.html" title="http_rewrite" /> <link rel="refentry" href="/virtuoso/fn_http_root/" oldhref="fn_http_root.html" title="http_root" /> <link rel="refentry" href="/virtuoso/fn_http_value/" oldhref="fn_http_value.html" title="http_value" /> <link rel="refentry" href="/virtuoso/fn_json_parse/" oldhref="fn_json_parse.html" title="json_parse" /> <link rel="refentry" href="/virtuoso/fn_http_url/" oldhref="fn_http_url.html" title="http_url" /> <link rel="refentry" href="/virtuoso/fn_http_xslt/" oldhref="fn_http_xslt.html" title="http_xslt" /> <link rel="refentry" href="/virtuoso/fn_urlrewrite_create_regex_rule/" oldhref="fn_urlrewrite_create_regex_rule.html" title="URLREWRITE_CREATE_REGEX_RULE" /> <link rel="refentry" href="/virtuoso/fn_identity_value/" oldhref="fn_identity_value.html" title="identity_value" /> <link rel="refentry" href="/virtuoso/fn_import_clr/" oldhref="fn_import_clr.html" title="import_clr" /> <link rel="refentry" href="/virtuoso/fn_import_jar/" oldhref="fn_import_jar.html" title="import_jar" /> <link rel="refentry" href="/virtuoso/fn_initcap/" oldhref="fn_initcap.html" title="initcap" /> <link rel="refentry" href="/virtuoso/fn_internal_to_sql_type/" oldhref="fn_internal_to_sql_type.html" title="internal_to_sql_type" /> <link rel="refentry" href="/virtuoso/fn_internal_type/" oldhref="fn_internal_type.html" title="internal_type" /> <link rel="refentry" href="/virtuoso/fn_internal_type_name/" oldhref="fn_internal_type_name.html" title="internal_type_name" /> <link rel="refentry" href="/virtuoso/fn_isarray/" oldhref="fn_isarray.html" title="isarray" /> <link rel="refentry" href="/virtuoso/fn_isblob/" oldhref="fn_isblob.html" title="isblob" /> <link rel="refentry" href="/virtuoso/fn_isbinary/" oldhref="fn_isbinary.html" title="isbinary" /> <link rel="refentry" href="/virtuoso/fn_isdouble/" oldhref="fn_isdouble.html" title="isdouble" /> <link rel="refentry" href="/virtuoso/fn_isentity/" oldhref="fn_isentity.html" title="isentity" /> <link rel="refentry" href="/virtuoso/fn_isfloat/" oldhref="fn_isfloat.html" title="isfloat" /> <link rel="refentry" href="/virtuoso/fn_isinteger/" oldhref="fn_isinteger.html" title="isinteger" /> <link rel="refentry" href="/virtuoso/fn_isnull/" oldhref="fn_isnull.html" title="isnull" /> <link rel="refentry" href="/virtuoso/fn_isnumeric/" oldhref="fn_isnumeric.html" title="isnumeric" /> <link rel="refentry" href="/virtuoso/fn_isfinitenumeric/" oldhref="fn_isfinitenumeric.html" title="isfinitenumeric" /> <link rel="refentry" href="/virtuoso/fn_isstring/" oldhref="fn_isstring.html" title="isstring" /> <link rel="refentry" href="/virtuoso/fn_iszero/" oldhref="fn_iszero.html" title="iszero" /> <link rel="refentry" href="/virtuoso/fn_nm_min/" oldhref="fn_nm_min.html" title="__min" /> <link rel="refentry" href="/virtuoso/fn_nm_max/" oldhref="fn_nm_max.html" title="__max" /> <link rel="refentry" href="/virtuoso/fn_nm_max_notnull/" oldhref="fn_nm_max_notnull.html" title="__max_notnull" /> <link rel="refentry" href="/virtuoso/fn_nm_min_notnull/" oldhref="fn_nm_min_notnull.html" title="__min_notnull" /> <link rel="refentry" href="/virtuoso/fn_java_call_method/" oldhref="fn_java_call_method.html" title="java_call_method" /> <link rel="refentry" href="/virtuoso/fn_java_set_property/" oldhref="fn_java_set_property.html" title="java_set_property" /> <link rel="refentry" href="/virtuoso/fn_java_get_property/" oldhref="fn_java_get_property.html" title="java_get_property" /> <link rel="refentry" href="/virtuoso/fn_java_load_class/" oldhref="fn_java_load_class.html" title="java_load_class" /> <link rel="refentry" href="/virtuoso/fn_java_new_object/" oldhref="fn_java_new_object.html" title="java_new_object" /> <link rel="refentry" href="/virtuoso/fn_java_vm_attach/" oldhref="fn_java_vm_attach.html" title="java_vm_attach" /> <link rel="refentry" href="/virtuoso/fn_java_vm_detach/" oldhref="fn_java_vm_detach.html" title="java_vm_detach" /> <link rel="refentry" href="/virtuoso/fn_jvm_ref_import/" oldhref="fn_jvm_ref_import.html" title="jvm_ref_import" /> <link rel="refentry" href="/virtuoso/fn_lcase/" oldhref="fn_lcase.html" title="lcase" /> <link rel="refentry" href="/virtuoso/fn_ldap_search/" oldhref="fn_ldap_search.html" title="ldap_search" /> <link rel="refentry" href="/virtuoso/fn_ldap_delete/" oldhref="fn_ldap_delete.html" title="ldap_delete" /> <link rel="refentry" href="/virtuoso/fn_ldap_add/" oldhref="fn_ldap_add.html" title="ldap_add" /> <link rel="refentry" href="/virtuoso/fn_ldap_modify/" oldhref="fn_ldap_modify.html" title="ldap_modify" /> <link rel="refentry" href="/virtuoso/fn_left/" oldhref="fn_left.html" title="left" /> <link rel="refentry" href="/virtuoso/fn_length/" oldhref="fn_length.html" title="length" /> <link rel="refentry" href="/virtuoso/fn_lfs_exp/" oldhref="fn_lfs_exp.html" title="LFS_EXP" /> <link rel="refentry" href="/virtuoso/fn_lh_get_handler/" oldhref="fn_lh_get_handler.html" title="lh_get_handler" /> <link rel="refentry" href="/virtuoso/fn_lh_load_handler/" oldhref="fn_lh_load_handler.html" title="lh_load_handler" /> <link rel="refentry" href="/virtuoso/fn_locate/" oldhref="fn_locate.html" title="locate" /> <link rel="refentry" href="/virtuoso/fn_log/" oldhref="fn_log.html" title="log" /> <link rel="refentry" href="/virtuoso/fn_log10/" oldhref="fn_log10.html" title="log10" /> <link rel="refentry" href="/virtuoso/fn_log_enable/" oldhref="fn_log_enable.html" title="log_enable" /> <link rel="refentry" href="/virtuoso/fn_log_message/" oldhref="fn_log_message.html" title="log_message" /> <link rel="refentry" href="/virtuoso/fn_log_text/" oldhref="fn_log_text.html" title="log_text" /> <link rel="refentry" href="/virtuoso/fn_read_log/" oldhref="fn_read_log.html" title="read_log" /> <link rel="refentry" href="/virtuoso/fn_lower/" oldhref="fn_lower.html" title="lower" /> <link rel="refentry" href="/virtuoso/fn_ltrim/" oldhref="fn_ltrim.html" title="ltrim" /> <link rel="refentry" href="/virtuoso/fn_dbf_set/" oldhref="fn_dbf_set.html" title="__dbf_set" /> <link rel="refentry" href="/virtuoso/fn_stat_import/" oldhref="fn_stat_import.html" title="stat_import" /> <link rel="refentry" href="/virtuoso/fn_stat_export/" oldhref="fn_stat_export.html" title="stat_export" /> <link rel="refentry" href="/virtuoso/fn_make_array/" oldhref="fn_make_array.html" title="make_array" /> <link rel="refentry" href="/virtuoso/fn_make_string/" oldhref="fn_make_string.html" title="make_string" /> <link rel="refentry" href="/virtuoso/fn_md5/" oldhref="fn_md5.html" title="md5" /> <link rel="refentry" href="/virtuoso/fn_md5_init/" oldhref="fn_md5_init.html" title="md5_init" /> <link rel="refentry" href="/virtuoso/fn_md5_update/" oldhref="fn_md5_update.html" title="md5_update" /> <link rel="refentry" href="/virtuoso/fn_md5_final/" oldhref="fn_md5_final.html" title="md5_final" /> <link rel="refentry" href="/virtuoso/fn_mime_body/" oldhref="fn_mime_body.html" title="mime_body" /> <link rel="refentry" href="/virtuoso/fn_mime_part/" oldhref="fn_mime_part.html" title="mime_part" /> <link rel="refentry" href="/virtuoso/fn_mime_tree/" oldhref="fn_mime_tree.html" title="mime_tree" /> <link rel="refentry" href="/virtuoso/fn_minute/" oldhref="fn_minute.html" title="minute" /> <link rel="refentry" href="/virtuoso/fn_mod/" oldhref="fn_mod.html" title="mod" /> <link rel="refentry" href="/virtuoso/fn_month/" oldhref="fn_month.html" title="month" /> <link rel="refentry" href="/virtuoso/fn_monthname/" oldhref="fn_monthname.html" title="monthname" /> <link rel="refentry" href="/virtuoso/fn_msec_time/" oldhref="fn_msec_time.html" title="msec_time" /> <link rel="refentry" href="/virtuoso/fn_mts_connect/" oldhref="fn_mts_connect.html" title="mts_connect" /> <link rel="refentry" href="/virtuoso/fn_mts_get_timeout/" oldhref="fn_mts_get_timeout.html" title="mts_get_timeout" /> <link rel="refentry" href="/virtuoso/fn_mts_set_timeout/" oldhref="fn_mts_set_timeout.html" title="mts_set_timeout" /> <link rel="refentry" href="/virtuoso/fn_mts_status/" oldhref="fn_mts_status.html" title="mts_status" /> <link rel="refentry" href="/virtuoso/fn_sha1_digest/" oldhref="fn_sha1_digest.html" title="sha1_digest" /> <link rel="refentry" href="/virtuoso/fn_name_part/" oldhref="fn_name_part.html" title="name_part" /> <link rel="refentry" href="/virtuoso/fn_nntp_auth_get/" oldhref="fn_nntp_auth_get.html" title="nntp_auth_get" /> <link rel="refentry" href="/virtuoso/fn_nntp_auth_post/" oldhref="fn_nntp_auth_post.html" title="nntp_auth_post" /> <link rel="refentry" href="/virtuoso/fn_nntp_get/" oldhref="fn_nntp_get.html" title="nntp_get" /> <link rel="refentry" href="/virtuoso/fn_nntp_post/" oldhref="fn_nntp_post.html" title="nntp_post" /> <link rel="refentry" href="/virtuoso/fn_now/" oldhref="fn_now.html" title="now" /> <link rel="refentry" href="/virtuoso/fn_amazon_start_instance/" oldhref="fn_amazon_start_instance.html" title="DB.DBA.AMAZON_START_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_run_instance/" oldhref="fn_amazon_run_instance.html" title="DB.DBA.AMAZON_RUN_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_stop_instance/" oldhref="fn_amazon_stop_instance.html" title="DB.DBA.AMAZON_STOP_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_terminate_instance/" oldhref="fn_amazon_terminate_instance.html" title="DB.DBA.AMAZON_TERMINATE_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_volume/" oldhref="fn_amazon_create_volume.html" title="DB.DBA.AMAZON_CREATE_VOLUME" /> <link rel="refentry" href="/virtuoso/fn_amazon_deregister_image/" oldhref="fn_amazon_deregister_image.html" title="DB.DBA.AMAZON_DEREGISTER_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_image/" oldhref="fn_amazon_create_image.html" title="DB.DBA.AMAZON_CREATE_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_snapshot/" oldhref="fn_amazon_create_snapshot.html" title="DB.DBA.AMAZON_CREATE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_amazon_delete_snapshot/" oldhref="fn_amazon_delete_snapshot.html" title="DB.DBA.AMAZON_DELETE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_amazon_delete_volume/" oldhref="fn_amazon_delete_volume.html" title="DB.DBA.AMAZON_DELETE_VOLUME" /> <link rel="refentry" href="/virtuoso/fn_amazon_describe_images/" oldhref="fn_amazon_describe_images.html" title="DB.DBA.AMAZON_DESCRIBE_IMAGES" /> <link rel="refentry" href="/virtuoso/fn_amazon_describe_instances/" oldhref="fn_amazon_describe_instances.html" title="DB.DBA.AMAZON_DESCRIBE_INSTANCES" /> <link rel="refentry" href="/virtuoso/fn_amazon_import_key_pair/" oldhref="fn_amazon_import_key_pair.html" title="DB.DBA.AMAZON_IMPORT_KEY_PAIR" /> <link rel="refentry" href="/virtuoso/fn_os_chmod/" oldhref="fn_os_chmod.html" title="os_chmod" /> <link rel="refentry" href="/virtuoso/fn_os_chown/" oldhref="fn_os_chown.html" title="os_chown" /> <link rel="refentry" href="/virtuoso/fn_pem_certificates_to_array/" oldhref="fn_pem_certificates_to_array.html" title="pem_certificates_to_array" /> <link rel="refentry" href="/virtuoso/fn_pldbg_stats/" oldhref="fn_pldbg_stats.html" title="pldbg_stats" /> <link rel="refentry" href="/virtuoso/fn_pldbg_stats_load/" oldhref="fn_pldbg_stats_load.html" title="pldbg_stats_load" /> <link rel="refentry" href="/virtuoso/fn_pop3_get/" oldhref="fn_pop3_get.html" title="pop3_get" /> <link rel="refentry" href="/virtuoso/fn_imap_get/" oldhref="fn_imap_get.html" title="imap_get" /> <link rel="refentry" href="/virtuoso/fn_position/" oldhref="fn_position.html" title="position" /> <link rel="refentry" href="/virtuoso/fn_power/" oldhref="fn_power.html" title="power" /> <link rel="refentry" href="/virtuoso/fn_prof_enable/" oldhref="fn_prof_enable.html" title="prof_enable" /> <link rel="refentry" href="/virtuoso/fn_prof_sample/" oldhref="fn_prof_sample.html" title="prof_sample" /> <link rel="refentry" href="/virtuoso/fn_quarter/" oldhref="fn_quarter.html" title="quarter" /> <link rel="refentry" href="/virtuoso/fn_quote_dotted/" oldhref="fn_quote_dotted.html" title="quote_dotted" /> <link rel="refentry" href="/virtuoso/fn_randomize/" oldhref="fn_randomize.html" title="randomize" /> <link rel="refentry" href="/virtuoso/fn_rclose/" oldhref="fn_rclose.html" title="rclose" /> <link rel="refentry" href="/virtuoso/fn_regexp_match/" oldhref="fn_regexp_match.html" title="regexp_match" /> <link rel="refentry" href="/virtuoso/fn_regexp_parse/" oldhref="fn_regexp_parse.html" title="regexp_parse" /> <link rel="refentry" href="/virtuoso/fn_regexp_substr/" oldhref="fn_regexp_substr.html" title="regexp_substr" /> <link rel="refentry" href="/virtuoso/fn_rdf_audit_metadata/" oldhref="fn_rdf_audit_metadata.html" title="DB.DBA.RDF_AUDIT_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_security_audit/" oldhref="fn_rdf_graph_security_audit.html" title="DB.DBA.RDF_GRAPH_SECURITY_AUDIT" /> <link rel="refentry" href="/virtuoso/fn_rdf_default_user_perms_set/" oldhref="fn_rdf_default_user_perms_set.html" title="DB.DBA.RDF_DEFAULT_USER_PERMS_SET" /> <link rel="refentry" href="/virtuoso/fn_rdf_default_user_perms_del/" oldhref="fn_rdf_default_user_perms_del.html" title="DB.DBA.RDF_DEFAULT_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdf_backup_metadata/" oldhref="fn_rdf_backup_metadata.html" title="DB.DBA.RDF_BACKUP_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_void_store/" oldhref="fn_rdf_void_store.html" title="DB.DBA.RDF_VOID_STORE" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_stop/" oldhref="fn_rdf_load_stop.html" title="rdf_load_stop" /> <link rel="refentry" href="/virtuoso/fn_rdf_loader_run/" oldhref="fn_rdf_loader_run.html" title="rdf_loader_run" /> <link rel="refentry" href="/virtuoso/fn_ld_dir_all/" oldhref="fn_ld_dir_all.html" title="ld_dir_all" /> <link rel="refentry" href="/virtuoso/fn_rdf_restore_metadata/" oldhref="fn_rdf_restore_metadata.html" title="DB.DBA.RDF_RESTORE_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfxml_mt/" oldhref="fn_rdf_load_rdfxml_mt.html" title="DB.DBA.RDF_LOAD_RDFXML_MT" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfxml/" oldhref="fn_rdf_load_rdfxml.html" title="DB.DBA.RDF_LOAD_RDFXML" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfa/" oldhref="fn_rdf_load_rdfa.html" title="DB.DBA.RDF_LOAD_RDFA" /> <link rel="refentry" href="/virtuoso/fn_ld_dir/" oldhref="fn_ld_dir.html" title="ld_dir" /> <link rel="refentry" href="/virtuoso/fn_ttlp/" oldhref="fn_ttlp.html" title="DB.DBA.TTLP" /> <link rel="refentry" href="/virtuoso/fn_ttlp_mt/" oldhref="fn_ttlp_mt.html" title="DB.DBA.TTLP_MT" /> <link rel="refentry" href="/uda/mt/fn_ttlp_mt_local_file/" oldhref="fn_ttlp_mt_local_file.html" title="DB.DBA.TTLP_MT_LOCAL_FILE" /> <link rel="refentry" href="/virtuoso/fn_rdf_datatype_of_obj/" oldhref="fn_rdf_datatype_of_obj.html" title="DB.DBA.RDF_DATATYPE_OF_OBJ" /> <link rel="refentry" href="/virtuoso/fn_rdf_triples_to_rdf_xml_text/" oldhref="fn_rdf_triples_to_rdf_xml_text.html" title="DB.DBA.RDF_TRIPLES_TO_RDF_XML_TEXT" /> <link rel="refentry" href="/virtuoso/fn_rdf_triples_to_ttl/" oldhref="fn_rdf_triples_to_ttl.html" title="DB.DBA.RDF_TRIPLES_TO_TTL" /> <link rel="refentry" href="/virtuoso/fn_rdf_64bit_upgrade/" oldhref="fn_rdf_64bit_upgrade.html" title="DB.DBA.RDF_64BIT_UPGRADE" /> <link rel="refentry" href="/virtuoso/fn_rdf_view_sync_to_physical/" oldhref="fn_rdf_view_sync_to_physical.html" title="RDF_VIEW_SYNC_TO_PHYSICAL" /> <link rel="refentry" href="/virtuoso/fn_rdf_convert_rdfxml_to_ttl/" oldhref="fn_rdf_convert_rdfxml_to_ttl.html" title="DB.DBA.RDF_CONVERT_RDFXML_TO_TTL" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_group_create/" oldhref="fn_rdf_graph_group_create.html" title="DB.DBA.RDF_GRAPH_GROUP_CREATE" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_group_ins/" oldhref="fn_rdf_graph_group_ins.html" title="DB.DBA.RDF_GRAPH_GROUP_INS" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_set/" oldhref="fn_rdf_graph_user_perms_set.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_SET" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_get/" oldhref="fn_rdf_graph_user_perms_get.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_GET" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_del/" oldhref="fn_rdf_graph_user_perms_del.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdf_all_user_perms_del/" oldhref="fn_rdf_all_user_perms_del.html" title="DB.DBA.RDF_ALL_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdfs_rule_set/" oldhref="fn_rdfs_rule_set.html" title="rdfs_rule_set" /> <link rel="refentry" href="/virtuoso/fn_rdf_geo_fill/" oldhref="fn_rdf_geo_fill.html" title="DB.DBA.RDF_GEO_FILL" /> <link rel="refentry" href="/virtuoso/fn_rdf_geo_add/" oldhref="fn_rdf_geo_add.html" title="DB.DBA.RDF_GEO_ADD" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_collect_fp_list/" oldhref="fn_rdf_graph_collect_fp_list.html" title="DB.DBA.RDF_GRAPH_COLLECT_FP_LIST" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_diff/" oldhref="fn_rdf_graph_diff.html" title="DB.DBA.RDF_GRAPH_DIFF" /> <link rel="refentry" href="/virtuoso/fn_rdf_suo_apply_patch/" oldhref="fn_rdf_suo_apply_patch.html" title="DB.DBA.RDF_SUO_APPLY_PATCH" /> <link rel="refentry" href="/virtuoso/fn_rdf_suo_diff_ttl/" oldhref="fn_rdf_suo_diff_ttl.html" title="DB.DBA.RDF_SUO_DIFF_TTL" /> <link rel="refentry" href="/virtuoso/fn_sparql_rdb2rdf_codegen/" oldhref="fn_sparql_rdb2rdf_codegen.html" title="DB.DBA.SPARQL_RDB2RDF_CODEGEN" /> <link rel="refentry" href="/virtuoso/fn_sparql_rdb2rdf_list_tables/" oldhref="fn_sparql_rdb2rdf_list_tables.html" title="DB.DBA.SPARQL_RDB2RDF_LIST_TABLES" /> <link rel="refentry" href="/virtuoso/fn_sparql_select_known_graphs/" oldhref="fn_sparql_select_known_graphs.html" title="DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS" /> <link rel="refentry" href="/virtuoso/fn_rowvector_digit_sort/" oldhref="fn_rowvector_digit_sort.html" title="rowvector_digit_sort" /> <link rel="refentry" href="/virtuoso/fn_isref/" oldhref="fn_isref.html" title="IsRef" /> <link rel="refentry" href="/virtuoso/fn_sample/" oldhref="fn_sample.html" title="DB.DBA.SAMPLE" /> <link rel="refentry" href="/virtuoso/fn_group_concat/" oldhref="fn_group_concat.html" title="DB.DBA.GROUP_CONCAT" /> <link rel="refentry" href="/virtuoso/fn_group_concat_distinct/" oldhref="fn_group_concat_distinct.html" title="DB.DBA.GROUP_CONCAT_DISTINCT" /> <link rel="refentry" href="/virtuoso/fn_group_digest/" oldhref="fn_group_digest.html" title="DB.DBA.GROUP_DIGEST" /> <link rel="refentry" href="/virtuoso/fn_http_nt_triple/" oldhref="fn_http_nt_triple.html" title="http_nt_triple" /> <link rel="refentry" href="/virtuoso/fn_http_ttl_triple/" oldhref="fn_http_ttl_triple.html" title="http_ttl_triple" /> <link rel="refentry" href="/virtuoso/fn_ann_phrase_class_add/" oldhref="fn_ann_phrase_class_add.html" title="DB.DBA.ANN_PHRASE_CLASS_ADD" /> <link rel="refentry" href="/virtuoso/fn_ann_phrase_class_del/" oldhref="fn_ann_phrase_class_del.html" title="DB.DBA.ANN_PHRASE_CLASS_DEL" /> <link rel="refentry" href="/virtuoso/fn_ap_build_match_list/" oldhref="fn_ap_build_match_list.html" title="AP_BUILD_MATCH_LIST" /> <link rel="refentry" href="/virtuoso/fn_ap_add_phrases/" oldhref="fn_ap_add_phrases.html" title="AP_ADD_PHRASES" /> <link rel="refentry" href="/virtuoso/fn_iri_split/" oldhref="fn_iri_split.html" title="iri_split" /> <link rel="refentry" href="/virtuoso/fn___xml_get_ns_prefix/" oldhref="fn___xml_get_ns_prefix.html" title="__xml_get_ns_prefix" /> <link rel="refentry" href="/virtuoso/fn___xml_get_ns_uri/" oldhref="fn___xml_get_ns_uri.html" title="__xml_get_ns_uri" /> <link rel="refentry" href="/virtuoso/fn___xml_ns_uname/" oldhref="fn___xml_ns_uname.html" title="__xml_ns_uname" /> <link rel="refentry" href="/virtuoso/fn___xml_ns_iristr/" oldhref="fn___xml_ns_iristr.html" title="__xml_ns_iristr" /> <link rel="refentry" href="/virtuoso/fn___xml_nsexpand_iristr/" oldhref="fn___xml_nsexpand_iristr.html" title="__xml_nsexpand_iristr" /> <link rel="refentry" href="/virtuoso/fn_sparql_eval/" oldhref="fn_sparql_eval.html" title="DB.DBA.SPARQL_EVAL" /> <link rel="refentry" href="/virtuoso/fn_sparql_eval_to_array/" oldhref="fn_sparql_eval_to_array.html" title="DB.DBA.SPARQL_EVAL_TO_ARRAY" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec/" oldhref="fn_sparql_rexec.html" title="DB.DBA.SPARQL_REXEC" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec_to_array/" oldhref="fn_sparql_rexec_to_array.html" title="DB.DBA.SPARQL_REXEC_TO_ARRAY" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec_with_meta/" oldhref="fn_sparql_rexec_with_meta.html" title="DB.DBA.SPARQL_REXEC_WITH_META" /> <link rel="refentry" href="/virtuoso/fn_rdf_regex/" oldhref="fn_rdf_regex.html" title="DB.DBA.RDF_REGEX" /> <link rel="refentry" href="/virtuoso/fn_rdf_langmatches/" oldhref="fn_rdf_langmatches.html" title="DB.DBA.RDF_LANGMATCHES" /> <link rel="refentry" href="/virtuoso/fn_rdf_ttl2hash/" oldhref="fn_rdf_ttl2hash.html" title="DB.DBA.RDF_TTL2HASH" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri/" oldhref="fn_rdf_quad_uri.html" title="DB.DBA.RDF_QUAD_URI" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri_l/" oldhref="fn_rdf_quad_uri_l.html" title="DB.DBA.RDF_QUAD_URI_L" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri_l_typed/" oldhref="fn_rdf_quad_uri_l_typed.html" title="DB.DBA.RDF_QUAD_URI_L_TYPED" /> <link rel="refentry" href="/virtuoso/fn_regexp_replace/" oldhref="fn_regexp_replace.html" title="regexp_replace" /> <link rel="refentry" href="/virtuoso/fn_regexp_instr/" oldhref="fn_regexp_instr.html" title="regexp_instr" /> <link rel="refentry" href="/virtuoso/fn_regexp_like/" oldhref="fn_regexp_like.html" title="regexp_like" /> <link rel="refentry" href="/virtuoso/fn_registry_get/" oldhref="fn_registry_get.html" title="registry_get" /> <link rel="refentry" href="/virtuoso/fn_registry_get_all/" oldhref="fn_registry_get_all.html" title="registry_get_all" /> <link rel="refentry" href="/virtuoso/fn_registry_name_is_protected/" oldhref="fn_registry_name_is_protected.html" title="registry_name_is_protected" /> <link rel="refentry" href="/virtuoso/fn_registry_set/" oldhref="fn_registry_set.html" title="registry_set" /> <link rel="refentry" href="/virtuoso/fn_registry_remove/" oldhref="fn_registry_remove.html" title="registry_remove" /> <link rel="refentry" href="/virtuoso/fn_repeat/" oldhref="fn_repeat.html" title="repeat" /> <link rel="refentry" href="/virtuoso/fn_replace/" oldhref="fn_replace.html" title="replace" /> <link rel="refentry" href="/virtuoso/fn_replay/" oldhref="fn_replay.html" title="replay" /> <link rel="refentry" href="/virtuoso/fn_repl_disconnect/" oldhref="fn_repl_disconnect.html" title="repl_disconnect" /> <link rel="refentry" href="/virtuoso/fn_repl_grant/" oldhref="fn_repl_grant.html" title="REPL_GRANT" /> <link rel="refentry" href="/virtuoso/fn_repl_init_copy/" oldhref="fn_repl_init_copy.html" title="REPL_INIT_COPY" /> <link rel="refentry" href="/virtuoso/fn_repl_new_log/" oldhref="fn_repl_new_log.html" title="repl_new_log" /> <link rel="refentry" href="/virtuoso/fn_repl_publish/" oldhref="fn_repl_publish.html" title="REPL_PUBLISH" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_add/" oldhref="fn_repl_pub_add.html" title="REPL_PUB_ADD" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_init_image/" oldhref="fn_repl_pub_init_image.html" title="REPL_PUB_INIT_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_remove/" oldhref="fn_repl_pub_remove.html" title="REPL_PUB_REMOVE" /> <link rel="refentry" href="/virtuoso/fn_repl_revoke/" oldhref="fn_repl_revoke.html" title="REPL_REVOKE" /> <link rel="refentry" href="/virtuoso/fn_repl_sched_init/" oldhref="fn_repl_sched_init.html" title="REPL_SCHED_INIT" /> <link rel="refentry" href="/virtuoso/fn_repl_server/" oldhref="fn_repl_server.html" title="REPL_SERVER" /> <link rel="refentry" href="/virtuoso/fn_repl_server_rename/" oldhref="fn_repl_server_rename.html" title="repl_server_rename" /> <link rel="refentry" href="/virtuoso/fn_repl_stat/" oldhref="fn_repl_stat.html" title="REPL_STAT" /> <link rel="refentry" href="/virtuoso/fn_repl_status/" oldhref="fn_repl_status.html" title="repl_status" /> <link rel="refentry" href="/virtuoso/fn_repl_subscribe/" oldhref="fn_repl_subscribe.html" title="REPL_SUBSCRIBE" /> <link rel="refentry" href="/virtuoso/fn_repl_sync/" oldhref="fn_repl_sync.html" title="repl_sync" /> <link rel="refentry" href="/virtuoso/fn_repl_sync_all/" oldhref="fn_repl_sync_all.html" title="repl_sync_all" /> <link rel="refentry" href="/virtuoso/fn_repl_text/" oldhref="fn_repl_text.html" title="repl_text" /> <link rel="refentry" href="/virtuoso/fn_repl_this_server/" oldhref="fn_repl_this_server.html" title="repl_this_server" /> <link rel="refentry" href="/virtuoso/fn_repl_unpublish/" oldhref="fn_repl_unpublish.html" title="REPL_UNPUBLISH" /> <link rel="refentry" href="/virtuoso/fn_repl_unsubscribe/" oldhref="fn_repl_unsubscribe.html" title="REPL_UNSUBSCRIBE" /> <link rel="refentry" href="/virtuoso/fn_repl_purge/" oldhref="fn_repl_purge.html" title="repl_purge" /> <link rel="refentry" href="/virtuoso/fn_repl_create_snapshot_pub/" oldhref="fn_repl_create_snapshot_pub.html" title="REPL_CREATE_SNAPSHOT_PUB" /> <link rel="refentry" href="/virtuoso/fn_repl_create_snapshot_sub/" oldhref="fn_repl_create_snapshot_sub.html" title="REPL_CREATE_SNAPSHOT_SUB" /> <link rel="refentry" href="/virtuoso/fn_repl_drop_snapshot_sub/" oldhref="fn_repl_drop_snapshot_sub.html" title="REPL_DROP_SNAPSHOT_SUB" /> <link rel="refentry" href="/virtuoso/fn_repl_drop_snapshot_pub/" oldhref="fn_repl_drop_snapshot_pub.html" title="REPL_DROP_SNAPSHOT_PUB" /> <link rel="refentry" href="/virtuoso/fn_repl_init_snapshot/" oldhref="fn_repl_init_snapshot.html" title="REPL_INIT_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_repl_update_snapshot/" oldhref="fn_repl_update_snapshot.html" title="REPL_UPDATE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_repl_snp_server/" oldhref="fn_repl_snp_server.html" title="REPL_SNP_SERVER" /> <link rel="refentry" href="/virtuoso/fn_repl_server_name/" oldhref="fn_repl_server_name.html" title="REPL_SERVER_NAME" /> <link rel="refentry" href="/virtuoso/fn_repl_add_cr/" oldhref="fn_repl_add_cr.html" title="REPL_ADD_CR" /> <link rel="refentry" href="/virtuoso/fn_repl_add_dav_cr/" oldhref="fn_repl_add_dav_cr.html" title="REPL_ADD_DAV_CR" /> <link rel="refentry" href="/virtuoso/fn_repl_add_snapshot_cr/" oldhref="fn_repl_add_snapshot_cr.html" title="REPL_ADD_SNAPSHOT_CR" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_start/" oldhref="fn_rdf_repl_start.html" title="RDF_REPL_START" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_stop/" oldhref="fn_rdf_repl_stop.html" title="RDF_REPL_STOP" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_sync/" oldhref="fn_rdf_repl_sync.html" title="RDF_REPL_SYNC" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_graph_ins/" oldhref="fn_rdf_repl_graph_ins.html" title="RDF_REPL_GRAPH_INS" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_graph_del/" oldhref="fn_rdf_repl_graph_del.html" title="RDF_REPL_GRAPH_DEL" /> <link rel="refentry" href="/virtuoso/fn_result/" oldhref="fn_result.html" title="result" /> <link rel="refentry" href="/virtuoso/fn_result_names/" oldhref="fn_result_names.html" title="result_names" /> <link rel="refentry" href="/virtuoso/fn_rexecute/" oldhref="fn_rexecute.html" title="rexecute" /> <link rel="refentry" href="/virtuoso/fn_rstmtexec/" oldhref="fn_rstmtexec.html" title="rstmtexec" /> <link rel="refentry" href="/virtuoso/fn_right/" oldhref="fn_right.html" title="right" /> <link rel="refentry" href="/virtuoso/fn_rmoreresults/" oldhref="fn_rmoreresults.html" title="rmoreresults" /> <link rel="refentry" href="/virtuoso/fn_rnd/" oldhref="fn_rnd.html" title="rnd" /> <link rel="refentry" href="/virtuoso/fn_rnext/" oldhref="fn_rnext.html" title="rnext" /> <link rel="refentry" href="/virtuoso/fn_row_count/" oldhref="fn_row_count.html" title="row_count" /> <link rel="refentry" href="/virtuoso/fn_rtrim/" oldhref="fn_rtrim.html" title="rtrim" /> <link rel="refentry" href="/virtuoso/fn_search_excerpt/" oldhref="fn_search_excerpt.html" title="search_excerpt" /> <link rel="refentry" href="/virtuoso/fn_second/" oldhref="fn_second.html" title="second" /> <link rel="refentry" href="/virtuoso/fn_sequence_get_all/" oldhref="fn_sequence_get_all.html" title="sequence_get_all" /> <link rel="refentry" href="/virtuoso/fn_sequence_next/" oldhref="fn_sequence_next.html" title="sequence_next" /> <link rel="refentry" href="/virtuoso/fn_sequence_remove/" oldhref="fn_sequence_remove.html" title="sequence_remove" /> <link rel="refentry" href="/virtuoso/fn_sequence_set/" oldhref="fn_sequence_set.html" title="sequence_set" /> <link rel="refentry" href="/virtuoso/fn_serialize/" oldhref="fn_serialize.html" title="serialize" /> <link rel="refentry" href="/virtuoso/fn_serialize_to_utf8_xml/" oldhref="fn_serialize_to_utf8_xml.html" title="serialize_to_UTF8_xml" /> <link rel="refentry" href="/virtuoso/fn_serv_queue_top/" oldhref="fn_serv_queue_top.html" title="SERV_QUEUE_TOP" /> <link rel="refentry" href="/virtuoso/fn_ses_connect/" oldhref="fn_ses_connect.html" title="ses_connect" /> <link rel="refentry" href="/virtuoso/fn_ses_disconnect/" oldhref="fn_ses_disconnect.html" title="ses_disconnect" /> <link rel="refentry" href="/virtuoso/fn_ses_read_line/" oldhref="fn_ses_read_line.html" title="ses_read_line" /> <link rel="refentry" href="/virtuoso/fn_ses_write/" oldhref="fn_ses_write.html" title="ses_write" /> <link rel="refentry" href="/virtuoso/fn_set_row_count/" oldhref="fn_set_row_count.html" title="set_row_count" /> <link rel="refentry" href="/virtuoso/fn_set_user_id/" oldhref="fn_set_user_id.html" title="set_user_id" /> <link rel="refentry" href="/virtuoso/fn_set_identity_column/" oldhref="fn_set_identity_column.html" title="set_identity_column" /> <link rel="refentry" href="/virtuoso/fn_sign/" oldhref="fn_sign.html" title="sign" /> <link rel="refentry" href="/virtuoso/fn_signal/" oldhref="fn_signal.html" title="signal" /> <link rel="refentry" href="/virtuoso/fn_sinv_create_key_mapping/" oldhref="fn_sinv_create_key_mapping.html" title="sinv_create_key_mapping" /> <link rel="refentry" href="/virtuoso/fn_sinv_create_inverse/" oldhref="fn_sinv_create_inverse.html" title="sinv_create_inverse" /> <link rel="refentry" href="/virtuoso/fn_sinv_drop_inverse/" oldhref="fn_sinv_drop_inverse.html" title="sinv_drop_inverse" /> <link rel="refentry" href="/virtuoso/fn_smime_sign/" oldhref="fn_smime_sign.html" title="smime_sign" /> <link rel="refentry" href="/virtuoso/fn_smime_verify/" oldhref="fn_smime_verify.html" title="smime_verify" /> <link rel="refentry" href="/virtuoso/fn_smime_encrypt/" oldhref="fn_smime_encrypt.html" title="smime_encrypt" /> <link rel="refentry" href="/virtuoso/fn_smime_decrypt/" oldhref="fn_smime_decrypt.html" title="smime_decrypt" /> <link rel="refentry" href="/virtuoso/fn_smtp_send/" oldhref="fn_smtp_send.html" title="smtp_send" /> <link rel="refentry" href="/virtuoso/fn_soap_box_xml_entity/" oldhref="fn_soap_box_xml_entity.html" title="soap_box_xml_entity" /> <link rel="refentry" href="/virtuoso/fn_soap_dt_define/" oldhref="fn_soap_dt_define.html" title="soap_dt_define" /> <link rel="refentry" href="/virtuoso/fn_soap_call/" oldhref="fn_soap_call.html" title="soap_call" /> <link rel="refentry" href="/virtuoso/fn_soap_client/" oldhref="fn_soap_client.html" title="soap_client" /> <link rel="refentry" href="/virtuoso/fn_soap_make_error/" oldhref="fn_soap_make_error.html" title="soap_make_error" /> <link rel="refentry" href="/virtuoso/fn_soap_print_box/" oldhref="fn_soap_print_box.html" title="soap_print_box" /> <link rel="refentry" href="/virtuoso/fn_soap_sdl/" oldhref="fn_soap_sdl.html" title="soap_sdl" /> <link rel="refentry" href="/virtuoso/fn_soap_server/" oldhref="fn_soap_server.html" title="soap_server" /> <link rel="refentry" href="/virtuoso/fn_soap_wsdl/" oldhref="fn_soap_wsdl.html" title="soap_wsdl" /> <link rel="refentry" href="/virtuoso/fn_soap_wsdl_import/" oldhref="fn_soap_wsdl_import.html" title="soap_wsdl_import" /> <link rel="refentry" href="/virtuoso/fn_soap_box_structure/" oldhref="fn_soap_box_structure.html" title="soap_box_structure" /> <link rel="refentry" href="/virtuoso/fn_soap_current_url/" oldhref="fn_soap_current_url.html" title="soap_current_url" /> <link rel="refentry" href="/virtuoso/fn_space/" oldhref="fn_space.html" title="space" /> <link rel="refentry" href="/virtuoso/fn_split_and_decode/" oldhref="fn_split_and_decode.html" title="split_and_decode" /> <link rel="refentry" href="/virtuoso/fn_sprintf/" oldhref="fn_sprintf.html" title="sprintf" /> <link rel="refentry" href="/virtuoso/fn_sprintf_inverse/" oldhref="fn_sprintf_inverse.html" title="sprintf_inverse" /> <link rel="refentry" href="/virtuoso/fn_sprintf_iri/" oldhref="fn_sprintf_iri.html" title="sprintf_iri" /> <link rel="refentry" href="/virtuoso/fn_sprintf_iri_or_null/" oldhref="fn_sprintf_iri_or_null.html" title="sprintf_iri_or_null" /> <link rel="refentry" href="/virtuoso/fn_sprintf_or_null/" oldhref="fn_sprintf_or_null.html" title="sprintf_or_null" /> <link rel="refentry" href="/virtuoso/fn_sql_columns/" oldhref="fn_sql_columns.html" title="sql_columns" /> <link rel="refentry" href="/virtuoso/fn_sql_data_sources/" oldhref="fn_sql_data_sources.html" title="sql_data_sources" /> <link rel="refentry" href="/virtuoso/fn_sql_gettypeinfo/" oldhref="fn_sql_gettypeinfo.html" title="sql_gettypeinfo" /> <link rel="refentry" href="/virtuoso/fn_sql_primary_keys/" oldhref="fn_sql_primary_keys.html" title="sql_primary_keys" /> <link rel="refentry" href="/virtuoso/fn_sql_statistics/" oldhref="fn_sql_statistics.html" title="sql_statistics" /> <link rel="refentry" href="/virtuoso/fn_sql_tables/" oldhref="fn_sql_tables.html" title="sql_tables" /> <link rel="refentry" href="/virtuoso/fn_sql_special_columns/" oldhref="fn_sql_special_columns.html" title="sql_special_columns" /> <link rel="refentry" href="/virtuoso/fn_sql_procedures/" oldhref="fn_sql_procedures.html" title="sql_procedures" /> <link rel="refentry" href="/virtuoso/fn_sql_write_private_profile_string/" oldhref="fn_sql_write_private_profile_string.html" title="sql_write_private_profile_string" /> <link rel="refentry" href="/virtuoso/fn_sql_get_private_profile_string/" oldhref="fn_sql_get_private_profile_string.html" title="sql_get_private_profile_string" /> <link rel="refentry" href="/virtuoso/fn_sql_config_data_sources/" oldhref="fn_sql_config_data_sources.html" title="sql_config_data_sources" /> <link rel="refentry" href="/virtuoso/fn_sql_get_installed_drivers/" oldhref="fn_sql_get_installed_drivers.html" title="sql_get_installed_drivers" /> <link rel="refentry" href="/virtuoso/fn_sql_remove_dsn_from_ini/" oldhref="fn_sql_remove_dsn_from_ini.html" title="sql_remove_dsn_from_ini" /> <link rel="refentry" href="/virtuoso/fn_sql_transact/" oldhref="fn_sql_transact.html" title="sql_transact" /> <link rel="refentry" href="/virtuoso/fn_sql_write_file_dsn/" oldhref="fn_sql_write_file_dsn.html" title="sql_write_file_dsn" /> <link rel="refentry" href="/virtuoso/fn_sql_driver_connect/" oldhref="fn_sql_driver_connect.html" title="sql_driver_connect" /> <link rel="refentry" href="/virtuoso/fn_sqrt/" oldhref="fn_sqrt.html" title="sqrt" /> <link rel="refentry" href="/virtuoso/fn_status/" oldhref="fn_status.html" title="status" /> <link rel="refentry" href="/virtuoso/fn_key_estimate/" oldhref="fn_key_estimate.html" title="key_estimate" /> <link rel="refentry" href="/virtuoso/fn_strcasestr/" oldhref="fn_strcasestr.html" title="strcasestr" /> <link rel="refentry" href="/virtuoso/fn_strchr/" oldhref="fn_strchr.html" title="strchr" /> <link rel="refentry" href="/virtuoso/fn_stringdate/" oldhref="fn_stringdate.html" title="stringdate" /> <link rel="refentry" href="/virtuoso/fn_stringtime/" oldhref="fn_stringtime.html" title="stringtime" /> <link rel="refentry" href="/virtuoso/fn_string_output/" oldhref="fn_string_output.html" title="string_output" /> <link rel="refentry" href="/virtuoso/fn_string_output_flush/" oldhref="fn_string_output_flush.html" title="string_output_flush" /> <link rel="refentry" href="/virtuoso/fn_string_output_gz_compress/" oldhref="fn_string_output_gz_compress.html" title="string_output_gz_compress" /> <link rel="refentry" href="/virtuoso/fn_string_output_string/" oldhref="fn_string_output_string.html" title="string_output_string" /> <link rel="refentry" href="/virtuoso/fn_string_to_file/" oldhref="fn_string_to_file.html" title="string_to_file" /> <link rel="refentry" href="/virtuoso/fn_strrchr/" oldhref="fn_strrchr.html" title="strrchr" /> <link rel="refentry" href="/virtuoso/fn_strstr/" oldhref="fn_strstr.html" title="strstr" /> <link rel="refentry" href="/virtuoso/fn_subseq/" oldhref="fn_subseq.html" title="subseq" /> <link rel="refentry" href="/virtuoso/fn_substring/" oldhref="fn_substring.html" title="substring" /> <link rel="refentry" href="/virtuoso/fn_sub_schedule/" oldhref="fn_sub_schedule.html" title="sub_schedule" /> <link rel="refentry" href="/virtuoso/fn_system/" oldhref="fn_system.html" title="system" /> <link rel="refentry" href="/virtuoso/fn_uptime/" oldhref="fn_uptime.html" title="uptime" /> <link rel="refentry" href="/virtuoso/fn_sys_db_stat/" oldhref="fn_sys_db_stat.html" title="SYS_DB_STAT" /> <link rel="refentry" href="/virtuoso/fn_sys_lockdown/" oldhref="fn_sys_lockdown.html" title="sys_lockdown" /> <link rel="refentry" href="/virtuoso/fn_sys_stat/" oldhref="fn_sys_stat.html" title="sys_stat" /> <link rel="refentry" href="/virtuoso/fn_sys_stat_analyze/" oldhref="fn_sys_stat_analyze.html" title="sys_stat_analyze" /> <link rel="refentry" href="/virtuoso/fn_sys_stat_histogram/" oldhref="fn_sys_stat_histogram.html" title="sys_stat_histogram" /> <link rel="refentry" href="/virtuoso/fn_table_set_policy/" oldhref="fn_table_set_policy.html" title="table_set_policy" /> <link rel="refentry" href="/virtuoso/fn_table_drop_policy/" oldhref="fn_table_drop_policy.html" title="table_drop_policy" /> <link rel="refentry" href="/virtuoso/fn_strcontains/" oldhref="fn_strcontains.html" title="strcontains" /> <link rel="refentry" href="/virtuoso/fn_starts_with/" oldhref="fn_starts_with.html" title="starts_with" /> <link rel="refentry" href="/virtuoso/fn_ends_with/" oldhref="fn_ends_with.html" title="ends_with" /> <link rel="refentry" href="/virtuoso/fn_tcpip_gethostbyname/" oldhref="fn_tcpip_gethostbyname.html" title="tcpip_gethostbyname" /> <link rel="refentry" href="/virtuoso/fn_tcpip_gethostbyaddr/" oldhref="fn_tcpip_gethostbyaddr.html" title="tcpip_gethostbyaddr" /> <link rel="refentry" href="/virtuoso/fn_tmp_file_name/" oldhref="fn_tmp_file_name.html" title="tmp_file_name" /> <link rel="refentry" href="/virtuoso/fn_tidy_html/" oldhref="fn_tidy_html.html" title="tidy_html" /> <link rel="refentry" href="/virtuoso/fn_tidy_list_errors/" oldhref="fn_tidy_list_errors.html" title="tidy_list_errors" /> <link rel="refentry" href="/virtuoso/fn_timezone/" oldhref="fn_timezone.html" title="timezone" /> <link rel="refentry" href="/virtuoso/fn_trace_off/" oldhref="fn_trace_off.html" title="trace_off" /> <link rel="refentry" href="/virtuoso/fn_trace_on/" oldhref="fn_trace_on.html" title="trace_on" /> <link rel="refentry" href="/virtuoso/fn_trace_status/" oldhref="fn_trace_status.html" title="trace_status" /> <link rel="refentry" href="/uda/ee/fn_tree_md5/" oldhref="fn_tree_md5.html" title="tree_md5" /> <link rel="refentry" href="/virtuoso/fn_hs_resolve/" oldhref="fn_hs_resolve.html" title="HS_Resolve" /> <link rel="refentry" href="/virtuoso/fn_acos/" oldhref="fn_acos.html" title="trigonometric" /> <link rel="refentry" href="/virtuoso/fn_trim/" oldhref="fn_trim.html" title="trim" /> <link rel="refentry" href="/virtuoso/fn_txn_error/" oldhref="fn_txn_error.html" title="txn_error" /> <link rel="refentry" href="/virtuoso/fn_txn_killall/" oldhref="fn_txn_killall.html" title="txn_killall" /> <link rel="refentry" href="/virtuoso/fn_ucase/" oldhref="fn_ucase.html" title="ucase" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_binding/" oldhref="me_uddi_delete_binding.html" title="uddi_delete_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_business/" oldhref="me_uddi_delete_business.html" title="uddi_delete_business" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_service/" oldhref="me_uddi_delete_service.html" title="uddi_delete_service" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_tmodel/" oldhref="me_uddi_delete_tmodel.html" title="uddi_delete_tModel" /> <link rel="refentry" href="/virtuoso/me_uddi_discard_authtoken/" oldhref="me_uddi_discard_authtoken.html" title="uddi_discard_authToken" /> <link rel="refentry" href="/virtuoso/me_uddi_find_binding/" oldhref="me_uddi_find_binding.html" title="uddi_find_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_find_business/" oldhref="me_uddi_find_business.html" title="uddi_find_business" /> <link rel="refentry" href="/virtuoso/me_uddi_find_service/" oldhref="me_uddi_find_service.html" title="uddi_find_service" /> <link rel="refentry" href="/virtuoso/me_uddi_find_tmodel/" oldhref="me_uddi_find_tmodel.html" title="uddi_find_tModel" /> <link rel="refentry" href="/virtuoso/me_uddi_get_authtoken/" oldhref="me_uddi_get_authtoken.html" title="uddi_get_authToken" /> <link rel="refentry" href="/virtuoso/me_uddi_get_bindingdetail/" oldhref="me_uddi_get_bindingdetail.html" title="uddi_get_bindingDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_businessdetail/" oldhref="me_uddi_get_businessdetail.html" title="uddi_get_businessDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_businessdetailext/" oldhref="me_uddi_get_businessdetailext.html" title="uddi_get_businessDetailExt" /> <link rel="refentry" href="/virtuoso/me_uddi_get_registeredinfo/" oldhref="me_uddi_get_registeredinfo.html" title="uddi_get_registeredInfo" /> <link rel="refentry" href="/virtuoso/me_uddi_get_servicedetail/" oldhref="me_uddi_get_servicedetail.html" title="uddi_get_serviceDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_tmodeldetail/" oldhref="me_uddi_get_tmodeldetail.html" title="uddi_get_tModelDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_save_binding/" oldhref="me_uddi_save_binding.html" title="uddi_save_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_save_business/" oldhref="me_uddi_save_business.html" title="uddi_save_business" /> <link rel="refentry" href="/virtuoso/me_uddi_save_service/" oldhref="me_uddi_save_service.html" title="uddi_save_service" /> <link rel="refentry" href="/virtuoso/me_uddi_save_tmodel/" oldhref="me_uddi_save_tmodel.html" title="uddi_save_tModel" /> <link rel="refentry" href="/virtuoso/fn_udt_defines_field/" oldhref="fn_udt_defines_field.html" title="udt_defines_field" /> <link rel="refentry" href="/virtuoso/fn_udt_get/" oldhref="fn_udt_get.html" title="udt_get" /> <link rel="refentry" href="/virtuoso/fn_udt_implements_method/" oldhref="fn_udt_implements_method.html" title="udt_implements_method" /> <link rel="refentry" href="/virtuoso/fn_udt_instance_of/" oldhref="fn_udt_instance_of.html" title="udt_instance_of" /> <link rel="refentry" href="/virtuoso/fn_udt_set/" oldhref="fn_udt_set.html" title="udt_set" /> <link rel="refentry" href="/virtuoso/fn_unimport_clr/" oldhref="fn_unimport_clr.html" title="unimport_clr" /> <link rel="refentry" href="/virtuoso/fn_unimport_jar/" oldhref="fn_unimport_jar.html" title="unimport_jar" /> <link rel="refentry" href="/virtuoso/fn_updatexml/" oldhref="fn_updatexml.html" title="updateXML" /> <link rel="refentry" href="/virtuoso/fn_upper/" oldhref="fn_upper.html" title="upper" /> <link rel="refentry" href="/virtuoso/fn_user_change_password/" oldhref="fn_user_change_password.html" title="USER_CHANGE_PASSWORD" /> <link rel="refentry" href="/virtuoso/fn_user_create/" oldhref="fn_user_create.html" title="USER_CREATE" /> <link rel="refentry" href="/virtuoso/fn_user_drop/" oldhref="fn_user_drop.html" title="USER_DROP" /> <link rel="refentry" href="/virtuoso/fn_user_get_option/" oldhref="fn_user_get_option.html" title="USER_GET_OPTION" /> <link rel="refentry" href="/virtuoso/fn_user_grant_role/" oldhref="fn_user_grant_role.html" title="USER_GRANT_ROLE" /> <link rel="refentry" href="/virtuoso/fn_user_revoke_role/" oldhref="fn_user_revoke_role.html" title="USER_REVOKE_ROLE" /> <link rel="refentry" href="/virtuoso/fn_user_role_create/" oldhref="fn_user_role_create.html" title="USER_ROLE_CREATE" /> <link rel="refentry" href="/virtuoso/fn_user_role_drop/" oldhref="fn_user_role_drop.html" title="USER_ROLE_DROP" /> <link rel="refentry" href="/virtuoso/fn_user_set_qualifier/" oldhref="fn_user_set_qualifier.html" title="USER_SET_QUALIFIER" /> <link rel="refentry" href="/virtuoso/fn_user_set_option/" oldhref="fn_user_set_option.html" title="USER_SET_OPTION" /> <link rel="refentry" href="/virtuoso/fn_user_set_password/" oldhref="fn_user_set_password.html" title="user_set_password" /> <link rel="refentry" href="/virtuoso/fn_username/" oldhref="fn_username.html" title="username" /> <link rel="refentry" href="/virtuoso/fn_uudecode/" oldhref="fn_uudecode.html" title="uudecode" /> <link rel="refentry" href="/virtuoso/fn_uuencode/" oldhref="fn_uuencode.html" title="uuencode" /> <link rel="refentry" href="/virtuoso/fn_uuvalidate/" oldhref="fn_uuvalidate.html" title="uuvalidate" /> <link rel="refentry" href="/virtuoso/fn_user_key_store/" oldhref="fn_user_key_store.html" title="USER_KEY_STORE" /> <link rel="refentry" href="/virtuoso/fn_vad_check/" oldhref="fn_vad_check.html" title="VAD_CHECK" /> <link rel="refentry" href="/virtuoso/fn_vad_check_installability/" oldhref="fn_vad_check_installability.html" title="VAD_CHECK_INSTALLABILITY" /> <link rel="refentry" href="/virtuoso/fn_vad_check_uninstallability/" oldhref="fn_vad_check_uninstallability.html" title="VAD_CHECK_UNINSTALLABILITY" /> <link rel="refentry" href="/virtuoso/fn_vad_fail_check/" oldhref="fn_vad_fail_check.html" title="VAD_FAIL_CHECK" /> <link rel="refentry" href="/virtuoso/fn_vad_install/" oldhref="fn_vad_install.html" title="VAD_INSTALL" /> <link rel="refentry" href="/virtuoso/fn_vad_load_file/" oldhref="fn_vad_load_file.html" title="VAD_LOAD_FILE" /> <link rel="refentry" href="/virtuoso/fn_vad_load_sql_file/" oldhref="fn_vad_load_sql_file.html" title="VAD_LOAD_SQL_FILE" /> <link rel="refentry" href="/virtuoso/fn_vad_pack/" oldhref="fn_vad_pack.html" title="VAD_PACK" /> <link rel="refentry" href="/virtuoso/fn_vad_safe_exec/" oldhref="fn_vad_safe_exec.html" title="VAD_SAFE_EXEC" /> <link rel="refentry" href="/virtuoso/fn_vad_uninstall/" oldhref="fn_vad_uninstall.html" title="VAD_UNINSTALL" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_data_source/" oldhref="fn_vd_remote_data_source.html" title="vd_remote_data_source" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_proc_wrapper/" oldhref="fn_vd_remote_proc_wrapper.html" title="vd_remote_proc_wrapper" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_table/" oldhref="fn_vd_remote_table.html" title="vd_remote_table" /> <link rel="refentry" href="/virtuoso/fn_vd_statistics/" oldhref="fn_vd_statistics.html" title="vd_statistics" /> <link rel="refentry" href="/virtuoso/fn_vdd_disconnect_data_source/" oldhref="fn_vdd_disconnect_data_source.html" title="vdd_disconnect_data_source" /> <link rel="refentry" href="/virtuoso/fn_vdd_measure_rpc_time/" oldhref="fn_vdd_measure_rpc_time.html" title="vdd_measure_rpc_time" /> <link rel="refentry" href="/virtuoso/fn_vector/" oldhref="fn_vector.html" title="vector" /> <link rel="refentry" href="/virtuoso/fn_vector_concat/" oldhref="fn_vector_concat.html" title="vector_concat" /> <link rel="refentry" href="/virtuoso/fn_vhost_define/" oldhref="fn_vhost_define.html" title="VHOST_DEFINE" /> <link rel="refentry" href="/virtuoso/fn_vhost_remove/" oldhref="fn_vhost_remove.html" title="VHOST_REMOVE" /> <link rel="refentry" href="/virtuoso/fn_virtuoso_ini_path/" oldhref="fn_virtuoso_ini_path.html" title="virtuoso_ini_path" /> <link rel="refentry" href="/virtuoso/fn_server_root/" oldhref="fn_server_root.html" title="server_root" /> <link rel="refentry" href="/virtuoso/fn_vsp_calculate_digest/" oldhref="fn_vsp_calculate_digest.html" title="vsp_calculate_digest" /> <link rel="refentry" href="/virtuoso/fn_vt_batch/" oldhref="fn_vt_batch.html" title="vt_batch" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_d_id/" oldhref="fn_vt_batch_d_id.html" title="vt_batch_d_id" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_feed/" oldhref="fn_vt_batch_feed.html" title="vt_batch_feed" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_feed_offband/" oldhref="fn_vt_batch_feed_offband.html" title="vt_batch_feed_offband" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_update/" oldhref="fn_vt_batch_update.html" title="VT_BATCH_UPDATE" /> <link rel="refentry" href="/virtuoso/fn_vt_create_text_index/" oldhref="fn_vt_create_text_index.html" title="vt_create_text_index" /> <link rel="refentry" href="/virtuoso/fn_vt_drop_ftt/" oldhref="fn_vt_drop_ftt.html" title="VT_DROP_FTT" /> <link rel="refentry" href="/virtuoso/fn_vt_is_noise/" oldhref="fn_vt_is_noise.html" title="vt_is_noise" /> <link rel="refentry" href="/virtuoso/fn_week/" oldhref="fn_week.html" title="week" /> <link rel="refentry" href="/virtuoso/fn_wsdl_import_udt/" oldhref="fn_wsdl_import_udt.html" title="wsdl_import_udt" /> <link rel="refentry" href="/virtuoso/fn_wst_cli/" oldhref="fn_wst_cli.html" title="wst_cli" /> <link rel="refentry" href="/virtuoso/fn_user_key_load/" oldhref="fn_user_key_load.html" title="USER_KEY_LOAD" /> <link rel="refentry" href="/virtuoso/fn_dsig_template_ext/" oldhref="fn_dsig_template_ext.html" title="dsig_template_ext" /> <link rel="refentry" href="/virtuoso/fn_x509_certificate_verify/" oldhref="fn_x509_certificate_verify.html" title="x509_certificate_verify" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_certificate_serialize/" oldhref="fn_xenc_x509_certificate_serialize.html" title="xenc_X509_certificate_serialize" /> <link rel="refentry" href="/virtuoso/fn_xenc_decrypt_soap/" oldhref="fn_xenc_decrypt_soap.html" title="xenc_decrypt_soap" /> <link rel="refentry" href="/virtuoso/fn_xenc_delete_temp_keys/" oldhref="fn_xenc_delete_temp_keys.html" title="xenc_delete_temp_keys" /> <link rel="refentry" href="/virtuoso/fn_xenc_encrypt/" oldhref="fn_xenc_encrypt.html" title="xenc_encrypt" /> <link rel="refentry" href="/virtuoso/fn_encrypt/" oldhref="fn_encrypt.html" title="encrypt" /> <link rel="refentry" href="/virtuoso/fn_decrypt/" oldhref="fn_decrypt.html" title="decrypt" /> <link rel="refentry" href="/virtuoso/fn_totp_generate/" oldhref="fn_totp_generate.html" title="TOTP_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_get_key_algo/" oldhref="fn_xenc_get_key_algo.html" title="xenc_get_key_algo" /> <link rel="refentry" href="/virtuoso/fn_xenc_get_key_identifier/" oldhref="fn_xenc_get_key_identifier.html" title="xenc_get_key_identifier" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_read/" oldhref="fn_xenc_key_3des_read.html" title="xenc_key_3DES_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_create/" oldhref="fn_xenc_key_3des_create.html" title="xenc_key_3DES_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_rand_create/" oldhref="fn_xenc_key_3des_rand_create.html" title="xenc_key_3DES_rand_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_dsa_read/" oldhref="fn_xenc_key_dsa_read.html" title="xenc_key_DSA_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_rsa_read/" oldhref="fn_xenc_key_rsa_read.html" title="xenc_key_RSA_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_aes_create/" oldhref="fn_xenc_key_aes_create.html" title="xenc_key_AES_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_aes_rand_create/" oldhref="fn_xenc_key_aes_rand_create.html" title="xenc_key_AES_rand_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_create_cert/" oldhref="fn_xenc_key_create_cert.html" title="xenc_key_create_cert" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_dsa_create/" oldhref="fn_xenc_key_dsa_create.html" title="xenc_key_DSA_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_exists/" oldhref="fn_xenc_key_exists.html" title="xenc_key_exists" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_inst_create/" oldhref="fn_xenc_key_inst_create.html" title="xenc_key_inst_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_remove/" oldhref="fn_xenc_key_remove.html" title="xenc_key_remove" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_serialize/" oldhref="fn_xenc_key_serialize.html" title="xenc_key_serialize" /> <link rel="refentry" href="/virtuoso/fn_xenc_set_primary_key/" oldhref="fn_xenc_set_primary_key.html" title="xenc_set_primary_key" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_ss_generate/" oldhref="fn_xenc_x509_ss_generate.html" title="xenc_x509_ss_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_generate/" oldhref="fn_xenc_x509_generate.html" title="xenc_x509_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_pkcs12_export/" oldhref="fn_xenc_pkcs12_export.html" title="xenc_pkcs12_export" /> <link rel="refentry" href="/virtuoso/fn_xenc_pem_export/" oldhref="fn_xenc_pem_export.html" title="xenc_pem_export" /> <link rel="refentry" href="/virtuoso/fn_xenc_spki_read/" oldhref="fn_xenc_spki_read.html" title="xenc_SPKI_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_bn2dec/" oldhref="fn_xenc_bn2dec.html" title="xenc_bn2dec" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_rsa_create/" oldhref="fn_xenc_key_rsa_create.html" title="xenc_key_RSA_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_csr_generate/" oldhref="fn_xenc_x509_csr_generate.html" title="xenc_x509_csr_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_from_csr/" oldhref="fn_xenc_x509_from_csr.html" title="xenc_x509_from_csr" /> <link rel="refentry" href="/virtuoso/fn_xte_head/" oldhref="fn_xte_head.html" title="xte_head" /> <link rel="refentry" href="/virtuoso/fn_xte_node/" oldhref="fn_xte_node.html" title="xte_node" /> <link rel="refentry" href="/virtuoso/fn_xte_node_from_nodebld/" oldhref="fn_xte_node_from_nodebld.html" title="xte_node_from_nodebld" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_acc/" oldhref="fn_xte_nodebld_acc.html" title="xte_nodebld_acc" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_final/" oldhref="fn_xte_nodebld_final.html" title="xte_nodebld_final" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_init/" oldhref="fn_xte_nodebld_init.html" title="xte_nodebld_init" /> <link rel="refentry" href="/virtuoso/fn_xmlagg/" oldhref="fn_xmlagg.html" title="XMLAGG" /> <link rel="refentry" href="/virtuoso/fn_xmlattributes/" oldhref="fn_xmlattributes.html" title="XMLATTRIBUTES" /> <link rel="refentry" href="/virtuoso/fn_xmladdattribute/" oldhref="fn_xmladdattribute.html" title="XMLAddAttribute" /> <link rel="refentry" href="/virtuoso/fn_xmlappendchildren/" oldhref="fn_xmlappendchildren.html" title="XMLAppendChildren" /> <link rel="refentry" href="/virtuoso/fn_xmlconcat/" oldhref="fn_xmlconcat.html" title="XMLCONCAT" /> <link rel="refentry" href="/virtuoso/fn_xmlelement/" oldhref="fn_xmlelement.html" title="XMLELEMENT" /> <link rel="refentry" href="/virtuoso/fn_xmlforest/" oldhref="fn_xmlforest.html" title="XMLFOREST" /> <link rel="refentry" href="/virtuoso/fn_xmlinsertafter/" oldhref="fn_xmlinsertafter.html" title="XMLInsertAfter" /> <link rel="refentry" href="/virtuoso/fn_xmlinsertbefore/" oldhref="fn_xmlinsertbefore.html" title="XMLInsertBefore" /> <link rel="refentry" href="/virtuoso/fn_xmlreplace/" oldhref="fn_xmlreplace.html" title="XMLReplace" /> <link rel="refentry" href="/virtuoso/fn_xml_auto/" oldhref="fn_xml_auto.html" title="xml_auto" /> <link rel="refentry" href="/virtuoso/fn_xml_auto_dtd/" oldhref="fn_xml_auto_dtd.html" title="xml_auto_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_auto_schema/" oldhref="fn_xml_auto_schema.html" title="xml_auto_schema" /> <link rel="refentry" href="/virtuoso/fn_xml_create_tables_from_mapping_schema_decl/" oldhref="fn_xml_create_tables_from_mapping_schema_decl.html" title="xml_create_tables_from_mapping_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_cut/" oldhref="fn_xml_cut.html" title="xml_cut" /> <link rel="refentry" href="/virtuoso/fn_xml_doc_output_option/" oldhref="fn_xml_doc_output_option.html" title="xml_doc_output_option" /> <link rel="refentry" href="/virtuoso/fn_xml_load_schema_decl/" oldhref="fn_xml_load_schema_decl.html" title="xml_load_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_load_mapping_schema_decl/" oldhref="fn_xml_load_mapping_schema_decl.html" title="xml_load_mapping_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_namespace_scope/" oldhref="fn_xml_namespace_scope.html" title="xml_namespace_scope" /> <link rel="refentry" href="/virtuoso/fn_xml_add_system_path/" oldhref="fn_xml_add_system_path.html" title="xml_add_system_path" /> <link rel="refentry" href="/virtuoso/fn_xml_get_system_paths/" oldhref="fn_xml_get_system_paths.html" title="xml_get_system_paths" /> <link rel="refentry" href="/virtuoso/fn_xml_persistent/" oldhref="fn_xml_persistent.html" title="xml_persistent" /> <link rel="refentry" href="/virtuoso/fn_xml_template/" oldhref="fn_xml_template.html" title="xml_template" /> <link rel="refentry" href="/virtuoso/fn_xml_tree/" oldhref="fn_xml_tree.html" title="xml_tree" /> <link rel="refentry" href="/uda/ee/fn_xml_tree_doc/" oldhref="fn_xml_tree_doc.html" title="xml_tree_doc" /> <link rel="refentry" href="/uda/ee/fn_xml_tree_doc_media_type/" oldhref="fn_xml_tree_doc_media_type.html" title="xml_tree_doc_media_type" /> <link rel="refentry" href="/virtuoso/fn_xml_uri_get/" oldhref="fn_xml_uri_get.html" title="xml_uri_get" /> <link rel="refentry" href="/virtuoso/fn_xml_validate_dtd/" oldhref="fn_xml_validate_dtd.html" title="xml_validate_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_validate_schema/" oldhref="fn_xml_validate_schema.html" title="xml_validate_schema" /> <link rel="refentry" href="/virtuoso/fn_xml_view_dtd/" oldhref="fn_xml_view_dtd.html" title="xml_view_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_set_ns_decl/" oldhref="fn_xml_set_ns_decl.html" title="xml_set_ns_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_view_schema/" oldhref="fn_xml_view_schema.html" title="xml_view_schema" /> <link rel="refentry" href="/virtuoso/fn_xmlsql_update/" oldhref="fn_xmlsql_update.html" title="xmlsql_update" /> <link rel="refentry" href="/virtuoso/fn_xmlupdate/" oldhref="fn_xmlupdate.html" title="XMLUpdate" /> <link rel="refentry" href="/virtuoso/fn_xpath_eval/" oldhref="fn_xpath_eval.html" title="xpath_eval" /> <link rel="refentry" href="/virtuoso/fn_xper_cut/" oldhref="fn_xper_cut.html" title="xper_cut" /> <link rel="refentry" href="/virtuoso/fn_xper_doc/" oldhref="fn_xper_doc.html" title="xper_doc" /> <link rel="refentry" href="/virtuoso/fn_xper_locate_words/" oldhref="fn_xper_locate_words.html" title="xper_locate_words" /> <link rel="refentry" href="/virtuoso/fn_xper_right_sibling/" oldhref="fn_xper_right_sibling.html" title="XPER navigation" /> <link rel="refentry" href="/virtuoso/fn_xpf_extension/" oldhref="fn_xpf_extension.html" title="xpf_extension" /> <link rel="refentry" href="/virtuoso/fn_xpf_extension_remove/" oldhref="fn_xpf_extension_remove.html" title="xpf_extension_remove" /> <link rel="refentry" href="/virtuoso/fn_xquery_eval/" oldhref="fn_xquery_eval.html" title="xquery_eval" /> <link rel="refentry" href="/virtuoso/fn_xslt/" oldhref="fn_xslt.html" title="xslt" /> <link rel="refentry" href="/virtuoso/fn_xslt_format_number/" oldhref="fn_xslt_format_number.html" title="xslt_format_number" /> <link rel="refentry" href="/virtuoso/fn_xslt_sheet/" oldhref="fn_xslt_sheet.html" title="xslt_sheet" /> <link rel="refentry" href="/virtuoso/fn_xslt_stale/" oldhref="fn_xslt_stale.html" title="xslt_stale" /> <link rel="refentry" href="/uda/ee/fn_xtree_doc/" oldhref="fn_xtree_doc.html" title="xtree_doc" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.registeruser/" oldhref="fn_xmlstoragesystem.registeruser.html" title="xmlStorageSystem.registerUser" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.mailpasswordtouser/" oldhref="fn_xmlstoragesystem.mailpasswordtouser.html" title="xmlStorageSystem.mailPasswordToUser" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.getservercapabilities/" oldhref="fn_xmlstoragesystem.getservercapabilities.html" title="xmlStorageSystem.getServerCapabilities" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.deletemultiplefiles/" oldhref="fn_xmlstoragesystem.deletemultiplefiles.html" title="xmlStorageSystem.deleteMultipleFiles" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.savemultiplefiles/" oldhref="fn_xmlstoragesystem.savemultiplefiles.html" title="xmlStorageSystem.saveMultipleFiles" /> <link rel="refentry" href="/virtuoso/fn_xmltype.xmltype/" oldhref="fn_xmltype.xmltype.html" title="XMLType.XMLType" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createnonschemabasedxml/" oldhref="fn_xmltype.createnonschemabasedxml.html" title="XMLType.createNonSchemaBasedXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createschemabasedxml/" oldhref="fn_xmltype.createschemabasedxml.html" title="XMLType.createSchemaBasedXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createxml/" oldhref="fn_xmltype.createxml.html" title="XMLType.createXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.existsnode/" oldhref="fn_xmltype.existsnode.html" title="XMLType.existsNode" /> <link rel="refentry" href="/virtuoso/fn_xmltype.extract/" oldhref="fn_xmltype.extract.html" title="XMLType.extract" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getclobval/" oldhref="fn_xmltype.getclobval.html" title="XMLType.getClobVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getnamespace/" oldhref="fn_xmltype.getnamespace.html" title="XMLType.getNamespace" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getnumval/" oldhref="fn_xmltype.getnumval.html" title="XMLType.getNumVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getrootelement/" oldhref="fn_xmltype.getrootelement.html" title="XMLType.getRootElement" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getschemaurl/" oldhref="fn_xmltype.getschemaurl.html" title="XMLType.getSchemaURL" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getstringval/" oldhref="fn_xmltype.getstringval.html" title="XMLType.getStringVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isfragment/" oldhref="fn_xmltype.isfragment.html" title="XMLType.isFragment" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemabased/" oldhref="fn_xmltype.isschemabased.html" title="XMLType.isSchemaBased" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemavalid/" oldhref="fn_xmltype.isschemavalid.html" title="XMLType.isSchemaValid" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemavalidated/" oldhref="fn_xmltype.isschemavalidated.html" title="XMLType.isSchemaValidated" /> <link rel="refentry" href="/virtuoso/fn_xmltype.schemavalidate/" oldhref="fn_xmltype.schemavalidate.html" title="XMLType.schemaValidate" /> <link rel="refentry" href="/virtuoso/fn_xmltype.setschemavalidated/" oldhref="fn_xmltype.setschemavalidated.html" title="XMLType.setSchemaValidated" /> <link rel="refentry" href="/virtuoso/fn_xmltype.toobject/" oldhref="fn_xmltype.toobject.html" title="XMLType.toObject" /> <link rel="refentry" href="/virtuoso/fn_xmltype.transform/" oldhref="fn_xmltype.transform.html" title="XMLType.transform" /> <link rel="refentry" href="/virtuoso/xpf__sql__column/" oldhref="xpf__sql__column.html" title="sql:column" /> <link rel="refentry" href="/virtuoso/xpf_and/" oldhref="xpf_and.html" title="and" /> <link rel="refentry" href="/virtuoso/xpf_append/" oldhref="xpf_append.html" title="append" /> <link rel="refentry" href="/virtuoso/xpf_assign/" oldhref="xpf_assign.html" title="assign" /> <link rel="refentry" href="/virtuoso/xpf_avg/" oldhref="xpf_avg.html" title="avg" /> <link rel="refentry" href="/virtuoso/xpf_boolean/" oldhref="xpf_boolean.html" title="boolean" /> <link rel="refentry" href="/virtuoso/xpf_ceiling/" oldhref="xpf_ceiling.html" title="ceiling" /> <link rel="refentry" href="/virtuoso/xpf_collection/" oldhref="xpf_collection.html" title="fn:collection" /> <link rel="refentry" href="/virtuoso/xpf_concat/" oldhref="xpf_concat.html" title="concat" /> <link rel="refentry" href="/virtuoso/xpf_contains/" oldhref="xpf_contains.html" title="contains" /> <link rel="refentry" href="/virtuoso/xpf_count/" oldhref="xpf_count.html" title="count" /> <link rel="refentry" href="/virtuoso/xpf_create_attribute/" oldhref="xpf_create_attribute.html" title="create-attribute" /> <link rel="refentry" href="/virtuoso/xpf_create_comment/" oldhref="xpf_create_comment.html" title="create-comment" /> <link rel="refentry" href="/virtuoso/xpf_create_element/" oldhref="xpf_create_element.html" title="create-element" /> <link rel="refentry" href="/virtuoso/xpf_create_pi/" oldhref="xpf_create_pi.html" title="create-pi" /> <link rel="refentry" href="/virtuoso/xpf_current/" oldhref="xpf_current.html" title="current" /> <link rel="refentry" href="/virtuoso/xpf_distinct/" oldhref="xpf_distinct.html" title="distinct" /> <link rel="refentry" href="/virtuoso/xpf_doc/" oldhref="xpf_doc.html" title="doc" /> <link rel="refentry" href="/virtuoso/xpf_document/" oldhref="xpf_document.html" title="document" /> <link rel="refentry" href="/virtuoso/xpf_document_literal/" oldhref="xpf_document_literal.html" title="document-literal" /> <link rel="refentry" href="/virtuoso/xpf_empty/" oldhref="xpf_empty.html" title="empty" /> <link rel="refentry" href="/virtuoso/xpf_ends_with/" oldhref="xpf_ends_with.html" title="ends-with" /> <link rel="refentry" href="/virtuoso/xpf_every/" oldhref="xpf_every.html" title="every" /> <link rel="refentry" href="/virtuoso/xpf_except/" oldhref="xpf_except.html" title="except" /> <link rel="refentry" href="/virtuoso/xpf_false/" oldhref="xpf_false.html" title="false" /> <link rel="refentry" href="/virtuoso/xpf_filter/" oldhref="xpf_filter.html" title="filter" /> <link rel="refentry" href="/virtuoso/xpf_floor/" oldhref="xpf_floor.html" title="floor" /> <link rel="refentry" href="/virtuoso/xpf_for/" oldhref="xpf_for.html" title="for" /> <link rel="refentry" href="/virtuoso/xpf_format_number/" oldhref="xpf_format_number.html" title="format-number" /> <link rel="refentry" href="/virtuoso/xpf_function_available/" oldhref="xpf_function_available.html" title="function-available" /> <link rel="refentry" href="/virtuoso/xpf_generate_id/" oldhref="xpf_generate_id.html" title="generate-id" /> <link rel="refentry" href="/virtuoso/xpf_id/" oldhref="xpf_id.html" title="id" /> <link rel="refentry" href="/virtuoso/xpf_if/" oldhref="xpf_if.html" title="if" /> <link rel="refentry" href="/virtuoso/xpf_intersect/" oldhref="xpf_intersect.html" title="intersect" /> <link rel="refentry" href="/virtuoso/xpf_is_after/" oldhref="xpf_is_after.html" title="is_after" /> <link rel="refentry" href="/virtuoso/xpf_is_before/" oldhref="xpf_is_before.html" title="is_before" /> <link rel="refentry" href="/virtuoso/xpf_key/" oldhref="xpf_key.html" title="key" /> <link rel="refentry" href="/virtuoso/xpf_lang/" oldhref="xpf_lang.html" title="lang" /> <link rel="refentry" href="/virtuoso/xpf_last/" oldhref="xpf_last.html" title="last" /> <link rel="refentry" href="/virtuoso/xpf_let/" oldhref="xpf_let.html" title="let" /> <link rel="refentry" href="/virtuoso/xpf_list/" oldhref="xpf_list.html" title="list" /> <link rel="refentry" href="/virtuoso/xpf_local_name/" oldhref="xpf_local_name.html" title="local-name" /> <link rel="refentry" href="/virtuoso/xpf_max/" oldhref="xpf_max.html" title="max" /> <link rel="refentry" href="/virtuoso/xpf_min/" oldhref="xpf_min.html" title="min" /> <link rel="refentry" href="/virtuoso/xpf_name/" oldhref="xpf_name.html" title="name" /> <link rel="refentry" href="/virtuoso/xpf_namespace_uri/" oldhref="xpf_namespace_uri.html" title="namespace-uri" /> <link rel="refentry" href="/virtuoso/xpf_normalize_space/" oldhref="xpf_normalize_space.html" title="normalize-space" /> <link rel="refentry" href="/virtuoso/xpf_not/" oldhref="xpf_not.html" title="not" /> <link rel="refentry" href="/virtuoso/xpf_number/" oldhref="xpf_number.html" title="number" /> <link rel="refentry" href="/virtuoso/xpf_or/" oldhref="xpf_or.html" title="or" /> <link rel="refentry" href="/virtuoso/xpf_position/" oldhref="xpf_position.html" title="position" /> <link rel="refentry" href="/virtuoso/xpf_processxquery/" oldhref="xpf_processxquery.html" title="processXQuery" /> <link rel="refentry" href="/virtuoso/xpf_processxslt/" oldhref="xpf_processxslt.html" title="processXSLT" /> <link rel="refentry" href="/virtuoso/xpf_processxsql/" oldhref="xpf_processxsql.html" title="processXSQL" /> <link rel="refentry" href="/virtuoso/xpf_progn/" oldhref="xpf_progn.html" title="progn" /> <link rel="refentry" href="/virtuoso/xpf_replace/" oldhref="xpf_replace.html" title="replace" /> <link rel="refentry" href="/virtuoso/xpf_round/" oldhref="xpf_round.html" title="round" /> <link rel="refentry" href="/virtuoso/xpf_serialize/" oldhref="xpf_serialize.html" title="serialize" /> <link rel="refentry" href="/virtuoso/xpf_shallow/" oldhref="xpf_shallow.html" title="shallow" /> <link rel="refentry" href="/virtuoso/xpf_some/" oldhref="xpf_some.html" title="some" /> <link rel="refentry" href="/virtuoso/xpf_starts_with/" oldhref="xpf_starts_with.html" title="starts-with" /> <link rel="refentry" href="/virtuoso/xpf_string/" oldhref="xpf_string.html" title="string" /> <link rel="refentry" href="/virtuoso/xpf_string_length/" oldhref="xpf_string_length.html" title="string-length" /> <link rel="refentry" href="/virtuoso/xpf_substring/" oldhref="xpf_substring.html" title="substring" /> <link rel="refentry" href="/virtuoso/xpf_substring_after/" oldhref="xpf_substring_after.html" title="substring-after" /> <link rel="refentry" href="/virtuoso/xpf_substring_before/" oldhref="xpf_substring_before.html" title="substring-before" /> <link rel="refentry" href="/virtuoso/xpf_sum/" oldhref="xpf_sum.html" title="sum" /> <link rel="refentry" href="/virtuoso/xpf_system_property/" oldhref="xpf_system_property.html" title="system-property" /> <link rel="refentry" href="/virtuoso/xpf_text_contains/" oldhref="xpf_text_contains.html" title="text_contains" /> <link rel="refentry" href="/virtuoso/xpf_translate/" oldhref="xpf_translate.html" title="translate" /> <link rel="refentry" href="/virtuoso/xpf_true/" oldhref="xpf_true.html" title="true" /> <link rel="refentry" href="/virtuoso/xpf_tuple/" oldhref="xpf_tuple.html" title="tuple" /> <link rel="refentry" href="/virtuoso/xpf_union/" oldhref="xpf_union.html" title="union" /> <link rel="refentry" href="/virtuoso/xpf_unordered/" oldhref="xpf_unordered.html" title="unordered" /> <link rel="refentry" href="/virtuoso/xpf_unparsed_entity_uri/" oldhref="xpf_unparsed_entity_uri.html" title="unparsed-entity-uri" /> <link rel="refentry" href="/virtuoso/xpf_urlify/" oldhref="xpf_urlify.html" title="urlify" /> <link rel="refentry" href="/virtuoso/xpf_xmlview/" oldhref="xpf_xmlview.html" title="xmlview" /> <link rel="refentry" href="/virtuoso/fn_bpel_compile_script/" oldhref="fn_bpel_compile_script.html" title="BPEL.BPEL.compile_script" /> <link rel="refentry" href="/virtuoso/fn_bpel_copy_script/" oldhref="fn_bpel_copy_script.html" title="BPEL.BPEL.copy_script" /> <link rel="refentry" href="/virtuoso/fn_bpel_get_partner_links/" oldhref="fn_bpel_get_partner_links.html" title="BPEL.BPEL.get_partner_links" /> <link rel="refentry" href="/virtuoso/fn_bpel_instance_delete/" oldhref="fn_bpel_instance_delete.html" title="BPEL.BPEL.instance_delete" /> <link rel="refentry" href="/virtuoso/fn_bpel_purge/" oldhref="fn_bpel_purge.html" title="BPEL.BPEL.purge_instance" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_delete/" oldhref="fn_bpel_script_delete.html" title="BPEL.BPEL.script_delete" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_obsolete/" oldhref="fn_bpel_script_obsolete.html" title="BPEL.BPEL.script_obsolete" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_source_update/" oldhref="fn_bpel_script_source_update.html" title="BPEL.BPEL.script_source_update" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_upload/" oldhref="fn_bpel_script_upload.html" title="BPEL.BPEL.script_upload" /> <link rel="refentry" href="/virtuoso/fn_bpel_wsdl_upload/" oldhref="fn_bpel_wsdl_upload.html" title="BPEL.BPEL.wsdl_upload" /> <link rel="refentry" href="/virtuoso/fn_bpel_get_var/" oldhref="fn_bpel_get_var.html" title="BPEL.BPEL.getVariableData" /> <link rel="refentry" href="/virtuoso/fn_bpel_set_var/" oldhref="fn_bpel_set_var.html" title="BPEL.BPEL.setVariableData" /> <link rel="refentry" href="/virtuoso/fn_plink_get_option/" oldhref="fn_plink_get_option.html" title="BPEL.BPEL.plink_get_option" /> <link rel="refentry" href="/virtuoso/fn_plink_set_option/" oldhref="fn_plink_set_option.html" title="BPEL.BPEL.plink_set_option" /> <link rel="refentry" href="/virtuoso/fn_bpel_import_script/" oldhref="fn_bpel_import_script.html" title="BPEL.BPEL.import_script" /> <link rel="refentry" href="/virtuoso/fn_geometrytype/" oldhref="fn_geometrytype.html" title="GeometryType" /> <link rel="refentry" href="/virtuoso/fn_http_st_dxf_entity/" oldhref="fn_http_st_dxf_entity.html" title="http_st_dxf_entity" /> <link rel="refentry" href="/virtuoso/fn_http_st_ewkt/" oldhref="fn_http_st_ewkt.html" title="http_st_ewkt" /> <link rel="refentry" href="/virtuoso/fn_st_ewkt_read/" oldhref="fn_st_ewkt_read.html" title="st_ewkt_read" /> <link rel="refentry" href="/virtuoso/fn_postgis_proj_version/" oldhref="fn_postgis_proj_version.html" title="postgis_proj_version" /> <link rel="refentry" href="/virtuoso/fn_dist_from_point_to_line_segment/" oldhref="fn_dist_from_point_to_line_segment.html" title="dist_from_point_to_line_segment" /> <link rel="refentry" href="/virtuoso/fn_earth_radius/" oldhref="fn_earth_radius.html" title="earth_radius" /> <link rel="refentry" href="/virtuoso/fn_st_exteriorring/" oldhref="fn_st_exteriorring.html" title="ST_ExteriorRing" /> <link rel="refentry" href="/virtuoso/fn_st_geometryn/" oldhref="fn_st_geometryn.html" title="ST_GeometryN" /> <link rel="refentry" href="/virtuoso/fn_st_get_bounding_box/" oldhref="fn_st_get_bounding_box.html" title="st_get_bounding_box" /> <link rel="refentry" href="/virtuoso/fn_st_get_bounding_box_n/" oldhref="fn_st_get_bounding_box_n.html" title="st_get_bounding_box_n" /> <link rel="refentry" href="/virtuoso/fn_haversine_deg_km/" oldhref="fn_haversine_deg_km.html" title="haversine_deg_km" /> <link rel="refentry" href="/virtuoso/fn_st_interiorringn/" oldhref="fn_st_interiorringn.html" title="ST_InteriorRingN" /> <link rel="refentry" href="/virtuoso/fn_st_linestring/" oldhref="fn_st_linestring.html" title="st_linestring" /> <link rel="refentry" href="/virtuoso/fn_st_m/" oldhref="fn_st_m.html" title="ST_M" /> <link rel="refentry" href="/virtuoso/fn_st_may_intersect/" oldhref="fn_st_may_intersect.html" title="st_may_intersect" /> <link rel="refentry" href="/virtuoso/fn_st_mmax/" oldhref="fn_st_mmax.html" title="ST_MMax" /> <link rel="refentry" href="/virtuoso/fn_st_mmin/" oldhref="fn_st_mmin.html" title="ST_MMin" /> <link rel="refentry" href="/virtuoso/fn_st_numgeometries/" oldhref="fn_st_numgeometries.html" title="ST_NumGeometries" /> <link rel="refentry" href="/virtuoso/fn_st_numinteriorrings/" oldhref="fn_st_numinteriorrings.html" title="ST_NumInteriorRings" /> <link rel="refentry" href="/virtuoso/fn_st_transform/" oldhref="fn_st_transform.html" title="ST_Transform" /> <link rel="refentry" href="/virtuoso/fn_st_transform_by_custom_projection/" oldhref="fn_st_transform_by_custom_projection.html" title="st_transform_by_custom_projection" /> <link rel="refentry" href="/virtuoso/fn_st_translate/" oldhref="fn_st_translate.html" title="ST_Translate" /> <link rel="refentry" href="/virtuoso/fn_st_transscale/" oldhref="fn_st_transscale.html" title="ST_TransScale" /> <link rel="refentry" href="/virtuoso/fn_st_xmax/" oldhref="fn_st_xmax.html" title="ST_XMax" /> <link rel="refentry" href="/virtuoso/fn_st_xmin/" oldhref="fn_st_xmin.html" title="ST_XMin" /> <link rel="refentry" href="/virtuoso/fn_st_ymax/" oldhref="fn_st_ymax.html" title="ST_YMax" /> <link rel="refentry" href="/virtuoso/fn_st_ymin/" oldhref="fn_st_ymin.html" title="ST_YMin" /> <link rel="refentry" href="/virtuoso/fn_st_z/" oldhref="fn_st_z.html" title="ST_Z" /> <link rel="refentry" href="/virtuoso/fn_st_zmax/" oldhref="fn_st_zmax.html" title="ST_ZMax" /> <link rel="refentry" href="/virtuoso/fn_st_zmflag/" oldhref="fn_st_zmflag.html" title="ST_Zmflag" /> <link rel="refentry" href="/virtuoso/fn_st_zmin/" oldhref="fn_st_zmin.html" title="ST_ZMin" /> <link rel="section" href="/virtuoso/ch-server/" oldhref="ch-server.html#databaseadmsrv" title="6.1.聽Database Server Administration" /> <link rel="section" href="/virtuoso/htmlconductorbar/" oldhref="htmlconductorbar.html" title="6.2.聽HTML based Administration Console (Conductor) Guide" /> <link rel="section" href="/virtuoso/clusteroperation/" oldhref="clusteroperation.html" title="6.3.聽Virtuoso Cluster Operation" /> <link rel="section" href="/virtuoso/fault/" oldhref="fault.html" title="6.4.聽Virtuoso Cluster Fault Tolerance" /> <link href="/virtuoso/feeds/rss/" type="application/rss+xml" rel="alternate" title="OpenLink Software: RSS Feed: virtdocs" /> <link href="/virtuoso/feeds/atom/" type="application/atom+xml" rel="alternate" title="OpenLink Software: Atom Feed: virtdocs" /> <link href="/virtuoso/feeds/json/" type="application/feed+json" rel="alternate" title="OpenLink Software: JSON Feed: virtdocs" /> <link rel="canonical" href="http://docs.openlinksw.com/virtuoso/ch-server/" /> <script type="application/ld+json"> { "@context": "http://schema.org/", "@type": "WebSite", "url": "http://docs.openlinksw.com/virtuoso/ch-server/", "potentialAction": { "@type": "SearchAction", "name": "Website Search", "target": "/search/?q={search_term_string}", "query-input": "required name=search_term_string" } } </script><link rel="chapter" href="/virtuoso/ch-overview/" oldhref="ch-overview.html" title="Chapter聽1.聽Overview" /> <link rel="chapter" href="/virtuoso/ch-installation/" oldhref="ch-installation.html" title="Chapter聽2.聽Installation Guide" /> <link rel="chapter" href="/virtuoso/ch-quicktours/" oldhref="ch-quicktours.html" title="Chapter聽3.聽Quick Start & Tours" /> <link rel="chapter" href="/virtuoso/ch-sampleapps/" oldhref="ch-sampleapps.html" title="Chapter聽4.聽Sample ODBC & JDBC Applications" /> <link rel="chapter" href="/virtuoso/ch-concepts/" oldhref="ch-concepts.html" title="Chapter聽5.聽Conceptual Overview" /> <link rel="chapter" href="/virtuoso/ch-server/" oldhref="ch-server.html" title="Chapter聽6.聽Administration" /> <link rel="chapter" href="/virtuoso/ch-accessinterfaces/" oldhref="ch-accessinterfaces.html" title="Chapter聽7.聽Data Access Interfaces" /> <link rel="chapter" href="/virtuoso/ch-vdbengine/" oldhref="ch-vdbengine.html" title="Chapter聽8.聽Virtual Database Engine" /> <link rel="chapter" href="/virtuoso/ch-sqlreference/" oldhref="ch-sqlreference.html" title="Chapter聽9.聽SQL Reference" /> <link rel="chapter" href="/virtuoso/ch-clusterprogramming/" oldhref="ch-clusterprogramming.html" title="Chapter聽10.聽Virtuoso Cluster Programming" /> <link rel="chapter" href="/virtuoso/ch-sqlprocedures/" oldhref="ch-sqlprocedures.html" title="Chapter聽11.聽SQL Procedure Language Guide" /> <link rel="chapter" href="/virtuoso/ch-hooks/" oldhref="ch-hooks.html" title="Chapter聽12.聽Database Event Hooks" /> <link rel="chapter" href="/virtuoso/ch-repl/" oldhref="ch-repl.html" title="Chapter聽13.聽Data Replication, Synchronization and Transformation Services" /> <link rel="chapter" href="/virtuoso/ch-webappdevelopment/" oldhref="ch-webappdevelopment.html" title="Chapter聽14.聽Web Application Development" /> <link rel="refentry" href="/virtuoso/vc_type_calculateablevalue/" oldhref="vc_type_calculateablevalue.html" title="CalculateableValue" /> <link rel="refentry" href="/virtuoso/vc_type_forcedcalculateablevalue/" oldhref="vc_type_forcedcalculateablevalue.html" title="ForcedCalculateableValue" /> <link rel="refentry" href="/virtuoso/vc_type_sqlcode/" oldhref="vc_type_sqlcode.html" title="SqlCode" /> <link rel="refentry" href="/virtuoso/vc_type_sqlname/" oldhref="vc_type_sqlname.html" title="SqlName" /> <link rel="refentry" href="/virtuoso/vc_after_data_bind/" oldhref="vc_after_data_bind.html" title="after-data-bind" /> <link rel="refentry" href="/virtuoso/vc_after_data_bind_container/" oldhref="vc_after_data_bind_container.html" title="after-data-bind-container" /> <link rel="refentry" href="/virtuoso/vc_before_data_bind/" oldhref="vc_before_data_bind.html" title="before-data-bind" /> <link rel="refentry" href="/virtuoso/vc_before_data_bind_container/" oldhref="vc_before_data_bind_container.html" title="before-data-bind-container" /> <link rel="refentry" href="/virtuoso/vc_before_render/" oldhref="vc_before_render.html" title="before-render" /> <link rel="refentry" href="/virtuoso/vc_before_render_container/" oldhref="vc_before_render_container.html" title="before-render-container" /> <link rel="refentry" href="/virtuoso/vc_button/" oldhref="vc_button.html" title="button" /> <link rel="refentry" href="/virtuoso/vc_calendar/" oldhref="vc_calendar.html" title="calendar" /> <link rel="refentry" href="/virtuoso/vc_check_box/" oldhref="vc_check_box.html" title="check-box" /> <link rel="refentry" href="/virtuoso/vc_code_file/" oldhref="vc_code_file.html" title="code-file" /> <link rel="refentry" href="/virtuoso/vc_column/" oldhref="vc_column.html" title="column" /> <link rel="refentry" href="/virtuoso/vc_data_grid/" oldhref="vc_data_grid.html" title="data-grid" /> <link rel="refentry" href="/virtuoso/vc_data_list/" oldhref="vc_data_list.html" title="data-list" /> <link rel="refentry" href="/virtuoso/vc_data_set/" oldhref="vc_data_set.html" title="data-set" /> <link rel="refentry" href="/virtuoso/vc_data_source/" oldhref="vc_data_source.html" title="data-source" /> <link rel="refentry" href="/virtuoso/vc_error_summary/" oldhref="vc_error_summary.html" title="error-summary" /> <link rel="refentry" href="/virtuoso/vc_expression/" oldhref="vc_expression.html" title="expression" /> <link rel="refentry" href="/virtuoso/vc_field/" oldhref="vc_field.html" title="field" /> <link rel="refentry" href="/virtuoso/vc_form/" oldhref="vc_form.html" title="form" /> <link rel="refentry" href="/virtuoso/vc_hidden/" oldhref="vc_hidden.html" title="hidden" /> <link rel="refentry" href="/virtuoso/vc_horizontal_template/" oldhref="vc_horizontal_template.html" title="horizontal-template" /> <link rel="refentry" href="/virtuoso/vc_include/" oldhref="vc_include.html" title="include" /> <link rel="refentry" href="/virtuoso/vc_isql/" oldhref="vc_isql.html" title="isql" /> <link rel="refentry" href="/virtuoso/vc_item/" oldhref="vc_item.html" title="item" /> <link rel="refentry" href="/virtuoso/vc_key/" oldhref="vc_key.html" title="key" /> <link rel="refentry" href="/virtuoso/vc_label/" oldhref="vc_label.html" title="label" /> <link rel="refentry" href="/virtuoso/vc_leaf_template/" oldhref="vc_leaf_template.html" title="leaf-template" /> <link rel="refentry" href="/virtuoso/vc_local_variable/" oldhref="vc_local_variable.html" title="local-variable" /> <link rel="refentry" href="/virtuoso/vc_login/" oldhref="vc_login.html" title="login" /> <link rel="refentry" href="/virtuoso/vc_login_form/" oldhref="vc_login_form.html" title="login-form" /> <link rel="refentry" href="/virtuoso/vc_method/" oldhref="vc_method.html" title="method" /> <link rel="refentry" href="/virtuoso/vc_node/" oldhref="vc_node.html" title="node" /> <link rel="refentry" href="/virtuoso/vc_node_template/" oldhref="vc_node_template.html" title="node-template" /> <link rel="refentry" href="/virtuoso/vc_on_init/" oldhref="vc_on_init.html" title="on-init" /> <link rel="refentry" href="/virtuoso/vc_on_init_container/" oldhref="vc_on_init_container.html" title="on-init-container" /> <link rel="refentry" href="/virtuoso/vc_on_post/" oldhref="vc_on_post.html" title="on-post" /> <link rel="refentry" href="/virtuoso/vc_on_post_container/" oldhref="vc_on_post_container.html" title="on-post-container" /> <link rel="refentry" href="/virtuoso/vc_page/" oldhref="vc_page.html" title="page" /> <link rel="refentry" href="/virtuoso/vc_param/" oldhref="vc_param.html" title="param" /> <link rel="refentry" href="/virtuoso/vc_placeholder/" oldhref="vc_placeholder.html" title="placeholder" /> <link rel="refentry" href="/virtuoso/vc_radio_button/" oldhref="vc_radio_button.html" title="radio-button" /> <link rel="refentry" href="/virtuoso/vc_radio_group/" oldhref="vc_radio_group.html" title="radio-group" /> <link rel="refentry" href="/virtuoso/vc_script/" oldhref="vc_script.html" title="script" /> <link rel="refentry" href="/virtuoso/vc_select_list/" oldhref="vc_select_list.html" title="select-list" /> <link rel="refentry" href="/virtuoso/vc_style/" oldhref="vc_style.html" title="style" /> <link rel="refentry" href="/virtuoso/vc_tab/" oldhref="vc_tab.html" title="tab" /> <link rel="refentry" href="/virtuoso/vc_template/" oldhref="vc_template.html" title="template" /> <link rel="refentry" href="/virtuoso/vc_text/" oldhref="vc_text.html" title="text" /> <link rel="refentry" href="/virtuoso/vc_textarea/" oldhref="vc_textarea.html" title="textarea" /> <link rel="refentry" href="/virtuoso/vc_tree/" oldhref="vc_tree.html" title="tree" /> <link rel="refentry" href="/virtuoso/vc_url/" oldhref="vc_url.html" title="url" /> <link rel="refentry" href="/virtuoso/vc_validator/" oldhref="vc_validator.html" title="validator" /> <link rel="refentry" href="/virtuoso/vc_variable/" oldhref="vc_variable.html" title="variable" /> <link rel="refentry" href="/virtuoso/vc_vscx/" oldhref="vc_vscx.html" title="vscx" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub/" oldhref="vc_xsd_stub.html" title="xsd-stub" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub_script/" oldhref="vc_xsd_stub_script.html" title="xsd-stub-script" /> <link rel="refentry" href="/virtuoso/vc_xsd_stub_top/" oldhref="vc_xsd_stub_top.html" title="xsd-stub-top" /> <link rel="chapter" href="/virtuoso/ch-webandxml/" oldhref="ch-webandxml.html" title="Chapter聽15.聽XML Support" /> <link rel="chapter" href="/virtuoso/ch-rdfandsparql/" oldhref="ch-rdfandsparql.html" title="Chapter聽16.聽RDF Data Access and Data Management" /> <link rel="chapter" href="/virtuoso/ch-webservices/" oldhref="ch-webservices.html" title="Chapter聽17.聽Web Services" /> <link rel="chapter" href="/virtuoso/ch-runtimehosting/" oldhref="ch-runtimehosting.html" title="Chapter聽18.聽Runtime Hosting" /> <link rel="chapter" href="/virtuoso/ch-internetservices/" oldhref="ch-internetservices.html" title="Chapter聽19.聽Internet Services" /> <link rel="chapter" href="/virtuoso/ch-freetext/" oldhref="ch-freetext.html" title="Chapter聽20.聽Free Text Search" /> <link rel="chapter" href="/virtuoso/ch-tpcc/" oldhref="ch-tpcc.html" title="Chapter聽21.聽TPC C Benchmark Kit" /> <link rel="chapter" href="/virtuoso/ch-xa/" oldhref="ch-xa.html" title="Chapter聽22.聽Using Virtuoso with Tuxedo" /> <link rel="chapter" href="/virtuoso/ch-appendixa/" oldhref="ch-appendixa.html" title="Chapter聽23.聽Appendix A" /> <link rel="chapter" href="/virtuoso/ch-functions/" oldhref="ch-functions.html" title="Chapter聽24.聽Virtuoso Functions Guide & Reference" /> <link rel="refentry" href="/virtuoso/fn_var/" oldhref="fn_var.html" title="VAR" /> <link rel="refentry" href="/virtuoso/fn_var_samp/" oldhref="fn_var_samp.html" title="VAR_SAMP" /> <link rel="refentry" href="/virtuoso/fn_var_pop/" oldhref="fn_var_pop.html" title="VAR_POP" /> <link rel="refentry" href="/virtuoso/fn_stddev/" oldhref="fn_stddev.html" title="STDDEV" /> <link rel="refentry" href="/virtuoso/fn_stddev_samp/" oldhref="fn_stddev_samp.html" title="STDDEV_SAMP" /> <link rel="refentry" href="/virtuoso/fn_stddev_pop/" oldhref="fn_stddev_pop.html" title="STDDEV_POP" /> <link rel="refentry" href="/virtuoso/fn_regr_syy/" oldhref="fn_regr_syy.html" title="REGR_SYY" /> <link rel="refentry" href="/virtuoso/fn_regr_sxx/" oldhref="fn_regr_sxx.html" title="REGR_SXX" /> <link rel="refentry" href="/virtuoso/fn_regr_sxy/" oldhref="fn_regr_sxy.html" title="REGR_SXY" /> <link rel="refentry" href="/virtuoso/fn_regr_avgx/" oldhref="fn_regr_avgx.html" title="REGR_AVGX" /> <link rel="refentry" href="/virtuoso/fn_regr_avgy/" oldhref="fn_regr_avgy.html" title="REGR_AVGY" /> <link rel="refentry" href="/virtuoso/fn_regr_r2/" oldhref="fn_regr_r2.html" title="REGR_R2" /> <link rel="refentry" href="/virtuoso/fn_regr_count/" oldhref="fn_regr_count.html" title="REGR_COUNT" /> <link rel="refentry" href="/virtuoso/fn_regr_intercept/" oldhref="fn_regr_intercept.html" title="REGR_INTERCEPT" /> <link rel="refentry" href="/virtuoso/fn_regr_slope/" oldhref="fn_regr_slope.html" title="REGR_SLOPE" /> <link rel="refentry" href="/virtuoso/fn_covar_samp/" oldhref="fn_covar_samp.html" title="COVAR_SAMP" /> <link rel="refentry" href="/virtuoso/fn_covar_pop/" oldhref="fn_covar_pop.html" title="COVAR_POP" /> <link rel="refentry" href="/virtuoso/fn_corr/" oldhref="fn_corr.html" title="CORR" /> <link rel="refentry" href="/virtuoso/fn_xq_sequence_agg/" oldhref="fn_xq_sequence_agg.html" title="DB.DBA.XQ_SEQUENCE_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_agg/" oldhref="fn_vector_agg.html" title="DB.DBA.VECTOR_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_of_nonnulls_agg/" oldhref="fn_vector_of_nonnulls_agg.html" title="DB.DBA.VECTOR_OF_NONNULLS_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_or_null_agg/" oldhref="fn_vector_or_null_agg.html" title="DB.DBA.VECTOR_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_of_nonnulls_or_null_agg/" oldhref="fn_vector_of_nonnulls_or_null_agg.html" title="DB.DBA.VECTOR_OF_NONNULLS_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_vector_concat_agg/" oldhref="fn_vector_concat_agg.html" title="DB.DBA.VECTOR_CONCAT_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_agg/" oldhref="fn_bag_agg.html" title="DB.DBA.BAG_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_of_nonnulls_agg/" oldhref="fn_bag_of_nonnulls_agg.html" title="DB.DBA.BAG_OF_NONNULLS_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_or_null_agg/" oldhref="fn_bag_or_null_agg.html" title="DB.DBA.BAG_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_of_nonnulls_or_null_agg/" oldhref="fn_bag_of_nonnulls_or_null_agg.html" title="DB.DBA.BAG_OF_NONNULLS_OR_NULL_AGG" /> <link rel="refentry" href="/virtuoso/fn_bag_concat_agg/" oldhref="fn_bag_concat_agg.html" title="DB.DBA.BAG_CONCAT_AGG" /> <link rel="refentry" href="/virtuoso/fn_abs/" oldhref="fn_abs.html" title="abs" /> <link rel="refentry" href="/virtuoso/fn___any_grants/" oldhref="fn___any_grants.html" title="__any_grants" /> <link rel="refentry" href="/virtuoso/fn_aref/" oldhref="fn_aref.html" title="aref" /> <link rel="refentry" href="/virtuoso/fn_ascii/" oldhref="fn_ascii.html" title="ascii" /> <link rel="refentry" href="/virtuoso/fn_aset/" oldhref="fn_aset.html" title="aset" /> <link rel="refentry" href="/virtuoso/fn_atof/" oldhref="fn_atof.html" title="atof" /> <link rel="refentry" href="/virtuoso/fn_atoi/" oldhref="fn_atoi.html" title="atoi" /> <link rel="refentry" href="/virtuoso/fn_att_local_name/" oldhref="fn_att_local_name.html" title="att_local_name" /> <link rel="refentry" href="/virtuoso/fn_backup/" oldhref="fn_backup.html" title="backup" /> <link rel="refentry" href="/virtuoso/fn_backup_online/" oldhref="fn_backup_online.html" title="backup_online" /> <link rel="refentry" href="/virtuoso/fn_backup_context_clear/" oldhref="fn_backup_context_clear.html" title="backup_context_clear" /> <link rel="refentry" href="/virtuoso/fn_bif_arg/" oldhref="fn_bif_arg.html" title="Virtuoso Server Extension Interface (VSEI) functions" /> <link rel="refentry" href="/virtuoso/fn_bit_and/" oldhref="fn_bit_and.html" title="bit_and" /> <link rel="refentry" href="/virtuoso/fn_bit_or/" oldhref="fn_bit_or.html" title="bit_or" /> <link rel="refentry" href="/virtuoso/fn_bit_not/" oldhref="fn_bit_not.html" title="bit_not" /> <link rel="refentry" href="/virtuoso/fn_bit_shift/" oldhref="fn_bit_shift.html" title="bit_shift" /> <link rel="refentry" href="/virtuoso/fn_bit_xor/" oldhref="fn_bit_xor.html" title="bit_xor" /> <link rel="refentry" href="/virtuoso/fn_blob_to_string/" oldhref="fn_blob_to_string.html" title="blob_to_string" /> <link rel="refentry" href="/virtuoso/fn_blob_to_string_output/" oldhref="fn_blob_to_string_output.html" title="blob_to_string_output" /> <link rel="refentry" href="/virtuoso/fn_bookmark/" oldhref="fn_bookmark.html" title="bookmark" /> <link rel="refentry" href="/virtuoso/fn_ceiling/" oldhref="fn_ceiling.html" title="ceiling" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_count/" oldhref="fn_cfg_item_count.html" title="cfg_item_count" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_name/" oldhref="fn_cfg_item_name.html" title="cfg_item_name" /> <link rel="refentry" href="/virtuoso/fn_cfg_item_value/" oldhref="fn_cfg_item_value.html" title="cfg_item_value" /> <link rel="refentry" href="/virtuoso/fn_cfg_section_count/" oldhref="fn_cfg_section_count.html" title="cfg_section_count" /> <link rel="refentry" href="/virtuoso/fn_cfg_section_name/" oldhref="fn_cfg_section_name.html" title="cfg_section_name" /> <link rel="refentry" href="/virtuoso/fn_cfg_write/" oldhref="fn_cfg_write.html" title="cfg_write" /> <link rel="refentry" href="/virtuoso/fn_charset_define/" oldhref="fn_charset_define.html" title="charset_define" /> <link rel="refentry" href="/virtuoso/fn_charset_recode/" oldhref="fn_charset_recode.html" title="charset_recode" /> <link rel="refentry" href="/virtuoso/fn_charsets_list/" oldhref="fn_charsets_list.html" title="charsets_list" /> <link rel="refentry" href="/virtuoso/fn_checkpoint_interval/" oldhref="fn_checkpoint_interval.html" title="checkpoint_interval" /> <link rel="refentry" href="/virtuoso/fn_chr/" oldhref="fn_chr.html" title="chr" /> <link rel="refentry" href="/virtuoso/fn_client_attr/" oldhref="fn_client_attr.html" title="client_attr" /> <link rel="refentry" href="/virtuoso/fn_collation_define/" oldhref="fn_collation_define.html" title="collation_define" /> <link rel="refentry" href="/virtuoso/fn_complete_table_name/" oldhref="fn_complete_table_name.html" title="complete_table_name" /> <link rel="refentry" href="/virtuoso/fn_composite/" oldhref="fn_composite.html" title="composite" /> <link rel="refentry" href="/virtuoso/fn_composite_ref/" oldhref="fn_composite_ref.html" title="composite_ref" /> <link rel="refentry" href="/virtuoso/fn_concat/" oldhref="fn_concat.html" title="concat" /> <link rel="refentry" href="/virtuoso/fn_concatenate/" oldhref="fn_concatenate.html" title="concatenate" /> <link rel="refentry" href="/virtuoso/fn_connection_get/" oldhref="fn_connection_get.html" title="connection_get" /> <link rel="refentry" href="/virtuoso/fn_connection_id/" oldhref="fn_connection_id.html" title="connection_id" /> <link rel="refentry" href="/virtuoso/fn_connection_is_dirty/" oldhref="fn_connection_is_dirty.html" title="connection_is_dirty" /> <link rel="refentry" href="/virtuoso/fn_connection_set/" oldhref="fn_connection_set.html" title="connection_set" /> <link rel="refentry" href="/virtuoso/fn_connection_vars/" oldhref="fn_connection_vars.html" title="connection_vars" /> <link rel="refentry" href="/virtuoso/fn_connection_vars_set/" oldhref="fn_connection_vars_set.html" title="connection_vars_set" /> <link rel="refentry" href="/virtuoso/fn_contains/" oldhref="fn_contains.html" title="contains" /> <link rel="refentry" href="/virtuoso/fn_cov_load/" oldhref="fn_cov_load.html" title="cov_load" /> <link rel="refentry" href="/virtuoso/fn_cov_report/" oldhref="fn_cov_report.html" title="cov_report" /> <link rel="refentry" href="/virtuoso/fn_cov_store/" oldhref="fn_cov_store.html" title="cov_store" /> <link rel="refentry" href="/virtuoso/fn_createxml/" oldhref="fn_createxml.html" title="createXML" /> <link rel="refentry" href="/virtuoso/fn_curdate/" oldhref="fn_curdate.html" title="curdate" /> <link rel="refentry" href="/virtuoso/fn_forget_timezone/" oldhref="fn_forget_timezone.html" title="forget_timezone" /> <link rel="refentry" href="/virtuoso/fn_is_timezoneless/" oldhref="fn_is_timezoneless.html" title="is_timezoneless" /> <link rel="refentry" href="/virtuoso/fn_adjust_timezone/" oldhref="fn_adjust_timezone.html" title="adjust_timezone" /> <link rel="refentry" href="/virtuoso/fn_rdf_now_impl/" oldhref="fn_rdf_now_impl.html" title="rdf_now_impl" /> <link rel="refentry" href="/virtuoso/fn_current_timestamp/" oldhref="fn_current_timestamp.html" title="current_timestamp" /> <link rel="refentry" href="/virtuoso/fn_curdatetime/" oldhref="fn_curdatetime.html" title="curdatetime" /> <link rel="refentry" href="/virtuoso/fn_curdatetimeoffset/" oldhref="fn_curdatetimeoffset.html" title="curdatetimeoffset" /> <link rel="refentry" href="/virtuoso/fn_curutcdatetime/" oldhref="fn_curutcdatetime.html" title="curutcdatetime" /> <link rel="refentry" href="/virtuoso/fn_sysutcdatetime/" oldhref="fn_sysutcdatetime.html" title="sysutcdatetime" /> <link rel="refentry" href="/virtuoso/fn_current_charset/" oldhref="fn_current_charset.html" title="current_charset" /> <link rel="refentry" href="/virtuoso/fn_vacuum/" oldhref="fn_vacuum.html" title="DB.DBA.VACUUM" /> <link rel="refentry" href="/virtuoso/fn_sparql_to_sql_text/" oldhref="fn_sparql_to_sql_text.html" title="sparql_to_sql_text" /> <link rel="refentry" href="/virtuoso/fn_dateadd/" oldhref="fn_dateadd.html" title="dateadd" /> <link rel="refentry" href="/virtuoso/fn_datediff/" oldhref="fn_datediff.html" title="datediff" /> <link rel="refentry" href="/virtuoso/fn_datestring/" oldhref="fn_datestring.html" title="datestring , datestring_gmt ," /> <link rel="refentry" href="/virtuoso/fn_datestring_gmt/" oldhref="fn_datestring_gmt.html" title="datestring_GMT" /> <link rel="refentry" href="/virtuoso/fn_dav_api_add/" oldhref="fn_dav_api_add.html" title="DAV add & update functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_change/" oldhref="fn_dav_api_change.html" title="DAV manipulation functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_lock/" oldhref="fn_dav_api_lock.html" title="DAV lock manipulation functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_search/" oldhref="fn_dav_api_search.html" title="DAV search functions" /> <link rel="refentry" href="/virtuoso/fn_dav_api_user/" oldhref="fn_dav_api_user.html" title="WebDAV Users & Groups administration" /> <link rel="refentry" href="/virtuoso/fn_dav_exp/" oldhref="fn_dav_exp.html" title="DAV_EXP" /> <link rel="refentry" href="/virtuoso/fn_dayname/" oldhref="fn_dayname.html" title="dayname" /> <link rel="refentry" href="/virtuoso/fn_dayofmonth/" oldhref="fn_dayofmonth.html" title="dayofmonth" /> <link rel="refentry" href="/virtuoso/fn_dayofweek/" oldhref="fn_dayofweek.html" title="dayofweek" /> <link rel="refentry" href="/virtuoso/fn_dayofyear/" oldhref="fn_dayofyear.html" title="dayofyear" /> <link rel="refentry" href="/virtuoso/fn_dbg_obj_print/" oldhref="fn_dbg_obj_print.html" title="dbg_obj_print" /> <link rel="refentry" href="/virtuoso/fn_dbg_printf/" oldhref="fn_dbg_printf.html" title="dbg_printf" /> <link rel="refentry" href="/virtuoso/fn_dbname/" oldhref="fn_dbname.html" title="dbname" /> <link rel="refentry" href="/virtuoso/fn_delay/" oldhref="fn_delay.html" title="delay" /> <link rel="refentry" href="/virtuoso/fn_cl_exec/" oldhref="fn_cl_exec.html" title="cl_exec" /> <link rel="refentry" href="/virtuoso/fn_dict_dec_or_remove/" oldhref="fn_dict_dec_or_remove.html" title="dict_dec_or_remove" /> <link rel="refentry" href="/virtuoso/fn_dict_duplicate/" oldhref="fn_dict_duplicate.html" title="dict_duplicate" /> <link rel="refentry" href="/virtuoso/fn_dict_get/" oldhref="fn_dict_get.html" title="dict_get" /> <link rel="refentry" href="/virtuoso/fn_dict_inc_or_put/" oldhref="fn_dict_inc_or_put.html" title="dict_inc_or_put" /> <link rel="refentry" href="/virtuoso/fn_dict_iter_next/" oldhref="fn_dict_iter_next.html" title="dict_iter_next" /> <link rel="refentry" href="/virtuoso/fn_dict_iter_rewind/" oldhref="fn_dict_iter_rewind.html" title="dict_iter_rewind" /> <link rel="refentry" href="/virtuoso/fn_dict_list_keys/" oldhref="fn_dict_list_keys.html" title="dict_list_keys" /> <link rel="refentry" href="/virtuoso/fn_dict_destructive_list_rnd_keys/" oldhref="fn_dict_destructive_list_rnd_keys.html" title="dict_destructive_list_rnd_keys" /> <link rel="refentry" href="/virtuoso/fn_dict_new/" oldhref="fn_dict_new.html" title="dict_new" /> <link rel="refentry" href="/virtuoso/fn_dict_put/" oldhref="fn_dict_put.html" title="dict_put" /> <link rel="refentry" href="/virtuoso/fn_dict_remove/" oldhref="fn_dict_remove.html" title="dict_remove" /> <link rel="refentry" href="/virtuoso/fn_dict_size/" oldhref="fn_dict_size.html" title="dict_size" /> <link rel="refentry" href="/virtuoso/fn_dict_to_vector/" oldhref="fn_dict_to_vector.html" title="dict_to_vector" /> <link rel="refentry" href="/virtuoso/fn_dict_zap/" oldhref="fn_dict_zap.html" title="dict_zap" /> <link rel="refentry" href="/virtuoso/fn_disconnect_user/" oldhref="fn_disconnect_user.html" title="disconnect_user" /> <link rel="refentry" href="/virtuoso/fn_dt_set_tz/" oldhref="fn_dt_set_tz.html" title="dt_set_tz" /> <link rel="refentry" href="/virtuoso/fn_dvector/" oldhref="fn_dvector.html" title="dvector" /> <link rel="refentry" href="/virtuoso/fn_end_result/" oldhref="fn_end_result.html" title="end_result" /> <link rel="refentry" href="/virtuoso/fn_either/" oldhref="fn_either.html" title="either" /> <link rel="refentry" href="/virtuoso/fn_elh_get_handler/" oldhref="fn_elh_get_handler.html" title="elh_get_handler" /> <link rel="refentry" href="/virtuoso/fn_elh_load_handler/" oldhref="fn_elh_load_handler.html" title="elh_load_handler" /> <link rel="refentry" href="/virtuoso/fn_encode_base64/" oldhref="fn_encode_base64.html" title="encode_base64" /> <link rel="refentry" href="/virtuoso/fn_equ/" oldhref="fn_equ.html" title="equ" /> <link rel="refentry" href="/virtuoso/fn_exec/" oldhref="fn_exec.html" title="exec" /> <link rel="refentry" href="/virtuoso/fn_exec_close/" oldhref="fn_exec_close.html" title="close" /> <link rel="refentry" href="/virtuoso/fn_exec_next/" oldhref="fn_exec_next.html" title="exec_next" /> <link rel="refentry" href="/virtuoso/fn_exec_result/" oldhref="fn_exec_result.html" title="exec_result" /> <link rel="refentry" href="/virtuoso/fn_exec_result_names/" oldhref="fn_exec_result_names.html" title="exec_result_names" /> <link rel="refentry" href="/virtuoso/fn_exec_metadata/" oldhref="fn_exec_metadata.html" title="exec_metadata" /> <link rel="refentry" href="/virtuoso/fn_exec_score/" oldhref="fn_exec_score.html" title="exec_score" /> <link rel="refentry" href="/virtuoso/fn_exp/" oldhref="fn_exp.html" title="exp" /> <link rel="refentry" href="/virtuoso/fn_explain/" oldhref="fn_explain.html" title="explain" /> <link rel="refentry" href="/virtuoso/fn_file_delete/" oldhref="fn_file_delete.html" title="file_delete" /> <link rel="refentry" href="/virtuoso/fn_file_open/" oldhref="fn_file_open.html" title="file_open" /> <link rel="refentry" href="/virtuoso/fn_ft_set_file/" oldhref="fn_ft_set_file.html" title="ft_set_file" /> <link rel="refentry" href="/virtuoso/fn_file_dirlist/" oldhref="fn_file_dirlist.html" title="file_dirlist" /> <link rel="refentry" href="/virtuoso/fn_file_mkdir/" oldhref="fn_file_mkdir.html" title="file_mkdir" /> <link rel="refentry" href="/virtuoso/fn_file_mkpath/" oldhref="fn_file_mkpath.html" title="file_mkpath" /> <link rel="refentry" href="/virtuoso/fn_file_stat/" oldhref="fn_file_stat.html" title="file_stat" /> <link rel="refentry" href="/virtuoso/fn_file_to_string/" oldhref="fn_file_to_string.html" title="file_to_string" /> <link rel="refentry" href="/virtuoso/fn_file_to_string_output/" oldhref="fn_file_to_string_output.html" title="file_to_string_output" /> <link rel="refentry" href="/virtuoso/fn_file_unlink/" oldhref="fn_file_unlink.html" title="file_unlink" /> <link rel="refentry" href="/virtuoso/fn_fk_check_input_values/" oldhref="fn_fk_check_input_values.html" title="fk_check_input_values" /> <link rel="refentry" href="/virtuoso/fn_floor/" oldhref="fn_floor.html" title="floor" /> <link rel="refentry" href="/virtuoso/fn_ftp_get/" oldhref="fn_ftp_get.html" title="ftp_get" /> <link rel="refentry" href="/virtuoso/fn_ftp_ls/" oldhref="fn_ftp_ls.html" title="ftp_ls" /> <link rel="refentry" href="/virtuoso/fn_ftp_put/" oldhref="fn_ftp_put.html" title="ftp_put" /> <link rel="refentry" href="/virtuoso/fn_gz_file_open/" oldhref="fn_gz_file_open.html" title="gz_file_open" /> <link rel="refentry" href="/virtuoso/fn_get_csv_row/" oldhref="fn_get_csv_row.html" title="get_csv_row" /> <link rel="refentry" href="/virtuoso/fn_csv_load_file/" oldhref="fn_csv_load_file.html" title="csv_load_file" /> <link rel="refentry" href="/virtuoso/fn_attach_from_csv/" oldhref="fn_attach_from_csv.html" title="attach_from_csv" /> <link rel="refentry" href="/virtuoso/fn_csv_load/" oldhref="fn_csv_load.html" title="csv_load" /> <link rel="refentry" href="/virtuoso/fn_csv_parse/" oldhref="fn_csv_parse.html" title="csv_parse" /> <link rel="refentry" href="/virtuoso/fn_csv_cols_def/" oldhref="fn_csv_cols_def.html" title="csv_cols_def" /> <link rel="refentry" href="/virtuoso/fn_csv_table_def/" oldhref="fn_csv_table_def.html" title="csv_table_def" /> <link rel="refentry" href="/virtuoso/fn_get_certificate_info/" oldhref="fn_get_certificate_info.html" title="get_certificate_info" /> <link rel="refentry" href="/virtuoso/fn_get_keyword/" oldhref="fn_get_keyword.html" title="get_keyword" /> <link rel="refentry" href="/virtuoso/fn_get_keyword_ucase/" oldhref="fn_get_keyword_ucase.html" title="get_keyword_ucase" /> <link rel="refentry" href="/virtuoso/fn_get_timestamp/" oldhref="fn_get_timestamp.html" title="get_timestamp" /> <link rel="refentry" href="/virtuoso/fn_getdate/" oldhref="fn_getdate.html" title="getdate" /> <link rel="refentry" href="/virtuoso/fn_gvector_sort/" oldhref="fn_gvector_sort.html" title="gvector_sort" /> <link rel="refentry" href="/virtuoso/fn_gvector_digit_sort/" oldhref="fn_gvector_digit_sort.html" title="gvector_digit_sort" /> <link rel="refentry" href="/virtuoso/fn_gz_compress/" oldhref="fn_gz_compress.html" title="gz_compress" /> <link rel="refentry" href="/virtuoso/fn_gz_uncompress/" oldhref="fn_gz_uncompress.html" title="gz_uncompress" /> <link rel="refentry" href="/virtuoso/fn_st_affine/" oldhref="fn_st_affine.html" title="ST_Affine" /> <link rel="refentry" href="/virtuoso/fn_st_point/" oldhref="fn_st_point.html" title="st_point" /> <link rel="refentry" href="/virtuoso/fn_st_x/" oldhref="fn_st_x.html" title="st_x" /> <link rel="refentry" href="/virtuoso/fn_st_y/" oldhref="fn_st_y.html" title="st_y" /> <link rel="refentry" href="/virtuoso/fn_st_distance/" oldhref="fn_st_distance.html" title="st_distance" /> <link rel="refentry" href="/virtuoso/fn_st_srid/" oldhref="fn_st_srid.html" title="ST_SRID" /> <link rel="refentry" href="/virtuoso/fn_st_setsrid/" oldhref="fn_st_setsrid.html" title="ST_SetSRID" /> <link rel="refentry" href="/virtuoso/fn_st_astext/" oldhref="fn_st_astext.html" title="st_astext" /> <link rel="refentry" href="/virtuoso/fn_st_geomfromtext/" oldhref="fn_st_geomfromtext.html" title="st_geomfromtext" /> <link rel="refentry" href="/virtuoso/fn_st_intersects/" oldhref="fn_st_intersects.html" title="st_intersects" /> <link rel="refentry" href="/virtuoso/fn_st_contains/" oldhref="fn_st_contains.html" title="st_contains" /> <link rel="refentry" href="/virtuoso/fn_st_within/" oldhref="fn_st_within.html" title="st_within" /> <link rel="refentry" href="/virtuoso/fn_isgeometry/" oldhref="fn_isgeometry.html" title="isgeometry" /> <link rel="refentry" href="/virtuoso/fn_geo_insert/" oldhref="fn_geo_insert.html" title="geo_insert" /> <link rel="refentry" href="/virtuoso/fn_geo_delete/" oldhref="fn_geo_delete.html" title="geo_delete" /> <link rel="refentry" href="/virtuoso/fn_hour/" oldhref="fn_hour.html" title="hour" /> <link rel="refentry" href="/virtuoso/fn_http/" oldhref="fn_http.html" title="http" /> <link rel="refentry" href="/virtuoso/fn_http_lock/" oldhref="fn_http_lock.html" title="http_lock" /> <link rel="refentry" href="/virtuoso/fn_http_unlock/" oldhref="fn_http_unlock.html" title="http_unlock" /> <link rel="refentry" href="/virtuoso/fn_http_acl_set/" oldhref="fn_http_acl_set.html" title="http_acl_set" /> <link rel="refentry" href="/virtuoso/fn_http_acl_get/" oldhref="fn_http_acl_get.html" title="http_acl_get" /> <link rel="refentry" href="/virtuoso/fn_http_acl_remove/" oldhref="fn_http_acl_remove.html" title="http_acl_remove" /> <link rel="refentry" href="/virtuoso/fn_http_body_read/" oldhref="fn_http_body_read.html" title="http_body_read" /> <link rel="refentry" href="/virtuoso/fn_http_client/" oldhref="fn_http_client.html" title="http_client" /> <link rel="refentry" href="/virtuoso/fn_http_client_ext/" oldhref="fn_http_client_ext.html" title="http_client_ext" /> <link rel="refentry" href="/virtuoso/fn_http_client_ip/" oldhref="fn_http_client_ip.html" title="http_client_ip" /> <link rel="refentry" href="/virtuoso/fn_dns_txt_get/" oldhref="fn_dns_txt_get.html" title="dns_txt_get" /> <link rel="refentry" href="/virtuoso/fn_http_debug_log/" oldhref="fn_http_debug_log.html" title="http_debug_log" /> <link rel="refentry" href="/virtuoso/fn_http_enable_gz/" oldhref="fn_http_enable_gz.html" title="http_enable_gz" /> <link rel="refentry" href="/virtuoso/fn_http_file/" oldhref="fn_http_file.html" title="http_file" /> <link rel="refentry" href="/virtuoso/fn_http_flush/" oldhref="fn_http_flush.html" title="http_flush" /> <link rel="refentry" href="/virtuoso/fn_http_internal_redirect/" oldhref="fn_http_internal_redirect.html" title="http_internal_redirect" /> <link rel="refentry" href="/virtuoso/fn_http_get/" oldhref="fn_http_get.html" title="http_get" /> <link rel="refentry" href="/virtuoso/fn_http_header/" oldhref="fn_http_header.html" title="http_header" /> <link rel="refentry" href="/virtuoso/fn_http_header_get/" oldhref="fn_http_header_get.html" title="http_header_get" /> <link rel="refentry" href="/virtuoso/fn_http_kill/" oldhref="fn_http_kill.html" title="http_kill" /> <link rel="refentry" href="/virtuoso/fn_http_listen_host/" oldhref="fn_http_listen_host.html" title="http_listen_host" /> <link rel="refentry" href="/virtuoso/fn_http_map_table/" oldhref="fn_http_map_table.html" title="http_map_table" /> <link rel="refentry" href="/virtuoso/fn_http_map_get/" oldhref="fn_http_map_get.html" title="http_map_get" /> <link rel="refentry" href="/virtuoso/fn_http_param/" oldhref="fn_http_param.html" title="http_param" /> <link rel="refentry" href="/virtuoso/fn_http_path/" oldhref="fn_http_path.html" title="http_path" /> <link rel="refentry" href="/virtuoso/fn_http_pending_req/" oldhref="fn_http_pending_req.html" title="http_pending_req" /> <link rel="refentry" href="/virtuoso/fn_http_physical_path/" oldhref="fn_http_physical_path.html" title="http_physical_path" /> <link rel="refentry" href="/virtuoso/fn_http_proxy/" oldhref="fn_http_proxy.html" title="http_proxy" /> <link rel="refentry" href="/virtuoso/fn_http_request_header/" oldhref="fn_http_request_header.html" title="http_request_header" /> <link rel="refentry" href="/virtuoso/fn_http_request_header_full/" oldhref="fn_http_request_header_full.html" title="http_request_header_full" /> <link rel="refentry" href="/virtuoso/fn_http_request_status/" oldhref="fn_http_request_status.html" title="http_request_status" /> <link rel="refentry" href="/virtuoso/fn_http_request_get/" oldhref="fn_http_request_get.html" title="http_request_get" /> <link rel="refentry" href="/virtuoso/fn_http_rewrite/" oldhref="fn_http_rewrite.html" title="http_rewrite" /> <link rel="refentry" href="/virtuoso/fn_http_root/" oldhref="fn_http_root.html" title="http_root" /> <link rel="refentry" href="/virtuoso/fn_http_value/" oldhref="fn_http_value.html" title="http_value" /> <link rel="refentry" href="/virtuoso/fn_json_parse/" oldhref="fn_json_parse.html" title="json_parse" /> <link rel="refentry" href="/virtuoso/fn_http_url/" oldhref="fn_http_url.html" title="http_url" /> <link rel="refentry" href="/virtuoso/fn_http_xslt/" oldhref="fn_http_xslt.html" title="http_xslt" /> <link rel="refentry" href="/virtuoso/fn_urlrewrite_create_regex_rule/" oldhref="fn_urlrewrite_create_regex_rule.html" title="URLREWRITE_CREATE_REGEX_RULE" /> <link rel="refentry" href="/virtuoso/fn_identity_value/" oldhref="fn_identity_value.html" title="identity_value" /> <link rel="refentry" href="/virtuoso/fn_import_clr/" oldhref="fn_import_clr.html" title="import_clr" /> <link rel="refentry" href="/virtuoso/fn_import_jar/" oldhref="fn_import_jar.html" title="import_jar" /> <link rel="refentry" href="/virtuoso/fn_initcap/" oldhref="fn_initcap.html" title="initcap" /> <link rel="refentry" href="/virtuoso/fn_internal_to_sql_type/" oldhref="fn_internal_to_sql_type.html" title="internal_to_sql_type" /> <link rel="refentry" href="/virtuoso/fn_internal_type/" oldhref="fn_internal_type.html" title="internal_type" /> <link rel="refentry" href="/virtuoso/fn_internal_type_name/" oldhref="fn_internal_type_name.html" title="internal_type_name" /> <link rel="refentry" href="/virtuoso/fn_isarray/" oldhref="fn_isarray.html" title="isarray" /> <link rel="refentry" href="/virtuoso/fn_isblob/" oldhref="fn_isblob.html" title="isblob" /> <link rel="refentry" href="/virtuoso/fn_isbinary/" oldhref="fn_isbinary.html" title="isbinary" /> <link rel="refentry" href="/virtuoso/fn_isdouble/" oldhref="fn_isdouble.html" title="isdouble" /> <link rel="refentry" href="/virtuoso/fn_isentity/" oldhref="fn_isentity.html" title="isentity" /> <link rel="refentry" href="/virtuoso/fn_isfloat/" oldhref="fn_isfloat.html" title="isfloat" /> <link rel="refentry" href="/virtuoso/fn_isinteger/" oldhref="fn_isinteger.html" title="isinteger" /> <link rel="refentry" href="/virtuoso/fn_isnull/" oldhref="fn_isnull.html" title="isnull" /> <link rel="refentry" href="/virtuoso/fn_isnumeric/" oldhref="fn_isnumeric.html" title="isnumeric" /> <link rel="refentry" href="/virtuoso/fn_isfinitenumeric/" oldhref="fn_isfinitenumeric.html" title="isfinitenumeric" /> <link rel="refentry" href="/virtuoso/fn_isstring/" oldhref="fn_isstring.html" title="isstring" /> <link rel="refentry" href="/virtuoso/fn_iszero/" oldhref="fn_iszero.html" title="iszero" /> <link rel="refentry" href="/virtuoso/fn_nm_min/" oldhref="fn_nm_min.html" title="__min" /> <link rel="refentry" href="/virtuoso/fn_nm_max/" oldhref="fn_nm_max.html" title="__max" /> <link rel="refentry" href="/virtuoso/fn_nm_max_notnull/" oldhref="fn_nm_max_notnull.html" title="__max_notnull" /> <link rel="refentry" href="/virtuoso/fn_nm_min_notnull/" oldhref="fn_nm_min_notnull.html" title="__min_notnull" /> <link rel="refentry" href="/virtuoso/fn_java_call_method/" oldhref="fn_java_call_method.html" title="java_call_method" /> <link rel="refentry" href="/virtuoso/fn_java_set_property/" oldhref="fn_java_set_property.html" title="java_set_property" /> <link rel="refentry" href="/virtuoso/fn_java_get_property/" oldhref="fn_java_get_property.html" title="java_get_property" /> <link rel="refentry" href="/virtuoso/fn_java_load_class/" oldhref="fn_java_load_class.html" title="java_load_class" /> <link rel="refentry" href="/virtuoso/fn_java_new_object/" oldhref="fn_java_new_object.html" title="java_new_object" /> <link rel="refentry" href="/virtuoso/fn_java_vm_attach/" oldhref="fn_java_vm_attach.html" title="java_vm_attach" /> <link rel="refentry" href="/virtuoso/fn_java_vm_detach/" oldhref="fn_java_vm_detach.html" title="java_vm_detach" /> <link rel="refentry" href="/virtuoso/fn_jvm_ref_import/" oldhref="fn_jvm_ref_import.html" title="jvm_ref_import" /> <link rel="refentry" href="/virtuoso/fn_lcase/" oldhref="fn_lcase.html" title="lcase" /> <link rel="refentry" href="/virtuoso/fn_ldap_search/" oldhref="fn_ldap_search.html" title="ldap_search" /> <link rel="refentry" href="/virtuoso/fn_ldap_delete/" oldhref="fn_ldap_delete.html" title="ldap_delete" /> <link rel="refentry" href="/virtuoso/fn_ldap_add/" oldhref="fn_ldap_add.html" title="ldap_add" /> <link rel="refentry" href="/virtuoso/fn_ldap_modify/" oldhref="fn_ldap_modify.html" title="ldap_modify" /> <link rel="refentry" href="/virtuoso/fn_left/" oldhref="fn_left.html" title="left" /> <link rel="refentry" href="/virtuoso/fn_length/" oldhref="fn_length.html" title="length" /> <link rel="refentry" href="/virtuoso/fn_lfs_exp/" oldhref="fn_lfs_exp.html" title="LFS_EXP" /> <link rel="refentry" href="/virtuoso/fn_lh_get_handler/" oldhref="fn_lh_get_handler.html" title="lh_get_handler" /> <link rel="refentry" href="/virtuoso/fn_lh_load_handler/" oldhref="fn_lh_load_handler.html" title="lh_load_handler" /> <link rel="refentry" href="/virtuoso/fn_locate/" oldhref="fn_locate.html" title="locate" /> <link rel="refentry" href="/virtuoso/fn_log/" oldhref="fn_log.html" title="log" /> <link rel="refentry" href="/virtuoso/fn_log10/" oldhref="fn_log10.html" title="log10" /> <link rel="refentry" href="/virtuoso/fn_log_enable/" oldhref="fn_log_enable.html" title="log_enable" /> <link rel="refentry" href="/virtuoso/fn_log_message/" oldhref="fn_log_message.html" title="log_message" /> <link rel="refentry" href="/virtuoso/fn_log_text/" oldhref="fn_log_text.html" title="log_text" /> <link rel="refentry" href="/virtuoso/fn_read_log/" oldhref="fn_read_log.html" title="read_log" /> <link rel="refentry" href="/virtuoso/fn_lower/" oldhref="fn_lower.html" title="lower" /> <link rel="refentry" href="/virtuoso/fn_ltrim/" oldhref="fn_ltrim.html" title="ltrim" /> <link rel="refentry" href="/virtuoso/fn_dbf_set/" oldhref="fn_dbf_set.html" title="__dbf_set" /> <link rel="refentry" href="/virtuoso/fn_stat_import/" oldhref="fn_stat_import.html" title="stat_import" /> <link rel="refentry" href="/virtuoso/fn_stat_export/" oldhref="fn_stat_export.html" title="stat_export" /> <link rel="refentry" href="/virtuoso/fn_make_array/" oldhref="fn_make_array.html" title="make_array" /> <link rel="refentry" href="/virtuoso/fn_make_string/" oldhref="fn_make_string.html" title="make_string" /> <link rel="refentry" href="/virtuoso/fn_md5/" oldhref="fn_md5.html" title="md5" /> <link rel="refentry" href="/virtuoso/fn_md5_init/" oldhref="fn_md5_init.html" title="md5_init" /> <link rel="refentry" href="/virtuoso/fn_md5_update/" oldhref="fn_md5_update.html" title="md5_update" /> <link rel="refentry" href="/virtuoso/fn_md5_final/" oldhref="fn_md5_final.html" title="md5_final" /> <link rel="refentry" href="/virtuoso/fn_mime_body/" oldhref="fn_mime_body.html" title="mime_body" /> <link rel="refentry" href="/virtuoso/fn_mime_part/" oldhref="fn_mime_part.html" title="mime_part" /> <link rel="refentry" href="/virtuoso/fn_mime_tree/" oldhref="fn_mime_tree.html" title="mime_tree" /> <link rel="refentry" href="/virtuoso/fn_minute/" oldhref="fn_minute.html" title="minute" /> <link rel="refentry" href="/virtuoso/fn_mod/" oldhref="fn_mod.html" title="mod" /> <link rel="refentry" href="/virtuoso/fn_month/" oldhref="fn_month.html" title="month" /> <link rel="refentry" href="/virtuoso/fn_monthname/" oldhref="fn_monthname.html" title="monthname" /> <link rel="refentry" href="/virtuoso/fn_msec_time/" oldhref="fn_msec_time.html" title="msec_time" /> <link rel="refentry" href="/virtuoso/fn_mts_connect/" oldhref="fn_mts_connect.html" title="mts_connect" /> <link rel="refentry" href="/virtuoso/fn_mts_get_timeout/" oldhref="fn_mts_get_timeout.html" title="mts_get_timeout" /> <link rel="refentry" href="/virtuoso/fn_mts_set_timeout/" oldhref="fn_mts_set_timeout.html" title="mts_set_timeout" /> <link rel="refentry" href="/virtuoso/fn_mts_status/" oldhref="fn_mts_status.html" title="mts_status" /> <link rel="refentry" href="/virtuoso/fn_sha1_digest/" oldhref="fn_sha1_digest.html" title="sha1_digest" /> <link rel="refentry" href="/virtuoso/fn_name_part/" oldhref="fn_name_part.html" title="name_part" /> <link rel="refentry" href="/virtuoso/fn_nntp_auth_get/" oldhref="fn_nntp_auth_get.html" title="nntp_auth_get" /> <link rel="refentry" href="/virtuoso/fn_nntp_auth_post/" oldhref="fn_nntp_auth_post.html" title="nntp_auth_post" /> <link rel="refentry" href="/virtuoso/fn_nntp_get/" oldhref="fn_nntp_get.html" title="nntp_get" /> <link rel="refentry" href="/virtuoso/fn_nntp_post/" oldhref="fn_nntp_post.html" title="nntp_post" /> <link rel="refentry" href="/virtuoso/fn_now/" oldhref="fn_now.html" title="now" /> <link rel="refentry" href="/virtuoso/fn_amazon_start_instance/" oldhref="fn_amazon_start_instance.html" title="DB.DBA.AMAZON_START_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_run_instance/" oldhref="fn_amazon_run_instance.html" title="DB.DBA.AMAZON_RUN_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_stop_instance/" oldhref="fn_amazon_stop_instance.html" title="DB.DBA.AMAZON_STOP_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_terminate_instance/" oldhref="fn_amazon_terminate_instance.html" title="DB.DBA.AMAZON_TERMINATE_INSTANCE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_volume/" oldhref="fn_amazon_create_volume.html" title="DB.DBA.AMAZON_CREATE_VOLUME" /> <link rel="refentry" href="/virtuoso/fn_amazon_deregister_image/" oldhref="fn_amazon_deregister_image.html" title="DB.DBA.AMAZON_DEREGISTER_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_image/" oldhref="fn_amazon_create_image.html" title="DB.DBA.AMAZON_CREATE_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_amazon_create_snapshot/" oldhref="fn_amazon_create_snapshot.html" title="DB.DBA.AMAZON_CREATE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_amazon_delete_snapshot/" oldhref="fn_amazon_delete_snapshot.html" title="DB.DBA.AMAZON_DELETE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_amazon_delete_volume/" oldhref="fn_amazon_delete_volume.html" title="DB.DBA.AMAZON_DELETE_VOLUME" /> <link rel="refentry" href="/virtuoso/fn_amazon_describe_images/" oldhref="fn_amazon_describe_images.html" title="DB.DBA.AMAZON_DESCRIBE_IMAGES" /> <link rel="refentry" href="/virtuoso/fn_amazon_describe_instances/" oldhref="fn_amazon_describe_instances.html" title="DB.DBA.AMAZON_DESCRIBE_INSTANCES" /> <link rel="refentry" href="/virtuoso/fn_amazon_import_key_pair/" oldhref="fn_amazon_import_key_pair.html" title="DB.DBA.AMAZON_IMPORT_KEY_PAIR" /> <link rel="refentry" href="/virtuoso/fn_os_chmod/" oldhref="fn_os_chmod.html" title="os_chmod" /> <link rel="refentry" href="/virtuoso/fn_os_chown/" oldhref="fn_os_chown.html" title="os_chown" /> <link rel="refentry" href="/virtuoso/fn_pem_certificates_to_array/" oldhref="fn_pem_certificates_to_array.html" title="pem_certificates_to_array" /> <link rel="refentry" href="/virtuoso/fn_pldbg_stats/" oldhref="fn_pldbg_stats.html" title="pldbg_stats" /> <link rel="refentry" href="/virtuoso/fn_pldbg_stats_load/" oldhref="fn_pldbg_stats_load.html" title="pldbg_stats_load" /> <link rel="refentry" href="/virtuoso/fn_pop3_get/" oldhref="fn_pop3_get.html" title="pop3_get" /> <link rel="refentry" href="/virtuoso/fn_imap_get/" oldhref="fn_imap_get.html" title="imap_get" /> <link rel="refentry" href="/virtuoso/fn_position/" oldhref="fn_position.html" title="position" /> <link rel="refentry" href="/virtuoso/fn_power/" oldhref="fn_power.html" title="power" /> <link rel="refentry" href="/virtuoso/fn_prof_enable/" oldhref="fn_prof_enable.html" title="prof_enable" /> <link rel="refentry" href="/virtuoso/fn_prof_sample/" oldhref="fn_prof_sample.html" title="prof_sample" /> <link rel="refentry" href="/virtuoso/fn_quarter/" oldhref="fn_quarter.html" title="quarter" /> <link rel="refentry" href="/virtuoso/fn_quote_dotted/" oldhref="fn_quote_dotted.html" title="quote_dotted" /> <link rel="refentry" href="/virtuoso/fn_randomize/" oldhref="fn_randomize.html" title="randomize" /> <link rel="refentry" href="/virtuoso/fn_rclose/" oldhref="fn_rclose.html" title="rclose" /> <link rel="refentry" href="/virtuoso/fn_regexp_match/" oldhref="fn_regexp_match.html" title="regexp_match" /> <link rel="refentry" href="/virtuoso/fn_regexp_parse/" oldhref="fn_regexp_parse.html" title="regexp_parse" /> <link rel="refentry" href="/virtuoso/fn_regexp_substr/" oldhref="fn_regexp_substr.html" title="regexp_substr" /> <link rel="refentry" href="/virtuoso/fn_rdf_audit_metadata/" oldhref="fn_rdf_audit_metadata.html" title="DB.DBA.RDF_AUDIT_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_security_audit/" oldhref="fn_rdf_graph_security_audit.html" title="DB.DBA.RDF_GRAPH_SECURITY_AUDIT" /> <link rel="refentry" href="/virtuoso/fn_rdf_default_user_perms_set/" oldhref="fn_rdf_default_user_perms_set.html" title="DB.DBA.RDF_DEFAULT_USER_PERMS_SET" /> <link rel="refentry" href="/virtuoso/fn_rdf_default_user_perms_del/" oldhref="fn_rdf_default_user_perms_del.html" title="DB.DBA.RDF_DEFAULT_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdf_backup_metadata/" oldhref="fn_rdf_backup_metadata.html" title="DB.DBA.RDF_BACKUP_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_void_store/" oldhref="fn_rdf_void_store.html" title="DB.DBA.RDF_VOID_STORE" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_stop/" oldhref="fn_rdf_load_stop.html" title="rdf_load_stop" /> <link rel="refentry" href="/virtuoso/fn_rdf_loader_run/" oldhref="fn_rdf_loader_run.html" title="rdf_loader_run" /> <link rel="refentry" href="/virtuoso/fn_ld_dir_all/" oldhref="fn_ld_dir_all.html" title="ld_dir_all" /> <link rel="refentry" href="/virtuoso/fn_rdf_restore_metadata/" oldhref="fn_rdf_restore_metadata.html" title="DB.DBA.RDF_RESTORE_METADATA" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfxml_mt/" oldhref="fn_rdf_load_rdfxml_mt.html" title="DB.DBA.RDF_LOAD_RDFXML_MT" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfxml/" oldhref="fn_rdf_load_rdfxml.html" title="DB.DBA.RDF_LOAD_RDFXML" /> <link rel="refentry" href="/virtuoso/fn_rdf_load_rdfa/" oldhref="fn_rdf_load_rdfa.html" title="DB.DBA.RDF_LOAD_RDFA" /> <link rel="refentry" href="/virtuoso/fn_ld_dir/" oldhref="fn_ld_dir.html" title="ld_dir" /> <link rel="refentry" href="/virtuoso/fn_ttlp/" oldhref="fn_ttlp.html" title="DB.DBA.TTLP" /> <link rel="refentry" href="/virtuoso/fn_ttlp_mt/" oldhref="fn_ttlp_mt.html" title="DB.DBA.TTLP_MT" /> <link rel="refentry" href="/uda/mt/fn_ttlp_mt_local_file/" oldhref="fn_ttlp_mt_local_file.html" title="DB.DBA.TTLP_MT_LOCAL_FILE" /> <link rel="refentry" href="/virtuoso/fn_rdf_datatype_of_obj/" oldhref="fn_rdf_datatype_of_obj.html" title="DB.DBA.RDF_DATATYPE_OF_OBJ" /> <link rel="refentry" href="/virtuoso/fn_rdf_triples_to_rdf_xml_text/" oldhref="fn_rdf_triples_to_rdf_xml_text.html" title="DB.DBA.RDF_TRIPLES_TO_RDF_XML_TEXT" /> <link rel="refentry" href="/virtuoso/fn_rdf_triples_to_ttl/" oldhref="fn_rdf_triples_to_ttl.html" title="DB.DBA.RDF_TRIPLES_TO_TTL" /> <link rel="refentry" href="/virtuoso/fn_rdf_64bit_upgrade/" oldhref="fn_rdf_64bit_upgrade.html" title="DB.DBA.RDF_64BIT_UPGRADE" /> <link rel="refentry" href="/virtuoso/fn_rdf_view_sync_to_physical/" oldhref="fn_rdf_view_sync_to_physical.html" title="RDF_VIEW_SYNC_TO_PHYSICAL" /> <link rel="refentry" href="/virtuoso/fn_rdf_convert_rdfxml_to_ttl/" oldhref="fn_rdf_convert_rdfxml_to_ttl.html" title="DB.DBA.RDF_CONVERT_RDFXML_TO_TTL" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_group_create/" oldhref="fn_rdf_graph_group_create.html" title="DB.DBA.RDF_GRAPH_GROUP_CREATE" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_group_ins/" oldhref="fn_rdf_graph_group_ins.html" title="DB.DBA.RDF_GRAPH_GROUP_INS" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_set/" oldhref="fn_rdf_graph_user_perms_set.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_SET" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_get/" oldhref="fn_rdf_graph_user_perms_get.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_GET" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_user_perms_del/" oldhref="fn_rdf_graph_user_perms_del.html" title="DB.DBA.RDF_GRAPH_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdf_all_user_perms_del/" oldhref="fn_rdf_all_user_perms_del.html" title="DB.DBA.RDF_ALL_USER_PERMS_DEL" /> <link rel="refentry" href="/virtuoso/fn_rdfs_rule_set/" oldhref="fn_rdfs_rule_set.html" title="rdfs_rule_set" /> <link rel="refentry" href="/virtuoso/fn_rdf_geo_fill/" oldhref="fn_rdf_geo_fill.html" title="DB.DBA.RDF_GEO_FILL" /> <link rel="refentry" href="/virtuoso/fn_rdf_geo_add/" oldhref="fn_rdf_geo_add.html" title="DB.DBA.RDF_GEO_ADD" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_collect_fp_list/" oldhref="fn_rdf_graph_collect_fp_list.html" title="DB.DBA.RDF_GRAPH_COLLECT_FP_LIST" /> <link rel="refentry" href="/virtuoso/fn_rdf_graph_diff/" oldhref="fn_rdf_graph_diff.html" title="DB.DBA.RDF_GRAPH_DIFF" /> <link rel="refentry" href="/virtuoso/fn_rdf_suo_apply_patch/" oldhref="fn_rdf_suo_apply_patch.html" title="DB.DBA.RDF_SUO_APPLY_PATCH" /> <link rel="refentry" href="/virtuoso/fn_rdf_suo_diff_ttl/" oldhref="fn_rdf_suo_diff_ttl.html" title="DB.DBA.RDF_SUO_DIFF_TTL" /> <link rel="refentry" href="/virtuoso/fn_sparql_rdb2rdf_codegen/" oldhref="fn_sparql_rdb2rdf_codegen.html" title="DB.DBA.SPARQL_RDB2RDF_CODEGEN" /> <link rel="refentry" href="/virtuoso/fn_sparql_rdb2rdf_list_tables/" oldhref="fn_sparql_rdb2rdf_list_tables.html" title="DB.DBA.SPARQL_RDB2RDF_LIST_TABLES" /> <link rel="refentry" href="/virtuoso/fn_sparql_select_known_graphs/" oldhref="fn_sparql_select_known_graphs.html" title="DB.DBA.SPARQL_SELECT_KNOWN_GRAPHS" /> <link rel="refentry" href="/virtuoso/fn_rowvector_digit_sort/" oldhref="fn_rowvector_digit_sort.html" title="rowvector_digit_sort" /> <link rel="refentry" href="/virtuoso/fn_isref/" oldhref="fn_isref.html" title="IsRef" /> <link rel="refentry" href="/virtuoso/fn_sample/" oldhref="fn_sample.html" title="DB.DBA.SAMPLE" /> <link rel="refentry" href="/virtuoso/fn_group_concat/" oldhref="fn_group_concat.html" title="DB.DBA.GROUP_CONCAT" /> <link rel="refentry" href="/virtuoso/fn_group_concat_distinct/" oldhref="fn_group_concat_distinct.html" title="DB.DBA.GROUP_CONCAT_DISTINCT" /> <link rel="refentry" href="/virtuoso/fn_group_digest/" oldhref="fn_group_digest.html" title="DB.DBA.GROUP_DIGEST" /> <link rel="refentry" href="/virtuoso/fn_http_nt_triple/" oldhref="fn_http_nt_triple.html" title="http_nt_triple" /> <link rel="refentry" href="/virtuoso/fn_http_ttl_triple/" oldhref="fn_http_ttl_triple.html" title="http_ttl_triple" /> <link rel="refentry" href="/virtuoso/fn_ann_phrase_class_add/" oldhref="fn_ann_phrase_class_add.html" title="DB.DBA.ANN_PHRASE_CLASS_ADD" /> <link rel="refentry" href="/virtuoso/fn_ann_phrase_class_del/" oldhref="fn_ann_phrase_class_del.html" title="DB.DBA.ANN_PHRASE_CLASS_DEL" /> <link rel="refentry" href="/virtuoso/fn_ap_build_match_list/" oldhref="fn_ap_build_match_list.html" title="AP_BUILD_MATCH_LIST" /> <link rel="refentry" href="/virtuoso/fn_ap_add_phrases/" oldhref="fn_ap_add_phrases.html" title="AP_ADD_PHRASES" /> <link rel="refentry" href="/virtuoso/fn_iri_split/" oldhref="fn_iri_split.html" title="iri_split" /> <link rel="refentry" href="/virtuoso/fn___xml_get_ns_prefix/" oldhref="fn___xml_get_ns_prefix.html" title="__xml_get_ns_prefix" /> <link rel="refentry" href="/virtuoso/fn___xml_get_ns_uri/" oldhref="fn___xml_get_ns_uri.html" title="__xml_get_ns_uri" /> <link rel="refentry" href="/virtuoso/fn___xml_ns_uname/" oldhref="fn___xml_ns_uname.html" title="__xml_ns_uname" /> <link rel="refentry" href="/virtuoso/fn___xml_ns_iristr/" oldhref="fn___xml_ns_iristr.html" title="__xml_ns_iristr" /> <link rel="refentry" href="/virtuoso/fn___xml_nsexpand_iristr/" oldhref="fn___xml_nsexpand_iristr.html" title="__xml_nsexpand_iristr" /> <link rel="refentry" href="/virtuoso/fn_sparql_eval/" oldhref="fn_sparql_eval.html" title="DB.DBA.SPARQL_EVAL" /> <link rel="refentry" href="/virtuoso/fn_sparql_eval_to_array/" oldhref="fn_sparql_eval_to_array.html" title="DB.DBA.SPARQL_EVAL_TO_ARRAY" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec/" oldhref="fn_sparql_rexec.html" title="DB.DBA.SPARQL_REXEC" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec_to_array/" oldhref="fn_sparql_rexec_to_array.html" title="DB.DBA.SPARQL_REXEC_TO_ARRAY" /> <link rel="refentry" href="/virtuoso/fn_sparql_rexec_with_meta/" oldhref="fn_sparql_rexec_with_meta.html" title="DB.DBA.SPARQL_REXEC_WITH_META" /> <link rel="refentry" href="/virtuoso/fn_rdf_regex/" oldhref="fn_rdf_regex.html" title="DB.DBA.RDF_REGEX" /> <link rel="refentry" href="/virtuoso/fn_rdf_langmatches/" oldhref="fn_rdf_langmatches.html" title="DB.DBA.RDF_LANGMATCHES" /> <link rel="refentry" href="/virtuoso/fn_rdf_ttl2hash/" oldhref="fn_rdf_ttl2hash.html" title="DB.DBA.RDF_TTL2HASH" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri/" oldhref="fn_rdf_quad_uri.html" title="DB.DBA.RDF_QUAD_URI" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri_l/" oldhref="fn_rdf_quad_uri_l.html" title="DB.DBA.RDF_QUAD_URI_L" /> <link rel="refentry" href="/virtuoso/fn_rdf_quad_uri_l_typed/" oldhref="fn_rdf_quad_uri_l_typed.html" title="DB.DBA.RDF_QUAD_URI_L_TYPED" /> <link rel="refentry" href="/virtuoso/fn_regexp_replace/" oldhref="fn_regexp_replace.html" title="regexp_replace" /> <link rel="refentry" href="/virtuoso/fn_regexp_instr/" oldhref="fn_regexp_instr.html" title="regexp_instr" /> <link rel="refentry" href="/virtuoso/fn_regexp_like/" oldhref="fn_regexp_like.html" title="regexp_like" /> <link rel="refentry" href="/virtuoso/fn_registry_get/" oldhref="fn_registry_get.html" title="registry_get" /> <link rel="refentry" href="/virtuoso/fn_registry_get_all/" oldhref="fn_registry_get_all.html" title="registry_get_all" /> <link rel="refentry" href="/virtuoso/fn_registry_name_is_protected/" oldhref="fn_registry_name_is_protected.html" title="registry_name_is_protected" /> <link rel="refentry" href="/virtuoso/fn_registry_set/" oldhref="fn_registry_set.html" title="registry_set" /> <link rel="refentry" href="/virtuoso/fn_registry_remove/" oldhref="fn_registry_remove.html" title="registry_remove" /> <link rel="refentry" href="/virtuoso/fn_repeat/" oldhref="fn_repeat.html" title="repeat" /> <link rel="refentry" href="/virtuoso/fn_replace/" oldhref="fn_replace.html" title="replace" /> <link rel="refentry" href="/virtuoso/fn_replay/" oldhref="fn_replay.html" title="replay" /> <link rel="refentry" href="/virtuoso/fn_repl_disconnect/" oldhref="fn_repl_disconnect.html" title="repl_disconnect" /> <link rel="refentry" href="/virtuoso/fn_repl_grant/" oldhref="fn_repl_grant.html" title="REPL_GRANT" /> <link rel="refentry" href="/virtuoso/fn_repl_init_copy/" oldhref="fn_repl_init_copy.html" title="REPL_INIT_COPY" /> <link rel="refentry" href="/virtuoso/fn_repl_new_log/" oldhref="fn_repl_new_log.html" title="repl_new_log" /> <link rel="refentry" href="/virtuoso/fn_repl_publish/" oldhref="fn_repl_publish.html" title="REPL_PUBLISH" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_add/" oldhref="fn_repl_pub_add.html" title="REPL_PUB_ADD" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_init_image/" oldhref="fn_repl_pub_init_image.html" title="REPL_PUB_INIT_IMAGE" /> <link rel="refentry" href="/virtuoso/fn_repl_pub_remove/" oldhref="fn_repl_pub_remove.html" title="REPL_PUB_REMOVE" /> <link rel="refentry" href="/virtuoso/fn_repl_revoke/" oldhref="fn_repl_revoke.html" title="REPL_REVOKE" /> <link rel="refentry" href="/virtuoso/fn_repl_sched_init/" oldhref="fn_repl_sched_init.html" title="REPL_SCHED_INIT" /> <link rel="refentry" href="/virtuoso/fn_repl_server/" oldhref="fn_repl_server.html" title="REPL_SERVER" /> <link rel="refentry" href="/virtuoso/fn_repl_server_rename/" oldhref="fn_repl_server_rename.html" title="repl_server_rename" /> <link rel="refentry" href="/virtuoso/fn_repl_stat/" oldhref="fn_repl_stat.html" title="REPL_STAT" /> <link rel="refentry" href="/virtuoso/fn_repl_status/" oldhref="fn_repl_status.html" title="repl_status" /> <link rel="refentry" href="/virtuoso/fn_repl_subscribe/" oldhref="fn_repl_subscribe.html" title="REPL_SUBSCRIBE" /> <link rel="refentry" href="/virtuoso/fn_repl_sync/" oldhref="fn_repl_sync.html" title="repl_sync" /> <link rel="refentry" href="/virtuoso/fn_repl_sync_all/" oldhref="fn_repl_sync_all.html" title="repl_sync_all" /> <link rel="refentry" href="/virtuoso/fn_repl_text/" oldhref="fn_repl_text.html" title="repl_text" /> <link rel="refentry" href="/virtuoso/fn_repl_this_server/" oldhref="fn_repl_this_server.html" title="repl_this_server" /> <link rel="refentry" href="/virtuoso/fn_repl_unpublish/" oldhref="fn_repl_unpublish.html" title="REPL_UNPUBLISH" /> <link rel="refentry" href="/virtuoso/fn_repl_unsubscribe/" oldhref="fn_repl_unsubscribe.html" title="REPL_UNSUBSCRIBE" /> <link rel="refentry" href="/virtuoso/fn_repl_purge/" oldhref="fn_repl_purge.html" title="repl_purge" /> <link rel="refentry" href="/virtuoso/fn_repl_create_snapshot_pub/" oldhref="fn_repl_create_snapshot_pub.html" title="REPL_CREATE_SNAPSHOT_PUB" /> <link rel="refentry" href="/virtuoso/fn_repl_create_snapshot_sub/" oldhref="fn_repl_create_snapshot_sub.html" title="REPL_CREATE_SNAPSHOT_SUB" /> <link rel="refentry" href="/virtuoso/fn_repl_drop_snapshot_sub/" oldhref="fn_repl_drop_snapshot_sub.html" title="REPL_DROP_SNAPSHOT_SUB" /> <link rel="refentry" href="/virtuoso/fn_repl_drop_snapshot_pub/" oldhref="fn_repl_drop_snapshot_pub.html" title="REPL_DROP_SNAPSHOT_PUB" /> <link rel="refentry" href="/virtuoso/fn_repl_init_snapshot/" oldhref="fn_repl_init_snapshot.html" title="REPL_INIT_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_repl_update_snapshot/" oldhref="fn_repl_update_snapshot.html" title="REPL_UPDATE_SNAPSHOT" /> <link rel="refentry" href="/virtuoso/fn_repl_snp_server/" oldhref="fn_repl_snp_server.html" title="REPL_SNP_SERVER" /> <link rel="refentry" href="/virtuoso/fn_repl_server_name/" oldhref="fn_repl_server_name.html" title="REPL_SERVER_NAME" /> <link rel="refentry" href="/virtuoso/fn_repl_add_cr/" oldhref="fn_repl_add_cr.html" title="REPL_ADD_CR" /> <link rel="refentry" href="/virtuoso/fn_repl_add_dav_cr/" oldhref="fn_repl_add_dav_cr.html" title="REPL_ADD_DAV_CR" /> <link rel="refentry" href="/virtuoso/fn_repl_add_snapshot_cr/" oldhref="fn_repl_add_snapshot_cr.html" title="REPL_ADD_SNAPSHOT_CR" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_start/" oldhref="fn_rdf_repl_start.html" title="RDF_REPL_START" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_stop/" oldhref="fn_rdf_repl_stop.html" title="RDF_REPL_STOP" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_sync/" oldhref="fn_rdf_repl_sync.html" title="RDF_REPL_SYNC" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_graph_ins/" oldhref="fn_rdf_repl_graph_ins.html" title="RDF_REPL_GRAPH_INS" /> <link rel="refentry" href="/virtuoso/fn_rdf_repl_graph_del/" oldhref="fn_rdf_repl_graph_del.html" title="RDF_REPL_GRAPH_DEL" /> <link rel="refentry" href="/virtuoso/fn_result/" oldhref="fn_result.html" title="result" /> <link rel="refentry" href="/virtuoso/fn_result_names/" oldhref="fn_result_names.html" title="result_names" /> <link rel="refentry" href="/virtuoso/fn_rexecute/" oldhref="fn_rexecute.html" title="rexecute" /> <link rel="refentry" href="/virtuoso/fn_rstmtexec/" oldhref="fn_rstmtexec.html" title="rstmtexec" /> <link rel="refentry" href="/virtuoso/fn_right/" oldhref="fn_right.html" title="right" /> <link rel="refentry" href="/virtuoso/fn_rmoreresults/" oldhref="fn_rmoreresults.html" title="rmoreresults" /> <link rel="refentry" href="/virtuoso/fn_rnd/" oldhref="fn_rnd.html" title="rnd" /> <link rel="refentry" href="/virtuoso/fn_rnext/" oldhref="fn_rnext.html" title="rnext" /> <link rel="refentry" href="/virtuoso/fn_row_count/" oldhref="fn_row_count.html" title="row_count" /> <link rel="refentry" href="/virtuoso/fn_rtrim/" oldhref="fn_rtrim.html" title="rtrim" /> <link rel="refentry" href="/virtuoso/fn_search_excerpt/" oldhref="fn_search_excerpt.html" title="search_excerpt" /> <link rel="refentry" href="/virtuoso/fn_second/" oldhref="fn_second.html" title="second" /> <link rel="refentry" href="/virtuoso/fn_sequence_get_all/" oldhref="fn_sequence_get_all.html" title="sequence_get_all" /> <link rel="refentry" href="/virtuoso/fn_sequence_next/" oldhref="fn_sequence_next.html" title="sequence_next" /> <link rel="refentry" href="/virtuoso/fn_sequence_remove/" oldhref="fn_sequence_remove.html" title="sequence_remove" /> <link rel="refentry" href="/virtuoso/fn_sequence_set/" oldhref="fn_sequence_set.html" title="sequence_set" /> <link rel="refentry" href="/virtuoso/fn_serialize/" oldhref="fn_serialize.html" title="serialize" /> <link rel="refentry" href="/virtuoso/fn_serialize_to_utf8_xml/" oldhref="fn_serialize_to_utf8_xml.html" title="serialize_to_UTF8_xml" /> <link rel="refentry" href="/virtuoso/fn_serv_queue_top/" oldhref="fn_serv_queue_top.html" title="SERV_QUEUE_TOP" /> <link rel="refentry" href="/virtuoso/fn_ses_connect/" oldhref="fn_ses_connect.html" title="ses_connect" /> <link rel="refentry" href="/virtuoso/fn_ses_disconnect/" oldhref="fn_ses_disconnect.html" title="ses_disconnect" /> <link rel="refentry" href="/virtuoso/fn_ses_read_line/" oldhref="fn_ses_read_line.html" title="ses_read_line" /> <link rel="refentry" href="/virtuoso/fn_ses_write/" oldhref="fn_ses_write.html" title="ses_write" /> <link rel="refentry" href="/virtuoso/fn_set_row_count/" oldhref="fn_set_row_count.html" title="set_row_count" /> <link rel="refentry" href="/virtuoso/fn_set_user_id/" oldhref="fn_set_user_id.html" title="set_user_id" /> <link rel="refentry" href="/virtuoso/fn_set_identity_column/" oldhref="fn_set_identity_column.html" title="set_identity_column" /> <link rel="refentry" href="/virtuoso/fn_sign/" oldhref="fn_sign.html" title="sign" /> <link rel="refentry" href="/virtuoso/fn_signal/" oldhref="fn_signal.html" title="signal" /> <link rel="refentry" href="/virtuoso/fn_sinv_create_key_mapping/" oldhref="fn_sinv_create_key_mapping.html" title="sinv_create_key_mapping" /> <link rel="refentry" href="/virtuoso/fn_sinv_create_inverse/" oldhref="fn_sinv_create_inverse.html" title="sinv_create_inverse" /> <link rel="refentry" href="/virtuoso/fn_sinv_drop_inverse/" oldhref="fn_sinv_drop_inverse.html" title="sinv_drop_inverse" /> <link rel="refentry" href="/virtuoso/fn_smime_sign/" oldhref="fn_smime_sign.html" title="smime_sign" /> <link rel="refentry" href="/virtuoso/fn_smime_verify/" oldhref="fn_smime_verify.html" title="smime_verify" /> <link rel="refentry" href="/virtuoso/fn_smime_encrypt/" oldhref="fn_smime_encrypt.html" title="smime_encrypt" /> <link rel="refentry" href="/virtuoso/fn_smime_decrypt/" oldhref="fn_smime_decrypt.html" title="smime_decrypt" /> <link rel="refentry" href="/virtuoso/fn_smtp_send/" oldhref="fn_smtp_send.html" title="smtp_send" /> <link rel="refentry" href="/virtuoso/fn_soap_box_xml_entity/" oldhref="fn_soap_box_xml_entity.html" title="soap_box_xml_entity" /> <link rel="refentry" href="/virtuoso/fn_soap_dt_define/" oldhref="fn_soap_dt_define.html" title="soap_dt_define" /> <link rel="refentry" href="/virtuoso/fn_soap_call/" oldhref="fn_soap_call.html" title="soap_call" /> <link rel="refentry" href="/virtuoso/fn_soap_client/" oldhref="fn_soap_client.html" title="soap_client" /> <link rel="refentry" href="/virtuoso/fn_soap_make_error/" oldhref="fn_soap_make_error.html" title="soap_make_error" /> <link rel="refentry" href="/virtuoso/fn_soap_print_box/" oldhref="fn_soap_print_box.html" title="soap_print_box" /> <link rel="refentry" href="/virtuoso/fn_soap_sdl/" oldhref="fn_soap_sdl.html" title="soap_sdl" /> <link rel="refentry" href="/virtuoso/fn_soap_server/" oldhref="fn_soap_server.html" title="soap_server" /> <link rel="refentry" href="/virtuoso/fn_soap_wsdl/" oldhref="fn_soap_wsdl.html" title="soap_wsdl" /> <link rel="refentry" href="/virtuoso/fn_soap_wsdl_import/" oldhref="fn_soap_wsdl_import.html" title="soap_wsdl_import" /> <link rel="refentry" href="/virtuoso/fn_soap_box_structure/" oldhref="fn_soap_box_structure.html" title="soap_box_structure" /> <link rel="refentry" href="/virtuoso/fn_soap_current_url/" oldhref="fn_soap_current_url.html" title="soap_current_url" /> <link rel="refentry" href="/virtuoso/fn_space/" oldhref="fn_space.html" title="space" /> <link rel="refentry" href="/virtuoso/fn_split_and_decode/" oldhref="fn_split_and_decode.html" title="split_and_decode" /> <link rel="refentry" href="/virtuoso/fn_sprintf/" oldhref="fn_sprintf.html" title="sprintf" /> <link rel="refentry" href="/virtuoso/fn_sprintf_inverse/" oldhref="fn_sprintf_inverse.html" title="sprintf_inverse" /> <link rel="refentry" href="/virtuoso/fn_sprintf_iri/" oldhref="fn_sprintf_iri.html" title="sprintf_iri" /> <link rel="refentry" href="/virtuoso/fn_sprintf_iri_or_null/" oldhref="fn_sprintf_iri_or_null.html" title="sprintf_iri_or_null" /> <link rel="refentry" href="/virtuoso/fn_sprintf_or_null/" oldhref="fn_sprintf_or_null.html" title="sprintf_or_null" /> <link rel="refentry" href="/virtuoso/fn_sql_columns/" oldhref="fn_sql_columns.html" title="sql_columns" /> <link rel="refentry" href="/virtuoso/fn_sql_data_sources/" oldhref="fn_sql_data_sources.html" title="sql_data_sources" /> <link rel="refentry" href="/virtuoso/fn_sql_gettypeinfo/" oldhref="fn_sql_gettypeinfo.html" title="sql_gettypeinfo" /> <link rel="refentry" href="/virtuoso/fn_sql_primary_keys/" oldhref="fn_sql_primary_keys.html" title="sql_primary_keys" /> <link rel="refentry" href="/virtuoso/fn_sql_statistics/" oldhref="fn_sql_statistics.html" title="sql_statistics" /> <link rel="refentry" href="/virtuoso/fn_sql_tables/" oldhref="fn_sql_tables.html" title="sql_tables" /> <link rel="refentry" href="/virtuoso/fn_sql_special_columns/" oldhref="fn_sql_special_columns.html" title="sql_special_columns" /> <link rel="refentry" href="/virtuoso/fn_sql_procedures/" oldhref="fn_sql_procedures.html" title="sql_procedures" /> <link rel="refentry" href="/virtuoso/fn_sql_write_private_profile_string/" oldhref="fn_sql_write_private_profile_string.html" title="sql_write_private_profile_string" /> <link rel="refentry" href="/virtuoso/fn_sql_get_private_profile_string/" oldhref="fn_sql_get_private_profile_string.html" title="sql_get_private_profile_string" /> <link rel="refentry" href="/virtuoso/fn_sql_config_data_sources/" oldhref="fn_sql_config_data_sources.html" title="sql_config_data_sources" /> <link rel="refentry" href="/virtuoso/fn_sql_get_installed_drivers/" oldhref="fn_sql_get_installed_drivers.html" title="sql_get_installed_drivers" /> <link rel="refentry" href="/virtuoso/fn_sql_remove_dsn_from_ini/" oldhref="fn_sql_remove_dsn_from_ini.html" title="sql_remove_dsn_from_ini" /> <link rel="refentry" href="/virtuoso/fn_sql_transact/" oldhref="fn_sql_transact.html" title="sql_transact" /> <link rel="refentry" href="/virtuoso/fn_sql_write_file_dsn/" oldhref="fn_sql_write_file_dsn.html" title="sql_write_file_dsn" /> <link rel="refentry" href="/virtuoso/fn_sql_driver_connect/" oldhref="fn_sql_driver_connect.html" title="sql_driver_connect" /> <link rel="refentry" href="/virtuoso/fn_sqrt/" oldhref="fn_sqrt.html" title="sqrt" /> <link rel="refentry" href="/virtuoso/fn_status/" oldhref="fn_status.html" title="status" /> <link rel="refentry" href="/virtuoso/fn_key_estimate/" oldhref="fn_key_estimate.html" title="key_estimate" /> <link rel="refentry" href="/virtuoso/fn_strcasestr/" oldhref="fn_strcasestr.html" title="strcasestr" /> <link rel="refentry" href="/virtuoso/fn_strchr/" oldhref="fn_strchr.html" title="strchr" /> <link rel="refentry" href="/virtuoso/fn_stringdate/" oldhref="fn_stringdate.html" title="stringdate" /> <link rel="refentry" href="/virtuoso/fn_stringtime/" oldhref="fn_stringtime.html" title="stringtime" /> <link rel="refentry" href="/virtuoso/fn_string_output/" oldhref="fn_string_output.html" title="string_output" /> <link rel="refentry" href="/virtuoso/fn_string_output_flush/" oldhref="fn_string_output_flush.html" title="string_output_flush" /> <link rel="refentry" href="/virtuoso/fn_string_output_gz_compress/" oldhref="fn_string_output_gz_compress.html" title="string_output_gz_compress" /> <link rel="refentry" href="/virtuoso/fn_string_output_string/" oldhref="fn_string_output_string.html" title="string_output_string" /> <link rel="refentry" href="/virtuoso/fn_string_to_file/" oldhref="fn_string_to_file.html" title="string_to_file" /> <link rel="refentry" href="/virtuoso/fn_strrchr/" oldhref="fn_strrchr.html" title="strrchr" /> <link rel="refentry" href="/virtuoso/fn_strstr/" oldhref="fn_strstr.html" title="strstr" /> <link rel="refentry" href="/virtuoso/fn_subseq/" oldhref="fn_subseq.html" title="subseq" /> <link rel="refentry" href="/virtuoso/fn_substring/" oldhref="fn_substring.html" title="substring" /> <link rel="refentry" href="/virtuoso/fn_sub_schedule/" oldhref="fn_sub_schedule.html" title="sub_schedule" /> <link rel="refentry" href="/virtuoso/fn_system/" oldhref="fn_system.html" title="system" /> <link rel="refentry" href="/virtuoso/fn_uptime/" oldhref="fn_uptime.html" title="uptime" /> <link rel="refentry" href="/virtuoso/fn_sys_db_stat/" oldhref="fn_sys_db_stat.html" title="SYS_DB_STAT" /> <link rel="refentry" href="/virtuoso/fn_sys_lockdown/" oldhref="fn_sys_lockdown.html" title="sys_lockdown" /> <link rel="refentry" href="/virtuoso/fn_sys_stat/" oldhref="fn_sys_stat.html" title="sys_stat" /> <link rel="refentry" href="/virtuoso/fn_sys_stat_analyze/" oldhref="fn_sys_stat_analyze.html" title="sys_stat_analyze" /> <link rel="refentry" href="/virtuoso/fn_sys_stat_histogram/" oldhref="fn_sys_stat_histogram.html" title="sys_stat_histogram" /> <link rel="refentry" href="/virtuoso/fn_table_set_policy/" oldhref="fn_table_set_policy.html" title="table_set_policy" /> <link rel="refentry" href="/virtuoso/fn_table_drop_policy/" oldhref="fn_table_drop_policy.html" title="table_drop_policy" /> <link rel="refentry" href="/virtuoso/fn_strcontains/" oldhref="fn_strcontains.html" title="strcontains" /> <link rel="refentry" href="/virtuoso/fn_starts_with/" oldhref="fn_starts_with.html" title="starts_with" /> <link rel="refentry" href="/virtuoso/fn_ends_with/" oldhref="fn_ends_with.html" title="ends_with" /> <link rel="refentry" href="/virtuoso/fn_tcpip_gethostbyname/" oldhref="fn_tcpip_gethostbyname.html" title="tcpip_gethostbyname" /> <link rel="refentry" href="/virtuoso/fn_tcpip_gethostbyaddr/" oldhref="fn_tcpip_gethostbyaddr.html" title="tcpip_gethostbyaddr" /> <link rel="refentry" href="/virtuoso/fn_tmp_file_name/" oldhref="fn_tmp_file_name.html" title="tmp_file_name" /> <link rel="refentry" href="/virtuoso/fn_tidy_html/" oldhref="fn_tidy_html.html" title="tidy_html" /> <link rel="refentry" href="/virtuoso/fn_tidy_list_errors/" oldhref="fn_tidy_list_errors.html" title="tidy_list_errors" /> <link rel="refentry" href="/virtuoso/fn_timezone/" oldhref="fn_timezone.html" title="timezone" /> <link rel="refentry" href="/virtuoso/fn_trace_off/" oldhref="fn_trace_off.html" title="trace_off" /> <link rel="refentry" href="/virtuoso/fn_trace_on/" oldhref="fn_trace_on.html" title="trace_on" /> <link rel="refentry" href="/virtuoso/fn_trace_status/" oldhref="fn_trace_status.html" title="trace_status" /> <link rel="refentry" href="/uda/ee/fn_tree_md5/" oldhref="fn_tree_md5.html" title="tree_md5" /> <link rel="refentry" href="/virtuoso/fn_hs_resolve/" oldhref="fn_hs_resolve.html" title="HS_Resolve" /> <link rel="refentry" href="/virtuoso/fn_acos/" oldhref="fn_acos.html" title="trigonometric" /> <link rel="refentry" href="/virtuoso/fn_trim/" oldhref="fn_trim.html" title="trim" /> <link rel="refentry" href="/virtuoso/fn_txn_error/" oldhref="fn_txn_error.html" title="txn_error" /> <link rel="refentry" href="/virtuoso/fn_txn_killall/" oldhref="fn_txn_killall.html" title="txn_killall" /> <link rel="refentry" href="/virtuoso/fn_ucase/" oldhref="fn_ucase.html" title="ucase" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_binding/" oldhref="me_uddi_delete_binding.html" title="uddi_delete_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_business/" oldhref="me_uddi_delete_business.html" title="uddi_delete_business" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_service/" oldhref="me_uddi_delete_service.html" title="uddi_delete_service" /> <link rel="refentry" href="/virtuoso/me_uddi_delete_tmodel/" oldhref="me_uddi_delete_tmodel.html" title="uddi_delete_tModel" /> <link rel="refentry" href="/virtuoso/me_uddi_discard_authtoken/" oldhref="me_uddi_discard_authtoken.html" title="uddi_discard_authToken" /> <link rel="refentry" href="/virtuoso/me_uddi_find_binding/" oldhref="me_uddi_find_binding.html" title="uddi_find_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_find_business/" oldhref="me_uddi_find_business.html" title="uddi_find_business" /> <link rel="refentry" href="/virtuoso/me_uddi_find_service/" oldhref="me_uddi_find_service.html" title="uddi_find_service" /> <link rel="refentry" href="/virtuoso/me_uddi_find_tmodel/" oldhref="me_uddi_find_tmodel.html" title="uddi_find_tModel" /> <link rel="refentry" href="/virtuoso/me_uddi_get_authtoken/" oldhref="me_uddi_get_authtoken.html" title="uddi_get_authToken" /> <link rel="refentry" href="/virtuoso/me_uddi_get_bindingdetail/" oldhref="me_uddi_get_bindingdetail.html" title="uddi_get_bindingDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_businessdetail/" oldhref="me_uddi_get_businessdetail.html" title="uddi_get_businessDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_businessdetailext/" oldhref="me_uddi_get_businessdetailext.html" title="uddi_get_businessDetailExt" /> <link rel="refentry" href="/virtuoso/me_uddi_get_registeredinfo/" oldhref="me_uddi_get_registeredinfo.html" title="uddi_get_registeredInfo" /> <link rel="refentry" href="/virtuoso/me_uddi_get_servicedetail/" oldhref="me_uddi_get_servicedetail.html" title="uddi_get_serviceDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_get_tmodeldetail/" oldhref="me_uddi_get_tmodeldetail.html" title="uddi_get_tModelDetail" /> <link rel="refentry" href="/virtuoso/me_uddi_save_binding/" oldhref="me_uddi_save_binding.html" title="uddi_save_binding" /> <link rel="refentry" href="/virtuoso/me_uddi_save_business/" oldhref="me_uddi_save_business.html" title="uddi_save_business" /> <link rel="refentry" href="/virtuoso/me_uddi_save_service/" oldhref="me_uddi_save_service.html" title="uddi_save_service" /> <link rel="refentry" href="/virtuoso/me_uddi_save_tmodel/" oldhref="me_uddi_save_tmodel.html" title="uddi_save_tModel" /> <link rel="refentry" href="/virtuoso/fn_udt_defines_field/" oldhref="fn_udt_defines_field.html" title="udt_defines_field" /> <link rel="refentry" href="/virtuoso/fn_udt_get/" oldhref="fn_udt_get.html" title="udt_get" /> <link rel="refentry" href="/virtuoso/fn_udt_implements_method/" oldhref="fn_udt_implements_method.html" title="udt_implements_method" /> <link rel="refentry" href="/virtuoso/fn_udt_instance_of/" oldhref="fn_udt_instance_of.html" title="udt_instance_of" /> <link rel="refentry" href="/virtuoso/fn_udt_set/" oldhref="fn_udt_set.html" title="udt_set" /> <link rel="refentry" href="/virtuoso/fn_unimport_clr/" oldhref="fn_unimport_clr.html" title="unimport_clr" /> <link rel="refentry" href="/virtuoso/fn_unimport_jar/" oldhref="fn_unimport_jar.html" title="unimport_jar" /> <link rel="refentry" href="/virtuoso/fn_updatexml/" oldhref="fn_updatexml.html" title="updateXML" /> <link rel="refentry" href="/virtuoso/fn_upper/" oldhref="fn_upper.html" title="upper" /> <link rel="refentry" href="/virtuoso/fn_user_change_password/" oldhref="fn_user_change_password.html" title="USER_CHANGE_PASSWORD" /> <link rel="refentry" href="/virtuoso/fn_user_create/" oldhref="fn_user_create.html" title="USER_CREATE" /> <link rel="refentry" href="/virtuoso/fn_user_drop/" oldhref="fn_user_drop.html" title="USER_DROP" /> <link rel="refentry" href="/virtuoso/fn_user_get_option/" oldhref="fn_user_get_option.html" title="USER_GET_OPTION" /> <link rel="refentry" href="/virtuoso/fn_user_grant_role/" oldhref="fn_user_grant_role.html" title="USER_GRANT_ROLE" /> <link rel="refentry" href="/virtuoso/fn_user_revoke_role/" oldhref="fn_user_revoke_role.html" title="USER_REVOKE_ROLE" /> <link rel="refentry" href="/virtuoso/fn_user_role_create/" oldhref="fn_user_role_create.html" title="USER_ROLE_CREATE" /> <link rel="refentry" href="/virtuoso/fn_user_role_drop/" oldhref="fn_user_role_drop.html" title="USER_ROLE_DROP" /> <link rel="refentry" href="/virtuoso/fn_user_set_qualifier/" oldhref="fn_user_set_qualifier.html" title="USER_SET_QUALIFIER" /> <link rel="refentry" href="/virtuoso/fn_user_set_option/" oldhref="fn_user_set_option.html" title="USER_SET_OPTION" /> <link rel="refentry" href="/virtuoso/fn_user_set_password/" oldhref="fn_user_set_password.html" title="user_set_password" /> <link rel="refentry" href="/virtuoso/fn_username/" oldhref="fn_username.html" title="username" /> <link rel="refentry" href="/virtuoso/fn_uudecode/" oldhref="fn_uudecode.html" title="uudecode" /> <link rel="refentry" href="/virtuoso/fn_uuencode/" oldhref="fn_uuencode.html" title="uuencode" /> <link rel="refentry" href="/virtuoso/fn_uuvalidate/" oldhref="fn_uuvalidate.html" title="uuvalidate" /> <link rel="refentry" href="/virtuoso/fn_user_key_store/" oldhref="fn_user_key_store.html" title="USER_KEY_STORE" /> <link rel="refentry" href="/virtuoso/fn_vad_check/" oldhref="fn_vad_check.html" title="VAD_CHECK" /> <link rel="refentry" href="/virtuoso/fn_vad_check_installability/" oldhref="fn_vad_check_installability.html" title="VAD_CHECK_INSTALLABILITY" /> <link rel="refentry" href="/virtuoso/fn_vad_check_uninstallability/" oldhref="fn_vad_check_uninstallability.html" title="VAD_CHECK_UNINSTALLABILITY" /> <link rel="refentry" href="/virtuoso/fn_vad_fail_check/" oldhref="fn_vad_fail_check.html" title="VAD_FAIL_CHECK" /> <link rel="refentry" href="/virtuoso/fn_vad_install/" oldhref="fn_vad_install.html" title="VAD_INSTALL" /> <link rel="refentry" href="/virtuoso/fn_vad_load_file/" oldhref="fn_vad_load_file.html" title="VAD_LOAD_FILE" /> <link rel="refentry" href="/virtuoso/fn_vad_load_sql_file/" oldhref="fn_vad_load_sql_file.html" title="VAD_LOAD_SQL_FILE" /> <link rel="refentry" href="/virtuoso/fn_vad_pack/" oldhref="fn_vad_pack.html" title="VAD_PACK" /> <link rel="refentry" href="/virtuoso/fn_vad_safe_exec/" oldhref="fn_vad_safe_exec.html" title="VAD_SAFE_EXEC" /> <link rel="refentry" href="/virtuoso/fn_vad_uninstall/" oldhref="fn_vad_uninstall.html" title="VAD_UNINSTALL" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_data_source/" oldhref="fn_vd_remote_data_source.html" title="vd_remote_data_source" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_proc_wrapper/" oldhref="fn_vd_remote_proc_wrapper.html" title="vd_remote_proc_wrapper" /> <link rel="refentry" href="/virtuoso/fn_vd_remote_table/" oldhref="fn_vd_remote_table.html" title="vd_remote_table" /> <link rel="refentry" href="/virtuoso/fn_vd_statistics/" oldhref="fn_vd_statistics.html" title="vd_statistics" /> <link rel="refentry" href="/virtuoso/fn_vdd_disconnect_data_source/" oldhref="fn_vdd_disconnect_data_source.html" title="vdd_disconnect_data_source" /> <link rel="refentry" href="/virtuoso/fn_vdd_measure_rpc_time/" oldhref="fn_vdd_measure_rpc_time.html" title="vdd_measure_rpc_time" /> <link rel="refentry" href="/virtuoso/fn_vector/" oldhref="fn_vector.html" title="vector" /> <link rel="refentry" href="/virtuoso/fn_vector_concat/" oldhref="fn_vector_concat.html" title="vector_concat" /> <link rel="refentry" href="/virtuoso/fn_vhost_define/" oldhref="fn_vhost_define.html" title="VHOST_DEFINE" /> <link rel="refentry" href="/virtuoso/fn_vhost_remove/" oldhref="fn_vhost_remove.html" title="VHOST_REMOVE" /> <link rel="refentry" href="/virtuoso/fn_virtuoso_ini_path/" oldhref="fn_virtuoso_ini_path.html" title="virtuoso_ini_path" /> <link rel="refentry" href="/virtuoso/fn_server_root/" oldhref="fn_server_root.html" title="server_root" /> <link rel="refentry" href="/virtuoso/fn_vsp_calculate_digest/" oldhref="fn_vsp_calculate_digest.html" title="vsp_calculate_digest" /> <link rel="refentry" href="/virtuoso/fn_vt_batch/" oldhref="fn_vt_batch.html" title="vt_batch" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_d_id/" oldhref="fn_vt_batch_d_id.html" title="vt_batch_d_id" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_feed/" oldhref="fn_vt_batch_feed.html" title="vt_batch_feed" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_feed_offband/" oldhref="fn_vt_batch_feed_offband.html" title="vt_batch_feed_offband" /> <link rel="refentry" href="/virtuoso/fn_vt_batch_update/" oldhref="fn_vt_batch_update.html" title="VT_BATCH_UPDATE" /> <link rel="refentry" href="/virtuoso/fn_vt_create_text_index/" oldhref="fn_vt_create_text_index.html" title="vt_create_text_index" /> <link rel="refentry" href="/virtuoso/fn_vt_drop_ftt/" oldhref="fn_vt_drop_ftt.html" title="VT_DROP_FTT" /> <link rel="refentry" href="/virtuoso/fn_vt_is_noise/" oldhref="fn_vt_is_noise.html" title="vt_is_noise" /> <link rel="refentry" href="/virtuoso/fn_week/" oldhref="fn_week.html" title="week" /> <link rel="refentry" href="/virtuoso/fn_wsdl_import_udt/" oldhref="fn_wsdl_import_udt.html" title="wsdl_import_udt" /> <link rel="refentry" href="/virtuoso/fn_wst_cli/" oldhref="fn_wst_cli.html" title="wst_cli" /> <link rel="refentry" href="/virtuoso/fn_user_key_load/" oldhref="fn_user_key_load.html" title="USER_KEY_LOAD" /> <link rel="refentry" href="/virtuoso/fn_dsig_template_ext/" oldhref="fn_dsig_template_ext.html" title="dsig_template_ext" /> <link rel="refentry" href="/virtuoso/fn_x509_certificate_verify/" oldhref="fn_x509_certificate_verify.html" title="x509_certificate_verify" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_certificate_serialize/" oldhref="fn_xenc_x509_certificate_serialize.html" title="xenc_X509_certificate_serialize" /> <link rel="refentry" href="/virtuoso/fn_xenc_decrypt_soap/" oldhref="fn_xenc_decrypt_soap.html" title="xenc_decrypt_soap" /> <link rel="refentry" href="/virtuoso/fn_xenc_delete_temp_keys/" oldhref="fn_xenc_delete_temp_keys.html" title="xenc_delete_temp_keys" /> <link rel="refentry" href="/virtuoso/fn_xenc_encrypt/" oldhref="fn_xenc_encrypt.html" title="xenc_encrypt" /> <link rel="refentry" href="/virtuoso/fn_encrypt/" oldhref="fn_encrypt.html" title="encrypt" /> <link rel="refentry" href="/virtuoso/fn_decrypt/" oldhref="fn_decrypt.html" title="decrypt" /> <link rel="refentry" href="/virtuoso/fn_totp_generate/" oldhref="fn_totp_generate.html" title="TOTP_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_get_key_algo/" oldhref="fn_xenc_get_key_algo.html" title="xenc_get_key_algo" /> <link rel="refentry" href="/virtuoso/fn_xenc_get_key_identifier/" oldhref="fn_xenc_get_key_identifier.html" title="xenc_get_key_identifier" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_read/" oldhref="fn_xenc_key_3des_read.html" title="xenc_key_3DES_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_create/" oldhref="fn_xenc_key_3des_create.html" title="xenc_key_3DES_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_3des_rand_create/" oldhref="fn_xenc_key_3des_rand_create.html" title="xenc_key_3DES_rand_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_dsa_read/" oldhref="fn_xenc_key_dsa_read.html" title="xenc_key_DSA_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_rsa_read/" oldhref="fn_xenc_key_rsa_read.html" title="xenc_key_RSA_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_aes_create/" oldhref="fn_xenc_key_aes_create.html" title="xenc_key_AES_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_aes_rand_create/" oldhref="fn_xenc_key_aes_rand_create.html" title="xenc_key_AES_rand_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_create_cert/" oldhref="fn_xenc_key_create_cert.html" title="xenc_key_create_cert" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_dsa_create/" oldhref="fn_xenc_key_dsa_create.html" title="xenc_key_DSA_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_exists/" oldhref="fn_xenc_key_exists.html" title="xenc_key_exists" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_inst_create/" oldhref="fn_xenc_key_inst_create.html" title="xenc_key_inst_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_remove/" oldhref="fn_xenc_key_remove.html" title="xenc_key_remove" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_serialize/" oldhref="fn_xenc_key_serialize.html" title="xenc_key_serialize" /> <link rel="refentry" href="/virtuoso/fn_xenc_set_primary_key/" oldhref="fn_xenc_set_primary_key.html" title="xenc_set_primary_key" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_ss_generate/" oldhref="fn_xenc_x509_ss_generate.html" title="xenc_x509_ss_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_generate/" oldhref="fn_xenc_x509_generate.html" title="xenc_x509_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_pkcs12_export/" oldhref="fn_xenc_pkcs12_export.html" title="xenc_pkcs12_export" /> <link rel="refentry" href="/virtuoso/fn_xenc_pem_export/" oldhref="fn_xenc_pem_export.html" title="xenc_pem_export" /> <link rel="refentry" href="/virtuoso/fn_xenc_spki_read/" oldhref="fn_xenc_spki_read.html" title="xenc_SPKI_read" /> <link rel="refentry" href="/virtuoso/fn_xenc_bn2dec/" oldhref="fn_xenc_bn2dec.html" title="xenc_bn2dec" /> <link rel="refentry" href="/virtuoso/fn_xenc_key_rsa_create/" oldhref="fn_xenc_key_rsa_create.html" title="xenc_key_RSA_create" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_csr_generate/" oldhref="fn_xenc_x509_csr_generate.html" title="xenc_x509_csr_generate" /> <link rel="refentry" href="/virtuoso/fn_xenc_x509_from_csr/" oldhref="fn_xenc_x509_from_csr.html" title="xenc_x509_from_csr" /> <link rel="refentry" href="/virtuoso/fn_xte_head/" oldhref="fn_xte_head.html" title="xte_head" /> <link rel="refentry" href="/virtuoso/fn_xte_node/" oldhref="fn_xte_node.html" title="xte_node" /> <link rel="refentry" href="/virtuoso/fn_xte_node_from_nodebld/" oldhref="fn_xte_node_from_nodebld.html" title="xte_node_from_nodebld" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_acc/" oldhref="fn_xte_nodebld_acc.html" title="xte_nodebld_acc" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_final/" oldhref="fn_xte_nodebld_final.html" title="xte_nodebld_final" /> <link rel="refentry" href="/virtuoso/fn_xte_nodebld_init/" oldhref="fn_xte_nodebld_init.html" title="xte_nodebld_init" /> <link rel="refentry" href="/virtuoso/fn_xmlagg/" oldhref="fn_xmlagg.html" title="XMLAGG" /> <link rel="refentry" href="/virtuoso/fn_xmlattributes/" oldhref="fn_xmlattributes.html" title="XMLATTRIBUTES" /> <link rel="refentry" href="/virtuoso/fn_xmladdattribute/" oldhref="fn_xmladdattribute.html" title="XMLAddAttribute" /> <link rel="refentry" href="/virtuoso/fn_xmlappendchildren/" oldhref="fn_xmlappendchildren.html" title="XMLAppendChildren" /> <link rel="refentry" href="/virtuoso/fn_xmlconcat/" oldhref="fn_xmlconcat.html" title="XMLCONCAT" /> <link rel="refentry" href="/virtuoso/fn_xmlelement/" oldhref="fn_xmlelement.html" title="XMLELEMENT" /> <link rel="refentry" href="/virtuoso/fn_xmlforest/" oldhref="fn_xmlforest.html" title="XMLFOREST" /> <link rel="refentry" href="/virtuoso/fn_xmlinsertafter/" oldhref="fn_xmlinsertafter.html" title="XMLInsertAfter" /> <link rel="refentry" href="/virtuoso/fn_xmlinsertbefore/" oldhref="fn_xmlinsertbefore.html" title="XMLInsertBefore" /> <link rel="refentry" href="/virtuoso/fn_xmlreplace/" oldhref="fn_xmlreplace.html" title="XMLReplace" /> <link rel="refentry" href="/virtuoso/fn_xml_auto/" oldhref="fn_xml_auto.html" title="xml_auto" /> <link rel="refentry" href="/virtuoso/fn_xml_auto_dtd/" oldhref="fn_xml_auto_dtd.html" title="xml_auto_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_auto_schema/" oldhref="fn_xml_auto_schema.html" title="xml_auto_schema" /> <link rel="refentry" href="/virtuoso/fn_xml_create_tables_from_mapping_schema_decl/" oldhref="fn_xml_create_tables_from_mapping_schema_decl.html" title="xml_create_tables_from_mapping_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_cut/" oldhref="fn_xml_cut.html" title="xml_cut" /> <link rel="refentry" href="/virtuoso/fn_xml_doc_output_option/" oldhref="fn_xml_doc_output_option.html" title="xml_doc_output_option" /> <link rel="refentry" href="/virtuoso/fn_xml_load_schema_decl/" oldhref="fn_xml_load_schema_decl.html" title="xml_load_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_load_mapping_schema_decl/" oldhref="fn_xml_load_mapping_schema_decl.html" title="xml_load_mapping_schema_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_namespace_scope/" oldhref="fn_xml_namespace_scope.html" title="xml_namespace_scope" /> <link rel="refentry" href="/virtuoso/fn_xml_add_system_path/" oldhref="fn_xml_add_system_path.html" title="xml_add_system_path" /> <link rel="refentry" href="/virtuoso/fn_xml_get_system_paths/" oldhref="fn_xml_get_system_paths.html" title="xml_get_system_paths" /> <link rel="refentry" href="/virtuoso/fn_xml_persistent/" oldhref="fn_xml_persistent.html" title="xml_persistent" /> <link rel="refentry" href="/virtuoso/fn_xml_template/" oldhref="fn_xml_template.html" title="xml_template" /> <link rel="refentry" href="/virtuoso/fn_xml_tree/" oldhref="fn_xml_tree.html" title="xml_tree" /> <link rel="refentry" href="/uda/ee/fn_xml_tree_doc/" oldhref="fn_xml_tree_doc.html" title="xml_tree_doc" /> <link rel="refentry" href="/uda/ee/fn_xml_tree_doc_media_type/" oldhref="fn_xml_tree_doc_media_type.html" title="xml_tree_doc_media_type" /> <link rel="refentry" href="/virtuoso/fn_xml_uri_get/" oldhref="fn_xml_uri_get.html" title="xml_uri_get" /> <link rel="refentry" href="/virtuoso/fn_xml_validate_dtd/" oldhref="fn_xml_validate_dtd.html" title="xml_validate_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_validate_schema/" oldhref="fn_xml_validate_schema.html" title="xml_validate_schema" /> <link rel="refentry" href="/virtuoso/fn_xml_view_dtd/" oldhref="fn_xml_view_dtd.html" title="xml_view_dtd" /> <link rel="refentry" href="/virtuoso/fn_xml_set_ns_decl/" oldhref="fn_xml_set_ns_decl.html" title="xml_set_ns_decl" /> <link rel="refentry" href="/virtuoso/fn_xml_view_schema/" oldhref="fn_xml_view_schema.html" title="xml_view_schema" /> <link rel="refentry" href="/virtuoso/fn_xmlsql_update/" oldhref="fn_xmlsql_update.html" title="xmlsql_update" /> <link rel="refentry" href="/virtuoso/fn_xmlupdate/" oldhref="fn_xmlupdate.html" title="XMLUpdate" /> <link rel="refentry" href="/virtuoso/fn_xpath_eval/" oldhref="fn_xpath_eval.html" title="xpath_eval" /> <link rel="refentry" href="/virtuoso/fn_xper_cut/" oldhref="fn_xper_cut.html" title="xper_cut" /> <link rel="refentry" href="/virtuoso/fn_xper_doc/" oldhref="fn_xper_doc.html" title="xper_doc" /> <link rel="refentry" href="/virtuoso/fn_xper_locate_words/" oldhref="fn_xper_locate_words.html" title="xper_locate_words" /> <link rel="refentry" href="/virtuoso/fn_xper_right_sibling/" oldhref="fn_xper_right_sibling.html" title="XPER navigation" /> <link rel="refentry" href="/virtuoso/fn_xpf_extension/" oldhref="fn_xpf_extension.html" title="xpf_extension" /> <link rel="refentry" href="/virtuoso/fn_xpf_extension_remove/" oldhref="fn_xpf_extension_remove.html" title="xpf_extension_remove" /> <link rel="refentry" href="/virtuoso/fn_xquery_eval/" oldhref="fn_xquery_eval.html" title="xquery_eval" /> <link rel="refentry" href="/virtuoso/fn_xslt/" oldhref="fn_xslt.html" title="xslt" /> <link rel="refentry" href="/virtuoso/fn_xslt_format_number/" oldhref="fn_xslt_format_number.html" title="xslt_format_number" /> <link rel="refentry" href="/virtuoso/fn_xslt_sheet/" oldhref="fn_xslt_sheet.html" title="xslt_sheet" /> <link rel="refentry" href="/virtuoso/fn_xslt_stale/" oldhref="fn_xslt_stale.html" title="xslt_stale" /> <link rel="refentry" href="/uda/ee/fn_xtree_doc/" oldhref="fn_xtree_doc.html" title="xtree_doc" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.registeruser/" oldhref="fn_xmlstoragesystem.registeruser.html" title="xmlStorageSystem.registerUser" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.mailpasswordtouser/" oldhref="fn_xmlstoragesystem.mailpasswordtouser.html" title="xmlStorageSystem.mailPasswordToUser" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.getservercapabilities/" oldhref="fn_xmlstoragesystem.getservercapabilities.html" title="xmlStorageSystem.getServerCapabilities" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.deletemultiplefiles/" oldhref="fn_xmlstoragesystem.deletemultiplefiles.html" title="xmlStorageSystem.deleteMultipleFiles" /> <link rel="refentry" href="/virtuoso/fn_xmlstoragesystem.savemultiplefiles/" oldhref="fn_xmlstoragesystem.savemultiplefiles.html" title="xmlStorageSystem.saveMultipleFiles" /> <link rel="refentry" href="/virtuoso/fn_xmltype.xmltype/" oldhref="fn_xmltype.xmltype.html" title="XMLType.XMLType" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createnonschemabasedxml/" oldhref="fn_xmltype.createnonschemabasedxml.html" title="XMLType.createNonSchemaBasedXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createschemabasedxml/" oldhref="fn_xmltype.createschemabasedxml.html" title="XMLType.createSchemaBasedXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.createxml/" oldhref="fn_xmltype.createxml.html" title="XMLType.createXML" /> <link rel="refentry" href="/virtuoso/fn_xmltype.existsnode/" oldhref="fn_xmltype.existsnode.html" title="XMLType.existsNode" /> <link rel="refentry" href="/virtuoso/fn_xmltype.extract/" oldhref="fn_xmltype.extract.html" title="XMLType.extract" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getclobval/" oldhref="fn_xmltype.getclobval.html" title="XMLType.getClobVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getnamespace/" oldhref="fn_xmltype.getnamespace.html" title="XMLType.getNamespace" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getnumval/" oldhref="fn_xmltype.getnumval.html" title="XMLType.getNumVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getrootelement/" oldhref="fn_xmltype.getrootelement.html" title="XMLType.getRootElement" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getschemaurl/" oldhref="fn_xmltype.getschemaurl.html" title="XMLType.getSchemaURL" /> <link rel="refentry" href="/virtuoso/fn_xmltype.getstringval/" oldhref="fn_xmltype.getstringval.html" title="XMLType.getStringVal" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isfragment/" oldhref="fn_xmltype.isfragment.html" title="XMLType.isFragment" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemabased/" oldhref="fn_xmltype.isschemabased.html" title="XMLType.isSchemaBased" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemavalid/" oldhref="fn_xmltype.isschemavalid.html" title="XMLType.isSchemaValid" /> <link rel="refentry" href="/virtuoso/fn_xmltype.isschemavalidated/" oldhref="fn_xmltype.isschemavalidated.html" title="XMLType.isSchemaValidated" /> <link rel="refentry" href="/virtuoso/fn_xmltype.schemavalidate/" oldhref="fn_xmltype.schemavalidate.html" title="XMLType.schemaValidate" /> <link rel="refentry" href="/virtuoso/fn_xmltype.setschemavalidated/" oldhref="fn_xmltype.setschemavalidated.html" title="XMLType.setSchemaValidated" /> <link rel="refentry" href="/virtuoso/fn_xmltype.toobject/" oldhref="fn_xmltype.toobject.html" title="XMLType.toObject" /> <link rel="refentry" href="/virtuoso/fn_xmltype.transform/" oldhref="fn_xmltype.transform.html" title="XMLType.transform" /> <link rel="refentry" href="/virtuoso/xpf__sql__column/" oldhref="xpf__sql__column.html" title="sql:column" /> <link rel="refentry" href="/virtuoso/xpf_and/" oldhref="xpf_and.html" title="and" /> <link rel="refentry" href="/virtuoso/xpf_append/" oldhref="xpf_append.html" title="append" /> <link rel="refentry" href="/virtuoso/xpf_assign/" oldhref="xpf_assign.html" title="assign" /> <link rel="refentry" href="/virtuoso/xpf_avg/" oldhref="xpf_avg.html" title="avg" /> <link rel="refentry" href="/virtuoso/xpf_boolean/" oldhref="xpf_boolean.html" title="boolean" /> <link rel="refentry" href="/virtuoso/xpf_ceiling/" oldhref="xpf_ceiling.html" title="ceiling" /> <link rel="refentry" href="/virtuoso/xpf_collection/" oldhref="xpf_collection.html" title="fn:collection" /> <link rel="refentry" href="/virtuoso/xpf_concat/" oldhref="xpf_concat.html" title="concat" /> <link rel="refentry" href="/virtuoso/xpf_contains/" oldhref="xpf_contains.html" title="contains" /> <link rel="refentry" href="/virtuoso/xpf_count/" oldhref="xpf_count.html" title="count" /> <link rel="refentry" href="/virtuoso/xpf_create_attribute/" oldhref="xpf_create_attribute.html" title="create-attribute" /> <link rel="refentry" href="/virtuoso/xpf_create_comment/" oldhref="xpf_create_comment.html" title="create-comment" /> <link rel="refentry" href="/virtuoso/xpf_create_element/" oldhref="xpf_create_element.html" title="create-element" /> <link rel="refentry" href="/virtuoso/xpf_create_pi/" oldhref="xpf_create_pi.html" title="create-pi" /> <link rel="refentry" href="/virtuoso/xpf_current/" oldhref="xpf_current.html" title="current" /> <link rel="refentry" href="/virtuoso/xpf_distinct/" oldhref="xpf_distinct.html" title="distinct" /> <link rel="refentry" href="/virtuoso/xpf_doc/" oldhref="xpf_doc.html" title="doc" /> <link rel="refentry" href="/virtuoso/xpf_document/" oldhref="xpf_document.html" title="document" /> <link rel="refentry" href="/virtuoso/xpf_document_literal/" oldhref="xpf_document_literal.html" title="document-literal" /> <link rel="refentry" href="/virtuoso/xpf_empty/" oldhref="xpf_empty.html" title="empty" /> <link rel="refentry" href="/virtuoso/xpf_ends_with/" oldhref="xpf_ends_with.html" title="ends-with" /> <link rel="refentry" href="/virtuoso/xpf_every/" oldhref="xpf_every.html" title="every" /> <link rel="refentry" href="/virtuoso/xpf_except/" oldhref="xpf_except.html" title="except" /> <link rel="refentry" href="/virtuoso/xpf_false/" oldhref="xpf_false.html" title="false" /> <link rel="refentry" href="/virtuoso/xpf_filter/" oldhref="xpf_filter.html" title="filter" /> <link rel="refentry" href="/virtuoso/xpf_floor/" oldhref="xpf_floor.html" title="floor" /> <link rel="refentry" href="/virtuoso/xpf_for/" oldhref="xpf_for.html" title="for" /> <link rel="refentry" href="/virtuoso/xpf_format_number/" oldhref="xpf_format_number.html" title="format-number" /> <link rel="refentry" href="/virtuoso/xpf_function_available/" oldhref="xpf_function_available.html" title="function-available" /> <link rel="refentry" href="/virtuoso/xpf_generate_id/" oldhref="xpf_generate_id.html" title="generate-id" /> <link rel="refentry" href="/virtuoso/xpf_id/" oldhref="xpf_id.html" title="id" /> <link rel="refentry" href="/virtuoso/xpf_if/" oldhref="xpf_if.html" title="if" /> <link rel="refentry" href="/virtuoso/xpf_intersect/" oldhref="xpf_intersect.html" title="intersect" /> <link rel="refentry" href="/virtuoso/xpf_is_after/" oldhref="xpf_is_after.html" title="is_after" /> <link rel="refentry" href="/virtuoso/xpf_is_before/" oldhref="xpf_is_before.html" title="is_before" /> <link rel="refentry" href="/virtuoso/xpf_key/" oldhref="xpf_key.html" title="key" /> <link rel="refentry" href="/virtuoso/xpf_lang/" oldhref="xpf_lang.html" title="lang" /> <link rel="refentry" href="/virtuoso/xpf_last/" oldhref="xpf_last.html" title="last" /> <link rel="refentry" href="/virtuoso/xpf_let/" oldhref="xpf_let.html" title="let" /> <link rel="refentry" href="/virtuoso/xpf_list/" oldhref="xpf_list.html" title="list" /> <link rel="refentry" href="/virtuoso/xpf_local_name/" oldhref="xpf_local_name.html" title="local-name" /> <link rel="refentry" href="/virtuoso/xpf_max/" oldhref="xpf_max.html" title="max" /> <link rel="refentry" href="/virtuoso/xpf_min/" oldhref="xpf_min.html" title="min" /> <link rel="refentry" href="/virtuoso/xpf_name/" oldhref="xpf_name.html" title="name" /> <link rel="refentry" href="/virtuoso/xpf_namespace_uri/" oldhref="xpf_namespace_uri.html" title="namespace-uri" /> <link rel="refentry" href="/virtuoso/xpf_normalize_space/" oldhref="xpf_normalize_space.html" title="normalize-space" /> <link rel="refentry" href="/virtuoso/xpf_not/" oldhref="xpf_not.html" title="not" /> <link rel="refentry" href="/virtuoso/xpf_number/" oldhref="xpf_number.html" title="number" /> <link rel="refentry" href="/virtuoso/xpf_or/" oldhref="xpf_or.html" title="or" /> <link rel="refentry" href="/virtuoso/xpf_position/" oldhref="xpf_position.html" title="position" /> <link rel="refentry" href="/virtuoso/xpf_processxquery/" oldhref="xpf_processxquery.html" title="processXQuery" /> <link rel="refentry" href="/virtuoso/xpf_processxslt/" oldhref="xpf_processxslt.html" title="processXSLT" /> <link rel="refentry" href="/virtuoso/xpf_processxsql/" oldhref="xpf_processxsql.html" title="processXSQL" /> <link rel="refentry" href="/virtuoso/xpf_progn/" oldhref="xpf_progn.html" title="progn" /> <link rel="refentry" href="/virtuoso/xpf_replace/" oldhref="xpf_replace.html" title="replace" /> <link rel="refentry" href="/virtuoso/xpf_round/" oldhref="xpf_round.html" title="round" /> <link rel="refentry" href="/virtuoso/xpf_serialize/" oldhref="xpf_serialize.html" title="serialize" /> <link rel="refentry" href="/virtuoso/xpf_shallow/" oldhref="xpf_shallow.html" title="shallow" /> <link rel="refentry" href="/virtuoso/xpf_some/" oldhref="xpf_some.html" title="some" /> <link rel="refentry" href="/virtuoso/xpf_starts_with/" oldhref="xpf_starts_with.html" title="starts-with" /> <link rel="refentry" href="/virtuoso/xpf_string/" oldhref="xpf_string.html" title="string" /> <link rel="refentry" href="/virtuoso/xpf_string_length/" oldhref="xpf_string_length.html" title="string-length" /> <link rel="refentry" href="/virtuoso/xpf_substring/" oldhref="xpf_substring.html" title="substring" /> <link rel="refentry" href="/virtuoso/xpf_substring_after/" oldhref="xpf_substring_after.html" title="substring-after" /> <link rel="refentry" href="/virtuoso/xpf_substring_before/" oldhref="xpf_substring_before.html" title="substring-before" /> <link rel="refentry" href="/virtuoso/xpf_sum/" oldhref="xpf_sum.html" title="sum" /> <link rel="refentry" href="/virtuoso/xpf_system_property/" oldhref="xpf_system_property.html" title="system-property" /> <link rel="refentry" href="/virtuoso/xpf_text_contains/" oldhref="xpf_text_contains.html" title="text_contains" /> <link rel="refentry" href="/virtuoso/xpf_translate/" oldhref="xpf_translate.html" title="translate" /> <link rel="refentry" href="/virtuoso/xpf_true/" oldhref="xpf_true.html" title="true" /> <link rel="refentry" href="/virtuoso/xpf_tuple/" oldhref="xpf_tuple.html" title="tuple" /> <link rel="refentry" href="/virtuoso/xpf_union/" oldhref="xpf_union.html" title="union" /> <link rel="refentry" href="/virtuoso/xpf_unordered/" oldhref="xpf_unordered.html" title="unordered" /> <link rel="refentry" href="/virtuoso/xpf_unparsed_entity_uri/" oldhref="xpf_unparsed_entity_uri.html" title="unparsed-entity-uri" /> <link rel="refentry" href="/virtuoso/xpf_urlify/" oldhref="xpf_urlify.html" title="urlify" /> <link rel="refentry" href="/virtuoso/xpf_xmlview/" oldhref="xpf_xmlview.html" title="xmlview" /> <link rel="refentry" href="/virtuoso/fn_bpel_compile_script/" oldhref="fn_bpel_compile_script.html" title="BPEL.BPEL.compile_script" /> <link rel="refentry" href="/virtuoso/fn_bpel_copy_script/" oldhref="fn_bpel_copy_script.html" title="BPEL.BPEL.copy_script" /> <link rel="refentry" href="/virtuoso/fn_bpel_get_partner_links/" oldhref="fn_bpel_get_partner_links.html" title="BPEL.BPEL.get_partner_links" /> <link rel="refentry" href="/virtuoso/fn_bpel_instance_delete/" oldhref="fn_bpel_instance_delete.html" title="BPEL.BPEL.instance_delete" /> <link rel="refentry" href="/virtuoso/fn_bpel_purge/" oldhref="fn_bpel_purge.html" title="BPEL.BPEL.purge_instance" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_delete/" oldhref="fn_bpel_script_delete.html" title="BPEL.BPEL.script_delete" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_obsolete/" oldhref="fn_bpel_script_obsolete.html" title="BPEL.BPEL.script_obsolete" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_source_update/" oldhref="fn_bpel_script_source_update.html" title="BPEL.BPEL.script_source_update" /> <link rel="refentry" href="/virtuoso/fn_bpel_script_upload/" oldhref="fn_bpel_script_upload.html" title="BPEL.BPEL.script_upload" /> <link rel="refentry" href="/virtuoso/fn_bpel_wsdl_upload/" oldhref="fn_bpel_wsdl_upload.html" title="BPEL.BPEL.wsdl_upload" /> <link rel="refentry" href="/virtuoso/fn_bpel_get_var/" oldhref="fn_bpel_get_var.html" title="BPEL.BPEL.getVariableData" /> <link rel="refentry" href="/virtuoso/fn_bpel_set_var/" oldhref="fn_bpel_set_var.html" title="BPEL.BPEL.setVariableData" /> <link rel="refentry" href="/virtuoso/fn_plink_get_option/" oldhref="fn_plink_get_option.html" title="BPEL.BPEL.plink_get_option" /> <link rel="refentry" href="/virtuoso/fn_plink_set_option/" oldhref="fn_plink_set_option.html" title="BPEL.BPEL.plink_set_option" /> <link rel="refentry" href="/virtuoso/fn_bpel_import_script/" oldhref="fn_bpel_import_script.html" title="BPEL.BPEL.import_script" /> <link rel="refentry" href="/virtuoso/fn_geometrytype/" oldhref="fn_geometrytype.html" title="GeometryType" /> <link rel="refentry" href="/virtuoso/fn_http_st_dxf_entity/" oldhref="fn_http_st_dxf_entity.html" title="http_st_dxf_entity" /> <link rel="refentry" href="/virtuoso/fn_http_st_ewkt/" oldhref="fn_http_st_ewkt.html" title="http_st_ewkt" /> <link rel="refentry" href="/virtuoso/fn_st_ewkt_read/" oldhref="fn_st_ewkt_read.html" title="st_ewkt_read" /> <link rel="refentry" href="/virtuoso/fn_postgis_proj_version/" oldhref="fn_postgis_proj_version.html" title="postgis_proj_version" /> <link rel="refentry" href="/virtuoso/fn_dist_from_point_to_line_segment/" oldhref="fn_dist_from_point_to_line_segment.html" title="dist_from_point_to_line_segment" /> <link rel="refentry" href="/virtuoso/fn_earth_radius/" oldhref="fn_earth_radius.html" title="earth_radius" /> <link rel="refentry" href="/virtuoso/fn_st_exteriorring/" oldhref="fn_st_exteriorring.html" title="ST_ExteriorRing" /> <link rel="refentry" href="/virtuoso/fn_st_geometryn/" oldhref="fn_st_geometryn.html" title="ST_GeometryN" /> <link rel="refentry" href="/virtuoso/fn_st_get_bounding_box/" oldhref="fn_st_get_bounding_box.html" title="st_get_bounding_box" /> <link rel="refentry" href="/virtuoso/fn_st_get_bounding_box_n/" oldhref="fn_st_get_bounding_box_n.html" title="st_get_bounding_box_n" /> <link rel="refentry" href="/virtuoso/fn_haversine_deg_km/" oldhref="fn_haversine_deg_km.html" title="haversine_deg_km" /> <link rel="refentry" href="/virtuoso/fn_st_interiorringn/" oldhref="fn_st_interiorringn.html" title="ST_InteriorRingN" /> <link rel="refentry" href="/virtuoso/fn_st_linestring/" oldhref="fn_st_linestring.html" title="st_linestring" /> <link rel="refentry" href="/virtuoso/fn_st_m/" oldhref="fn_st_m.html" title="ST_M" /> <link rel="refentry" href="/virtuoso/fn_st_may_intersect/" oldhref="fn_st_may_intersect.html" title="st_may_intersect" /> <link rel="refentry" href="/virtuoso/fn_st_mmax/" oldhref="fn_st_mmax.html" title="ST_MMax" /> <link rel="refentry" href="/virtuoso/fn_st_mmin/" oldhref="fn_st_mmin.html" title="ST_MMin" /> <link rel="refentry" href="/virtuoso/fn_st_numgeometries/" oldhref="fn_st_numgeometries.html" title="ST_NumGeometries" /> <link rel="refentry" href="/virtuoso/fn_st_numinteriorrings/" oldhref="fn_st_numinteriorrings.html" title="ST_NumInteriorRings" /> <link rel="refentry" href="/virtuoso/fn_st_transform/" oldhref="fn_st_transform.html" title="ST_Transform" /> <link rel="refentry" href="/virtuoso/fn_st_transform_by_custom_projection/" oldhref="fn_st_transform_by_custom_projection.html" title="st_transform_by_custom_projection" /> <link rel="refentry" href="/virtuoso/fn_st_translate/" oldhref="fn_st_translate.html" title="ST_Translate" /> <link rel="refentry" href="/virtuoso/fn_st_transscale/" oldhref="fn_st_transscale.html" title="ST_TransScale" /> <link rel="refentry" href="/virtuoso/fn_st_xmax/" oldhref="fn_st_xmax.html" title="ST_XMax" /> <link rel="refentry" href="/virtuoso/fn_st_xmin/" oldhref="fn_st_xmin.html" title="ST_XMin" /> <link rel="refentry" href="/virtuoso/fn_st_ymax/" oldhref="fn_st_ymax.html" title="ST_YMax" /> <link rel="refentry" href="/virtuoso/fn_st_ymin/" oldhref="fn_st_ymin.html" title="ST_YMin" /> <link rel="refentry" href="/virtuoso/fn_st_z/" oldhref="fn_st_z.html" title="ST_Z" /> <link rel="refentry" href="/virtuoso/fn_st_zmax/" oldhref="fn_st_zmax.html" title="ST_ZMax" /> <link rel="refentry" href="/virtuoso/fn_st_zmflag/" oldhref="fn_st_zmflag.html" title="ST_Zmflag" /> <link rel="refentry" href="/virtuoso/fn_st_zmin/" oldhref="fn_st_zmin.html" title="ST_ZMin" /> <link rel="section" href="/virtuoso/ch-server/" oldhref="ch-server.html#databaseadmsrv" title="6.1.聽Database Server Administration" /> <link rel="section" href="/virtuoso/htmlconductorbar/" oldhref="htmlconductorbar.html" title="6.2.聽HTML based Administration Console (Conductor) Guide" /> <link rel="section" href="/virtuoso/clusteroperation/" oldhref="clusteroperation.html" title="6.3.聽Virtuoso Cluster Operation" /> <link rel="section" href="/virtuoso/fault/" oldhref="fault.html" title="6.4.聽Virtuoso Cluster Fault Tolerance" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta name="keywords" content="documentation , docs , openlink , openlink software , virtuoso , database , SQL , PL , RDBMS " /> <meta name="date" property="http://purl.org/dc/terms/created" itemprop="http://schema.org/dateCreated" content="" /> <link rel="canonical" href="http://docs.openlinksw.com/virtuoso/ch-server/" /> <style type="text/css"> body * { font-display: swap; } div#repaint { position: absolute; width: 100%; height: 100%; left: 0; top: 0; background-color: white; z-index: 1000; } </style><script type="text/javascript"> function embedToData(id, encodeURI=1) { var fieldnames = $("#" + id).xpath("*//div[contains(@class,'header') and contains(@class,'field')]").map(function(idx, x) { return x.innerHTML }).toArray(); var rows = $.xpath("#"+id, "div[contains(@class,'results')]/div"); var norows=rows.length; var nocols=fieldnames.length; var data=[]; for(r=0; r<norows; r++) { data[r]={}; for(c=0; c<nocols; c++) { data[r][fieldnames[c]]=rows[r].children[c].innerHTML; if(!encodeURI) { data[r][fieldnames[c]]=rows[r].children[c].innerText.trim(); } } } return data; } function embedToDataCSV(id, encodeURI=1) { var fieldnames = $("#" + id).xpath("*//div[contains(@class,'header') and contains(@class,'field')]").map(function(idx, x) { return x.innerHTML }).toArray(); var rows = $.xpath("#"+id, "div[contains(@class,'results')]/div"); var norows=rows.length; var nocols=fieldnames.length; var data=[]; for(r=0; r<norows; r++) { data[r]=[]; for(c=0; c<nocols; c++) { data[r][c]=rows[r].children[c].innerHTML; if(!encodeURI) { data[r][c]=rows[r].children[c].innerText.trim(); } } } var obj=Object(); obj.data=data; obj.dims=[ nocols, norows ]; obj.fieldnames=fieldnames; return obj; } </script> </head> <body onload="pageOnLoad()"> <div class="gridcontainer"> <header class="masthead"> <ul> <li> <a href="//www.openlinksw.com/"><img src="/skin/docs-v3/images/logo.png" alt="OpenLink Software logo" /> </a> </li> <li> <a href="//www.openlinksw.com/" title="Corporate Homepage"> OpenLink Software</a> </li> <li> <a href="//docs.openlinksw.com" title="Product Documentation">Documentation</a> </li> <li> <a href="//community.openlinksw.com" title="Community Discussion Forum">Community Forum</a> </li> <li> <a href="//support.openlinksw.com" title="Customer Support Portal">Support</a> </li> <li> <a href="//shop.openlinksw.com" title="OpenLink Shop">Shop</a> </li> <li> <a href="//virtuoso.openlinksw.com" title="Virtuoso Universal Server product home">Virtuoso</a> </li> <li> <a href="//uda.openlinksw.com" title="Universal Data Access Drivers products">UDA</a> </li> </ul> <div id="search"> <form id="searchform" name="searchform" action="/search.vsp" method="post"><input type="text" name="q" size="24" id="new_search_txt" accesskey="/" value="search..." onclick="javascript:this.value=''" /> <svg onclick="javascript:document.searchform.submit()" viewBox="0 0 24 24" fill="currentColor" width="1em" height="1em" class="x1lliihq x1heor9g xxk0z11 xvy4d1p" role="img" aria-label="Search"><path fill-rule="evenodd" clip-rule="evenodd" d="M16.618 18.032a9 9 0 1 1 1.414-1.414l3.675 3.675a1 1 0 0 1-1.414 1.414l-3.675-3.675zM18 11a7 7 0 1 1-14 0 7 7 0 0 1 14 0z"></path> </svg> </form> </div> </header> <div class="leftmargin"> <div class="navfootertop"> <table width="100%"> <tr width="100%"> <td id="navfootertopprev" width="50%" align="center"></td> <td id="navfootertopnext" width="50%" align="center"></td> </tr> </table> </div> <div class="hamburger" onclick="toggleMenu()"> <div class="bar"></div> <div class="bar"></div> <div class="bar"></div> </div> <div class="menu" id="menu"> <ul> <li class="menupoint"> <a href="/">Documentation Home</a> </li> <li class="menupoint expandable"> <a id="menuuda" onclick="toggleSubmenu(this)">Universal Data Access (UDA) Documentation <br /> - ODBC, JDBC, ADO.NET, OLEDB </a> <ul class="submenu"> <li> <a href="http://wikis.openlinksw.com/UdaWikiWeb/UDAInstallConfig">Installation Guide</a> </li> <li> <a onclick="toggleSubmenu(this)">Enterprise Edition (Multi-Tier) Manual</a> <ul class="submenu"> <li> <a href="/uda/mt/mt/">OpenLink ODBC Driver (Multi-Tier Edition) Documentation</a> </li> <li> <a href="/uda/mt/bk01pr01/">Preface</a> </li> <li> <a href="/uda/mt/mt_overview/">Overview</a> </li> <li> <a href="/uda/mt/mt_newfeatures/">New Features in OpenLink UDA</a> </li> <li> <a href="/uda/mt/mt_clientcompinstall/">OpenLink ODBC Driver (Multi-Tier Edition) Client Component</a> </li> <li> <a href="/uda/mt/mt_dotnet/">OpenLink ADO.NET Data Providers</a> </li> <li> <a href="/uda/mt/mt_oledb/">OpenLink OLE-DB Provider</a> </li> <li> <a href="/uda/mt/mt_srvcompinstall/">Server Components Installation</a> </li> <li> <a href="/uda/mt/mt_SrvCompAdm/">Request Broker Administration</a> </li> <li> <a href="/uda/mt/mt_AgentCompAdm/">Server Agent Administration</a> </li> <li> <a href="/uda/mt/mt_uda52ssl/">Securing a Multi-Tier connection using SSL</a> </li> <li> <a href="/uda/mt/mt_UDAZeroConf/">Zero Configuration Networking</a> </li> <li> <a href="/uda/mt/mt_JDBCClientClasses/">JDBC Components</a> </li> <li> <a href="/uda/mt/mt_xamt/">Distributed Transaction Processing (XA)</a> </li> <li> <a href="/uda/mt/mt_udauserrac/">Real Application Cluster (RAC) / TAF Support</a> </li> <li> <a href="/uda/mt/mt_iodbc/">OpenLink ODBC Driver Manager (iODBC SDK)</a> </li> <li> <a href="/uda/mt/mt_sampleapps/">Sample Applications</a> </li> <li> <a href="/uda/mt/mt_bugsfixed/">Bugs Fixed</a> </li> <li> <a href="/uda/mt/mt_appendix/">Technical Appendix</a> </li> </ul> </li> <li> <a onclick="toggleSubmenu(this)">Express Edition (Single-Tier) Manual</a> <ul class="submenu"> <li> <a href="/uda/ee/ee_EEIntro/">OpenLink ODBC Driver (Express Edition) Documentation</a> </li> <li> <a href="/uda/ee/ee_licensing/">Product Licensing</a> </li> <li> <a href="/uda/ee/ee_EEDB2/">OpenLink ODBC Driver for DB2 (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEFireBird/">OpenLink ODBC Driver for Firebird (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEInformix/">OpenLink ODBC Driver for Informix (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEIngres/">OpenLink ODBC Driver for Ingres (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEMySQL/">OpenLink ODBC Driver for MySQL (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEOracle/">OpenLink ODBC Driver for Oracle (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EEPostgres/">OpenLink ODBC Driver for PostgreSQL (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EESQLServer/">OpenLink ODBC Driver for SQL Server (Express Edition)</a> </li> <li> <a href="/uda/ee/ee_EESybase/">OpenLink ODBC Driver for Sybase (Express Edition)</a> </li> </ul> </li> <li> <a onclick="toggleSubmenu(this)">Lite Edition (Single-Tier) Manual</a> <ul class="submenu"> <li> <a href="/uda/lite/bk03pr01/">Preface</a> </li> <li> <a href="/uda/lite/lite_odbcintro/">Overview</a> </li> <li> <a href="/uda/lite/lite_newfeatures/">New Features in OpenLink UDA</a> </li> <li> <a href="/uda/lite/lite_requirements/">OpenLink ODBC Driver (Single-Tier Edition) System Requirements and Basic Instructions</a> </li> <li> <a href="/uda/lite/lite_installation/">OpenLink ODBC Driver (Single-Tier Edition) Installation</a> </li> <li> <a href="/uda/lite/lite_datasource/">OpenLink ODBC Driver (Single-Tier Edition) Configuration</a> </li> <li> <a href="/uda/lite/lite_dotnet/">OpenLink ADO.NET Data Providers</a> </li> <li> <a href="/uda/lite/lite_oled b/">OpenLink OLE-DB Provider</a> </li> <li> <a href="/uda/lite/lite_tuning/">OpenLink ODBC Driver (Single-Tier Edition) Performance Tuning</a> </li> <li> <a href="/uda/lite/lite_iodbc/">OpenLink ODBC Driver Manager (iODBC SDK)</a> </li> <li> <a href="/uda/lite/lite_mac/">Mac OS X Specifics</a> </li> <li> <a href="/uda/lite/lite_jdbc/">JDBC Components</a> </li> <li> <a href="/uda/lite/lite_xa/">Distributed Transaction Processing (XA)</a> </li> <li> <a href="/uda/lite/lite_udauserrac/">Real Application Cluster (RAC) / TAF Support</a> </li> <li> <a href="/uda/lite/lite_odbcwithperl/">Using OpenLink Single-Tier ODBC Drivers with Perl</a> </li> <li> <a href="/uda/lite/lite_sampleapps/">Sample Applications</a> </li> <li> <a href="/uda/lite/lite_bugsfixed/">Bugs Fixed</a> </li> <li> <a href="/uda/lite/lite_appendix/">Technical Appendix</a> </li> </ul> </li> </ul> </li> <li class="menupoint expandable"> <a id="menuvirtuoso" onclick="toggleSubmenu(this)">Virtuoso Documentation</a> <ul class="submenu"> <li> <a href="http://wikis.openlinksw.com/VirtuosoWikiWeb/VirtuosoInstallConfig">Installation Guide</a> </li> <li class="expandable"> <a id="menuvirtuosoinside" onclick="toggleSubmenu(this)">Manual</a> <ul class="submenu"> <li> <a href="/virtuoso/">Home</a> </li> <li> <a href="/virtuoso/preface/">Preface</a> </li> <li> <a href="/virtuoso/ch-overview/">Overview</a> </li> <li> <a href="/virtuoso/ch-installation/">Installation Guide</a> </li> <li> <a href="/virtuoso/ch-quicktours/">Quick Start &Tours</a> </li> <li> <a href="/virtuoso/ch-sampleapps/">Sample ODBC &JDBC Applications</a> </li> <li> <a href="/virtuoso/ch-concepts/">Conceptual Overview</a> </li> <li> <a href="/virtuoso/ch-server/">Conductor Guide</a> </li> <li> <a href="/virtuoso/ch-server/">Virtuoso Server</a> </li> <li> <a href="/virtuoso/ch-accessinterfaces/">Data Access Interfaces</a> </li> <li> <a href="/virtuoso/ch-vdbengine/">Virtual Database Engine</a> </li> <li> <a href="/virtuoso/ch-sqlreference/">SQL Reference</a> </li> <li> <a href="/virtuoso/ch-clusterprogramming/">Virtuoso Cluster Programming</a> </li> <li> <a href="/virtuoso/ch-sqlprocedures/">SQL Procedure Language Guide</a> </li> <li> <a href="/virtuoso/ch-hooks/">Database Event Hooks</a> </li> <li> <a href="/virtuoso/ch-repl/">Data Replication Services</a> </li> <li> <a href="/virtuoso/ch-webappdevelopment/">Web Application Development</a> </li> <li> <a href="/virtuoso/ch-webandxml/">XML Support</a> </li> <li> <a href="/virtuoso/ch-rdfandsparql/">RDF Data Access Management</a> </li> <li> <a href="/virtuoso/ch-webservices/">Web Services</a> </li> <li> <a href="/virtuoso/ch-runtimehosting/">Runtime Hosting</a> </li> <li> <a href="/virtuoso/ch-internetservices/">Internet Services</a> </li> <li> <a href="/virtuoso/ch-freetext/">Free Text Search</a> </li> <li> <a href="/virtuoso/ch-tpcc/">TPC C Benchmark Kit</a> </li> <li> <a href="/virtuoso/ch-xa/">Using Virtuoso with Tuxedo</a> </li> <li> <a href="/virtuoso/ch-appendixa/">Appendix A</a> </li> <li> <a href="/virtuoso/ch-functions/">Functions Reference Guide</a> </li> </ul> </li> <li> <a href="http://wikis.openlinksw.com/VirtuosoWikiWeb/WelcomeVisitors">Evolving Documentation</a> </li> </ul> </li> <li class="menupoint"> <a onclick="toggleSubmenu(this)">OpenLink Software</a> <ul> <li> <a href="http://uda.openlinksw.com/">Universal Data Access (UDA)</a> <ul class="submenu"> <li>ODBC, JDBC, ADO.NET and OleDB Drivers</li> </ul> </li> <li> <a href="http://virtuoso.openlinksw.com/">Virtuoso</a> </li> <li> <a href="http://vos.openlinksw.com/">Virtuoso Open-Souce Edition</a> </li> <li> <a href="http://osde.openlinksw.com/">OpenLink Structured Data Editor</a> </li> <li> <a href="http://osds.openlinksw.com/">OpenLink Structured Data Sniffer</a> </li> <li> <a href="http://ods.openlinksw.com/wiki/ODS/">OpenLink Data Spaces (ODS)</a> </li> </ul> </li> </ul> </div> </div> <div class="content"> <a id="top">  </a><a href="#top" id="toplink">Top</a> <div> <div> <div class="breadcrumbs" style="display:none;"> <ul> <li class="breadcrumb-link"> <a href="/virtuoso/index/">OpenLink Virtuoso Universal Server Documentation </a> <ul> <li class="breadcrumb-node"></li> </ul> </li> </ul> </div> </div> <div id="thecontent">  <div class="chapter" id="ch-server"> <div class="titlepage"> <div> <div> <h1 class="title">Chapter聽6.聽Administration</h1> </div> </div> </div> <div class="toc"> <p> <strong>Table of Contents</strong> </p> <dl class="toc"> <dt> <span class="section">6.1. <a href="/virtuoso/ch-server/#databaseadmsrv">Database Server Administration</a> </span> </dt> <dd> <dl> <dt> <span class="section">6.1.1. <a href="/virtuoso/ch-server/#dbadm">Database</a> </span> </dt> <dt> <span class="section">6.1.2. <a href="/virtuoso/ch-server/#vdbconcepts">Virtual Database</a> </span> </dt> <dt> <span class="section">6.1.3. <a href="/virtuoso/ch-server/#usermodel">Virtuoso User Model</a> </span> </dt> <dt> <span class="section">6.1.4. <a href="/virtuoso/ch-server/#vaddistr">VAD - Virtuoso Application Distribution</a> </span> </dt> <dt> <span class="section">6.1.5. <a href="/virtuoso/ch-server/#backup_recovery">Data Backup & Recovery</a> </span> </dt> <dt> <span class="section">6.1.6. <a href="/virtuoso/ch-server/#perfdiag">Performance diagnostics</a> </span> </dt> <dt> <span class="section">6.1.7. <a href="/virtuoso/ch-server/#ptune">Performance Tuning</a> </span> </dt> </dl> </dd> <dt> <span class="section">6.2. <a href="/virtuoso/htmlconductorbar/">HTML based Administration Console (Conductor) Guide</a> </span> </dt> <dd> <dl> <dt> <span class="section">6.2.1. <a href="/virtuoso/htmlconductorbar/#conductorbar">Virtuoso Conductor Administration</a> </span> </dt> <dt> <span class="section">6.2.2. <a href="/virtuoso/admui.runtimehosting/">Runtime Hosting</a> </span> </dt> <dt> <span class="section">6.2.3. <a href="/virtuoso/admui.webservices/">Web Services</a> </span> </dt> <dt> <span class="section">6.2.4. <a href="/virtuoso/webdavadmin/">WebDAV Administration</a> </span> </dt> <dt> <span class="section">6.2.5. <a href="/virtuoso/admui.internetdomains/">Internet Domains</a> </span> </dt> <dt> <span class="section">6.2.6. <a href="/virtuoso/admui.xmlservices/">XML Services</a> </span> </dt> <dt> <span class="section">6.2.7. <a href="/virtuoso/querytools/">Query Tools</a> </span> </dt> <dt> <span class="section">6.2.8. <a href="/virtuoso/replicationandsynchronization/">Replication & Synchronization</a> </span> </dt> <dt> <span class="section">6.2.9. <a href="/virtuoso/dbadmin/">Database Administration</a> </span> </dt> <dt> <span class="section">6.2.10. <a href="/virtuoso/rdfadm/">Conductor Linked Data Administration</a> </span> </dt> <dt> <span class="section">6.2.11. <a href="/virtuoso/newssrvadm/">Conductor News Server Administration</a> </span> </dt> </dl> </dd> <dt> <span class="section">6.3. <a href="/virtuoso/clusteroperation/">Virtuoso Cluster Operation</a> </span> </dt> <dd> <dl> <dt> <span class="section">6.3.1. <a href="/virtuoso/clusteroperation/#clusteroperationgeneral">General</a> </span> </dt> <dt> <span class="section">6.3.2. <a href="/virtuoso/clusteroperationsetcl/">Setting up a Cluster</a> </span> </dt> <dt> <span class="section">6.3.3. <a href="/virtuoso/clusteroperationexdb/">Using Clustering with an Existing Database</a> </span> </dt> <dt> <span class="section">6.3.4. <a href="/virtuoso/clusteroperationpart/">Partitioning</a> </span> </dt> <dt> <span class="section">6.3.5. <a href="/virtuoso/clusteroperationtransc/">Transactions</a> </span> </dt> <dt> <span class="section">6.3.6. <a href="/virtuoso/clusteroperationadmin/">Administration</a> </span> </dt> <dt> <span class="section">6.3.7. <a href="/virtuoso/clusteroperationdiagnostics/">Cluster Network Diagnostics and Metrics</a> </span> </dt> <dt> <span class="section">6.3.8. <a href="/virtuoso/elasticclusteroperation/">Elastic Cluster Operations</a> </span> </dt> <dt> <span class="section">6.3.9. <a href="/virtuoso/ch06s03s09/">Setting CPU Affinity</a> </span> </dt> </dl> </dd> <dt> <span class="section">6.4. <a href="/virtuoso/fault/">Virtuoso Cluster Fault Tolerance</a> </span> </dt> <dd> <dl> <dt> <span class="section">6.4.1. <a href="/virtuoso/fault/#faultfaulttolerinto">Introduction</a> </span> </dt> <dt> <span class="section">6.4.2. <a href="/virtuoso/faultfaulttolersampleconfig/">Sample Configuration</a> </span> </dt> <dt> <span class="section">6.4.3. <a href="/virtuoso/faultfaulttolertransactions/">Transactions</a> </span> </dt> <dt> <span class="section">6.4.4. <a href="/virtuoso/faultfaulttolerdivid/">Dividing Virtuoso Hosts Over Physical Machines</a> </span> </dt> <dt> <span class="section">6.4.5. <a href="/virtuoso/faultfaulttolermng/">Managing Availability</a> </span> </dt> <dt> <span class="section">6.4.6. <a href="/virtuoso/faultfaulttoleroptm/">Optimizing Schema for Fault Tolerance</a> </span> </dt> <dt> <span class="section">6.4.7. <a href="/virtuoso/faultfaulttolerinterprt/">Interpreting Status Messages</a> </span> </dt> <dt> <span class="section">6.4.8. <a href="/virtuoso/faultfaulttoleradmapi/">Administration API</a> </span> </dt> <dt> <span class="section">6.4.9. <a href="/virtuoso/faultfaulttolerrdfspecf/">RDF Specifics</a> </span> </dt> <dt> <span class="section">6.4.10. <a href="/virtuoso/faultfaulttolerpragram/">Fault Tolerance Programming</a> </span> </dt> </dl> </dd> </dl> </div> <div> <span class="permalink"><a id="databaseadmsrv" onclick="javascript:permalink(this)" href="#databaseadmsrv">露</a> </span> <div class="titlepage"> <div> <div> <h2 class="title">6.1.聽Database Server Administration</h2> </div> <div> <div class="abstract"> <p class="title"> <strong>Abstract</strong> </p> <p> This section explains the use of the server executables, configuration files and general administration procedures. These include backup, server tuning and profiling, installing extension packages etc. See the Access Interfaces chapter for a discussion of the command line SQL interface. </p> </div> </div> </div> </div> <div> <span class="permalink"><a id="dbadm" onclick="javascript:permalink(this)" href="#dbadm">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.1.聽Database</h3> </div> </div> </div> <p>See details for <a href="/virtuoso/ch-installation/#srvadminstallreqt">Installation Requirements</a> , <a href="/virtuoso/ch-installation/#srvadmopreq">Operational Requirements</a> , <a href="/virtuoso/ch-installation/#srvadmossupport">Operating System Support</a> and <a href="/virtuoso/ch-installation/#limitsandparameters">Limits</a> .</p> <div> <span class="permalink"><a id="srvadmsrvinst" onclick="javascript:permalink(this)" href="#srvadmsrvinst">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Server Instance Creation</h4> </div> </div> </div> <p>Multiple Virtuoso server instances may coexist on a single machine. Each database will need to be assigned a unique TCP port number. On the windows platforms (except 95,98,ME) the Virtuoso can be configured for multiple services. For further details, see the <a href="/virtuoso/creatingdeletingservices/">Creating and Deleting Virtuoso Services</a> in the Installation chapter. </p> <p>To run Virtuoso on a machine, only the Virtuoso server executable and a valid virtuoso.ini file are needed. An empty database file will be created automatically at first startup. None of the other files in the installation are needed for basic operation. Client interfaces may additionally need ODBC drivers or the like to be set up in system configuration files or the Windows registry but the server itself does not depend on these. </p> </div> <div> <span class="permalink"><a id="srvextinst" onclick="javascript:permalink(this)" href="#srvextinst">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Installing Application Packages</h4> </div> </div> </div> <p> Virtuoso comes with optionally installable SQL application packages (VAD packages) for web based admin, on-line documentation, programming tutorials and a BPEL processor. The installer typically asks whether to install these into the demo or the default empty database. Depending on the OS and form of installer, also depending on whether the installation is the commercial or open source one, the package files will be in different locations. To locate them, look for *.vad. The packages are typically made in two variants, where one keeps the installed items in the DAV repository and the other in the file system. They are functionally equivalent in most cases, except for some tutorials that will only work in the file system. Keeping installed resources in DAV has advantages when moving the database or backing up, since the installed items will not have to be treated separately. To install these on a database, login as dba using the isql utility and issue the SQL command: </p> <pre class="programlisting"> # at the OS command line prompt, assuming the dba password is dba and the server is at the default port 1111: $ isql 1111 dba dba -- At the SQL prompt: SQL> vad_install ('conductor_dav.vad', 0); -- The path is relative to the server's working directory. </pre> <p> Since the packages are read from and sometimes the extracted contents are written to the file system, the server must have access to the directories in question. Checjk OS permissions and set the DirsAllowed parameter in the ini file to allow the needed access. </p> <p> After the packages are installed, they can be used by pointing the web browser to their start page. The start pages are listed on the root page of the demo database and at the Getting Started section of the Open Virtuoso web site. The start page for the Conductor web admin interface is /conductor, the docs are at /doc/html, the tutorials at /tutorial, the BPEL admin and demos at /BPELGUI. All these are directly under the default Virtuoso web listener, the port is shown in the messages log and read from the HTTP Server section of the virtuoso.ini file. </p> </div> <div> <span class="permalink"><a id="srvadmlicensing" onclick="javascript:permalink(this)" href="#srvadmlicensing">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Server Licensing</h4> </div> </div> </div> <p>The Virtuoso server requires a valid license file before it will successfully start. The license file is a file always called <span class="emphasis"><em>virtuoso.lic</em></span> and must reside in the working directory of the database instance - where the <database-name>.db file resides for the instance.</p> <p>Evaluations versions of Virtuoso come without a license file, however the registration procedure takes your email address, which will be used to email a new license file for you evaluation.</p> </div> <div> <span class="permalink"><a id="srvadmlogging" onclick="javascript:permalink(this)" href="#srvadmlogging">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Server Logging - Detecting Errors</h4> </div> </div> </div> <p>Virtuoso provides extensive log information for resolving problems. Should any problems arise Virtuoso logs should always be consulted.</p> <p>The Virtuoso server by default will send log information to two places, the appropriate system log for the operating system and the virtuoso.log file. On Unix based operating systems, including Linux, this information will appear in the system log files. On Windows the Virtuoso log information will appear in the Application Event Log.</p> <p>Virtuoso logs information in the system logs before the Virtuoso.log file is open. This advantageously will log errors that cannot be placed in the virtuoso.log file, such as when the virtuoso.ini file cannot be located during Virtuoso startup.</p> <p>The system log feature can be disabled using the "Syslog" parameter in the [Database] section. This is described in more detail in the following section.</p> </div> <div> <span class="permalink"><a id="configsrvstupfiles" onclick="javascript:permalink(this)" href="#configsrvstupfiles">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Configuring Server Startup Files</h4> </div> </div> </div> <div> <span class="permalink"><a id="virtini" onclick="javascript:permalink(this)" href="#virtini">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Virtuoso Configuration File</h5> </div> </div> </div> <p>The virtuoso.ini file is read from the directory that is current at server startup. This file contains an entry for all user settable options in the server. It is divided into the following sections: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>[Database] Location of database files</p> </li> <li class="listitem"> <p>[Parameters] Server tuning, options</p> </li> <li class="listitem"> <p>[HTTPServer] Settings in this section control the web server component of the Virtuoso Server.</p> </li> <li class="listitem"> <p>[URIQA] Settings in this optional section control URIQA semantic web enabler.</p> </li> <li class="listitem"> <p>[Flags] Settings for options that are generally used with <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> as temporally valid ( such as enable_joins_only), to be set as permanent.</p> </li> <li class="listitem"> <p>[SPARQL] Settings in this optional section control SPARQL protocol endpoint default parameters and limits.</p> </li> <li class="listitem"> <p>[I18N] encoding settings</p> </li> <li class="listitem"> <p>[Replication] The replication section sets the transactional replication parameters for the server. </p> </li> <li class="listitem"> <p>[Mono] The Mono section contains settings for Virtuoso with Mono Runtime CLR support. </p> </li> <li class="listitem"> <p>[Client] Client default settings</p> </li> <li class="listitem"> <p>[AutoRepair] Corrupted database recovery</p> </li> <li class="listitem"> <p>[Striping] Multi-file / multi-disk databases</p> </li> <li class="listitem"> <p>[VDB] Virtual database functionality related options</p> </li> <li class="listitem"> <p>[Ucms] location of UCM files describing multi-byte encodings such as Far East languages</p> </li> <li class="listitem"> <p>[Zero Config] ZeroConfig related options</p> </li> <li class="listitem"> <p>[Plugins] VSEI plugin modules</p> </li> </ul> </div> <p>Below are the descriptions for each parameter</p> <div> <span class="permalink"><a id="ini_database" onclick="javascript:permalink(this)" href="#ini_database">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Database]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_database_databasefile"> <p> <strong>DatabaseFile=virtuoso.db.聽</strong> For a single file database, this is the relative path of the file in the format appropriate to the platform. The path is resolved relative to the directory that is current at server startup. All other paths are interpreted similarly. </p> </li> <li class="listitem" id="ini_database_transactionfile"> <p> <strong>TransactionFile=virtuoso.trx.聽</strong> This is the transaction log file. If this parameter is omitted, which should never be the case in practice, the database will run without log, meaning that it cannot recover transactions committed since last checkpoint if it should abnormally terminate. There is always a single log file for one server. The file grows as transactions get committed until a checkpoint is reached at which time the transactions are applied to the database file and the trx file is reclaimed, unless CheckpointAuditTrail is enabled. </p> </li> <li class="listitem" id="ini_database_errorlogfile"> <p> <strong>ErrorLogFile=virtuoso.log.聽</strong> This file logs database error messages, e.g. 'out of disk'. By viewing this the dba can trace problems and see at which times the server has started, checkpoints have been made, etc. </p> </li> <li class="listitem" id="ini_database_errorloglevel"> <p> <strong>ErrorLogLevel=7.聽</strong> This controls what events get logged into the database error log. This should always be 7. </p> </li> <li class="listitem" id="ini_database_lockfile"> <p> <strong>LockFile=virtuoso.lck.聽</strong> This optional parameter can be used to manually specify the location of the Virtuoso lock (.lck) file. This can be relative or the full path to the lock file. Virtuoso, by default, creates a file with the same name as the DatabaseFile but with the extension of .lck. This file exists when the Virtuoso server is running to prevent it starting multiple times using the same parameters, and should be automatically removed by the server upon exit. However, not all file systems support file locking, such as NFS, therefore this parameter can be set to keep the lock file on a more appropriate file system. </p> </li> <li class="listitem" id="ini_database_fileextend"> <p> <strong>FileExtend=100.聽</strong> This is the size that the database file automatically grows (in 8k pages) when the current file is not large enough. Default = minimum = 100. The parameter has no effect if striping is set. </p> </li> <li class="listitem" id="ini_database_striping"> <p> <strong>Striping=0.聽</strong> A non-zero value will enable the settings in [Striping] to take effect. If this is the case the DatabaseFile parameter is ignored and the files in [striping] are used. </p> </li> <li class="listitem" id="ini_database_logsegments"> <p> <strong>LogSegments.聽</strong> If this is non-zero log segmentation is enabled. This is only used for crash dumps where several files may be needed to accommodate the recovery logs. If non-zero, this will be followed by entries of the form Log1=... </p> </li> <li class="listitem" id="ini_database_log"> <p> <strong>Log1=/tmp/log1.trx 100M.聽</strong> The number in Log<n> is the ordinal number of the log, starting at 1. The entry consists of the file name and allocated size with an optional size modifier. Available modifiers are B for blocks of 4k (default if unspecified, K for kilobytes, M for megabytes, and G for gigabytes. The log is filled up to the first transaction that exceeds the size. The log therefore will be longer than the allocated size. If blobs are involved, this amount can be quite substantial. It is therefore advisable to have some extra space available on the storage device used for recovery logs. </p> </li> <li class="listitem" id="ini_database_crashdump"> <p> <strong>crashdump_start_dp, crashdump_end_dp.聽</strong> These options make it possible to produce a crash dump of a specified range of disk pages. In case the server runs out of disk space during a dump, the error message indicates the page at which the next dump should be started after the user has made more space available. In this case it is important to rename the already produced crash dump or change the Logx= -entries in virtuoso.ini to avoid overwriting said files. If none of these options are provided, the server will attempt a crash dump of the entire database storage. </p> </li> <li class="listitem" id="ini_database_tempstorage"> <p> <strong>TempStorage = <TempDatabase_Name>.聽</strong> The name of a section in the INI file containing temporary database details. If this parameter is omitted or the section does not exist the default values for temporary storage are used. </p> </li> <li class="listitem" id="ini_database_syslog"> <p> <strong>Syslog = 1/0 (default 0).聽</strong> Virtuoso can writes log worthy messages to the system log (Unix based operating systems including Linux) or the Windows Event Log (Windows operating systems). Messages are written in the system/event log before the virtuoso.log file is opened, therefore errors due to absence of virtuoso.ini log are loggable there. This system/event logging can be enabled using this option, by default it is set to 0 meaning off. </p> <p>On Unix/Linux messages are written as "Virtuoso" events.</p> <p>On Windows messages are written in the Application event log.</p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_tempdatabase" onclick="javascript:permalink(this)" href="#ini_tempdatabase">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[<TempDatabase_Name>]</h6> </div> </div> </div> <p>This section name must match the TempStorage parameter in the Database section of the Virtuoso INI file to be of any use. Otherwise this section will be ignored.</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem" id="ini_tempdatabase_databasefile"> <p> <strong>DatabaseFile = <database file name>.tdb.聽</strong> Name of temporary database file. </p> </li> <li class="listitem" id="ini_tempdatabase_transactionfile"> <p> <strong>TransactionFile = <transaction file name>.ttr.聽</strong> Name of temporary transaction file. </p> </li> <li class="listitem" id="ini_tempdatabase_fileextend"> <p> <strong>FileExtend = NNN.聽</strong> Increment amount by which the database file will dynamically grow. This setting is identical in use and purpose to parameter in the Database section with the same name. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_parameters" onclick="javascript:permalink(this)" href="#ini_parameters">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Parameters]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_parameters_singlecpu"> <p> <strong>SingleCPU=0.聽</strong> This is a Win32 specific option that forces Virtuoso to only run on one CPU in a multiprocessor environment. </p> </li> <li class="listitem" id="ini_parameters_serverport"> <p> <strong>ServerPort=[<IP Address>]:<port>.聽</strong> This is the IP Address and port number where the server will start listening. You do not need to specify the listening IP Address but can do in a situation that you want the server to bind to a specific address only. </p> </li> <li class="listitem" id="ini_parameters_serverthreads"> <p> <strong>ServerThreads=10.聽</strong> This is the maximum number of threads used in the server. This should be close to the number of concurrent connections if heavy usage is expected. Different systems have different limitations on threads per process but a value of 100 should work in most places. </p> </li> <li class="listitem" id="ini_parameters_serverthreadsize"> <p> <strong>ServerThreadSize=50000.聽</strong> Stack size of thread used for reading client messages and accepting connections.(default : 50 000 bytes) </p> </li> <li class="listitem" id="ini_parameters_mainthreadsize"> <p> <strong>MainThreadSize=100000.聽</strong> Stack size of the main thread (default : 100 000 bytes) </p> </li> <li class="listitem" id="ini_parameters_threadcleanupinterval"> <p> <strong>ThreadCleanupInterval.聽</strong> The interval in minutes (default : 0) after which threads in the thread pool should be released. </p> </li> <li class="listitem" id="ini_parameters_threadthreshold"> <p> <strong>ThreadThreshold.聽</strong> The maximum number of threads (default : 10) to leave in the thread queue after thread clean-up interval has expired. </p> </li> <li class="listitem" id="ini_parameters_schedulerinterval"> <p> <strong>SchedulerInterval.聽</strong> Defines the scheduler wake-up interval ( in minutes). By default is 0 i.e. the scheduler is disabled. </p> </li> <li class="listitem" id="ini_parameters_resourcecleanupinterval"> <p> <strong>ResourcesCleanupInterval.聽</strong> The interval in minutes (default : 0) after which allocated resources will be flushed.. </p> </li> <li class="listitem" id="ini_parameters_futurethreadsize"> <p> <strong>FutureThreadSize=100000.聽</strong> Stack size of worker threads. This is the stack size for serving any client SQL statements or HTTP requests. This can be increased if the application uses recursive stored procedures or links in external code needing a large stack. (default 100 000 bytes) </p> </li> <li class="listitem" id="ini_parameters_tempallocationpct"> <p> <strong>TempAllocationPct.聽</strong> A Percentage that may be greater than 100%. This gives a percentage of the main .db file to which the temp db file may grow before starting to reclaim the oldest persistent hash index. Basically if a particular hash index is reusable (i.e. it references only table columns and the values in these columns have not changed) the engine keeps the hash index defined into the temp db for reuse. This parameter allows some control over the temp db file size. </p> </li> <li class="listitem" id="ini_parameters_odirect"> <p> <strong>O_DIRECT.聽</strong> If this is non-zero, the database file(s) will be opened with the O_DIRECT option on platforms where this is supported. This has the effect of doing file system I/O from application buffers directly, bypassing caching by the operating system. This may be useful if a large fraction of RAM is configured as database buffers. If this is on, the file system cache will not grow at the expense of the database process, for example it is less likely to swap out memory that Virtuoso uses for its own database buffers. Mileage will vary according to operating system and version. For large databases where most of system memory is used for database buffers it is advisable to try this. </p> </li> <li class="listitem" id="ini_parameters_checkpointinterval"> <p> <strong>CheckpointInterval=60.聽</strong> This is the interval in minutes at which Virtuoso will automatically make a database checkpoint. The automatic checkpoint will not be made if there is less than MinAutoCheckpointSize bytes in the current transaction log. A checkpoint interval of 0 means that no periodic automatic checkpoints are made. </p> <p> Setting the value to -1 disables also the checkpoints made after a roll forward upon database startup. This setting should be used when backing up the database file(s). This guarantees that even if the server dies and restarts during the copy, no checkpoints that would change these files will take place and thus the backup is clean. </p> <p>the checkpoint_interval SQL function may be used to change the checkpoint interval value while the database is running.</p> </li> <li class="listitem" id="ini_parameters_checkpointsyncmode"> <p> <strong>CheckpointSyncMode=2.聽</strong> This controls how the file system is synchronized after a checkpoint. Once the checkpoint has issued all write system calls it needs it can do one of the following depending on this setting: </p> <p>0. - Continue, leave the OS to flush buffers when it will.</p> <p>1. - Initiate the flush but do not wait for it to complete.</p> <p>2. - Block until the OS has flushed all writes pertaining to any of the database files.</p> </li> <li class="listitem" id="ini_parameters_pagemapcheck"> <p> <strong>PageMapCheck=0.聽</strong> This controls the check of page maps: </p> <p>0. - disables the check of page maps.</p> <p>1. - enables the check of page maps.</p> </li> <li class="listitem" id="ini_parameters_numberofbuffers"> <p> <strong>NumberOfBuffers=2000.聽</strong> This controls the amount of RAM used by Virtuoso to cache database files. This has a critical performance impact and thus the value should be fairly high for large databases. Exceeding physical memory in this setting will have a significant negative impact. For a database-only server about 65% of available RAM could be configured for database buffers. </p> <p>Each buffer caches one 8K page of data and occupies approximately 8700 bytes of memory.</p> </li> <li class="listitem" id="ini_parameters_maxcheckpointremap"> <p> <strong>MaxCheckpointRemap=2000.聽</strong> Specifies how many pages Virtuoso is allowed to remap. Remapping means that pages can consume the space of two actual pages until checkpoint. See the <a href="/virtuoso/checkpoint/#checkpointparams">Checkpoint & Page Remapping</a> section in the SQL Reference chapter for more information. </p> </li> <li class="listitem" id="ini_parameters_prefixresultnames"> <p> <strong>PrefixResultNames=0.聽</strong> This setting should always be 0. </p> </li> <li class="listitem" id="ini_parameters_casemode"> <p> <strong>CaseMode=1.聽</strong> This controls the case sensitivity of the Virtuoso SQL interpreter. The following values are supported: </p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="disc"> <li class="listitem"> <p>0 - SQL is case sensitive and identifiers are stored in the case they are entered in. This is similar to the Progress or Informix default.</p> </li> <li class="listitem"> <p>1 - SQL is case sensitive and Unquoted identifiers are converted to upper case when read. To use non-upper case identifiers, the identifiers must be quoted with double quotes ("). This is similar to Oracle. </p> </li> <li class="listitem"> <p>2 - SQL is case-insensitive and identifiers are stored in the case where first seen. Unlike the situation in other modes, two identifiers differing only in case cannot exist. This is similar to the MS SQL Server 7 default behavior. </p> </li> </ul> </div> <p> </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"><p>Once a database is created in one case mode the case mode should not be changed as that may change the interpretation of stored procedures etc.</p> </td> </tr> </table> </div> <p> </p> </li> <li class="listitem" id="ini_parameters_minautocheckpointsize"> <p> <strong>MinAutoCheckpointSize=4000000.聽</strong> See CheckpointInterval. </p> </li> <li class="listitem" id="ini_parameters_autocheckpointlogsize"> <p> <strong>AutoCheckpointLogSize.聽</strong> This is the size of transaction log in bytes after which an automatic checkpoint is initiated. If this is non-zero, whenever the transaction log size exceeds this size an automatic checkpoint is started. This will result in approximately like sized logs to be generated. This is useful with the CheckpointAuditTrail option for generating a trail of equal sized consecutive logs. </p> </li> <li class="listitem" id="ini_parameters_checkpointaudittrail"> <p> <strong>CheckpointAuditTrail=1.聽</strong> If this is non-zero each checkpoint will start a new log and leave the old transaction log untouched. A 0 value indicates that the transaction log may be reused once the transactions in it have been written in a checkpoint. </p> <p> If it is important to keep an audit trail of all transactions in the database's life time then this option should be true. A new log file will be generated in the old log file's directory with a name ending with the date and time of the new log file's creation. Old log files can be manually copied into backup storage or deleted. Only one log file is active at one time. The newest log file may at any time be written to by the server, but that is the only log file Virtuoso has open at each time. Thus reading any logs is safe. Writing or deleting the active log file will result in loss of data, and possibly referential integrity, in the database. See the <a href="/virtuoso/ch-functions/#backup">Back and Recovery</a> chapter for more information on this and related parameters.</p> </li> <li class="listitem" id="ini_parameters_allowoscalls"> <p> <strong>AllowOSCalls=0.聽</strong> If non-zero the system SQL function is enabled. This will allow a dba group user to run shell commands through SQL. This poses a potential security risk and hence the setting should normally be 0. </p> </li> <li class="listitem" id="ini_parameters_maxstaticcursorrows"> <p> <strong>MaxStaticCursorRows=5000.聽</strong> This is the maximum number of rows returned by a static cursor. Default = 5000 </p> </li> <li class="listitem" id="ini_parameters_freetextbatchsize"> <p> <strong>FreeTextBatchSize=10000000.聽</strong> This is the amount of text data processed in one batch of the free-text index when doing a batch update or non-incrementally reindexing the data. Default : 10,000,000 </p> </li> <li class="listitem" id="ini_parameters_mullunspecifiedparams"> <p> <strong>NullUnspecifiedParams.聽</strong> When set to 1, if an application prepares a statement with insufficient number of input parameters, the unspecified ones are assumed to be NULL. </p> </li> <li class="listitem" id="ini_parameters_collation"> <p> <strong>Collation.聽</strong> Defines a sorting order according to SYS_COLLATIONS. The name supplied to this parameter must be in <a href="/virtuoso/fn_charsets_list/"><code class="function">charsets_list(1)</code></a> . </p> </li> <li class="listitem" id="ini_parameters_dirsallowed"> <p> <strong>DirsAllowed=<path> [, <path>].聽</strong> <path> := <absolute_path> or <relative_path> comma-delimited list of OS directories allowed for file operations such as <code class="function">file_to_string()</code> . The server base directory (the directory containing this INI file) must appear in this list to enable File DSNs to work. On Windows, use "\" as the path separator; on Unix-like OS including Linux and macOS 10.x and later, use ":". The Virtuoso ISQL utility can be used to check the Server DirsAllowed params as described below. The following should show the server's working directory and INI file name in the result. </p> <pre class="programlisting"> SQL> select server_root (), virtuoso_ini_path (); </pre><p> You can also check the relevant INI setting by running the following statement: </p> <pre class="programlisting"> SQL> select cfg_item_value (virtuoso_ini_path (), 'Parameters', 'DirsAllowed'); </pre><p> </p> </li> <li class="listitem" id="ini_parameters_dirsdenied"> <p id="aclinidenied"> <strong>DirsDenied=<path> [, <path>].聽</strong> <path> := <absolute_path> or <relative_path> OS directories denied for file operations. See <a href="/virtuoso/ch-server/#acl">Virtuoso ACL's</a> for information on functions that are restricted. </p> </li> <li class="listitem" id="ini_parameters_vadinstalldir"> <p> <strong>VADInstallDir=<path>.聽</strong> <path> := <absolute_path> or <relative_path> OS directory containig VADs files. When set, enables automatic update of vads on server startup. On Windows use in the path "\". </p> </li> <li class="listitem" id="ini_parameters_sslserverport"> <p> <strong>SSLServerPort.聽</strong> Specifies the port on which the server listens for incoming SSL CLI requests. </p> </li> <li class="listitem" id="ini_parameters_sslcertificate"> <p> <strong>SSLCertificate.聽</strong> The SSL certificate to use (same meaning as the SSLCertificate in HTTPServer section) </p> </li> <li class="listitem" id="ini_parameters_sslprivatekey"> <p> <strong>SSLPrivateKey.聽</strong> The server's private key (same meaning as the SSLCertificate in HTTPServer section) </p> </li> <li class="listitem" id="ini_parameters_maxoptimizelayouts"> <p> <strong>MaxOptimizeLayouts = 1000.聽</strong> This parameter governs the maximum number of partial or full join orders that the Virtuoso SQL Optimized compiler will calculate per select statement. When MaxOptimizeLayouts has been reached, the best execution plan reached thus far will be used. The default value is 1000, specifying 0 will try all possible orders and guarantee that the best plan is reached. </p> </li> <li class="listitem" id="ini_parameters_stopcompilerwhenxoverruntime"> <p> <strong>StopCompilerWhenXOverRunTime = 0.聽</strong> The default value is 0. If non-zero, this specifies that the SQL compiler should stop considering alternative execution plans after the elapsed compilation time exceeds the best run time estimate times the parameter. For example, if this is 2, then compilation stops after using twice the time of the best plan reached thus far. Enabling this option increases performance when processing short running queries that are each executed once. Using this with long running queries or prepared parametrized queries is not useful and may lead to non-optimal plans being selected. </p> </li> <li class="listitem" id="ini_parameters_traceon"> <p> <strong>TraceOn = option1 [, option2 [, ..]].聽</strong> This parameter accepts a comma-delimited list of tracing options to activate by default. Enabled trace options will list there respective errors in the virtuoso.log file when encountered. Valid options are: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>user_log</td> </tr> <tr> <td>failed_log</td> </tr> <tr> <td>compile</td> </tr> <tr> <td>ddl_log</td> </tr> <tr> <td>client_sql</td> </tr> <tr> <td>errors</td> </tr> <tr> <td>dsn</td> </tr> <tr> <td>sql_send</td> </tr> <tr> <td>transact</td> </tr> <tr> <td>remote_transact</td> </tr> <tr> <td>exec</td> </tr> <tr> <td>soap</td> </tr> </table> <p> </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"><p>The functions: <a href="/virtuoso/fn_trace_on/"><code class="function">trace_on()</code></a> and <a href="/virtuoso/fn_trace_off/"><code class="function">trace_off()</code></a> which use the same options and can turn logging options on/off while the server is running.</p> </td> </tr> </table> </div> <p> </p> <div class="example" id="ex_traceoniniopt"> <p class="title"> <strong>Example聽6.1.聽Using the TraceOn ini file option</strong> </p> <div class="example-contents"> <pre class="programlisting"> [Parameters] .... TraceOn = soap, errors ... </pre><p>This will enable logging of additional information regarding SOAP calls and SQL run-time errors into the virtuoso.log file.</p> </div> </div> <p> <br class="example-break" /> </p> <div class="example" id="ex_threadcleanupinterval"> <p class="title"> <strong>Example聽6.2.聽Using the ThreadCleanupInterval and ResourcesCleanupInterval ini file option</strong> </p> <div class="example-contents"> <pre class="programlisting"> [Parameters] .... ThreadCleanupInterval = 1 ResourcesCleanupInterval = 1 ... </pre><p>Set both to 1 in order to clean up unused threads/resources and reduce memory consumption of the Virtuoso server, which can otherwise be construed as memory leaks.</p> </div> </div> <p> <br class="example-break" /> </p> <p>If an invalid option is set then this error will be listed in the virtuoso.log file upon server startup. Virtuoso will continue to log selected options unless the trace_off() function is called for that item.</p> </li> <li class="listitem" id="ini_parameters_allowpasswordencryption"> <p> <strong>AllowPasswordEncryption = 1/0.聽</strong> Determines whether Virtuoso encryption should be accepted from client connections. The default value is 1 - on. If set to 0 then only clear text and digest authentication will be accepted. </p> </li> <li class="listitem" id="ini_parameters_javaclasspath"> <p> <strong>JavaClasspath.聽</strong> This parameter is applied to the environment prior to the server's startup. It is valid only for binaries hosted in the Virtuoso Java VM. This has the same format as the Java CLASSPATH environment variable for the platform being used. </p> <p>Virtuoso searches for classes in the following order:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>The java_vm_create VSE parameter list</td> </tr> <tr> <td>This "JavaClasspath" in [Parameters] INI section</td> </tr> <tr> <td>The CLASSPATH environment variable</td> </tr> <tr> <td>If none of the above the CLASSPATH is the current directory.</td> </tr> </table> </li> <li class="listitem" id="ini_parameters_javavmoption"> <p> <strong>JavaVMOption1..N = <opts>.聽</strong> These can be used for setting Java options for the Java runtime hosted in Virtuoso. These options work as if provided as command line options to the JRE's Java command line. </p> <p>More than one line of options can be specified by using consecutively numbered options:</p> <pre class="programlisting"> JavaVMOption1 = -Ddt1=val1 JavaVMOption2 = -Ddt2=val2 ... JavaVMOption5 = -Ddt5=val5 </pre> </li> <li class="listitem" id="ini_parameters_pldebug"> <p> <strong>PLDebug = 0.聽</strong> The PLDebug switch controls the type of debugging enabled: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <span class="emphasis"><em>PLDebug = 0</em> </span> - default debugging information and test coverage disabled.</td> </tr> <tr> <td> <span class="emphasis"><em>PLDebug = 1</em> </span> - debugging information enabled.</td> </tr> <tr> <td> <span class="emphasis"><em>PLDebug = 2</em> </span> - debugging information enabled, test coverage data will be written to file specified in TestCoverage Virtuoso ini file parameter.</td> </tr> </table> </li> <li class="listitem" id="ini_parameters_testcoverage"> <p> <strong>TestCoverage = cov.xml.聽</strong> </p> </li> <li class="listitem" id="ini_parameters_callstackonexception"> <p> <strong>CallstackOnException = 0.聽</strong> Controls whether Virtuoso will report call stack on errors. </p> <p>This parameters takes the following values:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>0 (default) - Call stack reporting disabled.</td> </tr> <tr> <td>1 - Call stack reporting enabled.</td> </tr> </table> </li> <li class="listitem" id="ini_parameters_compileproceduresonstartup"> <p> <strong>CompileProceduresOnStartup = 1.聽</strong> This controls whether Virtuoso will recompile all stored procedures listed in SYS_PROCEDURES and internal PL procedures defined during server startup. By default Virtuoso will recompile all procedures, with this setting set to 0 Virtuoso will defer compilation until procedures' first call. The benefits of this are that Virtuoso may start up up to 2-3 times faster, also the initial memory consumption will be significantly reduced as it does not need to analyze all the long varchar data allocating memory for execution. This setting is a boolean, either 1 or 0. This setting does not apply to attached VDB procedures or modules. </p> </li> <li class="listitem" id="ini_parameters_fdsperfile"> <p> <strong>FDsPerFile = 1.聽</strong> Controls the number of file descriptors per file to be obtained from the OS. The default and minimum value is 1. This parameter only effects databases that use striping. Having multiple FDs per file means that as many concurrent I/O operations may simultaneously be pending per file. This allows more flexibility for the OS to schedule the operations, potentially improving file I/O throughput </p> </li> <li class="listitem" id="ini_parameters_recursivefreetextusage"> <p> <strong>RecursiveFreeTextUsage = 1/0 default 1.聽</strong> This option controls the behavior of free-text triggers in super-tables. If this option is set to 1 then Virtuoso will scan the hierarchy of tables until a free-text index is used to use when compiling SQL statements involving contains, xcontains or xpath_contains. </p> </li> <li class="listitem" id="ini_parameters_recursivetriggercalls"> <p> <strong>RecursiveTriggerCalls = 1/0 default 1.聽</strong> This option controls the behavior of super-table triggers. When this option is set to 1 then triggers in the super-table will be called before its own (sub-table) triggers. This behavior is recursive and will continue up the branch of recursion, hence the triggers in the top most table in the chain will be called first. </p> </li> <li class="listitem" id="ini_parameters_maxsortedtoprows"> <p> <strong>MaxSortedTopRows = 10000.聽</strong> The TOP select statement clause caches in memory the rows pertinent to the result. The number of rows allowed to be cached within memory is limited by this parameter. </p> <p> <span class="emphasis"><em>Simple example using OFFSET and LIMIT:</em></span> </p> <p>Virtuoso uses a zero index in the OFFSET. Thus in the example below, will be taken position at record 9000 in the result set, and will get the next 1000 rows starting from 9001 record. Note that the MaxSortedTopRows in parameters Virtuoso ini section needs to be increased (default is 10000).</p> <pre class="programlisting"> select ?name ORDER BY ?name OFFSET 9000 LIMIT 1000 </pre> </li> <li class="listitem" id="ini_parameters_disableunixsocket"> <p> <strong>DisableUnixSocket = 0/1 default 0.聽</strong> This parameter is only applicable to Unix servers. Virtuoso clients on the <code class="computeroutput">localhost</code> of the server can benefit from using Unix Domain sockets to improve connection performance. By default (DisableUnixSocket = 0) Virtuoso will open a Unix Domain listen socket in addition to the TCP listen socket. The name of the UD socket is <code class="computeroutput">/tmp/virt-<tcp-listen-port></code> . When a client attempts to connect to the Virtuoso server using the specific address <code class="computeroutput">localhost</code> it will first try connecting to the UD socket, failing that it will silently revert to the TCP socket. See the <a href="/virtuoso/accintudsockets/">Unix Domain Socket Connections</a> section for more details. </p> </li> <li class="listitem" id="ini_parameters_transactionafterimagelimit"> <p> <strong>TransactionAfterImageLimit = N bytes default 50000000.聽</strong> When the roll-forward log entry of a transaction exceeds this size, the transaction is too large and is marked as uncommittable. This work as upper limit otherwise infinite (transactions). The default is 50Mb . Then also note that transaction roll-back data takes about 2x of roll-forward data. Hence when the transaction roll-forward data which is 50Mb the total transient consumption is closer to 150 Mb. </p> </li> <li class="listitem" id="ini_parameters_tempsesdir"> <p> <strong>TempSesDir.聽</strong> Directory for storing temporary data for large object handled in replication and HTTP server. Defaults to server home directory. </p> </li> <li class="listitem" id="ini_parameters_dbevenable"> <p> <strong>DbevEnable = 0/1 default 1.聽</strong> Enable or disable Database Event Hooks . </p> </li> <li class="listitem" id="ini_parameters_runas"> <p> <strong>RunAs.聽</strong> Specifies the OS user name to which the server will switch after opening the listen ports. Has an effect only on the operating systems that support it. </p> </li> <li class="listitem" id="ini_parameters_maxmempoolsize"> <p> <strong>MaxMemPoolSize = 200000000.聽</strong> This parameter specifies the limit of the memory to be used for compiling a SQL statement. If the query compilation requires more memory an error will be signalled. If this is a zero then no limit will be applied. The default is 200000000. i.e. when no parameter is specified, also if negative number or less than 5000000 is given then it would be set to 5000000 bytes. </p> </li> <li class="listitem" id="ini_parameters_defaultisolation"> <p> <strong>DefaultIsolation.聽</strong> This specifies the default transaction isolation. This isolation is used unless overridden by a client setting it using the SQL_TXN_ISOLATION or equivalent connection option or a stored procedure locally setting it with the SET statement. The values are as by the SQL_TXN_ constants in ODBC, that is, 1 for read uncommitted, 2 for read committed, 4 for repeatable read and 8 for serializable. If nothing is specified, the default is repeatable read. </p> </li> <li class="listitem" id="ini_parameters_useaio"> <p> <strong>UseAIO.聽</strong> This specifies whether to use asynchronous file I/O on supporting Unix systems. A value of 0 means not using it. A value of 1 means using lio_listio for any background write or read ahead if available. A value of 2 means to use the regular blocking read and write but to merge adjacent operations into a single system call when possible. </p> </li> <li class="listitem" id="ini_tempdbsize"> <p> <strong>TempDBSize.聽</strong> Controls the acceptable size of the temp database file. If on startup it's size (in MB) is greater than TempDBSize the file gets deleted and reset. This feature can be turned off by setting TempDBSize to 0. Note that the temp db file serves as an optimization storage only and doesn't have any client data that are not in either the main database files or the corresponding transaction log files. </p> </li> <li class="listitem" id="ini_litemode"> <p> <strong>LiteMode = 0/1 (default 0).聽</strong> Runs server in lite mode. When Lite mode is on: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>the web services are not initialized i.e. no web server, dav, soap, pop3 etc. </p> </li> <li class="listitem"> <p>the replication is stopped </p> </li> <li class="listitem"> <p>the pl debugging is disabled </p> </li> <li class="listitem"> <p>plugins are disabled </p> </li> <li class="listitem"> <p>rendezvous is disabled </p> </li> <li class="listitem"> <p>the relevant tables to the above are not created </p> </li> <li class="listitem"> <p>the index tree maps is set to 8 if no other setting is given </p> </li> <li class="listitem"> <p>memory reserve is not allocated </p> </li> <li class="listitem"> <p>affects DisableTcpSocket. So DisableTcpSocket setting is treated as 1 when LiteMode=1, regardless of value in INI file</p> </li> </ul> </div> <p> </p> </li> <li class="listitem" id="ini_rdffreetextrulessize"> <p> <strong>RdfFreeTextRulesSize = 10 or more.聽</strong> The size of hash to control rdf free text index </p> </li> <li class="listitem" id="ini_indextreemaps"> <p> <strong>IndexTreeMaps = 2 -1024 (power of 2).聽</strong> Size of index tree maps, larger is better for speed but consume memory, in lite is 2 in 'normal' mode is 256 by default. </p> </li> <li class="listitem" id="ini_disabletcpsocket"> <p> <strong>DisableTcpSocket = 1/0.聽</strong> Default = 0. If set to 1, disables database listener on TCP port; unix socket must be used for data access connections (ODBC, JDBC, ADO.NET, OLE DB). When LiteMode=1, DisableTcpSocket setting in INI file is ignored and treated as if set to 1. </p> </li> <li class="listitem" id="ini_extentreadthreshold"> <p> <strong>ExtentReadThreshold.聽</strong> Controls speculative read of disk pages. If pages are read in close succession from an extent of 256 consecutive pages, the system may decide to speculatively read the entire extent. </p> <p>ExtentReadThreshold parameter gives how many consecutive reads are needed to trigger this.</p> <p>When is set to 0, this means that anytime a page is read, the whole extent is read along with it</p> <p>When is set to 1, this means that if the first read is at time <span class="emphasis"><em>t</em></span> and the next one at time <span class="emphasis"><em>t1</em></span> and <span class="emphasis"><em>t1-t</em></span> < ini_ExtentReadWindow msec, then 2nd read triggers the speculative read.</p> <p>Default is 2.</p> <p>Takes effect after the buffer pool is full.</p> </li> <li class="listitem" id="ini_extentreadwindow"> <p> <strong>ExtentReadWindow.聽</strong> Controls speculative read of disk pages. If pages are read in close succession from an extent of 256 consecutive pages, the system may decide to speculatively read the entire extent. </p> <p>ExtentReadWindow parameter gives the time within which the reads must fall.</p> <p>Default is 1000.</p> <p>Takes effect after the buffer pool is full.</p> </li> <li class="listitem" id="ini_extentreadstartupthreshold"> <p> <strong>ExtentReadStartupThreshold.聽</strong> Controls speculative read of disk pages. If pages are read in close succession from an extent of 256 consecutive pages, the system may decide to speculatively read the entire extent. </p> <p>ExtentReadStartupThreshold parameter value applies while the server is freshly started and the buffer pool is not yet full. It can be set to preread more aggressively.</p> <p>Default is 0.</p> </li> <li class="listitem" id="ini_extentreadstartupwindow"> <p> <strong>ExtentReadStartupWindow.聽</strong> Controls speculative read of disk pages. If pages are read in close succession from an extent of 256 consecutive pages, the system may decide to speculatively read the entire extent. </p> <p>ExtentReadStartupWindow parameter value applies while the server is freshly started and the buffer pool is not yet full. It can be set to preread more aggressively.</p> <p>Default is 40000.</p> </li> <li class="listitem" id="ini_columnstore"> <p> <strong>ColumnStore.聽</strong> If 1, all create table and create index statements will create column-store structures by default. </p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_asyncqueuemaxthreads"> <p> <strong>AsyncQueueMaxThreads.聽</strong> Sets the number of threads in a pool that is used for getting extra threads for running queries and for aq_request. Each running statement has at least one thread that is not allocated from this pool plus zero or more threads from this pool. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>Setting the pool size to the number of cores plus a few is a reasonable default. On platforms with core multithreading, one can count a core thread as a core for purposes of this parameter.</p> <p>If one expects to run many slow <code class="function">aq_requests()</code> (see <code class="function">async_queue()</code> , <code class="function">aq_request()</code> , etc.), then the number of threads should be increased by the number of slow threads one expects. </p> <p>Slow threads are typically I/O bound threads used for web crawling or similar long-latency, low-CPU activity.</p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_threadsperquery"> <p> <strong>ThreadsPerQuery.聽</strong> This is maximum number of threads that can be claimed from the thread pool by a single query. A value of one means that no query parallelization will take place, and all queries will run single threaded. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>The number of cores on the machine is a reasonable default if running large queries.</p> <p>Note that since every query is served by at least one thread, a single query taking all the extra threads will not prevent other queries from progressing.</p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_vectorsize"> <p> <strong>VectorSize.聽</strong> This the number of simultaneous sets of query variable bindings processed at one time. The default is 10,000, which is good for most cases. </p> <pre class="programlisting"> SELECT COUNT (*) FROM t1 a, t1 b WHERE a.row_no + 1 = b.row_no OPTION (LOOP, ORDER) </pre><p> </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>If we are evaluating the query:</p> <p>with vector size of 10,000, then 10,000 rows of t1 a will be fetched first; 1 will be added to the 10,000 row_no values; and then the corresponding row of t1 b will be fetched for the 10,000 row_no of t1 a. This process will repeat until enough batches of t1 a have been fetched to come to its end.</p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_adjustvectorsize"> <p> <strong>AdjustVectorSize.聽</strong> Using a larger vector size when evaluating large queries with indexed random-access can yield up to a 3x speed-up relative to using the default vector size. However, always using a large vector size will prohibitively increase the overhead of running small queries. For this reason, there is the option to adaptively select the vector size. Set AdjustVectorSize = 1 to enable this feature. The SQL execution engine will increase the vector size when it sees an index lookup that does not get good locality, (e.g., after sorting the keys to look for, too few consecutive lookups fall on the same page). Having more keys to look up increases the chance that consecutive keys should be found on the same page, thus eliminating much of the index lookup cost. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_maxquerymem"> <p> <strong>MaxQueryMem.聽</strong> This controls the maximum amount of memory that can be used across the server process for large vectors, i.e. if the memory in use is near this limit, a query will not switch to large vector size even if it finds it useful. The event counter tc_no_mem_for_longer_batch counts how many times this situation is detected. A size letter of G or M follows the value. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_hashjoinspace"> <p> <strong>HashJoinSpace.聽</strong> This controls the maximum amount of memory that can be used across the server process for hash join hash tables. This is followed by a size letter M or G. A single hash join hash table will only claim a percentage of the remaining hash join space, by default 50. This is controlled by the chash_per_query_pct setting, see section on vectored execution tuning. If there is not enough memory, a partitioned hash join will be used, making as many passes over the data as needed so that the hash table will fit within the set limits. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_maxvectorsize"> <p> <strong>MaxVectorSize.聽</strong> When AdjustVectorSize is on, this setting gives the maximum vector size. The default is 1,000,000 and the largest allowed value is about 3,500,000. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#confvectexec">Configuring Vectored Execution</a> </p> </td> </tr> </table> </div> <p> </p> <p>Note: Only effective with Virtuoso 7.0 and later.</p> </li> <li class="listitem" id="ini_timezonelessdatetimes"> <p> <strong>TimezonelessDatetimes.聽</strong> Enables Timezoneless Support. Different applications may require different behavior when input data contain timezoneless values. In some cases it is better to "cast" all of them to timezoned than to upgrade existing code. Virtuoso offers 5 different modes of support -- 0, 1, 2, 3 and 4. This should be set before creating the database and the set value is stored in the database. After database is created, an attempt to change the mode by patching <a href="/virtuoso/ch-server/#virtini">virtuoso.ini</a> will have no effect and virtuoso.log will contain a warning about mismatch between virtuoso.ini and the database file. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>TimezonelessDatetimes=0 -- Never use timezoneless, as it was in old databases. Always set local timezone on parsing strings if no timezone specified. An attempt to set timezoneless by calling function <a href="/virtuoso/fn_forget_timezone/"><code class="function">forget_timezone()</code></a> will signal error. Timezoneless values still may come from outside as dezerializations of timezoneless DATETIME values, serialized by other database instances, but not in any other way: </p> </li> <li class="listitem"> <p>TimezonelessDatetimes=1 -- When parsing strings, set timezoneless if ISO format tells so: </p> </li> <li class="listitem"> <p>TimezonelessDatetimes=2 -- Set timezoneless always, exception is when the parsed string contains explicit timezone or when RFC requires the use of GMT or when timezone is set by function <a href="/virtuoso/fn_adjust_timezone/"><code class="function">adjust_timezone()</code></a> . This is default for new databases if <code class="code">TimezonelessDatetimes</code> parameter is missing in virtuoso.ini </p> </li> <li class="listitem"> <p>TimezonelessDatetimes=3 -- Never use timezoneless. Always set local timezone on parsing strings if not timezone specified. An attempt to set timezoneless by calling function <a href="/virtuoso/fn_forget_timezone/"><code class="function">forget_timezone()</code></a> will signal error. Timezoneless values still may come from outside as deserializations of timezoneless DATETIME values, serialized by other database instances, but not in any other way. The difference with <code class="code">TimezonelessDatetimes=0</code> is that timezones are always printed on cast datetimes to strings etc. so timezoneless-aware clients will get unambiguous data. </p> </li> <li class="listitem"> <p>TimezonelessDatetimes=4 -- On parsing string, set timezone to GMT if no timezone specified. However, timezoneless can be set by calling function <a href="/virtuoso/fn_forget_timezone/"><code class="function">forget_timezone()</code></a> . This mode can be convenient for global web services when real "local" timezones of specific users are not known. </p> </li> </ul> </div> <p> </p> <p>The possible variants are:</p> <p>For new applications, consider the use of <code class="code">TimezonelessDatetimes=2</code> as primary variant, <code class="code">TimezonelessDatetimes=1</code> as the second best.</p> </li> </ul> </div> <p>Note: The default for startup behavior is to always read full extents and the default for the normal behavior is to trigger preread on the third read inside one second.</p> </div> <div> <span class="permalink"><a id="ini_httpserver" onclick="javascript:permalink(this)" href="#ini_httpserver">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[HTTPServer]</h6> </div> </div> </div> <p>Settings in this section control the web server component of the Virtuoso Server.</p> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_httpserver_serverport"> <p> <strong>ServerPort.聽</strong> This specifies the initial HTTP listen port for the HTTP server. Can be specified also as ipaddress:port. Once Virtuoso is started it is possible to create multiple listeners using virtual directories. </p> </li> <li class="listitem" id="ini_httpserver_httpthreadsize"> <p> <strong>HTTPThreadSize = 120000.聽</strong> The stack size of the HTTP thread used for reading/processing HTTP client requests and accepting connections. The default is 120,000 bytes. This parameter cannot have value less than the default; if a smaller value is specified the default will be used. </p> </li> <li class="listitem" id="ini_httpserver_serverthreads"> <p> <strong>ServerThreads.聽</strong> This specifies the number of concurrently serviced HTTP requests. Its alias is <span class="emphasis"><em>MaxClientConnections</em></span> . If there are more concurrent requests, accepting the connections will be deferred until there is a thread ready to serve each. If an attempt to exceed the number of licensed connections is found. the latter will be used. When the number of threads is low some of the tutorials may perform poorly and appear not to work; this is due to the demonstration licensing. When testing Virtuoso with the demonstration license it can be quite easy to hit the limits unless remote connections and HTTP connections are conserved. You may wish to either wait for previous transactions to finish or restart the server to be sure. </p> </li> <li class="listitem" id="ini_httpserver_httpthreadsize_01"> <p> <strong>HTTPThreadSize = 120000.聽</strong> The stack size of HTTP thread used for reading/processing HTTP client requests and accepting connections. The default setting, if not supplied, is 120,000 bytes. The default value is the minimum; lesser values will be rounded up. </p> </li> <li class="listitem" id="ini_httpserver_serverroot"> <p> <strong>ServerRoot = ../vsp.聽</strong> This is the file system path of the root directory of files served by the Virtuoso web server. The index.html in that directory will be served for the / URI. If relative, the path is interpreted relative to the server's working directory. </p> </li> <li class="listitem" id="ini_httpserver_serveridstring"> <p> <strong>ServerIdString = Virtuoso.聽</strong> String passed as Server: header to HTTP client. This string is not required, in its absence the above default will be assumed. This string can be set to anything required. </p> </li> <li class="listitem" id="ini_httpserver_clientidstring"> <p> <strong>ClientIdString = Mozilla/4.0 (compatible; Virtuoso).聽</strong> String passed as User-Agent: header to server by HTTP client. This string is not required, in its absence the above default will be assumed. This string can be set to anything required. </p> </li> <li class="listitem" id="ini_httpserver_charset"> <p> <strong>Charset = [CHARSET-NAME].聽</strong> Allows you to set the default server character set. If no default is specified then ISO-8859-1 will be used automatically by the server. </p> </li> <li class="listitem" id="ini_httpserver_enabledgzipcontent"> <p> <strong>EnabledGzipContent = 0.聽</strong> This sets the default behavior of HTTP transmission. If set to 1 The Virtuoso HTTP server will send GZipped content to user agents. Otherwise content will be sent as is. The function <a href="/virtuoso/fn_http_enable_gz/"><code class="function">http_enable_gz()</code></a> lets you change the server mode on the fly. </p> </li> <li class="listitem" id="ini_httpserver_maxkeepalives"> <p> <strong>MaxKeepAlives = 10.聽</strong> Connections by HTTP 1.1 clients can remain open after the initial response has been sent. This parameters sets a cap on how many socket descriptors will at most be taken by keep alive connections. Such connections will be dropped by the server ahead of timeout if this number would be exceeded. Thus the maximum number of open sockets for the Virtuoso HTTP server is this number plus the number of threads. A keep alive connection is by definition not associated to any pending processing on any thread. </p> </li> <li class="listitem" id="ini_httpserver_keepalivetimeout"> <p> <strong>KeepAliveTimeout = 10.聽</strong> This is a timeout in seconds before Virtuoso closes an idle HTTP 1.1 connection. </p> </li> <li class="listitem" id="ini_httpserver_httpproxyenabled"> <p> <strong>HTTPProxyEnabled = 0.聽</strong> Setting this to 1 activates Virtuoso proxy service capabilities. The default value of 0 deactivates the proxy service. </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>Ports on which proxying is enabled should not be presented to the outside world under any situation.</p> </td> </tr> </table> </div> </li> <li class="listitem" id="ini_httpserver_httpproxyserver"> <p> <strong>HTTPProxyServer = proxylocal:3128.聽</strong> HTTP proxy server name and port </p> </li> <li class="listitem" id="ini_httpserver_httpproxyexceptions"> <p> <strong>HTTPProxyExceptions = localhost:8890, 127.0.0.1:8890.聽</strong> HTTP proxy exceptions name and port. </p> </li> <li class="listitem" id="ini_httpserver_httplogfile"> <p> <strong>HTTPLogFile = log.out.聽</strong> If specified, Virtuoso will produce an HTTP server log file with the date appended to the name given in the parameter and the files extension as ".out". The log file is rotated daily. </p> <p>It will contain the following information:</p> <p> <code class="computeroutput">logDDMMYYYY.out</code> :-</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>Client IP address</td> </tr> <tr> <td>Date and time of request/response</td> </tr> <tr> <td>Timestamp (milliseconds)</td> </tr> <tr> <td>Request/response line</td> </tr> </table> <p>An example of which is:</p> <pre class="programlisting"> 127.0.0.1 - - [12/Sep/2006:12:31:17 +0300] "GET /ods/ HTTP/1.1" 200 19453 "" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko.." 127.0.0.1 - - [12/Sep/2006:12:31:18 +0300] "GET /ods/default.css HTTP/1.1" 200 41389 "http://example.com/ods/" "Mozilla/5.0 (Windows; U; ..." 127.0.0.1 - - [12/Sep/2006:12:31:19 +0300] "GET /ods/common.js HTTP/1.1" 200 7481 "http://example.com/ods/" "Mozilla/5.0 (Windows; U; ..." </pre> </li> <li class="listitem" id="ini_httpserver_httplogformat"> <p> <strong>HTTPLogFormat = format string like apache mod_log.聽</strong> "HTTPLogFormat" INI file param works in conjunction with the "HTTPLogFile" INI file param. In http log we support format string like <a class="ulink" href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html" target="_top">Apache Module mod_log_config</a> . For example: </p> <pre class="programlisting"> ... [HTTPServer] ... HTTPLogFormat = %h %u %t "%r" %s %b "%{Referer}i" "%{User-agent}i" "%{NetId}e" </pre><p> </p> <p>In this example we have %{User-Agent}i which means to log the HTTP header for user-agent. In similar way can log other input headers, "e" modifier is for environment variable NetId in this case. </p> <p>Note that not all escapes from <a class="ulink" href="http://httpd.apache.org/docs/2.2/mod/mod_log_config.html" target="_top">Apache Module mod_log_config</a> are supported. </p> </li> <li class="listitem" id="ini_httpserver_maccachedproxyconnections"> <p> <strong>MaxCachedProxyConnections = 10.聽</strong> When Virtuoso is acting as a proxy or HTTP client, as is the case with the http_get or the SOAP client functions, it caches connections to HTTP 1.1 servers. This is the maximum population of said cache. </p> </li> <li class="listitem" id="ini_httpserver_proxyconnectioncachetimeout"> <p> <strong>ProxyConnectionCacheTimeout = 15.聽</strong> This is a timeout in seconds for dropping idle connections to other HTTP servers. These result from http_get, SOAP client functions and proxying. </p> </li> <li class="listitem" id="ini_httpserver_davroot"> <p> <strong>DavRoot = DAV.聽</strong> This specifies the root path of DAV resources. If DAV specific HTTP methods are used on Virtuoso, these should only reference resources with paths starting with this. This is the top level DAV collection. Other paths can be declared as managed in DAV using the virtual directory mechanism, but this applies to the default virtual directory. </p> </li> <li class="listitem" id="ini_httpserver_davquotaenabled"> <p> <strong>DAVQuotaEnabled = 1/0.聽</strong> The Virtuoso administrator can enforce a quota on all DAV accounts, apart from the "dav" administration user, that restricts that amount of space a DAV user can consume in their DAV home directory. When this parameter is set to one (1) quotas are enabled, when this parameter is set to zero (0), they are disabled. The default quota value is five Megabytes (5MB) but can be uniquely defined for each user. Every user has a quota except "dav", which is unlimited. Dav quotas are disabled if this parameter is not specified for backwards compatibility. </p> </li> <li class="listitem" id="ini_httpserver_davchunkedquota"> <p> <strong>DAVChunkedQuota = 1000000.聽</strong> Virtuoso send resources to from WebDAV to the requesting client in chunked encoding to save memory if the request is in HTTP/1.1 and the files size is greater then the <code class="computeroutput">DAVChunkedQuota</code> number of bytes. The default chunked-quota value is approximately one-megabyte. </p> </li> <li class="listitem" id="ini_httpserver_sslport"> <p> <strong>SSLPort=4433.聽</strong> this is the port on which SSL HTTPS connections will be accepted. Can be specified also as ipaddress:port. If unspecified then the service will be disabled. </p> </li> <li class="listitem" id="ini_httpserver_sslcertificate"> <p> <strong>SSLCertificate=./virtuoso_cert.pem.聽</strong> the option must point to the file with the server certificate in PEM format. </p> <p> If the option begins with 'db:' e.g. 'db:id_server', then certificate and key will be loaded from DBA key space. </p> </li> <li class="listitem" id="ini_httpserver_sslprivatekey"> <p> <strong>SSLPrivateKey=./virtuoso_key.pem.聽</strong> points to the file containing the RSA private key in PEM format. </p> <p>the certificate/key pair must be valid (eq. certificate is generated on base of key)</p> <p> If the option begins with 'db:' e.g. 'db:id_server', then certificate and key will be loaded from DBA key space. Note: in the case of database stored key, both SSLCertificate and SSLPrivateKey settings MUST be same. </p> </li> <li class="listitem" id="ini_httpserver_x509clientverify"> <p> <strong>X509ClientVerify=0.聽</strong> Whether the server will require X509 certificates from the browsers. </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <span class="emphasis"><em>X509ClientVerify = 0</em> </span> - no certificate verification required</td> </tr> <tr> <td> <span class="emphasis"><em>X509ClientVerify = 1</em> </span> - ask for trusted certificates</td> </tr> <tr> <td> <span class="emphasis"><em>X509ClientVerify = 2</em> </span> - optionally ask for trusted certificates, if trusted certificate is presented it will be verified</td> </tr> <tr> <td> <span class="emphasis"><em>X509ClientVerify = 3</em> </span> - optionally accept any certificate including self-signed certificates</td> </tr> </table> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/secureodbcx509/#secureodbcx509foafsll">WebID Protocol ODBC Login</a> </p> </td> </tr> </table> </div> </li> <li class="listitem" id="ini_httpserver_x509clientverifydepth"> <p> <strong>X509ClientVerifyDepth=1.聽</strong> Specifies how deep the client certificate verification process will traverse the Issuer chain before giving up. The default value of 0 means that only verification of the client certificate itself being in the server's CA list is performed. Setting this option to -1 will ignore the depth checks </p> </li> <li class="listitem" id="ini_httpserver_x509clientverifycafile"> <p> <strong>X509ClientVerifyCAFile=./calist.pem.聽</strong> a PEM file of all the X509 certificates of the Certification Authorities (CA) which the server will use for verifying the client's client certificate. A list of these will be sent to the client as a part of the SSL handshake so the client will know which certificate to send. </p> <p> Note this option is in effect when X509ClientVerify is 1 or 2. If X509ClientVerify is 3 and X509ClientVerifyCAFile is given, server will send certificated during handshake, thus some clients may restrict user to send any certificate. </p> </li> <li class="listitem" id="ini_httpserver_pop3port"> <p> <strong>POP3Port=1234.聽</strong> Defines the TCP port number on which the Virtuoso POP3 server will listen. The POP3 server will be disabled if this value is 0 or undefined. </p> </li> <li class="listitem" id="ini_httpserver_newsserverport"> <p> <strong>NewsServerPort=1235.聽</strong> Defines the TCP port number on which the Virtuoso NNTP server will listen. The NNTP server will be disabled if this value is 0 or undefined. </p> </li> <li class="listitem" id="ini_httpserver_ftpserverport"> <p> <strong>FTPServerPort.聽</strong> The Virtuoso FTP server can be enabled by supplying this parameter with a value. This value will then be the listening port of the FTP server. The usual port for FTP is port 21. </p> </li> <li class="listitem" id="ini_httpserver_ftpserverminfreeport"> <p> <strong>FTPServerMinFreePort = 20000.聽</strong> The Virtuoso FTP client and server use FTPServerMinFreePort and FTPServerMaxFreePort parameters as lower and upper bounds for active and passive connections. This parameters sets the lower bound. </p> </li> <li class="listitem" id="ini_httpserver_ftpservermaxfreeport"> <p> <strong>FTPServerMaxFreePort = 30000.聽</strong> The Virtuoso FTP client and server use FTPServerMinFreePort and FTPServerMacFreePort parameters as lower and upper bounds for active and passive connections. This parameters sets the upper bound. </p> </li> <li class="listitem" id="ini_httpserver_ftpserverlogfile"> <p> <strong>FTPServerLogFile = ftpserver.聽</strong> If specified Virtuoso will produce an FTP server log file with the date appended to the name given in the parameter and the files extension as ".log". The log file is rotated daily. </p> <p>It will contain the following information:</p> <p> <code class="computeroutput">ftpserverDDMMYYYY.log</code> :-</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>Client Host Name</td> </tr> <tr> <td>Authorized User</td> </tr> <tr> <td>Time</td> </tr> <tr> <td>User Command</td> </tr> <tr> <td>Server Response Code</td> </tr> <tr> <td>Bytes Transferred</td> </tr> </table> <p>An example of which is:</p> <pre class="programlisting"> hostname anonymous [22/Oct/2003:15:21:43 +0300] "PASS user@domain.com" 230 0 hostname anonymous [22/Oct/2003:15:23:11 +0300] "LIST" 226 162 hostname dav [22/Oct/2003:15:25:00 +0300] "PASS <hidden>" 230 0 </pre> </li> <li class="listitem" id="ini_httpserver_ftpserveranonymouslogin"> <p> <strong>FTPServerAnonymousLogin = 0.聽</strong> Allows the FTP server to be accessible via the "anonymous" user login. The anonymous user is not a real user, it has no SQL or DAV login ability. The anonymous user can only access collections or resources that are set to public. </p> </li> <li class="listitem" id="ini_httpserver_defaultmailserver"> <p> <strong>DefaultMailServer=localhost:25.聽</strong> Default SMTP server name and port, this is used when the first parameter of the smtp_send function is omitted or NULL. </p> </li> <li class="listitem" id="ini_httpserver_tempaspxdir"> <p> <strong>TempASPXDir.聽</strong> Allows you to choose what file system directory to be used for temporary storage of ASPX files hosted in DAV. </p> </li> <li class="listitem" id="ini_httpserver_persistenthostingmodules"> <p> <strong>PersistentHostingModules = [1/]0.聽</strong> When set to "1" prevents Virtuoso from removing the plugin interpreters from the HTTP threads after each request. The default setting is "0". </p> </li> <li class="listitem" id="ini_httpserver_httpsessionsize"> <p> <strong>HttpSessionSize = size in bytes, default 10000000.聽</strong> The size threshold for large objects received by HTTP server. When this limit is exceeded by incoming or outgoing data, this will be stored in a temp file, see 'TempSesDir' parameter in 'Parameters' section. </p> </li> <li class="listitem" id="ini_httpserver_maintenancepage"> <p> <strong>MaintenancePage = file_name.聽</strong> The name of a HTML page or other static content to be returned to the user agents when server is running in atomic mode. Note that this page should be self-contained, i.e. no image or CSS not JavaScript references can be used. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_flags" onclick="javascript:permalink(this)" href="#ini_flags">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Flags]</h6> </div> </div> </div> <p> </p> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_uriqa_enablejoinsonly"> <p> <strong>enable_joins_only = 0.聽</strong> Setting enable_joins_only will cause the optimizer to only consider next plan candidates that are connected by a join to the existing partial plan. In other words, no cartesian products will be considered. This may save some space and time. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_uriqa" onclick="javascript:permalink(this)" href="#ini_uriqa">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[URIQA]</h6> </div> </div> </div> <p> The URIQA section sets parameters of both URIQA HTTP extension and URIQA web service. Section <a href="/virtuoso/uriqa/">URIQA Semantic Web Enabler</a> contains detailed description of this functionality, including more details about <a href="/virtuoso/uriqainifile/">URIQA configuration parameters</a> . This section should stay commented out as long as URIQA is not in use. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_uriqa_defaulthost"> <p> <strong>DefaultHost = canonical name of the server, used by default for metadata retrieval, no default value.聽</strong> The server name, including domain and port if needed, such as "www.example.com" or "www.example.com:8088". </p> </li> <li class="listitem" id="ini_uriqa_localhostnames"> <p> <strong>LocalHostNames = comma-delimited list of names of the server, that can be used for retrieval of metadata, no default value.聽</strong> List of various allowed spellings of the server name, such as "www.example.com, mail.example.com, mail, localhost, localhost.localdomain". </p> </li> <li class="listitem" id="ini_uriqa_localhostmasks"> <p> <strong>LocalHostMasks = comma-delimited list of name masks of the server, no default value.聽</strong> List of various allowed spellings of the server name in form of pattern strings for SQL "like" operator, not in form of exact strings. </p> </li> <li class="listitem" id="ini_uriqa_fingerprint"> <p> <strong>Fingerprint = unique fingerprint string of the server or group of identical servers, no default value.聽</strong> Do not use this without an explicit need, to let server configure itself. Please refer to <a href="/virtuoso/uriqainifile/">detailed description</a> before use. </p> </li> <li class="listitem" id="ini_uriqa_dynamiclocal"> <p> <strong>DynamicLocal = 1/0 default 0, allow dynamic hostname translation in the IRIs.聽</strong> If DynamicLocal is on and the host part of the IRI matches the Host header of the HTTP request in context or the DefaultHost if outside of HTTP context, then this is replaced with local: before looking up the IRI ID. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_sparql" onclick="javascript:permalink(this)" href="#ini_sparql">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[SPARQL]</h6> </div> </div> </div> <p> The SPARQL section sets parameters and limits for SPARQL query protocol web service service. This section should stay commented out as long as SPARQL is not in use. Section RDF Data Access and Data Management contains detailed description of this functionality. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_sparql_externalquerysource"> <p> <strong>ExternalQuerySource = 1 or 0 .聽</strong> This controls processing of the "query-uri" parameter of the SPARQL query protocol webservice, means enable 1 or prohibited 0. </p> </li> <li class="listitem" id="ini_minexpiration"> <p> <strong>MinExpiration = 86400 .聽</strong> Sponger caching parameter in seconds. It will cause sponger to use this value as minimal expiration of the pages, which would help in cases where source document's server do not report expiration or it reports no caching at all. </p> </li> <li class="listitem" id="ini_maxcacheexpiration"> <p> <strong>MaxCacheExpiration = 1 .聽</strong> Cache Expiration time in seconds that overrides Sponger's default cache invalidation. </p> </li> <li class="listitem" id="ini_maxdatasourcesize"> <p> <strong>MaxDataSourceSize = 20971520 .聽</strong> Controls the max size that can be sponged. Default is 20 MB. </p> </li> <li class="listitem" id="ini_sparql_externalxsltsource"> <p> <strong>ExternalXsltSource = 1 or 0 .聽</strong> This controls processing of the "xslt-uri" parameter of the SPARQL query protocol webservice, means enable 1 or prohibited 0. </p> </li> <li class="listitem" id="ini_sparql_resultsetmaxrows"> <p> <strong>ResultSetMaxRows = number .聽</strong> This setting is used to limit the number of the rows in the result. The effective limit will be the lowest of this setting, SPARQL query 'LIMIT' clause value (if present), and SPARQL Endpoint request URI <a href="/virtuoso/rdfsparqlprotocolendpoint/#rdfrequestparamsofunctions">&maxrows </a> parameter value (if present). </p> </li> <li class="listitem" id="ini_sparql_defaultgraph"> <p> <strong>DefaultGraph = IRI .聽</strong> IRI of the default graph to be used if no "default-graph-uri" parameter is specified. </p> </li> <li class="listitem" id="ini_sparql_maxquerycostestimationtime"> <p> <strong>MaxQueryCostEstimationTime = seconds .聽</strong> This setting is used to limit the estimate time cost of the query to certain number of seconds, the default is no limit. </p> </li> <li class="listitem" id="ini_sparql_maxqueryexecutiontime"> <p> <strong>MaxQueryExecutionTime = seconds .聽</strong> This setting is used to set the transaction execution timeout to certain limit in number of seconds, the default is no limit. </p> </li> <li class="listitem" id="ini_sparql_immutablegraphs"> <p> <strong>ImmutableGraphs = URI .聽</strong> IRI of graphs over which the sponger not to be able able to write. </p> </li> <li class="listitem" id="ini_sparql_pingservice"> <p> <strong>PingService = URI .聽</strong> IRI of notification service to which the sponger results will be send. </p> </li> <li class="listitem" id="ini_sparql_defaultquery"> <p> <strong>DefaultQuery = SPARQL Query .聽</strong> Default SPARQL Query. </p> </li> <li class="listitem" id="ini_sparql_deferinferencerulesinit"> <p> <strong>DeferInferenceRulesInit = 1 .聽</strong> Defer Loading of inference rules at start up. </p> </li> <li class="listitem" id="ini_sparql_shortenlonguris"> <p> <strong>ShortenLongURIs = 1 .聽</strong> Shorten extremely long URIs in datasets when loading with the RDF Bulk Loader. Default is 0. </p> <p> <span class="emphasis"><em>Note </em> </span> : This parameter is only in the Virtuoso 06.03.3131+ commercial builds, at the time of writing it is not included in the open source 6.1.4 archives but will be in the next 6.1.5 release. A patch to enable this feature is however available from the <a class="ulink" href="http://sourceforge.net/tracker/?func=detail&aid=3496331&group_id=161622&atid=820576" target="_top">Virtuso patches page on source forge</a> , which can be applied to a 6.1.4 archive from source forge and the Virtuoso server binary rebuilt. </p> </li> <li class="listitem" id="ini_sparql_maxmeminuse"> <p> <strong>MaxMemInUse = 0 .聽</strong> Maximum amount of memory that is allowed for temporary storing parts of a SPARQL query result. Default is zero for no limit. ResultSetMaxRows is maximum length of a SPARQL query result. Default is zero for no limit. These two options may be useful for protecting public web service endpoints against DOS attacks, but at the same time it may cause returning incomplete results without reporting errors. When used, it is strongly advised to set the value orders of magnitude larger than the expected size of longest reply. As a rule of thumb, timeout should happen before this limit has reached. Values less than 1000000 bytes are impractical in all cases. </p> </li> </ul> </div> <p>The SPARQL INI can be get as RDF via http://cname/sparql?ini service.</p> </div> <div> <span class="permalink"><a id="ini_i18n" onclick="javascript:permalink(this)" href="#ini_i18n">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[I18N]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem" id="ini_i18n_xanynormalization"> <p> <strong>XAnyNormalization = 1/2/3/0.聽</strong> 0: default value. It means not to normalize anything, so, for example, "Jos茅" and "Jose" are two distinct words. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/virtuosotipsandtrickscontrolunicode3/">How Can I Control the normalization of UNICODE3 accented chars in free-text index?</a> </p> </td> </tr> </table> </div> <p> </p> <p>1: Any pair of base char and combining char (NSM, non-spacing modifier) is replaced with a single combined char, so if character "茅" is written as a sequence of "base" character "e" and a unicode char U+0301 ("combining acute accent"), then the pair will be replaced with a single U+00E9 ("latin small letter e acute"). </p> <p>2: Any combined char is converted to its (smallest known) base, so, "茅" will lose its accent and become plain old ASCII "e". </p> <p>3: This is equal to 1+2, and when set, both conversions are performed. As a result, any pair of base char and combining char loses its second char, and any chars with accents will lose accents.</p> <p>If the parameter is required at all, the needed value is probably 3, so the fragment of virtuoso.ini should be:</p> <pre class="programlisting"> [I18N] XAnyNormalization=3 </pre> </li> <li class="listitem" id="ini_i18n_widefilenames"> <p> <strong>WideFileNames = 1/0.聽</strong> Default is 0. When 1 then file access and directory listing functions may use wide strings as file names. If a file name contains non-ASCII characters then directory listing result set will contain a wide string instead of narrow string with question marks. Note, however, that most of existing applications do not support wide strings for that purposes, so the feature should be used with extreme care. </p> </li> <li class="listitem" id="ini_i18n_volumeencoding"> <p> <strong>VolumeEncoding.聽</strong> Encoding identifier. If set, file names are translated from wide strings and default server encoding to the specified encoding before using them in file manipulation BIFs. This is useful when server's filesystem is in some national encoding or in UTF-8. The translation is bi-directional: directory listing items are translated from volume encoding to the default server encoding or wide. </p> </li> <li class="listitem" id="ini_i18n_volumeemergencyencoding"> <p> <strong>VolumeEmergencyEncoding.聽</strong> Encoding identifier. If set, this encoding is used when the use of VolumeEncoding causes encoding errors. The most popular case is when an UNIX filesystem tree with UTF-8 contains some mounts of legacy storages with KOI or CP encoding. Less popular is UTF-8 volume encoding and UTF-8QR as emergency encoding to recover poorly encoded filenames. </p> </li> <li class="listitem" id="ini_i18n_volumeemergencyencodingdirs"> <p> <strong>VolumeEmergencyEncodingDirs.聽</strong> List of directories in same syntax as DirsAllowed, default is empty. If set, all file names in the listed directories are supposed to be in VolumeEmergencyEncoding and VolumeEncoding is even not tried. The most popular case is when an UNIX filesystem tree with UTF-8 contains some mounts of legacy storages with KOI or CP encoding. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_replication" onclick="javascript:permalink(this)" href="#ini_replication">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Replication]</h6> </div> </div> </div> <p> The replication section sets the transactional replication parameters for the server. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_replication_serverenable"> <p> <strong>ServerEnable=0/1.聽</strong> A boolean parameter controlling whether a Virtuoso can or cannot act as a transactional replication publisher. </p> </li> <li class="listitem" id="ini_replication_servername"> <p> <strong>ServerName = log1.聽</strong> This identifies the server instance. The entries in SYS_REPL_ACCOUNTS where SERVER equals this name are considered locally published accounts. This is the value returned by repl_this_server () SQL function. </p> </li> <li class="listitem" id="ini_replication_queuemax"> <p> <strong>QueueMax = 50000.聽</strong> This controls how much synchronized transactional subscribers may fall behind before being disconnected. This controls how much memory the server will use to buffer undelivered replication casts. If the queue exceeds this byte amount subscribers are disconnected and must request re-synchronization. The byte count refers to the total length of the replay records being buffered. The actual memory usage is somewhat greater. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_mono" onclick="javascript:permalink(this)" href="#ini_mono">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Mono]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_mono_mono_root"> <p> <strong>MONO_ROOT.聽</strong> A path to the directory where the Mono system assemblies are located. Usually it is a compile time setting, but the MONO_ROOT overrides it. This ini setting overrides the Mono environment variable of the same name. </p> </li> <li class="listitem" id="ini_mono_mono_path"> <p> <strong>MONO_PATH.聽</strong> A colon separated list of directories where the assemblies are located to be found by Assembly.Load (equivalent to MS.NET Global assembly cache). This ini setting overrides the Mono environment variable of the same name. </p> </li> <li class="listitem" id="ini_mono_mono_cfg_dir"> <p> <strong>MONO_CFG_DIR.聽</strong> A path where the 'machine.config' file is to be found while running the ASPX code in Mono. This ini setting overrides an environment variable of the same name. This is also usually a Mono compile time default. </p> </li> <li class="listitem" id="ini_mono_virtclr.dll"> <p> <strong>virtclr.dll.聽</strong> A fully qualified path and filename of the virtclr.dll virtuoso helper assembly. </p> </li> <li class="listitem" id="ini_mono_mono_trace"> <p> <strong>MONO_TRACE = Off.聽</strong> Mono debug tracing can be enabled by setting this parameter to On. When tracing is On, Mono debug output with be sent to the Virtuoso debug console. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_client" onclick="javascript:permalink(this)" href="#ini_client">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Client]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_client_sql_query_timeout"> <p> <strong>SQL_QUERY_TIMEOUT=0.聽</strong> This sets the initial value of the SQL_QUERY_TIMEOUT statement option in connected clients. The ODBC standard value is 0, meaning indefinite, which is impractical in many applications. This allows overriding the default. The timeout is expressed in seconds. If the client application sets this option in a statement, this default is overridden for the statement in question. </p> </li> <li class="listitem" id="ini_client_sql_txn_timeout"> <p> <strong>SQL_TXN_TIMEOUT=0.聽</strong> This is an ODBC extension option allowing setting a maximum duration for a transaction. 0 means that there is no maximum. </p> </li> <li class="listitem" id="ini_client_sql_prefetch_rows"> <p> <strong>SQL_PREFETCH_ROWS=100.聽</strong> For a forward only cursor, this option sets the number of rows prefetched at the execute and on subsequent fetch requests. A high value will speed up long selects but will be a disadvantage if only the first few rows are fetched from a cursor that has a large result set. </p> <p>This should not be confused with the SQL_ROWSET_SIZE setting for scrollable cursors.</p> </li> <li class="listitem" id="ini_client_sql_prefetch_bytes"> <p> <strong>SQL_PREFETCH_BYTES=16000.聽</strong> This option specifies the maximum number of bytes the server will send as prefetched rows on a forward only cursor. If long rows are being prefetched this will cut off the prefetch after this many bytes even if the number of rows is less than SQL_ROWSET_SIZE. </p> </li> <li class="listitem" id="ini_client_sql_no_char_c_escape"> <p> <strong>SQL_NO_CHAR_C_ESCAPE=0.聽</strong> This options is 0 by default and can be either 1 or 0. This option controls Virtuoso's interpretation of the backslash in PL text which is normal interpreted as escaping rather than literal. </p> </li> <li class="listitem" id="ini_client_sql_utf8_execs"> <p> <strong>SQL_UTF8_EXECS = 0.聽</strong> Setting SQL_UTF8_EXECS = 1 enables UTF-8 identifier storage and retrieval, whereas setting SQL_UTF8_EXECS = 0 disables it. The default setting is 0: disabled for backwards compatible. See the <a href="/virtuoso/wideidentifiers/">Wide Character Identifiers</a> section for more information </p> </li> <li class="listitem" id="ini_client_sql_binary_timestamp"> <p> <strong>SQL_BINARY_TIMESTAMP = 1.聽</strong> When SQL_BINARY_TIMESTAMP is set to 1 Virtuoso will describe all TIMESTAMP columns as SQL_BINARY. If it is set to 0 then Virtuoso will report the TIMESTAMP columns as SQL_TIMESTAMP </p> </li> <li class="listitem" id="ini_client_sql_no_system_tables"> <p> <strong>SQL_NO_SYSTEM_TABLES = 0.聽</strong> This setting can be used to prevent SQLTables from returning system tables. The default value of this setting is 0, which is allow system tables to be returned in the normal way. Setting this to 1 will prevent system tables from being returned from SQLTables. The client can also issue a "set SQL_NO_SYSTEM_TABLE = 1/0" statement to set this in-connection. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_autorepair" onclick="javascript:permalink(this)" href="#ini_autorepair">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[AutoRepair]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_autorepair_badparentlinks"> <p> <strong>BadParentLinks=0.聽</strong> As a result of an internal error in the database the physical integrity of references may be lost. Enabling this option causes the database to automatically repair such faults without having to go through a crash dump plus restore. A value of 0 should be normally used. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_vdb" onclick="javascript:permalink(this)" href="#ini_vdb">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[VDB]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_vdb_arrayoptimization"> <p> <strong>ArrayOptimization=0/1.聽</strong> Boolean parameter which allows the Virtuoso VDB to use Array parameters if the remote data source supports these. </p> </li> <li class="listitem" id="ini_vdb_usemts"> <p> <strong>UseMTS = 0.聽</strong> This parameter turns on/off MTS support in Virtuoso. It is applicable to windows multithreaded version of the Virtuoso server only. </p> </li> <li class="listitem" id="ini_vdb_numarrayparameters"> <p> <strong>NumArrayParameters.聽</strong> Specifies a size of the parameter batch used by the VDB (default = 10) </p> </li> <li class="listitem" id="ini_vdb_vdbdisconnecttimeout"> <p> <strong>VDBDisconnectTimeout.聽</strong> The time (in seconds) after which a VDB connection is considered timed-out and closed. Default : 1000 </p> </li> <li class="listitem" id="ini_vdb_vdboraclecatalogfix"> <p> <strong>VDBOracleCatalogFix=0/1.聽</strong> This setting can be enabled to improve compatibility with the MS Oracle Driver which has problems with mixed case table names in catalog calls. </p> <p>Boolean parameter : allows a special mode for the ORACLE ODBC drivers which do not return correct catalog data for mixed case tables. When this is on and the return from the catalog functions is empty, then a Catalog function is issued to take the same catalog data and the result is filtered on the client side.</p> </li> <li class="listitem" id="ini_vdb_attachinautocommit"> <p> <strong>AttachInAutoCommit.聽</strong> An boolean parameter controlling whether the VDB Catalog functions called while attaching a table will be called in AutoCommit mode (required by some Sybase drivers). </p> </li> <li class="listitem" id="ini_vdb_numarrayparameters_01"> <p> <strong>NumArrayParameters=10.聽</strong> </p> </li> <li class="listitem" id="ini_vdb_reconnectonfailure"> <p> <strong>ReconnectOnFailure=0 [1|0].聽</strong> The default setting of 0 instructs the VDB layer to return underlying DB errors to the client rather than automatically reconnecting without reporting the error, which would be setting 1. </p> </li> <li class="listitem" id="ini_vdb_keepconnectiononfixedthread"> <p> <strong>KeepConnectionOnFixedThread=1 [0|1|2|4|8].聽</strong> The default option is 1, this forces the VDB to map a single thread to each ODBC session in the VDB rather than multiple threads. Some ODBC drivers expect that calls concerning a particular connection all take place on one thread. For example, the Oracle 8.xx ODBC driver can produce flaky crashes if this option is not set. </p> <p>0 - If a second request comes while a thread is processing the epilogue or previous request for same connection the second request is scheduled for the same thread. This is called burst mode. Once this mode is active all requests on this connection will be processed in the same thread. until there is a break at delay more than 'PrpcBurstTimeoutMsecs' elapses between ending the last and receiving the next in same connection. This break in activity return the thread to the thread pool. The burst mode optimization saves thread switching time and may improve performance by up to 30% in situations involving short requests immediately following each other. </p> <p>"ForcedFixedThread" mode (4). This is the same as VDBFixedThread mode, except that the thread enters this state immediately on connection (as opposed to doing that on the first VDB activity). Otherwise the scheduling stays the same as in VDB FixedThread. </p> <p>"Forced Burst" mode (8). When a connection is initially made it's added to the select thread for monitoring. When an RPC comes in it causes the select thread to take the connection out of the select thread and assign that connection to designated worker thread. That thread from now on will read the data coming in from that connection directly (not depending on the select thread to detect the incoming data and wake the worker thread up). That mode saves the thread switch done handling each RPC (from the select thread to the worker thread). When the connection terminates the thread is unbound from it and returned to it's default idle state. If an lengthy RPC is being processed the server will switch the thread from burst mode to default mode while running the RPC, so the asynchronous cancellation requests can be processed.</p> <p> To disable ever going to burst mode, this option can be set to 2 </p> </li> <li class="listitem" id="ini_vdb_prpcbursttimeoutmsecs"> <p> <strong>PrpcBurstTimeoutMsecs=100 (milliseconds).聽</strong> RPC burst mode timeout in milliseconds. (see above) </p> </li> <li class="listitem" id="ini_vdb_serializeconnect"> <p> <strong>SerializeConnect=0 [1|0].聽</strong> When enabled causes Virtuoso to wrap SQLAllocConnect/SQLConnect calls sequence in a mutex, thus preventing abnormal program exits when there are a large number of connection requests to the VDB. Certain ODBC drivers have been noted to produce flaky errors when a large number of threads is concurrently inside one of the ODBC connect calls.. </p> </li> <li class="listitem" id="ini_vdb_skipdmlprimarykey"> <p> <strong>SkipDMLPrimaryKey=0 [1|0].聽</strong> This setting controls SQL compilation (not execution) for conditions where rows in a local table are used to determine rows of a remote table to be deleted (e.g. delete from rmt1 where rmc1 = 12 and rmc2 in (select lc1 from lt1)) where the remote table was linked without a Primary Key primary key specified. Normally the primary key is used, even when not in the original select select, to identify the rows to be deleted. When the primary key is false or not available and SkipDMLPrimaryKey = 1 then the original where clause will be used instead. </p> </li> <li class="listitem" id="ini_vdb_remotepknotunique"> <p> <strong>RemotePKNotUnique=0 [1|0].聽</strong> This option controls the SQL compiler ability to do some optimizations when it knows it will receive 1 row from a remote table (using the applicable WHERE clause). In some cases the remote is not providing any info about a primary key (or is providing wrong data for the primary keys and unique indices of a table) through ODBC API and the Virtuoso SQL optimizer may get fooled into thinking that a given SQL query over a remote table will return no more than 1 row. To avoid that turn on the above parameter to stop the compiler from doing that optimizations. </p> </li> <li class="listitem" id="ini_vdb_useglobalpool"> <p> <strong>UseGlobalPool=0 [1|0].聽</strong> This option controls the aggregation point of the VDB connection pools. When it is off (=0, the default) the VDB connections that are no longer needed after transaction end are collected server-side in a per-user connection cache. This (together with the <code class="code">KeepConnectionOnFixedThread</code> INI option) ensures conformance even with older ODBC drivers that require that connections must be used only within the OS thread that initiated them. This however may result in somewhat low reuse rate for the pooled connections. That's why when this option is 1 (On) the connections are stored in a server-side per-DSN connection cache. Keep in mind that this may not work with all the ODBC drivers, but it may provide lower ratio between virtuoso client connections and VDB-to-remote DBMS connections, thus requiring smaller number of active connections on the remotes and faster execution of VDB operations. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_ucms" onclick="javascript:permalink(this)" href="#ini_ucms">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Ucms]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_ucms_ucmpath"> <p> <strong>UcmPath.聽</strong> String parameter which specifies the path where UCM files are located. If this parameter is not specified, UCM files cannot be loaded. </p> </li> <li class="listitem" id="ini_ucms_ucm"> <p> <strong>Ucm1, Ucm2,... Ucm99.聽</strong> Every UcmN parameter specifies one UCM file to load. The value of UcmN is a pair of comma delimited strings. The first string is a name of the UCM file to load, (relative to the path specified in UcmPath), the second string is a name of the encoding as it was used by the server. E.g. Ucm1 = java-Cp933-1.3-P.ucm,Cp933 will load the encoding from the file java-Cp933-1.3-P.ucm and associate it with the identifier 'Cp933'. You can register one encoding with more than one name, if they are delimited by '|' (with no white spaces in the string). e.g. Ucm2 = java-Cp949-1.3-P.ucm,Cp949|Korean will load the encoding from the file java-Cp949-1.3-P.ucm and associate it with two identifiers, 'Cp949' and 'Korean'. See <a href="/virtuoso/xmlencoding/#ucmencodings">UCM Encodings</a> for more details. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ini_zeroconfig" onclick="javascript:permalink(this)" href="#ini_zeroconfig">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Zero Config]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_zeroconfig_servername"> <p> <strong>ServerName.聽</strong> Name used to advertise the Virtuoso ODBC service details in ZeroConfig. This is the name that will be shown to clients amongst other ZeroConfig datasources. </p> </li> <li class="listitem" id="ini_zeroconfig_serverdsn"> <p> <strong>ServerDSN.聽</strong> An ODBC style connect string to preset the values of the parameters when the ODBC service offered by this server is selected by the Virtuoso ZeroConfig enabled clients. </p> </li> <li class="listitem" id="ini_zeroconfig_sslservername"> <p> <strong>SSLServerName.聽</strong> Name used to advertise the Virtuoso ODBC SSL encrypted service details in ZeroConfig. </p> </li> <li class="listitem" id="ini_zeroconfig_sslserverdsn"> <p> <strong>SSLServerDSN.聽</strong> An ODBC style connect string to preset the values of the parameters when the ODBC SSL encrypted service offered by this server is selected by the Virtuoso ZeroConfig enabled clients. </p> </li> </ul> </div> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p>The <a href="/virtuoso/ch-server/#rendezvous">Zero Config</a> section.</p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="ini_plugins" onclick="javascript:permalink(this)" href="#ini_plugins">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Plugins]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_plugins_loadpath"> <p> <strong>LoadPath = /home/virtuoso/hosting.聽</strong> The directory containing shared objects/libraries for use as Virtuoso VSEI plugins. </p> </li> <li class="listitem" id="ini_plugins_load"> <p> <strong>Load<number> = <module type>, <module name>.聽</strong> <code class="computeroutput"><number></code> is the module load number, required and starting with 1. <code class="computeroutput"><module type></code> specifies the type of module that is to be loaded, and hence how Virtuoso is to use it. So far "Hosting" and "attach" types exist. <code class="computeroutput"><module name></code> is the file name of the modules shared library or object. </p> <p>Example:</p> <p> <code class="computeroutput">Load6 = attach, libphp5.so</code> )</p> <p> <code class="computeroutput">Load7 = Hosting, hosting_php.so</code> )</p> <p>"Attach" is used for now for the php library. It can be used to load other libraries in future too. The reason is to load PHP5 functionality into virtuoso namespace, so when actually is loaded the hosting plugin, it can bind to the already available symbols for php5. </p> </li> </ul> </div> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> VSEI Plugins </p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="ini_striping" onclick="javascript:permalink(this)" href="#ini_striping">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">[Striping]</h6> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="dash"> <li class="listitem" id="ini_striping_segment"> <p> <strong>Segment<number> = <size>, <stripe file name> [, <stripe file name> .. ].聽</strong> <number> must be ordered from 1 upwards; The <size> is the size of the segment which is equally divided across all stripes comprising the segment. </p> </li> </ul> </div> <p>This section is only effective when <code class="computeroutput">Striping = 1</code> is set in the <code class="computeroutput">[Database]</code> section. When striping is enabled the Virtuoso database spans multiple segments where each segment can have multiple stripes.</p> <p>Striping can be used to distribute the database across multiple locations of a file system for performance. Segmentation can be used for expansion or dealing with file size limitations. To allow for database growth when a file system is near capacity or near the OS file size limitation, new segments can be added on the same or other file systems.</p> <p>Striping only has a potential performance benefit when striped across multiple devices. Striping on the same file system is needless and unlikely to alter performance, however, multiple segments do provide convenience and flexibility as described above. Striping across partitions on the same device is likely to reduce performance by causing high unnecessary seek times on the physical disk.</p> <p>Database segments are pre-allocated as defined. This can reduce the potential for file fragmentation which could also provide some performance benefit.</p> <p>Virtuoso striping alone does not allow for any fault tolerance. This is best handled at the I/O layer or by the operating system. File system RAID with fault-tolerant striping defined should be used to host the Virtuoso files if striping based protection is desired.</p> <p>The segments are numbered, their segment <number> must be specified in order starting with segment1.</p> <p>The <size> is the total size of the segment which is that will be divided equally across all stripes comprising the segment. Its specification can be in gigabytes (g), megabytes (m), kilobytes (k) or in database blocks (b) the default.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>The segment size must be a multiple of the database page size which is currently 8k. Also, the segment size must be divisible by the number of stripe files contained in the segment.</p> </td> </tr> </table> </div> <p>Segments can be added to a database, however once defined they should never be altered. Databases that were created without striping cannot automatically be restarted with striping. You can convert a non-striping database to striping by dumping the contents of the database to a transaction file and replaying it with striping enabled. An on-line backup made with backup_online () can be restored on a database with a different striping configuration as long as the total number of pages is no less than the number of pages of the backed up database. </p> <p>Striping can be useful for the temporary objects database if large hash join temporary spaces or such are expected. This is enabled by the Striping setting in the Temp Database section of the ini file. The stripes will be declared in the TempStriping section. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#dbrebuild">Rebuilding A Database</a> in the Backup section.</p> </td> </tr> </table> </div> </div> </div> <div> <span class="permalink"><a id="sampleinifile" onclick="javascript:permalink(this)" href="#sampleinifile">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Sample Configuration File ("virtuoso.ini")</h5> </div> </div> </div> <p>Following is the text of the sample virtuoso.ini file that comes with the distribution. </p> <pre class="programlisting"> ; ; virtuoso.ini ; ; Configuration file for the OpenLink Virtuoso VDBMS Server ; ; ; Database setup ; [Database] DatabaseFile = virtuoso.db TransactionFile = virtuoso.trx ErrorLogFile = virtuoso.log ErrorLogLevel = 7 FileExtend = 200 Striping = 0 ; LogSegments = 1 ; crashdump_start_dp = 0 ; crashdump_end_dp = 0 ; Log1 = log1.trx ; ; Server parameters ; [Parameters] ServerPort = 1111 ServerThreads = 10 CheckpointInterval = 60 CheckpointSync = 2 NumberOfBuffers = 2000 MaxDirtyBuffers = 1200 MaxCheckpointRemap = 2000 PrefixResultNames = 0 CaseMode = 1 ;MinAutoCheckpointSize = 4000000 AutoCheckpointLogSize = 40000000 CheckpointAuditTrail = 1 [HTTPServer] ServerPort = 1122 ServerRoot = ../vsp ServerThreads = 2 MaxKeepAlives = 10 KeepAliveTimeout = 10 MaxCachedProxyConnections = 10 ProxyConnectionCacheTimeout = 15 DavRoot = DAV [Replication] ServerName = log1 Server = 1 QueueMax = 50000 [Client] SQL_QUERY_TIMEOUT = 0 SQL_TXN_TIMEOUT = 0 SQL_PREFETCH_ROWS = 100 SQL_PREFETCH_BYTES = 16000 [AutoRepair] BadParentLinks = 0 BadDTP = 0 ;[Ucms] ;UcmPath = /ucm ;Ucm1 = java-Cp933-1.3-P.ucm,Cp933 ;Ucm2 = java-Cp949-1.3-P.ucm,Cp949|Korean ;Ucm3 = java-ISO2022KR-1.3-P.ucm,ISO2022KR|ISO2022-KR ; ; Striping setup ; ; These parameters have only effect when Striping is set to 1 in the ; [Database] section, in which case the DatabaseFile parameter is ignored. ; ; With striping, the database spans multiple segments ; where each segment can have multiple stripes. ; ; Format of the lines below: ; Segment<number> = <size>, <stripe file name> [, <stripe file name> .. ] ; ; <number> must be ordered from 1 up. ; ; The <size> is the total size of the segment which is equally divided ; across all stripes comprising the segment. Its specification can be in ; gigabytes (g), megabytes (m), kilobytes (k) or in database blocks ; (b, the default) ; ; Note that the segment size must be a multiple of the database page size ; which is currently 8k. Also, the segment size must be divisible by the ; number of stripe files constituting the segment. ; ; The example below creates a 200 meg database striped on two segments ; with two stripes of 50 meg and one of 100 meg. ; ; You can always add more segments to the configuration, but once ; added, do not change the setup. ; [Striping] Segment1 = 100M, db-seg1-1.db, db-seg1-2.db Segment2 = 100M, db-seg2-1.db </pre> </div> <div> <span class="permalink"><a id="confvectexec" onclick="javascript:permalink(this)" href="#confvectexec">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Configuring Vectored Execution</h5> </div> </div> </div> <p>Note: Only effective with Virtuoso 7.0 and later.</p> <p>A Virtuoso 7 executable executes all SQL statements in vectored mode, except for positioned updates and deletes in stored procedures. Procedures are executed without vectoring unless they are declared vectored using the vectored keyword. A scalar (non-vectored) procedure can have a vectored block introduced with the for vectored construct. These are discussed in the SQL reference section on vectoring.</p> <p>Vectored execution is controlled by the following virtuoso.ini settings:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <span class="emphasis"><em>VectorSize = 10000</em></span> </p> <p>: This is the default number of concurrent variable bindings that are generated for a column in a batch of bindings. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>MaxQueryMem = 1G</em></span> </p> <p>: This controls the maximum amount of memory that can be used across the server process for large vectors, i.e. if the memory in use is near this limit, a query will not switch to large vector size even if it finds it useful. The event counter tc_no_mem_for_longer_batch counts how many times this situation is detected. A size letter of G or M follows the value. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>AdjustVectorSize = 1</em></span> </p> <p>: If non-zero, this enables automatic increasing of vector size whenever the system notices a random access pattern that is not benefiting from vectoring due to too few consecutive hits falling on the same page. The vector size can be increased up to MaxVectorSize if the situation warrants. This is the case if there is enough unprocessed state in the query. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>MaxVectorSize = 1000000</em></span> </p> <p>: This is the maximum vector size. This can reach up to 4000000 but values in excess of 1000000 have not been found useful in practice. If the server is running out of memory with multiuser workloads involving long queries, dropping the MaxVectorSize to a lower value is a means of curtailing per query memory consumption. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ThreadsPerQuery = 8</em></span> </p> <p>: This controls the maximum number of parallelizable work units a query will have outstanding at any one time. A value of 8 means that a scan or vector of lookups is maximally divided into 8 units, of which 7 will be allocated to a pool of worker threads and one will be processed by the thread coordinating the query. Each query will always have one thread running, which is the thread allocated for serving the client-server or HTTP request initiating the query. Extra work units are serviced by threads from a parallel execution thread pool. If there are unstarted parallel work units that have not started at the time the coordinated thread finishes its own work unit, it will execute any of its own pending work units locally. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>AsyncQueueMaxThreads = 16</em></span> </p> <p>: This is the maximum number of worker threads that can be started for running parallelized work units generated by queries or functions requested with the aq_request () PL function. Thus the number of threads running on a server at any time is the number of client server or HTTP threads that have a running request plus this number. These threads consider the totality of all async execution requests across all async queues and each thread picks a unit of work from the oldest queue that has unstarted work units. The age of the queue is the timestamp of its creation. A queue is created whenever a query operator decides to split its work. This scheduling favors thus old queries over new ones. However any request is guaranteed one thread, that on which its initiating request is served. </p> <p>For a query processing workload, one should set AsyncQueueMaxThreads to the number of cores minus the expected number of concurrent queries, this would in principle use all cores or core threads. In practice for machines with large numbers of cores, e.g. 32 cores, a lower value may serve in practice better, subject to experimentation. For a web crawling situation where threads are waiting for the network for most of the time, a larger number will do better.</p> </li> </ul> </div> <p>These parameters can be set at run time by a dba group user using the <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set()</code></a> function.</p> </div> <div> <span class="permalink"><a id="indexdefragm" onclick="javascript:permalink(this)" href="#indexdefragm">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Index Defragmentation</h5> </div> </div> </div> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note</th> </tr> <tr> <td align="left" valign="top"> <p>This section only applies to storage of indexes, not data. Index storage optimization happens automatically in Virtuoso v6 and greater. Users wishing to compact the whole database file itself should perform a <a href="/virtuoso/ch-server/#vdbrecovery">backup-dump/restore-crash-dump</a> cycle instead. </p> </td> </tr> </table> </div> <p> When data is inserted into tables, database pages are split and typically pages end up not being fully utilized. If data is inserted in ascending order of key value, which is often the case, space utilization is more efficient. Still, gaps can be left by updates, deletions and page splitting. Virtuoso has an autocompact feature which will take groups of adjacent dirty pages and see if it can fit the same content on a smaller number of pages. It will rewrite the pages to save space before writing these to disk. This operates automatically. Statistics on autocompaction are shown beside the Read ahead status line of the result set of status ('');. The number of pages affected by autocompaction and the number of resulting pages are shown. The numbers are cumulative since the start of the instance. </p> <p> Autocompact is non-locking and if pages are busy, they will not be touched. Only relatively old dirty pages, about to be written to disk are considered for compaction, not interfering with the hottest part of the working set. </p> <p> The automatic compaction is not however effective if pages are updated singly, never making stretches of consecutive dirty pages. Therefore a manual compaction function called DB.DBA.VACUUM () is also offered. </p> <p> The vacuum stored procedure gets an optional table and index name and will read the index from beginning to end. If neither argument is given, all indices of all tables will be compacted. If only the table is given, all indices of this table will be compacted. </p> <p> If consecutive leaves can be fit on fewer pages than they now occupy, this will rewrite them and free the pages left over. This does however require transient space since the pages are not really replaced until the next checkpoint, hence a vacuum operation can run out of disk. Using the checkpoint statement to force a checkpoint will free the space. </p> <p> The effects and need for explicitly vacuuming a database can be assessed with the DB.DBA.SYS_INDEX_SPACE_STATS view. </p> <p>Running: </p> <pre class="programlisting"> select * from DB..SYS_INDEX_SPACE_STATS order by ISS_PAGES desc; </pre> <p> produces a result set with the most space consuming index on top. ISS_PAGES is the total count of pages. ISS_ROW_BYTES is the byte count of the rows. If dividing the total count of bytes by the count of pages is much below 8172, (8K - 20), chances are that vacuuming the index may save space. Note that blobs are not affected by vacuuming. If the blobs are small enough to fit on the row as normal strings they are already there. Otherwise they occupy the needed number of pages and cannot be made more compact. </p> <p> Note that querying the SYS_INDEX_SPACE_STATS view will always read through all the allocated pages of the database and may take a while. The operation is not locking. Only the state as of the last checkpoint will be shown, hence it is a good idea to run the checkpoint statement before querying this view. </p> <p> Examples: </p> <pre class="programlisting"> DB..VACUUM (); -- Compact all tables and indices of the Virtuoso instance </pre> <pre class="programlisting"> Db..VACUUM ('WS.%'); -- compact all tables of the WS. qualifier </pre> <pre class="programlisting"> DB..VACUUM ('DB.DBA.RDF_QUAD', 'RDF_QUAD_PGOS'); -- compact the rdf_quad_pgos index of the rdf_quad table. </pre> <p> Virtuoso has an autocompact feature. </p> </div> </div> <div> <span class="permalink"><a id="commandline" onclick="javascript:permalink(this)" href="#commandline">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Server Startup Command Line Options</h4> </div> </div> </div> <div> <span class="permalink"><a id="ch-server_01" onclick="javascript:permalink(this)" href="#ch-server_01">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Virtuoso Server</h5> </div> </div> </div> <p> This section presents the command line switches of the Virtuoso server executable. Depending on the model and virtual database middleware the server will have different names, all starting with virtuoso-. All these however have the same options for UNIX systems and slightly different for Windows platform. </p> <p> on Windows platform are available following server command line options: </p> <pre class="programlisting"> Usage: virtuoso-odbc-t.exe [-clnCbDARf---dSIMKmrd] [+configfile arg] [+licensefile arg] [+no-checkpoint] [+checkpoint-only] [+backup-dump] [+crash-dump] [+crash-dump-data-ini arg] [+restore-crash-dump] [+foreground] [+pwdold arg] [+pwddba arg] [+pwddav arg] [+debug] [+service arg] [+instance arg] [+mode arg] [+dumpkeys arg] [+manual] [+restore-backup arg] [+debug] +configfile specify an alternate configuration file to use, or a directory where virtuoso.ini can be found +licensefile specify an alternate license file to use, or a directory where virtuoso.ini can be found +no-checkpoint do not checkpoint on startup +checkpoint-only exit as soon as checkpoint on startup is complete +backup-dump dump database into the transaction log, then exit +crash-dump dump inconsistent database into the transaction log, then exit +crash-dump-data-ini specify the DB ini to use for reading the data to dump +restore-crash-dump restore from a crash-dump +foreground run in the foreground +pwdold Old DBA password +pwddba New DBA password +pwddav New DAV password +debug allocate a debugging console +service specify a service action to perform +instance specify a service instance to start/stop/create/delete +mode specify mode options for server startup (onbalr) +dumpkeys specify key id(s) to dump on crash dump (default : all) +manual specify when create a service to make it for manual startup +restore-backup restore from online backup +debug Show additional debugging info The argument to the +service option can be one of the following options start start a service instance stop stop a service instance create create a service instance screate create a service instance without deleting the existing one delete delete a service instance list list all service instances </pre> <p> The below are switches for server for UNIX platforms: </p> <pre class="programlisting"> Usage: virtuoso-iodbc-t [-fclnCbDARwMKr---d] [+foreground] [+configfile arg] [+licensefile arg] [+no-checkpoint] [+checkpoint-only] [+backup-dump] [+crash-dump] [+crash-dump-data-ini arg] [+restore-crash-dump] [+wait] [+mode arg] [+dumpkeys arg] [+restore-backup arg] [+pwdold arg] [+pwddba arg] [+pwddav arg] [+debug] +foreground run in the foreground +configfile use alternate configuration file +licensefile use alternate license file +no-checkpoint do not checkpoint on startup +checkpoint-only exit as soon as checkpoint on startup is complete +backup-dump dump database into the transaction log, then exit +crash-dump dump inconsistent database into the transaction log, then exit +log6 If you're starting with a Virtuoso 5 server, and migrating to a Virtuoso 6 or later server, append +log6 after +backup-dump or +crash-dump. Note: The extra +log6 argument is not needed, and may have unexpected effect, so please leave it off if starting with a Virtuoso 6 server and moving to Virtuoso 6 or later. +crash-dump-data-ini specify the DB ini to use for reading the data to dump +restore-crash-dump restore from a crash-dump +wait wait for background initialization to complete +mode specify mode options for server startup (onbalr) +dumpkeys specify key id(s) to dump on crash dump (default : all) +restore-backup restore from online backup +pwdold Old DBA password +pwddba New DBA password +pwddav New DAV password +debug Show additional debugging info </pre> <p> The <span class="emphasis"><em>+crash-dump</em></span> option will make use of the segmented log defined in virtuoso.ini for storing the recovery log. See <a href="/virtuoso/ch-server/#vdbrecovery">Crash Recovery</a> and virtuoso.ini below for more information. The other options will not use the segmented log. </p> <p> The <span class="emphasis"><em>+restore-crash-dump</em></span> option will alter the server startup sequence so that the recovery log produced by +crash-dump will be re-played correctly. </p> <p> The <span class="emphasis"><em>+mode</em></span> option can be a combination of the following letters: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <span class="emphasis"><em>o</em> </span> - only open the database and define the SYS_KEYS, SYS_COLS, SYS_KEY_PARTS, SYS_CHARSETS AND SYS_COLLATIONS system tables.</td> </tr> <tr> <td> <span class="emphasis"><em>n</em> </span> - leaves out the initialization of the system tables.</td> </tr> <tr> <td> <span class="emphasis"><em>b</em> </span> - do not process anything except the transaction log and system tables when restoring a crash dump (+restore-crash-dump).</td> </tr> <tr> <td> <span class="emphasis"><em>a</em> </span> - leaves out the initialization of the replication, users, compilation or stored and system procedures, as well as the caching of the grants.</td> </tr> <tr> <td> <span class="emphasis"><em>l</em> </span> - write only the schema tables in the backup or crash dump.</td> </tr> <tr> <td> <span class="emphasis"><em>r</em> </span> - don't do the complete initialization (useful for performing a crash dump).</td> </tr> </table> <p> On Unix platforms the executable will detach itself from the console and run in the background as a daemon unless the <span class="emphasis"><em>+foreground</em></span> switch is specified. </p> <p> For Windows NT and Windows 2000, the Virtuoso server will normally be installed as a Windows service and can be started from the Control Panel or automatically at system startup. </p> <p> Ordinarily the Windows service will be a system process that runs in the background. If you want the Virtuoso service on Windows to allocate a debugging console the you can use the <span class="emphasis"><em>+debug</em></span> (-d) switch. This switch is only applicable to starting a service. </p> <p> Virtuoso on Windows can be run directly from the command line using the <span class="emphasis"><em>+foreground</em></span> (-f) switch. The server will then start in the foreground of the current "cmd" session. If this switch is not used then the executable on Windows will assume that you are attempting to start a Virtuoso service. </p> <p> Windows services can be created and removed from the system as required. The default installation under Windows will create a service by the name: <span class="emphasis"><em>OpenLink Virtuoso VDBMS Server</em></span> , and optionally another service with the name <span class="emphasis"><em>OpenLink Virtuoso VDBMS Server [demo]</em></span> . The Demo service is a supplied demonstration database that can be installed. </p> <p> The following options are available to the <span class="emphasis"><em>+service</em></span> switch for configuring Virtuoso services: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>The argument to the +service option can be one of the following options <span class="emphasis"><em>start</em></span> start a service instance</td> </tr> <tr> <td> <span class="emphasis"><em>stop</em> </span> stop a service instance</td> </tr> <tr> <td> <span class="emphasis"><em>create</em> </span> create a service instance</td> </tr> <tr> <td> <span class="emphasis"><em>screate</em> </span> create a service instance without deleting the existing one</td> </tr> <tr> <td> <span class="emphasis"><em>delete</em> </span> delete a service instance</td> </tr> <tr> <td> <span class="emphasis"><em>list</em> </span> list all service instances</td> </tr> </table> <p> </p> <p>They are used with the <span class="emphasis"><em>+instance <name></em></span> where <span class="emphasis"><em><name></em></span> is the instance name to configure a particular instance. All instances are listed in the services applet, with their name in square brackets.</p> <p> <span class="emphasis"><em>+service list</em> </span> can be used to obtain the list if services that are registered with Windows.</p> <p>For each service listed you can start, stop, or delete the service.</p> <p> <span class="emphasis"><em>+service create</em> </span> can be used to create a new service. In this case you also need to specify other start up options that would be associated with the new service entry. If you were using an alternative configuration file this must be specified using <span class="emphasis"><em>+configfile</em></span> switch.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>Make sure the Services Control Panel is closed, before attempting to modify services from the command line, otherwise locking may occur.</p> </td> </tr> </table> </div> </div> </div> <div> <span class="permalink"><a id="rendezvous" onclick="javascript:permalink(this)" href="#rendezvous">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">ZeroConfig ("Zero Configuration") Support</h4> </div> </div> </div> <p>The "ZeroConfig" protocol, also known as "Zeroconf" or "Zero Configuration" is a protocol that allows discovery of services on the network that are advertised by their hosts. It also has provisions for automatic discovery of computers and various devices. The main benefit of ZeroConfig is that it does not require DHCP, DNS or directory servers.</p> <p>ZeroConfig is an open protocol that Apple submitted to the IETF for a standard-creation process.</p> <p>The Virtuoso server and ODBC driver use the capabilities of ZeroConfig to facilitate DSN (Data Source Name) setup and usage. This is divided in two parts: Server-side and Client-side.</p> <p>The Virtuoso server (Server-side) is configured via the Virtuoso INI file to advertise its availability on a network with a given name. This allows applications, and in particular the Virtuoso ODBC driver, to receive information about a server, such as its network address, default login, etc, and use it for configuring a data source or directory making a connection.</p> <p>The Virtuoso ODBC driver (Client side) uses ZeroConfig to locate the desired Virtuoso server during the set-up phase of a data source, and determine available connection options such as:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>secure connection options</td> </tr> <tr> <td>default database</td> </tr> <tr> <td>default user </td> </tr> <tr> <td>default password (if public/demo login is required)</td> </tr> <tr> <td>default character set </td> </tr> </table> <p>ZeroConfig provides the client with a service name, which must be bound to the IP address/port of a host of the chosen service during DSN configuration. This is used when existing DSN using a ZeroConfig name is used to connect, it will map name with IP address and port before making a connection.</p> <div> <span class="permalink"><a id="rendezvousserverside" onclick="javascript:permalink(this)" href="#rendezvousserverside">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Setting-up the Server for Service Advertising</h5> </div> </div> </div> <p>The Virtuoso server is configured to advertise itself based on the details specified in the <code class="computeroutput">[Zero Config]</code> section of the Virtuoso INI file. Below is an example of such:</p> <pre class="programlisting"> ... [Zero Config] ServerName = Virtuoso Server ServerDSN = UID=demo;PWD= SSLServerName = Virtuoso Server (via SSL) SSLServerDSN = UID=dba;PWD=;ENCRYPT=1 ... </pre> <p>The ServerName and SSLServerName are human readable strings chosen by the administrator to provide clients with a suitable description of the service being provided.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>If the Virtuoso does not have the SSL listener enabled then the SSL service will not be advertised automatically. The SSL* keys will simply be ignored and do not need to be removed. </p> </td> </tr> </table> </div> <p>The ServerDSN and SSLServerDSN are default connection strings that can be used by clients to make the advertised connection. You only need to to specify default username and password in these strings. The default database can be specified or left to the setting for the username. You cannot specify the server hostname, IP address or port number, these are supplied by Virtuoso automatically.</p> <p>ZeroConfig service advertising is multicast, hence it is advertised on all available network interfaces.</p> </div> <div> <span class="permalink"><a id="rendezvous_01" onclick="javascript:permalink(this)" href="#rendezvous_01">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Using the Windows ODBC Driver with ZeroConfig</h5> </div> </div> </div> <p>Upon DSN set-up the ODBC driver listens for advertising servers, and compiles a roster. This is displayed for the user to choose the desired service to connect to. </p> <p>If ZeroConfig is used to for data source set-up then the set-up dialog will be initialized based on the details in the connection string configured on the server.</p> <p>When a DSN is configured based on a ZeroConfig service, the driver will resolve the service name before making the connection to the server. The driver does not store the network address or port number of the Virtuoso server, only the ZeroConfig server name, so if the server's physical address is changed the client DSNs associated with it do not all have to reconfigured; they will resolve to the new address automatically on next use.</p> </div> </div> <div> <span class="permalink"><a id="dbstat" onclick="javascript:permalink(this)" href="#dbstat">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Server Status Monitoring</h4> </div> </div> </div> <p>The database status report is divided into 6 sections:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>Server</td> </tr> <tr> <td>Database</td> </tr> <tr> <td>Locks</td> </tr> <tr> <td>Clients</td> </tr> <tr> <td>Replication</td> </tr> <tr> <td>Index Usage</td> </tr> </table> <div> <span class="permalink"><a id="ch-server_02" onclick="javascript:permalink(this)" href="#ch-server_02">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Server</h5> </div> </div> </div> <p> This section shows how many connections are open and how many threads the process has and how many are running at the present time. This also displays the number of requests that have been received but are not yet running on any thread. </p> </div> <div> <span class="permalink"><a id="database" onclick="javascript:permalink(this)" href="#database">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Database</h5> </div> </div> </div> <pre class="screen"> File size 203161600, 24800 pages, 259 free. 7000 buffers, 6987 used, 3884 dirty 8 wired down, repl age 8251 . Disk Usage: 14246 reads avg 6 msec, 74% read last 10 s, 14457 writes, 4 read ahead, batch = 5. Gate: 2729 2nd in reads, 0 gate write waits, 3372547 in while read 0 busy scrap. Log = wi.log, 9851835 bytes 14950 pages have been changed since last backup (in checkpoint state) Current backup timestamp: 0x0000-0x00-0x00 Last backup date: unknown Clients: 18 connects, max 17 concurrent, 1024 licensed RPC: 54441 calls, 17 pending, 17 max until now, 0 queued, 53988 burst reads (99%), 0 second Checkpoint Remap 7646 pages, 0 mapped back. 0 s atomic time. DB master 24800 total 259 free 7646 remap 3415 mapped back temp 200 total 196 free </pre> <p> The status consists of the following items: </p> <p> <strong>File size:聽</strong> The database file size in bytes or 0 if the database consists of statically allocated files. The total number of 8K database pages follows, then the number of free pages. The number of buffers shown the total count of 8K file cache buffers, followed by the number of used buffers and the number of buffers that are dirty at the time. The wired down count is normally zero but can be transiently other if pages are wired down for processing by threads in the server. </p> <p> <strong>Disk Usage:聽</strong> Shows the cumulative total number of reads and writes and the average length of time spent inside the read system call for the database files. </p> <p> The percentage is the percentage of the real time spent inside read between this status report and the previous status report. This may exceed 100% if several reads are taking place concurrently on different stripes in a multi-file database. </p> <p> <strong>The Gate:聽</strong> Lists concurrent events. The <span class="emphasis"><em>2nd in read</em></span> is the count of concurrent requests for the same page, the <span class="emphasis"><em>gate write waits</em></span> is the count of times a modify operation had to wait for exclusive access to a page being read by another thread, the <span class="emphasis"><em>in while read</em></span> is the count of file cache hits that have taken place while a read system call was in progress on another thread. </p> <p> <strong>Databases.聽</strong> Thus section shows the count of pages, free pages, checkpoint remap and mapped back for the main database and the space for temporary data such as sort results and hash indices. The page count is the total size, the free count is the count of free pages, the checkpoint remap is the count of pages that occupy two pages in checkpoint space instead of one, the mapped back count is the number of pages that will return to their original place in checkpoint space at the next checkpoint. Understanding these is not necessary. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See:</th> </tr> <tr> <td align="left" valign="top"> <p>The Disk Configuration section for a discussion of checkpoint remapping.</p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="locks" onclick="javascript:permalink(this)" href="#locks">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Locks</h5> </div> </div> </div> <p> The lock section shows various locking statistics accumulated since the server was started. The deadlock count is divided into deadlocks caused by a situation where several transactions read a page and one wants to get write access and all other deadlock situations. The first is called 2r1w deadlock in the report. </p> <p> The lock section also shows the total number of threads running, i.e. engaged in performing some operation for a SQL or web client. The number of threads waiting is the number of running threads that are presently waiting for a lock. The number of threads in vdb is the number of threads engaged in remote database operations or other 'slow' I/O, such as access to outside HTTP or SOAP services. </p> <p> All locks currently in effect are listed with the owners (a) and possibly waiting transactions. The transactions are named after their client. A log or replication replay transaction is here named 'INTERNAL'. </p> </div> <div> <span class="permalink"><a id="clients" onclick="javascript:permalink(this)" href="#clients">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Clients</h5> </div> </div> </div> <p> Each connected client is listed with the number of bytes sent and received from the client. The transaction status is either PENDING for OK or BLOWN OFF or DELTA ROLLED BACK for a transaction killed by deadlock or timeout. The locks owned by the transaction are listed following the status. IE means exclusive and IS shared lock. </p> </div> <div> <span class="permalink"><a id="replication" onclick="javascript:permalink(this)" href="#replication">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Replication</h5> </div> </div> </div> <p> This section shows the server in question and a list of replication accounts either provided or received by this server. Accounts where the server name (left column) is the same as the server name are those provided by this. </p> <p> The columns are server name, account name, last transaction number and status. The status is OFF for a local account or a replicated account where the remote is not available. It is SYNCING if a resync is in progress, IN SYNC if the account is up to date or REMOTE DISCONNECTED if there was a connection to a remote party which subsequently disconnected. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/rdfgraphreplication/">RDF Graph Replication</a> </p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="indexusage" onclick="javascript:permalink(this)" href="#indexusage">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Index Usage</h5> </div> </div> </div> <p> This part of the report summarizes the database's access statistics. The output is a table with a row for each index in the database. Each row is composed of the following columns:</p> <pre class="screen"> Table The name of the table Index The name of the index. Same as the table for primary key. Touches The number of touches since startup. Each time the database engine looks at an entry of the index is counted as a touch. Not all touched entries are selected. For instance if the engine scans a table with non-indexed selection criteria it will touch each row but might select none. Reads The number of disk reads caused by reading this index. %Miss The percentage of touches that required a read. This can be over 100% since getting one entry may required more than one read if the top levels of the index are not in memory. Locks The number of times a lock is set on an entry of the index. Waits The number of times the engine has to wait for another transaction to finish in order to set a lock on this index. %W The percentage of waits of all locks set. </pre> <p> In interactive SQL </p> <pre class="screen"> SQL> status(); </pre> <p>Will print out the report.</p> </div> </div> <div> <span class="permalink"><a id="oemrelabeling" onclick="javascript:permalink(this)" href="#oemrelabeling">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Re-labeling Server Executable on Win32 Platforms</h4> </div> </div> </div> <p> The Virtuoso Service name can be altered using the key <span class="emphasis"><em>Win32ServiceName</em></span> in the <span class="emphasis"><em>Parameters</em></span> section. The default name is 'OpenLink Virtuoso VDBMS Server' </p> <p> To change the name of services: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>stop the service</td> </tr> <tr> <td>delete the service</td> </tr> <tr> <td>change the name in file virtuoso.ini</td> </tr> <tr> <td>create the service</td> </tr> <tr> <td>start the service</td> </tr> </table> <p>Services with old names must be deleted before creating service with the new name, i.e. with the Win32ServiceName setting set to the current name of the service. </p> <p> The name displayed in the ODBC Administrator, Setup and Configuration dialogs is taken from the driver section in the ODBCINST. This can be directly edited in the registry using the regedt32 Windows utility, or a registry import file can be created which can be applied by simply double-clicking the .reg file. Always exercise extreme caution when making changes to the registry. </p> </div> <div> <span class="permalink"><a id="dbsrcsecurity" onclick="javascript:permalink(this)" href="#dbsrcsecurity">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Transport Level Security</h4> </div> </div> </div> <div> <span class="permalink"><a id="srvadmencryption" onclick="javascript:permalink(this)" href="#srvadmencryption">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Encryption</h5> </div> </div> </div> <p> Virtuoso has the ability to encrypt it's CLI network connections using SSL. The server listens on a separate port for SSL CLI connections and handles them just as the normal CLI connections, vut now providing transport level security. </p> <div> <span class="permalink"><a id="srvsidesupport" onclick="javascript:permalink(this)" href="#srvsidesupport">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">Server-side Support</h6> </div> </div> </div> <p> Server side secure connections utilizes three parameters in the [Parameters] section of the virtuoso.ini: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <span class="emphasis"><em>SSLServerPort</em> </span> - Specifies the port on which the server listens for incoming SSL CLI requests.</td> </tr> <tr> <td> <span class="emphasis"><em>SSLCertificate</em> </span> - The SSL certificate to use (same meaning as the SSLCertificate in HTTPServer section)</td> </tr> <tr> <td> <span class="emphasis"><em>SSLPrivateKey</em> </span> - The server's private key (same meaning as the SSLCertificate in HTTPServer section)</td> </tr> </table> <p> These parameters should be all set in order to enable the SSL CLI server. </p> <p> If SSLServerPort is not specified, then the Virtuoso server ignores the other two and does not listen for SSL CLI connections. </p> <p> If a non-SSL connection is attempted to the SSL server port, the server rejects the connection. If an SSL connection is attempted against the non-SSL port the server rejects the connection. </p> </div> <div> <span class="permalink"><a id="clisidesupport" onclick="javascript:permalink(this)" href="#clisidesupport">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">Client-side Support</h6> </div> </div> </div> <p> The client does not require any SSL-specific files (like Certificates or Private keys) in the SSL connection process. </p> <p> <strong>Native Clients (e.g. ISQL).聽</strong> There is an custom ODBC connect option SQL_ENCRYPT_CONNECTION (=5004) supported by the Virtuoso CLI. It should be set before issuing the SQLConnect call. Values are 'NULL' (no encryption - default), '1' (encryption with no server X509 certificate checking and no X509 certificate sent to the server) and a valid file path to a PKCS#12 certificate file (protected with the same password as the one used to log in. Note that with the iODBC/ODBC clients this connect option is not applicable since the driver managers don't cache or pass through the custom ConnectOptions set before connecting to the data source. The ISQL has an additional option (-E) to do encrypted connects using the encryption option '1') and -X <file> to set the above option to the file supplied. </p> <p> <strong>ODBC & iODBC Driver.聽</strong> The drivers support an additional DSN attribute: </p> <pre class="programlisting"> ENCRYPT=<string> </pre> <p> If this attribute is not specified then it defaults to "No". </p> <p> It has the same meaning as the SQL_ENCRYPT_CONNECTION options (see above). If this is not specified then it defaults to NULL. </p> <p> The corresponding iODBC odbc.ini & ODBC Registry DSN attribute name is: </p> <pre class="programlisting"> "Encrypt"= <string> </pre> <p> The Windows Connect & Setup dialogs have an additional wizard page to configure encryption. </p> </div> <div> <span class="permalink"><a id="x509certsupport" onclick="javascript:permalink(this)" href="#x509certsupport">露</a> </span> <div class="titlepage"> <div> <div> <h6 class="title">X509 Certificate Support</h6> </div> </div> </div> <p> Virtuoso supports X509 certificate validation: server side for both ODBC and HTTPS connections, and client side for the ODBC connections. </p> <p> <strong>Server Side.聽</strong> To enable this option there are three new INI file parameters added the HTTPServer section for the HTTPS, and the Parameters section for ODBC): </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <span class="emphasis"><em>X509ClientVerify</em> </span> - Whether the server will require X509 certificates from the browsers. If set to 1 a client should send a X509 certificate which will be validated against the server CA list. </td> </tr> <tr> <td> <span class="emphasis"><em>X509ClientVerifyDepth</em> </span> - Specifies how deep the client certificate verification process will traverse the Issuer chain before giving up. The default value of 0 means that only verification of the client certificate itself being in the server's CA list is performed. Setting this option to -1 will ignore the depth checks. </td> </tr> <tr> <td> <span class="emphasis"><em>X509ClientVerifyCAFile</em> </span> - a PEM (base64) file of all the X509 certificates of the Certification Authorities (CA) which the server will use for verifying the client's client certificate. A list of these will be sent to the client as a part of the SSL handshake so the client will know which certificate to send. </td> </tr> </table> <p> <strong>ODBC Client Side.聽</strong> In order for verification of the server certificate to take place a PKCS#12 file should be supplied to the ODBC client. It will use the CA list in this PKCS#12 to verify the server certificate. It will set the verification depth to -1 (unlimited) while performing such a check. </p> <p> If the server certificate is not verified correctly it will refuse to connect to the server. When the ENCRYPT parameter is set to "1" (do SSL without X509 validation) the client will return a SQL_SUCCESS_WITH_INFO in SQLConnect/SQLDriverConnect with the Server's certificate subject and the verification result as the server will always send it's X509 certificate to the client as a part of the SSL connect handshake. </p> <p> If the PKCS#12 file is supplied the ODBC client will try to open it using the login password. In order for the file to be successfully opened it should be encrypted with the same password used for logging in. </p> <p> Normally when exporting a PKCS#12 file from other programs it will contain only the CAs of the Certificate validation chain. This means that client and server certificates should have common CA in their certificate chains in order to be used for ODBC X509 validation. The client certificate from the PKCS#12 file will not take place in the server certificate validation process. </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/fn_get_certificate_info/"> <code class="function">get_certificate_info()</code> </a> </p> </td> </tr> </table> </div> </div> </div> <div> <span class="permalink"><a id="acl" onclick="javascript:permalink(this)" href="#acl">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">File System Access Control Lists</h5> </div> </div> </div> <p> Access Control Lists (ACL) are used to restrict file system access. </p> <p> These lists are maintained in the Virtuoso INI file under the Parameters section with entries such as: </p> <pre class="programlisting"> DirsAllowed = <path> [, <path>] DirsDenied = <path> [, <path>] <path> := <absolute_path> or <relative_path> </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>A relative path is relative to the servers current working directory.</p> </td> </tr> </table> </div> <p>The Virtuoso ISQL utility can be used to check the Server DirsAllowed params as follows:</p> <pre class="programlisting"> SQL> select server_root (), virtuoso_ini_path (); </pre> <p>The above should show in the result the server working directory and INI file name.</p> <p>Also you can check the relevant INI setting by running following statement via ISQL command line utility:</p> <pre class="programlisting"> SQL> select cfg_item_value (virtuoso_ini_path (), 'Parameters', 'DirsAllowed'); </pre> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a href="/virtuoso/ch-server/#virtini">Virtuoso INI File Configuration</a> </p> </td> </tr> </table> </div> <p> ACL's work in the following way: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>All paths are converted from relative to absolute paths.</td> </tr> <tr> <td>The path beginning with <http_root> is always allowed.</td> </tr> <tr> <td>All DB files are always access denied (.db, db segments, .trx, log segments, .ini specified in INI file etc.)</td> </tr> <tr> <td>If a path is not allowed or exists as denied then access to the file is rejected. </td> </tr> <tr> <td>If a requested path is allowed and not in denied then access is allowed.</td> </tr> <tr> <td>ACL's are inherited. If a directory allows access so does its subdirectories.</td> </tr> </table> <p> The following functions are restricted by file Access Control Lists (ACL) in the virtuoso.ini file: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <a href="/virtuoso/fn_file_to_string/">file_to_string</a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_file_to_string_output/">file_to_string_output</a> </td> </tr> <tr> <td> sys_mkdir </td> </tr> <tr> <td> sys_dirlist </td> </tr> <tr> <td> <a href="/virtuoso/fn_string_to_file/">string_to_file</a> </td> </tr> <tr> <td> cfg_write </td> </tr> </table> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>the cfg_write function has restrictions against changing file access control lists in ini file</p> </td> </tr> </table> </div> </div> </div> </div> <div> <span class="permalink"><a id="vdbconcepts" onclick="javascript:permalink(this)" href="#vdbconcepts">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.2.聽Virtual Database</h3> </div> </div> </div> <div> <span class="permalink"><a id="linkrmttableauto" onclick="javascript:permalink(this)" href="#linkrmttableauto">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Linking Remote Tables & Views</h4> </div> </div> </div> <p>The Virtuoso Server supports linking in of tables, views, procedures and other components from a remote ODBC data-source, enabling them to be queried as native objects in Virtuoso; this process is called "attaching" or "linking". The easiest way to link to an external table is to use the <a href="/virtuoso/dbadmin/#remotetables">Linking Remote Tables Wizard</a> , part of the Visual Server Administration Interface. Alternatively you can attach these objects programmatically, as this section explains; finally you can attach tables manually - see <a href="/virtuoso/ch-server/#mansetrds">Manually Setting Up A Remote Data Source</a> which is useful for connections to less-capable ODBC data-sources.</p> <div> <span class="permalink"><a id="attach" onclick="javascript:permalink(this)" href="#attach">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">ATTACH TABLE Statement</h5> </div> </div> </div> <pre class="programlisting"> ATTACH TABLE <table> [PRIMARY KEY '(' <column> [, ...] ')'] [AS <local_name>] FROM <dsn> [USER <uid> PASSWORD <pwd>] [ON SELECT] [REMOTE AS <literal_table_name>] </pre> <div class="variablelist"> <dl class="variablelist"> <dt> <span class="term">table</span> </dt> <dd> <p>Adequately qualified table name of the form: identifier | identifier.identifier | identifier.identifier.identifier | identifier..identifier</p> </dd> <dt> <span class="term">column</span> </dt> <dd> <p>column to assume primary key</p> </dd> <dt> <span class="term">local_name</span> </dt> <dd> <p>fully qualified table name specifying local reference.</p> </dd> <dt> <span class="term">dsn</span> </dt> <dd> <p>scalar_exp</p> </dd> <dt> <span class="term">user</span> </dt> <dd> <p>scalar_exp</p> </dd> <dt> <span class="term">password</span> </dt> <dd> <p>scalar_exp</p> </dd> <dt> <span class="term">literal_table_name</span> </dt> <dd> <p>scalar_exp</p> </dd> </dl> </div> <p>This SQL statement defines a remote data source, copies the schema information of a given table to the local database and defines the table as a remote table residing on the data source in question. </p> <p> The table is a designation of the table's name on the remote data source dsn. It may consist of an optional qualifier, optional owner and table names, separated by dots. This must identify exactly one table on the remote dsn. The optional local_name is an optionally qualified table name which will identify the table on the local database. If qualifier or owner are omitted, these default to the current qualifier 'dbname()' and the logged in user, as with CREATE TABLE. If the local_name is not given it defaults to the <current qualifier>.<dsn>.<table name on dsn>. The <dsn> will be the dsn with all alphabetic characters in upper case and all non-alphanumeric characters replaced by underscores. The <table name on dsn> will be the exact name as it is on the remote dsn, case unmodified. </p> <p> The PRIMARY KEY option is only required for attaching views or tables where the primary key on the remote table cannot be ascertained directly from the remote data source.</p> <p> If a dsn is not previously defined with vd_remote_data_source or ATTACH TABLE, the USER and PASSWORD clauses have to be given. </p> <p>The <span class="emphasis"><em>REMOTE AS</em></span> option allows you to provide a string literal for referencing the remote table. This is useful when linking tables from sources that do not support three-part qualification correctly.</p> </div> <div> <span class="permalink"><a id="attachview" onclick="javascript:permalink(this)" href="#attachview">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Attaching views</h5> </div> </div> </div> <p> A view can be attached as a table if a set of uniquely identifying columns is supplied. </p> <p> This is done with the PRIMARY KEY option to ATTACH TABLE as follows: </p> <pre class="programlisting"> attach table T1_VIEW primary key (ROW_NO) from 'somedsn'; </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>Views cannot be attached unless the PRIMARY KEY options is used.</p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="linkrmttableautoexamples" onclick="javascript:permalink(this)" href="#linkrmttableautoexamples">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Examples for Linking Remote Tables into OpenLink Virtuoso</h5> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <a href="/virtuoso/vdbenginemclink/">Oracle</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbengineprlnk/">Progress</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbengineinglink/">Ingres</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbengineinflink/">IBM Informix</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginedb2link/">IBM DB2</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginesyblink/">Sybase</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginemsqllink/">MySQL</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginepsqllink/">PostgreSQL</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbengineodtjdlink/">JDBC</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbengineodbcodlink/">ODBC to ODBC</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginefirebdlink/">Firebird</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/vdbenginemsqlslink/">Microsoft SQL Server</a> </p> </li> </ul> </div> </div> </div> <div> <span class="permalink"><a id="linkrmtprocauto" onclick="javascript:permalink(this)" href="#linkrmtprocauto">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Linking Remote Procedures</h4> </div> </div> </div> <div> <span class="permalink"><a id="attachproc" onclick="javascript:permalink(this)" href="#attachproc">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">ATTACH PROCEDURE Statement</h5> </div> </div> </div> <pre class="programlisting"> ATTACH (PROCEDURE|FUNCTION) <proc_name> ([<parameter1>[,<parameter2>[...]]]) [ RETURNS <rettype> ] [AS <local_name>] FROM <dsn> </pre> <div class="variablelist"> <dl class="variablelist"> <dt> <span class="term">dsn</span> </dt> <dd> <p>scalar_exp</p> </dd> <dt> <span class="term">proc_name</span> </dt> <dd> <p>identifier | identifier.identifier | identifier.identifier.identifier | identifier..identifier</p> </dd> <dt> <span class="term">parameter1..parameterN</span> </dt> <dd> <p>parameters declaration (as in CREATE PROCEDURE)</p> </dd> <dt> <span class="term">local_name</span> </dt> <dd> <p>table</p> </dd> </dl> </div> <p>The ATTACH PROCEDURE statement allows you to associate stored procedures from remote datasources with Virtuoso so they can be used as if they were defined directly within Virtuoso. Much like the ATTACH TABLE statement, this SQL statement creates a local alias for a procedure on a given remote data source so it can be considered locally defined. When this alias is called called the procedure at the remote data source will actually be called.</p> <p>Procedure generated result sets are not supported by the ATTACH PROCEDURE statement. The only portable way to return values from a remote procedure is to use INOUT or OUT parameters. Remote procedure result sets can be used by combination of <code class="function">rexecute()</code> and Virtuoso PL, but this is left for the user to implement as required.</p> <p>The ATTACH PROCEDURE statement is not able to define new connections to remote data sources, the connection should be defined prior using either vd_remote_data_source or by attaching a table or view using the ATTACH TABLE statement with USER/PASSWORD supplied.</p> <p>Note that when generating pass-through statements to a given remote, any procedure call for an attached procedure is passed through if the current DSN is the same as the remote procedure's DSN.</p> <p>The <span class="emphasis"><em>proc_name</em></span> is the designation of the procedure's name on the remote data source, DSN. The remote procedure name supplied should always be fully qualified to avoid ambiguity, it may consist of an optional qualifier/catalog, optional owner and finally procedure name, separated by dots. This must identify exactly one procedure on the remote data source.</p> <p>The optional <span class="emphasis"><em>local_name</em></span> is an optionally qualified procedure name which will identify the procedure on the local Virtuoso database. If the local_name is not given it defaults to the <current qualifier>.<dsn>.<proc name on dsn>. The <dsn> will be the data source name in upper case and with all non-alphanumeric characters replaced by underscores. The <proc name on dsn> will be the exact name as it is on the remote dsn, case unmodified.</p> <p>If a dsn is not previously defined with vd_remote_data_source or ATTACH TABLE, the ATTACH PROCEDURE will fail.</p> <div class="example" id="vdocs-trans-01"> <p class="title"> <strong>Example聽6.3.聽Example:</strong> </p> <div class="example-contents"> <p> On remote Virtuoso (DSN name : remote_virt): </p> <pre class="programlisting"> CREATE PROCEDURE RPROC (IN PARAM VARCHAR) returns VARCHAR { return (ucase (PARAM)); } </pre> <p> On the local virtuoso (DSN name : local_virt) : </p> <pre class="programlisting"> vd_remote_data_source ('remote_virt', '', 'demo', 'demopwd'); ATTACH PROCEDURE RPROC (IN PARAM VARCHAR) RETURNS VARCHAR from 'remote_virt'; </pre> <p> will result in creation of an procedure alias for RPROC in local_virt named DB.REMOTE_VIRT.RPROC </p> <p> Calling it from the local_virt (using ISQL) </p> <pre class="programlisting"> select REMOTE_VIRT.RPROC ('MiXeD CaSe') as rproc_result; rproc_result --------------- MIXED CASE 1 rows </pre> </div> </div> <br class="example-break" /> </div> <div> <span class="permalink"><a id="id1321" onclick="javascript:permalink(this)" href="#id1321">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">See Also:</h5> </div> </div> </div> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">Tip</th> </tr> <tr> <td align="left" valign="top"> <p>The Virtuoso Visual Server Administration Interface provides a graphical user interface for <a href="/virtuoso/dbadmin/#remoteprocedures">linking remote stored procedures</a> .</p> </td> </tr> </table> </div> </div> </div> <div> <span class="permalink"><a id="typemapping" onclick="javascript:permalink(this)" href="#typemapping">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Data Type Mappings</h4> </div> </div> </div> <p> If a statement is passed through to a remote data source, the types returned by SQLDescribeCol are taken directly from the remote prepare and converted to the closest Virtuoso supported type. </p> <p> If a statement involves both local and remote resources all types are taken from the Virtuoso copy of the data dictionary. </p> <p> In executing remote selects Virtuoso binds output columns according to the type and precision given by SQLDescribeCol after preparing the remote statement. </p> <p> When a table is attached from a remote data source the catalog is read and the equivalent entries are created in Virtuoso. Since the types present on different DBMS's vary, the following logic is used to map ODBC types to Virtuoso types. </p> <div class="decimalstyle" id="id12058"> <p class="title"> <strong>Table聽6.1.聽Attach Table Type Mappings</strong> </p> <div class="decimalstyle-contents"> <table summary="Attach Table Type Mappings" border="1"> <colgroup> <col width="20pc" align="left" /> <col /> </colgroup> <thead> <tr> <th align="left" char="." charoff="50">SQL Type</th> <th align="char" char="." charoff="50">Mapped Type</th> </tr> </thead> <tbody> <tr> <td align="left" char="." charoff="50">SQL_CHAR</td> <td align="char" char="." charoff="50">varchar (precision)</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_VARCHAR</td> <td align="char" char="." charoff="50">varchar (precision)</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_BIT</td> <td align="char" char="." charoff="50">smallint </td> </tr> <tr> <td align="left" char="." charoff="50">SQL_TINYINT</td> <td align="char" char="." charoff="50">smallint</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_SMALLINT</td> <td align="char" char="." charoff="50">smallint </td> </tr> <tr> <td align="left" char="." charoff="50">SQL_INTEGER</td> <td align="char" char="." charoff="50">integer </td> </tr> <tr> <td align="left" char="." charoff="50">SQL_BIGINT</td> <td align="char" char="." charoff="50">decimal (20)</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_DECIMAL</td> <td align="char" char="." charoff="50">聽</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_NUMERIC</td> <td align="char" char="." charoff="50"> <p>smallint if precision < 5 and scale = 0</p> <p>integer if precision < 10 and scale = 0</p> <p>double precision if precision < 16</p> <p>decimal (precision, scale) otherwise</p> </td> </tr> <tr> <td align="left" char="." charoff="50">SQL_REAL</td> <td align="char" char="." charoff="50">real</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_FLOAT</td> <td align="char" char="." charoff="50">double precision</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_DOUBLE</td> <td align="char" char="." charoff="50">double precision</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_BINARY</td> <td align="char" char="." charoff="50">varbinary (precision)</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_VARBINARY</td> <td align="char" char="." charoff="50">varbinary (precision)</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_LONGVARCHAR</td> <td align="char" char="." charoff="50">long varchar</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_LONGVARBINARY</td> <td align="char" char="." charoff="50">long varbinary</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_DATE</td> <td align="char" char="." charoff="50">date </td> </tr> <tr> <td align="left" char="." charoff="50">SQL_TIME</td> <td align="char" char="." charoff="50">time</td> </tr> <tr> <td align="left" char="." charoff="50">SQL_TIMESTAMP</td> <td align="char" char="." charoff="50">datetime</td> </tr> </tbody> </table> </div> </div> <br class="decimalstyle-break" /> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>The general case of decimal and numeric both revert to the Virtuoso decimal type, which is a variable precision decimal floating point.</p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="transmodel" onclick="javascript:permalink(this)" href="#transmodel">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Transaction Model</h4> </div> </div> </div> <p> One transaction on the Virtuoso VDBMS server may contain operations on multiple remote data sources. As a general rule remote connections are in manual commit mode and Virtuoso either commits or rolls back the transaction on each of the remote connections as the main transaction terminates. </p> <p> ODBC does not support two phase commit. Therefore a transaction that succeeds on one remote party may fail on another. </p> <p> A transaction involving local tables and tables on one remote data source will always complete correctly since the remote is committed before the local and the local is rolled back if the remote commit fails. </p> <p> Note that even though the client to Virtuoso connection may be in autocommit mode the continuing connections will typically not be autocommitting. </p> <p> A remote connection is in autocommit mode if the Virtuoso connection is and the statement is passed through unmodified. In all other cases remote connections are in manual commit mode. </p> <p>Virtuoso supports 2PC - Two Phase Commit. See the <a href="/virtuoso/twopcimplementation/">Distributed Transaction & Two Phase Commit</a> section for more information.</p> </div> <div> <span class="permalink"><a id="vdb_sqlfunctions" onclick="javascript:permalink(this)" href="#vdb_sqlfunctions">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Virtual Database and SQL Functions</h4> </div> </div> </div> <p> Different DBMS's support slightly different sets of SQL built-in functions with slightly differing names. For example, what is called substring on Virtuoso is called substr on Informix. Virtuoso allows declaring equivalences between local user-defined or built-in functions and user defined or built-in functions on remote servers. Knowing that a function exists on a remote database allows passing processing closer to the data, resulting in evident gains in performance. </p> <p> To declare that substring is called substr on DSN inf10, you can execute: </p> <pre class="programlisting"> db..vd_pass_through_function ('inf10', 'substring', 'substr'); </pre> <p> The first argument is the name of the remote database, as used with attach table and related statements. If user defined functions with qualified names are involved, the names should be qualified in the vd_pass_through_function call also. If many qualified or unqualified forms of the name are in use, one should declare the mapping for them all. </p> <p> To verify whether this declaration takes effect, one can use explain to see the query execution plan, for example: </p> <pre class="programlisting"> explain ('select substring (str, 1, 2) from inf10.sample_table'); </pre> <p> The declarations are persistent and can be dropped by using a last argument of NULL for a given function. The declarations are kept at the level of a DSN and not at the level of the type of DBMS because different instances can have different user defined functions defined. </p> </div> <div> <span class="permalink"><a id="vdb_sqloptstatistics" onclick="javascript:permalink(this)" href="#vdb_sqloptstatistics">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Virtual Database and SQL Optimizer Statistics</h4> </div> </div> </div> <p> If a query can be executed in its entirety on a single remote database, then optimizing this query is exclusively the business of the remote database, as it gets the whole query text. Virtuoso rewrites some things and suggests a join order but these are not binding on the remote database. </p> <p> If a query involves tables from multiple remote databases or a a mix of local and remote tables, knowing basic SQL statistics on the tables is essential for producing a meaningful query plan. Virtuoso has information on indices existing on remote tables and if the remote table is attached from a known type of DBMS, Virtuoso may read the DBMS specific statistics at attach time. </p> <p> Note that the statistics of the remote database should be up to date before attaching. </p> <p> The function sys_db_stat can be used for forcing a refresh of Virtuoso's statistics on remote tables. </p> <pre class="programlisting"> sys_db_stat (5, 0) </pre> <p> will go through all tables, local and remote. For local tables, it will update statistics with a 5 percent sampling rate and for remote tables it will refresh the statistics if the type of the host DBMS is among the supported ones. If the remote DBMS is of an unknown type, Virtuoso will take the count of the remote table and select the 1000 first rows to get a sample of data lengths and column cardinalities. This is not very precise but will be better than nothing. </p> <p> In order to force a full read of a remote table for statistics gathering, one can use </p> <pre class="programlisting"> db..sys_stat_analyze ('fully qualified table name', 0, 0); </pre> <p> The table name is case sensitive, with all qualifiers, as it appears in SYS_KEYS and other system tables. This will read the whole table. </p> <p> Statistics on local as well as remote tables are kept in SYS_COL_STAT. One may look at this table to see the effects of remote statistics collection. In special cases, if a special effect is desired or the information is not otherwise available, as in the case of a very large table on an unsupported type of server, it is possible to manually update the contents of the table. Shutting down and restarting Virtuoso will force a reload of the statistics information. </p> <p> Presently Oracle, Informix and Virtuoso are supported for direct access to the remote database's statistics system tables. It is possible to define hook functions for accessing this same information from any other type of DBMS. Please contact support for instructions on this. </p> </div> <div> <span class="permalink"><a id="vdb_distrqueryoptm" onclick="javascript:permalink(this)" href="#vdb_distrqueryoptm">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Distributed Query Optimization</h4> </div> </div> </div> <p> When a query contains mixes of tables from different sources, the compiler must decide on an efficient execution plan that minimizes the number of round trips to remote servers and evaluates query conditions close to the data when possible. Additionally, any normal query optimization considerations such as choice of join order and join type apply. See the section on SQL optimization and optimizer hints for more on this. Additionally, the SQL optimizer uses round trip time statistics for the servers involved in the query. </p> <p> In the following examples, we use the tables r1..t1, r2..t1 and t1, of which r1..t1 is on a server close by, r2..t1 on a server farther away and t1 on the local server. The column row_no is a unique key and the string1 column is in indexed with 300 distinct values, the column fs1 has 3 distinct values. The tables all have 100000 rows. A round trip to r1 takes 10 ms and a round trip to r2 takes 100 ms. </p> <p> Consider </p> <pre class="programlisting"> select * from r1..t1 a, t1 b where a.row_no = b.row_no and a.fs1 = 'value1'; </pre> <p> The compiler notices that 33333 rows will be selected from r1..t1 based on fs1. It will decide to read these into a hash table, causing one linear scan of r1..t1 with relatively few round trips. Then it will read t1 locally and select the rows for which there is a matching entry in the hash. This is slightly faster than doing 33333 random lookups of t1. If fewer rows were selected from r1..t1, the compiler would do a loop join with the local t1 as the inner loop. </p> <p> The absolute worst plan would be a loop join with t1 as the outer loop, with 100000 round trips to r1. </p> <p> Now, if many tables are accessed from the same data source, the compiler tries to bundle these together into one statement. Thus, for: </p> <pre class="programlisting"> select * from r1..t1 a, r1..t1 b, t1 c where c.string1 = '111' and b.row_no = c.row_no and a.row_no = b.row_no + 1; </pre> <p> The compiler will probably do the outer loop for t1, which is expected to select 100000/300 rows. Then it will do a round trip to r1 with the statement. </p> <pre class="programlisting"> select * from t1 a, t1 b where a.row_no = b.row_no + 1 and a.row_no = ?. </pre> <p> This is likely better than doing the remote part as an outer loop, bringing all the approx 100000 results in. 333 round trips selecting 1 row is better than 100000 rows transferred. If the data source were further away, this could be otherwise, hence the importance of the round trip time statistic. </p> <p> In distributed queries, the compiler will honor the option (order) and the join types e.hg. table option *(hash) insofar the tables are local. </p> <p> Thus, if we wrote </p> <pre class="programlisting"> select * from r1..t1 a, t1 b, r1..t1 c where c.string1 = '111' and b.row_no = c.row_no and a.row_no = b.row_no + 1 option (order); </pre> <p> the compiler could not merge the two tablesfrom r1 into a single query because the order were given and there is an intervening table not located on r1. </p> </div> <div> <span class="permalink"><a id="vdb_arrayparameters" onclick="javascript:permalink(this)" href="#vdb_arrayparameters">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Use of Array Parameters</h4> </div> </div> </div> <p> ODBC and other data access API's usually offer a mechanism for executing a single parametrized statement multiple times with a single client-server round trip. This is usually called support of array parameters. </p> <p> Virtuoso can make use of array parameter support in ODBC drivers when available. Consider the statement: </p> <pre class="programlisting"> insert into r1..t1 select * from t1; </pre> <p> Without array parameters, this would make a round trip to r1 for each row inn t1. With array parameters enabled, with a batch size of 100, this would make only 1000 round trips for 100000 rows, resulting in dramatic increase in performance. Typically, if the remote server is on the same machine, array parameters make such batch operations about 3x faster. If the remote is farther away, the gain is greater. </p> <p> Array parameters are used if the remote database and its ODBC driver support them. The feature is globally disabled in the default configuration because some ODBC drivers falsely claim to support array parameters. To enable this feature, the the ArrayOptimization entry in the [VDB] section of the ini file to 1. To set the batch size, use the NumArrayParameters setting. 100 is a reasonable value. </p> <p> Some ODBC drivers also support array parameters for select statements. To enable using this, you can set the ArrayOptimization setting to 2. This may however not work with some drivers even if DML (insert/update/delete) statements do work with array parameters. </p> </div> <div> <span class="permalink"><a id="timestamp_autoincrement" onclick="javascript:permalink(this)" href="#timestamp_autoincrement">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Timestamps & Autoincrement</h4> </div> </div> </div> <p> A transaction timestamp is not the same across the transaction if the transaction has branches in different databases. </p> <p> The data type and precision of a time stamp will also vary between different types of databases. </p> <p> Hence timestamp columns coming from tables on different servers are not comparable for equality. </p> <p> In inserts and updates of remote tables timestamps are assigned by the database where the table in question is physically located. </p> <p> Identity or autoincrement columns are likewise handled by the database holding the remote table. </p> <p> Note that MS SQL Server and Virtuoso describe a timestamp column as a binary column in ODBC catalog and meta data calls. Thus remote SQL Server or Virtuoso timestamps will not appear as timestamps at all. </p> <p> In the case of a Virtuoso remote database the binary timestamp can be cast into a DATETIME data type and it will appear as a meaningful datetime. </p> </div> <div> <span class="permalink"><a id="vdbstoredprocs" onclick="javascript:permalink(this)" href="#vdbstoredprocs">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">VDB Stored Procedures & Functions</h4> </div> </div> </div> <p>These procedures allow you to manually manage remote data sources and their tables.</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <a href="/virtuoso/fn_vd_remote_data_source/">vd_remote_data_source()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_vd_remote_table/">vd_remote_table()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_rexecute/">rexecute()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_rnext/">rnext()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_rmoreresults/">rmoreresults()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_rclose/">rclose()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_rstmtexec/">rstmtexec()</a> </p> </li> </ul> </div> <p>Functions capable of returning a result-set make use of the <em class="parameter"><code>results_set</code></em> parameter. To prevent them from returning a result-set, the <em class="parameter"><code>results_set</code></em> parameter should be set to 'null'. If Virtuoso finds an awaiting parameter to contain <em class="parameter"><code>results_set</code></em> it will fetch the result set regardless of <em class="parameter"><code>cursor_handle</code></em> parameter.</p> <p>Unless explicitly granted, only the DBA group is permitted to use the <code class="function">rexecute()</code> to maintain security. Caution is required here since any user granted use of <code class="function">rexecute()</code> has full control of the remote data source set-up by the DBA, however limited to the overall abilities of the remote user on the remote data source. Users can be granted and denied access to this function using the following commands:</p> <pre class="programlisting"> GRANT REXECUTE ON '<attached_dsn_name>' TO <user_name> REVOKE REXECUTE ON '<attached_dsn_name>' FROM <user_name> </pre> <p>The following remote catalogue functions help you to obtain information about the remote datasources that you are using. These could be especially useful in Virtuoso PL later on if you are not able to know everything about the remote tables ahead of time for the ATTACH TABLE statement</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <a href="/virtuoso/fn_sql_data_sources/">sql_data_sources()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_sql_tables/">sql_tables()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_sql_columns/">sql_columns()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_sql_statistics/">sql_statistics()</a> </p> </li> <li class="listitem"> <p> <a href="/virtuoso/fn_sql_primary_keys/">sql_primary_keys()</a> </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="mansetrds" onclick="javascript:permalink(this)" href="#mansetrds">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Manually Setting Up A Remote Data Source</h4> </div> </div> </div> <p> Defining a remote table involves declaring the table as a local table and then defining the data source if not already defined and associating the new table with the remote data source. </p> <p> The data source on which a table resides is declared at the table level. This has no connection to the table's qualifier. </p> <p> Assume a remote ODBC data source named test containing a table xyz declared as follows: </p> <div class="example" id="vdocs-trans-01_01"> <p class="title"> <strong>Example聽6.4.聽Example:</strong> </p> <div class="example-contents"> <pre class="programlisting"> CREATE TABLE XYZ ( A INTEGER, B INTEGER, C INTEGER, PRIMARY KEY (A)); </pre> </div> </div> <br class="example-break" /> <p> To defined this as a remote table on the data source Virtuoso, first define the table locally, using the above CREATE TABLE statement above. </p> <p> Then define the data source: </p> <pre class="programlisting"> DB..vd_remote_data_source ('test', '', 'sa',''); </pre> <p> And the table: </p> <pre class="programlisting"> DB..vd_remote_table ('test', 'DB.DBA.XYZ', 'master.dbo.XYZ'); </pre> <p> This assumes that the remote data source has a login 'sa' with an empty password and no special connection string options. The table names in vd_remote_table have to be fully qualified. We here assume that the Virtuoso table was created by DBA in under the default qualifier DB and the remote XYZ was created by dbo in master. </p> <p> The vd_remote_table declaration does not affect statements or procedures compiled prior to the declaration. </p> <p> Additional indices of remote tables may optionally be defined. They do not affect the operation of the SQL compiler. The remote data source makes the choice of index based on the order by clause in the statement passed through. </p> </div> <div> <span class="permalink"><a id="bugslimits" onclick="javascript:permalink(this)" href="#bugslimits">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Caveats</h4> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> Never attempt to attach a local table as a remote. The server will hang if it tries to make a remote commit on itself. </p> </li> <li class="listitem"> <p> If the schema of the remote table is changed it will need to be re-attached to Virtuoso. </p> </li> <li class="listitem"> <p> The Virtuoso server treats dots (.) in the double-quotes escaped names as name element separators. For example : the table name "a.b.c" is treated as "a"."b"."c" . Because of this remote tables with dots in their table name (like tables from MS Text driver) require the dot inside the table name to be replaced with the VDB "non-delimiting-dot" (\x0A) and the vd_attach_table (in dsn varchar, in remote_name varchar, in local_name varchar, in uid varchar, in pwd varchar) to be used instead of ATTACH TABLE statement. </p> <p> The statement ATTACH TABLE "datafile.txt" as 'test' from 'text' user 'a' password 'b' should become : </p> <pre class="programlisting"> vd_attach_table ('text', 'datafile\x0Atxt', 'test', 'a', 'b'); </pre> </li> </ul> </div> <p>When Virtuoso interacts with a table or view attached from a remote data source, it must be able to uniquely identify each row of the query. At the attach time Virtuoso will query remote data source for the tables primary keys and indices. These will be used to construct a copy of the table definition in Virtuoso which is then used in reference to the remote data source. At query time this information is used as much as possible. This information may need to be supplemented by calls to SQLStatistics() for further indicies or primary key information, as a last resort Virtuoso will use SQLColAttribute() to determine which columns are SQL_DESC_SEARCHABLE. </p> </div> </div> <div> <span class="permalink"><a id="usermodel" onclick="javascript:permalink(this)" href="#usermodel">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.3.聽Virtuoso User Model</h3> </div> </div> </div> <p>The Virtuoso User Model is designed to support:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>Use of an external server for password and user account base maintenance for example an LDAP server, another database server etc. This allows user accounts to be verified against security information stored in some centralized repository, allowing integration into existing security infrastructure .</td> </tr> <tr> <td>Single namespace for users and groups for SQL and web service access. In this way the local security info is stored in one place and allows enabling SQL account to work as a web account or a web account as an SQL account. This enforces unique names for users and roles in the database.</td> </tr> <tr> <td>Extensibility of user information retrieval and checking.</td> </tr> <tr> <td>Extensibility of user account and group attributes.</td> </tr> </table> <p>There is a set of functions for administering the users and groups (roles) of a Virtuoso database. All the user administration functions are restricted to members of the dba group only.</p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>The terms 'role' and 'group' are identical in their usage in this document. The terms security object or grantee refer collectively to users and groups.</p> </td> </tr> </table> </div> <p>User manipulation functions do not generally return values. In case of error an error condition will be signaled.</p> <p>Users and roles are in the same namespace and are identified by name. One name will not both designate a user and a group. A user or group may be SQL enabled. A name that identifies a role (group) does not have a password and is not a valid login name.</p> <p>A user may belong to multiple roles. A role may inherit multiple other roles. One role may be inherited or directly granted to a security object multiple times. The order of granting is not relevant. The effective privileges of a user are those granted to public, those granted to the user plus those granted to a direct or indirect role of the user. The relationship between users and roles is many to many. A role can be granted multiple other roles as well as direct permissions. Cycles in granting roles are not allowed, an error will be signaled if an operation would result in a cycle in the role inheritance graph.</p> <p>When SQL procedures or queries are executing, the effective privileges are those granted to the owner of the procedure or view. A top level dynamic SQL statement executes with the effective privileges of the logged in user. If a SQL statement executes as a result of an HTTP request, the applicable virtual directory specifies on behalf of which SQL account the SQL is executed. A role cannot be the owner of procedures, views or other executable SQL entities.</p> <div> <span class="permalink"><a id="vumsecobjects" onclick="javascript:permalink(this)" href="#vumsecobjects">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Security Objects Management</h4> </div> </div> </div> <p>The following functions allow for creation and deletion of security objects and roles, and for assigning or removing roles from security objects:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td> <a href="/virtuoso/fn_user_create/"> <code class="function">USER_CREATE()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_role_create/"> <code class="function">USER_ROLE_CREATE()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_drop/"> <code class="function">USER_DROP()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_role_drop/"> <code class="function">USER_ROLE_DROP()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_change_password/"> <code class="function">USER_CHANGE_PASSWORD()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_set_qualifier/"> <code class="function">USER_SET_QUALIFIER()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_grant_role/"> <code class="function">USER_GRANT_ROLE()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_revoke_role/"> <code class="function">USER_REVOKE_ROLE()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_set_option/"> <code class="function">USER_SET_OPTIONS()</code> </a> </td> </tr> <tr> <td> <a href="/virtuoso/fn_user_get_option/"> <code class="function">USER_GET_OPTIONS()</code> </a> </td> </tr> </table> <p>The security objects and roles data are contained in the system tables described in the <a href="/virtuoso/usersystables/">User System Tables</a> Section of the Appendix</p> </div> <div> <span class="permalink"><a id="vumuseroptions" onclick="javascript:permalink(this)" href="#vumuseroptions">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">User Options</h4> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <strong>PASSWORD_MODE.聽</strong> Function for checking a given password on SQL or DAV login. See below. </p> </li> <li class="listitem"> <p> <strong>PASSWORD_MODE_DATA.聽</strong> Application specific data for the Password Mode hook. </p> </li> <li class="listitem"> <p> <strong>LOGIN_QUALIFIER.聽</strong> Default qualifier for SQL session. </p> </li> <li class="listitem"> <p> <strong>SQL_ENABLE.聽</strong> If set SQL login is granted. </p> </li> <li class="listitem"> <p> <strong>DAV_ENABLE.聽</strong> If set the user account can be user for web authentication. </p> </li> <li class="listitem"> <p> <strong>DISABLED.聽</strong> If set the user account is locked and cannot be used to login as SQL or Web user (depends of SQL_ENABLE and DAV_ENABLE flags). If the account in question is SQL enabled the DBA group can switch the execution identity to it (see set_user_id () function). This is useful when we need an account to execute Web pages (VSP/VSPX) with some execution permissions but we do not want to allow it to login via SQL/ODBC. </p> </li> <li class="listitem"> <p> <strong>PRIMARY_GROUP.聽</strong> This is the primary group of the user. This is no different from other group memberships. </p> </li> <li class="listitem"> <p> <strong>GET_PASSWORD.聽</strong> Function that will retrieve the password. If not defined the password is assumed to be in the SYS_USERS table. This allows for custom encrypted storage of passwords etc. This is simpler to use than the check hook. Note that for security configurations where the server never does know the passwords of user accounts, no digest based authentication schemes can be used, including the HTTP digest authentication, since the digests cannot be computed and checked without knowing the password. Possible users of this feature are DBEV_LOGIN or HTTP login hooks. </p> </li> <li class="listitem"> <p> <strong>E-MAIL.聽</strong> informative: e-mail of that user. </p> </li> <li class="listitem"> <p> <strong>FULL_NAME.聽</strong> informative: full name of the user. </p> </li> <li class="listitem"> <p> <strong>HOME.聽</strong> WebDAV home directory of the account, it is meaningful only if the account is web enabled. </p> </li> <li class="listitem"> <p> <strong>PERMISSIONS.聽</strong> WebDAV default permissions for new WebDAV objects created by the user. This is only meaningful when web access is enabled. </p> </li> </ul> </div> <p>The functions for setting/getting these options will accept any other named values, the above list only being those reserved for Virtuoso so far.</p> </div> <div> <span class="permalink"><a id="vumloginexthook" onclick="javascript:permalink(this)" href="#vumloginexthook">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Login Extension PL Hook</h4> </div> </div> </div> <p> <code class="code">DB.DBA.USER_FIND (in name varchar, ) </code> </p> <p>This is a user-defined PL function hook which, if it exists, will be executed before doing the SQL/ODBC login. In this hook the user can find a user account from some other server and register it in the local database. Or, this can be used to perform some pre-login actions. It is similar to the DBEV_LOGIN, but it does not change any account validation rule, it is purely for pre-processing.</p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p>The Database Event Hooks chapter.</p> </td> </tr> </table> </div> <div> <span class="permalink"><a id="vumplhooksxmpls" onclick="javascript:permalink(this)" href="#vumplhooksxmpls">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">PL Hooks Examples</h5> </div> </div> </div> <div class="example" id="vumqryldap"> <p class="title"> <strong>Example聽6.5.聽Querying an LDAP Server</strong> </p> <div class="example-contents"> <pre class="programlisting"> create procedure DB.DBA.LDAP_SEARCH (inout user_name varchar, in digest varchar) { whenever sqlstate '28000' goto ldap_validation_failure; if (lcase(user_name) <> 'dba')) { ldap_search('foo.bar.com', 0, 'o=organization', '(cn=a*)', sprintf('uid=%s,ou=users,o=organization', user_name), pwd_magic_calc(user_name,digest,1)); user_name := 'dba'; return 1; -- force validation as dba } else { -- bypassing ldap authentication for dba, let validation occur normally return -1; } ldap_validation_failure: return -1; -- try to validate normally }</pre> <pre class="programlisting"> create procedure DB.DBA.DBEV_LOGIN (inout user_name varchar, in digest varchar, in session_random varchar) { declare get_pwd varchar; get_pwd := user_get_option (user_name, 'PASSWORD_MODE'); if (get_pwd is not null) { declare rc integer; rc := call (get_pwd) (user_name, digest); return rc; } return -1; };</pre> <pre class="programlisting"> user_create ('test_ldap', 'secret', vector ('PASSWORD_MODE', 'DB.DBA.LDAP_SEARCH')); </pre> </div> </div> <br class="example-break" /> <div class="example" id="vumuserfindhook"> <p class="title"> <strong>Example聽6.6.聽USER_FIND PL Hook Example</strong> </p> <div class="example-contents"> <pre class="programlisting"> create table MY_DBA_USERS (M_NAME varchar primary key, M_PASSWORD varchar);</pre> <pre class="programlisting"> create procedure DB.DBA.USER_FIND (in name varchar) { -- do nothing for existing users if (exists (select 1 from SYS_USERS where U_NAME = name)) return; -- if there is in custom table if (exists (select 1 from MY_DBA_USERS where M_NAME = name)) { declare pwd varchar; -- get password select M_PASSWORD into pwd from from MY_DBA_USERS where M_NAME = name; -- create a new SQL user based on external data USER_CREATE (name, pwd, NULL); } };</pre> </div> </div> <br class="example-break" /> </div> </div> <div> <span class="permalink"><a id="vumrolesemantics" onclick="javascript:permalink(this)" href="#vumrolesemantics">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">SQL Role Semantics</h4> </div> </div> </div> <p>The terms user group and role are used interchangeably. Roles can be nested. There is a many to many relationship between users and roles. There is likewise a similar, acyclic many to many relationship between roles. Each role has a component role list of its granted (parent) roles, recursively, no cycles allowed.</p> <p>All role grants are listed in the roles system table whether they be explicitly granted or only as a result of granting a group with groups granted to it. The role grant graph has an explicit edge for each role membership, direct or otherwise. The GI_DIRECT flag is true if the grant is direct. Only direct role grants can be revoked.</p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p>The role system table description can be found in the appendix under <a href="/virtuoso/usersystables/">System Tables</a> .</p> </td> </tr> </table> </div> <p>The following SQL statements deal with roles. To create a new role (group) object the following statement can be used:</p> <pre class="programlisting">CREATE ROLE <NAME></pre> <p>The <NAME> is a name of role to be created. It must be unique in space of all security objects.</p> <div class="example" id="vumcreaterole"> <p class="title"> <strong>Example聽6.7.聽Creating a security role</strong> </p> <div class="example-contents"> <pre class="programlisting">SQL> create role admins;</pre> </div> </div> <br class="example-break" /> <p>Use the following statement to remove an existing role from the security schema. </p> <pre class="programlisting">DROP ROLE <NAME></pre> <div class="example" id="vumrmrole"> <p class="title"> <strong>Example聽6.8.聽Removing a security role</strong> </p> <div class="example-contents"> <pre class="programlisting">SQL> drop role admins;</pre> </div> </div> <br class="example-break" /> <p>The GRANT and REVOKE statements are used for controlling role membership as follows: To assign a new group, or list of groups (<ROLE>,...) to user <USER> use:</p> <pre class="programlisting">GRANT <ROLE> [, <ROLE>] TO <USER> [WITH ADMIN OPTION];</pre> <p>If the admin option is specified, the grantee can grant this same privilege further to other grantees.</p> <p>Roles can be revoked using:</p> <pre class="programlisting">REVOKE <ROLE> [, <ROLE>] FROM <USER>;</pre> <div class="example" id="vumgranting"> <p class="title"> <strong>Example聽6.9.聽Granting & revoking security roles</strong> </p> <div class="example-contents"> <pre class="programlisting">SQL> grant admins, users to demo;</pre> <pre class="programlisting">SQL> revoke admins from demo;</pre> </div> </div> <br class="example-break" /> <p>Only the dba group accounts may administer roles.</p> <p>The dba group is not physically a role. When an empty database is created, it will have the dba account with full privileges. To grant these same full privileges to another user, the dba uses the grant all privileges to <grantee>. statement. This will give the grantee full dba privileges, or in other words, add to the dba group. This may be reversed with the revoke all privileges from <grantee> statement. </p> <p>The GRANT statement accepts any valid SQL security object in the TO clause. One cannot log in or perform any operations as a role. Roles are exclusively shorthand for specific sets of permissions which are changed together and are needed for multiple users. </p> </div> </div> <div> <span class="permalink"><a id="vaddistr" onclick="javascript:permalink(this)" href="#vaddistr">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.4.聽VAD - Virtuoso Application Distribution</h3> </div> </div> </div> <p>VAD provides a package distribution framework for installation, management, dependency checking and un-installation of Virtuoso applications. A VAD package contains all required Virtuoso components, which would constitute an application or hosted solution, within a single distributable file. A VAD package cannot contain any system parts independent of Virtuoso thus excluding operating system executables, shared objects, installers or settings.</p> <p>Virtuoso and VAD provide the following abilities: </p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>List all installed VAD packages.</td> </tr> <tr> <td>List all completed operations over VAD packages.</td> </tr> <tr> <td>Dependency checking - Check preconditions for installation of a package.</td> </tr> <tr> <td>Install a VAD package.</td> </tr> <tr> <td>Verification of installed package, compare to distribution state with ability to build of list of locally changed parts of the package.</td> </tr> <tr> <td>Check preconditions for un-installation of a package.</td> </tr> <tr> <td>Uninstall a VAD package.</td> </tr> </table> <div> <span class="permalink"><a id="vadsummary" onclick="javascript:permalink(this)" href="#vadsummary">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Summary of VAD Operations</h4> </div> </div> </div> <p> The following is what the dba needs to know about VAD packages.</p> <p>A VAD package is installed from a file with the db..vad_install SQL function. The first argument is the file path, which must be in a location that the server process can open, i.e. it is in the DirsAllowed list in the virtuoso.ini file. The second argument is 0, meaning that we are installing from a file.</p> <pre class="programlisting"> SQL> vad_install ('conductor_dav.vad', 0); </pre> <p>is an example. If the package installation fails, the server exits and will have to be restarted. No effects of a failed installation will remain in the database after restart. Contact the supplier of the VAD package for further instructions.</p> <p>To know what is installed, do:</p> <pre class="programlisting"> SQL> vad_list_packages (); </pre> <p>VAD package installations are not recorded in the transaction log. Thus, if there is a backup followed by archived transaction logs produced if CheckpointAuditTrail is on in virtuoso.ini, the VAD install must be performed before replaying any logs that were made after the VAD installation. The package installation must be just in the right place in the replay sequence. In practice it is simplest to make an incremental backup after installing and packages, see backup_online () or the section on backing up.</p> <p>For any further information, including how to make VAD packages, see the rest of this chapter. </p> </div> <div> <span class="permalink"><a id="vadpackcomposition" onclick="javascript:permalink(this)" href="#vadpackcomposition">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">VAD Package Composition</h4> </div> </div> </div> <p>A VAD package has no developer tie-ins; it is built in a development environment from source code that can be managed and versioned in the developers system of preference.</p> <p>The VAD package is described by an XML structure called the 'VAD Sticker'. The VAD sticker describes items to deploy, procedures to execute at install and uninstall time and all conditions to be checked to ensure correct installation. The VAD Sticker consists of the following:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>VAD package meta data </p> <div class="itemizedlist"> <ul class="itemizedlist" type="circle"> <li class="listitem"> <p>Names of package, developer, copyright holder etc. </p> </li> <li class="listitem"> <p>Version number of package, build date, build number, build type (e.g. sort of optimization performed). </p> </li> <li class="listitem"> <p>Dependency information: minimal/maximal allowed version numbers of Virtuoso server and depending VAD packages. Every required package may include hint-text that may help the administrator determine (a) why the dependent package is required, and (b) how to obtain the required package.</p> </li> <li class="listitem"> <p>Information regarding known conflicts between packages; conflicting package names and version number, with optional troubleshooting hints.</p> </li> <li class="listitem"> <p>Ability to uninstall, a flag and list of reasons why it may be impossible to uninstall the package.</p> </li> <li class="listitem"> <p>Custom configuration data to be placed in the VAD Registry </p> </li> </ul> </div> </li> <li class="listitem"> <p>Locations of SQL files containing main and installation code: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="circle"> <li class="listitem"> <p>Pre-install code, used to check application-specific installation preconditions. </p> </li> <li class="listitem"> <p>Application specific table and view definitions. </p> </li> <li class="listitem"> <p>Application specific stored procedure and trigger definitions. </p> </li> <li class="listitem"> <p>Post-install (initialization) code, such as initial contents of tables. </p> </li> <li class="listitem"> <p>Pre-uninstall code, used to check that it is safe to uninstall a package. </p> </li> <li class="listitem"> <p>Post-uninstall code, used for removal of cached resources unusable or meaningless without the package.</p> </li> </ul> </div> </li> <li class="listitem"> <p>Locations of Resources: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="circle"> <li class="listitem"> <p>Documentation files. </p> </li> <li class="listitem"> <p>Samples data for demonstration or package sanity check.</p> </li> <li class="listitem"> <p>VSP/VSPX pages, related graphics, Java scripts, stylesheets, other web content. </p> </li> <li class="listitem"> <p>XML docs, XSLT sheets, DTDs and Schemas. </p> </li> </ul> </div> </li> </ul> </div> </div> <div> <span class="permalink"><a id="vadpackversion" onclick="javascript:permalink(this)" href="#vadpackversion">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Package Versioning</h4> </div> </div> </div> <p>All required packages should be listed in the VAD sticker. Known conflict may be listed in either of the conflicting VAD packages stickers, hence VAD stickers of all installed packages should be checked.</p> <p>Later versions of a package may be installed replacing earlier versions of the same package. This however can be prohibited by listing either version (or limit) as a known conflict in either VAD package sticker in the usual way. Furthermore, it is possible to prevent re-installation of a package by stating that it conflicts with itself. This provides some security against exploits involving attempts to upgrade, downgrade or re-install a package, in the hope that the administrator may corrupt the existing installation by installing new packages and working through installing their dependencies.</p> <p>Packages may differ in language and encoding of documentation and resource files, even though the version number remains the same. If a package is sensitive to internationalization issues, the developer should either assign different names to various localizations of the package, or divide it into kernel package for any language-independent parts and set of language-specific packages, with some dependency between them.</p> </div> <div> <span class="permalink"><a id="vadprocessres" onclick="javascript:permalink(this)" href="#vadprocessres">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Processing of Resources</h4> </div> </div> </div> <p>During creation of a VAD package, the "location" mentioned above may be name of a file in file system or URI or DAV path. Upon package-time, URIs will be resolved and resources under them will be copied into the package. The resulting sticker will thus contain the location of resource within the package, the resource itself, and the target location.</p> <p>All SQL files have a specific order of loading. Tables, views etc. must be defined before being referenced.</p> </div> <div> <span class="permalink"><a id="vadunsupportfeat" onclick="javascript:permalink(this)" href="#vadunsupportfeat">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Unsupported Features of VAD</h4> </div> </div> </div> <p>The VAD specification explicitly does not define the following:</p> <p> <strong>Method of development or environment.聽</strong> There are no specific restrictions for the schema or Virtuoso/PL code of the package. The VAD system does not make assumptions on the method of software development. </p> <p> <strong>Method of source code control or versioning.聽</strong> Version numbers used in the sticker have nothing common with tag labels in a developers versioning system. Procedures edited directly within the database using a web interface or CASE tools should be exported to a file for inclusion in a VAD package. If the application developer uses some script to export such code, this script is not usually part of sticker or the resulting package. </p> <p> <strong>Shipping/Deployment the VAD package from vendor to user.聽</strong> VAD provides no methods for downloading dependent packages, or check for package updates etc. </p> <p> <strong>Concurrent running of multiple versions of the same VAD package on a single server.聽</strong> There can be no guarantee that pre- or post-installation checks will provide valid results if more than one VAD is being processed at the same time. VAD does however guarantee that a package installation will be either entirely successful or entirely rolled back. </p> <p> <strong>Installation or maintenance of non-Virtuoso hosted components.聽</strong> Unlike Virtuoso-based packages, these components are usually operating system specific, they may require some complex tuning, and their usage from within Virtuoso applications may even require changes in virtuoso.ini configuration file. VAD packages may contain test calls in pre-installation SQL procedures to check that required external executables are available and provide the functionality required. </p> <p> <strong>Data migration.聽</strong> Some installations may require several days to complete migration/conversion of stored data. Whilst it may be possible to provide a restricted service during such time, VAD contains no tools to simplify such a process, this is left to the administrator or developer. VAD completes its work right after the execution of the post-installation code. </p> <p> <strong>Synchronous installation of a package on all hosts of a distributed system or cluster.聽</strong> VAD has no standardized metadata regarding replication issues, hence package-specific code may be required. Similarly, if a cluster uses "round-robin" or a "director" loading management system and the server should be stopped for VAD installation, the administrator should explicitly inform the cluster manager about this event. </p> </div> <div> <span class="permalink"><a id="vadsecurity" onclick="javascript:permalink(this)" href="#vadsecurity">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Security</h4> </div> </div> </div> <p>Since VAD packages are run by an administrator as the database DBA user, care must be taken to ensure the package comes from a safe source. Any new package installed may violate the security regulations of the target database and may even inflict damage to files under the web-root of the Virtuoso Server or in directories specified in the "DirsAllowed" parameter of the virtuoso.ini. If the virtuoso.ini parameter "AllowOsCalls" is enabled then the installation procedures of the package may call operating executables. It is the responsibility of the database administrator to control this via the "AllowOsCalls", "SafeExecutables" and "DbaExecutables" parameters of the virtuoso.ini.</p> <p>VAD packages do not offer any automatic protection against unauthorized modifications. Although ever VAD package contains a checksum, its purpose is to guard against data transfer errors, it may not be sufficient to detect unwanted modification.</p> </div> <div> <span class="permalink"><a id="vadbuildingvadpacks" onclick="javascript:permalink(this)" href="#vadbuildingvadpacks">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Building VAD Packages</h4> </div> </div> </div> <p>Initially, the VAD sticker and resources may reside in the file system, DAV directory and or other locations available through the <code class="function">DB.DBA.HTTP_URI_GET()</code> function.</p> <p>The VAD creation operation parses the VAD sticker's XML description and constructs the VAD file by calling <a href="/virtuoso/fn_vad_pack/"><code class="function">DB.DBA.VAD_PACK</code></a> .</p> <p>This function reads the VAD sticker identified by the <em class="parameter"><code>sticker_uri</code></em> which contains the <code class="computeroutput">vad:package</code> root element. Then the resources identified in the sticker are retrieved. All resource URIs are interpreted in the context of the <em class="parameter"><code>base_uri_of_resources</code></em> and are parsed and checked to be syntactically correct. Resources are appended to generated package that will be stored at the <em class="parameter"><code>package_uri</code></em> . <a href="/virtuoso/fn_vad_pack/"><code class="function">DB.DBA.VAD_PACK</code></a> returns a human readable log of error and warning messages, it will signal errors if any resource or database objects are unavailable at build time.</p> <p>By convention, VAD package files have the extension '.vad'.</p> </div> <div> <span class="permalink"><a id="vadutils" onclick="javascript:permalink(this)" href="#vadutils">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">VAD Utilities</h4> </div> </div> </div> <p>An optional VAD package named VADutils provides various tools for capturing changes made in the database after some point in time. The result of a capture consists of:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Database object additions whose names match given patterns (e.g. all tables and procedures within a particular catalog/qualifier).</p> </li> <li class="listitem"> <p>Resource additions under particular locations.</p> </li> <li class="listitem"> <p>Post-install local customizations of selected packages.</p> </li> </ul> </div> <p>The capture results may be useful for the following purposes:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Archival of changes for replaying later.</p> </li> <li class="listitem"> <p>Creating a special package of the changes for applying against a fresh installation of the package. </p> </li> <li class="listitem"> <p>Creating a new complete package containing both the original and changes that will be included in the package sticker.</p> </li> </ul> </div> <p>These mechanisms provide good support for centralized development and custom deployment methodology. If a site is localized to contain local links, graphics, custom layout and such, then VAD capabilities offer help to the developer to define the specific overlay of customizations over another VAD package. When the underlying VAD package is updated the local customizations will be overwritten. Being saved in a VAD package, customizations can be reapplied over the updated base package.</p> </div> <div> <span class="permalink"><a id="vadadminrspnslts" onclick="javascript:permalink(this)" href="#vadadminrspnslts">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">VAD Administrator Responsibilities</h4> </div> </div> </div> <p>VAD package installation, upgrade and uninstallation requires a temporary break of service. The package checks may be performed on the fly if it can be guaranteed that the resources being inspected will not be altered by any users. The package check is a read-only process and operates solely within the VAD Registry using read-only functions.</p> <p>All VAD operations are logged in the server event log. All completed operations are reflected in the <code class="computeroutput">DB.DBA.VAD_HISTORY</code> system table.</p> <p>The optional VADutils package provides some additional administrative tools, mostly for troubleshooting. These include special installation and de-installation functions that can ignore error signals, and provide an interactive editor for the VAD Registry etc.</p> <p>All operations described below require DBA access to the database.</p> <p>Check if a VAD package may be installed by calling <a href="/virtuoso/fn_vad_check_installability/"><code class="function">DB.DBA.VAD_CHECK_INSTALLABILITY</code></a> .</p> <p>Checks the presence and correct versions of required packages and of the Virtuoso platform. It does not executes any pre-install Virtuoso/PL code from the package, so there's no guarantee that installation will be successful if the check found no error. If <em class="parameter"><code>package_uri</code></em> is DAV path, <em class="parameter"><code>is_dav=1</code></em> , else <em class="parameter"><code>is_dav=0</code></em> .</p> <p>Perform VAD Package Installation by calling <a href="/virtuoso/fn_vad_install/"><code class="function">DB.DBA.VAD_INSTALL</code></a> .</p> <p>If <em class="parameter"><code>package_uri</code></em> is DAV path, <em class="parameter"><code>is_dav=1</code></em> , else <em class="parameter"><code>is_dav=0</code></em> .</p> <p>The administrator performs the following operations when installing:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Invoke the install procedure from the web user interface or interactive SQL. This will perform the following: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="circle"> <li class="listitem"> <p>Install documentation files. </p> </li> <li class="listitem"> <p>Check for version and prerequisite package compatibility. </p> </li> <li class="listitem"> <p>Disconnect SQL users and terminate web processing. </p> </li> <li class="listitem"> <p>Make a database checkpoint. </p> </li> <li class="listitem"> <p>Run the pre-install SQL script. </p> </li> <li class="listitem"> <p>Load SQL code in the VAD package, in the order specified by the developer. </p> </li> <li class="listitem"> <p>Copy web resources (VSP, VSPX, XSLT, etc.) into their designated places in WebDAV or file system Web root. </p> </li> <li class="listitem"> <p>Run any post-install SQL code. </p> </li> </ul> </div> </li> <li class="listitem"> <p>If the installation was successful, the server will come back on-line. </p> </li> <li class="listitem"> <p>If the installation was unsuccessful, e.g., mid-install failure due to running out of disk space, or some other serious unrecoverable database error, the Virtuoso server will exit. The administrator should consult the Virtuoso log file to see what caused the failure. The installation can be completely undone manually by halting the server (if not already stopped), and removing the transaction log file (.trx). Upon Virtuoso restart, the server will continue from the last checkpoint, made prior to install, as if the installation never took place.</p> </li> </ul> </div> <p>The return value of the <a href="/virtuoso/fn_vad_install/"><code class="function">DB.DBA.VAD_INSTALL()</code></a> function is usually a sum of messages from pre- and post-installation procedures of the package. It should normally contain at least the following:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>any errors and/or warnings encountered.</p> </li> <li class="listitem"> <p>created users and catalogs/qualifiers </p> </li> <li class="listitem"> <p>root VSP page for accessing the application, if applicable.</p> </li> <li class="listitem"> <p>path to installed documentation files.</p> </li> <li class="listitem"> <p>performance optimization hints.</p> </li> </ul> </div> <p>The VAD packages should be tested to install on an empty Virtuoso database, after any required VAD packages. Installing a package on an empty server is useful for determining that no other procedures or components were missed. Since the application would normally run on the development machine where the VAD package was built, it can be easy to overlook some components. The completeness of the source archive of the application and its independence from any ad hoc SQL objects is important, this is the only way the package can be reliably versioned, tracked or uninstalled.</p> <p>Check if a VAD package may be uninstalled by calling <a href="/virtuoso/fn_vad_check_uninstallability/"><code class="function">DB.DBA.VAD_CHECK_UNINSTALLABILITY</code></a> </p> <p>Performs a preliminary read-only checks to see whether the package given can be uninstalled. This does not execute any pre-uninstall Virtuoso/PL code from within the package at this stage. Hence, the success of this function does not guarantee that uninstallation will be successful.</p> <p>Perform VAD Package Uninstallation by calling <a href="/virtuoso/fn_vad_uninstall/"><code class="function">DB.DBA.VAD_UNINSTALL</code></a> .</p> <p>The administrator will perform the following operations for the uninstallation process:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Invoke the uninstall procedure from the web user interface or interactive SQL. This will initiate the following: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="circle"> <li class="listitem"> <p>Check that no other packages are using the package to be uninstalled. </p> </li> <li class="listitem"> <p>disconnect SQL users and terminate web processing. </p> </li> <li class="listitem"> <p>Make a database checkpoint. </p> </li> <li class="listitem"> <p>Run the pre-uninstall SQL script. </p> </li> <li class="listitem"> <p>Remove web resources installed by the package (all VSP , VSPX, XSLT, etc files) in WebDAV or the filesystem under the web root.</p> </li> <li class="listitem"> <p>Drop all SQL procedures and data. This is performed in reverse order to the install. </p> </li> <li class="listitem"> <p>Run any post-uninstall SQL code.</p> </li> <li class="listitem"> <p>Remove documentation files explicitly marked as removable. Usually documentation would not be deleted as part of package uninstallation in case it is needed e.g. if a set of documents is distributed as VAD package) </p> </li> </ul> </div> </li> <li class="listitem"> <p>If uninstallation was successful the server will come back on-line. </p> </li> <li class="listitem"> <p>If uninstallation was unsuccessful, the server will exit. Uninstallation could fail due to lack of disk space or some other serious unrecoverable database error. The failed uninstallation attempt can be manually reversed by halting the server (if not already) and deleting the transaction log file (.trx). Upon server restart Virtuoso will continue from the last checkpoint, made prior to uninstallation, as if the uninstallation was never attempted. The administrator should consult the log file for clues to the failure. </p> </li> </ul> </div> <p>Check the state of VAD package installation by calling <a href="/virtuoso/fn_vad_check/"><code class="function">DB.DBA.VAD_CHECK</code></a> .</p> <p>This checks to see if the elements of the package are as they are defined in the original distribution. A list of differing elements is returned. Differences revealed may not indicate a corruption, such changes could have been made intentionally by another package, possibly a later version or upgrade that added some columns to tables, and some resources may be customized by the user post-installation.</p> <p>This will check for the prior existence of tables, views etc owned by other applications that are not compatible with this application. Any such schema objects found are listed, the installation will not continue. These may be dropped by the DBA to help the installation to succeed. Some such elements may not be part of some other package, hence no package uninstall would be available leading the DBA to drop them with the appropriate SQL commands.</p> <p>To enable automatic vads updates on server startup, set the VADInstallDir parameter in the <a href="/virtuoso/ch-server/#ini_parameters">[Parameters] ini section</a> with path the folder containg the vads files.</p> </div> <div> <span class="permalink"><a id="vadpackageoverlap" onclick="javascript:permalink(this)" href="#vadpackageoverlap">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Package Overlap</h4> </div> </div> </div> <p>Each package contains full definitions of all tables and indices. Upon installing the following outcomes can occur:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>If a table already exists with the same primary key as the new definition, additional columns are added to the table. If the primary keys differ, the installation automatically fails. Note that a pre-install SQL script can be defined to explicitly alter tables if consecutive versions of an application use different primary keys. </p> </li> <li class="listitem"> <p>Existing indexes are left untouched. New indices are added as specified in the package. If indices should be modified or dropped, the pre-install script is a reasonable place for dropping these.</p> </li> </ul> </div> <p>Thus the same SQL schema can be loaded twice without ill effect.</p> <p>The post install script should be used to populate tables and such. Inserts should be executed using the insert soft statement so that attempts to insert duplicate are silently ignored without causing the installation to fail. The post install script can perform any application level data format changes.</p> <p>Packages should define their own distinct catalog or qualifier. They should not overwrite another package unless upgrading a prior version. Sometimes a package will require the use of another package's tables. This should be achieved via grants issued in a pre-install script. A schema element such as a table, view or procedure will always have at most one owner package even though it may be referenced or even modified with additional columns by another package installed later. These elements will only be dropped when the owner package is dropped. Tables created ad-hoc from interactive SQL do not have any owner package.</p> </div> <div> <span class="permalink"><a id="vadsticker" onclick="javascript:permalink(this)" href="#vadsticker">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">VAD Sticker</h4> </div> </div> </div> <p>The VAD Sticker contains meta-data and descriptions of resources contained, or to be contained, within a VAD package. Like any XML documents, the target VAD package sticker can be sourced from more than one source file, which can aid maintenance and development.</p> <div> <span class="permalink"><a id="vadstickerdtd" onclick="javascript:permalink(this)" href="#vadstickerdtd">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">VAD Sticker DTD</h5> </div> </div> </div> <p>The namespace vad, used below, represents the URI <code class="computeroutput">http://example.com/urn/vad</code> .</p> <p>The top level element of a VAD Sticker is <sticker>. It must contain a <caption> element and may contain <dependencies>, <procedures>, <ddls> and <resources> elements.</p> <pre class="programlisting">  <!ENTITY % vad.source_sticker "INCLUDE"> <!ENTITY % vad.package_sticker "IGNORE"> <!ENTITY % vad.ecm.group_content "(dependencies | procedures | ddls | resources | registry)" > <![%vad.source_sticker;[ <!ENTITY % vad.ecm.sticker "(caption, (group | %vad.ecm.group_content;)*)"> <!ELEMENT group ((group | %vad.ecm.group_content;)*) > ]]> <![%vad.package_sticker;[ <!ENTITY % vad.ecm.sticker "(caption, %vad.ecm.group_content;)"> ]]> <!ELEMENT sticker %vad.ecm.sticker; > <!ATTLIST sticker version NMTOKEN #REQUIRED xml:lang CDATA #REQUIRED >   <!ELEMENT caption (name, version)> <!ELEMENT name ((prop)*)> <!ATTLIST name package NMTOKEN #REQUIRED > <!ELEMENT version ((prop)*)> <!ATTLIST version package NMTOKEN #REQUIRED > <!ELEMENT prop EMPTY> <!ATTLIST prop name NMTOKEN #REQUIRED value CDATA #REQUIRED >  </pre> <p>The caption contains one name and one version element. These elements have a package attribute for keeping requisites used by VAD procedures. Other prop-s are for keeping admin-readable info, but they will not affect the installer's behavior. Typical names of properties here are Vendor, Copyright, Release+Date, Build, Language, Encoding, but any (even non-unique) names are acceptable.</p> <p>Sticker's elements for dependencies</p> <pre class="programlisting">  <!ELEMENT dependencies ((require | allow | conflict)*) > <!ATTLIST dependencies> <!ENTITY % vad.ecm.version_list "((version | versions_earlier | versions_later)*)"> <!ELEMENT require (name, %vad.ecm.version_list;) > <!ELEMENT allow (name, %vad.ecm.version_list;) > <!ELEMENT conflict (name, %vad.ecm.version_list;) > <!ATTLIST require group NMTOKEN #IMPLIED > <!ELEMENT versions_earlier ((prop)*)> <!ATTLIST versions_earlier package NMTOKEN #REQUIRED > <!ELEMENT versions_later ((prop)*)> <!ATTLIST versions_later package NMTOKEN #REQUIRED >  </pre> <p>Element dependencies contains an list of packages related to given one. For every version or range of versions of every package, developer may specify whether the given version is required for the package, or allowed but not required, or will cause some sort of troubles.</p> <p>More precisely, to find information about some particular version of a package, the list of children of dependencies element will be scanned from top to bottom. If the first matching record is in conflict group, not in require or allow, then installation is impossible. From other side, there must be at least one installed package for every require section.</p> <p>Element require may be labeled with optional group attribute. As an exception from common rule, there must be at least one installed package for every group of require sections with identical name. E.g. If an installation of package B requires either of two interchangeable packages A1 and A2, sticker should contain a pair of nodes in the same group:</p> <pre class="programlisting"> <require group="G"> <name package="A1">...</name> </require> </pre> <p>...</p> <pre class="programlisting"> <require group="G"> <name package="A2">...</name> </require> </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>There are no methods to specify that exactly one package, either A1 or A2, should be installed. It must be done by placing proper conflict descriptions in stickers of A1 and/or A2, but not in the sticker of B.</p> </td> </tr> </table> </div> <p>Sticker's elements for procedures</p> <pre class="programlisting">  <!ELEMENT procedures ((sql)*)> <!ATTLIST procedures uninstallation (supported | prohibited) #REQUIRED > <![%vad.source_sticker;[ <!ENTITY % vad.sql.include "include CDATA #IMPLIED"> ]]> <![%vad.package_sticker;[ <!ENTITY % vad.sql.include ""> ]]> <!ELEMENT sql (#PCDATA)> <!ATTLIST sql purpose (install-check | pre-install | post-install | uninstall-check | pre-uninstall | post-uninstall) #REQUIRED %vad.sql.include; >  </pre> <p>Element procedures contains an list of Virtuoso/PL fragments, and every fragment is tagged by one of four values of the purpose attribute. At every stage of install or uninstall VAD procedure, a whole list of procedures will be scanned from the beginning to the end, and all procedures of appropriate sort will be executed in the same order as they are listed. In source sticker files, include attribute may be used to insert text of some external file instead of having SQL code written inside the element.</p> <p>Sticker's elements for ddls</p> <pre class="programlisting">  <!ELEMENT ddls ((sql)*)> <!ATTLIST ddls >  </pre> <p>Element ddls is very similar to procedures and contains an list of Virtuoso/PL fragments to create schemas etc.</p> <p>Sticker's elements for resources</p> <pre class="programlisting">  <!ELEMENT resources ((file | location)*)> <!ATTLIST resources > <![%vad.source_sticker;[ <!ENTITY % vad.file.source_uri "source_uri CDATA #IMPLIED"> ]]> <![%vad.package_sticker;[ <!ENTITY % vad.file.source_uri ""> ]]> <!ELEMENT file EMPTY> <!ATTLIST file type (doc | http | dav | code | special) #REQUIRED source (http) "http" target_uri CDATA #REQUIRED makepath (yes | no | abort) "abort" overwrite (yes | no | abort | equal | expected) "equal" package_id CDATA #IMPLIED location IDREF #IMPLIED dav_owner CDATA #IMPLIED dav_grp CDATA #IMPLIED dav_perm CDATA #IMPLIED %vad.file.source_uri; > <!ELEMENT location ((prop)*) > <!ATTLIST location id ID #REQUIRED default_target_uri CDATA #REQUIRED >  </pre> <p>Element resources lists all files to be copied onto target box. For every file, source and target URIs should be specified, and suggested behavior for cases when a directory should be created or file should be overwritten. Target URI may be relative to one of roots: for documentation, web-resources, DAV, SQL code (it's where virtuoso.ini is located) and one of special locations, additionally specified by location elements. (Installer may query administrator to allow changing of locations' roots; in such case, information from location's properties will be shown to the administrator.) By default, the value of <em class="parameter"><code>package_id</code></em> is a space delimited list of type, location ID (if any) and target URI.</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>dav_owner - DAV owner for file (used if type="dav", ignored if "filesystem");</td> </tr> <tr> <td>dav_grp - DAV group for file (used if type="dav", ignored if "filesystem");</td> </tr> <tr> <td>dav_perm - DAV permissions for file (used if type="dav", ignored if "filesystem").</td> </tr> </table> <div class="example" id="ex_vadstickfile"> <p class="title"> <strong>Example聽6.10.聽VAD installable file descriptions</strong> </p> <div class="example-contents"> <p>To install files into DAV:</p> <pre class="programlisting"> <file type="dav" source="http" target_uri="yacutia/yacutia_style.css" dav_owner='dav' dav_grp='administrators' dav_perm='111101101N' makepath="yes"/> <file type="dav" source="http" target_uri="yacutia/yacutia_vdir_style.css" dav_owner='dav' dav_grp='administrators' dav_perm='111101101N' makepath="yes"/> </pre> <p>To install files into file system:</p> <pre class="programlisting"> <file type="http" source="http" target_uri="yacutia/yacutia_style.css" makepath="yes"/> <file type="http" source="http" target_uri="yacutia/yacutia_vdir_style.css" makepath="yes"/> </pre> </div> </div> <br class="example-break" /> <p>Sticker's elements for registry</p> <pre class="programlisting">  <!ELEMENT registry ((record)*)> <!ATTLIST registry > <!ELEMENT record ANY> <!ATTLIST record key CDATA #REQUIRED type (STRING | INTEGER | KEY | URL | XML) #REQUIRED overwrite (yes | no | abort | equal | expected) "equal" >  </pre> <p>Element registry lists all branches to be defined in the VAD Registry. Every record element contain data of one record. The first children of record element (either a text or an element) will be serialized and stored as a value of <em class="parameter"><code>DB.DBA.VAD_REGISTRY.R_VALUE</code></em> cell. To prevent errors, it is recommended to keep comments to the data outside the record element: being in the wrong place inside, they may be stored in the registry instead of actually needed data.</p> <div class="example" id="ex_vadstickers"> <p class="title"> <strong>Example聽6.11.聽Sample Stickers</strong> </p> <div class="example-contents"> <p>A package that contains only some commonly useful ("exported") functions, one table for internal purposes, a small sample VSP application, and small set of documentation files.</p> <pre class="programlisting"> <?xml version="1.0" encoding="ASCII" ?> <!DOCTYPE sticker SYSTEM "vad_sticker.dtd"> <sticker version="1.0.010505A" xml:lang="en-UK">  <caption> <name package="rdf_lib"> <prop name="Title" value="RDF Support Library" /> <prop name="Developer" value="OpenLink Software" /> <prop name="Copyright" value="(C) 2024 OpenLink Software" /> <prop name="Download" value="http://example.com/virtuoso/rdf_lib/download" /> </name> <version package="3.14"> <prop name="Release+Date" value="2003-05-05" /> <prop name="Build" value="Release, optimized" /> </version> </caption>  <dependencies> <allow> <name package="virtodp"></name> <versions_earlier package="1.00"></versions_earlier> </allow> <conflict> <name package="virtodp"> <prop name="Title" value="Virtuoso ODP Sample" /> </name> <versions_earlier package="2.17"> <prop name="Date" value="2001-01-26" /> <prop name="Comment" value="An incompatible version of RDF library is included in some old versions of virtodp " /> </versions_earlier> </conflict> </dependencies>  <procedures uninstallation="supported"></procedures>  <ddls> <sql purpose="pre-install"> "DB"."DBA"."VAD_CREATE_TABLE" ('DB', 'DBA', 'RDF_SCHEDULED_IMPORTS', 'ID integer, URI varchar, CALLBACK varchar, VERSION varchar, REPORT long varchar, primary key (ID)'); </sql> <sql purpose="post-install"> "DB"."DBA"."VAD_LOAD_RESOURCE" ('rdf_functions'); </sql> </ddls>  <resources>  <file type="doc" target_uri="rdf_lib/1.1/intro.dxt" /> <file type="doc" target_uri="rdf_lib/1.1/interface.dxt" /> <file type="doc" target_uri="rdf_lib/1.1/implementation.dxt" /> <file type="doc" target_uri="rdf_lib/1.1/sample_app.dxt" />  <file package_id="rdf_functions" type="code" target_uri="rdf_lib/1.1/rdf_lib.sql" />  <file type="http" target_uri="rdf_lib/rdf_edit/default.htm" /> <file type="http" target_uri="rdf_lib/rdf_edit/browse.vsp" /> <file type="http" target_uri="rdf_lib/rdf_edit/edit.vsp" />  <file type="dav" target_uri="rdf_lib/sample_odp_structure.rdf" />  <file type="code" target_uri="rdf_lib/1.1/rdf_edit/content_level.sql" /> <file type="code" target_uri="rdf_lib/1.1/rdf_edit/view_level.sql" /> </resources>  </sticker> </pre> </div> </div> <br class="example-break" /> </div> </div> </div> <div> <span class="permalink"><a id="backup_recovery" onclick="javascript:permalink(this)" href="#backup_recovery">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.5.聽Data Backup & Recovery</h3> </div> </div> </div> <p>Administering a database involves taking backups and having a readiness to recover from backups and subsequent transaction logs.</p> <p>Backups can be taken in two principal ways:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>Using the Virtuoso backup function/procedures.</td> </tr> <tr> <td>Copying the database files.</td> </tr> </table> <p>The Virtuoso backup functions can be used from any client directly, such as ISQL. It is possible, and perhaps preferable, to create stored procedures for performing the backup functions and scheduling these with the Virtuoso scheduler.</p> <p>The actual database file(s) can be copied while the database is running so long as no checkpoint is made during the copy process. Checkpointing can be disabled for this, but make sure it is re-enabled after the backup has been made.</p> <p>Making a full backup of a large database can take several hours if not days just due to the speed of tapes or local area networks. Full backups must in all cases be done without an intervening checkpoint. This is why frequent full backups are not desirable. To ensure the possibility of full recovery one must have the complete set of transaction logs (audit trail log) since the last backup.</p> <p>Restarting the database after restoring backed up files will show the state in effect since the last checkpoint preceding the backup. Any transaction log files made after the point of backup can be replayed to bring the state up to the last recorded transaction.</p> <div> <span class="permalink"><a id="backup_audit" onclick="javascript:permalink(this)" href="#backup_audit">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Log Audit Trail</h4> </div> </div> </div> <p>Virtuoso can maintain a transaction audit trail. This is enabled using the CheckpointAuditTrail setting in the virtuoso.ini file. When this setting is non-zero, Virtuoso will begin a new transaction log after each checkpoint. Thus one automatically gets a full, unbroken sequence of transaction logs for the entire age of the database. These logs are named as specified in virtuoso.ini and are suffixed with their creation time.</p> <p>Transaction logs older than the log that was current at the time of the last backup are superfluous for recovery, since their transactions were checkpointed before the backup started. Transactions of the log current at the time of the backup are NOT in the backed up state since they were not checkpointed, i.e. written into the read-only section of the database containing the data being backed up.</p> <p>We strongly advise having the CheckpointAuditTrail enabled in any production environment.</p> <p>It is good practice to have at least two generations of full backup, since the last backup may contain errors that were not known at the time of its making. If such precaution is taken then only transactions logs older than the oldest backup are safe to remove. If we needed to recover from the oldest backup for any reason we would require all audit transaction logs created during and after that backup.</p> <p>A Virtuoso database can be restored from the last full backup and all Audit Trail transaction files created during and after the backup. You would need to start the database as normal with the backup version of the database file. Once the database has been started, connect using iSQL. You can then use the <a href="/virtuoso/fn_replay/">replay()</a> function to replay the transaction files up to the required point. It is vital that these files are replayed in the correct order.</p> </div> <div> <span class="permalink"><a id="onlinebackups" onclick="javascript:permalink(this)" href="#onlinebackups">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">On-Line Backups</h4> </div> </div> </div> <div> <span class="permalink"><a id="usingbackuponline" onclick="javascript:permalink(this)" href="#usingbackuponline">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Backup Using Backup_Online()</h5> </div> </div> </div> <p>Virtuoso is capable of performing online backups so that normal database operation does not have to be disrupted in order to take backups. The <a href="/virtuoso/fn_backup_online/"><code class="function">backup_online()</code></a> can be used to backup the database in the state effective at the last checkpoint to a series of backup files.</p> <p> The database storage is divided into a checkpoint space that is a read only image from the time of the last checkpoint and thus can be safely backed up anytime between checkpoints and the commit space where updates subsequent to the last checkpoint data are stored. Additionally, the database records what pages have changed since the last checkpoint every time new checkpoint is made. This change tracking makes it possible to make incremental backups. The first time the backup_online function is called, it saves a compressed copy of the then current checkpoint state into one or more files. The next time it is called, it will write the changes that have come into the checkpoint space since the last time backup_online was called. It is possible to erase the change tracking data with the backup_context_clear function. The next call to backup_online will then make a full backup. Files generated by one or more calls to backup_online without intervening backup_context_clear form a series with distinct serial numbers and will be restored together. In order to restore such files, the administrator must delete the previous database files and start the server with a special flag and indicate the location of the backup files. This will bring the database to the state corresponding to the state as of the checkpoint immediately preceding the last call to backup_online, i.e. the one that wrote the newest of the backup files being restored. To restore onwards from this state, the administrator must replay transaction logs, starting with the log that was current when the last call to backup_online was made. In order to preserve all such logs, one must run with the CheckpointAuditTrail ini parameter set to 1. </p> <p>A database checkpoint cannot be performed while an online backup is in progress. </p> <div class="example" id="ex_anonlinebackup"> <p class="title"> <strong>Example聽6.12.聽Performing an Online Backup</strong> </p> <div class="example-contents"> <pre class="programlisting"> SQL> backup_context_clear (); SQL> checkpoint; SQL> backup_online ('virt-inc_dump_#', 150); </pre> </div> </div> <br class="example-break" /> <p>The <code class="function">backup_online()</code> procedure differs from the the CheckPointAuditTrail mainly because it can be started from any point in the database. Unless CheckPointAuditTrail was enabled when the database was created, the database file at a particular state and all transaction logs created by the AuditTrail since that state would be required to restore the database. Only the backup set files would be required to restore from <code class="function">backup_online()</code> . The <code class="function">backup_online()</code> also makes a compressed backup, making it far more suitable for large databases.</p> <p>The last optional parameter allows to point the directory(ies) where the backup files must be stored. See <code class="function">backup_online()</code> description for details. </p> </div> <div> <span class="permalink"><a id="rstrfrmbckuponline" onclick="javascript:permalink(this)" href="#rstrfrmbckuponline">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Restoring From an Online Backup Series</h5> </div> </div> </div> <p>To restore from a backup series the administrator must first shutdown the Virtuoso database server and move all database files (e.g. virtuoso.db and virtuoso.trx) out of the database directory. It is recommended that copies by taken rather than deleting them entirely. Then the command:</p> <pre class="programlisting"> <virtuoso exe> +restore-backup <FILE_PREFIX> </pre> <pre class="programlisting"> -- for example: virtuoso-iodbc-t +restore-backup dump-20011010_# </pre> <p>must be issued in the directory where the "*.bp" were stored. The database will then be restored. The expression <virtuoso exe> above must be replaced with the path and filename to the Virtuoso server executable used on your system (e.g. ..\virtuoso-odbc-t.exe).</p> <p>Each file in the series has a header containing a unique identifier, for the backup set and the sequence number of the file in the backup set . If an identifier in any file in the backup sequence differs from the identifier contained in the first file, the restoration process will stop and report an error, which is written to the Virtuoso log file.</p> <p>At times the backup or restoration commands may return errors. Use the following list to help diagnose and resolve them:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <strong>Timestamp [%lx] is wrong in file %s.聽</strong> The unique identifier in header of the file differs from the identifier of the first file. It is possible that the file was renamed or corrupt or belongs to another backup set. </p> </li> <li class="listitem"> <p> <strong>Number of file %s differs from internal number [%ld].聽</strong> The sequence number of the file does not correspond to the internal sequence number of file. This could be caused by the file being renamed or corrupt. </p> </li> <li class="listitem"> <p> <strong>Prefix is wrong in file %s.聽</strong> The prefix of the file does not correspond to internal information. Possible reason: file was renamed or corrupt or belongs to another backup set. </p> </li> <li class="listitem"> <p> <strong>Could not begin online-backup.聽</strong> Read error. Possible reason: Virtuoso database file was corrupt. </p> </li> <li class="listitem"> <p> <strong>Seek/Read failure on stripe %s/database.聽</strong> Read error. Possible reason: Virtuoso database file was truncated or hardware error. </p> </li> <li class="listitem"> <p> <strong>Read of page %ld failed.聽</strong> Read error. Possible reason: Virtuoso database file was truncated or hardware error. </p> </li> <li class="listitem"> <p> <strong>Backup file writing error.聽</strong> Write error. Possible reason: disk is malfunctioning or full. </p> </li> </ul> </div> <div class="example" id="ex_anonlinebackuprestore"> <p class="title"> <strong>Example聽6.13.聽Restoring an Online Backup</strong> </p> <div class="example-contents"> <p>Following the online backup example above:</p> <pre class="programlisting"> SQL> backup_context_clear (); SQL> checkpoint; SQL> backup_online ('virt-inc_dump_#', 150); </pre> <p>The following command could be used to restore the database from the backup files created:</p> <pre class="programlisting"> virtuoso-iodbc-t -c <db-ini-file> +restore-backup virt-inc_dump_# </pre> <p>or:</p> <pre class="programlisting"> virtuoso-odbc-t.exe -c <db-ini-file> +restore-backup virt-inc_dump_# </pre> </div> </div> <br class="example-break" /> </div> </div> <div> <span class="permalink"><a id="otherbackupmethods" onclick="javascript:permalink(this)" href="#otherbackupmethods">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Other Backup Methods</h4> </div> </div> </div> <p> A possible way of making a full backup of a large databases is first to turn off any automatic checkpoints and make a compressed copy of the files. After the back up is complete, checkpointing should be re-enabled. The files should be compressed to make efficient use of space, and should be copied to a disk separate from the location of the database, and preferably to an external backup medium such as tape. </p> <div> <span class="permalink"><a id="manualbackup" onclick="javascript:permalink(this)" href="#manualbackup">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Manual Backup</h5> </div> </div> </div> <p> For a large database it is best to turn off any automatic checkpoints and copy the database files to external storage. Checkpoints should be turned off by issuing the command: </p> <pre class="programlisting"> checkpoint_interval (-1); </pre> <p> at the SQL prompt. Checkpoints can be re-enabled in a post-backup script by: </p> <pre class="programlisting"> checkpoint_interval (<n>); </pre> <p> which sets the automatic checkpoint interval to <n> minutes. The backup will be unusable if there are checkpoints made while it is in progress. Thus it is important to guarantee that checkpoints do not occur. The only safe way of doing this is the above, since it is in principle possible to have a server crash during the backup and a roll forward following restart, all while the backup is in progress. If this happens the backup will be readable and consistent with the state of the last checkpoint if and only if there are no checkpoints between its start and completion. Setting the interval to -1 will guarantee that the server, when starting after recovery will not make a checkpoint. </p> <p> The dba must make sure that clients do not issue checkpoint or shutdown statements while a backup is in progress. </p> <p>The presence or absence of checkpoints at a given point in time can be ascertained from the virtuoso.log event log file. </p> </div> <div> <span class="permalink"><a id="offlinebackups" onclick="javascript:permalink(this)" href="#offlinebackups">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Off-Line Backups</h5> </div> </div> </div> <p> When Virtuoso is not running a complete and clean backup can be taken by making a copy of the database file and transaction file(s) created after the last checkpoint. </p> <p> To get an up to the minute copy of a running database one can copy the database file and the associated log, i.e. the file specified in TransactionFile in the database's configuration file. When started, the log will roll forward and restore the database to the state following the last logged transaction. </p> </div> </div> <div> <span class="permalink"><a id="vdbrecovery" onclick="javascript:permalink(this)" href="#vdbrecovery">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Database Recovery</h4> </div> </div> </div> <div> <span class="permalink"><a id="dbrebuild" onclick="javascript:permalink(this)" href="#dbrebuild">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Rebuilding A Database</h5> </div> </div> </div> <p> The process of rebuilding a database consists of dumping its contents into a large log file, or log files, and doing a roll forward from an empty database with that log. </p> <p> The general steps to rebuild a database are as follows: </p> <div class="important" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Important"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Important]" src="images/important.png" /> </td> <th align="left">Important</th> </tr> <tr> <td align="left" valign="top"> <p> It is recommended that you take a backup copy of the database file(s) prior to performing this procedure. </p> </td> </tr> </table> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>Shut down the running server, making a checkpoint. This is done with the SHUTDOWN command from interactive SQL.</p> </li> <li class="listitem"> <p>Make sure there is a log file specified in virtuoso.ini.</p> </li> <li class="listitem"> <p>Start the server process virtuoso with the -b command line option: e.g. % ./virtuoso -b (+backup-dump)</p> <p>This will write the contents of the database into the log file specified in virtuoso.ini and exit when complete.</p> </li> <li class="listitem"> <p>Take a backup of the old database file.</p> </li> <li class="listitem"> <p>Change the DatabaseFile setting in virtuoso.ini to a non-existing database file or delete the old database file.</p> </li> <li class="listitem"> <p>Start the server with the +restore-crash-dump option. The option is essential.</p> <p>Important: When restore on v6 you also must give it +log6 flag i.e.: +restore-crash-dump +log6 .</p> <p> </p> <div class="tip" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Tip: See Also:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Tip]" src="images/tip.png" /> </td> <th align="left">See Also:</th> </tr> <tr> <td align="left" valign="top"> <p> <a class="ulink" href="" target="_top">How can I move a Virtuoso database from one hardware and/or software platform to another?</a> </p> </td> </tr> </table> </div> <p> </p> </li> <li class="listitem"> <p>The server will build a new database file from the log and once completed it will, by default, perform a checkpoint of the transactions to the database file and start listening at the specified port. Virtuoso can be started without a checkpoint using the -n (+no-checkpoint) option.</p> </li> <li class="listitem"> <p>You may then connect to the database with interactive SQL and if necessary make a checkpoint. The checkpoint will write freeze the state following roll forward and delete the log used for the rebuild.</p> </li> <li class="listitem"> <p>The database is now ready for normal use.</p> </li> </ul> </div> <p> It may sometimes be useful to rebuild a database as above to save space. Virtuoso does not relinquish space in the DB file back to the file system as records are removed, however, Virtuoso does reuse pages that are made available from a deletion of records. The steps above will build a new compact database file. You would ordinarily not have to worry about this. </p> </div> <div> <span class="permalink"><a id="diagnosingrepairing" onclick="javascript:permalink(this)" href="#diagnosingrepairing">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Diagnosing and Recovering a Damaged Database File</h5> </div> </div> </div> <p> It is possible to recover data from a damaged Virtuoso database by a procedure similar to rebuilding a database as described above. A database file may be corrupt if the database repeatedly crashes during a specific operation. </p> <p> To determine whether a database is corrupt, you may use the backup to a null file command in isql, for Unix platforms: </p> <pre class="programlisting"> SQL> backup '/dev/null'; </pre> <p>For windows platforms you can use:</p> <pre class="programlisting"> SQL> backup 'NUL'; </pre> <p>This command will read through the database checking its integrity. If the server crashes before completing the backup process, then the database is indeed corrupt and needs to be recovered. No other activity should take place while the command is executing. </p> <p> To recover the database, follow the procedure for rebuilding it, except use the -D 'capital D' or +crash-dump switch instead of -b. This will construct a log file which you can replay to make a new database. The database will contain the transactions that were committed as of the last successful checkpoint. If the database altogether fails to open it may be the case that the schema is damaged. </p> <p> It is possible that the database to be recovered is too large to fit in a single log file. The crash dump feature therefore allows segmenting the recovery log into a number of files. See the virtuoso.ini configuration file documentation for details. It is possible to make a crash dump in several pieces if there is not enough total disk space to hold the dump on the system where the database is running. </p> <p> If the recovery log is split over several files it is necessary to set the transaction file in the ini to point to the first of these files, delete the database file(s) and start the server with the +restore-crash-dump option. When the server comes online, one can connect to it with isql and use the replay () function for replaying the remaining logs, one by one, in their original order. </p> <p> For example,assuming the virtuoso.ini fragment: </p> <pre class="programlisting"> Log1 = rec-1.log 100M Log2 = rec-2.log 100M </pre> <p> we would make the dump with </p> <pre class="programlisting"> virtuoso +crash-dump </pre> <p> and once the server has been started with +restore-crash-dump, with the ini setting TransactionFile set to rec1.log, replay the remaining log with the isql commands: </p> <pre class="programlisting"> SQL> replay ('rec-2.log'); Done. SQL> checkpoint; </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p>If the recovery is interrupted it can be restarted at the last checkpoint made during the recovery. Note that a mid recovery checkpoint may take a very long time, e.g. 1 hour for a 10GB database, since it is possible that the delta since the previous recovery checkpoint comprise almost all the database. </p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="xcrashrecovery" onclick="javascript:permalink(this)" href="#xcrashrecovery">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Crash Recovery When The Normal Crash Recovery Fails</h5> </div> </div> </div> <p> When the schema tables (e.g. DB.DBA.SYS_COLS, DB.DBA.SYS_KEYS) have corrupt rows the normal crash dump/crash restore procedure will not be possible because the server relies on the schema tables to know the key layouts for reading the data rows of other tables upon crash dump.</p> <p>In such situations there is a special procedure to be followed to save as much data as possible from the corrupt database. The general steps are:</p> <table border="0" summary="Simple list" class="simplelist"> <tr> <td>dump the intact schema table rows, and read them into a fresh database</td> </tr> <tr> <td>read the schema from the fresh database in the normal way</td> </tr> <tr> <td>proceed with dumping the rest of the tables from the corrupt database</td> </tr> </table> <p>Thus the transaction log produced from the corrupt database, when replayed on the new database file (the one holding the schema tables data) makes the closest approximation to the corrupt database's data. However, this will not produce a workable database by itself - it may possibly deny inserting of data into tables with IDENTITY columns and will lose all the data within the Virtuoso registry (accessible from <code class="function">registry_get()</code> /<code class="function">registry_set()</code> functions).</p> <p>Because of the very nature of the crash-restore process described here and because of the fact that data is lost in the database schema, the server will not attempt to dump tables whose schema description is lost. So care should be taken when reading the data from the database.</p> <p>This restoration procedure in no way replaces the regular database backup procedures, it merely tries to save whatever reasonable data there may be left from the database file.</p> <p> The recovery sequence is as follows: </p> <div class="orderedlist"> <ol class="orderedlist" type="1"> <li class="listitem"> <p> Do a crash dump of the schema tables (using the '<code class="computeroutput">+crash-dump +mode oa +dumpkeys schema</code> ' virtuoso command line options). </p> </li> <li class="listitem"> <p> Create a new INI file to describe the layout of the new database you'll use to temporarily fill up the restored data. </p> </li> <li class="listitem"> <p> Move the transaction log file(s) produced in step 1 to the location required by the new INI file. </p> </li> <li class="listitem"> <p> Replay the transaction log from step 1 on an empty database using the new INI file. You will now have the schema tables readable in the new database (and nothing else):</p> <pre class="programlisting"> Virtuoso options : -c <your new ini file> +restore-crash-dump -f </pre> </li> <li class="listitem"> <p> Make a crashdump of the data in the non-schema tables of the old database while having read the schema tables from the new database: </p> <pre class="programlisting"> +crash-dump -c <your new ini file> +crash-dump-data-ini <your old ini file> +mode o -f </pre> </li> <li class="listitem"> <p> Move the transaction log file(s) produced in step 1 to the location required by the new INI file. </p> </li> <li class="listitem"> <p> Replay the transaction log from the previous step into the new db file using: </p> <pre class="programlisting"> -c <your new ini file> +restore-crash-dump </pre> </li> <li class="listitem"> <p> Do a normal crash dump of the new database:</p> <pre class="programlisting"> -c <your new ini file> +crash-dump </pre> </li> <li class="listitem"> <p> Move away (backup) the original (old) database files and put the transaction log produced by the above step into the location specified in the original INI file. You can also delete the rest of the DB files of the new database at that point.</p> </li> <li class="listitem"> <p> Replay the transaction log to make the old database afresh. </p> </li> </ol> </div> <p> To automate the above procedure, a sample Unix script follows that automates it somewhat. This script expects the crashed database virtuoso.db.save and an appropriate INI file (no striping, no log segmentation, transaction log file name virtuoso.trx) in the current directory and creates the restored database. It also expects the virtuoso-iodbc-t executable to be in the operating system path. Also, make sure that you have a suitable <code class="computeroutput">virtuoso.lic</code> license file in the current directory. </p> <pre class="programlisting"> #!/bin/sh rm -rf xmemdump.txt virtuoso.trx virtuoso.tdb virtuoso.log virtuoso.db virtuoso.lck core.* new.lck new.log new.trx new.tdb new.db new.ini cp -f virtuoso.db.save virtuoso.db cat virtuoso.ini | sed 's/virtuoso\./new./g' > new.ini virtuoso-iodbc-t -f +crash-dump +mode oa +dumpkeys schema ls -la *.trx mv virtuoso.trx new.trx virtuoso-iodbc-t -c new -f -R virtuoso-iodbc-t -c new +crash-dump +crash-dump-data-ini virtuoso.ini +mode o -f ls -la *.trx mv virtuoso.trx new.trx virtuoso-iodbc-t -c new -R -f virtuoso-iodbc-t -c new +crash-dump -f rm -f virtuoso.trx virtuoso.tdb virtuoso.log virtuoso.db virtuoso.lck ls -la *.trx mv new.trx virtuoso.trx virtuoso-iodbc-t -R -f </pre> </div> <div> <span class="permalink"><a id="xversionrecovery" onclick="javascript:permalink(this)" href="#xversionrecovery">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Crash Recovery Across Virtuoso VDBMS Server Versions</h5> </div> </div> </div> <p> If the database was created with a version prior to the one being used for rebuilding, the system tables may be different. The creation here refers to the first time the database was made, a crash recovery does not count as a fresh start here. </p> <p> If this is or may be the case, the first log must be rolled forward into the empty database BEFORE the new and possibly incompatible system tables are created. This is done by setting the TransactionFile parameter to the first of the recovery logs and starting the server with the -R or +restore-crash-dump switch. For good practice one should also specify the no checkpoint switch, so that the log will in no case be damaged after the initial step of the roll forward. After this initial step the system tables will be compatible and the dba can proceed to replay the remaining recovery logs with the replay function. </p> </div> <div> <span class="permalink"><a id="procindexrecov" onclick="javascript:permalink(this)" href="#procindexrecov">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Backup and Restore individual table(s) and individual index(s) on a new fresh db</h5> </div> </div> </div> <p>This section describes how to get a part of db tables and restore on a new db.</p> <p>Additionally, part of the steps from below can be used to backup separate table and recover on same db.</p> <p>Note: Only effective with Virtuoso 6.0 and later.</p> <p>Basic steps:</p> <div class="orderedlist"> <ol class="orderedlist" type="1"> <li class="listitem"> <p>Create a function for dumping the key: </p> <pre class="programlisting"> 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 (); } ; </pre> </li> <li class="listitem"> <p>On the source db execute: </p> <pre class="programlisting"> bkp_key ('mylog.txn', 'DB.DBA.T1', 'T1'); </pre> <p>This will dump in a "mylog.txn" file the T1 table's primary key.</p> </li> <li class="listitem"> <p>On source db stop server and do: </p> <pre class="programlisting"> virtuoso +backup-dump +foreground +mode l ## ( lower case L ) </pre> <p>This will dump the schema tables only into the trx file.</p> </li> <li class="listitem"> <p>On the target db make sure there is no db file and place the trx file produced by previous step. Execute: </p> <pre class="programlisting"> virtuoso +restore-crash-dump +foreground ; </pre> <p>This will create a new db with same db schema as on the source db.</p> </li> <li class="listitem"> <p>Start the target and do: </p> <pre class="programlisting"> replay ('mylog.txn') ; </pre> <p>This will insert the PK data into the table from the source db dump.</p> </li> <li class="listitem"> <p>If the table in question has other indexes must drop them and re-create them, since they are empty as in previous step we have been restoring only the PK. </p> </li> </ol> </div> <p> <span class="emphasis"><em>Note</em> </span> : following the steps from above can be dumped each index and then replay. Also the steps may be combined for multiple tables and keys in the backup procedure - just needs to be added the corresponding calls to the backup_index() function.</p> </div> </div> </div> <div> <span class="permalink"><a id="perfdiag" onclick="javascript:permalink(this)" href="#perfdiag">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.6.聽Performance diagnostics</h3> </div> </div> </div> <p>This section provides a checklist for improving performance of a Virtuoso server.</p> <p>If something does not work fast, this is mostly for the following reasons:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Not enough memory</p> </li> <li class="listitem"> <p>Not the right indices, missing statistics</p> </li> <li class="listitem"> <p>Too much locking or too many threads on the same data</p> </li> <li class="listitem"> <p>Bad disk layout, for example not striped or not enough file descriptors.</p> </li> </ul> </div> <p>Determining which is the case is simple. The result set returned by status ('') has most of the information. Do this twice with some 10 seconds between the samples and see the second result set. </p> <div> <span class="permalink"><a id="perfdiagmemory" onclick="javascript:permalink(this)" href="#perfdiagmemory">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Memory</h4> </div> </div> </div> <p>If there is not enough memory, there will be frequent disk access. This is seen from the buffers and disk usage lines. </p> <p>The very simplest test for this is looking at the CPU % of the process in top. If there is constant load and the percent is low then the server is IO bound. </p> <p>If all memory is not in use, then memory cannot be the problem. This is seen from the buffers line. If the used number is under 80% of the total or if the replace age is several times larger than the count of buffers, then things are OK. If the replace age is 0 then no buffers have ever been replaced and all that ever was read is still in memory. </p> <p>If the replace age is less than or close to the buffer count times 4, then cache replacement is frequent and adding buffers is advised. </p> <p>Adding more than 60-70% of system ram as buffers is not useful. The setting is NumberOfBuffers in the ini file, count 9K per buffer. </p> <p>The disk access is summarized on the disk usage line. First is the number of reads since start then the average latency in N ms. If %r is high, then a lot of the time between the previous status and this is taken by disk. This can be over 100. One thread that is waiting for disk all the time counts for 100. If the percent is high then adding more disks and striping over them will be useful. Even with a single database file, adding file descriptors (FDsPerFile setting in the ini) may be useful. If the average read latency is 0 or close, then the data is cached by the OS. If it is high, then adding disks and striping may reduce it. </p> <p>The read ahead line will tell if there are sequential reads. These are faster than random ones and can efficiently use striped disks. </p> <p>If the workload is random access, then a high number of read ahead means that one might not have the required indices, thereby causing full table scans. More on this in the query plans section below. </p> </div> <div> <span class="permalink"><a id="perfdiagswapping" onclick="javascript:permalink(this)" href="#perfdiagswapping">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Swapping</h4> </div> </div> </div> <p>Swapping is always bad. If swapping occurs, then one has too many buffers and should decrease the number of buffers. Use an OS tool like top to see the size of the database process and its virtual memory use. Having a resident size smaller than logical size is not always bad since some code or data in the process may simply be unused but having, after running in a steady state, i.e. all buffers used, a resident size less than the amount of memory allocated for buffers is always bad. Before steady state, i.e. during cache warm-up, the resident size is normally less than the buffer pool's size. </p> <p> To see the count of major page faults. i.e. ones that read the disk, do: </p> <pre class="programlisting"> getrusage ()[]4]; </pre> <p>through interactive SQL. The result is the count of major faults since starting the process. The count should not vary between samples, at least not more than a few units per minute. </p> <p>This function is not available under Windows. Use the task manager instead for tracking this.</p> <p>There can be an actual memory leak, specially with plugins or hosting. See the growth of the virtual size throughout the run, reaching full buffer utilization and doing a couple of checkpoints. Past this, the process should not grow. You may also see if the ThreadCleanupInterval or ResourcesCleanupInterval ini parameters have an effect. If in spite of all the process grows there can be a genuine leak. It is normal for the size to fluctuate somewhat due to varying amounts of uncommitted data, threads, connections and the like. </p> </div> <div> <span class="permalink"><a id="perfdiaglocking" onclick="javascript:permalink(this)" href="#perfdiaglocking">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Locking</h4> </div> </div> </div> <p>The lock status section indicates the count of deadlocks and waits. If the 2r1w number is high then it means that the application should read for update. It gets shared locks and cannot change them to exclusive. Adding the for update option to selects in the right place will fix this, also setting DefaultIsolation in the ini to 2 for read committed will be good. If the lock wait count increases fast, then locking may downgrade performance. The threads line below shows how many threads have some task to do. The waiting is the number of these threads that are waiting for a lock at the time of the status. The vdb number is the number of threads waiting for network io, either from virtual database or any web protocol. </p> <p>Take a few samples and if these show few threads waiting and the waits or deadlocks counts do not climb much locking will not be a problem. If these numbers are high, see the sys_l_stat view for details. </p> <pre class="programlisting"> select sum (waits), sum (wait_msecs) from sys_l_stat; </pre> <p>for the totals. The first number is the count of times a thread waited for a lock, the second is the sum of the real times spent waiting. </p> <pre class="programlisting"> select top 10 * from sys_l_stat order by waits desc; </pre> <p>shows the keys on which most waits take place. See also the deadlocks and the wait_msecs columns. Numbers are cumulative. </p> <p>For details on disk, see:</p> <pre class="programlisting"> select top 10 * from sys_d_stat order by reads desc; </pre> <p>These views are explained in more detail in the performance meters section.</p> <p>If there is a multi-user application doing random access for read or write, it is an idea to partition the data so that they do not hit the same page all the time. For example, to allow for parallel insert of orders without contention, the TPC C schema prefixes the order number with a warehouse and district number, so that simultaneous inserts will most often not hit the same page. </p> <p>Even when there is no locking, there is still some serialization for database page access. This is shown in the various wait columns of SYS_L_STAT. If the sum of the waits for a key is over 1% of the touches for the key, as given in SYS_D_STAT, there is contention and a performance penalty of maybe 10%. </p> <p>Such things can be improved by altering the schema design and configuration parameters do not usually help. If there is disk access, having more memory always helps because then locks will be in effect for less time. </p> </div> <div> <span class="permalink"><a id="perfdiagqueryplans" onclick="javascript:permalink(this)" href="#perfdiagqueryplans">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Query Plans</h4> </div> </div> </div> <p>To know if there is a bad query plan, see the explain output of the query.</p> <p>Unless a full table scan is intended, a full table scan is pretty much always bad.</p> <p>In the explain () result set, a table access is marked by a From table name. Below is mentioned the driving index, the conditions on the index and the conditions that are not indexable. </p> <p>Joins are listed one after the other, the outermost first. The join order can be read from the explain output going from top to bottom. </p> <p>If a table is read on a non primary key and columns not covered by the driving index are accessed, there is a second key mentioned with a full match of the primary key columns as condition. </p> <p>A full table scan looks like this:</p> <pre class="programlisting"> explain (select count (*) from t1'); ... from DB.DBA.T1 by STR2 8.4e+04 rows Key STR2 ASC () Local Code 0: $30 "count" := artm $30 "count" + <constant (1)> ... </pre> <p>There are no conditions mentioned.</p> <p>A lookup with index looks like this.</p> <pre class="programlisting"> explain ('select fi2 from t1 where row_no = 11'); ... from DB.DBA.T1 by T1 Unique Key T1 ASC ($26 ".FI2") inlined <col=1694 ROW_NO = <constant (11)>> ... </pre> <p>The condition is shown on the line below the key.</p> <p>A lookup with full scan testing every row looks like this:</p> <pre class="programlisting"> ... from DB.DBA.T1 by T1 2.5e+04 rows Key T1 ASC ($26 ".FI2") row specs: <col=1699 FI2 > <constant (11)>> ... </pre> <p>The condition is shown after the heading row specs. The whole key mentioned in the key will be read and the entries tested. if both indexed and row tests exist, the indexed are done first as one would think. </p> <p>If your query has full table scans, consider adding an index.</p> <p>If the index choice is not the right one, consider the following possibilities:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>Run statistics. This is not always necessary because the database takes dynamic samples but it can help in cases.</p> </li> <li class="listitem"> <p>specify the desired index explicitly with table option.</p> </li> <li class="listitem"> <p>Use literal constants instead of parameters, specially if the query is long running and values of the columns being compared are not evenly distributed.</p> </li> <li class="listitem"> <p>To exclude index usage for a column, write col + 0 =xx.</p> </li> </ul> </div> <p>Hash joins can make full table scans. This is OK if the table scanned is small.</p> <p>A hash join looks like this:</p> <pre class="programlisting"> explain ('select count (*) from t1 a, t1 b where a.row_no = b.row_no + 1'); ... { Fork { Fork { from DB.DBA.T1 by STR2 8.4e+04 rows Key STR2 ASC ($26 "B.ROW_NO") Local Code 0: $30 "temp" := artm $26 "B.ROW_NO" + <constant (1)> 4: BReturn 0 Current of: <$28 "<DB.DBA.T1 B>" spec 5> Sort (HASH) ($30 "temp") -> ($26 "B.ROW_NO") } from DB.DBA.T1 by STR2 8.4e+04 rows Key STR2 ASC ($37 "A.ROW_NO") Current of: <$39 "<DB.DBA.T1 A>" spec 5> Hash source ($37 "A.ROW_NO") -> ($26 "B.ROW_NO") After code: 0: $44 "count" := artm $44 "count" + <constant (1)> 4: BReturn 0 } Select ($44 "count", <$39 "<DB.DBA.T1 A>" spec 5>, <$28 "<DB.DBA.T1 B>" spec 5>) } </pre> <p>First t1 is read from start to end and a hash is filled with row_no + 1. Then t1 is read from start to end a second time. The hash source is the hash lookup. A hash join, if there is no index or if the whole table or a large part thereof is traversed is better than a loop join because it replaces random access with sequential. The complexity is close to O(n + n) instead of O (n * log n). Plus sequential read makes better use of read ahead. </p> <p>The corresponding loop join looks like this:</p> <pre class="programlisting"> explain ('select count (*) from t1 a, t1 b where a.row_no = b.row_no + 1 option (loop)'); { Fork { from DB.DBA.T1 by STR2 8.4e+04 rows Key STR2 ASC ($26 "B.ROW_NO") Current of: <$28 "<DB.DBA.T1 B>" spec 5> Precode: 0: $29 "temp" := artm $26 "B.ROW_NO" + <constant (1)> 4: BReturn 0 from DB.DBA.T1 by T1 Unique Key T1 ASC () inlined <col=1694 ROW_NO = $29 "temp"> Local Code 0: $35 "count" := artm $35 "count" + <constant (1)> 4: BReturn 0 Current of: <$31 "<DB.DBA.T1 A>" spec 4> } Select ($35 "count", <$31 "<DB.DBA.T1 A>" spec 4>, <$28 "<DB.DBA.T1 B>" spec 5>) } </pre> <p>To prevent hash joins, use table option or option at the end of the select as seen above. A hash join is very bad if a whole table is read for filling a hash and then only a small number of entries are fetched from the hash. However, if there is no index, then even this is better than a loop join. </p> </div> <div> <span class="permalink"><a id="perfdiagcheckpointduration" onclick="javascript:permalink(this)" href="#perfdiagcheckpointduration">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Checkpoint Duration</h4> </div> </div> </div> <p>A checkpoint can take a very long time in certain special conditions. Normally a log checkpoint is about a minute if flushing several G worth of buffers to disk. The flushing is mostly done online, after which there is an atomic time of a few seconds. After this operation resumes. Applications do not notice the checkpoint except as a temporary increase in response delays. </p> <p>If spikes in response time are to be avoided, then making frequent checkpoints is better than making infrequent ones. </p> <p>If there are long running transactions with many locks or uncommitted changes, then the checkpoint interval should anyhow be longer than several times the expected duration of such a transaction. If this is not so, the checkpoint can fall in the middle of the transaction and will internally have to rollback and again reestablish the uncommitted state so as to write a clean image on the new checkpoint. Doing this many times in the life of a transaction is very inefficient. In generally do not make long transactions with locking. Preferentially use read committed for anything long. </p> <p>A checkpoint's atomic time can be prohibitively long under the following circumstances:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>There are transactions with a lot of locks and uncommitted state at the time of the checkpoint. Specially a transaction which has updated pages paged out to disk is bad. In general one should not do transactions that update a large part of the disk cache, let alone exceed its size. Use the row autocommit mode (log_enable (2)) for doing batch updates. Batch updates most often do not require isolation anyway. If they do, then break the job into smaller transactions. </p> </li> <li class="listitem"> <p>The MaxCheckpointRemap parameter in the ini is too small and the database exceeds the size of disk cache either in the Virtuoso process or the OS. This may increase the count of used pages by the value of this parameter but will make for faster checkpoints. Set this to up to 25% of the database page count. </p> </li> </ul> </div> </div> </div> <div> <span class="permalink"><a id="ptune" onclick="javascript:permalink(this)" href="#ptune">露</a> </span> <div class="titlepage"> <div> <div> <h3 class="title">6.1.7.聽Performance Tuning</h3> </div> </div> </div> <div> <span class="permalink"><a id="io" onclick="javascript:permalink(this)" href="#io">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">I/O</h4> </div> </div> </div> <div> <span class="permalink"><a id="diskio" onclick="javascript:permalink(this)" href="#diskio">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Optimizing Disk I/O</h5> </div> </div> </div> <p> Virtuoso allows splitting a database over several files that may be on different devices. By allocating database fragments onto independent disks I/O performance in both random and sequential database operations can be greatly enhanced. </p> <p> The basic unit of a database is the segment. A segment consists of an integer number of 8K pages. A segment may consist of one or more files called stripes. If a segment has multiple stripes these will be of identical length and the segment size will be an integer multiple of the stripe size. </p> <p> The size limit on individual database files is platform dependent, but 64 bit file offsets are used where available. For large databases use of multiple disks and segments is recommended for reasons of parallelism even though a single database file can get very large. A database can in principle grow up to 32TB (32-bit page number with 8KB per page). </p> <p> When a segment is striped each logically consecutive page resides in a different file, thus for a segment of 2 stripes the first stripe will contain all even numbered pages and the second all the odd numbered pages. The stripes of a segment should always be located on independent disks. </p> <p> In serving multiple clients that do random access to tables the server can perform multiple disk operations in parallel, taking advantage of the independent devices. Striping guarantees a statistically uniform access frequency to all devices holding stripes of a segment. </p> <p> The random access advantages of striping are available without any specific configuring besides that of the stripes themselves. </p> </div> <div> <span class="permalink"><a id="ioqs" onclick="javascript:permalink(this)" href="#ioqs">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Configuring I/O queues</h5> </div> </div> </div> <p> Striping is also useful for a single client doing long sequential read operations. The server can detect the serial nature of an operation, for example a count of all rows in a table and can intelligently prefetch rows. </p> <p> If the table is located in a striped segment then the server will read all relevant disks in parallel if these disks are allocated to different I/O queues. </p> <p> All stripes of different segments on one device should form an I/O queue. The idea is that the database stripes that benefit from being sequentially read form a separate queue. All queues are then read and written independently, each on a different thread. This means that a thread will be allocated per queue. If no queues are declared all database files, even if located on different disks share one queue. </p> <p> A queue is declared in the striping section by specifying a stripe id after the path of the file, separated by an equal sign. </p> <pre class="programlisting"> [Striping] Segment1 = 200M, disk1/db-seg1-1.db = iq1, disk2/db-seg1-2.db = iq2 Segment2 = 200M, disk1/db-seg2-1.db = iq1, (disk2/db-seg2-2.db = iq2 </pre> <p> In the above example the first stripes of the segments form one queue and the second stripes form another. This makes sense because now all database files on /disk1 are in iq1 and all on /disk2 are on iq2. </p> <p> This configuration could have resulted from originally planning a 200 MB database split on 2 disks and subsequently expanding that by another 200 MB. </p> <p> The I/O queue identifier can be an arbitrary string. As many background I/O threads will be made as there are distinct I/O queues. </p> <p> Striping and using I/O queues can multiply sequential read rates by a factor almost equal to the number of independent disks. On the other hand assigning stripes on one disk to different queues can have a very detrimental effect. The rule is that all that is physically accessed sequentially will be on the same queue. </p> </div> </div> <div> <span class="permalink"><a id="schemas" onclick="javascript:permalink(this)" href="#schemas">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Schema Design Considerations</h4> </div> </div> </div> <div> <span class="permalink"><a id="dataorg" onclick="javascript:permalink(this)" href="#dataorg">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Data Organization</h5> </div> </div> </div> <p> One should keep the following in mind when designing a schema for maximum efficiency. </p> </div> <div> <span class="permalink"><a id="indexusage_01" onclick="javascript:permalink(this)" href="#indexusage_01">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Index Usage</h5> </div> </div> </div> <p> A select from a table using a non-primary key will need to retrieve the main row if there are search criteria on columns appearing on the main row or output columns that have to be fetched from the main row. Operations are noticeably faster if they can be completed without fetching the main row if the driving key is a non-primary key. This is the case when search criteria and output columns are on the secondary key parts or primary key parts. Note that all secondary keys contain a copy of the primary key. For this purpose it may be useful to add trailing key parts to a secondary key. Indeed, a secondary key can hold all the columns of a row as trailing key parts. This slows insert and update but makes reference to the main row unnecessary when selecting using the secondary key. </p> <p> A sequential read on the primary key is always fastest. A sequential search with few hits can be faster on a secondary key if the criterion can be evaluated without reference to the main row. This is because a short key can have more entries per page. </p> </div> <div> <span class="permalink"><a id="spaceconsump" onclick="javascript:permalink(this)" href="#spaceconsump">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Space Consumption</h5> </div> </div> </div> <p> Each column takes the space 'naturally' required by its value. No field lengths are preallocated. Space consumption for columns is the following: </p> <div class="decimalstyle" id="id13084"> <p class="title"> <strong>Table聽6.2.聽Data type Space Consumption</strong> </p> <div class="decimalstyle-contents"> <table summary="Data type Space Consumption" border="1"> <colgroup> <col width="20pc" align="left" /> <col /> </colgroup> <thead> <tr> <th align="left" char="." charoff="50">Data</th> <th align="char" char="." charoff="50">Bytes</th> </tr> </thead> <tbody> <tr> <td align="left" char="." charoff="50">Integer below 128</td> <td align="char" char="." charoff="50">1</td> </tr> <tr> <td align="left" char="." charoff="50">Smallint</td> <td align="char" char="." charoff="50">2</td> </tr> <tr> <td align="left" char="." charoff="50">long</td> <td align="char" char="." charoff="50">4</td> </tr> <tr> <td align="left" char="." charoff="50">float</td> <td align="char" char="." charoff="50">4</td> </tr> <tr> <td align="left" char="." charoff="50">timestamp</td> <td align="char" char="." charoff="50">10</td> </tr> <tr> <td align="left" char="." charoff="50">double</td> <td align="char" char="." charoff="50">8</td> </tr> <tr> <td align="left" char="." charoff="50">string</td> <td align="char" char="." charoff="50">2 + characters</td> </tr> <tr> <td align="left" char="." charoff="50">NULL</td> <td align="char" char="." charoff="50">data length for fixed length column, as value of 0 length for variable length column. </td> </tr> <tr> <td align="left" char="." charoff="50">BLOB</td> <td align="char" char="." charoff="50">88 on row + n x 8K (see note below)</td> </tr> </tbody> </table> </div> </div> <br class="decimalstyle-break" /> <p> If a BLOB fits in the remaining free bytes on a row after non-LOBs are stored, it is stored inline and consumes only 3 bytes + BLOB length. </p> <p> Each index entry has an overhead of 4 bytes. This applies to the primary key as well as any other keys. The length of the concatenation of the key parts is added to this. For the primary key the length of all columns are summed. For any other key the lengths of the key parts plus any primary key parts not on the secondary key are summed. The maximum length of a row is 4076 bytes. </p> <p> In light of these points primary keys should generally be short. </p> </div> <div> <span class="permalink"><a id="pagealloc" onclick="javascript:permalink(this)" href="#pagealloc">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Page Allocation</h5> </div> </div> </div> <p> For data inserted in random order pages tend to be 3/4 full. For data inserted in ascending order pages will be about 90% full due to a different splitting point for a history of rising inserts. </p> </div> </div> <div> <span class="permalink"><a id="efficientsql" onclick="javascript:permalink(this)" href="#efficientsql">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Efficient Use of SQL - SQL Execution profiling</h4> </div> </div> </div> <p> Virtuoso offers an execution profiling mechanism that keeps track of the relative time consumption and response times of different SQL statements. </p> <p> Profiling can be turned on or off with the prof_enable function. When profiling is on, the real time between the start and end of each SQL statement execute call is logged on the server. When prof_enable is called for the second time the statistics gathered between the last call to prof_enable and this call are dumped to the virtprof.out file in the server's working directory. </p> <p> Profiling is off by default. Profiling can be turned on with the statement: </p> <pre class="programlisting"> prof_enable (1); </pre> <p> The virtprof.out file will be generated when prof_enable is called for the second time, e.g. </p> <pre class="programlisting"> prof_enable (0); </pre> <p> will write the file and turn profiling back off. </p> <p> Below is a sample profile output file: </p> <pre class="screen"> Query Profile (msec) Real 183685, client wait 2099294, avg conc 11.428772 n_execs 26148 avg exec 80 99 % under 1 s 99 % under 2 s 99 % under 5 s 100 % under 10 s 100 % under 30 s 23 stmts compiled 26 msec, 99 % prepared reused. % total n-times n-errors 49 % 1041791 7952 53 new_order 28 % 602789 8374 490 delivery_1 12 % 259833 8203 296 payment 5 % 123162 821 35 slevel 2 % 54182 785 0 ostat (?, ?, ?, ?) 0 % 11614 4 0 checkpoint 0 % 2790 2 1 select no_d_id, count (*) from new_orde 0 % 2457 3 1 select count (*) from new_order 0 % 662 2 0 status () 0 % 11 1 1 set autocommit on 0 % 3 1 0 select * from district </pre> <p> This file was produced by profiling the TPC C sample application for 3 minutes. The numbers have the following meanings: </p> <p> The real time is the real time interval of the measurement, that is the space in time between the prof_enable call that started the profiling and the call that wrote the report. The client wait time is the time cumulatively spent inside the execute call server side, only calls completely processed between profiling start and end are counted. The average concurrency is the exec time divided by real time and indicates how many requests were on the average concurrently pending during the measurement interval. The count of executes and their average duration is also shown. </p> <p> The next section shows the percentage of executes that finished under 1, 2, 5, 10 and 30 seconds of real time. </p> <p> The compilation section indicates how many statements were compiled during the interval. These will be SQLPrepare calls or SQLExecDirect calls where the text of the statement was not previously known to the server. The real time spent compiling the statements is added up. The percentage of prepared statement reuses, that is, executes not involving compiling over all executes is shown. This is an important performance metric, considering that it is always better to use prepared statements with parameters than statements with parameters as literals. </p> <p> The next section shows individual statements executed during the measurement interval sorted by descending cumulative real time between start and completion of the execute call. </p> <p> The table shows the percentage of real time spent during the calls to the statement as a percentage of the total real time spent in all execute calls. Note that these real times can be higher than the measurement interval since real times on all threads are added up. </p> <p> The second column shows the total execute real time, the third column shows the count of executes of the statement during the measurement interval. The fourth column is the count of executes that resulted in an error. The error count can be used for instance to spot statements that often produce deadlocks. </p> <p> Statements are distinguished for profiling purposes using the 40 first characters of their text. Two distinct statements that do not differ in their first 40 characters will be considered the same for profiling. If a statement is a procedure call then only the name of the procedure will be considered, not possibly differing literal parameters. </p> <p> The profiler will automatically write the report after having 10000 distinct statements in the measurement interval. This is done so as to have a maximum on the profiling memory consumption for applications that always compile a new statement with different literals, resulting in a potentially infinitely long list of statements each executed once. It is obvious that such a profile will not be very useful. </p> <p> It cannot be overemphasized that if an application does any sort of repetitive processing then this should be done with prepared statements and parameters, for both reasons of performance and profilability. </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <table border="0" summary="Note: Note:"> <tr> <td rowspan="2" align="center" valign="top" width="25"><img loading="lazy" alt="[Note]" src="images/note.png" /> </td> <th align="left">Note:</th> </tr> <tr> <td align="left" valign="top"> <p> Note that measurements are made with a one millisecond precision. Percentages are rounded to 2 digits. Timing of fast operations, under a few milliseconds, will be imprecise as a result of the 1 ms resolution. Also the cumulative compilation time may be substantially off, since the compilation may often take less than 1 ms at a time. Also note that the precision may also vary between platforms. </p> </td> </tr> </table> </div> </div> <div> <span class="permalink"><a id="readingqueryprofile" onclick="javascript:permalink(this)" href="#readingqueryprofile">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Reading a Query profile</h4> </div> </div> </div> <p>A query plan is essentially a pipeline of operations that can be read from top to bottom. The operator above produces the input for the operator below. Nesting is indicated by braces. Operators enclosed in braces must completely process their input before continuing with operators after the section in braces. A case in point is aggregation which is demoted by for { ... } ... . The section in braces generates the rows to be aggregated and one it is fully evaluated the execution proceeds with the operators after the fork. These will typically read the temporary table filled by the operators inside the fork.</p> <p>Query variables are demoted with <$v...>. A reference to a query variable set by an operator that is not immediately the preceding one is demoted by <r $...> via ...>. The position of the variable in the query state follows the $ sign.</p> <p>After this is given the symbolic name of the variable, e.g. a column name or the name of the function of which this is the return value.</p> <p>If this is a reference to a query variable assigned earlier in the plan with one or more operators between the reference and the assignment, the reference contains a via .... section which lists the operators that are between the reference and the assignment.</p> <p>The operators are identified by a unique number. Internally this is the location in the query state where the operator keeps the mapping between its rows of input and output.</p> <p>With vectored execution, an operator may receive any number of rows of input which it may reorder at its convenience. For this it must record for each row of output which row of input this corresponds to. Thus when referencing a query variable set earlier in the plan one must take into account the reordering and addition/dropping of rows in affected by the operators between the reference and the initial assignment. This is the meaning of the via section in the <r $xx > notation.</p> <p>The last part of the query variable reference is a two letter indication of the type. If the first letter is followed by n this means that the variable is non-null. The type letters are a for any, r for IRI, i for integer, d for double, f for float, t for datetime, N for wide string, s for string.</p> <p>If the plan is a profile, i.e. it is annotated with actual times and cardinalities from running the query, each operator is preceded by a passage that indicates its percentage of total CPU time of the plan, its fanout and the number of rows of input. The fanout is the number of rows of Output divided by the number of rows of input.</p> <p>The principal operators in a plan are:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <span class="emphasis"><em>Cluster outer seq start</em></span> </p> <p> -- Queries and subqueries begin with this operator. It assigns numbers to the sets of parameter bindings the query gets as input. An optional section also begins with this. An optional section is the table or derived table on the right hand side of a left outer join. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>From</em></span> </p> <p> -- Accessing an index </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Sort</em></span> </p> <p> -- Group by, order by, distinct or hash join build side </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>group by read</em></span> </p> <p> -- Accessing the results of a group by filled in by a previous sort operator. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Top oby</em></span> </p> <p> -- Accessing a previously filled top k order by temporary space </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Select</em></span> </p> <p> -- At the end of a plan, send the rows of input to the client. If Subq select return the rows of input as rows of output of the enclosing subquery. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Subquery</em></span> </p> <p> -- Indicates a SQL derived table, i.e. select in a from clause. The input is the output of the previous node. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Cluster ocation fragment</em></span> </p> <p> -- A set of operators partitioned and shipped to a partition in a cluster. There are single part fragments and distributed fragments (DFG). A DFG is a query fragment which begins with a stage operator. The stage is a partitioning exchange operator which routes its rows of input to the next operator in the appropriate partition based on the partitioningh columns of the row of input. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>Outer seq end</em></span> </p> <p> -- This demotes the end of an optional section, i.e. the table/derived table on the right side of left outer join. This has the effect of making aligned vectors of all the vector query variables assigned in the optional section. When producing rows for which there was no match in the optional section, these will be set to null. References to these variables downstream in the plan will be to the shadowing variables, listed in the shadow clause following this. </p> </li> </ul> </div> <p>Some operators such as index access (From) have a section called vector param casts. This is used when the vector that serves as parameter is not aligned or not of the type required by the operator. For example, a vector of column values in an index lookup might not be of the type of the column but might be of a type castable to this. In any case, the para,key values for index lookup are made into solid aligned, materialized vectors. After this there is a sort step that orders the input according to key order, so that matches are generated from left to right.</p> <p>In the event of a cluster partitioned operation, i.e. stage node or non-DFG location fragment (QF), the first table source (From) after the stage or fragment serves to both align and cast all inputs needed downstream in the DFG or QF. The operator first partitions the rows of input. Each partition then gets solid, aligned vectors of input values which are directly suitable for input to the first index lookup (From).</p> <p>We consider an example: The setup is a cluster of 4 server processes with each 8 slices of data. There is one table, ct_c, which is joined to itself:</p> <pre class="programlisting"> profile ('SELECT COUNT (*) from ct_c a, ct_c b WHERE a.k2 = b.k1 option (loop, order)'); </pre> <p>This returns a result set in which is found the below. This is also in the ql_plan column of the sys_query_log view:</p> <pre class="programlisting"> { -- In the below excerpt some lines are omitted. Comments are inline. time 1.3e-06% fanout 1 1 rows in s# 98 cluster outer seq start, set no <V $40 set_ctr in> save ctx:() -- the section inside the fork is executed to the end -- before the section after the fork is started. s# 161 Fork 42 { wait time 0.00012% of exec real time, fanout 0 -- The below introduces the 2 stage DFG which does most of the work. s# 108 { Cluster location fragment 51 0 unordered Params: () Output: () -- First partitioning step. Each of the 32 slices gets the -- identical plan to execute, this is a flood for all is this -- first step does not specify a partitioning key value. time 8e-05% fanout 0 0 rows in s# 115 Stage 1: Params: (<V $112 set_ctr in>) -- This is the initial table scan. The operator is executed -- 32 times, once for each slice of data. time 0.33% fanout 3.1e+06 32 rows in s# 121 from DB.DBA.ct_c by ct_c 1.7e+08 rows Key ct_c ASC (<V $28 a.k2 in>) [copies params] vector param casts: <V $40 set_ctr in>-> <V $112 set_ctr in> -- This is the second partitioning step, each of the rows of -- output of the previous is sent to the slice corresponding to K2. time 31% fanout 0.9 2e+08 rows in s# 131 Stage 2: Params: (<v $134 q_a.k2 S136 in>, <V $138 set_ctr in>) -- This is the 2nd index lookup, by a.k2 = b.k1 There are two -- parameters given in the vector param cast section, the first -- is a.k2 and the second is the set number. This is constant -- since the query is run on a single row of input but if the -- query were run on multiple rows of input this would specify -- which row of input the a.k2 comes from so that this would be -- aggregated in the right place. Many aggregates can be produced -- in a single invocation with multiple rows of input. time 68% fanout 0 2e+08 rows in s# 144 from DB.DBA.ct_c by ct_c unq 1 rows Key ct_c ASC () inlined k1 = <v $134 q_a.k2 S136 in> vector param casts: <V $28 a.k2 in>-> <v $134 q_a.k2 S136 in>, <r $112 set_ctr via S121>-> <V $138 set_ctr in> -- This is the aggregation. After code: 0: sum <V $43 count i> 1 set no <r $138 set_ctr via S144> 5: BReturn 0 } } -- The below returns the aggregate to the client. The combining of -- aggregates from different slices is implicit in the for operator -- whenever this ends with a cluster location fragment. time 5.4e-07% fanout 0 1 rows in s# 164 Select (<V $43 count i>) set no: <V $40 set_ctr in> } </pre> </div> <div> <span class="permalink"><a id="tunvectoredexecandhashjoins" onclick="javascript:permalink(this)" href="#tunvectoredexecandhashjoins">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Tuning Vectored Execution and Hash Joins</h4> </div> </div> </div> <p> <span class="emphasis"><em>Note</em> </span> : This section applies only to versions 7.00 and up.</p> <p>Query evaluation performance is significantly affected by parallelization, the vector size and the use of hash joins and fast in-memory hash tables for group by and distinct.</p> <p>This section explains the configuration parameters and event counters that allow optimizing these factors.</p> <p>The SQL function <span class="emphasis"><em>cl_sys_stat</em></span> (in name varchar, in clr int := 0) allows reading and optionally resetting these counters. In the case of a cluster, the value returned is the sum of the values of the metric gathered from all server processes, for a single server this is the local value. In a cluster, to get individual counter values, use sys_stat instead when connected to the process of interest.</p> <p>To do TPC H at scale 100G on a 32 thread machine, the virtuoso.ini should have the following settings. Only settings at non-default values are mentioned:</p> <pre class="programlisting"> [Parameters] ServerThreads = 100 NumberOfBuffers = 5000000 ; The working set of the 100G database when stored column-wise is 38G, ; so configure this much for database buffers: ; 5000000 / 128 = 39G ; Read committed DefaultIsolation = 2 ; SQL optimizer work space MaxMemPoolSize = 100000000 ; Use large vectors when appropriate AdjustVectorSize = 1 ; Split queries in up to 32 independently evaluable fragments, ; so up to 32 threads per query. ThreadsPerQuery = 32 ; Thread pool has 32 worker threads divided across all queries ; in addition to the client thread taken by each query. AsyncQueueMaxThreads = 32 ; All queries can collectively take up to 30G without space ; saving measures being applied. Space saving measures are ; running on small vector size when a large size would be ; faster and the use of partitioned (multiple pass) hash join. MaxQueryMem = 30G ; Of the MaxQueryMem, hash join hash tables can take up to 30G, ; i.e. all of it. A single hash table will only take half of the ; remaining space, though. So if 2 queries that both need a 30G ; hash table run at the same time, the first will do 2 passes, ; taking a hash table of 15G at a time, This leaves 20G space. ; The second will have 15G left, of which it will take half, ; 7.5G. This will require 4 passes over the data. HashJoinSpace = 30G </pre> <p>To analyze the performance of a query workload:</p> <div class="orderedlist"> <ol class="orderedlist" type="1"> <li class="listitem"> <p>Turn on query logging in sys_query_log. This view contains most metrics and the full text of the query plan with the per operator timings and cardinalities: </p> <pre class="programlisting"> SQL> prof_enable (1); </pre> </li> <li class="listitem"> <p> Print long result columns without truncating: </p> <pre class="programlisting"> SQL> set blobs on; </pre> </li> <li class="listitem"> <p>Run the query.</p> </li> <li class="listitem"> <p>Use the profile function for a convenient overview of query execution. For example: </p> <pre class="programlisting"> SQL> profile ('SELECT COUNT (*) FROM orders, lineitem WHERE l_orderkey = o_orderkey'); </pre> <p> <a href="/virtuoso/ch-server/#efficientsql">See summary of execution time, CPU%, compilation time and IO</a> </p> </li> <li class="listitem"> <p>Read the relevant event counters, resetting the count for the next query. For example: </p> <pre class="programlisting"> SQL> select cl_sys_stat ('tc_qp_thread', clr => 1); </pre> <p>The relevant counters are:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <span class="emphasis"><em>tc_qp_thread</em> </span> -- How many threads were started for query parallelization. This is not the number of parallel threads as not all of these threads needed to be running at the same time. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>tc_part_hash_join</em> </span> -- If a hash join is partitioned, i.e. needs to make multiple passes on over the data, this is the count of passes. This is incremented by 2 if the hash join does 2 passes and not incremented if the hash join goes in a single pass. Normally this should stay at 0 or the hash join space (HashJoinSpace in init, see above) should be increased. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>tc_no_mem_for_longer_batch</em> </span> -- This is the count of times the execution engine did not switch to large vectors because there was not enough space. This should normally be 0, if this is not so, increase MaxQueryMem in the ini file.</p> </li> <li class="listitem"> <p> <span class="emphasis"><em>tc_slow_temp_insert</em> </span> -- If a distinct or group by temporary space grows over the available query memory, a another data structure will be used so that the hash table can be paged out to disk. This is tens of times less efficient than the memory only structure. This counter is the count of rows inserted into a page-able group by or distinct hash table. This should be 0, if not, increase MaxQueryMem. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>mp_max_large_in_use</em> </span> -- This is the maximum amount of query memory that has been allocated to date. Reset this before the query of interest, run and read the counter. This is the peak simultaneous memory use by the query. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>mp_large_in_use</em> </span> -- This is the current amount of query memory in use. Do not reset this. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>c_max_large_vec</em> </span> -- This is the MaxQueryMem init setting in bytes. This can be altered at run time with <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> . </p> </li> </ul> </div> </li> </ol> </div> </div> <div> <span class="permalink"><a id="ptunehighcardin" onclick="javascript:permalink(this)" href="#ptunehighcardin">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">High Cardinality Group By And Distinct</h4> </div> </div> </div> <p>There are multiple implementations of group by and distinct used in different circumstances by different versions of Virtuoso. Versions of Virtuoso 7 prior to 7.5 have a memory based cuckoo hash based group by and hash join. 7.5 and onwards have a linear hash based implementation of same. Additionally, all version 7's have a pageable, i.e. potentially disk based implementation of group by that may get used if there is no space in memory.</p> </div> <div> <span class="permalink"><a id="ptuneprtgroupby" onclick="javascript:permalink(this)" href="#ptuneprtgroupby">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Partitioned Group By</h4> </div> </div> </div> <p>Versions 7.5 and onwards have a choice of a partitioned or re-aggregated parallel group by. The group by with re-aggregation produces an intermediate result on each thread and then adds these up after the completion of each thread into a final result. This is efficient for low-cardinality cases (few distinct values of grouping columns) but inefficient for high cardinality. In the high cardinality case, it is better to use a partitioned group by operator. In the partitioned case, a hash is computed from the grouping columns and this decides which thread gets to do the aggregation. There is information exchange between threads (or processes in a scale-out setting) but there is no need for re-aggregation. This is significantly more performant with many groups. The peak memory utilization is the same.</p> <p>The <code class="code">c_setp_partition_threshold</code> setting in the <span class="emphasis"><em>Flags</em></span> section of virtuoso.ini defines when to use a partitioned group by. The default threshold is 100000. If the cost model estimates more distinct values than this threshold, a partitioned group by will be produced. In a query plan with explain of profile, a partitioned group by is present when there is a stage <n> operator in front of the sort operator for the group by. In a cluster plan, the partitioned group by may be colocated with the table right before it, so the stage operator will be before this.</p> </div> <div> <span class="permalink"><a id="ptuneorderedgroupby" onclick="javascript:permalink(this)" href="#ptuneorderedgroupby">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Ordered Group By</h4> </div> </div> </div> <p>For version 7.5 onwards, a special case for ordered group by is recognized. In an ordered group by, the system takes advantage of physical data ordering to limit the memory footprint of the group by: If it is known that grouping keys will not reoccur past a certain window, then all grouping keys that are processed can be emitted as results in a continuous stream so that only a window of groups need be kept at a time.</p> <p>This is recognized in a query plan by the word "streaming" occurring on the line of the sort operator for the group by.</p> <p>Ordered group by is rare to non-existent with RDF, where data orderings with an application meaning do not occur, due to having no multipart keys. With a SQL schema grouping on a set of columns including the primary ordering column of the outermost scan in a plan, an ordered group by will typically be generated. An ordered group by is usually better than a partitioned or re-aggregated group by. The exception may be cases where the outermost ordering column has low cardinality, or a very biased value distribution e.g. the P in the RDF PSOG.</p> </div> <div> <span class="permalink"><a id="ptunememorygroupby" onclick="javascript:permalink(this)" href="#ptunememorygroupby">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Memory for Group By</h4> </div> </div> </div> <p>In Virtuoso 7 prior to 7.5, the memory for a group by is <code class="code"> (3 + n_keys + n_aggregates) * 8 </code> bytes per group plus the natural length of any dates or strings in the keys or aggregates. In 7.5 onwards, the memory is 8 bytes less per entry.</p> </div> <div> <span class="permalink"><a id="ptuneslowgroupby" onclick="javascript:permalink(this)" href="#ptuneslowgroupby">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Slow Group By</h4> </div> </div> </div> <p>The use of the disk-based group by is easily 100x less efficient than the vectored memory based hash tables. Falling back to this can be considered an error in configuration and can be detected with the <code class="code">tc_slow_temp_insert</code> counter readable with <code class="code">sys_stat</code> . If this increases then there is not enough memory for group by/distinct as used by the application. The monitor may print a message about this in the server messages log.</p> <p>The maximum size of a memory based group by hash table is by default 1/10 of the MaxQueryMem setting in Parameters in the virtuoso.ini file. If a single hash table exceeds this or if the hash table plus the amount of large query memory blocks (e.g. vectors) allocated across the process exceeds MaxQueryMem, then the switch to the slow pageable hash table takes place. This can be avoided by explicitly setting a larger MaxQueryMem or by changing the <code class="code">cha_max_gby_bytes</code> setting in the Flags section of the ini file. We note that for parallel query plans the first condition to trigger is the condition on <code class="code">mp_large_in_use</code> + the hash table memory exceeding MaxQueryMem. A query will have more than 10 threads and the hash tables for memory based hashes are included in <code class="code">mp_large_in_use</code> .</p> <p>To track the general memory consumption in large blocks, use the <code class="code">mp_large_in_use</code> and <code class="code">mp_max_large_in_use meters</code> accessible with <code class="code">sys_stat</code> and <code class="code">__dbf_set</code> . Large blocks are for example vectors, group by's and hash join build sides.</p> <p>To interactively try different memory settings, one can modify <code class="code">c_max_large_vec</code> with <code class="code">__dbf_set</code> . This is the number of bytes of outstanding large blocks after which pageable group by's will be used and vector sizes will no longer be adjusted upward.</p> </div> <div> <span class="permalink"><a id="tunparamsmworkload" onclick="javascript:permalink(this)" href="#tunparamsmworkload">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Tuning Parameters for Multiuser Workloads</h4> </div> </div> </div> <p>This section describes parameters and event counters that affect memory and parallelism and are specially relevant for high concurrency situations. Different switches and event counters are described. Setting these requires dba privileges. The event counters are accessed with <span class="emphasis"><em>sys_stat</em></span> and set with <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> . For example: </p> <pre class="programlisting"> select sys_stat ('tc_qp_thread'); or __dbf_set ('dc_batch_sz', 10000); </pre> <p>Some of the parameters have corresponding INI file settings. All of these can be set in an INI file in the [Flags] section with a stanza like: </p> <pre class="programlisting"> dc_batch_sz = 10000 </pre> <p>First, make sure that the <span class="emphasis"><em>ServerThreads</em></span> in either <a href="/virtuoso/ch-server/#ini_parameters">[Parameters] ini section</a> (if application with connected clients) or in <a href="/virtuoso/ch-server/#ini_httpserver">[HTTPServer] ini section</a> (if over web protocols), is larger than the number of actual connections. </p> <p>Next, the workload should be profiled to see its memory utilization and intrinsic use of parallelism. Splitting a query into independently executable parallel fragments increases its memory utilization, Switching to larger vector sizes also increases a query's memory utilization while providing increased locality of data access. Together these techniques can result in a 100+ fold difference in the transient memory consumption of a query. Use of hash joins may also increase the transient memory consumption since in a hash join one half of the join must be materialized.</p> <p>With relatively small numbers of concurrent queries, e.g. 10, these techniques are nearly always beneficial. With hundreds of queries the memory overhead may become a limiting factor.</p> <p>The <span class="emphasis"><em>MaxQueryMem</em></span> INI file setting controls how much memory is kept for query execution. This amount of space is maintained allocated. Transient memory use may exceed this but then the memory above this amount is unmapped when no longer needed. Mapping and unmapping memory takes time. Concurrent mmap and munmap calls on different threads will serialize and bring down the CPU utilization of a process even when there is enough parallelism for full platform utiliization.</p> <p>The <span class="emphasis"><em>mp_mmap_clocks</em></span> counter is the cumulative amount of real time in CPU clocks spent in mmap or munmap systtem calls. This can increase faster than real time if multiple threads are involved.</p> <p>If this value grows fast, e.g. at over 10% of real time, the monitor prints a message in the server event log. This is an indication that memory utilization may have to be tuned.</p> <p>For analyzing the behavior of a workload as concerns memory, do the following:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>Run the workload once for warmup.</p> </li> <li class="listitem"> <p>Clear the following counters: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <code class="code">mp_max_large_in_use </code> -- Highest to date amount of concurrently used memory </p> </li> <li class="listitem"> <p> <code class="code">tc_qp_thread </code> -- count of times a query made a parallel executive fragment. Not increased if running single threaded. </p> </li> <li class="listitem"> <p> <code class="code">tc_adjust_batch_sz </code> -- count of times vector size was switched to larger </p> </li> <li class="listitem"> <p> <code class="code">mp_mmap_clocks </code> -- cumulative time inside mmap or munmap. </p> </li> </ul> </div> <p>For example:</p> <pre class="programlisting"> __dbf_set ('mp_max_large_in_use', 0); </pre> </li> <li class="listitem"> <p>Run the workload on a single thread with default settings.</p> </li> <li class="listitem"> <p>Observe the values.</p> </li> </ul> </div> <div> <span class="permalink"><a id="tunparamsmworkloadex" onclick="javascript:permalink(this)" href="#tunparamsmworkloadex">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Example Scenario</h5> </div> </div> </div> <div class="orderedlist"> <ol class="orderedlist" type="1"> <li class="listitem"> <p>Clear the counters.</p> </li> <li class="listitem"> <p>Set <code class="code">enable_dyn_batch_sz</code> to 0, causing queries to only use the initial vector size, <code class="code">dc_batch_sz</code> or <code class="code">VectorSize</code> in the INI file.</p> </li> <li class="listitem"> <p>Set <code class="code">enable_qp</code> to 1, causing queries to run single threaded.</p> </li> <li class="listitem"> <p>Run the workload on a single thread. The difference in elapsed real time will show how much benefit the workload has from intra-query parallelization and long vector sizes. If the workload used any of the memory consuming techniques the peak memory in the second case will be lower. How much lower is entirely workload dependent. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <span class="emphasis"><em>Note</em> </span> : One may additionally try the workload on a single thread with <code class="code">hash_join_enable</code> set to 0 and 2, respectively. 0 means no hash join plans are made, 2 means that hash join is used when appropriate for either SQL or SPARQL queries. The peak memory utilization and run times may be significantly affected.</p> </li> </ul> </div> </li> <li class="listitem"> <p>Having completed these metrics, one may move to the multi-user case. Note that <code class="code">MaxQueryMem</code> , ( <code class="code">c_max_large_vec</code> setting with <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> ) should be set to a reasonable value, e.g. the peak consumption with the chosen settings times the number of parallel sessions. </p> </li> <li class="listitem"> <p>Expected Results -- Experience demonstrates for example that with a 128 concurrent users <code class="code">setting enable_qp</code> to 1 and <code class="code">enable_dyn_batch_sz</code> to 0 increased the throughput of the sample workload by a factor of 2.5. The workload derived, even in single user mode, little benefit from dynamic vector size or multithreading, under 30%. In the case at hand, the difference in performance was mostly accounted for by <code class="code">mmap</code> , see the <code class="code">mp_mmap_clocks</code> counter. </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>If more concurrent queries are than CPU cores are expected, there is little point in intra-query parallelism, controlled by <code class="code">ThreadsPerQuery</code> in the INI file or <code class="code">enable_qp</code> in <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> . </p> </li> <li class="listitem"> <p>If <code class="code">mp_mmap_clocks</code> continues to grow fast during the execution one may increase <code class="code">c_max_large_vec</code> . This will cause more <code class="code">mmap</code> 's to be kept in reserve, thus in principle decreasing the frequency of <code class="code">mmap</code> and <code class="code">munmap</code> system calls.</p> </li> <li class="listitem"> <p>If running with hash join enabled, there is a possibility of partitioned hash joins where the query executes in multiple passes in order to build smaller hash tables. This is given by <code class="code">tc_part_hash_join</code> , which is increased by 1 for each non-first pass over a hash join. If the counter increases the <code class="code">HashJoinSpace</code> setting in the INI file should be increased. With <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set</code></a> this is <code class="code">chash_space_avail</code> . </p> </li> </ul> </div> </li> <li class="listitem"> <p>Notes: </p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>The results from above may not happen with a single user but happen all the time with multiple users. The monitor will print a warning message about this in the message log. </p> </li> <li class="listitem"> <p>One may also try a different default vector size, specially if very pressed on memory. The default of 10000 values is generally a good small value but smaller may be possible, however not under 1000. </p> </li> </ul> </div> </li> </ol> </div> </div> </div> <div> <span class="permalink"><a id="querylogging" onclick="javascript:permalink(this)" href="#querylogging">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Query Logging</h4> </div> </div> </div> <p>As of version 7.00 Virtuoso offers optional server side query logging. This records a large number of execution statistics as well as the full query text and execution plan with per-operator timing and cardinality information.</p> <p>This feature is enabled in the Parameters section of virtuoso.ini:</p> <pre class="programlisting"> ; virtuoso.ini ... [Parameters] QueryLog = filename </pre> <p>At run time, this may be enabled or disabled with prof_enable (), overriding the specification of the ini file. The default file name for the query log is virtuoso.qrl in the server's working directory, if not otherwise specified in the ini file.</p> <p>The file is in binary format and is not conveniently readable as such. It is most easily accessed via the DB.DBA.SYS_QUERY_LOG system view. This view has parameters for specifying a non-default file path for the query log file as well as a datetime range for selecting the entries of interest.</p> <p>For example:</p> <pre class="programlisting"> SELECT * FROM sys_query_log WHERE qrl_file = 'other.qrl' AND qrl_start_dt = cast ('2011-10-1' as datetime) AND qrl_end_dt = cast ('2011-10-2' as datetime) </pre> <p>This will select entries from the file other.qrl that are between the given dates. Note that the qrl* columns are not actual result column of the view but are considered as parameters, hence the use of = instead of a range condition.</p> <p>All statements executed over a SQL client connection (ODBC/JDBC etc) are logged, as well as any statements executed on an SPARQL end point. DAV and web services requests are not logged unless they perform an exec function call. CPU usage for committing transactions or for background data organization such as autocompact or automatic checkpoints are not logged.</p> <p>A select statement is logged at the time it produces its last row of output, not at the time this row of output is fetched by a client.</p> <p>Some of the columns are in units of clocks, whose meaning varies from system to system. On Intel this corresponds to the value returned by the RDTSC instruction. All values are intervals. The relation of this to real time may vary in function of automatic variation of clock frequency.</p> <p>The columns of SYS_QUERY_LOG are as follows:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p> <span class="emphasis"><em>ql_id</em></span> </p> <p> -- Serial number of the log entry. If the server was started many times with the same file these will not be unique. Combine with </p> <p> <span class="emphasis"><em>ql_start_dt</em></span> </p> <p> for unique identification. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_start_dt</em></span> </p> <p> -- datetime of the start of the query </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_rt_msec</em></span> </p> <p> -- real time elapsed in milliseconds between the start and the logging of the query </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_rt_clocks</em></span> </p> <p> -- Clock cycles of real time spent running the query, not including time between consecutive fetches from a client if the query was a cursor fetched in multiple chunks by a client. This is the number of clocks during which there was at least one thread running on behalf of the query. The average CPU% of the query is given by: </p> <pre class="programlisting"> 100 * ql_thread_clocks / ql_rt_clocks </pre> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_client_ip</em></span> </p> <p> -- Requesting client IP as dotted decimal. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_user</em></span> </p> <p> -- User account on behalf of which the query was executed. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_sqlstate</em></span> </p> <p> -- SQL state if query terminated with error, NULL otherwise. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_error</em></span> </p> <p> -- Error message if query terminated with error, NULL otherwise. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_swap</em></span> </p> <p> -- Cumulative count of major page faults since startup of this Virtuoso process. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_user_cpu</em></span> </p> <p> -- Cumulative user CPU in milliseconds for this server process. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_sys_cpu</em></span> </p> <p> -- Cumulative system CPU in milliseconds for this server process. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_text</em></span> </p> <p> -- Source text of the query </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_params</em></span> </p> <p> -- NULL. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_plan_hash</em></span> </p> <p> -- Hash number calculated from the execution plan, ignoring literals. Can be used for grouping executions of the same query with differing literals together. If difference of literals causes a different plan, this number will be different. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_clocks</em></span> </p> <p> -- CPU clocks of real time used for query compilation. This will be 0 if the query is separately prepared of if the query compilation comes from a cache of recently compiled queries. This is likely if the query is parametrized and executed multiple times. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_msec</em></span> </p> <p> -- Real time used for query compilation in milliseconds. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_disk</em></span> </p> <p> -- Count of disk reads done on behalf of the query compilation, this stands for index sampling initiated by the compilation and does not include any speculative read possibly triggered by the sampling. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_disk_wait</em></span> </p> <p> -- Count of clocks the compilation was blocked waiting for disk. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_cl_wait</em></span> </p> <p> -- Count of clocks the compilation was waiting for information from cluster peers. Such waiting indicates sampling done on remote partitions. If the run time of the query is small, this may be a significant factor in query execution real time. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_cl_messages</em></span> </p> <p> -- Count of distinct cluster messages sent on behalf of the compilation. These are all related to sampling. Many samples can be combined into one message in some situations. Samples are also cached on the requesting server so repeatedly compiling the same statement will send the messages only the first time in unless the cache has timed out in the meantime. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_rnd_rows</em></span> </p> <p> -- Count of rows retrieved as part of compile time sampling. </p> </li> </ul> </div> <p>The below columns correspond directly to the fields returned by db_activity (). These are summed over all the threads in all the hosts that have done something on behalf of the logged query.</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <span class="emphasis"><em>ql_rnd_rows</em></span> </p> <p> -- Count of random row lookups. Each sequential lookup begins with one random one for each partition concerned. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_seq_rows</em></span> </p> <p> -- Sequential rows fetched, each non-first row which is selected counts as one. A row that is looked at but does not satisfy applicable query criteria does not count. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_same_seg</em></span> </p> <p> -- Count of times the next random lookup in a vectored lookup falls on the same column-wise segment as the previous. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_same_page</em></span> </p> <p> -- Ibid, for the next lookup falling on the same row-wise leaf page. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_same_parent</em></span> </p> <p> -- Ibid, for the case of the next lookup falling on a sibling page of the row-wise leaf page of the previous lookup. </p> </li> </ul> </div> <p>For column-wise indices, all the three above counters can be non-zero since these consist of multi-row segments each under a row on a row-wise leaf page. For a row-wise index the same seg counter is always 0.</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p> <span class="emphasis"><em>ql_thread_clocks</em></span> </p> <p> -- Sum of clocks spent on any thread for the logged query. Time spent waiting for other threads, for disk or for replies from cluster peers is not counted, thus only running cycles count. These are added up across all hosts in a cluster. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_disk_wait_clocks</em></span> </p> <p> -- Total clocks any thread spends waiting for disk on behalf of the query. If two threads wait for the same page which is fetched once the wait is counted double. This is not the same as the total read time of the pages since read ahead can fetch pages before they are needed, thus involving no wait. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_cl_wait_clocks</em></span> </p> <p> -- Total clocks a thread running on behalf of the query spends waiting for a cluster reply. This may be zero if the coordinating thread has work until any cluster replies arrive, in which case there will be no wait. If this is high then the workload is bound by interconnect or is unevenly distributed across a cluster. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_pg_wait_clocks</em></span> </p> <p> -- Count get page wait. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_disk_reads</em></span> </p> <p> -- Count disc reads. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_spec_disk_reads</em></span> </p> <p> -- Count of speculative disk reads triggered on behalf of the query. Any read ahead or any upgrading of a single page read into a read of a whole extent counts towards this, only allocated pages that are read are counted but merging near-adjacent reads may cause actually more disk IO to take place. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_messages</em></span> </p> <p> -- Count of distinct cluster messages sent on behalf of the query. Any message is counted once. Client-server messages are not counted. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_message_bytes</em></span> </p> <p> -- Total bytes sent in all cluster messages sent on behalf of the query. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_qp_threads</em></span> </p> <p> -- Count of times an extra thread is created for parallelizing work on the query in question. The count may be high since consecutively launched threads are counted, this is not a maximum degree of concurrency. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_vec_bytes</em></span> </p> <p> -- reserved </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_vec_bytes_max</em></span> </p> <p> -- reserved </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_lock_waits</em></span> </p> <p> -- Count of times a thread has waited for a lock on behalf of the query. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_lock_wait_msec</em></span> </p> <p> -- Total milliseconds any thread has spent waiting for a lock on behalf of the query. This may be longer than real time since many threads may wait at the same time. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_plan</em></span> </p> <p> -- Text representation of the execution plan, annotated with CPU time percentages and fanouts for the different operators. Fanout is the count of output rows divided by the count of input rows. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_node_stat</em></span> </p> <p> -- reserved </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_c_memory</em></span> </p> <p> -- Count of bytes allocated for compiling the query. This is the peak size of the memory pool for query compilation. </p> </li> <li class="listitem"> <p> <span class="emphasis"><em>ql_rows_affected</em></span> </p> <p> -- Count of inserted/updated/deleted rows. If the query was a select with a top and an order by, this is is the count of produced rows before the top restriction was applied. </p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="meters_sysviews" onclick="javascript:permalink(this)" href="#meters_sysviews">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Meters & System Views</h4> </div> </div> </div> <div> <span class="permalink"><a id="kdlstat" onclick="javascript:permalink(this)" href="#kdlstat">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">DB.DBA.SYS_K_STAT, DB.DBA.SYS_D_STAT, DB.DBA.SYS_L_STAT view</h5> </div> </div> </div> <p> These views provide statistics on the database engine </p> <pre class="programlisting"> create view SYS_K_STAT as select KEY_TABLE, name_part (KEY_NAME, 2) as index_name, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'n_landings') as landed, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'total_last_page_hits') as consec, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'page_end_inserts') as right_edge, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'page_end_inserts') as lock_esc from SYS_KEYS; </pre> <pre class="programlisting"> create view SYS_L_STAT as select KEY_TABLE, name_part (KEY_NAME, 2) as index_name, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'lock_set') as locks, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'lock_waits') as waits, (key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'lock_waits') * 100) / (key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'lock_set') + 1) as wait_pct, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'deadlocks') as deadlocks, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'lock_escalations') as lock_esc from SYS_KEYS; </pre> <pre class="programlisting"> create view sys_d_stat as select KEY_TABLE, name_part (KEY_NAME, 2) as index_name, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'touches') as touches, key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'reads') as reads, (key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'reads') * 100) > / (key_stat (KEY_TABLE, name_part (KEY_NAME, 2), 'touches') + 1) as read_pct from SYS_KEYS; </pre> <p> These views offer detailed statistics on index access locality, lock contention and disk usage. </p> <p> 'reset' specified as the stat name will reset all counts for the key in question. </p> </div> <div> <span class="permalink"><a id="keystats" onclick="javascript:permalink(this)" href="#keystats">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">SYS_K_STAT - Key statistics</h5> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>KEY_TABLE The fully qualified table name, e.g. DB.DBA.SYS_PROCEDURES</p> </li> <li class="listitem"> <p>INDEX_NAME The name of the index. This will be equal to the table name for the table's primary key.</p> </li> <li class="listitem"> <p>LANDED The count of random accesses, including inserts. Any insert or select, whether empty, single line or multi- line counts as one. Updates and deletes do not count, as they imply a select in the same or previous statement.</p> </li> <li class="listitem"> <p>CONSEC The number of times a random access falls on the same page as the previous random access. This is always less than LANDED. For repetitive access to the same place or an ascending insert, this will be near LANDED. For a totally random access pattern this will be near 0.</p> </li> <li class="listitem"> <p>RIGHT_EDGE The number of times an insert has added a row to the right edge of the page where the insert was made. </p> </li> <li class="listitem"> <p>LOCK_ESC The count of lock escalations, see SYS_L_STAT.</p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="lstats" onclick="javascript:permalink(this)" href="#lstats">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">SYS_L_STAT</h5> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>KEY_TABLE The fully qualified table name, e.g. DB.DBA.SYS_PROCEDURES</p> </li> <li class="listitem"> <p>INDEX_NAME The name of the index. This will be equal to the table name for the table's primary key.</p> </li> <li class="listitem"> <p>LOCKS The number of times a lock has been set on the index. Making a new row or page lock counts as one. Entering a row or page lock either after a wait or without wait (for a shared lock) counts as one.</p> </li> <li class="listitem"> <p>WAITS The number of times a cursor reading this index waited for a lock. Note that this can be higher than the number of locks set, e.g. a 'read committed' cursor may wait for a lock but will never make one.</p> </li> <li class="listitem"> <p>WAIT_PCT The percentage of lock set events that involved a wait. </p> </li> <li class="listitem"> <p>DEADLOCKS The number of times a deadlock was detected when trying to wait for a lock on this index. Note that one deadlock event may involve locks on several indices. Each deadlock detection counts as one.</p> </li> <li class="listitem"> <p>LOCK_ESC The number of times the set of row locks on a page of this index where escalated into one page lock or a page lock was set initially. This is always less than LOCKS. This value will be near LOCKS when there are many sequential selects which switch to page lock mode. This happens when a cursor has performed over 2 lock escalations and the page being entered has no locks, i.e. the lock can be set over the entire page.</p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="dstats" onclick="javascript:permalink(this)" href="#dstats">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">SYS_D_STAT</h5> </div> </div> </div> <div class="itemizedlist"> <ul class="itemizedlist" type="bullet"> <li class="listitem"> <p>KEY_TABLE The fully qualified table name, e.g. DB.DBA.SYS_PROCEDURES</p> </li> <li class="listitem"> <p>INDEX_NAME The name of the index. This will be equal to the table name for the table's primary key.</p> </li> <li class="listitem"> <p>TOUCHES The number of times a row is located on the index. Every row retrieved by a select or inserted counts as one. All rows scanned by an select count or other aggregate counts as one. </p> </li> <li class="listitem"> <p>READS The number of times a disk read was caused by a read operation on this index. This may theoretically be higher than TOUCHES, since several levels of the index tree may have to be read to get to a leaf.</p> </li> <li class="listitem"> <p>READ_PCT The percentage of READS in TOUCHES.</p> </li> </ul> </div> <div class="example" id="id13647"> <p class="title"> <strong>Example聽6.14.聽Examples:</strong> </p> <div class="example-contents"> <pre class="programlisting"> select index_name, locks, waits, wait_pct, deadlocks from sys_l_stat order by 2 desc; Get lock data, indices in descending order of lock count. select index_name, touches, reads, read_pct from sys_d_stat order by 3 desc; Get disk read counts, index with most reads first. select index_name, (consec * 100) / (landed + 1) from sys_k_stat where landed > 1000 order by 2; </pre> </div> </div> <br class="example-break" /> <p>Get the percentage of consecutive page access on indices with over 1000 accesses so far, most randomly accessed first. </p> </div> <div> <span class="permalink"><a id="statusfunc" onclick="javascript:permalink(this)" href="#statusfunc">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">status SQL function - status ();</h5> </div> </div> </div> <p>This function returns a summary of the database status as a result set. The result set has one varchar column, which has consecutive lines of text. The lines can be up to several hundred characters. </p> <p>The contents of the status summary are described in the <a href="/virtuoso/ch-server/#dbstat">Administrator's Guide</a> .</p> </div> <div> <span class="permalink"><a id="statusfunc_01" onclick="javascript:permalink(this)" href="#statusfunc_01">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Virtuoso db file usage detailed info</h5> </div> </div> </div> <p>All data in a virtuoso database are logically stored as database key rows. Thus the primary key for a table holds the entire row (including the dependent part) and the secondary keys just hold their respective key parts. So the space that the table occupies is the sum of the space occupied by it's primary key and all the secondary keys.</p> <p>The main physical unit of allocation in a virtuoso db file is the database page (about 8k in virtuoso 3.x). So the server needs to map the key rows and outline blobs to database pages.</p> <p>Virtuoso will store as many rows in a db page as it can, so usually one DB page will contain more than 1 row of a given key. No page contains rows from more than one key. However blobs (when not inlined on the row) will be placed in consecutive DB pages (up to their size). In addition to the blob and key pages the Virtuoso DB will hold a number of pages containing internal data. So the sum of the pages occupied by the key rows and the blobs is leas then the amount of occupied pages (as reported by the <a href="/virtuoso/fn_status/"><code class="function">status()</code></a> BIF).</p> <p>To provide detailed information about the space consumption of each key there's a system view:</p> <pre class="programlisting"> DB.DBA.SYS_INDEX_SPACE_STATS ISS_KEY_TABLE varchar -- name of the table ISS_KEY_NAME varchar -- name of the key ISS_KEY_ID integer -- id of the key (corresponding to KEY_ID from DB.DBA.SYS_KEYS) ISS_NROWS integer -- number of rows in the table ISS_ROW_BYTES integer -- sum of the byte lengths of all the rows in the table ISS_BLOB_PAGES integer -- sum of the blob pages occupied by the outline blobs on all the rows of the table ISS_ROW_PAGES integer -- sum of all the db pages containing rows of this key ISS_PAGES integer -- = ISS_BLOB_PAGES + ISS_ROW_PAGES (for convenience). </pre> <p>Each select on that view causes the server to go over all the db pages in the db file (similarly to how the crash dump operates) and collect the statistics above. The pages are traversed 1 time per select, but still on large database files that may take some time. </p> </div> </div> <div> <span class="permalink"><a id="transaction_isolation_levels" onclick="javascript:permalink(this)" href="#transaction_isolation_levels">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Transaction Metrics, Diagnostics and Optimization</h4> </div> </div> </div> <p>Bad design and implementation of transactions affects applications in the following ways:</p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="bullet"> <li class="listitem"> <p>Performance is lost by having to needlessly retry transactions that are aborted by deadlock.</p> </li> <li class="listitem"> <p>Concurrency is lost by having rows stay locked for too long.</p> </li> <li class="listitem"> <p>Memory is transiently consumed, adversely affecting working set, by keeping data structures for too many simultaneous locks, rollback records and uncommitted roll forward logs.</p> </li> </ul> </div> <p>The following rules should be observed when writing transactions:</p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="bullet"> <li class="listitem"> <p>Do not lock needlessly. For example, any report transaction that reads the data once can always be done as read committed instead of repeatable read without affecting semantics. Even if some data is read multiple times, the repeatable read semantic is typically not relevant for reports.</p> </li> <li class="listitem"> <p>Lock for what is needed. If you mean to update later, do the initial read with exclusive locks. See the for update clause in select, for example.</p> </li> <li class="listitem"> <p>Lock in constant order. If you must lock different resources in one transaction, lock them always in the same order. When updating stock for an order, update the quantity on hand in increasing order of item number, for instance. </p> </li> <li class="listitem"> <p>Lock the item with the least contention first. For example, update the detail before updating the summary. Update the quantity in stock for the ordered items before updating the orders count of the whole warehouse. </p> </li> <li class="listitem"> <p>Keep transactions short. Use stored procedures. Use the explicit commit work statement.</p> </li> <li class="listitem"> <p>For each transaction in a stored procedure, make sure that if it is deadlocked, the deadlocked transaction gets retried. For example, have a "declare exit handler for sqlstate 40001" for every transaction context. Make sure that a deadlocking transaction is never retried endlessly. Two mutually deadlocking transactions can keep retrying and again deadlocking each other endlessly. To avoid this, have a maximum count of retries and a random delay before restarting. The restart delay should be between 0 and the expected duration of the transaction. </p> </li> <li class="listitem"> <p>Always break batch updates into multiple transactions. Update a few thousand or tens of thousands of rows per transaction, never more than that. Failing to do this makes for prohibitive cost of retry with deadlocks and can cause swapping by keeping tens or hundreds of megabytes in rollback state, locks and other transaction temporary structures. This happens if one inserts, updates, deletes several million rows in a single transaction. If this is really needed and concurrency is no issue, use the atomic mode, effectively making the server single user for the transaction, thus having no locking or rollback. See the use of the </p> <p> <span class="emphasis"><em>__atomic()</em></span> </p> <p> function in the <a href="/virtuoso/faultfaulttoleradmapi/">Cluster Administration API</a> . </p> </li> </ul> </div> <div> <span class="permalink"><a id="ptuneprogvirtpl" onclick="javascript:permalink(this)" href="#ptuneprogvirtpl">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Programming Virtuoso/PL</h5> </div> </div> </div> <p>The isolation level is set in Virtuoso/PL with the</p> <pre class="programlisting"> set isolation := level; </pre> <p>statement, where level is one of 'serializable', 'repeatable', 'committed', 'uncommitted'. Example :</p> <pre class="programlisting"> set isolation = 'serializable'; </pre> <p> The standard SQL syntax is also supported :</p> <pre class="programlisting"> SET TRANSACTION ISOLATION LEVEL <isolation_level> isolation level : READ UNCOMMITTED | READ COMMITTED | REPEATABLE READ | SERIALIZABLE </pre> <p> Example :</p> <pre class="programlisting"> SET TRANSACTION ISOLATION LEVEL READ COMMITTED </pre> <p>The effect is for the rest of the procedure and any procedure called from this procedure. The effect stops when the procedure having executed the set isolation statement returns.</p> </div> <div> <span class="permalink"><a id="ptunetransparallel" onclick="javascript:permalink(this)" href="#ptunetransparallel">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Transaction Parallelism</h5> </div> </div> </div> <p>From Virtuoso 7.1 onwards, data manipulation statements can be multithreaded. The virtuoso.ini <code class="code">[Flags]</code> settings <code class="code">enable_mt_txn</code> and <code class="code">enable_mt_transact</code> control transaction parallelism. These are 1 for enable and 0 for disable. Defaults are version dependent, off in 7.1 and 7.2 and on in subsequent. The <a href="/virtuoso/fn_sys_stat/"><code class="function">sys_stat()</code></a> and <a href="/virtuoso/fn_dbf_set/"><code class="function">__dbf_set()</code></a> functions can be used for querying and altering these.</p> <p>DML statements, e.g. insert, delete, update, are automatically multithreaded according to <code class="code">enable_qp</code> (<code class="code">ThreadsPerQuery</code> in ini [Parameters] when <code class="code">enable_mt_txn</code> is on).</p> <p>RDF load (<a href="/virtuoso/fn_ttlp/"><code class="function">DB.DBA.ttlp()</code></a> and related functions) when in transactional mode (log_enable 0 or 1) are also multithreaded when <code class="code">enable_mt_txn</code> is on. Otherwise these are multithreaded when in non-transactional mode (<code class="code">log_enable</code> 2 or 3) and single threaded in transactional mode.</p> <p>The <code class="code">enable_mt_transact</code> setting controls the parallelism of a commit or rollback. Specially for column store deletes, the commit may take a long time, as this is the point where the physical deletion takes place. To accelerate this, <code class="code">enable_mt_transact</code> should be on. This is however not worthwhile for short row store transactions, as the overhead of making threads is greater than the time it takes to finalize a transaction om a page. Again, large, scattered row store deletes may justify use of <code class="code">enable_mt_transact</code> .</p> </div> <div> <span class="permalink"><a id="ptunesampledeadlockhandler" onclick="javascript:permalink(this)" href="#ptunesampledeadlockhandler">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Sample Deadlock Handler</h5> </div> </div> </div> <p>The text for a deadlock handler is</p> <pre class="programlisting"> declare retry_count int; retry_count := 0; retry: { declare exit handler for sqlstate '40001' { rollback work; ... delay (rnd (2.5)); --- if 2.5 seconds is the expected duration of the transaction. ... retry_count := retry_count + 1; if (retry_count > 5) signal ("xxxxx", "Too many deadlock retries in xxxxx."); goto retry; } -- do the operations. The actual working code here. commit work; } </pre> <p>An exclusive read is done with</p> <pre class="programlisting"> select s_quantity from stock where s_i_id = 111 for update; </pre> </div> <div> <span class="permalink"><a id="ptuneodbciso" onclick="javascript:permalink(this)" href="#ptuneodbciso">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">ODBC</h5> </div> </div> </div> <p>For the Virtuoso ODBC driver the isolation is set by :</p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="bullet"> <li class="listitem"> <p>connection option (in either <a class="ulink" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlsetconnectattr.asp" target="_top">SQLSetConnectAttr ()</a> or <a class="ulink" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqlsetconnectoption.asp" target="_top">SQLSetConnectOption ()</a> ) </p> <pre class="programlisting"> rc = SQLSetConnectOption (hdbc, SQL_TXN_ISOLATION, SQL_TXN_READ_COMMITTED); </pre> <p> or </p> <pre class="programlisting"> rc = SQLSetConnectAttr (hdbc, SQL_TXN_ISOLATION, SQL_TXN_READ_COMMITTED, NULL); </pre> <p>Constants are : SQL_TXN_READ_UNCOMMITTED, SQL_TXN_READ_COMMITTED, SQL_TXN_REPEATABLE_READ, SQL_TXN_SERIALIZABLE</p> </li> <li class="listitem"> <p>ODBC setup dialog option : In Windows there is a drop-down combo box to set the default transaction isolation level for a connection.</p> </li> <li class="listitem"> <p>connection string element : You may specify the default transaction isolation level for a given connection in it's connect string (passed to the <a class="ulink" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/odbc/htm/odbcsqldriverconnect.asp" target="_top">SQLDriverConnect ()</a> ODBC API). Example :</p> <pre class="programlisting"> SQLDriverConnect (hdbc, hwnd, "DSN=MyDSN;IsolationLevel=Repeatable Read;UID=dba;PWD=dbapwd", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT). </pre> <p>The possible options for the connection string are : "Read Uncommitted", "Read Committed", "Repeatable Read" and "Serializable"</p> </li> </ul> </div> </div> <div> <span class="permalink"><a id="ptunejdbciso" onclick="javascript:permalink(this)" href="#ptunejdbciso">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">JDBC</h5> </div> </div> </div> <p>In the Virtuoso JDBC driver the isolation is set by the <a class="ulink" href="http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Connection.html#setTransactionIsolation(int)" target="_top">java.sql.Connection.setTransactionIsolation()</a> JDBC API.</p> <pre class="programlisting"> conn.setTransactionIsolation (java.sql.Connection.TRANSACTION_SERIALIZABLE) </pre> <p>The constants are described in the <a class="ulink" href="http://java.sun.com/j2se/1.5.0/docs/api/java/sql/Connection.html#field_summary" target="_top">Java Docs</a> </p> </div> <div> <span class="permalink"><a id="ptunedotnetiso" onclick="javascript:permalink(this)" href="#ptunedotnetiso">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">.Net</h5> </div> </div> </div> <p>In the VirtuosoClient.NET provider the isolation is set by the <a class="ulink" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdataidbconnectionclassbegintransactiontopic2.asp" target="_top">System.Data.IDbConnection.BeginTransaction Method (IsolationLevel)</a> function.</p> <pre class="programlisting"> System.Data.IDBTransaction trx = conn.BeginTransaction (System.Data.IsolationLevel.ReadCommitted) </pre> <p>The constants are described <a class="ulink" href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemdataisolationlevelclasstopic.asp" target="_top">here</a> </p> </div> </div> <div> <span class="permalink"><a id="ptunemetricsdiag" onclick="javascript:permalink(this)" href="#ptunemetricsdiag">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Metrics and Diagnostics</h4> </div> </div> </div> <p>Metrics are presented at the server and the table level.</p> <p>The first metric to check is the output of status ('');</p> <p>The paragraph titled transaction status contains the following:</p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="bullet"> <li class="listitem"> <p>Count of deadlocks since server startup. There is a total number of deadlocks and the number of 2r1w deadlocks. The latter is a special case where two transactions both hold a shared lock on a resource and one tries to convert the lock to exclusive. This situation can kill the transaction attempting to write. Such deadlocks are essentially always needless. These are avoided by reading for update when first reading the resource. </p> </li> <li class="listitem"> <p>Count of waits since server startup. This is incremented every time some operation waits for a lock, except if this wait leads into a deadlock. If the number of deadlocks is high, let's say over 5% of the number of waits, transactions are likely badly designed and deadlock too often, either because of not locking for write at the get go (2r1w) or because of locking resources in varying order. </p> </li> <li class="listitem"> <p>Count of threads running. This is the count of all threads that are somehow occupied, whether running or waiting. This count minus the count of waiting minus the count of threads in vdb is the count of threads that in principle could be on CPU. </p> </li> <li class="listitem"> <p>Count of threads waiting. This is the count of threads that are waiting for a lock. If this is a high percentage of the count of threads running, say over 30%, resources are likely locked inefficiently, keeping too many locked. </p> </li> <li class="listitem"> <p>Count of threads in vdb. This is the count of threads that are at the time waiting for I/O either from a remote database or any sort of network operation, including access to web services on other serbers, access to web pages on other hosts etc. </p> </li> </ul> </div> <p>The system view db.dba.sys_l_stat is used for locating bottlenecks.</p> <p>The columns are:</p> <div class="itemizedlist"> <ul class="itemizedlist compact" type="bullet"> <li class="listitem"> <p>index - The index being locked. Note that when reading on non-primary key, the lock is set on the index first, only then on the pk, that is if the pk is accessed at all. For all updates however, the pk will always be accessed. *locks - The count of times a lock was set on this index. </p> </li> <li class="listitem"> <p>waits - The number of times there was a wait on this index. There can be more waits than locks because a read committed cursor can wait but will not lock, thus all waits do not result in locks. </p> </li> <li class="listitem"> <p>wait_pct - The percentage of times setting a lock waited. (100 * waits) / locks </p> </li> <li class="listitem"> <p>deadlocks - The number of times a deadlock was signalled when attempting to wait for a lock on this index. </p> </li> <li class="listitem"> <p>lock_esc - The number of times a set of row locks was converted into a page lock on this index. </p> </li> <li class="listitem"> <p>wait_msecs - The total amount of real time spent by some thread waiting for a lock on this index. This may be greater than elapsed time because many threads can wait at the same time. </p> </li> </ul> </div> <p>All counts and times are cumulative from server startup.</p> <p>The interpretation is as follows:</p> <p>If deadlocks is high in relation to waits or locks, i.e. over 5%, there are many deadlocks and the transaction profiles may have to be adjusted. The table where deadlocks is incremented is the table where the deadlock was detected but the deadlock may involve any number of tables. So, if A and B are locked in the order A, B half of the time and B, a the rest of the time, then the deadlocks of the tables of A and B will be about the same, half of the deadlocks being detected when locking A, the other half when locking B.</p> <p>If waits is high in relation to locks, for example 20%, then there is probably needless contention. Things are kept locked needlessly. Use read committed or make shorter transactions or lock items with the less contention first.</p> <p>Because transaction duration varies, the place with the highest count of waits is not necessarily the place with the heaviest contention if the waits are short. Use wait_msecs in addition to waits for determining where the waiting takes place.</p> <p>To get a general picture, use the Conductor's Statistics page or simply do:</p> <pre class="programlisting"> select top 5 * from sys_l_statt order by wait_msecs desc; </pre> <p>to get a quick view of where time is spent. You can also sort by waits desc or locks desc.</p> <div> <span class="permalink"><a id="ptunemetricdiagsqlissues" onclick="javascript:permalink(this)" href="#ptunemetricdiagsqlissues">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">SQL Issues</h5> </div> </div> </div> <p>It is possible to get bad locking behavior if the SQL compiler decides to make linear scans of tables or indices and the isolation is greater than read committed. The presence of a linear scan on an index with locking is often indicated by having a large number of lock escalations. If lock_esc is near locks then a large part of the activity is likely sequential reads.</p> <p>The general remedy is to do any long report type transactions as read committed unless there are necessary reasons to do otherwise.</p> <p>To see how a specific query is compiled, one can use the explain () function. To change how a query is compiled, one can use the table option or option SQL clauses.</p> </div> <div> <span class="permalink"><a id="ptunemetricdiagdynmicsobs" onclick="javascript:permalink(this)" href="#ptunemetricdiagdynmicsobs">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Observation of Dynamics</h5> </div> </div> </div> <p>Deadlocks and contention do not occur uniformly across time. The occurrences will sharply increase after a certain application dependent load threshold is exceeded.</p> <p>Also, deadlocks will occur in batches. Several transactions will first wait for each other and then retry maybe several times, maybe only one succeeding at every round. In such worst cases, there will be many more deadlocks than successfully completed transactions. Optimize locking order and make the transactions smaller.</p> <p>Looking at how counts change, specially if they change in bursts is useful.</p> </div> <div> <span class="permalink"><a id="ptunemetricdiagsqdebug" onclick="javascript:permalink(this)" href="#ptunemetricdiagsqdebug">露</a> </span> <div class="titlepage"> <div> <div> <h5 class="title">Tracing and Debugging</h5> </div> </div> </div> <p>The most detailed picture of a system's behavior, including deadlocks nd other exceptions cn be obtained with profiling. If the application is in C, Java or some other compiled language, one can use the language's test coverage facility to see execution counts for various branches of the code.</p> <p>For client applications, using the Virtuoso <code class="function">trace()</code> function can be useful for seeing which statements signal errors. Also the profiling report produced by <a href="/virtuoso/fn_prof_enable/"><code class="function">prof_enable ()</code></a> can give useful hints on execution times and error frequencies. See Profiling and <a href="/virtuoso/fn_prof_enable/"><code class="function">prof_enable ()</code></a> .</p> <p>For PL applications, Virtuoso provides a profiler and test coverage facility. This is activated by setting PLDebug = 2 in the Parameters section of the ini file and starting the server. The functions cov_store () and cov_report are used for obtaining a report of the code execution profile thus far. See the documentation on "Branch Coverage" for this. The execution counts of the lines for exception handler code will show the frequency of exceptions. If in a linear block of code a specific line has an execution count lower than that of the line above it, then this means that the line with the higher count has signalled as many exceptions as the difference of the higher and lower count indicates.</p> <p>The times indicated in the flat and call graph profile reports for PL procedures are totals across all threads and include time spent waiting for locks. Thus a procedure that consumes almost no CPU can appear high on the list if it waits for locks, specially if this is so on multiple threads concurrently. The times are real times measured on threads separately and can thus exceed any elapsed real tiime.</p> <p>Single stepping is not generally useful for debugging locking since locking issues are timing sensitive.</p> </div> </div> <div> <span class="permalink"><a id="clientlevelresourceaccounting" onclick="javascript:permalink(this)" href="#clientlevelresourceaccounting">露</a> </span> <div class="titlepage"> <div> <div> <h4 class="title">Client Level Resource Accounting</h4> </div> </div> </div> <p>Starting with version 6, Virtuoso keeps track of the count of basic database operations performed on behalf of each connected client. The resource use statistics are incremented as work on the connection proceeds. The db_activity () function can be called to return the accumulated operation counts and to optionally reset these. </p> <p>The db_activity built-in function has one optional argument. The possible values are:</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>0 - (default) - Return human readable string and reset the counts.</p> </li> <li class="listitem"> <p>1 - return an array of numbers and reset the counts.</p> </li> <li class="listitem"> <p>2 - return a human readable string and leave the counts.</p> </li> <li class="listitem"> <p>3 - return an array of numbers and leave the counts.</p> </li> </ul> </div> <p>The human readable string is of the form:</p> <pre class="programlisting"> 22.56MR rnd 1.102GR seq 10P disk 1.341GB / 102.7K messages </pre> <p>The postfixes K, M, G, T mean 10^3 to 10^15, except when applied to bytes, where these mean consecutive powers of 1024.</p> <p>The numbers, left to right are the count of random row lookups, sequential row lookups, disk page reads, cluster inter-node traffic in bytes and cluster inter-node message count as an integer number of messages. If the configuration is a single server, the two last are 0. </p> <p>The random and sequential lookup counts are incremented regardless of whether the row was found or not or whether it matched search conditions.</p> <p>If the information is retrieved as an array, the array contains integer numbers representing these plus some more metrics.</p> <p>Index - Meaning</p> <div class="itemizedlist"> <ul class="itemizedlist" type="disc"> <li class="listitem"> <p>0 - Random lookups</p> </li> <li class="listitem"> <p>1 - sequential lookups</p> </li> <li class="listitem"> <p>3 - lock waits</p> </li> <li class="listitem"> <p>4 - total msec spent in lock wait on some thread. In a cluster situation, this may be more than elapsed real time.</p> </li> <li class="listitem"> <p>5 - Disk reads</p> </li> <li class="listitem"> <p>6 - Speculative disk reads. These are also counted in disk reads. A speculative read is a prefetch made on the basis of a read history of a disk extent.</p> </li> <li class="listitem"> <p>7 - Cluster inter node message count</p> </li> <li class="listitem"> <p>8 - Total bytes sent in cluster inter node traffic. A message is counted once, when sent.</p> </li> </ul> </div> <p>If the thread calling db_activity is a web server thread, the totals are automatically reset when beginning the processing of the current web request.</p> </div> </div> </div> </div> </div> </div> </div> <div class="navfooter"> <hr /> <table width="100%" summary="Navigation footer"> <tr> <td width="40%" align="left"><a href="/virtuoso/conceptarchitecture/">Prev</a>聽</td> <td width="20%" align="center">聽</td> <td width="40%" align="right">聽<a href="/virtuoso/htmlconductorbar/">Next</a></td> </tr> <tr> <td width="40%" align="left" valign="top">5.5.聽Architecture聽</td> <td width="20%" align="center"> <a href="/virtuoso/index/">Home</a> </td> <td width="40%" align="right" valign="top">聽6.2.聽HTML based Administration Console (Conductor) Guide</td> </tr> </table> </div> <div role="contentinfo" class="copyright"> <p>© OpenLink Software <span id="footercopyrightyear">2016</span> . </p> </div> </div> <script> function toggleMenu() { var menu = document.getElementById('menu'); if (menu.style.display === 'block') { menu.style.display = 'none'; } else { menu.style.display = 'block'; } } function toggleSubmenu(element) { var parentLi = element.parentElement; parentLi.classList.toggle('active'); } function permalink(el) { var link=el.href if(!link.match(/^https?:/)) { link=document.location.href + el.href } navigator.clipboard.writeText(link) alert("Link copied to clipboard") } function startup() { var path=document.location.pathname var udatop=document.getElementById("menuuda") var udainside=document.getElementById("menuudainside") var virtuosotop=document.getElementById("menuvirtuoso") var virtuosoinside=document.getElementById("menuvirtuosoinside") var navfootertopprev=document.getElementById("navfootertopprev") var navfootertopnext=document.getElementById("navfootertopnext") var navprev=document.querySelector("body > div.gridcontainer > div.navfooter > table > tbody > tr:nth-child(1) > td:nth-child(1) > a") var navnext=document.querySelector("body > div.gridcontainer > div.navfooter > table > tbody > tr:nth-child(1) > td:nth-child(3) > a") var navprevtitle=document.querySelector("body > div.gridcontainer > div.navfooter > table > tbody > tr:nth-child(2) > td:nth-child(1)") var navnexttitle=document.querySelector("body > div.gridcontainer > div.navfooter > table > tbody > tr:nth-child(2) > td:nth-child(3)") var d=new Date() var did=document.getElementById("footercopyrightyear") did.innerHTML = d.getFullYear() if(window.innerWidth/14 > 58) { if (path.match(/^\/virtuoso/)) { toggleSubmenu(virtuosotop) toggleSubmenu(virtuosoinside) } if (path.match(/^\/uda/)) { toggleSubmenu(udatop) toggleSubmenu(udainside) } } if(navfootertopprev && navprevtitle) { navprevtitle=navprevtitle.innerHTML navfootertopprev.innerHTML='<a accesskey="p" title="Previous: '+navprevtitle+'" href="'+navprev.getAttribute("href")+'">芦</a>' } if(navfootertopnext && navnexttitle) { navnexttitle=navnexttitle.innerHTML navfootertopnext.innerHTML='<a accesskey="n" title="Next: '+navnexttitle+'" href="'+navnext.getAttribute("href")+'">禄</a>' } } startup(); </script>  <script type="text/turtle"><![CDATA[@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#> . @prefix schema: <http://schema.org/> . <http://docs.openlinksw.com/virtuoso/ch-server/> rdf:type schema:TechArticle ; schema:name "Chapter\u00A06.\u00A0Administration" ; schema:copyrightHolder _:vb78672 ; schema:datePublished "2016-09-09 16:16:54" ; schema:headline "Chapter\u00A06.\u00A0Administration" ; schema:keywords "OpenLink,Virtuoso,database,RDBMS,relational,SQL,RDF,triple store,linked data,linked open data,Big Data" ; schema:license <http://creativecommons.org/licenses/by/4.0/deed.en_US> ; schema:publisher _:vb78671 ; schema:url <http://docs.openlinksw.com/virtuoso/ch-server/> . _:vb78671 rdf:type schema:Organization ; schema:name "OpenLink Software" . @prefix ns2: <http://www.openlinksw.com/#> . _:vb78671 schema:url ns2:this . _:vb78672 rdf:type schema:Organization ; schema:name "OpenLink Software" ; schema:url ns2:this . ]]> </script> <script type="application/ld+json">{ "@graph": [ { "@id": "http://docs.openlinksw.com/virtuoso/ch-server/", "@type": "http://schema.org/TechArticle", "http://schema.org/name": "Chapter\u00A06.\u00A0Administration", "http://schema.org/copyrightHolder": { "@id": "_:vb78672"}, "http://schema.org/datePublished": "2016-09-09 16:16:54", "http://schema.org/headline": "Chapter\u00A06.\u00A0Administration", "http://schema.org/keywords": "OpenLink,Virtuoso,database,RDBMS,relational,SQL,RDF,triple store,linked data,linked open data,Big Data", "http://schema.org/license": { "@id": "http://creativecommons.org/licenses/by/4.0/deed.en_US"}, "http://schema.org/publisher": { "@id": "_:vb78671"}, "http://schema.org/url": { "@id": "http://docs.openlinksw.com/virtuoso/ch-server/"} }, { "@id": "_:vb78671", "@type": "http://schema.org/Organization", "http://schema.org/name": "OpenLink Software", "http://schema.org/url": { "@id": "http://www.openlinksw.com/#this"} }, { "@id": "_:vb78672", "@type": "http://schema.org/Organization", "http://schema.org/name": "OpenLink Software", "http://schema.org/url": { "@id": "http://www.openlinksw.com/#this"} } ] } </script> <div class="microdata" style="display: none"> <div class="container-fluid"> <nav class="navbar navbar-expand-md sticky-top navbar-light bg-light"><a class="navbar-brand" href="#" onclick="javascript:history.go(-1); return false;">SPARQL | </a></nav> <p>This HTML5 document contains 15 embedded RDF statements represented using HTML+Microdata notation.</p> <p>The embedded RDF content will be recognized by any processor of HTML5 Microdata.</p> <h3>Namespace Prefixes</h3> <table class="table table-sm table-borderless"> <tr> <th>Prefix</th> <th>IRI</th> </tr> <tr> <td>schema</td> <td>http://schema.org/</td> </tr> <tr> <td>n5</td> <td>http://creativecommons.org/licenses/by/4.0/</td> </tr> <tr> <td>n2</td> <td>http://docs.openlinksw.com/virtuoso/ch-server/</td> </tr> <tr> <td>rdf</td> <td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td> </tr> <tr> <td>n4</td> <td>http://www.openlinksw.com/#</td> </tr> <tr> <td>xsdh</td> <td>http://www.w3.org/2001/XMLSchema#</td> </tr> </table> <h3>Statements</h3> <dl itemscope="itemscope" itemid="http://docs.openlinksw.com/virtuoso/ch-server/"> <dt>Subject Item</dt> <dd>n2:</dd> <dt>rdf:type</dt> <dd> <a itemprop="http://www.w3.org/1999/02/22-rdf-syntax-ns#type" href="http://schema.org/TechArticle">schema:TechArticle</a> </dd> <dt>schema:name</dt> <dd> <span itemprop="http://schema.org/name">Chapter脗聽6.脗聽Administration</span> </dd> <dt>schema:copyrightHolder</dt> <dd> <a itemprop="http://schema.org/copyrightHolder" href="nodeID://b78672">_:vb78672</a> </dd> <dt>schema:datePublished</dt> <dd> <span itemprop="http://schema.org/datePublished">2016-09-09 16:16:54</span> </dd> <dt>schema:headline</dt> <dd> <span itemprop="http://schema.org/headline">Chapter脗聽6.脗聽Administration</span> </dd> <dt>schema:keywords</dt> <dd> <span itemprop="http://schema.org/keywords">OpenLink,Virtuoso,database,RDBMS,relational,SQL,RDF,triple store,linked data,linked open data,Big Data</span> </dd> <dt>schema:license</dt> <dd> <a itemprop="http://schema.org/license" href="http://creativecommons.org/licenses/by/4.0/deed.en_US">n5:deed.en_US</a> </dd> <dt>schema:publisher</dt> <dd> <a itemprop="http://schema.org/publisher" href="nodeID://b78671">_:vb78671</a> </dd> <dt>schema:url</dt> <dd> <a itemprop="http://schema.org/url" href="http://docs.openlinksw.com/virtuoso/ch-server/">n2:</a> </dd> </dl> <dl itemscope="itemscope" itemid="nodeID://b78671"> <dt>Subject Item</dt> <dd>_:vb78671</dd> <dt>rdf:type</dt> <dd> <a itemprop="http://www.w3.org/1999/02/22-rdf-syntax-ns#type" href="http://schema.org/Organization">schema:Organization</a> </dd> <dt>schema:name</dt> <dd> <span itemprop="http://schema.org/name">OpenLink Software</span> </dd> <dt>schema:url</dt> <dd> <a itemprop="http://schema.org/url" href="http://www.openlinksw.com/#this">n4:this</a> </dd> </dl> <dl itemscope="itemscope" itemid="nodeID://b78672"> <dt>Subject Item</dt> <dd>_:vb78672</dd> <dt>rdf:type</dt> <dd> <a itemprop="http://www.w3.org/1999/02/22-rdf-syntax-ns#type" href="http://schema.org/Organization">schema:Organization</a> </dd> <dt>schema:name</dt> <dd> <span itemprop="http://schema.org/name">OpenLink Software</span> </dd> <dt>schema:url</dt> <dd> <a itemprop="http://schema.org/url" href="http://www.openlinksw.com/#this">n4:this</a> </dd> </dl> </div> </div> <div class="rdfa" style="display: none"> <div class="container-fluid"> <div class="navbar navbar-expand-md sticky-top navbar-light bg-light"> <a class="navbar-brand" href="#" onclick="javascript:history.go(-1); return false;">SPARQL | </a> </div> <p>This HTML document contains 15 embedded RDF statements represented using (X)HTML+RDFa notation.</p> <p>The embedded RDF content will be recognized by any processor of (X)HTML+RDFa.</p> <h3>Namespace Prefixes</h3> <table class="table table-striped table-sm table-borderless"> <thead> <tr> <th>Prefix</th> <th>URI</th> </tr> </thead> <tbody> <tr> <td>xmlns:schema</td> <td>http://schema.org/</td> </tr> <tr> <td>xmlns:n5</td> <td>http://creativecommons.org/licenses/by/4.0/</td> </tr> <tr> <td>xmlns:n2</td> <td>http://docs.openlinksw.com/virtuoso/ch-server/</td> </tr> <tr> <td>xmlns:rdf</td> <td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td> </tr> <tr> <td>xmlns:n4</td> <td>http://www.openlinksw.com/#</td> </tr> <tr> <td>xmlns:xsdh</td> <td>http://www.w3.org/2001/XMLSchema#</td> </tr> </tbody> </table> <h3>Statements</h3> <table class="table table-striped table-sm table-borderless"> <thead> <tr> <th>Subject</th> <th>Predicate</th> <th>Object</th> </tr> </thead> <tbody about="[n2:]"> <tr> <td>n2:</td> <td>rdf:type</td> <td rel="rdf:type" resource="[schema:TechArticle]">schema:TechArticle</td> </tr> <tr> <td>n2:</td> <td>schema:name</td> <td property="schema:name">Chapter脙聜脗聽6.脙聜脗聽Administration</td> </tr> <tr> <td>n2:</td> <td>schema:copyrightHolder</td> <td rel="schema:copyrightHolder" resource="[_:vb78672]">_:vb78672</td> </tr> <tr> <td>n2:</td> <td>schema:datePublished</td> <td property="schema:datePublished">2016-09-09 16:16:54</td> </tr> <tr> <td>n2:</td> <td>schema:headline</td> <td property="schema:headline">Chapter脙聜脗聽6.脙聜脗聽Administration</td> </tr> <tr> <td>n2:</td> <td>schema:keywords</td> <td property="schema:keywords">OpenLink,Virtuoso,database,RDBMS,relational,SQL,RDF,triple store,linked data,linked open data,Big Data</td> </tr> <tr> <td>n2:</td> <td>schema:license</td> <td rel="schema:license" resource="[n5:deed.en_US]">n5:deed.en_US</td> </tr> <tr> <td>n2:</td> <td>schema:publisher</td> <td rel="schema:publisher" resource="[_:vb78671]">_:vb78671</td> </tr> <tr> <td>n2:</td> <td>schema:url</td> <td rel="schema:url" resource="[n2:]">n2:</td> </tr> </tbody> <tbody about="[_:vb78671]"> <tr> <td>_:vb78671</td> <td>rdf:type</td> <td rel="rdf:type" resource="[schema:Organization]">schema:Organization</td> </tr> <tr> <td>_:vb78671</td> <td>schema:name</td> <td property="schema:name">OpenLink Software</td> </tr> <tr> <td>_:vb78671</td> <td>schema:url</td> <td rel="schema:url" resource="[n4:this]">n4:this</td> </tr> </tbody> <tbody about="[_:vb78672]"> <tr> <td>_:vb78672</td> <td>rdf:type</td> <td rel="rdf:type" resource="[schema:Organization]">schema:Organization</td> </tr> <tr> <td>_:vb78672</td> <td>schema:name</td> <td property="schema:name">OpenLink Software</td> </tr> <tr> <td>_:vb78672</td> <td>schema:url</td> <td rel="schema:url" resource="[n4:this]">n4:this</td> </tr> </tbody> </table> </div> </div> <script type="text/javascript"> $(document).xpath("//div[contains(@class,'embeddedsparql') and @id and @data-oplembed-target and @data-oplembed-template]").each( function(idx, datid) { var id = $(datid).attr("id"); var data= embedToData(id, 0); var dest= $(datid).attr("data-oplembed-target"); var templt= $("#"+id).attr("data-oplembed-template"); if(typeof embedDataPreHook === "function") { embedDataPreHook(datid); } if(typeof embedDataFixes === "function") { $("#"+dest).loadTemplate($("#"+templt), data, {complete: embedDataFixes}); } else { $("#"+dest).loadTemplate($("#"+templt), data); } if(typeof embedDataPostHook === "function") { embedDataPostHook(datid); } $(datid).toggle(false); } ) </script> </body> </html>

CINXE.COM

Chapter聽6.聽Administration