2300 to 2399

Note: In most Windows operating systems, the key is HKEY_LOCAL_MACHINE\SOFTWARE\PERVASIVE SOFTWARE. However, its location under HKEY_LOCAL_MACHINE\SOFTWARE can vary depending on the operating system.

The value should be 0 (for local) or 1 (for server) but in some cases the value is a number like 23785. In this case, status 2307 was returned while trying to create a data source in the ODBC Administrator and specifying a data path to the DDF directory. Deleting the MicroKernel Router key resolved the problem.

2308: The specified RI flag is invalid

While creating a database, you specified a RI flag that is not valid. Specify a database type of either integrity or non-integrity.

2309: The database is in use

You cannot modify the definition of a named database if another user is modifying the definition or if a user is connected to it. You also cannot connect to a named database if someone is modifying its definition.

2312: The bound database cannot share table data files

You cannot bind a data file referenced by a table in a bound, named database to another named database, or to another table in the same named database. For more information about bound databases, refer to Advanced Operations Guide.

2313: The bound database cannot share data dictionary files

The data dictionary files for a bound, named database cannot be referenced by another named database. For more information about bound databases, refer to Advanced Operations Guide.

2314: Cannot create DBNAMES.CFG file

An error occurred while attempting to generate the DBNAMES.CFG. The DBNAMES.CFG is created when the first database on the system is created. If the workstation DBNAMES.CFG file is being generated, ensure that the Windows directory in the Database Names Directory configuration option is a valid directory.

2316: Cannot create DDF files for the bound database

PSQL cannot create the database files for the bound database. Ensure that the data dictionary files do not already exist at the specified location. Remove any existing data dictionary files before creating the bound, named database. For more information about bound databases, refer to Advanced Operations Guide.

2324: Data dictionary files are not bound

The data dictionary files for the specified named database are not bound, but should be. This normally indicates a situation in which the data dictionary files have been restored from a backup prior to the database being bound. Make sure that you restore your data dictionary from a backup which is consistent with the bound state of the databases. For more information about bound databases, refer to Advanced Operations Guide.

2325: Data dictionary files are already bound

The data dictionary files for the specified named database are already bound to another database. However, the other named database is not defined to the engine that is trying to bind or unbind the database. Make sure that you only reference the data dictionary files for a bound database from one engine. For more information about bound databases, refer to the Advanced Operations Guide.

2326: Data dictionary files are bound, but do not need to be bound

An unbound, named database was checked. This does not indicate an invalid, or corrupted, named database, but does indicate an inconsistency between the named database definition and the actual state of the database.

This status code often indicates a situation in which the data dictionary files have been restored from a backup that was made when the database was bound. Either restore the data dictionary from a backup that is consistent with the bound state of the database, or bind and then unbind the database. The unbinding of the database removes the binding information from the data dictionary files.

2329: Data file for a table is not bound

The data file for a table in the database is not bound, but should be. This normally indicates a situation in which the data files for the database have been restored from a backup prior to the database being bound. Make sure that you restore your data from a backup that is consistent with the bound state of the database.

2330: Data file for a table is bound, but does not need to be bound

An unbound, named database was checked. This does not indicate an invalid, or corrupted, named database but does indicate an inconsistency between the named database definition and the actual state of the database. This status code often indicates a situation in which the data files for the database was bound. Either restore your data files from a backup that is consistent with the bound state of the database, or bind and then unbind the database.

The unbinding of the database removes the binding information from the data files if the binding information is no longer needed.

2331: Not allowed to change data dictionary location and change name at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2332: Not allowed to bind database and change name at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2333: Not allowed to unbind database and change name at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2334: Not allowed to create a data dictionary files and change name at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2335: Not allowed to change data locations and change name at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2336: Not allowed to change data dictionary location and bind database at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2337: Not allowed to change data dictionary location and unbind database at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2338: Not allowed to change the dictionary location and create dictionary files at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2339: Not allowed to create data dictionary files and bind database at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2340: Not allowed to create data dictionary and unbind database at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2341: Not allowed to bind database and change data locations at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2342: Not allowed to unbind database and change data locations at the same time

These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.

2343: Named database general error

Unspecified error.