XI installation with central SLD

Hello,
I have installed solution manger to generate key for XI installation. But, when i in stall solution manager, it installed MaxDB and local SLD and also i think WEBAS ABAP. After that i generated the key.
And, I am installing XI on the same host. There is no configuration as such i did.I tried to use the same solution manger DB, but i t failed. So i started with New DB creation. And central SLD........
Is there any configurations that i need to do to install XI with our any errors.
When i used existing SLD, is there any configuration i have to do.
More important, i have to install solution manager and XI on same host
Can anybody any issues here.
Please advice,
Srini

This should be straight forward.
If the SLD is set up for Sol Man, you enter these details on the in the installation wizard.
You will need seperate SIDs and you will need to assign the Virtual host names for each installation.
You will need to check the SLD config after install. the two sm59 conenctions - LCRSAPRFC & SAPSLDAPI, the sldapicust, the JCo Connections in Visual Admin and the SLD Data Supplier in Visual ADmin.

Similar Messages

Adapter monitoring with central SLD!

Hi ,
we have central SLD in our landscape(different host from XI server),and our basis guys installed PI7.0 SP12.And AE is local as I can see under Integration server.
I can see JPR in adapter in adapter monitoring.
I have question here!
should it needs to show all the list of adapters (FILE,JDBC,JMS,SOAP etc)in adapter monitoring in RWB?does it vary,if sld is central or local ?
what is the ideal way.
thank you,
babu

where the adapter engine should appear in RWB under integration server or under non central adapter engine if we have installed central AE and central SLD?
Under Component monitoring -> Integration server -> Adapter Engine
and it has show all the adapters when we install central AE and with central SLD when we furthur click the show all adapters?
As i mentioned above, u may view all the adapters after clicking
Adapter Engine -> Adapter Monitoring
or is it changed since PI 7.0 to cummunication channel monitoring and no adapter monitoring?
Yes. Now the monitoring of adapters r much intensively done by Communication Channel Monitoring
Regards,
Prateek

Instalation help Central SLD parameters connection

Hi Dear All,
I am installing solman 4.0 SR1 on Windows 2003 and Microsoft SQL.
during the instalation i got a screen which iam not aware of please help me
The scren says :
SELF REGISTRATION OF JAVA ENGINE in CENTRAL SLD:
SLD HTTP HOST -
SLD HTTP PORT -
SLDDATA SUPPLIER USER: SLDDSUSER
PASSWORD:
SELF REGISTRATION OF ABAP ENGINE IN CENTRAL SLD
SLD GATEWAY HOST: -
SLD GATEWAY INSTANCE NUMBER: -
COMMUNICATION WITH CENTRAL SLD:
SLD ABAP API USER: SLDAPIUSER
PASSWORD:
Please help what i have to choose and where i can find the relavent information.
kind regards,
Vamsi.

Hi,
For SLD configuration during installation,
SLD HTTP HOST - can be any name need not be your computer name. E.g <SID>SLD or <SID>SLDSRV or something like that.
SLD HTTP PORT - the port would be 50<instancenumber>00
eg:- 500100 where 01 is instance number.
as SLDDATA SUPPLIER USER and SLD ABAP API USER are automatically populated. just maintain your password.
That's it.
This will solve your problem. Feel free to revert back.
--Ragu

Local SLD not updating a central SLD

