1. Installation Guide
  2. Upgrade
  3. Prepare for Upgrade
  4. Verify the Log File Information for Upgrade

9.2.7 Verify the Log File Information for Upgrade

See the following logs paths for more information:

  • Verify if the release is applied successfully by checking the log file generated in the locations mentioned in section Verify the Log File Information.
  • Verify if the release is applied successfully by checking the log file generated in the OFS_HM _PACK/OFS_HM /logs installation directory.
  • You can also verify the OFSAAI log files from the OFS_HM_PACK/OFS_AAAI_PACK/logs directory.
  • Verify the Model Upload log file available in the ftpshare/<INFODOM>/logs directory.
  • You can ignore ORA-00001, ORA-00955, ORA-02260, ORA-01430, ORA-02298 errors in the log file. For any other errors, contact My Oracle Support.

    You can ignore the ORA-00001 error in the log file available in the path OFS_HM_PACK/schema_creator/logs.

    Note:

    Ignore all the warnings in the installation log. For any issues contact My Oracle Support.
  • The following ORA error messages can be ignored:
    • name already used by an existing constraint
    • unique constraint violated
  • Verify if the Data Model is uploaded successfully by checking the log file generated as per the directory or path mentioned in the Silent.props file.
  • Verify the Update.log file located at $FIC_HOME/utility/UpdateConstraints/logs directory which is created by Update Constraint utility.
    • Execution status information of the utility is available against each Information domain. For success, Update successful message is displayed. If it is successful, verify the following references for new constraint names:
    • ftpshare/<INFODOM>/erwin/fipxml/<INFODOM>_DATABASE.xml
    • Constraint scripts under ftpshare/<INFODOM>/erwin/scripts/table
    • Constraint scripts under ftpshare/<INFODOM>/scripts
  • Object registration tables for constraints, REV_TAB_CONSTRAINTS, REV_TAB_REF_CONSTRAINTS, REV_TAB_CONSTRAINT_COLUMNS.
  • Oracle Data Dictionary in the respective Atomic Schemas for each Infodom.
  • If you encounter errors in the Update.log file, identify and troubleshoot the failed Infodoms. Once you have completed the troubleshooting, execute the standalone utility for the failed Infodoms. For more information on executing the update constraints utility, see the Update Constraints Utility section, in the OFS AAAI Applications Pack Installation Guide, Release 8.1.2.