on 10-30-2008 11:40 AM
Dear all,
After the upgrade of the SolMan server (V3.2 to V7), we cannot generate the EWA task into the satellite system.
I followed the documentation:
Into SolMan,
the satellite systems are created
The Solution Landscape is created
The Logical Component is created
All the RFC are created and Tested (Trust & Read)
Into the Satellite system (Production):
All the RFC are created and Tested (Trust & Back)
In the SolMan system, the service SAP EarlyWatch Alert is created. I can open successfully a connection into the satellite system using Call Service Data Control Center.
In the remote SDCCN screen, I launch the task Refresh Session with the target RFC "SM_PS1CLNT100_BACK". Once the task finished, no additional task appear (No EWA).
I have try sevaral times, and the result is still the same.
Is someone could help me?
Fabrice CHAINE
Hi Fabrice,
you should check for example:
1)that the service definitions are uptodate on both satellite system and Solution Manager (note 727998)
(if they're not uptodate on Solution Manager, Solution Manager can't create EWA sessions correctly, if they're not uptodate on satellite system, the satellite system won't "see" EWA in Solution Manager correctly)
2)that the satellite system is maintained in SMSY with the same installation number as you see in the satellite in system->status. It should also be a real number and not something like INITIAL or #########
3)check also in SMSY that the SID of the satellite has been maintained correctly. Sometimes people get confused between PO1 and P01, for example.
4)that the user in SM_PS1CLNT100_BACK has the correct authorizations in the Solution Manager. (The information at the end of note 824521 might help with that.)
I hope that helps.
best regards,
-David.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
Thank you for your reply,
I have checked the differents points:
1/ The satelitte system was not uptodate. The SP for ST-PI 2005_1 was SP6. I have installed the SP8.
2/ OK
3/ OK
4/ OK
For the moment, I launched SDCCN and replaced the service definitions. The service Definition Refresh has running and finished without error message. I have also launched the job "Refresh Sessions". Same thing: finished and no generation of EWA.
Have you other ideas?
Fabrice
Hi Fabrice,
did you create a new EWA session in the Solution Manager after replacing the service definitions or did you just try to refresh already existing EWA sessions? I would try creating a new session after the replacement of the service definitions.
(Since if the service definitions were the problem, it's likely that older EWA sessions were not created correctly.)
best regards,
-David.
Hi David,
I started from scrash. The SDCCN setup has been deleted et created again. Idem for the EWA session into Solution Manager.
The following task are now scheduled:
Service Preparation Check
Maintenance Package
I have scheduled manually the task EWA but it Task system ID is O01 and not PS1 (SolutionManager ID).
Then, the EarlyWatch Alert data is sent directly to SAP and not to SolMan.
Fabrice
Hi Fabrice,
it's not possible to create EWA for Solution Manager in the satellite system. The satellite system has to fetch the EWA from the Solution Manager. Only then will the task system ID be correct. Does a refresh sessions task to the RFC to SolMan still bring no result? Can you tell me what the entries in table bdl2trans in both satellite and SolMan look like?
best regards,
-David.
Hi David,
The EWA task is not generated automatically by the SolMan. It's the reason why I have tried to generated it manually into the satellite. The Refresh Session task has bring no result.
The entries of the table BDL2TRANS on the satellite:
SAPNETBDL CUSTBDL SAPNET_CHG
BDLCTEXT BDLCTEXT 20010319131712
BDLCTX2EXE BDLCTX2EXE 19991202173000
BDLDIRFUNC BDLDIRFUNC 20000413114000
BDLENDFUNC BDLENDFUNC 20010129110000
BDLERRORS BDLERRORS 20010330100828
BDLEXCEPT BDLEXCEPT 20010227101031
BDLFUGRPS BDLFUGRPS 20010319131712
BDLFUNC BDLFUNC 20010305144359
BDLFUNCMAP BDLFUNCMAP 20010305144359
BDLFUPDEF BDLFUPDEF 20011015112101
BDLFUPEXP BDLFUPEXP 19990101000000
BDLFUPIMP BDLFUPIMP 20010313151906
BDLFUVER2 BDLFUVER2 20010301175838
BDLFUVERS BDLFUVERS 20010305144247
BDLGROUPS BDLGROUPS 20010319131712
BDLREFSERV BDLREFSERV 20010227140000
BDLSADATA BDLSADATA 20010305144346
BDLSAIF BDLSAIF 20010305144346
BDLSERGRPS BDLSERGRPS 20010319131712
BDLSERTRAN BDLSERTRAN 20010308100333
BDLSERVICE BDLSERVICE 20010319131712
BDLST14KEY BDLST14KEY 20010316144009
There is no table entries for table BDL2TRANS into SolMan
Thank you,
Fabrice
Hi Fabrice,
there is no point in trying to generate EWA for Solution Manager in the satellite. It won't work.
From the BDL2TRANS entries I can see that the service definitions are too old (look at the last column, it's a time stamp, that means none of the entries are newer than 2001) in the satellite and don't exist in the Solution Manager. That means that the Solution Manager is not able to create EWA for the satellite correctly and the satellite is not able to understand the sessions.
I would advise you go through note 727998 carefully again and delete and replace the service definitions in both Solution Manager and satellite. When the service definitions are correct, the entry for BDLSERVICE for example should read 20080429091013. (Though not all entries in BDL2TRANS should be that new.)
best regards,
-David.
Edited by: David Murphy on Nov 6, 2008 4:00 PM
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.