Hi everyone,
thank you for your replies - It seems that the current "TP" we are using has some Problems. We also created a ticket @ SAP to Analyse the current behavior.
Summarized the answer from SAP:
1. For your question: "Whats the difference between a triggered subset via Solution Manager and the Manual selection of transports and starting the subset via TMS?" : Compared with import directly via STMS there are additional tp calls to transfer buffer entries in ChaRM. However, the Major run times should be consumed by tp execution . Tp is responsible to clean semaphore file itself which failed in this case, as displayed in Directory: /usr/sap/trans.X01/log/SLOG1538.R01 . Currently transport coleagues have identified that some performance issues with tp version 380.31.61 ( your tp on R01 is 380.31.63) . and a correction version (380.38.89) will be released soon. As a workaround a tp version prior to 380.31.61 can be used as recommended by colleague Lueben on 18.09.2015 .
2. We don't think this is an issue related to ChaRM . Besides the possible issues related to tp version, we would recommend to check note 2025815 ( " Resolution when you get "WARN is already in use (), I'm waiting 5 sec" ) , specially try not to use tp processes in parallel to avoid this kind of issue.This means two users should not do transport at the same time on one system,even the same user should not open two different sessions to do transport at the same time on one system. --> Maybe it´s also helpfull for you. Best regards, Stefan