Ehp1:Solution Manager:Stuck at ddic activation

Hello All,
While upgrading the Solution Manager to Ehp1, import stuck at phase DDIC_ACTIVATION, reason for error is TP_STEP_FAILURE, the return code is 0012 and the error message: OCS Package ******** , tp step A, return code 0012.
I can see in the log of the import queue that the job RDDMASGL was terminated and I found the entry "ABAP / 4 processor: EXSORT_NOT_ENOUGH_MEMORY" in the log of that job.
My system is a 32 bit Windows operation system with 3GB physical Ram.
I have the following doubt
1.) If i keep on re-runing again will the already activated program will be skip or will be re-activated.
2.)How can i resolve this error.
Regards
Anthony

Hi
If i keep on re-runing again will the already activated program will be skip or will be re-activated.
It will be skiped and will proceed with rest of the object
How can i resolve this error.
You need to check import logs for better analysis
Rerun the import and see how the things go
Regards
Uday

Similar Messages

EP 7 systems in Solution Manager 7 for EWA activation

Dear Expert,
Greetings from Partha.
I need to include our EP 7 systems in Solution Manager 7 for EWA activation. Current lanscape scenario
Solution Manger 7.00 Installed
EP 7.00 Installed
No central SLD configured and all the system have local SLD.
1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
Help will be appreciated.
Regards,
Partha

1. As per the installtion guide & SAP notes we need to install
a> SM Diagnostics Agent & Wilo Introscope in Solution Manager (manging system).
b> Diagnostics Agent in every manged system(s).
For managing system we can download Diagnostics Agent installation DVDs from SAP Service Marketplace
at: http://service.sap.com/swdc --> Download --> SAP Support Packages --> Entry by Application Group
--> SAP Technology Components --> SAP SOLUTION MANAGER --> SAP SOLUTION MANAGER 7.0
--> Entry by Component --> Agents for Managed systems --> DIAGNOSTICS AGENT 7.11
--> <choose operating system of managed>
Our Solution Manager 7 is already installed and @SPS 17. My question is
1. Can we use the same file for SMD installtion in Solution Manger or we need to download it from some other area ?
If it is different then kindly let me know what are the DVDs to be downloaded and from where?
Check the pdf attached in note 1234387 - Inst. 7.1 EhP1 - Diagnostics Agent installation
If you have SP17, you must follow note 1357812 and install Diagnostics Agent 7.01 SR1
2. In our Managed System SMD installtion we have decided for
--> Installation Strategy as Direct Solution Manager Registration
But what strategy we should take for SMD installation on Sol Man 7 that is
Local SLD (wrt Sol Man) Registration or Direct Solution Manager Registration
It doesn't matter what strategy you'll decide. You could decide Direct Solution Manager registration
3. What is the need for the SAP Host Agent Installattion ? Is it mandatory ?
As you have solution Manager SP17, you can't install Saphostagent 7.11 and for this reason you can't use SAphostagent.
Agent 7.01 => No Saphostagent
Agent 7.11 => Must install saphostagent
Agent 7.20 => Already have SAPhostagent installed

EHP1 Solution Manager EHP5

Hi people,
I´m interested on to install the EHP5 for ERP6.0, but I´ve found the next doubt while I was reading the guides and notes. It´s mandatory to have the EHP1 for the solution manager for to generate the xml for the EHP5?
Could be a way to install the EHP5 without the EHP1 for the solution manager?
More thanks

Ruben Torres wrote:
Hi people,
>
> I´m interested on to install the EHP5 for ERP6.0, but I´ve found the next doubt while I was reading the guides and notes. It´s mandatory to have the EHP1 for the solution manager for to generate the xml for the EHP5?
>
> Could be a way to install the EHP5 without the EHP1 for the solution manager?
>
>
> More thanks
Hello,
As already mentioned by Joas, Solution manager should be with EhP1 and with certain SP level as well.
However, I would like to clear the air a bit.
We can install ECC 6 EhP5 without 'XML' as well. The installation will be 'ECC 6 EhP5 Ready' with 'Central Application' component. Rest of the business component will not be 'EhP5'. This is where then you have to upgrade this 'Ehp5 Ready' system to 'EhP5' for all the business components. In other words, Solution manager should be EhP1 SPSx to upgrade this ehp5 ready system and to generate proper XML file for this upgrade. Core ehp5 ready installation can be done without ehp1 in solman however, but not much 'Usable'.
So, better to keep solution manager updated before we go ahead to install and use ECC 6 EhP5 ! For further knowledge, please go through the installation guides once more.
Thanks

