Hi Martín, > I think one of our DB seems to have gotten corrupt. I wonder if there's > a command that will recover it.
Unfortunately, that's generally a difficult task. However, it may be important to find out how the problem was caused: Can you tell if there was any update that was manually interrupted? Christian Issuing REPLACE or OPTIMIZE on it will > result in "Out of Main Memory" errors. We have DBs that occupy more space > and have more documents, so I assume the problem must be that this DB broke > somehow. I've tried raising the -Xmx parameter to 1024m, but still get the > same "Out of Main Memory" error. > > Thanks, > Martín. > > INSPECT > Checking main table (11292441 nodes): > - 0 invalid node kinds > - 0 invalid parent references > - 87 wrong parent/descendant relationships (pre: 10932445,..) > Warning: Database is inconsistent. > > > INFO DB > Database Properties > Name: OrderInquiryV2_1 > Size: 2138 MB > Nodes: 11292441 > Documents: 251980 > Binaries: 0 > Timestamp: 2015-09-10T16:40:29.000Z > > Resource Properties > Timestamp: 2015-09-08T23:11:28.497Z > Encoding: UTF-8 > CHOP: false > > Indexes > Up-to-date: false > TEXTINDEX: false > ATTRINDEX: false > FTINDEX: false > LANGUAGE: English > STEMMING: false > CASESENS: false > DIACRITICS: false > STOPWORDS: > UPDINDEX: false > AUTOOPTIMIZE: false > MAXCATS: 100 > MAXLEN: 96 >
