Secondary indexes built on the source system are not carried over to the target system. If secondary index changes exist as a result of the promotion, consider rebuilding the secondary indexes on the target system.
If any TDS table or screen is bound (that is, the session memory copy is in use for the rest of the session), the Promotion system issues a warning message that the object is unbound. The Promotion system then requests that you restart the Execution Environment and apply the change request again. Unbinding the objects prior to applying the change prevents these warning messages. Two tools are available to assist with this, @PROMUNBINDOBJS and @PROMBINDOBJS.
You can use the @PROMUNBINDOBJS tool prior to applying a change or series of changes to unbind a set of objects. You can specify ALL, INSTALLATION or SYSTEM as the scope of the change. You must restart the Execution Environment after running this tool. After applying the change requests run @PROMBINDOBJS to rebind the objects and then restart the Execution Environment.
Tables modified by a promotion keep the security attributes they had before the promotion. When a promotion creates new protectable objects (screens, reports, and tables) in the target system, they are assigned default classification level and discretionary security attributes according to the settings in the @PROM_NSEC_DEF table. For more information on the @PROM_NSEC_DEF table, refer to
Chapter 2, Preparing For Promotions. When the promotion is completed, you can use the TIBCO Object Service Broker Security system to grant access to specific objects.