Unable to open index.db

Hello,
I have a problem on DI in one of the folders of the indexer/share the new indexer.db.xxx files are no longer created
the error I got is this:

---------------------

2019-04-23 16:45:02 INFO: V-378-0-0: #{5380} Product Version 6.1.4.9935
2019-04-23 16:45:02 INFO: V-378-1301-1: #{5380} Starting Index Writer
2019-04-23 16:45:02 INFO: V-378-1301-1: #{5380} [ D:\Program Files\DataInsight\bin\idxwriter.exe --indexdir D:\DataInsight\data\indexer\default\2\2 --maxperrun 300000000 --logfile --events D:\DataInsight\data\inbox\audit_mrg_cifs_2_1556030700011000_1.sqlite ]
2019-04-23 16:45:02 INFO: V-378-1301-1: #{5380} sqlite configuration successful
2019-04-23 16:45:02 INFO: V-378-1306-76: #{5380} [dbhandle_file_copy: 670] File copy time for D:\DataInsight\data\indexer\default\2\2/index.db.10313: 0 microseconds2019-04-23 16:45:02 ERROR: V-378-1301-1: #{5380} Unable to open index ("D:\DataInsight\data\indexer\default\2\2"). error=1
2019-04-23 16:45:02 ERROR: V-378-1301-1: #{5380} Unable to open index ("D:\DataInsight\data\indexer\default\2\2"). error=1
2019-04-23 16:45:02 INFO: V-378-1301-1: #{5380} Exiting Index Writer [ 1 ]

---------------------------------------------------------------------------------------------------------

[ERR] ================================================================================
[ERR] INDEX: 2 (D:/DataInsight/data/indexer/default/2/2)
[ERR] FILER: XXXXXXXXXX
[ERR] SHARE: vol_dirdfs_XX
[ERR] HELPER: 0
[ERR] 2019-04-08 18:01:56 INFO: V-378-0-0: #{6816} Product Version 6.1.3.9925
[ERR] 2019-04-08 18:01:56 ERROR: V-378-1306-67: #{6816} [dbhandle_open_read: 1290] SQLITE Error: unable to open database file 14
[ERR] Unable to open index reader. err=14
[ERR] 2019-04-08 18:01:56 INFO: V-378-0-0: #{8284} Product Version 6.1.3.9925
[ERR] 2019-04-08 18:01:56 ERROR: V-378-1306-67: #{8284} [dbhandle_open_read: 1290] SQLITE Error: unable to open database file 14
[ERR] Unable to open index reader. err=14
[ERR] 2019-04-08 18:01:56 INFO: V-378-0-0: #{7428} Product Version 6.1.3.9925
[ERR] 2019-04-08 18:01:56 ERROR: V-378-1306-67: #{7428} [dbhandle_open_read: 1290] SQLITE Error: unable to open database file 14
[ERR] Unable to open index reader. err=14
[ERR] 2019-04-08 18:01:56 INFO: V-378-0-0: #{6632} Product Version 6.1.3.9925
[ERR] 2019-04-08 18:01:56 ERROR: V-378-1306-67: #{6632} [dbhandle_open_read: 1290] SQLITE Error: unable to open database file 14
[ERR] Unable to open index reader. err=14
[ERR] 2019-04-08 18:01:57 INFO: V-378-0-0: #{6068} Product Version 6.1.3.9925
[ERR] 2019-04-08 18:01:57 ERROR: V-378-1306-67: #{6068} [dbhandle_open_read: 1290] SQLITE Error: unable to open database file 14
[ERR] Unable to open index reader. err=14
[ERR] STALE INDEXDB: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE DIRHASH: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE FILEHASH: 0 (0.00 Bytes), 0 file(s)
[ERR] STALE ACTINDEX: 0 (0.00 Bytes), 0 file(s)
[ERR] ================================================================================

I have enough space on the disc
only this index  and share has problems.
Do you have any ideas?

Tanks

Paolo Centenaro

 

 

3 Replies

Re: Unable to open index.db

Paolo this index is definitely having an issue opening.
On the indexer where you pulled the info from the idxcheck.0.log, which ran last Monday - you can check the other iterations .1, .2 going back for weeks to see when it occurred - can you verify the index is present?
> dir C:\Datainsight\data\indexer\default\2\2\*db*

It is important to note that if the disk filled up and the index was open in an active thread it may be corrupted. This may not apply to you as it is likely all threads would not properly close and you indicate you have only one index with issues but, if large, it could have been the only active thread and there are other causes so let us proceed with some basic troubleshooting.

We free up disk space on failures / successes to committing data to the database. That would leave the appearance of available disk even if there was none available. The stats for the indexer in the GUI or the watchdog log would provide you a more historical view of the range of disk you had available.

First while I suggest you open a incident case with Veritas Support for interactive and timely responses let me give you a couple of suggestions. We would want to see if your index could be read, clears a checkup or is too large to be copied to disk, etc.

Let us do these things and see if you are experiencing issues so you'll have a better understanding of where to look.

Can you just read from the index

C:\rod>idxreader.exe -i C:\Datainsight\data\indexer\default\2\2 -a -c 5 --sort dsc

NOTE: read from index on share 2 all activity listing out 5 in descending order

