Troubleshooting Real-Time Data Acquisition  

Use

You monitor the status of the data transfer in the monitor for real-time data acquisition (RDA). Problems can occur when data is transferred to the PSA or when data is further updated from the PSA into the DataStore object.

If an error occurs, the daemon terminates the data transfer. You can analyze and correct the error, and then restart the data transfer.

Procedure

You are in the monitor for real-time data acquisition. The daemon displays the status.

If data transfer for a DataSource terminates and this is the only DataSource assigned to the daemon, the daemon terminates (). If other DataSources are assigned to the daemon, only the data transfer in which the error occurred terminates. The daemon remains active () if no errors occur in the data transfer for at least one of the DataSources assigned to it.

Calling Logs for Daemons

...

       1.      Check the log for the daemon.

In the context menu of the daemon, choose Display Log, or select the daemon and choose  Display Log.

The screen that appears displays all logs for the daemon.

Using the application log (transaction SLG1), you can restrict the number of logs displayed to display those for a specific time period only. This makes the display easier to use.

In the application log (transaction SLG1), choose RSAP as the object and REALTIME as the subobject. Enter the InfoPackage ID as the external identification and restrict the time period to the period for which you want to display logs.

       2.      Open the error log.

       3.      Use the messages provided to determine whether the error occurred during extraction or in the transformation.

Only delete the daemon assignment for the DataSource if an error occurs in one of multiple assigned DataSources

If multiple DataSources are assigned to the daemon and you want to correct an error in one DataSource, we recommend that you delete the daemon assignment for this DataSource so that the load process can continue.

To do this, choose Delete Assignment in the context menu of the DataSource.

It might be necessary to stop the daemon. To do this, choose Stop Upload in the context menu of the daemon.

Correcting Errors That Occur During Extraction

If the PSA request is red because errors occurred during extraction, for example the RFC connection was interrupted, the background job was deleted, or the system terminated the program, proceed as follows:

...

       1.      Check the data in the PSA.

In the context menu of the PSA request choose Monitor. You can display the data in the PSA in the monitor by choosing  PSA Maintenance.

       2.      If the technical status of the request is red and you have corrected the error that occurred during extraction, proceed as follows: Delete the request from the PSA, repeat the delta update into the PSA, and execute a repair process chain. If you previously deleted the daemon assignment for the DataSource, assign the daemon to the DataSource again. Otherwise, start the daemon again to continue with the data transfer by real-time data acquisition. The steps you take are as follows:

       3.      Delete the request from the PSA.

To do so, open the list of requests in the PSA by double-clicking on the PSA request in the column Data Target.

Select the incorrect request and choose  Delete.

       4.      To repeat the last delta update, in the Data Warehousing Workbench, create a standard InfoPackage for the DataSource, choose Delta Update on the Update tab page, and execute the InfoPackage.

       5.      Check the status of the PSA request in the extraction monitor.

       6.      Go back to the Monitor for Real-Time Data Acquisition.

       7.      In the context menu of the data transfer processes that are assigned to the DataSource choose Generate Repair Process Chain.

The system creates a process chain in the display component Repair Process Chains for Real-Time Data Acquisition (RDA) for a data transfer process. The chain is assigned the following processes in addition to the start process:

○       Data transfer process

○       Possibly activation of the data in the DataStore object (no activation is required for write-optimized DataStore objects)

○       Subsequent process chains if they were defined for the data transfer process

One repair process chain can be generated for each data transfer process. The chain cannot be changed or transported.

       8.      In the context menu of the data transfer processes choose Execute Repair Process Chain. The relevant process chain starts immediately and performs the repair as follows:

○       The standard DTP is executed. All the data that is not yet in the DataStore object is transferred from the PSA to the DataStore object.

○       For standard DataStore objects: If the data was updated successfully in the DataStore object, the data is activated.

○       If there are subsequent process chains for the data transfer process, these are executed.

       9.      Activate the data transfer again with real-time data acquisition.

○       If the daemon was previously terminated, start it again by choosing Restart Batch Job in the context menu of the daemon.

○       If you previously deleted the assignment of the DataSource to the daemon because the daemon is still processing other DataSources and if the daemon is already running, assign thee DataSource to the daemon again by choosing Assign Daemon in the context menu of the DataSource. The daemon includes the DataSource in the processing with a few minutes delay.

Updating Delta Requests that were not Updated or that are Incorrect from the PSA to the InfoProvider

In some situations a PSA table may contain one or more successfully completed delta requests, but these requests were not yet updated in the DataStore object or were incorrectly updated in the DataStore object.

For example, errors can occur in the transformation, perhaps in data that does not have the expected data format. In this case, proceed as follows:

...

       1.      Check the status of the DTP request by choosing Monitor in the context menu of the request.

If the status of the request is red, proceed as follows:

       2.      Check whether the data for the DTP request is correct in the DataStore object.

To do this, in the monitor for the DTP request, choose  Administer Data Target. Alternatively, you can go to the monitor for real-time data acquisition to manage the DataStore object by double-clicking on the column Data Target for the data transfer process.

       3.      If, for example, the DTP request has the status 'red' due to technical problems in the transformation but the data in the DataStore object is correct, change the status of the DTP request to 'green' if the corresponding PSA request has status 'green'. Continue with step 8 and activate the data transfer for real-time data acquisition again.

       4.      If the data in the DataStore object contains errors, check the transformation and correct the errors.

       5.      To repeat the DTP request, set the status to 'red' if necessary and delete the request.

In the monitor for real-time data acquisition, call DataStore object administration by double-clicking on the column Data Target for the data transfer process. You can execute both functions here.

       6.      In the monitor for real-time data acquisition, choose Generate Repair Process Chain in the context menu of the data transfer process.

Also see step 7in the previous section.

       7.      In the context menu of the data transfer process choose Execute Repair Process Chain. The process chain starts immediately and performs the repair.

See step 8 in the previous section.

       8.      Activate the data transfer again with real-time data acquisition.

See step 9 in the previous section.

If the Daemon Cannot be Started

You cannot start the daemon in the following cases:

●      A PSA table that is the source of a data transfer process that is assigned to the daemon contains one or more successfully completed delta requests that were not yet written to the DataStore object.

The system suggests that you generate and execute a repair process chain. The procedure is described in the previous section.

If you no longer want to define values for the DataStore object by RDA, after executing the repair process chain, delete the assignment to the DataSource in the monitor for real-time data acquisition from the context menu of the data transfer process instead of executing step 7.

●      The target of a data transfer process assigned to the daemon contains one or more successfully completed delta requests that were not yet activated.

Proceed as follows:

                            a.      Select the delta requests that were not yet activated in the administration of the DataStore object and activate the data with Activate.

                            b.      If you no longer want to define values for the DataStore object by RDA, delete the assignment to the DataSource in the monitor for real-time data acquisition from the context menu of the data transfer process.

                            c.      To reactivate the data transfer with real-time data acquisition, open the monitor for real-time data acquisition and start the daemon by choosing Restart Batch Job.

●      Requests are deleted in the target of a data transfer process assigned to the daemon.

Wait until the deletion of the requests from the DataStore object has been completed and then restart the daemon.