Hi,
In my company landscape, I have
SolMan7.1 with Central SLD (Let's call this SLDA)
Portal 7.02 with local SLD (Let's call this SLDB)
ECC6
Both the Portal and ECC systems are updating SLDB, so I can see both technical systems in SLDB.
SolMan is updating SLDA, so I can see SolMan technical system in SLDA.
I linked SLDB to SLDA via
From SLDB> administration> data suppliers --> add SLDA
For this setting, I use the user SLDDSUSER, which have a role LcrInstanceWriterAll.
The problem now is SLDA does not get the data from SLDB. In SLDA, I see only the SolMan Technical System.
How often does SLDB update SLDA? Can we manually trigger an update SLDB->SDLA?
How can we troubleshoot the SLDB -> SLDA update?
What else needs to be configured other than "From SLDB> administration> data suppliers --> add SLDA" ?
Thanks
Edited by: Nick Foo on Sep 27, 2011 3:53 AM

Hi Sunny,
yes I have done those steps. Very short and easy setup steps to link to another SLD.
OK, just one thing to confirm here.
After Add SLD, the SLD URL syntax should be http://host:port correct?
I have tried all sorts of entires for the URL
http://host:port
http://host:port/sld
http://host:port/
All not working
Checked the user, user is ok, even tried giving the user Administrator role and still not working

Switching from central SLD to local SLD

Hello,
i have installed BI Java with central sld.
Could I switch back from cetral sld to local sld?
I didn't find any documentation or posts.
Thanks,
Sabrina

Hi,
Yes you can change the SLD configuration from local to central or a vice versa...
Please check the following SAP Note for your reference
Note 720717 - Reduce the number of System Landscape Directories (SLD)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/29b1f3ea-0c01-0010-2dae-cc64bb381c97
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e5e7cc9b-0501-0010-adb2-ffbe7f1f7e6f
Hope this helps,
Regards
CSM Reddy

Central SLD/Local SLD

Hello All,
Is there limitation with central SLD over Local SLD?.
To deploy Webdynpro applications (Mobile) please let me know if there are any limitations
Thanks

Hello.
SLD architecture is a long discussion
There are different views on how to set up SLD's.
In my oppinion, the limitations of SLD is that it's a central component to a growing number of netweaver component.
Right now, the portal, webdynpro, xi, nwdi wouldn't work very well without the SLD.
Considering this there is aspects on how to set up the SLD's. Usually critical systems have a local SLD, with supplyer briges to central SLD's.
You would have a separate SLD landscape for Production servers, since they usually run on different SLA (service level agreements).
If you're using NWDI, it's usually a good place to have you're central SLD.
If you're running a smaller landscape, go for the local SLD only and don't complicate your landscape too much.
Check this document (about last slide) with different SLD scenarios. https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/204994f3-0e44-2a10-17b3-808fbd8db4aa
Regards, Mikael Löwgren

Syncronizing two Solutions Manager with One SLD

Hello Experts, we have this issue: I am having one Central SLD in PI and one productive Solution Manager (new one) that is pointing to that SLD, for incidents we are managing another ¨productive¨Solution Manager (old one) . There is a new system that I need it in my SMSY in my old Solution Manager and the best way to do it would be to point that old Solman to the same SLD that the new one is pointing. my question is: I only have to set the SLD in the old solution manager in the RZ70 and add that Solution Manager in the Central SLD?, so I would end with two solution manager pointing the same Central SLD, it doesnt mess with my new productive Solution Manager SMSY?, I want to be sure that some trash data in the old Solution Manager wont be present in the new Solman that is pointing the Central SLD right now.
Best Regards,
Paul

Dear Mr. Paul,
There are few things to understand:
1. RZ70 is used to feed SLD with system information.
2. landscape fetch job need to be scheduled within Solution manager system to update SMSY with the latest information available in SLD which you have configured during SOLMAN_SETUP.
Here with your description it is clear that you have central SLD at your PI system and your both Solution manager system ( New and Old) are connected to the central SLD.
Here what I understand if you want to add a new system say X in SMSY of your old solution manager.
In order to do so you need to configure your new system to the central SLD using RZ70. Once you did this, system details of your new system would be available with central SLD.
Now in next step to make that system available to your old solution manager, you need to rerun the smsy_setup job. This will referesh your SMSY and new system would be available in SMSY of your OLD solution manager.
In this case there is a catch. Since you have added the system to the central SLD, the new system X would also appears in the SMSY of your new Solution Manager as well once SMSY of new solman gets refreshed.
So if you just want to add this new system X to SMSY of your old solution manager only and not to the new one, you can add this system to the local SLD of old solution manager only not to the central SLD.
Also you need not to worry about the trash data available in your Old solution manager. It would not effect the central SLD if your local SLD of old solution manager is not synch with central SLD.
Regards,
Sachin

Error in installation of Central Instance in Windows Cluster with Oracle

Hi!
If I try to continue with the installation of Central Instance of Cluster I get the following error:
The java load in database <sid>/<server> has already been configured.
Solution: remove the schema and load it with a new load before you run this installation
Can some one tell me how to proceed?
Thank you very much!
Regards
Thom

Thom,
Did you figure this one out?
Thanks
S.

Pi 7.1 Central SLD

I have installed PI 7.1 and will use it as central SLD. I am installing SCM 2007, ECC Oil and Gas and BI 7.0 and want to point these systems to the central SLD in PI system.
During the install the WAS 7.0 system use SLDDSUSER however there is no user like this on PI 7.1.
SCM 2007 install had as default SLDDSUSER but that user doesn't exist in the PI 7.1 install.
I check SAP notes and can't find nay notes regading this change.
I did find an account that is close to this SLD_DS_DS1 where DS1 is the SID.
Has anyone ran into this issue with WAS 70 and WAS 71 installations? Is it safe to select SLD_DS_SID as the correct one for hooking in my other component systems into the Central SLD on PI 71?
Thanks
Mikie Brogan

We have the same situation. Can you explain How?
Thank you
Raj GA

Central SLD and Webdynpro

Dear all,
I have a new EP 6.0 installation running ESS/MSS and BW reporting and implemented central SLD.The SLD server was the CEN Solution Manager system. Because of some issues with support pack application in the solution manager system, the solution manager system was unavailable for a week. As the Webdynpro JCOs that are used in ESS/MSS use SLD, ESS/MSS in my portal systems became unavailable for my users. I had to configure local SLDs for each portal system to avoid the application downtime
I am wondering what people are doing out there to avoid what happened to me: High Availability? Seems a bit over the top as we do not have HA for our mySAP ERP production system which is the most important system of the landscape. Any other thoughts or SAP recommendations would be very much appreciated
Many thanks
Andreas

Hi,
Ofcourse HA should be one of the strategies you should think about. But now that you don't have it in place and cause for downtime is something like upgrade or maintenance, which is unavoidable, you can maintain the ECC system (HCM System) in your SLD, point the JCo Connections to your ECC system and thereby you should be able to use ESS-MSS. This won't take more that an hour, trust me.
Would also like to know what's your User Management Strategy ? If you are using the solution manager as your datasource for user management on portal, then you can hardly do anything.
Cheers,
Sunil
PS: Reward points for helpful answers.

Local sld pull from central sld

We are in the process of configuring a brand new sp19 solution manager server. We have a central sld on a dedicated server with several systems already registered on it I created a local sld on the new solution manager server. I want to pull the systems from this central sld server into the solution manager server, but cant' seem to find any documentation on how to do it.
I've read the SLD planning guide, the sld post-installation guide,, and the sld user guide. If there are any steps that document how to do this, I've missed them.
Can anybody help?
--Carl

On your central SLD: Administration -> Data Suppliers -> Add SLD...
Type in URL, valid user and pass and that should be it. It works this way on SLD based on NW70.

Regarding Central SLD and Local SLD

Hello,
Can we maintain Central SLD as well as Local SLD?
We have maintain central sld during installation , now i want to maintain local sld also.
How can we do this? what is the benifit and disadvantage for maintaing both?
Regards,
V.Singh

Hi V.Singh
You can have as many SLD as you like - the service is available as part of a WAS JAVA install
Bear in mind the more SLD = the more administration and if you wish to sync them there is also many considerations
It is best you check the SLD planning guide at System Landscape Directory (SLD) to select the landscape that
best suits the intend use
The Central SLD concept is primarily to have an SLD containing all systems in your company i.e complete overview - this might not be specifically used for runtime of these systems - say PI useage etc - it might be used to populate Solution Manager with landscape data or just track all systems and changes in the organization
The central SLD concept is also not essential however an SLD (a local or app specific one) is essential for certain applications like PI, ESS etc
Best wishes
Stuart

Migrate local SLDs to a centralized SLD

We are in a big SAP project with one full landscape for each new SAP product (e.g. SRM, ECC, EP, BI, etc.)
We have a centralized SLD on a SM7.0.
We have 2 options when installing each system:
1) use the centralized SLD for each new install
2) use the local SLD for each new install, then change all local SLDs to the centralized SLD.
What will be the pros and cons of each option?
Thanks!

