Export Log File Content

The script does not run at all if you provide incorrect usernames (database and/or application user) or an incorrect database directory name. Rerun the script with correct parameter values in that case.

The export process fails if the script is unable to check in some or all exportable objects. This is usually because theOracle Life Sciences Data Hub application user whose username you provide while running the script does not have sufficient privileges or if some other user is modifying the Domain at the same time when you run the export script. The export log lists details of objects that it cannot check in.

When the export process runs successfully the log file lists the following:

• Names of all Remote Locations and Remote Connections used by all Load Sets being exported. This is useful in manually creating the same in the target Oracle LSH instance.
• Names of Source Code CLOBs and BLOBs that the export script converted into files.
• The object name, object type, version number, and container details of:
  • All objects that the export script could successfully check in and include in the export
  • All objects that could not be included in the export and the reason for that.

    Note:

    Object instances that refer to definitions outside the Domain being exported will not work in the target Oracle LSH instance.

    You must examine the log file, copy object definitions for such instances into the Domain, update the object instances to point to the copied object definitions, and rerun the export script.