Cant edit my solution in Solution Manager 7.1

Hi experts
I moved a database for 1 of my systems to a new host. There for I had to create a new technical system for the system.
Now I need to add this new system to my solution. This is where I am stuck.

Hi
I found where they are used , but i´m not sure how I can replace ibp200 with the new system.

Similar Messages

FAQ - SAP Solution Manager for VARs

You can find further technical questions around configuration & functionalities in a comprehensive
FAQ to SAP Solution Manager for VARs.
This FAQ covers questions and answers around:
    > SAP Solution Manager, enterprise edition
    > SAP Solution Manager VAR setup: configuration of Service Desk
    > Work Center Service Desk: functions & configuration
    > Work Center System Monitoring: setup of SAP EarlyWatch Alert
You can access the FAQ directly thru the following link [FAQ - SAP Solution Manager for VARs|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000722612&_OBJECT=011000358700000490172009E].
Navigation path: SAP Service Marketplace > SAP Support Portal > SAP Support Infrastructure > SAP Solution Manager > SAP Solution Manager for Partners > Information for Service Provider > Training and HowTo Documents > Administrator
Please notice: The FAQ will be updated from time to time.
Edited by: Susanne Schlehf on May 4, 2009 2:48 PM
Edited by: Susanne Schlehf on May 18, 2009 12:56 PM

Hello Richard,
(1) regarding network connections see document [Draft:Technical Support Network Connections for VAR Scenario|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000880802009E] as overview and with a lot of detailed information.
(2) yes, you have to setup once all your customer connections at the beginning but then only add/remove with customer contract changes
(3) the workaround by sending by email can handled a anexception. EWA has to be done for productive systems like nowadays done by SAP. Additional EWA services could meas additional business case for a VAR - that's contract between VAR and customer.
(4) whatever you think may be a business to sell - do it ! (and get a monetary bonus from your boss
Kind regards
Heinrich

Solution Manager Enterprise Edition upgrade slow

Hi
I am performing SOMAN 7.0 upgrade to Enterprise edition by upgrading kernel 701 and SP stack 18. I have already upgraded the kernel and java stack and now in the process of upgrading ABAP. I am expereincing really slow performance of this upgrade. I have checked tp and R3trans version which is uptodate as I updated kernel. I cant see any problem with CPU utilization as well swapping. I checked the SLOGs and there are no alerting errors. I see its moving and its very slow. I am just wondering if any of you guys experienced this - is this normal since this is a upgrade?

Thanks a lot, i realize the installation following the standard add-on installation procedure!
Now i have the ST-ETP
ST     400     0024     SAPKITL434     SAP Solution Manager Tool
ST-A/PI     01M_CRM570     0000     -     Application Servicetools for CRM 500 - 7
ST-ETP     100     0000     -     SAP Solution Manager Enterprise Edition
ST-ICO     150_700     0025     SAPK-1507PINSTPL     SAP Solution Manager Implementation Cont
ST-LV     100     0001     SAPK-10001INSTLV     SAP Landscape Verification Wizard
ST-SER     701_2010_1     0002     SAPKITLOS2     SAP Solution Manager Service Tools
Then don't forget to perform step 5. After the installation steps.
Step 5 says this:
5. After the installation
              To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
            a) In the case of ST-400 SP15-SP17
            To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
            b) In the case of ST-400 SP18 or higher
            The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
In my spro i don't have this options->
I see the route Activate Solution Manager Enhacements in SPRO -> Cross Scenario Settings
And in enterprise extension I only see ( SM_CRON, SM_QC_AD, SM_SSP,SM_SUPP_VAR)
I guess that this in SP24 is done automatically, but you said, that don´t forget the step 5 after installation.
update:I check for updates of SP and this add-on don´t have SP for now

Solution Manager Enterprise Edition - Creating Service Desk

Hi All...
Being a Channel Partner of SAP we have authority to sell sap licenses to our customers.
Now we want to setup a service desk for them in our Solution ManagerEE.
Could you please help me to understand....
1> I am not able to understand the extra functionality of SolMan EE with respect to Service Desk creation.
     Do we really required EE for Service Desk? or with just normal SolMan we can setup that?
     2nd is...
2> I am not able to understand how do I can create system in SMSY, because possibility of having same SID for any of our customers.
     I am not sure how do I can setup a Service Desk for each customers separately.
     If any one of you guys have did same kinda config. before, please guide me....
Thanks!
Amit
Edited by: amit bhisekar on Oct 28, 2008 7:12 AM