Hello Linda,
Eventually ,you want to register your systems to the central SLD.
You can do it in both ways,but during installation when you select the option of Configure a Local SLD SAPinst says that it will take longer time ,thats it no other issues.
So best is that you register your systems to Cenral/Remote SLD.The remote SLD should be running and available at that time.
Have a look at this blog /people/boris.zarske/blog/2008/03/21/sld-general-recommendation-how-to-set-up-the-system-landscape-directory , it will give you more wider view of planning the SLD.
Regards
Ajay

Need Suggestion on Central SLD System

Hi Experts,
I need a help/ suggestion on deciding the Central SLD system in our landscape. In our current SAP System landscape we do not have XI Servers for Central SLD, So we are using Solution Manager 7.01 as the Central SLD for the new Installations and including the old Systems too. But We came to know that SAP does not recommend using Solution Manager as the productive SLD System.
So we have stopped the process of including old systems to Solution Manager now and we decided to build the system for central SLD which is recommended by SAP. So please suggest me which system is more recommended by SAP like EP/ ECC/ NW or any other.
Thanks.

Hello Ajay,
you posted the question on wrong forum.
This forum is for sap business one.
Post your thread on appropriate forum to get the replies.
*Close this thread.
Thanks,
Neetu

SAP R-3 IDES 4.71 installation with Oracle9i

