There are also a number of other SQL statements that are not routed by a grid node:
▪ DDL Statements (for example CREATE TABLE and ALTER TABLE) are routed by the grid-aware driver.
Note If, instead of using the grid-aware driver, you connect directly to a node in a grid and attempt to run a DDL statement, the results are unpredictable.
▪ Sequencer calls are not routed. Using sequencers in grid-based applications is not recommended due to lack of global sequencers in the grid.
▪ Triggers cause procedure code to be executed inside a single grid node. Triggers that refer to a row other than the row that initiates the trigger are not recommended in a grid-based application.
▪ Database events, when posted, always remain in the same grid node,
▪ Admin commands are always routed by the grid-enabled driver to the node that is the grid leader and executed there. To execute an admin command on a node that is not the grid leader, you must create a direct connection to the node.