TimesTen datastore的DBI文件被删了如何恢复？

解决办法是重建一个DBI文件，具体做法是：1、把datastore数据文件移走；2、ttisql 连接datastore，这样会生成DBI文件；3、卸载掉datastore，把数据文件挪回，重新装载，ok。

以下是MOS针对这个问题的解决方案：

TT10003 Unexpected data store file exists for new data store

Symptoms

The daemon attempts to load a new data store, but finds there is an existing checkpoint file with that name in the checkpoint directory it uses. When this occurs it reports the following error:

Error in sql_initialize: ERROR in TTConnection.cpp, line 220: TTConnection::Connect() -- while connecting to driver [TimesTen][TimesTen 7.0.5.2.0 ODBC Driver][TimesTen]TT10003: Unexpected data store file exists for new data store: //TEST_DS.ds0. -- file "db.c", lineno 9350, procedure "sbDbConnect" *** ODBC Error/Warning = S1000, TimesTen Error/Warning = 10003 *** (connect string )

Cause

The main daemon keeps track of data stores using DBI (Database Information) Files.
The location of these files are the daemon home directory. At install time the default daemon home location is:
 
On UNIX, the installer suggests the use of install_dir/info if
installed as non-root or /var/TimesTen/ if running as root. 

On Windows, the install_dir\srv\info directory is used for this
purpose.

The existence of the DBI allows the daemon to provide the listing of all data stores managed to list in ttStatus output. A DBI file gets created once there is at least one data store that has been managed or created by the daemon and gets updated as new data stores are managed or created. As a data store get destroyed by ttDestroy, its entry in the DBI file gets removed. The DBI file is not a text file so do not attempt to modify it as that can cause the TT10003 error scenario.

If the complete error message matches this “TT10003: Unexpected data store file exists for new data store”, this document provides a possible solution for that if your intent is to create or copy a data store. 

The most likely scenario that lead to “Unexpected data store file exists for new data store” is that someone or script has deleted the DBI file, modified the DBI file, or moved the DBI file out of the daemon home and has attempted to load an existing data store or create a new data store. Users should never edit a DBI file. Users are also strongly advised against deleting or moving DBI files without guidance from TimesTen support.

Solution

1) If you need to keep the existing data store, You can try moving that data store’s checkpoint files and the log files from their existing location(s) to a temp location. Use ttIsql to do a first connection to the Data store so that it creates an empty version of it. Then overlay the data store’s desired checkpoint files and the transaction log files from the temp location over the location of the empty checkpoint and transaction log files.

2) If you don’t want the existing data store and want to create a new data store do a ttdestroy –force to get rid of the existing datastore so that you can create the new one. 

3) If this is a replicated system and you need to keep the existing data store and an acceptable copy exists on one of the replicated peers please follow the steps used to recover a data store from a peer.