Support pack SAPKB70014 stuck at ddic activation

Hi!
While upgrading Support Pack SAPKB70014, import stuck at phase DDIC_ACTIVATION, reason for error is TP_STEP_FAILURE, the return code is 0012 and the error message: OCS Package SAPKB70014, tp step A, return code 0012.
I can see in the log of the import queue that the job RDDMASGL was terminated and I found the entry "ABAP / 4 processor: EXSORT_NOT_ENOUGH_MEMORY" in the log of that job.
In SAP memory analysis (transaction st02) I can see that maximal 285 MB heap memory were used while 2 GB are possible. During installation of the support pack always 8 GB of physical memory were free in the OS. The SAP system is running under Windows 2003 R2 Enterprise Edition SP2 with 12 GB of physical memory.
What's the reason for this and what can I do?
Thanks in advance!
Nico Wallmeier

Hi
Please help
I am new in Basis my system has 4GB Ram running windows system 32. To what value should I set my memory parameters.

SAINT stuck at DDIC activation phase

Hi All
I am doing Virsa Add on installation on CRM production environment.
There were no issues when i did it in development and quality servers
But in production the Saint update hangs in DDIC_Actiation stage.
It does not give any error but goes in an endless loop.
The TP seems to have some issue...but the RDDIMPDP job is running ok
I am not able to get the issue
Plz help
Thanks and regards
Tushar

Hi Tushar,
Please check SLOG and ALOG at OS level.
Also provide the :-
1. Import logs for the queue
2. Action log for the Queue.
3. Tp system log
Regards
Pranay

Solution Manager - Logical Component for SAP Netweaver EHP2

Hello,
I installed the newest SAP Netweaver Ehp2 (with usage type AS ABAP only) for a future integrating with BI_CONT (SAP BI requirement). So... what I want to know is... I want to do an update of support packages to the latest Stack (SPS) and in this product version (NW EHP2) the latest stack is stack 06 !! But I ´m facing with a problem which is, because I have to maintain this system in Solution Manager (for Maintenance Optimizer activity)...so what I want is configure this new system on Solution Manager Ehp1 (with SPS 23) but in tcode SMSY I didn´t found this Product in Logical Components for I can apply this system to my Solution... I only see SAP Netweaver with EHP1 and not with EHP2 which is the version that I want to apply this new system. (This is mandatory task, because without it, I will not be able to download the support packages for NW 7.0 EHP2)
Tell me two things... first if this level version of Solution Manager that I have here (SPS 23) have this product in logical components, and two... if not it, is necessary to raise the level of Solution Manager support packages (to latest stack SPS 25) for I can see that logical component SAP Netweaver EHP2?!
Thank you very much
João Dimas - Portugal

Hi João,
You can verify if the EHP2 is available (if) in your system, this can be done once you are in SMSY -> Product Definitions -> SAP Netweaver where you should able to see the EHP2. If so, then it's a matter of marking the leading Product & Product Version under the Header Data ->Change Product Assignment where you can use the drop down arrow to select the Product and Product Version. If it's not available, then by checking the 'Free Product / Select Product Version' then use the drop down arrow to select the product & Product Version, once you selected that then click on copy and mark that as active and save.
Then you need to create a new logical component in System Group & logical Component under SAP Netweaver, then assign the system to the logical component. Once this is done you can use the logical component in a solution and create a maintenance transaction.
I hope this help you to proceed further, thanks.
Jay Soma.

Monitoring a non-SAP satellite system in Solution Manager