Success looks like:
Events between (Thu 01 Jan 00:00:00 1970 GMT - Thu 01 Jan 00:00:00 1970 GMT):
# timestamp pathtype pathname sid opcode count ipaddress
1 "Wed 30 May 00:39:00 2018 GMT" "file" "/Payroll/RLindsey_109.txt"
"S-1-5-21-470185602-4083902143-2641307348-4443" delete 1 0.0.0.0
2 "Wed 30 May 00:39:00 2018 GMT" "file" "/Support/LCampos_1681.txt"
"S-1-5-21-470185602-4083902143-2641307348-5104" read 1 0.0.0.0
3 "Wed 30 May 00:39:00 2018 GMT" "file" "/Support/LJensen_1686.txt"
"S-1-5-21-470185602-4083902143-2641307348-5104" read 1 0.0.0.0
4 "Wed 30 May 00:39:00 2018 GMT" "file" "/Support/LMccray_1686.txt"
"S-1-5-21-470185602-4083902143-2641307348-5104" read 1 0.0.0.0
5 "Wed 30 May 00:39:00 2018 GMT" "file" "/Support/MAndrews_1688.txt"
"S-1-5-21-470185602-4083902143-2641307348-5104" read 1 0.0.0.0

Total Events: 5 (delete=1, read=4)
Timespan for Events: 1527640740-1527640740 (Wed 30 May 00:39:00 2018 GMT-Wed 30
May 00:39:00 2018 GMT)
Results generated in: 78.13 milliseconds


Does it show corruption or clear a checkup?

If not in your path change to the DI installdir$ folder - typically C:\Program Files\DataInsight\ - and go to the binaries folder like:

>cd "C:\Program Files\DataInsight\bin"

run:

C:\Program Files\DataInsight\bin> sqlite3 C:\Datainsight\data\indexer\default\2\2\index.db.783 "pragma quick_check";

Where 783 is altered to the actual iteration number of your file

you are looking for an OK for integrity in your version or can report any error like 11 corruption, 14 unable to read (likely corruption), etc. You can check the meaning of the code at https://www.sqlite.org/c3ref/c_abort.html

What size is it? In relation to free space is there sufficient room for a copy on disk and the data to be indexed?

> do a directory listing as above.

if you do have a corrupted index you may be able to restore a properly backed up folder, can recreate it losing all historical information or could seek assistance on options available from the professionals at Veritas.

 

Hopefully that gives you some ammunition to consider your options.


Rod

Re: Unable to open index.db

Hi Rod. Thanks for your info. I have no problems with the disk space or about 100 GB available. The index should be around 4 GB, this is the situation of the folder: Mode LastWriteTime Length Name ---- ------------- ------ ---- -a--- 5/1/2019 12:00 AM 6144 archivelog_2.6.db -a--- 11/7/2016 8:45 PM 57344 custodian.db -a--- 4/23/2019 12:31 PM 24576 index.db.10804 -a--- 5/2/2019 8:45 AM 0 index.db.10804.lck -a--- 1/8/2019 1:38 AM 0 index.db.7568 - Copy.lck -a--- 5/2/2019 8:45 AM 65 index.db.helper -a--- 11/7/2016 1:33 PM 0 index.db.wlck -a--- 6/26/2017 12:34 PM 16384 ptag.db.1 -a--- 6/26/2017 2:12 PM 0 ptag.db.1.lck -a--- 6/26/2017 12:34 PM 13 ptag.db.helper -a--- 6/26/2017 12:34 PM 0 ptag.db.wlck -a--- 6/26/2017 12:34 PM 49152 tag.db.2 -a--- 6/26/2017 2:00 PM 0 tag.db.2.lck -a--- 6/27/2017 4:51 AM 114688 tag.db.7 -a--- 6/27/2017 6:44 AM 0 tag.db.7.lck -a--- 6/27/2017 11:49 PM 139264 tag.db.9 -a--- 6/28/2017 12:12 AM 0 tag.db.9.lck -a--- 6/27/2017 11:49 PM 39 tag.db.helper -a--- 11/7/2016 1:33 PM 0 tag.db.wlck -a--- 1/8/2019 1:02 PM 442368 userrisk_attack_surface.db.653 -a--- 1/8/2019 11:00 PM 0 userrisk_attack_surface.db.653.lck -a--- 1/8/2019 1:02 PM 15 userrisk_attack_surface.db.helper -a--- 12/29/2016 11:00 PM 0 userrisk_attack_surface.db.wlck I tried to run the first command but it gives me a 205 error as a result: PS D:\Program Files\DataInsight\bin> idxreader.exe -i D:\Datainsight\data\indexer\default\2\2 -a -c 5 --sort dsc Unable to get activity between Thu 01 Jan 00:00:00 1970 GMT-Thu 01 Jan 00:00:00 1970 GMT. error=205 What can it be? Thank you Paolo

Re: Unable to open index.db

First I would have to ask if the index actually resides in the location of the second MSU?
This location "D:\Datainsight\data\indexer\default\2\2" is the actual location of the index files.

In your case we have many disparite dates and too small of a file.

 

4/23/2019 12:31 PM 24576 index.db.10804

5/2/2019 8:45 AM 0 index.db.10804.lck

1/8/2019 1:38 AM 0 index.db.7568 Copy.lck

5/2/2019 8:45 AM 65 index.db.helper

11/7/2016 1:33 PM 0 index.db.wlck

Likely you should consult with Veritas Technical Support and get a technician on you machine to allow for an interactive investigation into the problem.


Rod