Multiple Solution Manager Connectivity to 1 Satellite system

HI..
I have a requirement. There is already an existing landscape with solution manager ECC, BI etc. The solution manager is configured for EWA, Maintenance optimizer etc. I now have to install a new solution manager and connect it to the same set of satellite systems so that I receive the EWA, configure MOPZ again. Will this create any kind of a problem and technically how can we do it? I have two ideas for this scenario
1. Connect the new solution manager to the same satellite systems and do configuration as normal. Got this idea from the below link but not sure how it will work.
Re: send EWA report to more than one solution manager
2. Is it possible to push data from the existing solution manager to the new solution manager?
Would highly appreciate technical suggestions. Thx in advance for your help.

Hello,
You need the SMD Agent in order to have ABAP data going to the Solution Manager. Some RFCs are established directly from Managed System to the Solution Manager to extract E2E Change Analysis, Exception Analysis. The Workload Analysis and Host Information (SAPOSCOL) is extracted from WIly EM
Having that said, you can imagine that you cannot have only RFCs and you cannot have only data extracted from WIly EM.
I suggest you to take a look at the FWK Administration in the solman_workcenter, choose the Managed System tab, and start looking into the details of each extractor. Some have an RFC destionation, others have SOLMANDIAG. The SOLMANDIAG are coming from the Solution Manager Java stack, which is responsible to poll the Wily EM.
The reason you need two SMD Agents is because the SMD Agent connects to the ABAP stack, retrieves data, and then connects to the Wily Enterprise Manager. The Solution Manager polls data from the Wily EM and persists it in the BW.
The SMD Agent doesn't support connecting to two Wily EMs at the same time.
So it is required to have TWO SMD agents polling data from the ABAP stack, at the same time, one of them reporting to one Wily EM, and the other reporting to the other Wily EM.
Each solution manager has it's own Wily EM, and it will pull the ABAP data from the Wily EM.
It is not possible to make the two Solution Manager's connect to one Wily EM, since the setup framework needs to see a SMD Agent available to run the setup wizard and to create the destinations. So each Solution Manager needs a SMD Agent running in the physical host.
I hope it is clear for you.
Best regards,
Guilherme
Edited by: Guilherme Balbinot on Feb 6, 2012 9:44 PM
Edited by: Guilherme Balbinot on Feb 6, 2012 9:49 PM

Similar Messages

Quality Center Adapter - Connecting Multiple Solution Manager Systems

We are running Solution Manager 7/Enhp 1 and Quality Center 10 successfully using the Quality Center Adapter integration. My question is, can we connect multiple Solution Manager systems (i.e. SMP/SMS/SMX) to a single Quality Center server simultaneously? Or is there a one-to-one relationship restriction. Thanks.

I have answered this question in this post below:
http://forums.sdn.sap.com/thread.jspa?threadID=2110531&messageID=10962875#10962875
To quote myself
Each tie up is based on the logical ports at the Solution Manager end and the relationship between the two entities is between Projects. So if you set up the configuration like you would in a normal scenario and at the right moment, connect the projects in SolMans to the corresponding projects in HPQC, you should be fine.
Hope that helps.

Multiple solution Manager

hello
We are in the process of implementing Solution Manger in our system landscape.
Is it possible to have multiple Solution Manger running on different physical server for the same landscape?
Kind Regards
Mohammad

Did you find any info in this link about running multiple solution manager's (SM), as I haven't.
We have two Data centres, with productive systems in one & DEV/QA in another.
I have configured SM in production datacentre to run Autoreaction alerts, sending emails & FTP messages to Mainframe console for errors, and have added a 2nd SM instance in our DEV/QA environment.
I now want to separate the alerting out between the environments, and also have the DEV/QA SM monitor via CCMSPING the Productive SM.
(With failover available.)
The problem I have is getting different systems registered to the relevant environment.
I have changed the cmsconf file to put the relevant SM CENs as primary & secondary, but they still show up in RZ21 topology as both registered with both.
Anyone else running multiple SMs?
Many thanks
Sean
Edited by: sean collins on Jun 16, 2008 1:14 PM

Solution Manager connection to Satellite system

Hi Gurus
I would like to find out on what kind of tests can I perform on business process management to ensure that the Solution Manager is communicating with the sattelite system.
Regards
Khuselwa

