Does the Migration Workbench support offline data loading in Microsoft Access?
Yes. The Migration Workbench uses SQL*Loader to provide an offline data loading capability, which improves the migration of large tables from Microsoft Access. To use offline data loading, you must manually create the data files from within the Microsoft Access Integrated Development Environment (IDE). Note: Microsoft Access 97 only supports the creation of a data file on a table-by-table basis. Therefore, you must perform the steps outlined in this section for each Microsoft Access table individually. The base directory for the SQL*Loader script output for Microsoft Access is %ORACLE_HOME%\Omwb\sqlloader_scripts\MSAccess\timestamp. The default Log directory is %ORACLE_HOME%\Omwb\sqlloader_scripts\. The Migration Workbench creates a directory in this base directory that represents the date and time that you generated the SQL*Loader scripts. For example, a sub-directory called 1-10-1999_17-58-16 indicates that the scripts were generated at 17:58 p.m. on 1st October, 1999. To manually cr
Related Questions
- Does the Migration Workbench support Microsoft SQL Server 6.0? If not, are there any plans to support this version of Microsoft SQL Server?
- How does the Migration Workbench handle Microsoft SQL Server 7.0 VARCHAR data types greater than 4000?
- Does the Migration Workbench support offline data loading in Microsoft Access?