Starts an explicit concurrent isolated load operation on a load isolated (LDI) table. You can perform concurrent read operations on committed rows while the table is being loaded.
After you perform the BEGIN ISOLATED LOADING statement, you must use SET QUERY_BAND to set the LDILoadGroup reserved query band to the load group value for the session before you can begin a load operation. See LDILoadGroup Query Band.
A load isolated table can either be in an explicit load state or implicit load state, but not both. After the explicit load starts, multiple sessions can load the table. Any session performing a load on the table is considered a load session. The table remains in a pending commit state until the load is committed. The table continues to be in load state until you perform an END ISOLATED LOADING statement.
For information on creating a load isolated table, see the CREATE TABLE option, WITH ISOLATED LOADING. You can also alter a table to specify the load isolation option. See the ALTER TABLE option, WITH ISOLATED LOADING.
You must have the INSERT, UPDATE, or DELETE privilege on the base LDI table.
Before you perform the BEGIN ISOLATED LOADING statement, the LDILoadGroup Query_Band value must not be set or must be set to NONE for the session.
You cannot issue a BEGIN ISOLATED LOADING statement from a session already performing a load operation. The current load operation must end and you must set the LDILoadGroup reserved query band to NONE before beginning another load operation.
The BEGIN ISOLATED LOADING statement must be the last statement in an explicit transaction.