Hello
I am having problems installing SAP R-3 IDES 4.71 installation with Oracle9i on windows 2003 Server. The log file comes up with this erorr
INFO 2008-05-14 22:50:30
Changed working directory to C:\SAPinst ORACLE SAPINST.
INFO 2008-05-14 22:53:59
See 'C:\usr\sap\DEV\SYS\exe\run/startsap name=DEV nr=00 SAPDIAHOST=bw2003' output in 'C:\SAPinst ORACLE SAPINST\startsap.log'.
TRACE
ProgramReturnCode='-1' means error.
ERROR 2030-05-14 22:53:59
MOS-01012 PROBLEM: 'C:\usr\sap\DEV\SYS\exe\run/startsap name=DEV nr=00 SAPDIAHOST=bw2003' returned with '-1' which is not a defined as a success code.
Windows 2003 Server
AMD 2GH Dual core
2GB Ram
250GB HDD
Computer name: bw2003
Central instance: DEV
I checked the host file system32/drivers/etc the IP adress and the host name is there.
I am hoping that someone could help me with the installation thanks in advance.
waiting .....

ok here you go
dev_disp
trc file: "dev_disp", trc level: 1, release: "620"
Sat May 18 00:27:08 2030
kernel runs with dp version 3(ext=1) (@(#) DPLIB-INT-VERSION-3)
length of sys_adm_ext is 304 bytes
systemid 560 (PC with Windows NT)
relno 6200
patchlevel 0
patchno 674
intno 20020600
pid 2276
***LOG Q00=> DpSapEnvInit, DPStart (00 2276) [dpxxdisp.c 978]
 shared lib "dw_xml.dll" version 674 successfully loaded
 shared lib "dw_xtc.dll" version 674 successfully loaded
 shared lib "dw_stl.dll" version 674 successfully loaded
MtxInit: -2 0 0
DpShMCreate: sizeof(wp_adm) 9776 (752)
DpShMCreate: sizeof(tm_adm) 1690816 (8412)
DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
DpShMCreate: sizeof(comm_adm) 192000 (384)
DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
DpShMCreate: SHM_DP_ADM_KEY (addr: 042F0040, size: 1974816)
DpShMCreate: allocated sys_adm at 042F0040
DpShMCreate: allocated wp_adm at 042F0560
DpShMCreate: allocated tm_adm_list at 042F2B90
DpShMCreate: allocated tm_adm at 042F2BB8
DpShMCreate: allocated wp_ca_adm at 0448F878
DpShMCreate: allocated appc_ca_adm at 04493EC8
DpShMCreate: allocated comm_adm_list at 04495638
DpShMCreate: allocated comm_adm at 04495650
DpShMCreate: allocated ca_info at 044C4450
DpShMCreate: allocated wall_adm at 044C4458
MBUF state OFF
Sat May 18 00:27:09 2030
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 1024 kByte.
Using implementation std
<EsNT> Memory Reset enabled as NT default
<EsNT> EsIUnamFileMapInit: Initialize the memory 307 MB
<ES> 306 blocks reserved for free list.
ES initialized.
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, NiPServToNo ( sapmsDEV) [nixxi.c 2599]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c 1451]
Sat May 18 00:27:18 2030
CCMS: Initalizing shared memory of size 20000000 for monitoring segment.
Sat May 18 00:27:32 2030
CCMS: start to initalize 3.X shared alert area (first segment).
Sat May 18 00:27:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
Sat May 18 00:27:50 2030
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:28:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:28:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:28:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:29:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
ERROR => W0 (pid 2328) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W0
ERROR => W11 (pid 2416) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W11
my types changed after wp death/restart 0xbf --> 0xaf
ERROR => MsIModTypes: not_attached [msxxi.c 1567]
Sat May 18 00:29:30 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
ERROR => W5 (pid 2368) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W5
ERROR => W6 (pid 2376) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W6
ERROR => W7 (pid 2384) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W7
my types changed after wp death/restart 0xaf --> 0xad
ERROR => MsIModTypes: not_attached [msxxi.c 1567]
Sat May 18 00:29:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
ERROR => W2 (pid 2344) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W2
ERROR => W8 (pid 2392) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W8
ERROR => W10 (pid 2408) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W10
ERROR => W12 (pid 2424) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W12
my types changed after wp death/restart 0xad --> 0x89
ERROR => MsIModTypes: not_attached [msxxi.c 1567]
Sat May 18 00:30:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
ERROR => W1 (pid 2336) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W1
Sat May 18 00:30:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:30:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:31:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:31:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:31:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:32:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
ERROR => W3 (pid 2352) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W3
ERROR => W4 (pid 2360) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W4
ERROR => W9 (pid 2400) died [dpxxdisp.c 11523]
force unlock of wp_adm mutex W9
Sat May 18 00:32:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:32:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:32:51 2030
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
Sat May 18 00:33:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:33:11 2030
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
Sat May 18 00:33:13 2030
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
Sat May 18 00:33:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:33:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:34:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:34:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:34:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:35:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:35:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:35:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:36:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:36:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:36:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:37:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:37:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:37:33 2030
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndName () [dpxxdisp.c 3885]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
ERROR => MsISnd2: not_attached [msxxi.c 1139]
***LOG Q0N=> DpRqNoWpHandle, MsSndAdmin () [dpxxdisp.c 3966]
Sat May 18 00:37:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:38:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:38:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:38:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:39:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:39:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:39:49 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:40:09 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:40:29 2030
***LOG Q0I=> NiPServToNo: getservbyname [ninti.c 428]
***LOG Q0A=> NiIServToNo, service_unkown ( sapmsDEV) [nixxi.c 2580]
ERROR => MsIAttach: NiBufConnect to bw2003/sapmsDEV failed (rc=NIESERV_UNKNOWN) [msxxi.c 545]
Sat May 18 00:40:30 2030
caught signal 2
Sat May 18 00:40:42 2030
***LOG Q05=> DpHalt, DPStop ( 2276) [dpxxdisp.c 7883]
dev_w0
trc file: "dev_w0", trc level: 1, release: "620"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, M
B
B Sat May 18 00:27:19 2030
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' ...
B Library 'C:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' loaded
B Version of 'C:\usr\sap\DEV\SYS\exe\run\dboraslib.dll' is "620.02", patchlevel (0.549)
B New connection 0 created
M systemid 560 (PC with Windows NT)
M relno 6200
M patchlevel 0
M patchno 674
M intno 20020600
M pid 2328
M
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 2328) [dpxxdisp.c 1028]
I MtxInit: -2 0 0
M
M Sat May 18 00:27:24 2030
M DpShMCreate: sizeof(wp_adm) 9776 (752)
M DpShMCreate: sizeof(tm_adm) 1690816 (8412)
M DpShMCreate: sizeof(wp_ca_adm) 18000 (60)
M DpShMCreate: sizeof(appc_ca_adm) 6000 (60)
M DpShMCreate: sizeof(comm_adm) 192000 (384)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: SHM_DP_ADM_KEY (addr: 04AF0040, size: 1974816)
M DpShMCreate: allocated sys_adm at 04AF0040
M DpShMCreate: allocated wp_adm at 04AF0560
M DpShMCreate: allocated tm_adm_list at 04AF2B90
M DpShMCreate: allocated tm_adm at 04AF2BB8
M DpShMCreate: allocated wp_ca_adm at 04C8F878
M DpShMCreate: allocated appc_ca_adm at 04C93EC8
M DpShMCreate: allocated comm_adm_list at 04C95638
M DpShMCreate: allocated comm_adm at 04C95650
M DpShMCreate: allocated ca_info at 04CC4450
M DpShMCreate: allocated wall_adm at 04CC4458
X
X Sat May 18 00:27:28 2030
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation std
M <EsNT> Memory Reset enabled as NT default
X ES initialized.
M
M Sat May 18 00:27:33 2030
M calling db_connect ...
C Got ORACLE_HOME=C:\oracle\ora92 from environment
C
C Sat May 18 00:28:05 2030
C Client NLS settings: AMERICAN_AMERICA.WE8DEC
C
C Sat May 18 00:28:06 2030
C Logon as OPS$-user to get SAPDEV's password
C Connecting as /@DEV on connection 0 ...
C Attaching to DB Server DEV (con_hdl=0,svchp=062414CC,svrhp=06243724)
C
C Sat May 18 00:28:17 2030
C Starting user session (con_hdl=0,svchp=062414CC,srvhp=06243724,usrhp=0624BEFC)
C
C Sat May 18 00:28:33 2030
C Now I'm connected to ORACLE
C Got SAPDEV's password from table SAPUSER
C Got SAPDEV's password from OPS$-user
C Disconnecting from connection 0 ...
C
C Sat May 18 00:28:34 2030
C Closing user session (con_hdl=0,svchp=062414CC,usrhp=0624BEFC)
C Now I'm disconnected from ORACLE
C Connecting as SAPDEV/<pwd>@DEV on connection 0 ...
C Starting user session (con_hdl=0,svchp=062414CC,srvhp=06243724,usrhp=0624BEFC)
C Now I'm connected to ORACLE
C Database NLS settings: AMERICAN_AMERICA.WE8DEC
C Database instance dev is running on BW2003 with ORACLE version 9.2.0.2.1 since 20300518
B
B Sat May 18 00:28:35 2030
B Connection 0 opened
B Wp Hdl ConName ConId ConState TX PRM RCT Date Time DBHost
B 000 000 R/3 000000000 ACTIVE NO YES NO 20300518 002733 BW2003
M
M Sat May 18 00:28:36 2030
M db_connect o.k.
I
I Sat May 18 00:29:01 2030
I MtxInit: 0 0 0
X
X Sat May 18 00:29:02 2030
X EmInit: MmSetImplementation( 2 ).
X <ES> client 0 initializing ....
X Using implementation std
X ES initialized.
B db_con_shm_ini: WP_ID = 0, WP_CNT = 13
B dbtbxbuf: Buffer TABL (addr: 0C2000C8, size: 30000000, end: 0DE9C448)
B dbtbxbuf: Buffer TABLP (addr: 0DEA00C8, size: 10240000, end: 0E8640C8)
B Layout of EIBUF buffer shared memory:
B 0: 1 * 4 = 4
B 1: 1 * 276 = 276
B 2: 13 * 20 = 260
B 3: 4001 * 40 = 160040
B 4: 2000 * 128 = 256000
B 5: 4001 * 4 = 16004
B 6: 1 * 100 = 100
B 7: 65 * 4 = 260
B 8: 29385 * 128 = 3761280
B Tracing = 0, Shm Protection = 0, Force checks = 0
I *** ERROR => [CreateOsShm] CreateFileMapping(54,4096 KB) failed with Err=1455
 ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete. [shmnt.c 2055]
