PDMS-DB configuration, fallback, merging

DB, abbreviated as database, is the carrier of data storage in PDMS. The various three-dimensional models, graphic drawings, databases, and so on in PDMS are almost always stored in db. So once the DB has an exception, the consequences will be devastating, so we need to have some technical means to deal with the DB problem.

1. Reconfigure re-configure the database

In the use of PDMS, due to network anomalies, operation of the exception, it may be the exception of the program itself, so that the PDMS is not properly closed. These conditions can result in a shadow user remaining in the project, or there are claims that are not properly dismissed, and the most extreme will cause some elements to be locked or even corrupted, causing the data in that db to become abnormal.

In general, shadow users and non-de-declaration can be in the admin module, the administrator can directly remove the solution, but if the element is locked or corrupted, you must use reconfigure to reconfigure the database.

1.1. Identify the DB to which the damaged element belongs

After selecting the damaged element, enter Q DBNAME on the command line to query the DB name to which the element belongs, and q dbnumber to query the number of the owning db.

1.2. Enter the Admin module

Only users with the free permission can perform reconfigure operations.

1.3. Lock the Project

Before reconfigure, kick out all the users and lock the project in case there is a user in the project.

1.4. Backup Project

Reconfigure, some operations are irreversible, once the reconfigure process, error, will cause the entire project a devastating disaster, so before reconfigure, be sure to back up the old project. Especially the novice who is inexperienced in operation.

1.5, Reconfigure

Enter the following command on the command line

A) from DB Paa/desi Note: The Paa/desi here is the result of our query in 1.1, which requires a db of reconfigure, and can only reconfigure one db at a time.
b) To FILE/P1/P2 Note: The data in db is stored in a temporary file, usually in the root directory of the PDMS, there will be so two files named P1, one for P2. Be aware that hard disk space is sufficient
c) Rcfcopy All
D) RECONFIGURE
e) Delete db paa/desi Note: Delete the old db, the reader should understand why to back up the project, because once there is an exception, DB is deleted, it is more difficult to find back.
f) CREATE DB Paa/desi DESI ACC multiwrite dbno 14

Note: Create a new db, where the new db and the old DB name are the same, Desi represents the type design DB,ACC Multiwrite is a multi-write database, Dbno 14 represents the DB number
g) From FILE/P1/P2 Note: Copy data back from temporary file
h) to DB Paa/desi
i) RECONFIGURE
j) Rcfupdate All

2, Backtrack back gear

In addition to the reconfigure,db mentioned above, it is possible to file back. The mechanism inside the PDMS is that each time the user clicks on the Savework, a session node is generated to record the state stored here, which is equivalent to a snapshot of the db. So with this snapshot, the db can go back to any save time point.

But it is not recommended that administrators often go to the db back, because this will generally be scolded ... If you have played online games are aware that the server back to the file, basically scold a piece of sound. Unless there is a serious problem, there is no other way than to return the document, the last resort to use this trick.

To open the back-up interface, in the admin module, the Data > Change management > Backtrack changes interface is as follows:

2.1. Select the DB to be returned

2.2. Select the time node you want to return to

You can set the node that needs to go back through the +,-number at session numbers, each node has a saved time, and the saved user.

2.3. Click Apply to complete the return file

Note: The return file does not overwrite the current node, but it generates a new node after the current node.

3. Merge merger

As mentioned above, the PDMS will generate a database node each time it is saved, and when the project is done for a long time or when the project is relatively large, the PDMS project file can be very large. At this point we can compress the nodes, merging some nodes, leaving only meaningful milestones. However, it is not mandatory to do so, in the current storage equipment is getting cheaper and larger capacity, the project file is no longer the bottleneck of constraints.

If the project has been completed, ready to file, it is appropriate to merge some nodes, leaving only the key points.

To open the back-up interface, in the admin module, the Data > Change management > Merge changes interface is as follows:

3.1. Select db to merge nodes

3.2. Merging methods

There are three ways to merge in the changes option:

3.2.1, all

Merges all nodes into one, leaving only the last one.

3.2.2, after

Merges all nodes after the currently selected node into one.

3.2.3, up to

Merges all nodes in front of the currently selected node into the current node.

3.3. Click Apply to complete the merge