The Oracle driver provides two mechanisms for supporting batch operations:
The first mechanism uses native Oracle batch functionality. This mechanism typically is the faster of the two mechanisms, but it is not compliant with the JDBC specification because the native Oracle functionality returns a single update count for all operations in the batch. Because that single update count cannot be resolved into individual update counts for the driver, the driver returns a value of SUCCESS_NO_INFO (-2) for each entry in the update count array. The JDBC specification requires individual update counts to be returned for each operation in the batch.
The second mechanism uses code that resides in the driver to execute the batch operations and complies with the JDBC specification, but it is slower than using native Oracle batch functionality.
The BatchMechanism property determines which batch mechanism is used. If the value of the BatchMechanism property is nativeBatch, the native Oracle batch mechanism is used; otherwise, the JDBC-compliant mechanism is used.
The first mechanism uses native Oracle batch functionality. This mechanism typically is the faster of the two mechanisms, but it is not compliant with the JDBC specification because the native Oracle functionality returns a single update count for all operations in the batch. Because that single update count cannot be resolved into individual update counts for the driver, the driver returns a value of SUCCESS_NO_INFO (-2) for each entry in the update count array. The JDBC specification requires individual update counts to be returned for each operation in the batch.