Hi,
on one of our customer systems, the event SAP_TRIGGER_RDDIMPDP always is sent to the application server (not to the CI)
The job RDDIMPDP is fixed to the CI - so the event triggered job RDDIMPDP becomes a time sceduled job and so the single transport steps have to wait some secondes (up to 60) bever they get startet.
In note 24092 i read following:
---
3. sapevt program
This is a program written and executed in C; it is located by default in the same directory as the kernel executables. If an event is triggered using sapevt, the event scheduler runs on the application server that has been active for the longest time.
---
But there is only the CI an one more application server. And the CI is definitely the AS "hat has been active for the longest time."
For single transports the time delay can be absorbed - but if we import a large amount of support packages the system downtime is incalculable.
This problem only exists on the production system not on the consolidation system (because there is no furthe app. server)
Data:
---
AS Abap - ERP 6
Rel. 700
Kernel: actual
R3trans/tp: actual
shared trans_dir
DB:ORA
Memory: Both on 32GB
OS: Win2003 64bit
Can anybody tell me, why the messageserver sends the event not to the CI??
Thanks!
Regards,
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.