Hi Folks,
I have two quick questions.
1.) What is the proper procedure/tool for monitoring a non-NW system in Solution Manager? Should I be able to use sapccmsr and saposcol on these systems?
2.) What is the proper way to connect a non-NW system to the SLD? Should I be able to use saposol and sldreg for these?
Background:
- My Solution Manager system is a NW70 EHP1
- Solution Manager Diagnostics is installed and monitoring my ABAP and Java systems
- I have my CCMS agents registered back to my CEN for the ABAP and Java systems
Satellite systems:
- Multiple Wintel servers (both IA32 and x64) that are running;
o standalone SQL server databases
o BOE/BOBJ
o BPC for Microsoft
Section 4.8 of the Monitoring Setup Guide (CEN SAP Netweaver 7.0 SPS18) states that I should be able to monitor a standalone database.
My confusion isu2026 in the absence of an SAP filesystem (kernel) and the standard SAP environment variables that get set during an install, how do I register the agents? The executables do not want to launch.
Thank you,
Bill

Dear William,
Monitoring of NON-SAP systems is not actually done on the solution manager system itself. The solution manager system gets its feed of alert information from the satellite, specifically CCMS. For SAP systems, alerts from CCMS are set up and activated by default. For Third-Party systems you have to be ablke to set up the interface to feed monitoring information from your non-SAP software to SAP's CCMS infrastructure.
You can get more information on CCMS agents via the website at http://service.sap.com/monitoring.
Go to "system Monitoring and Alert Management" > "Monitoring in Detail".
I hope this information is helpful.
Regards,
Paul

Install Solution Manager in RedHat Enterprise 6 with Oracle 11

Hello ,
In the marketplace-PAM, RedHat Enterprise 6 is not listed as approved for EHP1 Solution Manager 7.0 64 bit (unicode) with Oracle.
Does anyone have any information on this subject?
Has anyone installed the Solution Manager 7.0/Oracle with RedHat Enterprise 6?
tks

Yes, you are correct. Apart from PAM, following Note confirms this. RHEL 6 is not supported yet for Oracle, is in planning stage.
Note 1565179 - SAP software and Oracle Linux
Thanks

SAP Solution Manager Adapter for SAP Quality Center by HP (ST-QCA)

Hello Folks,
I am configuring Solution Manager, and the current activity asks to download to add-ons that I can't find in the Marketplace - they are required to activate Solution Manager Enhancements:
SAP Solution Manager Adapter for SAP Quality Center by HP (software component: ST-QCA)
SAP Support Enablement package (software component: ST-SEP)
Does anyone know where to get those components?
Thanks a lot,
Marco

Hi Ravindra babu/ Murali:
I have one very quick doubt and would be really glad if you can help clarify.
As per documentation from SAP and also IMG screens etc. it seems like 'a project' in SolMan will hand-shake with 'a project' in QC.
Can I therefore assume that if there is only one instance of SolMan (productive) and one QC server alone (again, productive), any number of trials I carry out between SolMan project and QC project will not spill over into other projects in these two systems and thus have no impact whatsoever at server level.
The reason for my asking this - in my project, Testing has started using QC in a standalone mode already. We have just one server. If I have to carry out any tests/ demo between SolMan and QC, it shouldn't impact other 'standalone' projects being done in QC.
Regards,
Srini

DDIC Password fails in middle of Solution Manager Installation

I'm performing a new install of Solution Manager 7.0 (4.0) on HPUX IA64 11.23. This is a brand new Landscape. The installation has halted at phase 29/47 "Check DDIC password", and reports the error:
Test login to SAP System SMA failed.
SOLUTION: Make sure that the system is started, that the user DDIC exists and that the password of user DDIC is correct.
From the SAPGUI 7.10., I was unable to login as DDIC or SAP. I used the master passwords given in the install. I also tried the default passwords as mention in another thread password '19920706' for DDIC and '06071992' for SAP.
I was able to login with SAP* password PASS after adding login/no_automatic_user_sapstar=0
to the default profile and restarting SAP, but was unable to change the DDIC password because change and transport system not configured.
How do I get past this point in the installation process?

