Suddently unstable SAP connector - General advices?
We're loading now since 2 years data out from SAP which worked quite well (maybe every 3th or 4th month a fail). But suddenly everything changed from one day to another. What happened? No idea! I guess you guys are our last chance before I just destroy the whole damn thing.
SAP Team: "No change on our side"
SAP Basis Team: "No change on our side"
Network Team: "No change on our side"
IT Team: "No change on our side"
Our team: No change (that's the only thing I truly know )
Our setup is the following:
SQL Loads: A couple of tables (smaller & "bigger" like 2 millions), reading * and saving it in a qvd. We're using Generators for this, each of them will take table by table. We had 3 in parallel in the past, tried also to do only one a time.
Bigger tables (like JFRK, JKAP etc.). Also done by Generators, extractor by extractor. 3 in parallel (tried also with 1).
- SQL connection for the status table, identify if the job still runs (from a previous failed load)
- BAPI to abort the job
- Extractor load (some with delta, some with *)
Cause we were helpless we did a complete upgrade of all components: - Qlik V12 Nov. SR3
- SAP Connector 6.6 (also updated the transports)
But the jobs still failing.
Sometimes it's doing smoothly load by load (however we didn't saw this since weeks ). Now most of the times it's starting to load some tables and suddently it hangs/freeze. And the timeout will appear. We also tried to work with retrys in the QMC, sometimes we're getting the data in the second load (therefore I assume the SAP service is still doing his job). Same with the SQL loads: It works, timeout, works again. SAP Service is running without any crash.
Re: Suddently unstable SAP connector - General advices?
Yes, it's solved
But - hard to say what I was at the end. We did several checks in SAP and also changed a lot of parameters. But to be honest at the a reboot of the whole SAP env. was the game changer. Even everything looked normal on SAP I believe somehow wehere ressourced allocated and not really free which caused instability. After the reboot everything was cleared and worked again smoothly...
If you can just reboot and check if this solved your problem.