ok, i understand, i'll give it a try, thanks

Le 13/12/2017 à 18:49, Kingsley Idehen a écrit :
On 12/12/17 9:52 AM, Thomas Michaux wrote:
Hello,

we made a dump (+backup-dump) after we found messages in virtuoso.log like these :

" There are pages in the backup set that are actually free. Should do backup_context_clear () and thus get a full backup. This can indicate corruption around page 73 81024."

Okay, but you are making a backup of data in a database where the aforementioned index is corrupt, as the system message indicates.



the dump was ok, no errors, after we saved the .db and delete it we recover by reading the .trx from previous step (+restore-crash-dump) and it was also successfull.

Yes, but you are using +restore-crash-dump against a backup of a corrupted database. You should have used +crash-dump as per:

./virtuoso -?

Usage:
  virtuoso [-fcnCbDARwMKrBd] [+foreground] [+configfile 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]
           [+backup-dirs arg] [+debug] [+pwdold arg] [+pwddba arg]
           [+pwddav arg]
  +foreground            run in the foreground
  +configfile            use alternate configuration 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*   +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
  +backup-dirs           default backup directories
  +debug                 Show additional debugging info
  +pwdold                Old DBA password
  +pwddba                New DBA password
  +pwddav                New DAV password


Kingsley


Now the problem is we have graphs but only with IRI_ID showed, no names ? is there an internal data structure to update to have the graph names back or is it definitely corrupted ?

Thanks

PS:

15:21:41 OpenLink Virtuoso Universal Server
15:21:41 Version 07.20.3217-pthreads for Linux as of Feb 10 2017
15:21:41 uses parts of OpenSSL, PCRE, Html Tidy
15:21:47 Database version 3126


graph list :

SQL> sparql select distinct ?g where {GRAPH ?g{?s a ?t}};
g
LONG VARCHAR
_______________________________________________________________________________

http://www.openlinksw.com/schemas/virtrdf#
iri_id_179939769_with_no_name_entry
b3sifp
http://www.w3.org/2002/07/owl#
iri_id_101440794_with_no_name_entry
iri_id_138171152_with_no_name_entry
iri_id_109064725_with_no_name_entry
iri_id_120447918_with_no_name_entry
iri_id_122475737_with_no_name_entry
iri_id_126542051_with_no_name_entry
iri_id_134423479_with_no_name_entry
iri_id_126235267_with_no_name_entry
iri_id_130855391_with_no_name_entry
iri_id_182388251_with_no_name_entry
iri_id_115082563_with_no_name_entry
iri_id_107233893_with_no_name_entry
iri_id_176955935_with_no_name_entry
iri_id_138170213_with_no_name_entry
http://localhost:8890/sparql
iri_id_120447899_with_no_name_entry
iri_id_126235266_with_no_name_entry
iri_id_111093750_with_no_name_entry
iri_id_111317575_with_no_name_entry
iri_id_115156110_with_no_name_entry
iri_id_169252958_with_no_name_entry
iri_id_184144716_with_no_name_entry
iri_id_176961926_with_no_name_entry
iri_id_104573215_with_no_name_entry
iri_id_126542040_with_no_name_entry
iri_id_173680485_with_no_name_entry
iri_id_169407489_with_no_name_entry
virtrdf-label
iri_id_102730058_with_no_name_entry
iri_id_113150701_with_no_name_entry
iri_id_126920998_with_no_name_entry

35 Rows. -- 3384 msec.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


--
Regards,

Kingsley Idehen 
Founder & CEO
OpenLink Software   (Home Page:http://www.openlinksw.com)

Weblogs (Blogs):
Legacy Blog:http://www.openlinksw.com/blog/~kidehen/
Blogspot Blog:http://kidehen.blogspot.com
Medium Blog:https://medium.com/@kidehen

Profile Pages:
Pinterest:https://www.pinterest.com/kidehen/
Quora:https://www.quora.com/profile/Kingsley-Uyi-Idehen
Twitter:https://twitter.com/kidehen
Google+:https://plus.google.com/+KingsleyIdehen/about
LinkedIn:http://www.linkedin.com/in/kidehen

Web Identities (WebID):
Personal:http://kingsley.idehen.net/public_home/kidehen/profile.ttl#i
         
:http://id.myopenlink.net/DAV/home/KingsleyUyiIdehen/Public/kingsley.ttl#this



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users

Reply via email to