Model Build Patch Log Showing Unrelated Map at Beginning of the Log File (Doc ID 2950966.1)

Last updated on JUNE 06, 2023

Applies to:

Goal

On : 2.6.0.0.0 version, Web Workspace

When building a map, the resulting $OPERATIONS_MODELS/errors/Patch####.log shows the wrong filename.

For example, building MAP_A.mb resulted in this Patch455.log:

Message:  MBS-00018      Location: MBService::differences      Severity: I
      Device:
      Applying patch 455 for map(s) MAP_C.mb .
      Context:
      Time: 05/11/22 11:12

Message:  MBS-00019      Location: MBService::submit      Severity: I
      Device:
      Committing patch 455.
      Context:
      Time: 05/11/22 11:12
...

Message:  MBS-00190      Location: MBService::submit      Severity: I
      Device:
      Patch 455 failed to be successfully created. Deleting patch.
      Context:
      Time: 05/11/22 11:12

Message:  MBS-00018      Location: MBService::differences      Severity: I
      Device:
      Applying patch 455 for map(s) MAP_A.mb .
      Context:
      Time: 06/05/23 14:31

Message:  MBS-00019      Location: MBService::submit      Severity: I
      Device:
      Committing patch 455.
      Context:
      Time: 06/05/23 14:31

Message:  MBS-00013      Location: MBService::submit      Severity: I
      Device:
      Patch 455 applied.
      Context:
      Time: 06/05/23 14:31

Message:  MBS-00014      Location: MBService::submit      Severity: I
      Device:
      Patch 455 committed.
      Context:
      Time: 06/05/23 14:31


NOTE: The Patch log starts with MAP_C, but we were building MAP_A.

 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.