1. Database Upgrade Guide for DB2 for z/OS

This procedure describes how to use Siebel Migration to view the history and log files for a migration task. The History screen in Siebel Migration keeps an ongoing log of the success or failure of each attempted migration task, along with the details of what happened. The following information is available for each migration task: Name, Desccription, Status, Source, Target, Archive ID, Start Date, End Date, Package Filename.

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

To view migration history and log files

  1. In Siebel Migration, navigate to the History or Execution tab.

  2. Select or click the plus (+) icon next to the migration task to show the log generated for the operation.

    For example, if you select the Incremental Runtime Repository Migration task, the task expands to show the Resource and Operation.

  3. Click Log next to an operation to view the log details for that migration operation.

    From Siebel CRM 19.7 Update onwards, you can review logs for the following Siebel Migration resource operations:

    • Runtime Repository Data Service: GetWatermark operation.

    • Application Workspace Data Service: GetFullSeedWatermark and GetSeedCopyWatermark operations.

    • Incremental Runtime Repository Data Service: ActivateTasks operation.

    • 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 you can review the migration.log file located in the migration server’s Application Interface application container’s \logs folder 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, then 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, then 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=}