Constraints That Affect onload

The onload utility performs faster than the dbimport, dbload, or LOAD methods. In exchange for this higher performance, onload has the following constraints:

• The onload utility can only create a new database or table; you must drop or rename an existing database or table of the same name before you run onload. During execution, the onload utility's prompt will ask you if you want to rename blobspaces.
• The onload utility places a shared lock on each of the tables in the database during the load. While you cannot update a table row with the lock in place, the database is available for queries.
• When you load a complete database, the user who executes onload becomes the owner of the database.
• The onload utility creates a database without logging; you must initiate logging after onload loads the database.
• When you use onload to load a table into a logged database, you must turn off logging for the database during the operation.
• The onload utility does not preserve dbspace assignments of table creation or table fragmentation.