propagation_doctor

This utility analyzes the propagation configurations to determine if any configuration issues exist in the database and generates a report. The report contains the configuration issues found and the remedy actions to fix those issues. Syntax propagation_doctor -u=user {-p=password | -pf=password-file} -g=group name -outputfile=output file path [-h] Arguments -u Specifies the user ID. This is a user with Teamcenter administration privileges -p Specifies the password. This argument is mutually exclusive with the-pf argument. -pf Specifies the password file. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -outputfile Path of output file to report the list of propagation configuration issues found in the database. -h Displays help for this utility. Note Whenever you find any propagation discrepancies or perform an upgrade, execute this utility to check if any configuration or data issue exists in your system. This utility investigates the following configurations: Configuration Issue: Problematic propagation loops that may cause a potential traversal risk. Analyzes the propagation rules to determine if any of the propagation rules set have potential traversal risks. It reports the propagation rule sets that have potential to create performance problems affecting various aspects of system behavior, related to user interactions and other Create/Read/Update/Delete activities. Note A user must deploy the propagation rules in the database before executing the utility. Example: A user deploys the following propagation rules in the database: After deploying the propagation rule, the user runs the utility command: propagation_doctor-u=userid -p=pwd g=grp -outputfile= This rule is problematic therefore the utility will report the following information in the output file: Copy Non COTS propagation rules in combination with COTS propagation rules could cause a potential traversal risk for the propagation paths below which could be forming a loop. A Loop is formed when traversal starts from a type and repeatedly encounter the same or sub/super type. This could cause potential performance problems for propagation related use cases. Inspect non-COTS propagation rules in each of the following problematic propagation loops and follow one of the solution proposals below in order to fix those non-COTS rules: Copy 1. Re-formulate the rule with more specific source/destination classes. 2. Navigate to the relevant destination objects from some other source objects. 3. Use custom post actions to populate the data instead of using a propagation rule. 4. Re-evaluate whether this particular propagation rule is required in the first place. Copy For more detail refer to the Teamcenter Documentation section Identify and fix propagation rules with potential traversal risk. Loop 1 Copy Forward AbsOccData ImanRelation Dataset Copy Forward Dataset IMAN_external_object_link ItemRevision Copy Forward WorkspaceObject IMAN_manifestation WorkspaceObject Copy Reverse PSBOMViewRevision qualifier_bvr AbsOccDataQualifier Copy Reverse AbsOccDataQualifier data_qualifier AbsOccData Loop 2 Copy Forward WorkspaceObject IMAN_specification WorkspaceObject Copy Forward Dataset IMAN_external_object_link ItemRevision Loop 3 Copy Forward WorkspaceObject IMAN_UG_altrep WorkspaceObject Copy Forward Dataset IMAN_external_object_link ItemRevision Loop 4 Copy Forward WorkspaceObject TC_Attaches WorkspaceObject Copy Forward Dataset IMAN_external_object_link ItemRevision Note After running the utility, four problematic propagation loops are found. The user should fix this non-COTS propagation rule by referring to the guidelines provided in Identify and fix propagation rules with potential traversal risk. Configuration Issue: Propagation rules using Operation Type other than "All". Reports propagation rules with operation type other than "All" in the output file as below. Creation of propagation rules with values for operation type other than "All" is disabled in BMIDE. Copy Configuration Issue: Propagation rules using Operation Type other than "All". Copy The propagation rules defined with operation type other than "All" are supported but we strongly encourage you to convert these propagation rules to operation type "All" so that all the propagation rules are consistent.
Going forward, we will deprecate the propagation rules defined with operation type other than "All".

The following propagation rules with operation type other than "All" are found in the Teamcenter database.
For each propagation rule, check if an equivalent propagation rule with "All" operation type already exists, if yes then delete the existing propagation rule.
If an equivalent propagation rule with "All" operation type does not exist,
then create an equivalent propagation rule with "All" operation type and then delete the existing propagation rule.

Copy Revise Forward ItemRevision IMAN_Motion Dataset Security Group II Merge SaveAs Forward ItemRevision IMAN_Motion Dataset Security Group III Merge