Hi Khuselwa -
Do you just want to ensure that a connection is established between Solution Manager and the satellite systems? You can do both a connection test and authorization test in the Configuration of RFC Connections transaction.
Transaction SM59
Expand ABAP Connections
Double click an entry
Choose Connection Test button.
You can also test the authorization by Utilities --> Test --> Authorization Test
Hope this helps,
Nathan

Solution Manager information for Java stack systems

Hi,
Could someone please help with the setup of Solution Manager, and how to connect to the backend of a Java stack system. For our ERP systems this is working via RFC, but I was hoping to get more information on the procedure for java. I can specify manually via SMSY, but I am sure there must be a setup that can pull the information for the system itself. Could anyone shed some light on this if possible please.
Regards,
Chris

Dear Chris,
ABAP Stacks use RFC as you know for inter system communications.
Java stack systems use Solution Manager Diagnostics.
You will need to run Solman_Setup > Managed System Configuration
First you should visit the link http://service.sap.com/diagnostics
There you will see a link to the media library, and there you will find complete documentation.
Hope you find this information Helpful.
Regards,
Paul

Solution Manager connection in Data Services

Hi,
When trying to make a data store connection in Data Services to a Solution Manager system I get an error that there is no connection or my credential are wrong.
I can ping the system so there is a connection.
I can log in to the Solution Manager system via the GUI so the credentials are ok.
So far i have found out that the Data Store connection cannot connect to Solution Manager because it per default tries to connect to port number 3200 while the Solution Manager system default has port number 3300.
But i can't change / select port number in the Data Services data store connection. So what do i do?

There is a problem in the transport file supplied with BODS installation folder. Pls refer to the SAP Note :
1616269 - Problems when installing Data Services 4.0 SAP transport files (900155.R63)
We have used the new transport files but we are still getting the below warnings in the log files and it returned with return code 4 :
Maximum length ("255") for "CHAR" in transparent tables exceeded
The SAP Note 1446648 - Warning Messages installing SAP R3 transports for Data Services sayou can ignore those warnings but we are still not able to see the ZAW0 Function group in SE37.
Let me know if you are able to do it successfully.

SLD Solution Manager & connections to other SAP productes in landscape?

Hi All
I have installed Solution Manager 4.0 SR3 in order to implement global monitoring across our landscape and I have decided to install and use the SLD.
I have set up the SLD and followed the post installation guide, however I now want to connect all of our sytems to it so that Stack , version Information, components etc can be transfered to the SLD automatically. Once this is done in Solution Manager (SMSY) I can then view all of my systems.
Firstly is this possible and does anyone have any information on how to do this?
Many Thanks
Phil

Hi Phil,
It is possible.
Firstly in satelite systems you need to enter your SLD server info using transaction SLDAPICUST. Here you specify your Solution Manager system as host, user usually j2ee_admin and j2ee_admin's password. The alias can be anything and default port is 5<instance no>00.
Secondly, you test the connection with transaction SLDCHECK. If it's green it's OK, you can ignore most warning messages.
Then last you setup data collection and job scheduling and you do this in transaction RZ70.
Sorry don't have any reference to notes or documentation but each transaction above should make sense of what I mentioned.
Hope this helps.
Regards,
Nelis
Message was edited by:
Nelis Lamprecht

Solution Manager to Solution Manager connection

