| Prev | Status Codes and Messages | Next |
2300 to 2399
Named Database Status Codes
This section lists the status codes you can receive when using the named database features of the Pervasive.SQL V8 engine.
2300: No more database names are defined
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.
2301: The database name is invalid
Not a named database. Verify you have entered a valid database name.
2302: Invalid buffer length
The size of the sending buffer is too small and needs to be increased.
2303: The database name must be unique; the specified database name already exists
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.
2304: The database type is invalid
While creating a database, you specified an invalid database type. Specify a database type of either bound or unbound.
2305: The specified path for data dictionary or data file locations is invalid
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.
2306: DBNAMES.CFG could not be updated
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.
2307: Cannot open DBNAMES.CFG file
- If you are trying to access the workstation DBNAMES.CFG file to obtain a list of database names defined for the Workgroup engine, ensure that the DBNAMES.CFG file is in your Windows directory or in the directory specified by the Database Names Directory configuration option. Either the location you have specified in the registry is incorrect or the registry key is corrupt. Use either of the following recovery solutions:
HKEY_LOCAL_MACHINE4SOFTWARE4Pervasive Software4Database Names4Version 84Settings4DBNamesDirectory
NOTE: The DBNames.cfg file should be located in the WINNT directory on Microsoft Windows NT or Windows 2000 or SYS:SYSTEM on a Novell NetWare server.
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
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.
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
| Prev 2200 to 2299 |
Contents Up Check for Revisions | Next 3000 to 3099 |