> 1> I am not able to understand the extra functionality of SolMan EE with respect to Service Desk creation.
>      Do we really required EE for Service Desk? or with just normal SolMan we can setup that?
SolMan EE has some additional functionality but that is not related to the service desk. A "normal" solMan is enough.
> 2> I am not able to understand how do I can create system in SMSY, because possibility of having same SID for any of our customers.
You can use SIDs like "SID_A" and "SID_B".
>      I am not sure how do I can setup a Service Desk for each customers separately.
Follow the IMG - and note 1023598 - SAP Solution Manager Service Desk for service providers
Additional info:
Out of my experience with the service desk: We are using it since SolMan 2.2 and if we could choose again we would definitely use a different product because
- as soon as you drift away a little bit from the standard configuration, that you can use by default (but often needs adaption) it becomes really complex. Support desk is based on CRM so make sure that you have CRM knowledge (including PPF) in house if you want to do the configuration alone
- after each service pack/support stack installation something is not working and almost each time we need help of the support (OSS/CSS) to get things fixed again
- Bidirectional communication is not possible, you can send answers/inquiries to the message creator but answers are not "automatically" put back into the system (e. g. Mail parsing). That is the biggest drawback
- The UI (if you use the GUI) is.. well... not really intuitive
Markus

Solution Manager upgrade to enterprise Edition

Dear All,
We are running Solution Manager 4.0 in Win2k3 32 bit server
with Oracle 10.2.0.2 Non Unicode version and ST patch level 11.
The memory of the server is recently increased from 4GB to 12GB.
We do not have any Java Stack.
We have configured EWA / System monitoring in our Solman and
also we have huge (really large) no. of documents uploaded into it.
We want to upgrade our Solman to Solution Manager Enterprise edition.
Can this upgrade from NUC to UC is possible with 32 bit OS platform
or we need to change our OS to 64 bit? If we change our OS to 64 bit,
will it have any impact on our existing application?
Also, is it possible to migrate the system as it is to a HPUX 11.31 box
without loosing any documents?
Kindly provide your views.
Thanks & Regards
Sudip

I strongly recomment to go for 64 bit in any case, 32 Bit is history...
For the migration to 64 bti you need to perform a homogenious system copy (Windows 32 Bit / Windows 64 Bit), if your target platform is HP-UX, then you need to perform a heterogenious system copy, which is more complex. Documents will not be lost during systemcopy operations.
regards
Peter

Solution Manager enterprise edition.

Hi, all, How can I check if my version of solution manager is stardart or enterprise edition.
I need that information because in one of the presentation slides of the enterprise service "SAP Modification Justification Check"-
The prerrequisites are.
"Sap Solution Manager Enterprise Edition Must be available". Scope and Architecture of bussiness processes must be documented according to the Minimum Documentation standard.
The solution manager enterprise edition have any special component in system -> status??? or how can i check if i have the enterprise edition of SOLMAN..
Thanks.

Thanks a lot, i realize the installation following the standard add-on installation procedure!
Now i have the ST-ETP
ST     400     0024     SAPKITL434     SAP Solution Manager Tool
ST-A/PI     01M_CRM570     0000     -     Application Servicetools for CRM 500 - 7
ST-ETP     100     0000     -     SAP Solution Manager Enterprise Edition
ST-ICO     150_700     0025     SAPK-1507PINSTPL     SAP Solution Manager Implementation Cont
ST-LV     100     0001     SAPK-10001INSTLV     SAP Landscape Verification Wizard
ST-SER     701_2010_1     0002     SAPKITLOS2     SAP Solution Manager Service Tools
Then don't forget to perform step 5. After the installation steps.
Step 5 says this:
5. After the installation
              To activate SAP Solution Manager Enterprise Edition, the Enterprise Addon SM_APPLM has to be activated in the IMG of the Solution Manager System. This is done via IMG activity SAP Solution Manager->Configuration->Scenario-Specific Settings->Activate Solution Manager Enhancements.
            a) In the case of ST-400 SP15-SP17
            To use Extended Tracebility in Change Request Management activate BC-Set SOLMAN40_CHARM_CONTEXT_001 in transaction SCPR20
            b) In the case of ST-400 SP18 or higher
            The activation of BC-Set SOLMAN40_CHARM_CONTEXT_001 will be done automatically.
