 | Status Codes and Messages (9.1 revision 1) |  |
|
This section lists the status codes you can receive when using the named database features of the Pervasive.SQL 9 SP1 (9.1) engine.
No more database names are defined. If the buffer is large enough to hold multiple database names, you might receive this status code and still have one or more database names returned. The application should check iBufLen to determine the number of names returned.
Not a named database. Verify you have entered a valid database name.
The size of the sending buffer is too small and needs to be increased.
While creating a database, you specified a database name that already exists in the DBNAMES.CFG file. Specify a different, unique name for the database, or remove the existing database name first.
While creating a database, you specified an invalid database type. Specify a database type of either bound or unbound.
The path you specified for the bound, named database is invalid or the paths you specified for the data file locations are invalid. Ensure that the entered paths are either UNC paths or local paths (a local path for a NetWare server would be volume:path) and then retry the operation. Paths that contain mapped drive letters are not allowed.
The path you specified for the bound, named database is invalid or the paths you specified for the data file locations are invalid. Ensure that the specified paths are either UNC or local paths (a local path for a NetWare server would be volume:path) and then retry the operation. Paths that contain mapped drive letters are not allowed.
HKEY_LOCAL_MACHINE4SOFTWARE4Pervasive Software4Database Names4Version 84Settings4DBNamesDirectory
NOTE: The DBNames.cfg file should be located in the Windows system directory on Windows 32-bit platforms or SYS:SYSTEM on a Novell NetWare server.
OR
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.
While creating a database, you specified a RI flag that is not valid. Specify a database type of either integrity or non-integrity.
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.
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.
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.
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.
Pervasive.SQL 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.
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.
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.
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.
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.
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.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
These two particular parameters are not allowed to be changed at the same time. Try changing each parameter separately.
Unspecified error.
|
Chapter contents
Prev topic: 2200 to 2299
|