Configuration Issue: Discrepancies between style value in “TC_propagation_security_group_style" preference and propagation rules. Analyzes the propagation rules and TC_propagation_security_group_style preference to determine if there are any discrepancies between the style value in the propagation rules and preference. It also verifies whether all the propagation rules for a specific propagation security group are defined with the same style. It reports the propagation rules where the style/group does not match with the preference value. Discrepancies between the style value in the propagation rules and preference can result in unexpected propagation behavior. If the specific propagation group is defined with multiple styles in the propagation rules and the group/style exists in the TC_propagation_security_group_style the utility will report the following information in the output file: Copy If a Propagation Security Group/Style is defined in the preference "TC_propagation_security_group_style" then the same Security Group/Style should be used in propagation rules. Security Group/Style defined in the preference take precedence over the Group/Style used in Propagation Rules. Please ensure that the Security Group/Style used in propagation rules are matching with Group/Style defined in the preference. Also, all propagation rules for a specific security group should have the same style. Please ensure that the same style is used for a specific group in propagation rules. Group/Style discrepancies are found for propagation rules shown below: The preference dictates Order Style for Security Group III But the following propagation rules are defined with Overwrite Style for Security Group III Copy Overwrite Forward A5_9338051_Item IMAN_based_on A5_9338051_Item All Overwrite Forward A5_9338051_ItemRevision IMAN_based_on A5_9338051_ItemRevision All If a specific propagation group is defined with multiple styles in the propagation rules and the group/style combination does not exist in the TC_propagation_security_group_style , the utility will report the following information in the output file: Copy Configuration Issue: Discrepancies of style value in TC_propagation_security_group_style preference and propagation rules. If a Propagation Security Group/Style is defined in the preference TC_propagation_security_group_style then the same Security Group/Style should be used in propagation rules. Security Group/Style defined in the preference take precedence over the Group/Style used in Propagation Rules. Please ensure that the Security Group/Style used in propagation rules are matching with Group/Style defined in the preference. Also, all propagation rules for a specific security group should have the same style. Please ensure that the same style is used for a specific group in propagation rules. Group/Style discrepancies are found for propagation rules shown below: No Style exists for Custom Group IX in the preference. But following propagation rules are defined with Merge and Overwrite Style for Custom Group IX Merge Forward ItemRevision IMAN_Motion Dataset All Overwrite Reverse Item items_tag ItemRevision All Configuration Issue: Propagation rules using "Fnd0TraversalCondition" for Traversal Condition. Fnd0TraversalCondition signature is not compatible with the new traversal engine starting with release 11.3. If this condition is used in propagation rules, then the propagation will not work as expected. Reports propagation rules with Fnd0TraversalCondition condition in the output file as below. Copy Configuration Issue: Propagation rules using Fnd0TraversalCondition for Traversal Condition. Copy The "Fnd0TraversalCondition" signature is not compatible with the new traversal engine used in release tc11.3 and up. If this condition is used in propagation rules then propagation will not work as expected. You are at release 'Teamcenter P12000.3.0.20190701.00', either change the traversal condition from "Fnd0TraversalCondition"
to "isTrue" or use "Fnd0TraversalCondition2" for the propagation rules shown below. Copy Forward Item bom_view_tags Match All Security Group II Fill Configuration Issue: ProjectObjectRelation (POR) with "NULL" propagation group. Reports PORs (ProjectObjectRelation) with "NULL" propagation security group in output file. Existence of such PORs in the database will impact the propagation behavior and result in Error Condition. Copy Configuration Issue: ProjectObjectRelation (POR) with "NULL" propagation group. Copy POR with "NULL" propagation group should not exists in Teamcenter Database, it is considered as Error Condition. 1 POR with Propagation Group as NULL found in Teamcenter database. Please review the SFB-Teamcenter-8001528 and execute migrate_propagation_data utility with -deleteSuperfluous option to fix such POR. Note The number of PORs listed above will be replaced depending on the number of such PORs existing in the database. For example, if you have 100 PORs in the database that number would then display 100. Configuration Issue: 'No Group' ProjectObjectRelation objects (PORs). Reports PORs with Propagation Group with value 'No Group' Copy Configuration Issue: 'No Group' ProjectObjectRelation objects (PORs). Copy Examine the Teamcenter database for the existence of PORs having Propagation Group as 'No Group'. Copy 4 ProjectObjectRelation objects (PORs) with Propagation Group as 'No Group' found in Teamcenter database. Please review the SFB-Teamcenter-8001528 to evaluate if it is required to run migrate_propagation_data utility. Note The number of PORs listed above will be replaced depending on the number of such PORs existing in the database. For example, if you have 100 PORs in the database with “No Group” that number would then display 100. Configuration Issue: Missing "No Group" propagation rules. Reports propagation rules with propagation group other than ‘No Group” for which there is no matching "No Group" propagation rule. If the equivalent "No Group" propagation rules are not deployed in the system, the propagation for objects having ‘No Group’ PORs will not work as expected. Copy Configuration Issue: Missing "No Group" propagation rules. Copy If any PORs with "No Group" propagation security group exist in the database, and you are deploying propagation rules for Security Groups other than "No Group" then please ensure that matching "No Group" propagation rules are also deployed in the DB. If those "No Group" propagation rules are not deployed then it will impact the propagation behavior for those "No Group" PORs (they will not be processed).