This problem is now resolved. The problems of:
1) The "Check DDIC password" phase of sapinst of SM 7.0 was failing with DB-Error 0.
Fix: Install latest kernel patch. Problem was fixed with NW 7.0 kernel patch 133. I installed kernel patch 159. The kernel patch had to be installed via the old method of using SAPCAR to untar the files, backup kernel dir, shutdown sap, and copy files over to kernel dir. See note 19466.
2) The Warning messages
WARNING => IcmJ2EEScheduleFunc: Cannot
access "/sap/public/icman" -
please check node in TA sicf [icxxman_mt.c 2206]
was resolved by TA SICF by SERVICE HOST -> active
to activate the complete default_host subtree.

System Monitoring with Solution Manager Ehp1

Hi,
I'm Tomas Piqueres, and I'm working in a VAR SAP with Solution Manager.
Recently, we installed Solution Manager Ehp1 and we are trying to configure it for System Monitoring. When I worked with Solution Manager SP17 I used to go to transaction RZ21 to add the system I wanted to monitoring and then put the SID and RFCs of the system.
Now with Solution Manager Ehp1, when I create the system in transaction RZ21, first I have to set the Component Type to Be Monitored and then the SID, Message Server Logon Group, the client and user are set automatically, and the password I've set to user CSMREG.
when I fill all the entries, I can see the RFCs used for the monitoring of the system. Those RFCs are set automatically:
<SID>_RZ20_COLLECT
<SID>_RZ20_ANALYZE
I can't edit those RFCs, so I have to create it manually. I check that RFCs destination works fine and both pass the authorization test, so when I try to save the system at transaction RZ21, I see the following errors:
<SID>_RZ20_COLLECT_123539Error when opening an RFC connection
Error during remote call of SAL_MS_GET_LOCAL_MS_INFO function: Error when opening an RFC connection
Error during remote call of SALC function: Error when opening an RFC connection
Error during remote call of RFC1 function: Error when opening an RFC connection
I've been looking for information about those errors and how to monitoring with Solution Manager Ehp1, but I haven't found anything usefull.
Please, Could you help me?
Thanks and regards,
Tomas.

Tomas,
I need to configure EWA from my Solman system and I completed the steps (defining and creation of RFC destinations to the target systems from my Solman system). I downloaded the lates ccmsagent file from the market place based my target system configurations.
Herewith attaching the logs while I'm trying to check the profile parameter.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sappfpar check pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
==   Checking profile:     /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
================================================================================
***WARNING: Unexpected parameter: DIR_EPS =/usr/sap/trans/EPS/----
***WARNING: Unexpected parameter: SAPSECULIB =/usr/sap/TQA/SYS/exe/run/libsapsecu.o
***WARNING: Unexpected parameter: abap/buffersize_part1 =1200000
***WARNING: Unexpected parameter: auth/auth_number_in_userbuffer =5000
***WARNING: Unexpected parameter: dbs/io_buf_size =100000
***WARNING: Unexpected parameter: rsau/local/file =/usr/sap/TQA/DVEBMGS30/log/audit/audit_++++++++
***WARNING: Unexpected parameter: rsau/selector1/class =35
***WARNING: Unexpected parameter: rsau/selector1/severity =2
***WARNING: Unexpected parameter: rsdb/rclu/cachelimt =0
***ERROR: Size of shared memory pool 40 too small
================================================================
SOLUTIONS: (1) Locate shared memory segments outside of pool 40
               with parameters like: ipc/shm_psize_<key> =0
SOLUTION: Increase size of shared memory pool 40
          with parameter: ipc/shm_psize_40 =1472000000
Shared memory disposition overview
================================================================
Shared memory pools
Key:   10 Pool
            Size configured.....:   642000000 ( 612.3 MB)
            Size min. estimated.:   637597428 ( 608.1 MB)
            Advised Size........:   640000000 ( 610.4 MB)
Key:   40 Pool for database buffers
            Size configured.....: 1048000000 ( 999.4 MB)
            Size min. estimated.: 1468229308 (1400.2 MB)
            Advised Size........: 1472000000 (1403.8 MB)
