Creating, Modifying, Deleting, and Repairing PSQL Databases
The following tasks pertain to databases.
•
To create a new database
•
To modify properties of a database
•
To delete a database
•
To repair a database name
For conceptual information on named databases, see PSQL Database Concepts in Advanced Operations Guide.
►
To create a new database
*Note: On Linux and OS X, the owner of the directory where you want to create the database must be psql. If not, error message 7039: Dictionary path is invalid results. Use the chown command to change owner of the directory. For example, chown psql directoryname.
1
In PCC PSQL Explorer, right-click the database engine for which you want the new database.
2
Click New > Database.
The Create New Database dialog box appears (see Figure 20).
3
Provide a name for the database and a location (see Table 1, Identifier Restrictions by Identifier Type).
The name cannot be the same as an existing DSN.
Also, no two files can share the same file name and differ only in their file name extension if both files are in the same directory. For example, do not name a data file Invoice.btr and another one Invoice.mkd in the same directory. This restriction applies because the database engine uses the file name for various areas of functionality while ignoring the file name extension. Since only the file name is used to differentiate files, files that differ only in their file name extension look identical to the database engine.
4
Specify the additional options on the dialog as required for the database. See Table 10 for a discussion of the options.
►
To modify properties of a database
1
In PCC PSQL Explorer, right-click the database engine for which you want to modify the properties, then click Properties.
2
On the Properties dialog, click the tree node for which you want to specify properties:
•
Code Page
•
Directories
•
General
•
Relational Constraints
•
Security
3
Set the specific properties as required.
►
To delete a database
You cannot delete the database to which you are currently logged in. See To log out from a database engine in PSQL User's Guide.
If database security is set to Mixed or Database, you must first remove the security, or it cannot be deleted. See To turn off security using PSQL Explorer and To turn off security using SQL.
If when you delete a datase you also want to remove its DSN, then in Window > Preferences > PSQL > General, the option Always remove associated DSN entries must be selected.
1
In PCC PSQL Explorer, right-click the database that you want to delete.
2
Click Delete.
3
In the Delete Item dialog, click one of the following:
•
Yes, but only database name - Delete only the database name in dbnames.cfg.
•
Yes, database name and ddfs - Delete the database name and associated DDF files.
•
No - Cancel without deleting.
*Note: Deletion of a database does not affect its user data files.
►
To repair a database name
Using the tables (data files) from one database for a newly created database with a different name can result in the inability to open the tables for the new database. In certain situations, the tables can have the original database name bound to them. For example, if the original database is set to Bound or if Referential Integrity is being enforced, the data files are bound to that database name. (See also Bound Database versus Integrity Enforced.)
To ensure that such tables can be opened for the new database, you need to repair the database name for the new database. The tables are then associated with the new database.
1
In PCC PSQL Explorer, expand the Databases node and right-click the database name that you want to repair.
2
Click Repair Database Name.
The following table explains additional actions, if any, that are required based on security settings for the database, the tables, or both. See also Security Tasks.
Security Setting
Action Required
None
None. Repair Database Name executes without further interaction required.
Database Security
You must provide the user name Master and its password.
See also Database Security in Advanced Operations Guide.
Btrieve Security Classic
If the database engine is running on a remote server and your operating system user name and password differ between the local machine and the remote server, you must provide the user name and password for the remote server.
See also Classic in Advanced Operations Guide.
Btrieve Security Mixed
The data directories for the tables must be added to the DEFAULTDB database. See The Default Database and the Current Database in Advanced Operations Guide.
In addition, the other aspects of Mixed security are enforced, such as user names defined in the database corresponding exactly with the user names defined in the operating system. See Mixed in Advanced Operations Guide.
Btrieve Security Database
If Database Security is turned on (Master password specified), no further requirements are needed for Database Btrieve Security. The privileges for Master are sufficient.
See also Database in Advanced Operations Guide.
Owner Name for a table
If a table has an owner name, Repair Database Name prompts you for the owner name. (An exception to this is if the option “Permit read-only access without an owner name” is specified for the owner name.) See also Managing Owner Names in Advanced Operations Guide.
You can provide the owner name for an individual table, or a list of all owner names associated with the set of tables (separate each owner name with a comma and a space). By default, owner names are displayed as asterisks. If you want to view the owner names as plain text, select Show owner names.
You can omit providing an owner name for a specific table with the Skip button. To skip all tables with an owner name, select Do not ask again for owner names. Tables requiring an owner name that is unknown will be skipped then click Skip.
The number of tables skipped is reported at the end of the repair operation in a dialog box. The names of the tables skipped are written to the PCC Log.