In my spro i don't have this options->
I see the route Activate Solution Manager Enhacements in SPRO -> Cross Scenario Settings
And in enterprise extension I only see ( SM_CRON, SM_QC_AD, SM_SSP,SM_SUPP_VAR)
I guess that this in SP24 is done automatically, but you said, that don´t forget the step 5 after installation.
update:I check for updates of SP and this add-on don´t have SP for now

Solution Manager 7.1 solution can not be edited

Hi Guru!
I have a problem about basic configuration of a solution manager 7.1 sp10, in the "specify solution" task i can't edited the logical component.
do you have any idea for editing the field?
Thanks

Hello Sunil,
"Solution SAP Solution already exists and cannot be modified" means that the SAP Solution is already there in your solman system. go to tcode solman_directory and you will see the list of all solution present. if you click on solution node, you will be able to see the logical component assigned to this solution.
If you want to delete this solution, then first you have to remove the logical component from solution
Regards,
suhel

Difference between Solution Manager and Enterprise Edition

Hi all,
Please can someone help define the key differences between the standard Solution Manager and the Enterprise Edition?
I have done my research but can only find the usual marketing material and benefits from SAP. Ideally, the key functionality and main benefits of Enterprise Edition would be appreciated.
Regards,
-Rohan

Hi, enterprise edition is the Solution manager with EHP1 or SOLMAN in SPS 18, we did the upgrade already and some SAP specialists came to do some initial configurations.
More workcenters are the key functionality in this version altough this was released in earlier SPS's, to be sincere with you, SAP specialists that came for the service told us that this new version is oriented to workcenters and some improvements but he did not know all the new functionalities besides workceneters.
Workcenters are a nice way of working and keeping the whole landscape at sight as far as my short experience.

EHP2 for Solution Manager Enterprise Edition

Hi
Can anyone please list the main features delivered by EHP2 for Solution Manager Enterprise Edition or point me to where I can find these? And if you only have one Solution Manager system for your landscape can someone confirm if EHP2 will be activated automatically? Will any new functionality still be delivered in the support packs in between the enhancement packages?
Many thanks in advance
Peter

>
Peter O'Leary wrote:
> Can anyone please list the main features delivered by EHP2 for Solution Manager Enterprise Edition or point me to where I can find these? And if you only have one Solution Manager system for your landscape can someone confirm if EHP2 will be activated automatically? Will any new functionality still be delivered in the support packs in between the enhancement packages?
Hi Peter,
Availability dates for a potential EhP2 for SolMan are not yet communicated.
Activation would be similar to update to EhP1. It's not automatically.
Best regards,
Ruediger

How to edit the URL in the mail that is triggered from Solution Manager 7.1 ?

Hi,
When we perform an action "To Be Approved" for an RFC (Request For Change) in Solution Manager, a mail will be triggered to the respective Change Manager. In that mail, a link will be there which will guide the Change Manager to the SAP Logon Pad.
The problem is, the link in that mail is not pointing towards the required system. It is taking the change manager to Development system instead of Production System.
Can you please help me, how to change this URL link in that e-mail that is being triggered when the action is performed. I just need to remove the Development system URL and paste the Production system URL.
Thanks in advance,
Bharath.

Hi Bharath,
Please check below Blog and KBA:
Incident Management and Change Request Management: E-Mail functionality
in SAP Solution Manager 7.1
http://scn.sap.com/docs/DOC-35291
1831361 - Solution Manager - Changing status in CRM_UI gives BSP error
Exception Class - CX_SY_DYN_CALL_PARAM_MISSING
Thanks
Vikram

Cant load Solutions manager 3.2

I am trying to install ECC 6.0 IDES to my desktop and need to get a solution manager key using solution manager 3.2. wanting to know the location of a software package by looking for a Label.ASC ORACLE:AKK:6.40: Kernel:*386. . I am installing this on a windows based OS using oracle that i have already installed. does anyone know where this software package resides?

Are you looking for Solution Manager Key or the Label file ASC ORACLE:AKK:6.40: Kernel:*386 . For solution Manager key , please check the link
http://help.sap.com/saphelp_sm32/helpdata/en/b3/023a4227deb16be10000000a155106/content.htm
Thanks
Prince Jose

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Question for installing Solution Manager & ECC 5.0