I *** ERROR => ShmCreate: Create (54,4194384,1) failed [shmnt.c 469]
Memory diagnostic *
Systeminformation
Processor-Typ : Intel unknown
Processor-Count : 1
Operating System : NT 5.2, Build 3790
Service Pack : Service Pack 1
NT Pagefile Informations
Config. minimum size : 589824 K
Config. maximum size : 1179648 K
Avail. maximum size : 1179648 K
Num
Pagefile
Min.Size
Max.Size
Avail.Max
Curr.Size
1
C:\pagefile.sys
589824 K
1179648 K
1179648 K
1178900 K
NT Task Manager Informations
Total Handles : 0
Total Threads : 0
Total Processes : 0
Commit Charge Total : 1670224 K
Commit Charge Limit : 1676596 K
Commit Charge Peak : 1670376 K
Phys.Memory Total : 0 K
Phys.Memory Available : 0 K
File Cache : 0 K
Kernel Memory Total : 0 K
Kernel Memory Paged : 0 K
Kernel Memory Nonpaged : 0 K
Memory usage of current process
Total virt.address space : 2097024 K
Avail.virt.address space : 1133576 K
Private Pages : 0 K
Total heap size : 10729 K
Virtual memory regions : 0 K
Uncommitted heap memory : 4108 K
Allocated heap memory : 4406 K
Moveable heap memory : 24 K
DDE shared heap memory : 0 K
Memory usage of all processes
PID
Image
Instance
Work.Set
WS Peak
Priv.Pages
PP Peak
Pg Fault
4
72 K
2100 K
0 K
0 K
3
352
smss.exe
212 K
448 K
144 K
160 K
0
424
winlogon.exe
996 K
9048 K
6188 K
6580 K
3
468
services.exe
1276 K
3136 K
1436 K
1564 K
0
480
lsass.exe
2148 K
6544 K
7048 K
7048 K
1
676
svchost.exe
552 K
2508 K
832 K
832 K
0
848
svchost.exe
4840 K
22520 K
13348 K
19208 K
9
972
spoolsv.exe
712 K
4060 K
3220 K
3228 K
1
1124
svchost.exe
392 K
1956 K
476 K
476 K
0
1176
agntsrvc.exe
948 K
7720 K
9128 K
9128 K
1
1196
TNSLSNR.exe
2432 K
5720 K
5764 K
5776 K
1
1212
cmd.exe
384 K
1572 K
1488 K
1488 K
0
1228
ORACLE.EXE
122564 K
135924 K
203080 K
205256 K
38
1324
SAPSTARTSRV.EXE
2520 K
13364 K
14828 K
14828 K
3
1420
VMwareService.exe
928 K
2164 K
604 K
604 K
0
1528
dbsnmp.exe
2240 K
11312 K
13608 K
39264 K
3
1816
Explorer.EXE
2928 K
15120 K
10200 K
10332 K
13
1864
jusched.exe
252 K
1764 K
432 K
432 K
0
1872
VMwareTray.exe
724 K
3144 K
852 K
888 K
0
1880
VMwareUser.exe
1376 K
3284 K
1032 K
1048 K
0
1996
svchost.exe
488 K
3740 K
1440 K
21664 K
1
216
svchost.exe
800 K
3708 K
2788 K
2788 K
0
2080
sapinst.exe
82868 K
105272 K
84324 K
105292 K
41
2088
javaw.exe
6944 K
21272 K
20396 K
20896 K
6
2200
startsap.exe
460 K
1772 K
748 K
748 K
0
2212
sapstart.exe
1244 K
3176 K
1188 K
1188 K
0
2276
disp+work.exe
[DP] DEV_00
26740 K
42464 K
30176 K
30176 K
10
2312
gwrd.EXE
[GW] DEV_00
1852 K
6116 K
3936 K
8208 K
1
2320
icman.EXE
56440 K
60192 K
75880 K
75880 K
17
2328
disp+work.EXE
[WP] DEV_00
10700 K
11516 K
43684 K
43788 K
7
2336
disp+work.EXE
[WP] DEV_00
6696 K
13084 K
42180 K
42180 K
6
2344
disp+work.EXE
[WP] DEV_00
10896 K
14092 K
42180 K
42180 K
6
2352
disp+work.EXE
[WP] DEV_00
10088 K
14588 K
42176 K
42176 K
6
2360
disp+work.EXE
[WP] DEV_00
9320 K
12960 K
42184 K
42184 K
6
2368
disp+work.EXE
[WP] DEV_00
9480 K
13076 K
42184 K
42184 K
6
2376
disp+work.EXE
[WP] DEV_00
10060 K
13220 K
42180 K
42180 K
6
2384
disp+work.EXE
[WP] DEV_00
10024 K
15128 K
42184 K
42184 K
6
2392
disp+work.EXE
[WP] DEV_00
6576 K
14752 K
42180 K
42180 K
6
2400
disp+work.EXE
[WP] DEV_00
8812 K
13436 K
42184 K
42184 K
6
2408
disp+work.EXE
[WP] DEV_00
8552 K
16140 K
42180 K
42180 K
6
2416
disp+work.EXE
25744 K
25972 K
41644 K
43788 K
10
2424
disp+work.EXE
[WP] DEV_00
6848 K
11060 K
42180 K
42180 K
6
Sum
460128 K
1063904 K
B dbexpbuf[0]: Shm 54: create failed
B ***LOG BBF=> internal error in export/import buffer: object buf init fail [dbexpbuf#4 @ 2611] [dbexpbuf2611 ]
B dbexpbuf: return code (sap_rc): 4
B Buffer 0 will not be available
B Unexpected returncode from db_exp_init(EXP_ATP) : 4
B db_objinit failed
M *** ERROR => ThCallHooks: event handler db_init for event CREATE_SHM failed [thxxtool3.c 237]
M *** ERROR => ThIPCInit: hook failed [thxxhead.c 1656]
M ***LOG R19=> tskh_init, ThIPCInit ( TSKH-IPC-000001) [thxxhead.c 1159]
M in_ThErrHandle: 1
M *** ERROR => tskh_init: ThIPCInit (step 1, th_errno 17, action 3, level 1) [thxxhead.c 8437]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M tid = -1
M mode = 255
M len = -1
M rq_id = -1
M rq_source = 255
M last_tid = 0
M last_mode = 0
M rfc_req = 0
M report = > <
M action = 0
M tab_name = > <
M
M *****************************************************************************
M *
M * LOCATION SAP-Server bw2003_DEV_00 on host bw2003 (wp 0)
M * ERROR tskh_init: ThIPCInit
M *
M * TIME Sat May 18 00:29:02 2030
M * RELEASE 620
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 17
M * MODULE thxxhead.c
M * LINE 8569
M * COUNTER 1
M *
M *****************************************************************************
M
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 672]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 237]
M Entering ThSetStatError
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 2328) [dpnttool.c 346]
M SemCleanup: Reset blocking on semaphore (Key:4/Slot:3)
Thanks buddy
waiting...

XI installation with central SLD

Similar Messages

Maybe you are looking for