> so, I can see the journal file in my work directory which I own (and > in which the db file is placed). > > still constantly, I have a disk I/O ERROR which I don't understand.
If you see journal file along your database file and each attempt to open database doesn't delete journal file it means you either don't have write permissions on database file, or you don't have write permissions on journal file, or you don't have write permissions on directory, so that SQLite cannot delete journal. Note: don't delete journal yourself - SQLite have to see it. You can make a copy of it and try to delete just to check your permissions, but then you should restore journal from backup and open database file with SQLite. Pavel On Fri, Dec 9, 2011 at 7:04 PM, Tal Tabakman <tal.tabak...@gmail.com> wrote: > Hi, > > thanks a lot. > > so, I can see the journal file in my work directory which I own (and > in which the db file is placed). > > still constantly, I have a disk I/O ERROR which I don't understand. > > the db is only 64M on disk and I have plenty of space. > > how can I get to the bottom of this ? > > can it be related not to the indexing, but rather to something bad > that happened during the db creation ? > > please advice > > Tal > >>* so, I don't have TMPDIR defined in my env. what is the behaviour of*>* >>sqlite in such cases ? is there a default ?* > The journal file will be created in the same directory as the database > file. For this to work, your application and user must have enough > privilages to create a new file in that directory. > > Simon. > > > On Sat, Dec 10, 2011 at 1:01 AM, Tal Tabakman <tal.tabak...@gmail.com>wrote: > >> Hi, >> >> thanks for the reply. >> >> so, I don't have TMPDIR defined in my env. what is the behaviour of sqlite >> in such cases ? is there a default ? >> >> cheers >> >> Tal >> >> On 12/09/2011 04:02 PM, Tal Tabakman wrote: >> >* Hi Guys,*>* I have an SQLITE database of 1.5 million rows in a single >> >table*>* each raw looks like:*>**>* >> >1499999|25|439198507|-1|0|1|44954|24|17|31|9|9|-1|-1|*>**>* now, from the >> >sqlite command line interface I am creating an INDEX on a sinGle*>* integer >> >column*>**>* CREATE INDEX IND1 ON ENTRIES (snum)*>**>* the result I get >> >is:*>**>* Error: disk I/O error*>**>* can you advice how to debug this one >> >?* >> You might be running out of space wherever temporary >> tables are stored on your system. >> >> If you're on unix, try changing environment variable >> TMPDIR to point to somewhere you have lots of free disk >> space (say three times the size of the eventual index). >> >> Or (I think) environment variable TMP or TEMP on Windows. >> >> >> > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
