Errors in Functions and Opening Databases

Problem 1: Any	“File is not a valid database”; “PDF Open Error”
	I attempt to open an old database and get the following message in a dialog box: File is not a valid database In the root window (the window from which Patran was run) I see the messages: PDB ERROR : PDF OPEN ERROR: Can’t XDR decode the header block. PDF ERROR: File ‘/tmp/blair/template.db’ is probably not a pdf file. PDB ERROR : CMF_FILE_PROB_NOT_PDF - File is probably not a pdf file. p3convert 7.0 initiated at Wed Apr 1 11:05:02 PST 1999 Creating (or updating) marker file for /tmp/blair/template.db /msc/patran/bin/exe/dbVersion[57]: /usr/interbase/bin/qli: not found. /msc/patran/bin/exe/dbVersion[70]: /usr/interbase/bin/qli: not found.
Resolution 1:	The PDB errors indicate that the PDB database system does not recognize this file as a PDB database. This typically means that the file is an older Patran database and is in InterBase format. PDB automatically spawns p3convert. See Upgrading Databases, 74 for information on the p3convert utility. In this case, p3convert fails with dbVersion errors. This indicates that /usr/interbase does not exist or is not properly installed. InterBase is required to convert Patran databases from versions prior to version 8.

Problem 2:	“PDF Open Error: Can’t open file”; “File’s schema version doesn’t match”
Any	I attempt to open an old database and get the following message in the root window (the window from which Patran was run): PDB ERROR : PDF OPEN ERROR: Can’t open file ‘<database>’ PDF ERROR: File’s schema version: ‘PATRAN_2_1_a’ doesn’t match requested version PDB ERROR : CMF_FILE_BAD_SCHEMA_VER - File schema version does not match Requested file not a valid database
Resolution 2:	These errors indicate that the database schema version is not recognized as a Patran database for the current or an earlier version. The most likely cause is an attempt to open a database from a later version of Patran. For example, opening a version 9 database in version 8.5 will produce a message similar to the above.

Problem 3: Any	No permission for REVOKE access; p3convert_1x12 failed
	I attempt to open an old database and get the following message in a dialog box: File is not a valid database In the root window (the window from which Patran was run) I see messages such as: Invoking p3convert_1x12.... .... Updating the ANALYSIS_ELEMENT_SUMMARY records. Enabling the relation triggers. no permission for REVOKE access to TABLE$USER_PRIVILEGES ***Error: p3convert_1x12 failed
Resolution 3:	Patran is using InterBase to upgrade a pre-version 8.0 database. The problem stems from an earlier version of InterBase which placed the creators name as the owner of the database. If a different user attempts to upgrade the database he/she is denied permission. This problem should not occur on Windows NT databases. A script is provided with Patran which will correct this problem. At the UNIX prompt, execute the following command: % $P3_HOME/bin/fixDb <database_name.db> Open the file in Patran and it will convert properly.

Problem 4: Unix	Cannot be opened for write access. It may already be in use.
	I attempt to open a new or existing database in an NFS mounted directory and get a message in the UNIX window: dbname.db cannot be opened for write access. It may already be in use by another process, or may lack the necessary permissions. Cannot continue.
Resolution 4:	Patran, like any software using file locking, requires NFS and RPC file locking daemons on the client and NFS server. These names of these daemons will be differ between platforms. For example, on a SUN Solaris NFS server the following daemons are required: /usr/lib/nfs/lockd /usr/lib/nfs/mountd /usr/lib/nfs/statd

Problem 5: Linux	Objects cannot be rotated using two button mouse
	I have a two button mouse. Pressing both buttons at the same time does not seem to emulate the third button and I am unable to rotate items in Patran
Resolution 5:	Assuming that you have installed the Linux drivers associated with your mouse, check the XF86config file (part of XFree86). You can turn on/off middle mouse button emulation. Note that XFree will look at XF86config-4 etc. before looking at XF86config.

Problem 6: Unix	Updating NODE records; p3convert_1x12 failed
	I attempt to open an old database and get the following message in a dialog box: File is not a valid database In the root window (the window from which Patran was run) I see messages such as: Invoking p3convert_1x12.... .... Updating the NODE records. ***Error: p3convert_1x12 failed This error will always occur immediately after the NODE update.
Resolution 6:	Patran is using InterBase to upgrade a pre-v8.0 database. The problem stems from an earlier version of Patran which incorrectly wrote certain Node information. The p3convert_1x12 utility does not recognize the information. This problem should not occur on Windows NT databases. A utility is provided with Patran which will correct this problem: 1. The database must be at schema version 1.11 (equivalent to v6.2) for the utility to work properly. Use the following command to determine the current version: % $P3_HOME/bin/dbVersion -p <database_name.db> 1.10 The value returned is the current schema version. Run the individual p3convert utilities to bring the schema version to 1.11. The p3convert_1x10 updates a 1.09 database to 1.10, p3convert_1x11 a 1.10 database to 1.11, etc. For the above example: % $P3_HOME/bin/p3convert_1x11 <database_name.db> 2. Run the chkdb62 utility to fix the database: % $P3_HOME/bin/chkdb62 <database_name.db> 3. Open the file in Patran and it will convert properly.

Problem 1:

Any

