Utility Change parent

Utility chparent.exe / chparent_ora.exe is used for the offline change of the parent.

"Offline" means that it makes the changes directly into the database without interaction with the D2000 server. The parent change will show after restarting the D2000 server.

Note: The parent can also be changed also in online, via XML Import (only for the objects of I/O tag, Event, Database or Table type)., Table, Eval Tag, Alarm, Remote Tag, Historical Value type). In addition, it is possible to change the parent to another type of object (e.g., Station, Line) provided that the parent process is not running (if changing the parent of a Process type, e.g., for an object of Line type, both the old and new parent must be stopped).

Syntax (it runs from the command line)

...

 
 - sybaseSybase/PostgreSQL/MsSql: chparent <app_name> <new_parent_name> <obj_name_mask1> [, <obj_name_mask2> [, ...] ]]
 
 - oracleOracle: chparent_ora <app_name> <new_parent_name> <obj_name_mask1> [, <obj_name_mask2> [, ...] ]
 

...

Utility changes the parents to all objectobjects, which whose names match to the mask <obj_name_mask1>, <obj_name_mask2>, etc., on to value <new_parent_name> in the configuration of the application (directly in the database).

Parent change does not run if the parent is not valid at least for one objectall objects. It means , it is checked if the selected parent can be assigned to the object of the given type.

The user must confirm this change (y = yes, other keys = no). In case of acceptance, the parent will be changed in the configuration of the application (directly in the database).

Potential errors

...

• incorrect Incorrect syntax for the utility chparent / chparent_exe.
• The database cannot be opened.
• The database error is notified.
• The new parent does not exist in the configuration database.
• none None of the objects object names match to the specified masks.
• The parent of the given type cannot be set to any of the objectssome of the objects.

Behavior in redundancy

...

The chparent utility does not change the object configuration change time (Modify Time). Therefore, the cfgsynchro utility does not synchronize such changes in the redundant system, and it is necessary to modify all configuration databases in the redundant system, not just one (or use export/import of the configuration database). A possible scenario for an outage-free change of a parent in a redundant system is as follows:

1. Shut down the standby (SBS) server.
2. Change the parent object in the SBS server configuration database.
3. Start the SBS server.
4. Connect to the SBS server using the CNF tool and check the correctness of the parent changes.
5. Redundancy switchover - The Standby (Passive) with the modified configuration will become a new HOT (Active) server.
6. Change of the parent object in the configuration database of the former HOT server.

...