Replication Task State Synchronization
sld_system_app (before 7.3.1), init_operations (from 7.3.1.)
Affected Domain Objects
Is Site Specific
This job determines all replication tasks of the system with state PENDING and updates the state to WAITING if current time reached or exceeds the replication tasks' pre-defined start time. This is necessary because only tasks with state WAITING can be assigned to replication processes.
Depends on the customer's operational needs. Per default the job is scheduled to run every 10 minutes, starting at 12:30 a.m.
What Happens Switched Off
Replication tasks with a predefined execution time are not set from PENDING to WAITING and are therefore not visible. Hence they cannot be assigned to replication processes.
Affected replication tasks would never be executed.
A data replication manager can create new replication tasks. He or she may submit a new task for immediate execution (i.e., the replication task's state is set to WAITING and can immediately be assigned to a replication process) or have it executed automatically at a later predefined time (i.e. the replication task's state is set to PENDING).
This job determines all replication tasks of the system with state PENDING and updates the state to WAITING if current time reaches or exceeds the replication tasks' predefined start time. This is necessary because only tasks with state WAITING can be assigned to replication processes.
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.