Shared memories inside of pool 10
Key:        1 Size:        2500 (   0.0 MB) System administration
Key:        4 Size:      523648 (   0.5 MB) statistic area
Key:        7 Size:       14838 (   0.0 MB) Update task administration
Key:        8 Size:    67108964 ( 64.0 MB) Paging buffer
Key:        9 Size:   134217828 ( 128.0 MB) Roll buffer
Key:       11 Size:      500000 (   0.5 MB) Factory calender buffer
Key:       12 Size:     6000000 (   5.7 MB) TemSe Char-Code convert Buf.
Key:       13 Size:   200500000 ( 191.2 MB) Alert Area
Key:       16 Size:       22400 (   0.0 MB) Semaphore activity monitoring
Key:       17 Size:     2672386 (   2.5 MB) Roll administration
Key:       30 Size:       37888 (   0.0 MB) Taskhandler runtime admin.
Key:       31 Size:     4806000 (   4.6 MB) Dispatcher request queue
Key:       33 Size:    39936000 ( 38.1 MB) Table buffer, part.buffering
Key:       34 Size:    20480000 ( 19.5 MB) Enqueue table
Key:       51 Size:     3200000 (   3.1 MB) Extended memory admin.
Key:       52 Size:       40000 (   0.0 MB) Message Server buffer
Key:       54 Size:    20488192 ( 19.5 MB) Export/Import buffer
Key:       55 Size:        8192 (   0.0 MB) Spool local printer+joblist
Key:       57 Size:     1048576 (   1.0 MB) Profilparameter in shared mem
Key:       58 Size:        4096 (   0.0 MB) Enqueue ID for reset
Key:       62 Size:    85983232 ( 82.0 MB) Memory pipes
Shared memories inside of pool 40
Key:        2 Size:    31168040 ( 29.7 MB) Disp. administration tables
Key:        3 Size:   114048000 ( 108.8 MB) Disp. communication areas
Key:        6 Size: 1064960000 (1015.6 MB) ABAP program buffer
Key:       14 Size:    28600000 ( 27.3 MB) Presentation buffer
Key:       19 Size:    90000000 ( 85.8 MB) Table-buffer
Key:       42 Size:    13920992 ( 13.3 MB) DB TTAB buffer
Key:       43 Size:    43422392 ( 41.4 MB) DB FTAB buffer
Key:       44 Size:     8606392 (   8.2 MB) DB IREC buffer
Key:       45 Size:     6558392 (   6.3 MB) DB short nametab buffer
Key:       46 Size:       20480 (   0.0 MB) DB sync table
Key:       47 Size:    13313024 ( 12.7 MB) DB CUA buffer
Key:       48 Size:      300000 (   0.3 MB) Number range buffer
Key:       49 Size:     3309932 (   3.2 MB) Spool admin (SpoolWP+DiaWP)
Shared memories outside of pools
Key:       18 Size:     1792100 (   1.7 MB) Paging adminitration
Key:       41 Size:    25010000 ( 23.9 MB) DB statistics buffer
Key:       63 Size:      409600 (   0.4 MB) ICMAN shared memory
Key:       64 Size:     4202496 (   4.0 MB) Online Text Repository Buf.
Key:       65 Size:     4202496 (   4.0 MB) Export/Import Shared Memory
Key:     1002 Size:      400000 (   0.4 MB) Performance monitoring V01.0
Key: 58900130 Size:        4096 (   0.0 MB) SCSA area
Nr of operating system shared memory segments: 9
Shared memory resource requirements estimated
================================================================
Nr of shared memory descriptors required for
Extended Memory Management (unnamed mapped file).: 64
Total Nr of shared segments required.....:         73
System-imposed number of shared memories.:       1000
Shared memory segment size required min..: 1472000000 (1403.8 MB)
System-imposed maximum segment size......: 35184372088832 (33554432.0 MB)
Swap space requirements estimated
================================================
Shared memory....................: 2050.4 MB
..in pool 10 608.1 MB,   99% used
..in pool 40 999.4 MB, 140% used !!
..not in pool:   34.4 MB
Processes........................: 716.8 MB
Extended Memory .................: 8192.0 MB
Total, minimum requirement.......: 10959.2 MB
Process local heaps, worst case..: 1907.3 MB
Total, worst case requirement....: 12866.5 MB
Errors detected..................:    1
Warnings detected................:    9
After checking the profile parameter I tried to run sapccm4x in /run directory but got the below error and I'm not able tomove further.
Pls have a look at these two and let me know what could I do to proceed further.
tqaadm@saptqa01:/usr/sap/TQA/SYS/exe/run 5> sapccm4x -R pf=/usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO: CCMS agent sapccm4x working directory is /usr/sap/TQA/DVEBMGS30/log/sapccm4x
INFO: CCMS agent sapccm4x config file is /usr/sap/TQA/DVEBMGS30/log/sapccm4x/csmconf
INFO: Central Monitoring System is [SMP]. (found in config file)
      additional CENTRAL system y/[n] ?   :