PORs with the "No Group" propagation security group are found in the database and propagation rules with "No Group" are missing for below corresponding propagation rules. Please either deploy equivalent propagation rules for the "No Group" or if you are planning to migrate those "No Group" PORs using migrate_propagation_data utility then refer to the SFB-Teamcenter-8001528. Copy Forward ItemRevision IMAN_3D_snap_shot Dataset All isTrue isTrue Forward ItemRevision IMAN_UG_wave_position Dataset All isTrue isTrue Configuration Issue: 'No Group' ProjectObjectRelation objects (PORs) with null security attributes. PORs with "No Group" and all security attributes as NULL is a bad condition. The utility reports PORs having propagation group as 'No Group' and empty security attributes in output file as below. Copy 1 ProjectObjectRelation object (POR) with Propagation Group as 'No Group' and null security attributes found in Teamcenter database. Please review the SFB-Teamcenter-8001528 to evaluate if it is required to run migrate_propagation_data utility. Note The number of PORs listed above will be replaced depending on the number of such PORs existing in the database. For example, if you have 100 PORs in the database with “No Group” and empty security attributes that number would then display 100. Configuration Issue: Superfluous ProjectObjectRelation objects (PORs). In below scenarios, PORs are considered as superfluous: If a top level object has more than one POR, and one of the PORs is a "No Group" POR If a top level object has multiple PORs for the same propagation security group Reports top level objects having superfluous PORs in the output file as below. Copy 2 Top level objects found with superfluous extra 'No Group' PORs in Teamcenter database. Please review the SFB-Teamcenter-8001528 to evaluate if it is required to run migrate_propagation_data utility. 1 Top level object found with superfluous duplicate group PORs in Teamcenter database. Please review the SFB-Teamcenter-8001528 to evaluate if it is required to run migrate_propagation_data utility. Note The number of top level objects listed above will be replaced depending on the number such top level objects existing in the database. For example, if you have 100 top level objects with superfluous PORs that number would then display 100. Configuration Issue: Non-COTS Multi-value Propagation Attributes. Migration of PORs with non-COTS multi-value propagation attributes is not supported. Utility reports following information in the output file if such non-COTS multi-value attributes exist. Copy The following non-COTS multi-value propagation attributes are enabled for propagation: Migration of PORs will not be supported due to these properties, please contact Siemens Support if you plan to migrate the 'No Group' PORs. Property: ProjectObjectRelation (POR) statistics report file: This utility also generates a *.report file. This report file contains information about ProjectObjectRelation (POR) statistics. It reports the total number of PORs that exist in the database and the number of PORs for each security group. Reports the PORs statistics in the output file as below. The POR count varies based on the POR data. Copy ProjectObjectRelation (POR) statistics Total number of PORs : 204

POR counts by group

Security Group I : 67 Security Group III : 133 No Group : 4 Related Topics BMIDE for Data Model Design