update_propagation_data

Propagates security data from top level objects to other related workspace objects based on current site propagation rules. Execute this utility when a propagation rule is added or an existing propagation rule is removed. Syntax update_propagation_data [-u=user-id {-p=password } -g=group] [-file=input file path] [-outputUIDfile=output file path] -h Arguments -u Specifies the user ID. This must be a user with Teamcenter administration privileges. Execute the following command if utility is not in the Authorization application. install_authorization_rules -u=Tc-admin-user -p=password -g=group -install The script will add update_propagation_data utility in Authorization application and system administrator/dba can provide full access to certain group/role. Note If Security Services single sign-on (SSO) is enabled for your server, the user and password arguments are authenticated externally through SSO rather than being authenticated against the Teamcenter database. If you do not supply these arguments, the utility attempts to join an existing SSO session. If no session is found, you are prompted to enter a user ID and password. -p Specifies the user's password. This argument is mutually exclusive with the -pf argument. -pf Specifies the password file. If used without a value, the system assumes a null value. If this argument is not used, the system assumes the user ID value to be the password. This argument is mutually exclusive with the -p argument. -g Specifies the group associated with the user. If used without a value, the user's default group is assumed. -file Path of the input file containing UIDs of top level objects having own ProjectObjectRelation(POR). Use SQL queries to get the list of object uids to process. Please refer Examples section. Utility propagates security data from these top level objects to other related workspace objects based on current site propagation rules. The file should not contain more that 50K UIDs. Split the file in multiple files each having 50K UIDs maximum. The object UIDs must be provided in a separate line in the file. This option should not be used with other options. -outputUIDfile Path of the output file which will be populated with the UIDs of top level objects having own ProjectObjectRelation. This file can be used as input value for -file option. This option should not be used with other option. Note You can use -outputUIDfile option, which will generate the UIDs of all top level objects having own ProjectObjectRelation or you can create your own UID file using SQL query. -h Displays help for this utility. Examples The following example illustrates a SQL query to generate a file of UIDs. Query to get all the workspace object UIDs that have own ProjectObjectRelation. Note This query is the default query used in utility. It will run on all the objects having own ProjectObjectRelation. This query is not sufficient to execute only on a set of few objects. You can add more criteria to the SQL and scope the objects you want to process. Copy select/+PARALLEL/distinct RTOP_LEVEL_PROJ_OBJU from Copy PROJECTOBJECTRELATION; Caution Utility must be run on the entire data object. If you only run the utility on few objects, then you should be aware that there is data that will not align with latest propagation rules. Only in exceptional cases where the volume of data is very high and takes a long time to run, you should scope in the objects by generating your own UID file.