“File is not a valid database”; “PDF Open Error”

I attempt to open an old database and get the following message in a dialog box:

File is not a valid database

In the root window (the window from which Patran was run) I see the messages:

PDB ERROR : PDF OPEN ERROR: Can’t XDR decode the header block.

PDF ERROR: File ‘/tmp/blair/template.db’ is probably not a pdf file.

PDB ERROR : CMF_FILE_PROB_NOT_PDF - File is probably not a pdf file.

p3convert 7.0 initiated at Wed Apr  1 11:05:02 PST 1999

Creating (or updating) marker file for /tmp/blair/template.db

/msc/patran/bin/exe/dbVersion[57]: /usr/interbase/bin/qli:  not found.

/msc/patran/bin/exe/dbVersion[70]: /usr/interbase/bin/qli:  not found.

Resolution 1:

The PDB errors indicate that the PDB database system does not recognize this file as a PDB database. This typically means that the file is an older Patran database and is in InterBase format. PDB automatically spawns p3convert.

See Upgrading Databases, 74 for information on the p3convert utility.

In this case, p3convert fails with dbVersion errors. This indicates that /usr/interbase does not exist or is not properly installed. InterBase is required to convert Patran databases from versions prior to version 8.

Problem 2:

“PDF Open Error: Can’t open file”; “File’s schema version doesn’t match”

Any

I attempt to open an old database and get the following message in the root window (the window from which Patran was run):

PDB ERROR : PDF OPEN ERROR: Can’t open file ‘<database>’

PDF ERROR: File’s schema version: ‘PATRAN_2_1_a’ doesn’t match requested version

PDB ERROR : CMF_FILE_BAD_SCHEMA_VER - File schema version does not match

Requested file not a valid database

Resolution 2:

These errors indicate that the database schema version is not recognized as a Patran database for the current or an earlier version. The most likely cause is an attempt to open a database from a later version of Patran. For example, opening a version 9 database in version 8.5 will produce a message similar to the above.

Problem 3:

Any

No permission for REVOKE access; p3convert_1x12 failed

I attempt to open an old database and get the following message in a dialog box:

File is not a valid database

In the root window (the window from which Patran was run) I see messages
such as:

Invoking p3convert_1x12....

....

Updating the ANALYSIS_ELEMENT_SUMMARY records.

Enabling the relation triggers.

no permission for REVOKE access to TABLE$USER_PRIVILEGES

***Error: p3convert_1x12 failed

Resolution 3:

Patran is using InterBase to upgrade a pre-version 8.0 database. The problem stems from an earlier version of InterBase which placed the creators name as the owner of the database. If a different user attempts to upgrade the database he/she is denied permission.

This problem should not occur on Windows NT databases.

A script is provided with Patran which will correct this problem. At the UNIX prompt, execute the following command:

% $P3_HOME/bin/fixDb <database_name.db>

Open the file in Patran and it will convert properly.

Problem 4:

Unix

Cannot be opened for write access. It may already be in use.

I attempt to open a new or existing database in an NFS mounted directory and get a message in the UNIX window:

dbname.db cannot be opened for write access. It may already be in use

by another process, or may lack the necessary permissions. Cannot continue.

Resolution 4:

Patran, like any software using file locking, requires NFS and RPC file locking daemons on the client and NFS server. These names of these daemons will be differ between platforms. For example, on a SUN Solaris NFS server the following daemons are required:

/usr/lib/nfs/lockd

/usr/lib/nfs/mountd

/usr/lib/nfs/statd

Problem 5:

Linux

Objects cannot be rotated using two button mouse

I have a two button mouse. Pressing both buttons at the same time does not seem to emulate the third button and I am unable to rotate items in Patran

Resolution 5:

Assuming that you have installed the Linux drivers associated with your mouse, check the XF86config file (part of XFree86). You can turn on/off middle mouse button emulation. Note that XFree will look at XF86config-4 etc. before looking at XF86config.

Problem 6:

Unix

Updating NODE records; p3convert_1x12 failed

I attempt to open an old database and get the following message in a dialog box:

File is not a valid database

In the root window (the window from which Patran was run) I see messages
such as:

Invoking p3convert_1x12....

....

Updating the NODE records.

***Error: p3convert_1x12 failed

This error will always occur immediately after the NODE update.

Resolution 6:

Patran is using InterBase to upgrade a pre-v8.0 database. The problem stems from an earlier version of Patran which incorrectly wrote certain Node information. The p3convert_1x12 utility does not recognize the information.

This problem should not occur on Windows NT databases.

A utility is provided with Patran which will correct this problem:

1. The database must be at schema version 1.11 (equivalent to v6.2) for the utility to work properly. Use the following command to determine the current version:

% $P3_HOME/bin/dbVersion -p <database_name.db>

1.10

The value returned is the current schema version. Run the individual p3convert utilities to bring the schema version to 1.11. The p3convert_1x10 updates a 1.09 database to 1.10, p3convert_1x11 a 1.10 database to 1.11, etc. For the above example:

% $P3_HOME/bin/p3convert_1x11 <database_name.db>

2. Run the chkdb62 utility to fix the database:

% $P3_HOME/bin/chkdb62 <database_name.db>

3. Open the file in Patran and it will convert properly.