1. Database Upgrade Guide
  2. Viewing Migration Log Files

Viewing Migration Log Files

This procedure describes how to use Siebel Migration to view the log files for a migration plan. You can access and view log files from the following screens:

  • Execution screen – for more information, see the following procedure.

  • History screen (after a migration completes) – for more information, see Viewing Migration History.

This task is a step in Process of Using Siebel Migration to Migrate Data.

To view migration log files

  1. In Siebel Migration, click Execution in the navigation menu in the side panel to go to the Execution screen.

    The following information is available for migration plans in the Execution screen: Name, Description, Status, Action, Source, Target, Archive ID, Start Date, End Date, and Package Filename. For more information about these fields, see Executing a Siebel Migration Plan.

  2. In the Name field, expand the '<Name_of_Plan>' migration plan to show all resource task details for the migration plan.

    The following table shows the information that is available for each resource task in the migration plan.

    Field Description Example Value

    Resource Name

    Resource task name – examples include the following for a Data Export migration plan: Application Data Service, PostProcessing_Export, and so on.

    Application Data Service

    Operation

    Resource task operation – examples include the following:

    • Export (for Application Data Service resource)

    • CreateManifest (for PostProcessing_Export resource)

    • preparePackage (for PostProcessing_Export resource).

    Export

    Seq Num

    Sequence number (1, 2, 3, and so on) indicating the order in which the resource tasks will be processed.

    1

    Status

    Resource task status, which can be one of the following: Not Started, Running.

    Not Started

    Action

    Refresh

    Refresh

    Log

    Log

    Log

    Start Date

    Start timestamp for resource task operation.

    2022-03-03 20:59:13

    End Date

    End timestamp for resource task operation.

    2022-03-03 21:10:10

  3. Click Log in the Log field to view the log details for a resource task.

    You can review logs for the following resource operations:

    • Runtime Repository Data Service: GetWatermark operation.

    • Application Workspace Data Service: GetFullSeedWatermark and GetSeedCopyWatermark operations.

    • Incremental Application Workspace Data Service: InvalidateSeedCaches operation.

    • File Prepare and Deploy: generateWatermark, readwatermarkfile, writewatermarkfile operations.

Reviewing Execution Log Messages

Log messages typically record the Archive Id, Resource name, and the Operation name in the log file along with the log message. After an Archive Id is generated, all corresponding log messages will contain the Archive Id.

Log files are generated by the Siebel Migration Application but they are not visible in the migration UI. If errors are encountered during migration execution, then review the migration.log file located in the applicationcontainer_external\logs folder on the server where migration is hosted to determine why the migration failed and to decide how to resolve the issue.

  • To find and review the logs generated for a particular migration execution, search for the appropriate Archive Id in the migration.log file.

  • To find and review the logs generated by a specific Resource under an Archive Id, search for the Resource name in the migration.log file.

  • To find and review the logs generated by a specific Operation under a Resource Name, then search for the Operation in the migration.log file.

Note: Migration logs are stored in the migration server’s application container’s (Apache Tomcat) log location: <AI_ROOT>\applicationcontainer_external\logs.

Once Siebel Migration starts executing operations that are part of a resource in the migration plan, all resulting log messages will contain the appropriate Archive Id, Resource name, and Operation name as shown in the following examples.

Example Log 1: Archive Id is in Brackets

[DEBUG] 2018-10-25 04:41:24.203 [Thread-33] Migration - com.siebel.migration.server.Transaction:callExecutor [88-1VBW0R] Exporting resource {"name":"Migration Schema Service","URI":["https:\/\/slc04ovj.us.oracle.com:9001\/siebel\/v1.0"],"Source":"https:\/\/slc04ovj.us.oracle.com:9001\/siebel\/v1.0","Target":"https:\/\/slc07fnj.us.oracle.com:9001\/siebel\/v1.0","Steps":[{"StepName":"Export","Business Service":"Migration Schema Service","Method":"Export","InArg":["migrationid"],"OutArg":["trackingid"],"Location":"Source","Async":{"Async Business Service":"Migration Schema Service","Async Method":"GetStatus","Async InArg":["migrationid","trackingid"],"Async OutArg":["error","getlog","log","status"]}}],"TransId":"88-1VBW0R","rowId":["88-1VBW0S"],"Watermark":"","ActivationDate":""} 
[DEBUG] 2018-10-25 04:41:24.212 [Thread-33] Migration - com.siebel.migration.server.ProcessFlow:<init>[88-1VBW0R] Entered process flow for resource : Migration Schema Service

Example Log 2: Archive Id and Resource Name are in Brackets

[DEBUG] 2018-10-25 04:41:24.214 [pool-4-thread-2] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Runtime Repository Data Service] Entered get resources for resource : Migration Runtime Repository Data Service
[DEBUG] 2018-10-25 04:41:24.216 [pool-4-thread-1] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Schema Service] Entered get resources for resource : Migration Schema Service
[DEBUG] 2018-10-25 04:41:24.216 [pool-4-thread-3] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Application Workspace Data Service] Entered get resources for resource : Migration Application Workspace Data Service

Example Log 3: Archive Id, Resource Name and Operation are in Brackets

[DEBUG] 2018-10-25 04:41:24.234 [pool-4-thread-2] Migration - com.siebel.migration.server.Transaction:invokeRestCall [88-1VBW0R] [Migration Runtime Repository Data Service] [GetWatermark] Input PostData : {"body":{"workspace":"MAIN","language":"ENU","version":"0"}}
[DEBUG] 2018-10-25 04:41:24.251 [pool-4-thread-3] Migration - com.siebel.migration.server.ProcessFlow:getResources [88-1VBW0R] [Migration Application Workspace Data Service] [GetFullSeedWatermark] Argument Map constructed : {migrationid=88-1VBW0R, password=, workspace=MAIN, fileName=Migration_88-1VBW0R.txt, filename=, watermark=, isUnicodeDatabase=Y, sharedPath=, language=ENU, ActivationDate=, version=0, username=}