INFO: found ini file /usr/sap/TQA/DVEBMGS30/log/sapccm4x/sapccmsr.ini.
INFO:
      CCMS version 20040229, 64 bit, multithreaded, Non-Unicode
      compiled at   Jun 28 2010
      systemid      324 (IBM RS/6000 with AIX)
      relno         6400
      patch text    patch collection 2010/1, OSS note 1304480
      patchno       335
INFO Runtime:
      running on    saptqa01 AIX 3 5 00069A8FD600
      running with profile   /usr/sap/TQA/SYS/profile/TQA_DVEBMGS30_saptqa01
INFO profile parameters:
      alert/MONI_SEGM_SIZE = 200000000
      alert/TRACE          = 1
      SAPSYSTEM            = 30
      SAPSYSTEMNAME        = TQA
      SAPLOCALHOST         = saptqa01
      DIR_CCMS             = /usr/sap/ccms
      DIR_LOGGING          = /usr/sap/TQA/DVEBMGS30/log
      DIR_PERF             = /usr/sap/tmp
INFO:
      pid           4165682
INFO: Attached to Shared Memory Key 13 (size 200141728) in pool 10
INFO: Connected to Monitoring Segment [CCMS Monitoring Segment for application server saptqa01_TQA_30, created with version CCMS version 20040229, 64 bit single threaded, compiled at Oct 3 2008, kernel 6400_20020600_254, platform 324 (IBM RS/6000 with AIX)]
        segment status     ENABLED
        segment started at Tue Sep 14 09:35:56 2010
        segment version    20040229
ERROR: Shared Memory misconfiguration ==> can not monitor SAP application server saptqa01_TQA_30
       Dispatcher Admin Shared Memory (Key 01) and CCMS Shared Memory (Key 13) both in pool 10.
       Please change configuration with profile parameters
           ipc/shm_psize_01 = -<different pool nr>
       xor
           ipc/shm_psize_13 = -<different pool nr>
EXITING with code 1

System monitoring configuration in solution manager EHP1

Hi all
I am in a bit of fix
We have upgraded our solution manager devlopment to EHP1
Now I have added one system through SMSY in solution manager to configure system monitoring
I have generated all the RFC's,I have created the logical component and solution and assigned the system to the solution
When I check my solution it is looking fine
Now when I go within solution and click on the tab system monitoring
It shows me on the left hand side -> Set up system monitoring
when I click on Set up system monitoring on the left part of SAP screen,strangely it doesnt take me to the activation of screen monitoring,it just shows me the best practices documents on the right side but nothing more than that
I have checked many guides,blogs and SAP tutors anfd have followed them but strangely I am not been able to go to the screen for activating system monitoring
Are there any activities that need to be done after upgrading to EHP1?
Are there any services to be activated for system monitoring?
Please advice
Rohit

I'm not 100% sure that it is necessary, but it won't hurt.
Perhaps the essential adjustment you need for system monitoring is being done in there.
It won't hurt

Solution Manager Addon Stuck BBPCRM SAPKU50008