Any idea for installing Solution Manager 3.2 on Windows server 2003 with Oracle9i problem when install Database Instance. Installation failed when the intallation progress went to Oracle Post-Load Action.
The message from startsap log file is
"running C:\usr\sap\T01\SYS\exe\run/sapstart.exe name=T01 nr=03 SAPDIAHOST=saptest02 -Wait
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
CreateNamedPipe for
saptest02\pipe\SAP01_03 Failed, Extended Error #2
start service SAP01_03 on machine
saptest02
OpenService of SAPT01_03 failed. Error#: 1060
C:\usr\sap\T01\SYS\exe\run/sapstart.exe=>sapparam(1c): No Profile Used."
Another question is about installing the Oracle database software: should we choose Create Databse or not when install Oracle Server Software only?
Is my installation process as following correct?
->SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
install Oracle9i Client 9.2.0.1.0->Administrator
Thanks a lot

Hi Shusen, I´m trying to do the same think (Install ECC IDES with Oracle 9i in one computer for educational propose), can you help me with this:
1.I made the same Oracle install process because when I tried with sapserver.cmd nothing happened, for that reason i made:
SELECT A PRODUCT TO INSTALL:
Oracle9i Database 9.2.0.1.0
->WHAT TPYE OF INSTALLATION DO YOU WANT:
Enterprise Edition
->SELECT A DATABASE SUITED TO YOUR NEEDS:
Software only
After end of installation
I did not install client, is this correct?
2.After install this, I run the sapins.exe but show me this error: INSTALL FIRST SAP J2EE ENGINE, I download the JAVA SDK from JAVA page (java_ee_sdk-5-windows) but did not fix the problem: Do you know what file is this? Or, where is it in the DVD installation?
Thanks in advance if you or somebody can help me and excuse me if the answers are obviously, but I´m not a system engineer I´m only try to install IDES for learn SAP WM.
Thanks.

Oracle upgrade in Solution Manager 10g to 11g

Dear Expert team ,
Our Solution Manager is running in Windows 2003 with oracle 10g .
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Prod
PL/SQL Release 10.2.0.2.0 - Production
CORE 10.2.0.2.0 Production
TNS for 32-bit Windows: Version 10.2.0.2.0 - Production
NLSRTL Version 10.2.0.2.0 - Production
SQL>
Now I want to upgrade my Solution Manager 10 g to 11g .
what oracle component should I download and how to upgrade 10.2.0.2.0 to 11.2.0.3.0.
Please suggest.
Regards
Pooja

Hi
The upgrade is possible as stated in the here under note.
Previous version (v15) of that note was even a bit more clear it is possible but version 10.2.0.4 is preferred.
Direct upgrade from 10.2.0.2 should not be a problem, as it is even possible to have a direct upgrade from 9.2.0.8 to 11.2.0.4.
1431793 - Oracle 11.2.0: Upgrade Scripts
A database < 9.2.0.8 must be upgraded to 9.2.0.8 before it can be upgraded directly to 11.2.0.4.
You should consider jumping directly to 11.2.0.4 that is the latest 11g version and the only one that will have a long term support.
Regards
1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade
For a database upgrade from 10.2. to 11.2 the minimum release is 10.2.0.2. This release is not supported any more.
1431797 - Oracle 11.2.0: Troubleshooting the Database Upgrade v15
We strongly recommend a minimum release 10.2.0.4 for the following reasons:
a) All SAP internal database upgrade tests have been performed with
release 10.2.0.4. This upgrade path has been very well tested and
is documented in the SAP Database Upgrade Guide for Oracle Release
11.2.
b) Oracle Database Release 10.2.0.2 is not supported any more.

Error while installing solution manager 7.1

