The Max Insert Array Size option has no effect when a TIMESTAMP(X) column is present for the Copy Data to Another Schema tool
When right-clicking a table in the Toad schema browser and use the "Copy Data to Another Schema" option, the "Max Insert Array Size" selection has no effect if a TIMESTAMP(X) Column is present in the source table. During a copy operation with a Max Array Size of 500, rows are always copied 1 at a time, resulting in an extremely slow copy operation. If a TIMESTAMP(X) column is not present, the issue does not occur and rows are copied using the setting specified for the "Max Array Size".
This has been logged as Defect ID: TOR-116595, and waiting for fix in a future version of Toad for Oracle.