Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
FAQ: Fixing the issue with l6 in the 4.2 Transpor database Adlib Information Systems Copyright © 2012 Adlib Information Systems B.V. ® All rights reserved. Adlib® is a product of Adlib Information Systems B.V. ® The information in this document is subject to change without notice and should not be construed as a commitment by Adlib Information Systems. Adlib assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a licence and may be used or copied only in accordance with the terms of such a licence. While making every effort to ensure the accuracy of this document, products are continually being improved. As a result of continuous improvements, later versions of the products may vary from those described here. Under no circumstances may this document be regarded as a part of any contractual obligation to supply software, or as a definitive product description. Identification and solution Identifying the cause of the problem An early version of the 4.2 model application may have issues due to a missing or corrupted index on the link reference tag l6 (lower-case L, number 6). The issues can cause different errors when you create preferred-term relations in the Persons and institutions data source (the People database) or when deleting name records from that data source since the feedback mechanism for the People database in 4.2 needs an index l6 from the Transpor database. Errors which may indicate this problem are: 24 (BTREE error) or error 94 (in CBF, error searching index file) when saving a record with a preferred name, 189 (in SQL, general ODBC error), “Error: Cannot write to file data+people, field <EH>, linkref <l6>”, “Duplicate index table name found: depositr, index tags: l3 and l6” and/or problems with removing record locks from within Designer, or an error when Adcopy fails to copy transpor.inf. Before solving it, we must find out exactly what is the matter with the index on l6. It might be one of the following four possibilities: 1. The index hasn’t been defined at all in the Transpor database. Open your applications \data folder in the Application browser of Adlib Designer. Open the Indexes node underneath the Transpor database. Check if there’s an index on l6 called depos_co. If there isn’t one you’ve located the cause. 2. The second possibility is that there exists an index on l6, but with the name dpositr, which also happens to be the name of the index on l3. This is a problem in SQL databases: l6 would not have its own index table in this case. 3. When you are using CBF database, it is also possible that an index on l6 has indeed been defined, while the physical transpor.017 index file doesn’t exist. You can check this by examining your Adlib \data folder in Windows explorer. 4. The fourth possibility, also for CBF, is that the index definition is okay and the physical transpor.017 index file exists but has been corrupted somehow. Solutions When you’ve identified the cause of the problem in the paragraph above, check the corresponding solution below to fix it. 1. If the problem is that the index hasn’t been defined, you’ll have to do that now. Open your applications \data folder in the Application browser of Adlib Designer. Right-click the Indexes node underneath the Transpor database and choose New > Index in the popup menu. Enter the properties of the new index, with depos_co as the Internal name, Key type Integer, Tags to index l6 (lower-case L, number 6) and leave the other options as they are. Then save the changes in de Transpor database and reindex the new index, for instance by clicking the Re-index button on the depos_co Index properties tab. See the Designer Help for more information about creating indexes. Restart Adlib and check if the problems are solved. 2. If the problem is that there exists an index on l6, but with the name dpositr, which also happens to be the name of the index on l3, then proceed as follows: open your applications \data folder in the Application browser of Adlib Designer. Open the Indexes node and delete the current index on l6. Save the changes in the Transpor database. Right-click the Indexes node underneath the Transpor database and choose New > Index in the pop-up menu. Enter the properties of the new index, with depos_co as the Internal name, Key type: Integer, Tags to index l6 (lower-case L, number 6) and leave the other options as they are. Then save the changes in de Transpor database and reindex the new index, for instance by clicking the Re-index button on the depos_co Index properties tab. Also reindex the depositr index on l3. See the Designer Help for more information about creating indexes. Restart Adlib and check if the problems are solved. 3. If for a defined CBF index on l6 the physical transpor.017 index file doesn’t exist, you must simply reindex the index to create the file: open your applications \data folder in the Application browser of Adlib Designer. Reindex the depos_co index, for instance by clicking the Re-index button on its Index properties tab. See the Designer Help for more information about managing indexes. Restart Adlib and check if the problems are solved. 4. If the CBF index has been defined as it should, and the physical transpor.017 index file is present too, you can try deleting the transpor.017 file from the Adlib \data folder from within Windows Explorer, and then reindexing the depos_co index: open your applications \data folder in the Application browser of Adlib Designer. Reindex the depos_co index, for instance by clicking the Re-index button on its Index properties tab. See the Designer Help for more information about managing indexes. Restart Adlib and check if the problems are solved. Remarks If you had problems with locked records, try to unlock them now (after your index changes) using the Record lock manager in Adlib Designer. If you do not have Adlib Designer (because you have an Adlib Basis application), then please contact our helpdesk for assistance. 28-7-2017