The master XML schema document contains xinclude references to each of the individual XML documents created for each of the tables being exported. For each table, a table specific schema (.xsd) document and a table specific instance (.xml) document are generated. Additional documents are created if the table contains LONG or LOB columns.
Click if you want to ensure that the data from all tables is consistent to a single point in time and does not change during the execution of the archive operation. The Oracle command SET TRANSACTION READ ONLY is used for the entire archive operation if this field is selected.
This field is optional. This field is only relevant if you have selected more than one table to be exported. If a single table only has been selected, it will be exported as an Oracle transaction that guarantees the consistency. If multiple tables have been selected and this field has not been selected, each table is exported as an independent transaction.
Use to specify the size of the buffer used to fetch rows. The size specified is the maximum number of rows fetched from Oracle at a time. Tables with LONG columns are always fetched one row at a time so this field will be ignored for only those tables that have LONG columns. This field is optional.
The WHERE clause will be added to each SELECT statement that is generated for each table. Since each SELECT statement refers to a single table at a time in the FROM clause, it is illegal to have a join in the WHERE clause specified in the field. This field is optional.
In , specify a file name that will receive informational and error messages. The user that is performing the archive operation must have the correct operating system permissions on the file. The file will be created if it doesn't already exist. If it does exist, the new log information will be appended to the existing file.