thanks. found ticket in "ticket" but not "article so seems you are
correct. will start fixing each corrupt entry.
Neil
On Mon, Feb 20, 2012 at 11:03 AM,
Hi Neil,****
** **
It seems your DB is inconsistent. Search for that TicketID in tables “ticket” and “article”. If you find that only in one of these, my guess is correct. You have to manually solve that in the DB. Either (try to) create the appropriate missing entry or (imo better solution) delete the found entry.****
** **
Regards****
Jan Dreyer****
** **
*Von:* otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] *Im Auftrag von *Neil Simpson *Gesendet:* Samstag, 18. Februar 2012 13:56 *An:* User questions and discussions about OTRS. *Betreff:* [otrs] change from runtimedb to staticdb****
** **
Hello,****
****
i wanted to switch from runtimedb to staticdb today for "core::ticket::indexmodule" on otrs 3.0.9. Changed the value in otrs gui to staticdb, then ran the otrs.rebuildticketindex.pl script.****
****
script fails almost immediately with:****
****
message - no such ticketid (72145)****
****
has anyone come across this and knows a simple fix?****
****
ive reverted back to runtimedb for now and run the cleanup script to avoid conflicts.****
****
any help appreciated.****
****
Neil****
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs