Sol Man 7.1 - SLD / LMDB Synchronisation Error

Hi experts,
I am trying to perfom a full synchronisation between LMDB of Sol Man 7.1 and our Central SLD (CIM 1.6.16, SAP_CR 7.3)
Somewhere around 20% - 30% the full synch gets an error and restarts automatically at 0%.
Error message in application log is:
Error in method call SAPExt_EnumerateInstancesNoSubclasses: Failed to leave transaction:
Full sync failed for class SAP_SoftwareFeatureSoftwareComponent
Full sync needs to be repeated after correcting this error
Error message #s:
BL001
LMDB_CS_ERROR023
LMDB_CS_ERROR024
Did raise a call already but no useful response until now.
Anyone else had problems like this?
Thanks

Hi,
[Note 1480419 - Release Restrictions for SAP Solution Manager 7.1|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1480419], this note saying the restriction on LMDB and SLD sync, Moreover they are suggesting to upgrade SP01 to fix the LMDB issue..
Have you tried out?
Thanks,
Jansi

Similar Messages

Sol Man Install-Windows/MSSQL-Import ABAP Errors

Hello,
During the Import ABAP phase (15 out of 41) of a Solution Manager 4.0 install on windows running MSSQL, I am seeing the below error in the SAPSDIC.log: ((IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful>)
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070122153431
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4
Compiled Sep 6 2006 00:36:09
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe -ctf I D:\Install_Export_EXP2\EXP2\DATA\SAPSDIC.STR C:\Program Files\sapinst_instdir\SOLMAN\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL SAPSDIC.TSK MSS -l SAPSDIC.log
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: job completed
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20070122153431
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: START OF LOG: 20070122153432
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe: version R7.00/V1.4
Compiled Sep 6 2006 00:36:09
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: /SDF/PAT03 created
(DB) INFO: /SDF/PAT03~0 created
(IMP) INFO: import of /SDF/PAT03 completed (0 rows) #20070122153435
(DB) INFO: APSRV created
(DB) INFO: APSRV~0 created
(IMP) INFO: import of APSRV completed (0 rows) #20070122153435
(DB) INFO: ASGRP created
(DB) INFO: ASGRP~0 created
(IMP) INFO: import of ASGRP completed (0 rows) #20070122153435
(DB) INFO: AUTHX created
(DB) INFO: AUTHX~0 created
Interface access functions from dynamic library dbmssslib.dll loaded.
(IMP) INFO: import of AUTHX completed (685 rows) #20070122153436
(DB) INFO: AVERS created
(DB) INFO: AVERS~0 created
(IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful>
(IMP) ERROR: EndFastload: rc = 2
(DB) INFO: AVERS_EXT created
(DB) INFO: AVERS_EXT~0 created
(IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful>
(IMP) ERROR: EndFastload: rc = 2
(DB) INFO: BADI_CHAR_COND created
(DB) INFO: BADI_CHAR_COND~0 created
(IMP) INFO: EndFastLoad failed with <2: Bulk-copy commit unsuccessful>
(IMP) ERROR: EndFastload: rc = 2
(DB) INFO: BADI_FILTER created
(DB) INFO: BADI_FILTER~0 created
(IMP) INFO: import of BADI_FILTER completed (52 rows) #20070122153437
Excerpt of import_monitor.log:
TRACE: 2007-01-22 15:41:08 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast
ERROR: 2007-01-22 15:41:08 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'D:\usr\sap\SLM\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSDIC.log' file.
Help please!
thanks...
Laurie

Update:
In the SAPSDIC log, I am seeing the following:
(DB) INFO: DDNTF created
(DB) INFO: DDNTF~0 created
rscpMCConvert: Error:
The output buffer was too short.
Size of output buffer was 1 bytes
Size of input buffer was 1 bytes
But only 0 bytes could be consumed
used ? ? addr=02505010 , len=0
unused00000000 42 |B
|
ERROR in nametab conversion
conversion of 'DDNTF '
current tabname (in hex):
2F314245412F424245415F42444820202020202020202020202020202020
rscpMCConvertNeutral error, rc = 32
function: get_version_conv
(CNV) ERROR: code page conversion failed
rc = 2
.--============--
RSCP - Error
Error from: Codepage handling (RSCP) 5
code: 32 RSCPETOOLONG The data was longer than the buffer.
convert output buffer overflow
module: rscpc no: 20 line: 11776 T100: TS006
TSL01: F39 p3: inlen&1&outlen&1&
`----
(DB) INFO: DDNTF_CONV_UC created
(DB) INFO: DDNTF_CONV_UC~0 created
rscpMCConvert: Error:
The output buffer was too short.
Size of output buffer was 1 bytes
Size of input buffer was 1 bytes
But only 0 bytes could be consumed
used ? ? addr=02505010 , len=0
unused00000000 42 |B
|
ERROR in nametab conversion
conversion of 'DDNTF_CONV_UC '
current tabname (in hex):
2F314245412F424245415F42444820202020202020202020202020202020
rscpMCConvertNeutral error, rc = 32
function: get_version_conv
(CNV) ERROR: code page conversion failed
rc = 2
When I was prompted for the Kernel NW04sSR1, the SAPINST would NOT except the 51032266_11 DVD (which is the 32bit UNICODE_Kernel 7.0 windows server IA32). It wanted the non-UNICODE DVD of 51032266_3.
If this is the issue, what is the correct Kernel to install??

Error while copy document in Sol Man

Dear friends,
I am working in Sol Man 4.0.
I have loaded the doc 'ABC" in SOLAR02. Now i want to copy the document in RMAMAIN using the option
"Assign Document" ---L> as a copy, i am getting the following error
"FOLDER CLASS IWB4FOLDER is NOT valid for objects of info object class SOLARGEN"
Please guide to solve this..
Regards
Kumar

Also have a look at the following notes:-
=> Note 26050 - FIPP:Posting not poss. (SAPMF05A,0700,batch input)
=> Note 800177 - FB01: No batch input data for SAPMF05A 0700
thanks
G. Lakshmipathi

Connecting SLD to Sol Man 4.0

Hi all,
I am trying to push my sld data to Sol Man 4.0. I have set up smsy_setup and ran sldcheck and set up sldapicust and everything seems o.k. but when I try to execute the job to pull data (SMSY_SETUP) and I review the update log I see a message stating "the sld server is inactive" and I am not sure why. I can log into sld and it's up an running so I don't know where to turn next.
One thing I do get is when I run sldcheck there is a message saying "No business systems found"?
Thanks,
Rodney Miller

Hi Rodney,
is the SLD brigde also running?
Go into SLD -> Administration -> Data Supplier Bridge, set update local SLD to true and start the bridge.
Business systems are only needed for XI, but not for what Solman is using.
Regards,
Pascal

SLD to LMDB synchronization error- cim model mismatch

Hello All,
In system preparation, we have configured the SLD and in the setup LMDB step we have added this SLD for synchronization to LMDB. Once we activate the synchronization (full sync) we first get a message "LMDB is on cim model 1.6.31 and SLD is on 1.6.37.Please confirm if you want to update LMDB to cim model 1.6.37." I clicked YES for this. Then it starts a job SAP_LMDB_LDB_0000000001 in the ABAP stack. However this job is getting cancelled with below message:
An exception of class CX_LMDB_CIM_ERR occurred
Classes for sync do not match: source model version 1.6.37, target 1.6.31
Can anyone advice what can be done to resolve this situation? Just FYI, This is not a new implementation there was another SLD that was connected to the LMDB earlier, however that stopped working due to a version mismatch. So now I am trying to sync the LMDB to a new SLD.
Thanks,
Anilraj Menon

Hi Anilraj,
When switching Your CRsource for the SLD/LMDB sync on Solution Manager, SOLMAN_SETUP You have to be very carefully as this is not a standard operation as such. You need to make sure that You don't have pending changes in the LMDB sync from the old SLD.
Furthermore, You should use the template in Solman_Setup, system preparation, step 5.2 --> click on "Advanced", and in actions, You should set the CRsource to the new SLD.
But please remark, this could lead to some inconsistence in Your LMDB thus the need to have no pending changes in the LMDB sync (You can see if there are any in the very same GUI where You set the CRsource - look in the "Status Details" pane: "Number of Source Changes Pending". This figure should be "0".
Also have a look on the blog from Wolf Hengevoss. I guess this adress Your exact problem:
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
Regards,
Kurt

Problem in moving project from Old Sol Man 3.1 to New Sol Man 4.0

Hi All,
I am trying to move a project from solution manager 3.1 version to a new solution manager 4.0 version. I followed the below steps:
1.Slected and transported the project using solar_project_admin tcode and created the transort requests in the old sol man version 3.1.
2.Copied the cofile and datafiles from old sol man and kept in trans directory of new Sol man 4.0 version at OS level.
3.Imported the requests into the new Sol Manager 4.0 successfully
4.When I tried to open the imported project it told me to run the "solman_log_comp_mgr program" to convert the project to the central logical components. I just did it and it went well.
I can see the project and do see the document types but no document names and getting all sorts of error messages when I tried to open these documents. Also I dont see the logical components under system landscape.
Before importing, I just have configured servers/hosts, databses and all the components of system landscapes in the new solution manager.
I request you to help me solve this issue. I also would like to know whether i followed proper procedures that i listed above? If not please suggest what procedures I should have follwed.
Thanks in advance.
Aravind Serikar

Hi Aravind,
to transport a project from 3.1 to 4.0 I would not use SOLAR_PROJECT_ADMIN to "migrate" a project. There for we developed SOLAR_MIGRATION there you can transport system landscape info, also you can transport projects. You should only transport system landscape info if in 4.0 SMSY is EMPTY. To transport projects you have only to specify your project and define a local folder. In this folder we store a few important information. Then all information will be collected in a batch job and automatically exported. Then you have to copy the data file and the cofile into the new trans folder. BUT do NOT forget the i-file. In the folder cofiles you will find a i-file, because we export knowledge warehouse content. This file is important, if you forget it you will get a return code 8. You do NOT have to add the files in the import buffer, we will do this automatically. To import the project, you have to call SOLAR_MIGRATION in SolMan 4.0 there you have to select import, then specify the folder with the few important information. We upload the info and start the import. That is it
Regards,
uDo

Sizing SOl Man and number/impact of Alerts

We are trying to access our sizing for a Sol man implementation. We
have read the sizing document and it proposes not to have more then 40
alterts per server. Is this 40 limitation at the alert group level or
the alert name level?
Example: Is the 40 limit based on a, b, c or (d and e)?
a. Database Monitoring
     b. Space management
           c1.Tablespaces
                                  system
                                       d.free space
                                       e. used space
           c2.Segments
          c3.Performance
          c4.SAP consistency
          c5.Health

Hello Jim,
Yes, this is correct for your current release and SP. There is no standard way to generate alerts for Communication Channels which are in error status. The alerting mechanism is based on messages. The message must throw an error for an alert to be generated.
However, some new functionality will be available with SP13. It does not cover exactly your requirement i.e. when a channel is in error. But it does cover channels that stop polling. See note 1808222 Trigger alerts if channel stops polling, for more details.
Regards
Mark

Unable to create EWA in SOL MAN

Hi Experts,
I configured EWA for SOL MAN....
I successfully generating alerts for satellite systems but not for own SOL MAN
Alert running successfully with PMS and Refresh sessins with out error
my RTCCTOOL not showing any errors/requiremwents...
please suggest...
version : SAP SOLMAN EHP1
Regards,
Siva.
Edited by: skreddy555 on Jan 30, 2011 1:38 PM

Hello,
So you are saying you can generate EWA reports for Satellite systems but not Solman itself?
That really doesn't give any details to the problem, as what has occured and what has not.
Is the EWA scheduled? Have you run solman_setup on Solution Manager as the managed system?
If you want to generate an EWA for Soman itself, then you also need to treat it like a managed system.
IWhat it the status in solman_ewa_adm? Is it active? If it is ther eand active it should be scheduled and then there should
be something in DSWP. Is the icon a bottle? 2 Bottles? A Red Flag? A Grey Diamond, a Document?
Is the maintenace package task scheduled and running with no errors? Are you using the SM_<SID>CLNT<nnn>_BACK RFC or the NONE RFC in SDCN as the back RFC and have you tested them?
Is SM:EXEC SERVICES finishing or cancelling? If it is cancelling is there a dump?
These are some things to check. But it is hard to even gues what the problem is because you have been so vague.
If you can describe what you have done to configure, what is working, and what seems not to be working, this would help to get an idea where & what the problem may be. But you generally need to treat the Solution Manager exactly the same as a satellite system when setting it up for EWA reporting. This make is both a managed and the managing system. So you can't skip any steps just because its the managing system. If you describe the problem in more detail, and if any part in the process is working, and what is not, that is helpful.
You should see it schedulied in DWSP. If not, then it's not scheduled. But the status in DSWP can tell a lot. A Red Flag means a problem with SDCCN tasks or the RFC, a Grey Diamond means important data is misisng and the report can't be generated, so that is a probelm is data collection, two flasks indicates sm:exec services has not run or is failing.
So you really need to give more information....unless I have already touch upon your problem, I don't know how helpful people can be but toss out general information.
I'd like to help more if you can give more details to what you see and don't see that you should.
Regards,
Paul

Generation of Configuration document through Sol Man

Dear Friends,
We are using Solution Manager for our R/3 implementation. In realization phase, we are capturing all transports in BC sets through Sol Man. Via Sol Man, i am executing t.code SCPR3 (Maintain BC set), after capturing all the confugurations in BC set, i am maintaining configuration related details in the same BC set, as below.
In SCPR3 t.code, in top menu,
Edit-----Add documentation.
Here i am maintaining all configuration related details. And saving as "Raw version".
The same way, for all the BC sets, i am maintaing the configuration related details within the same BC set itself.
My client requirement is:
1. Now i am calling all the BC set in Sol Man (t.code SOLAR02, "Configuration" tab, under "type" coloum, i am selecting, "BC set".
2. Now, if i generate "Configuration Guide", the system has to automatically pick the the configuration details, what i have maintained in the BC set (as Add documentation).
How to do this?
regards
Senthil

Dear Friends,
In SCPR3 t.code, in top menu,
Edit-----Add documentation. can we make this "Add documentation" to be mandatory? So without entering the details, one should not possible to SAVE the BC set.
Can we make any settings for this?
Thanks
Senthil

Latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0

Hi all,
I want to request SAP the latest DVDs of Support Package Stack for NW7.0, ERP 6.0, and Sol Man. 4.0, is it possible & how to do it?
Thanks,
Toan Do

Hi Toan,
It's possible to order them or download them from SAP Marketplace
http://service.sap.com/swdc
Regards
Juan

SAP Sol Man 4.0 Config guide

Can some one tell me where i can find SAP Solution Manager 4.0 config guide?
Also can some one send me any material for Sol Man certification exam.
will reward points
thanks
PR

Hi PR,
please have a look at: www.service.sap.com/instguides -> SAP Components -> SAP Solution Manager -> Release 4.0 for the Configuration Guide and other related Guides such as the Master Guide etc... Here you will also find links to other material.
For configuring the Solution Manager you need to go to transaction SPRO in your SolMan. Here you'll find the configuration of the Basic Setting, whcih you need to get it running and the scenariospecific settings, which are relevant for the scenarios.
Best regards,
Annett

SQL 2005 Authentication for Sol Man 4.0

Hi,
I have used the SQL4SAP.VBS to install SQL 2005 Entp Ed for Sol Man 4.0.
I do not know what authentication mode has been setup by this script
How do I know this ?
How can i change the mode to mixed mode as reuqired by Sol Man 4.0
I havent started the SAP Inst yet .
Thanks
Uday

Hi,
This is how you need to check.
1. In the Enterprise Manager, select the server and then choose Action ® Properties.
The SQL Server Properties dialog box opens.
2. Select the Security tab.
Here you can see. Hope this solves your problem. Feel free to revert back.
--Ragu

Sol Man 4.0 and Test Director 8.0

Hi,
We currently run Mercury's Test Director 8.0 (SP2) where we store all of our manual and automated test scripts.
We are also planning to use our Solution Manager 4.0 to create our project, our blueprint/configuration and from there on link our test cases to the process steps.
I've read that there is integration between Test Director.
What I'm looking for is that since all of our test scripts are stored in Test Director, is it possible to link those individual scripts to each process steps.
In the Test Case tab of Sol Man, there is the Test Case Type column with several options. If I select "Test document" and use "Web Link" to link to the test script, it would only bring me to the log-on page of Test Director upon which I would need to log-on and then search the Test lab for my script.
Just wondering if there's a way to accomplish (without downloading all of our scripts from Test Director and then uploading them to Sol Man.
Any thoughts would be appreciated.
Thanks
Danielle

Daniella,
Please take a look at this thread.This might help you how to integrate Sol Mngr with Test Director.
Solution Manager integration with Mercury product
Thanks
Sudhan Shan

Sol Man 4.0 and Reporting out to BW

We have upgraded to Sol Man 4.0 and need to report the Change Request info, Change Document info and Transports log using an external BW box. In researching this forum, I have learned that we can export data out by activating the CRM business content. I need more guidance as to what DataSources to use. So far we have activated and found data in 0CRM_SRV_PROCESS_H and 0CRM_SALES_ACT_1, but I am missing information such as Change Advisory Board, Subject, External Reference, Decision Date, and Implementation date to name a few. Can anyone help? Is this documented ANYWHERE?? Thank you.
Charis Davenport
Project Management Specialist
The Walt Disney Company

Daniella,
Please take a look at this thread.This might help you how to integrate Sol Mngr with Test Director.
Solution Manager integration with Mercury product
Thanks
Sudhan Shan

Digital Signatures in eCATT or Sol Man

Hi All,
How can we include digital signatures feature either in eCATT scripts or in sol man.
Regards,
Justin

HI Justin,
I am afraid I cannot be of much help either as it very much seems like SAP has not extended the digital signature functionality besides it's current support for approvals of test documents and notes in the test management domain.
To be able to use this function:
SAP Solution Manager -> Scenario specific settings -> Implementation -> Document Management -> Digital Signature & Document status
Please note that there is a 'catch' here which might be of help to you : Manual test cases of type - 'Test document' can also use this feature.
I did not find any customizations possible for automated test cases like eCATT
I, myself, am not in a position to try this feature and let you know.
However, if you are interested in the document, please revert with your email id so that I can mail it to you.
Byeeee!

Sol Man 7.1 - SLD / LMDB Synchronisation Error

Similar Messages

Maybe you are looking for