DDL Command Scope

DDL commands may be propagated to all nodes or be local to the executing node.

DDL command scope is as follows:

• Local scope – execute on the local server and affect the local catalog store or local temporary store only.
• Global scope – execute on the coordinator and affect the shared IQ store and global catalog store. The coordinator writes statements with global scope to the TLV log on commit.

• Local DDL Commands
  DDL commands that affect temporary objects, which lack a permanent object ID, are local.
• Global DDL Commands
  DDL commands that create, alter, or drop a permanent object ID in the ISYSOBJECT table are global.
• DDL Command Dependencies Example 1
  You cannot run global DDL commands if the coordinator node is not running. Attempting to do so results in the error SQLCODE: -1004011, SQLSTATE QIA11: Coordinator node not responding.
• DDL Command Dependencies Example 2
  When creating objects that are global, make sure that they do not depend on objects that are local.