Dear Experts,
When I am implementing ADDON BBPCRM SAPKU50008 in Solution Manager .In Queue Import It stuck in "Execution of report after put"
When I check SLOG .It show nothing.
START tp_getprots          SAL R      20101211160827              DDIC         testserver
STOP tp_getprots          SAL R      20101211160943              DDIC         testserver
STOP EXECUTION OF REPORTS SAL R      20101211160943              DDIC         testserver
START EXECUTION OF REPORTS SAL R      20101211161147              DDIC         testserver
START tp_getprots          SAL R      20101211161148              DDIC         testserver
But when I check \usr\sap\trans\log\SAPKU50008
2 EPU122XPost-import method "BEFB_AFTER_IMP" started for "BEFT" "T", date and time: "20101210153150"
A3 E/BEF/GENERATOR 008XGeneration of BE Application "CRMB" (Start Time "15:31:51")
A3WE/BEF/GENERATOR 010 Generation of application "CRMB" (user "DDIC") is already running
1AETR012XProgram terminated (job: "RDDEXECL", no.: "15313100")
1AEPU320 See job log"RDDEXECL""15313100""SAL"
1 ETP162 EXECUTION OF REPORTS AFTER PUT
1 ETP110 end date and time   : "20101211094736"
1 ETP111 exit code           : "12"
1 ETP199 ######################################
Transport is proper configure.
Whats the problem ?

Hello Pooja,
One thing you want to check is based on your SP level that the following notes have been applied on your system:
1172948 SAP Solution Manager: Basic functions (18 & 19)
1334252 SAP Solution Manager: Basic functions: SP20 and SP21
1405878 SAP Solution Manager: Basic functions: SP22 to SP24
1468591 SAP Solution Manager: Basic functions: SP25 and higher
If the relevent note is not already applied to your system, then please do so.
As Tom has already suggested you want to check the Job log for RDDEXECL.
You can do this with transaction code SM37.
Check for lines like:
ABAP/4 processor:...
Which indicates there was a short dump created and the program terminated.
You can look at the dump via ST22. This can be used for a Note search that may address the cause for the dump.
Hope this helps!
Regards,
Paul

SAP EHP1 for Solution Manager 7.0 - Post Install Procedure

Hello Folks:
I completed Sol Manager 7.0 EHP1 installation on Win 2008 R2 with MS SQL in a sandbox environment. This is the first time I ever installed SAP on my own and i am in the process of performing post installation steps from Installation Guide.
In the install guide, there is no mention of creating a new client ex: 100. Could you please, provide a list of tasks that generally needed to perform after the installation is completed and before doing any configuration in Solution manager.
I have some very basic idea on the Basis but while going thru Installation Guide I am not sure if there any steps that generally need to perform to complete the installation. My goal is to complete the Sol Mgr installation first and then start preparing for ECC 6.0 Installation.
Thanks a lot in Advance.

Hi,
First - the basic post installation steps are:
1. sick t-code need to execute
2. se06 --> Perform Post-Installation Actions
3. RZ10 --> Utilities --> Import profiles --> Of active servers
4. execute sgen T-code --> This will take some time
5. setup STMS
6. create client (If custom required)
7. Take backup of the system
For the solution manager client you could use the default created '001' client.
Next you need to run the solman_setup template which 'sets up' the SolMan for usage.
Follow config guide at: https://service.sap.com/~sapidb/011000358700000308502009E.PDF
For installing the ECC system, only a install key(from SMSY) is to be generated from SolMan. But if you want to use the SolMan effectively, suggest you to run the entire solman_setup.
Regards,
Srikishan

To extract portal activity data from the portal into Solution manager.

HI all,
I need to extract the portal activity data from the portal into Solution Manager BI and then later on into the SAP BW in order to generate BEx reports on the portal activity data. I need to know about the configuartions that are needed to be done on the portal side and the solution manager side so as to get the data into SolMan from portal. Waiting for a response.
Thanks and regards,
Divya.

Hi
In solution manager you can do the analysis of the ADC data files (Portal activity reporting) as as part of the End-to-End Diagnostics (Portal Activity Reporting tab in the End-to-End Workload Analysis).
Will you see the Portal Activity Reporting tab under End-to-End Workload Analysis?
by default PAR in SAP Solution Manager 7.0 EHP1 is deactivated ,since we requires
some manual configuration of the Activity Data Collector.
please follow the attached config guide in the SAP note for configuration.
Jansi

Ehp1:Solution Manager:Stuck at ddic activation

Similar Messages

Maybe you are looking for