Submitting forms on the support site are temporary unavailable for schedule maintenance. If you need immediate assistance please contact technical support. We apologize for the inconvenience.
The Max Insert Array Size option has no effect when a TIMESTAMP(X) column is present for the Copy Data to Another Schema tool
Description
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".
Resolution
WORKAROUND
None.
STATUS
This has been logged as Defect ID: TOR-116595, and waiting for fix in a future version of Toad for Oracle.
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Recommended Content
Product(s):
Toad for Oracle
Topic(s):
Configuration
Article History:
Created on: 1/16/2015 Last Update on: 5/7/2023
Thank you for your feedback for Topic Request
Your Request will be reviewed by our technical reviewer team and, if approved, will be added as a Topic in our Knowledgebase.
Welcome to Quest Support
You can find online support help for Quest *product* on an affiliate support site. Click continue to be directed to the correct support content and assistance for *product*.
The Quest Software Portal no longer supports IE8, 9, & 10 and it is recommended to upgrade your browser to the latest version of Internet Explorer or Chrome.