Quantcast
Viewing all articles
Browse latest Browse all 3548

/TMWFLOW/SCHEDULE_IMPORT occasionally not working correctly

Hello everyone,

 

 

I'm facing a recurring problem that has me somewhat stumped in Charm.

 

 

We're running SolMan 7.1 SP14

 

We've implemented Charm for a few projects, but also have 1 big maintenance project that is kept open for non-release changes & emergency fixes.
We have the /TMWFLOW/SCHEDULE_IMPORT scheduled every 30 minutes to import transports in our acceptance system that have the correct status in charm.

 

 

 

This works correctly most of the time. But from time to time, it seems to fail for the above mentioned big maintenance project. The job runs correctly (with the required variant to specify the system & client), but nothing happens. A few seconds of CPU time, tracing shows a big load of select queries & an update statement. But nothing arrives at the managed system (no entries in TWA alerts or import history)

 

In the corresponding tasklist within SolMan, nothing is logged either (which seems to be correct by design: if /TMWFLOW/SCHEDULE_IMPORT doesn't find anything, he doesn't log it in the tasklist calendar either). Unfortunate, because that means I can only guess what he did do.

 

And this situation doesn't change anymore, nothing is imported once this occurs.

 

A fix seems to be to schedule the import manually in the tasklist once, after which the import queue gets processed, and the next few times, import succeeds again.

 

I can rule out a restriction of rights since manually starting it does work. Setup seems to be OK as well, for the same reason.

 

 

But I'm not sure what to look at next in order to find a cause for this behaviour.

 

 

Has anybody had anything similar happen in the past? Any good ideas or suggestions?

 

Thank you for any assistance and for reading this far Image may be NSFW.
Clik here to view.


Viewing all articles
Browse latest Browse all 3548

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>