Hello everyone,
I am searching for an answer for such a question: is it possible to connect one SolMan (the one from the service provider) to another SolMan (customer's one) in a way that tickets would go from customer's ERP to their SolMan (as it is now) and afterwards would be automatically forwarded to the other SolMan where the tickets should be processed?
If you have any idea, experience or relevant document, please share it - I will be really grateful.
Best regards,
Katarzyna Klys

Hi Katarzyna,
Please check the External service desk functionality for this. You can check SPRO entry for this:
SPRO --> SAP Reference IMG --> SAP Solution Manager Implementation Guide
     --> SAP Solution Manager --> Scenario-Specific Settings --> Solution Manager - External Integration --> External Service Desk
Also check below link:
http://help.sap.com/saphelp_sm40/helpdata/en/8a/b0278648ac4f058a7111c3f9b60feb/frameset.htm
(All in One line)
In Solman 7.0 system:
1. T-code SM59   > Define an RFC connection to 7.1 system;
2. T-code ICTCONF   > Add an entry for the 7.1 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping (you may find the button on the top of ICTCONF).
In Solman 7.1 system:
1. T-code SM59   > Define an RFC connection to 7.0 system;
2. T-code ICTCONF   > Add an entry for the 7.0 service desk, specify the RFC Destination as the one you defined   > Activate -> Generate default value mapping;
3. Customize your own value mapping including the transaction type. You will find the details in:
    IMG -> SAP Solution Manager -> Capabilities (Optional)
    -> Application Incident Management (Service Desk)
    -> External Integration -> External Service Desk
Most fields of SIVA and SMIV are the same (for example, priority) so you do not need to care about the value mapping if you do not havespecial requirement. However, some fields only exist in SIVA (category, subject) and others only exist in SMIV (multilevel categories). You may need to implement your own code according to your requirement.
Notes might help:
1159722
1136816
Thanks
Vikram

Solution Manager: Connection via Service Connection???

Hello,
I would like to connect the solution manager with a customer system via an exististing service connection, there is no solution manager installed on the customer's system. Is this possible? Is it possible to find any documentation about this?
Regards,
Britta

Hello,
You can run TCD DSWP
Then clcik the Solution Landscape button
Then Clcik the Service Connection link
Then click the Solution Manager drop down menu and select setup connection
Then fill in the details:
Product System
Description
Installation Number
Systen ID
System Number
Service Connection type
The support Service Connection types are reference at http://service.sap.com/connectiontypes and for each connection type the corresponding Note is provided.
This setup will allow you to create service connections to OSS on Solution Manager
Once you have setup the connection you will still navigate to Service Connections, only you will use the Connection Drop down menu button to select Open Connection.
Regards,
Paul

Downtime Management Notification Users in Satellite Systems

Hi folks,
I'm starting to set up Solution Manager Downtime Management. It's kind of cumbersome but I realize it is new functionality and will get better over time. I'm trying to set up the notification users but when I select "Notification Settings" of a system then "Add Internal Recipients" then "from System Users" it only pulls in users in client 000 of the satellite system. Obviously we don't have our users in 000 so how do I make DT Management look in client 100 for the list of users? I know I can add business partners but don't want that right now. I've already looked through the setup guide in Work Centers in SAP Solution Manager [original link is broken] and notes 1129385 "Downtime Management with SAP Solution Manager: FAQ" & 1129052 "Downtime Management with SAP Solution Manager: a brief guide" so don't need links to those. Any help is appreciated, thanks,
David

Hi
what is your solutionn manager version?
as per the note 1129385, from SP17, downtime management sends notication to all the system users.
again review here [Notifying Users About Scheduled Downtime |http://help.sap.com/saphelp_sm70ehp1_sp23/helpdata/en/6b/575f97df0b47808ead4c1f5e2df172/frameset.htm]
regarding client, SOST(Email,sms) settings also client specific.
Have you configured Email settings on client 100 too? if not ... please configure and try.
Thanks,
Jansi

Solution Manager and external Central Monitoring system

We have a Solution Manager system SOL and a Central Monitoring system
CEN. The monitored system SDS is configured to report CCMS data to CEN
and I wanted SOL to be able to access this data. After configuring SDS
to CEN, CEN that the following entry in RZ21:
SDS#SDS_RZ20_COLLECT#SDS_RZ20_ANALYZE
After performing the wizard in SOL, SOL now has the following entries
in RZ21:
SDS2#SM_SDS2CLNT200_READ#SM_SDS2CLNT200_TRUSTED
This would indicate to me that SOL is reading the CCMS information
directly from the monitored system, rather than via CEN.
In the 'Setup System Monitoring' of Solution Manager the Central
Monitoring System and CEN destination are SOL and NONE respectively.
Is this configuration correct, and if not how do I correctly configure
it?
Is the monitored system now only reporting data to SOL, or is it
reporting to both CEN and SOL?
Regards,

Issue closed

"Error in Solution Manager Self Check While performing System Monitoring"

Hi All,
I'm running Solution Manager 7.1 SP8. We are running SOLMAN_SETUP Activities in Client 800, we are
not using the default client i.e. 001
I'm performing the "Solution Manager Self Check" in System Monitoring. When I execute
the Solution Manager Self Check option I'm getting an error message
Text = BI Setup check
'MYSELF_DEST' failed - Reason: ;Incorrect client 800; use BI client 001
Action = The CCMSBISETUP job was not completed successfully. Please run CCMSBISETUP again from the
transaction solman_admin and/or adjust the corresponding BI objects in RSA1 if
necessary.
Any Pointers, I am new to solution Manager, Will really appreciate your help.
Regards
Zohaib

Hi Amit,
This is what info I could see in the table RSBASIDOC
for Client 800
SLOGSYS        RLOGSYS       OBJSTAT BIDOCTYP TSIDOC3X TSPREFIX
XXXCLNT001   XXXCLNT001    ACT        ZSRA002                             RA
and for client 001
SLOGSYS        RLOGSYS       OBJSTAT BIDOCTYP TSIDOC3X TSPREFIX
XXXCLNT001   XXXCLNT001    ACT        ZSRA002                             RA
I could see the same info in both the clients.
@ Amit: Could you please provide me any inputs
Regards
Zohaib

SOLUTION MANAGER UPGRADE - Error when shadow system Starting

Hi All, We are upgrading our Solman system from 7.0 EHP 1 to SOLMAN 7.1. But the system is uable to start the Shadow
system. *** ERROR => DpHdlDeadWp: W0 (pid 12046) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12046) exited with exit code 255 *** ERROR => DpHdlDeadWp: W4 (pid 12050) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12050) exited with exit code 255 DpMBufHwIdSet: set Hardware-ID ***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1296] MBUF state ACTIVE DpWpBlksLow: max wp blocks in queue is 800 (80 %) MBUF component UP DpMsgProcess: 1 server in MBUF DpAppcBlksLow: max appc blocks in queue is 500 (50 %) *** ERROR => DpHdlDeadWp: W3 (pid 12049) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12049) exited with exit code 255 Sun Jan 8 21:50:33 2012 *** ERROR => DpHdlDeadWp: W2 (pid 12048) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12048) exited with exit code 255 *** ERROR => DpHdlDeadWp: W5 (pid 12051) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12051) exited with exit code 255 *** ERROR => DpHdlDeadWp: W6 (pid 12052) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12052) exited with exit code 255 *** ERROR => DpHdlDeadWp: W7 (pid 12053) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12053) exited with exit code 255 *** ERROR => DpHdlDeadWp: W8 (pid 12054) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12054) exited with exit code 255 *** ERROR => DpHdlDeadWp: W9 (pid 12055) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12055) exited with exit code 255 *** ERROR => DpHdlDeadWp: W10 (pid 12056) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12056) exited with exit code 255 *** ERROR => DpHdlDeadWp: W11 (pid 12057) died (severity=0, status=65280) [dpxxwp.c 1522] DpTraceWpStatus: child (pid=12057) exited with exit code 255 kill(12045,0) -> ESRCH: process died DpStartStopMsg: send stop message (myname is >solmanqazone_KSQ_04 <) DpStartStopMsg: Write AD_STARTSTOP message with type= 0, name=solmanqazone_KSQ_04 , sapsysnr= 4, hostname=solmanqazone AdGetSelfIdentRecord: > < AdCvtRecToExt: opcode 60 (AD_SELFIDENT), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 60 AdCallRegisteredCvtToExt: opcode 60 call 102164870 AdCallRegisteredCvtToExt: opcode 60 exit rc=SAP_O_K AdCvtRecToExt: opcode 4 (AD_STARTSTOP), ser 0, ex 0, errno 0 AdCallRegisteredCvtToExt: opcode 4 AdCallRegisteredCvtToExt: opcode 4 call 102160ff8 AdCallRegisteredCvtToExt: opcode 4 exit rc=SAP_O_K DpConvertRequest: net size = 189 bytes NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufSend starting NiIWrite: hdl 17 sent data (wrt=562,pac=1,MESG_IO) MsINiWrite: sent 562 bytes MsISnd2: send msg (ms hdr/msg 110/452 bytes) to name -, type 4, key - DpStartStopMsg: stop msg sent NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=274,pac=1,MESG_IO) NiBufIIn: NIBUF len=274 NiBufIIn: packet complete for hdl 17 NiBufSend starting NiIWrite: hdl 17 sent data (wrt=114,pac=1,MESG_IO) MsINiWrite: sent 114 bytes MsISnd2: send msg (ms hdr/msg 110/4 bytes) to name MSG_SERVER, type 0, key - MsSndName: MS_NOOP ok Send 4 bytes to MSG_SERVER NiBufIAlloc: malloc MSLIB-BUF, to 32110 bytes NiBufIAlloc: malloc NIBUF-IN, to 32110 bytes NiIRead: hdl 17 received data (rcd=114,pac=1,MESG_IO) NiBufIIn: NIBUF len=114 NiBufIIn: packet complete for hdl 17 NiBufReceive starting MsINiRead: received 114 bytes MsIReceive: received msg (ms hdr/msg 110/4 bytes), flag 3, from MSG_SERVER , typ 0, key - Received 4 bytes from MSG_SERVER Received opcode MS_NOOP from msg_server, reply MSOP_OK MsOpReceive: ok MsISendKeepalive : keepalive sent to message server NiIRead: hdl 17 recv would block (errno=EAGAIN) Sun Jan 8 21:52:21 2012 NiIPeek: peek for hdl 17 timed out (r; 1000ms) NiIRead: read for hdl 17 timed out (1000ms) DpHalt: no more messages from the message server DpHalt: sync with message server o.k. DpHalt: detach from message server ***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 12730] *** ERROR => e=28 semget(20465,1,2016) (28: No space left on device) [semux.c 498] *** ERROR => SemRq: Implicit SemInit failed. Key=65 [semux.c 1129] *** ERROR => Es2Cleanup: SemRq SEM_ES2_ADM (rc=1) [es2xx.c 1082] SemRq( 38, 1, -1) enter SemRq( 38, 1, -1) exit rtc=0, 0us SemRel( 38, 1 ) enter SemRel( 38, 1 ) exit rtc=0, 0us ShmDelete2( 73 ) DpHalt: cleanup event management DpHalt: cleanup shared memory/semaphores SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 1 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 6 ) = 0740 (octal) SemKeyPermission( 7 ) = 0740 (octal) SemKeyPermission( 8 ) = 0740 (octal) SemKeyPermission( 10 ) = 0740 (octal) SemKeyPermission( 11 ) = 0740 (octal) SemKeyPermission( 12 ) = 0740 (octal) SemKeyPermission( 13 ) = 0740 (octal) SemKeyPermission( 14 ) = 0740 (octal) SemKeyPermission( 15 ) = 0740 (octal) SemKeyPermission( 16 ) = 0740 (octal) SemKeyPermission( 17 ) = 0740 (octal) SemKeyPermission( 18 ) = 0740 (octal) SemKeyPermission( 19 ) = 0740 (octal) SemKeyPermission( 20 ) = 0740 (octal) SemKeyPermission( 21 ) = 0740 (octal) SemKeyPermission( 22 ) = 0740 (octal) *** ERROR => e=28 semget(20422,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 24 ) = 0740 (octal) *** ERROR => e=28 semget(20424,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 25 ) = 0740 (octal) *** ERROR => e=28 semget(20425,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 26 ) = 0740 (octal) *** ERROR => e=28 semget(20426,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 27 ) = 0740 (octal) *** ERROR => e=28 semget(20427,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 28 ) = 0740 (octal) *** ERROR => e=28 semget(20428,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 29 ) = 0740 (octal) *** ERROR => e=28 semget(20429,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 30 ) = 0740 (octal) *** ERROR => e=28 semget(20430,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 31 ) = 0740 (octal) *** ERROR => e=28 semget(20431,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 35 ) = 0740 (octal) *** ERROR => e=28 semget(20435,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 42 ) = 0740 (octal) *** ERROR => e=28 semget(20442,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 43 ) = 0740 (octal) *** ERROR => e=28 semget(20443,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 44 ) = 0740 (octal) *** ERROR => e=28 semget(20444,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 45 ) = 0740 (octal) *** ERROR => e=28 semget(20445,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 47 ) = 0740 (octal) *** ERROR => e=28 semget(20447,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 48 ) = 0740 (octal) *** ERROR => e=28 semget(20448,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 49 ) = 0740 (octal) *** ERROR => e=28 semget(20449,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 50 ) = 0740 (octal) *** ERROR => e=28 semget(20450,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 51 ) = 0740 (octal) *** ERROR => e=28 semget(20451,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 53 ) = 0740 (octal) *** ERROR => e=28 semget(20453,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 54 ) = 0740 (octal) *** ERROR => e=28 semget(20454,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 55 ) = 0740 (octal) *** ERROR => e=28 semget(20455,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 56 ) = 0740 (octal) *** ERROR => e=28 semget(20456,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 57 ) = 0740 (octal) *** ERROR => e=28 semget(20457,1,2016) (28: No space left on device) [semux.c 498] SemKeyPermission( 58 ) = 0740 (octal) DpCleanupSharedResources: MpiCleanup ShmCleanup( 62 ) ShmCreate( 62, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 62, 3 ) ShmKeySharedMMU( 62 ) = 0 (octal) ShmProtect: shmat key 62 prot 3/0 done ShmCreate( 62, 0, 2, -> 0xfffffffe1d400000 ) MpiCleanup() -> MPI_OK DpCleanupSharedResources: removing Semaphore-Management DpCleanupSharedResources: removing request queue ShmCleanup( 31 ) ShmCreate( 31, 0, 2, 0xffffffff7fffea78 ) ShmProtect( 31, 3 ) ShmKeySharedMMU( 31 ) = 0 (octal) ShmProtect: shmat key 31 prot 3/0 done ShmCreate( 31, 0, 2, -> 0xffffffff24000000 ) DpCleanupSharedResources: ShmCleanup SHM_SYS_ADM_KEY ShmCleanup( 1 ) ShmCreate( 1, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 1, 3 ) ShmKeySharedMMU( 1 ) = 0 (octal) ShmProtect: shmat key 1 prot 3/0 done ShmCreate( 1, 0, 2, -> 0xffffffff78100000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_ADM_KEY ShmCleanup( 2 ) ShmCreate( 2, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 2, 3 ) ShmKeySharedMMU( 2 ) = 0 (octal) ShmProtect: shmat key 2 prot 3/0 done ShmCreate( 2, 0, 2, -> 0xffffffff28800000 ) DpCleanupSharedResources: ShmCleanup SHM_DP_CA_KEY ShmCleanup( 3 ) ShmCreate( 3, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 3, 3 ) ShmKeySharedMMU( 3 ) = 0 (octal) ShmProtect: shmat key 3 prot 3/0 done ShmCreate( 3, 0, 2, -> 0xffffffff24800000 ) DpCleanupSharedResources: ShmCleanup SHM_PF_KEY ShmCleanup( 4 ) ShmCreate( 4, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 4 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_SAPSCSA_AREA_KEY ShmCleanup( 5 ) ShmCreate( 5, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 5 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PXA_KEY ShmCleanup( 6 ) ShmCreate( 6, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 6 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_VB_ADM_KEY ShmCleanup( 7 ) ShmCreate( 7, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 7 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_AREA_KEY ShmCleanup( 8 ) ShmCreate( 8, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 8 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_ROLL_AREA_KEY ShmCleanup( 9 ) ShmCreate( 9, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 9 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_CALI_BUFFER ShmCleanup( 11 ) ShmCreate( 11, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 11, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_CCC_KEY ShmCleanup( 12 ) ShmCreate( 12, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 12, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_ALERT_AREA_KEY ShmCleanup( 13 ) ShmCreate( 13, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 13, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_PRES_BUF ShmCleanup( 14 ) ShmCreate( 14, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 14, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup DVS_SHM_KEY ShmCleanup( 15 ) ShmCreate( 15, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 15, 0, 2, 0xffffffff7fffe9e0 ) DpCleanupSharedResources: ShmCleanup SHM_SEM_MONI_BUFFER ShmCleanup( 16 ) ShmCreate( 16, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 16, 3 ) ShmCreate( 16, 0, 2, -> 0xffffffff29004000 ) ShmDelete2( 10 ) Sun Jan 8 21:52:22 2012 DpCleanupSharedResources: ShmCleanup SHM_ROLL_ADM_KEY ShmCleanup( 17 ) ShmCreate( 17, 0, 2, 0xffffffff7fffeb28 ) ShmGet( 10, 17, 0, 2, 0xffffffff7fffe9e0 ) ShmCreate( 10, 0, 2, 0xffffffff7fffe828 ) ShmKeyPermission( 10 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PAGING_ADM_KEY ShmCleanup( 18 ) ShmCreate( 18, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 18 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_TBUFF ShmCleanup( 19 ) ShmProtect( 52, 3 ) ShmKeySharedMMU( 52 ) = 0 (octal) ShmProtect: shmat key 52 prot 3/0 done ShmCreate( 52, 0, 2, -> 0xffffffff77600000 ) DpCleanupSharedResources: ShmCleanup SHM_ES_ADM_T ShmCleanup( 53 ) ShmCreate( 53, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 53 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_DB_OBJ_BUFFER ShmCleanup( 54 ) ShmCreate( 54, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 54 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_RSPO_LOCAL_KEY ShmCleanup( 55 ) ShmCreate( 55, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 55 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PF_AS_KEY ShmCleanup( 56 ) ShmCreate( 56, 0, 2, 0xffffffff7fffeb28 ) ShmKeyPermission( 56 ) = 0740 (octal) DpCleanupSharedResources: ShmCleanup SHM_PROFILE ShmCleanup( 57 ) ShmCreate( 57, 0, 2, 0xffffffff7fffeb28 ) ShmProtect( 57, 3 ) ShmKeySharedMMU( 57 ) = 0 (octal) ShmProtect: shmat key 57 prot 3/0 done ShmCreate( 57, 0, 2, -> 0xffffffff75700000 ) DpCleanupSharedResources: ShmCleanup SHM_ENQID_KEY ShmCleanup( 58 )
Regards, VIjay K.G

Hi,
From logs:
28: No space left on device
Check the disk space. If linux, use df -h command. Windows its easier
Check if any drive / file system is 100% used up.
Regards,
Srikishan

Solution Manage Diagnostics - error in the system setup

Hello,
I have installed SMD and I installed one system with the Setup Wizard of the SMD. According to the result of the setup, it was successful.
However, when I do a self check in SMD, I get the five following errors in the Monitored Setup node :
5 error(s) found:
No DB agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No JVM startup parameters setting status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Roles assignment status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No SSO Setup status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
No Telnet agent autoconfig status found in SMD repository for sv42/SM1. Please make sure system has been setup in Monitored Setup.
Can anybody help me ?
Thank you

If you goto http://server:port/smd >>> Diagnostic Setup >>> Diagnostic System >>> Setup Wizard, do you have a message similar to:
Last Diagnostics setup wizard execution on Tue Oct 09 13:34:44 2007 :
- 0 setup steps disabled by user
- 13 setup steps succesfully executed
- 0 setup steps executed with warnings
- 0 setup steps in error
If you do, your Diagnostic server is correctly setup.
For Managed system, same thing, http://server:port/smd >>> Diagnostic Setup >>> Managed Systems >>> Setup Wizard, or check setup results to make sure it's completed.

SMSY - Generated RFC between solution mananger and a satellite system

Hi gurus,
I would like to ask you some things about configuration of SMSY - create systems and their RFC´s between solution manager (SSM) and a satellite system (for instance the DEV system SD3 (in solution manager system)
But my problem is which of these users I must use in each RFC???
Because until this moment I have been doing without knowing very well where I must put that users in those RFC´s!!!!! And I don´t know if I have been doing well!! You understand ?!? :- /
Can somebody give me a simple explanation about this... Which user I have to put (due to the authorizations) in those RFC connections?!
And other thing, if you don´t mind take a look to other question I ask yesterday which is related with this doubt:
Help me please... :- /
Thanks in advance
Best regards,
João Dimas

Hi Joao,
As I understand, the respective RFCs and users are created autmatically when the RFCs are
generated for a satellite system in SMSY.
Furthermore, the Z roles and profiles for each of these users are also created/generated during the
generation procedure. The roles/authorization assigned to each of the generated user are as mentioned
in the below link:
http://help.sap.com/saphelp_smehp1/helpdata/en/48/647e3ddf01910fe10000000a114084/frameset.htm
The administration/customizor specific authorization objects are also provided. As you mentioned the
above helps understand the roles/authorizations required for specific user with regards to an RFC.
Apart from this, all the actual creation, generation and assignment is done - thanks to the automated
setup in SMSY
Also I suppose the above link should help you decide the auhtorization objects requested by you
in the other thread.
Hope this helps.
Regards,
Srikishan

Multiple Solution Manager Connectivity to 1 Satellite system

Similar Messages

Maybe you are looking for