[Home] [Help]
95: -- 1. GSMCTL invokes this routine and it:
96: -- a. adds the primary database entry to the catalog with status "I"
97: -- b. assigns the database a unique number and reserves a range of
98: -- numbers for the standbys
99: -- c. generates a GSM change message indicating that an Add
100: -- Brokerconfig has been done. Included in the message is the
101: -- number of database id's reserved for the config
102: -- (-num_standbys S) [Note that this number will be greater than
103: -- the input parameter "num_standbys" to this routine to allow for
259: -- The "Add Database" command is implemented in three phases:
260: -- 1. GSMCTL invokes this routine and it:
261: -- a. Adds the database entry to the cloud catalog
262: -- b. Set the status to "I" (incomplete)
263: -- c. Generates a GSM change message indicating that an
264: -- Add Database has been done
265: -- 2. The Master GSM is notified of the change and then modifies
266: -- each database to become part of the cloud. This involves adding
267: -- some GSM related hidden parameters.
1160: -- Notes:
1161: -- This procedure is called from a trigger when gsm_requests status
1162: -- is updated to 'A' (Aborted) by the GSM server
1163: -------------------------------------------------------------------------------
1164: PROCEDURE catRollback (change IN gsm_change_message,
1165: old_instances IN instance_list);
1166:
1167: -------------------------------------------------------------------------------
1168: --
1177: -- Notes:
1178: -- This procedure is called from a trigger when gsm_requests status
1179: -- is updated to 'D' (Done) or the row is deleted by the GSM server
1180: -------------------------------------------------------------------------------
1181: PROCEDURE requestDone (change IN gsm_change_message);
1182:
1183: -------------------------------------------------------------------------------
1184: --
1185: -- PROCEDURE strtolist