Hi All,
I am installing SAP Solution Manager 7.1 SR1 i am facing below issue ,any one please suggest me how to proceed further.I am new to sybase .
An error occurred while processing option SAP Solution Manager 7.1 Support Release 1 > SAP Systems > SAP ASE > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now:
Choose Retry to repeat the current step.
Choose Log Files to get more information about the error.
Stop the option and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS.
import_monitor.java log:
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.016)
SAP Java Server VM (build 4.1.016 1.6-b03, Dec 31 2011 00:41:53 - 41_REL - optU - windows amd64 - 6 - bas2:164914 (mixed mode))
Import Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29.
import_monitor Log:
INFO: 2014-07-01 10:49:48
Import Monitor is started.
CONFIG: 2014-07-01 10:49:48
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 10:49:48
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 10:49:48
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 10:49:48
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 10:49:48
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 10:49:48 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 10:49:59 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 10:50:18
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 10:50:18
1 error(s) during processing of packages.
INFO: 2014-07-01 10:50:18
Import Monitor is stopped.
INFO: 2014-07-01 11:09:16
Import Monitor is started.
CONFIG: 2014-07-01 11:09:16
Application options:
dbCodepage=4103
dbType=SYB
extFiles=no
importDirs=D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP2;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP3;D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4
installDir=C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS
jobNum=8
loadArgs=-c 99000000 -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2014-07-01 11:09:16
List of packages with table structure: 'SAP0000'.
CONFIG: 2014-07-01 11:09:16
List of packages with views: 'SAPVIEW'.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is started.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2014-07-01 11:09:16
Data codepage 1100 is determined using TOC file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_1\DATA_UNITS\EXP1\DATA\SAPSSEXC.TOC' for package 'SAPSSEXC'.
INFO: 2014-07-01 11:09:16
Version table 'SVERS' is found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadThreadDispatcher loadPackage_report
Monitor jobs: running 1, waiting 28, completed 0, failed 0, total 29 Package Group max threads: 1 current running threads : 0 processing package: SAPNTAB
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2014-07-01 11:09:16 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
INFO: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run_report
Monitor jobs: running 0, waiting 28, completed 0, failed 1, total 29 error processing of package SAPNTAB
ERROR: 2014-07-01 11:09:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is interrupted with R3load error.
Process 'D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast' exited with return code 2.
For mode details see 'SAPNTAB.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-01 11:09:46
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2014-07-01 11:09:46
1 error(s) during processing of packages.
INFO: 2014-07-01 11:09:46
Import Monitor is stopped.
NOTE:
The same issue has been solved in SCN Thread http://scn.sap.com/thread/3360385. As suggested in that note i am trying to look into the sap note
Note 1716201 - SYB:Update control.xml files for installation: Sybase ASE
in service market place but it is displaying as Document not released.
Kindly can any one help me in provind the above mentioned note or help me how to resolve this issue.
Regards,
SURYA.

HI Divyanshu,
Below is the SAPNTAB.log:
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1680
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -ctf I D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DATA\SAPNTAB.STR C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\DDLSYB.TPL SAPNTAB.TSK SYB -l SAPNTAB.log
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job completed
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140630211543
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 1904
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) INFO: SVERS created
(IMP) INFO: import of SVERS completed (1 rows) #20140630211544
(DB) INFO: SVERS~0 created
(DB) INFO: DDNTF created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF~0 created
(DB) INFO: DDNTF_CONV_UC created
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC~0 created
(DB) INFO: DDNTT created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC created
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140630211555
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701104948
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2304
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701104959
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701110916
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2056
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701110927
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140701120231
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Dec 2 2011 03:21:30
patchinfo (patches.h): (0.113) NewDB R3load better support (note 1564286)
process id 2288
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -c 99000000 -loadprocedure fast
(DB) INFO: connected to DB
(DB) INFO: DDNTF deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTF_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "DDNTF_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: DDNTT deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file SDIC.SQL
(SQL) INFO: SDIC.SQL not found
(SQL) INFO: Searching for SQL file D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL
(SQL) INFO: D:\SAP_DOWNLOADS\INSTALLATION_EXPORTS\EXTRACTED\51042607_2\DATA_UNITS\EXP4\DB/SYB/SDIC.SQL not found
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT"."DDNTT~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT.DDNTT~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT~0" ON "DDNTT" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: DDNTT_CONV_UC deleted/truncated
(SYB_IMP) ERROR: DbSlEndModify failed
rc = 99, table "DDNTT_CONV_UC"
(SQL error 30128)
error message returned by DbSl:
[ASE Error SQL30128:HY000][SAP][ASE ODBC Driver]Data overflow. Increase specified column size or buffer size
(IMP) ERROR: EndFastload: rc = 2
(DB) ERROR: DDL statement failed
(DROP INDEX "DDNTT_CONV_UC"."DDNTT_CONV_UC~0")
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
[ASE Error SQL3701][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Cannot drop the index 'DDNTT_CONV_UC.DDNTT_CONV_UC~0', because it doesn't exist in the system catalogs.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "DDNTT_CONV_UC~0" ON "DDNTT_CONV_UC" ( "TABNAME" ) )
DbSlExecute: rc = 99
(SQL error 1505)
error message returned by DbSl:
[ASE Error SQL1505][SAP][ASE ODBC Driver][Adaptive Server Enterprise]Create unique index aborted on duplicate key. Primary key is '""'
(DB) INFO: disconnected from DB
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 6 error(s)
D:\usr\sap\MSM\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140701120242

Cant edit my solution in Solution Manager 7.1

Similar Messages

Maybe you are looking for