DDIC_ACTIVATION Error solman EHP1

Hi
I am updating the solman 7.0 to EHP1. I am facing the DDIC activation error and error as below. I have tried to apply the sap note no 1256384 but not success. The SAP india has suggested me to do the same manually but I am getting error as "user id locked by SAINT".
Now SAP told me to ignore this error. Can u please guide me (exact menu path) that how to ignore this error ?
Error as below:
the error can be seen in SAPAIBIIP9.SM2:
4 EDT012XActivate table "UMGSIUUC1"
4 EDT181 Key field "F19" has unpermitted type "RAWSTRING"
4WEDT135 Flag: 'Incorrect enhancement category' could not be updated
4 EDT013 Table "UMGSIUUC1" was not activated
Thanks & Regards
Vimal

hello
i faced the same problem today
here is how i tackled it
saw the recommendation to import the note too late
created the transport in other system, the import was successful, however as mentioned above, the result was the same :
in se11 the UMGSIUUC1 was giving errors on F19 field when checked
So i had no choice but to try to reset the SPAM queue, it is not a pleasant job to do in DDIC_Activation phase
se16- deleted the entries in debug mode in PAT01 and PAT03 tables and SPAM queue was green
then to SNOTE and reimported the NOTE and the UMGSIUUC1was now ok
then i got the error OCS queue not empty and needed to delete the TP buffer which was showing the packages from before resetting the queue
Now the DDIC Activation phase has passed and i am hoping everything will finish smoothly

Similar Messages

Solman ehp1 installation error

Hi all,
we are facing some problem while installing Solman EHP1 on solaris_X64. with SID = SOL
we are getting the following error while giving the binaries for the installation export
An error occurred while processing option SAP Solution Manager 7.0 EhP1 > SAP Systems > Oracle > Central System > Central System( Last error reported by the step :Assertion failed: in function (sid, fileName) { if (!sid) { installer.writeError("ind-rel.ind-os.ind-db.j2ee-eng.noSID"); } var result = false; var unicode; var nw = NW.getSystem(sid); var unicode = nw.isUnicode(); var product = installer.getInstallationParameter("INSTPARA_PRODUCT"); var prodrel = installer.getInstallationParameter("INSTPARA_PRODUCT_VERSION"); var dbHost = nw.getDB().getDBHost(); var localhost = installer.getHostName(); var osFAName = (new SystemMgt()).getSystemInfo().getOSFAName(); var dbOsFAName = "ALL"; OraCom.trace("OraCom localhost: ", localhost, " dbHost: ", dbHost); OraCom.trace("OraCom nw.getDB()getDBHost(): ", nw.getDB().getDBHost()); OraCom.trace("OraCom dbOsFAName: ", dbOsFAName, " osFAName: ", osFAName); dbOsFAName = (dbHost.equals(localhost)) ? osFAName : "ALL"; OraCom.trace("OraCom dbOsFAName: ", dbOsFAName); templateFilePathOra = "/COMMON/INSTALL/ORA/"; var unicode = (parseBool(unicode)) ? "YES" : "NO"; OraCom.trace("OraCom importOradbpar unicode: " + unicode); if (!fileName) { fileName = "ORADBPAR.XML"; } var fileMgt = new FileMgt(); if (!fileMgt.isExisting(fileName, "FILE")) { var fileSrc = installer.getCD("SAPINST") + templateFilePathOra + "ORADBPAR.XML"; if (!fileMgt.isExisting(fileSrc, "FILE")) { installer.abortInstallation("dbmodora.fileNotFound", fileSrc); } var file1 = fileMgt.getNode(fileSrc); file1.copy(fileName); } installer.writeTrace("Reading volatile database parameters from '" + fileName + "'."); var client = ; client.files.push(fileName); installer.setKdbClient(client); var where = " WHERE PRODUCT = '" + product + "' AND PRODREL = '" + prodrel + "' AND OsFAName = '" + dbOsFAName + "'"; installer.writeTrace("where: " + where); var se = OraCom._getTableSVE(); var s = OraCom._getTableSV(); s.remove(); var fields = new Array("OsFAName", "serverVersion", "UNICODE"); var rows_s = se.arraySelect(fields, where); ASSERT(arguments.callee, rows_s.length > 0, "found no server version for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { var temp = rows_s; OraCom.trace("OraCom(row: ", dump_properties(temp)); var v_row = new Array(); if (temp.UNICODE == "" || temp.UNICODE == unicode) { v_row.OsFAName = temp.OsFAName; v_row.serverVersion = temp.serverVersion; s.insertRow(v_row); } } var where = " WHERE PRODUCT = '" + product + "' AND PROD_REL = '" + prodrel + "' AND OsFAName = '" + osFAName + "'"; installer.writeTrace("where: " + where); var ce = OraCom._getTableCVE(); var c = OraCom._getTableCV(); c.remove(); var fields = new Array("OsFAName", "clientVersion", "UNICODE"); var rows_c = ce.arraySelect(fields, where); ASSERT(arguments.callee, rows_c.length > 0, "found no client version for this where clause: " + where); for (var i = 0; i rows_c.length; ++i) { var temp = rows_c; OraCom.trace("OraCom(row: ", dump_properties(temp)); var v_row = new Array(); if (temp.UNICODE == "" || temp.UNICODE == unicode) { v_row.OsFAName = temp.OsFAName; v_row.clientVersion = temp.clientVersion; c.insertRow(v_row); } } var se = OraCom._getTableSBE(); var s = OraCom._getTableSB(); s.remove(); var where = " WHERE OsFAName = '" + dbOsFAName + "'"; OraCom.trace("where: ", where); var rows_s = se.arraySelect(undefined, where); ASSERT(arguments.callee, rows_s.length > 0, "found no server Bit for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { OraCom.trace("OraCom(row: ", dump_properties(rows_s)); s.insertRow(rows_s); } var se = OraCom._getTableCBE(); var s = OraCom._getTableCB(); s.remove(); var where = " WHERE OsFAName = '" + dbOsFAName + "'"; OraCom.trace("where: ", where); var rows_s = se.arraySelect(undefined, where); ASSERT(arguments.callee, rows_s.length > 0, "found no client Bit for this where clause: " + where); for (var i = 0; i rows_s.length; ++i) { OraCom.trace("OraCom(row: ", dump_properties(rows_s)); s.insertRow(rows_s); } tORA_TablespaceNameMapping_External = new Table("tORA_TablespaceNameMapping_External"); tORA_TablespaceNameMapping = new Table("tORA_TablespaceNameMapping"); tORA_TablespaceNameMapping.remove(); var v_fields = new Array("oldName", "newName"); var v_where = " WHERE PRODUCT IN ('','" + product + "')"; var rows_t = tORA_TablespaceNameMapping_External.arraySelect(v_fields, v_where); for (var i = 0; i rows_t.length; ++i) { tORA_TablespaceNameMapping.insertRow(rows_t); } result = true; } found no server version for this where clause: WHERE PRODUCT = 'SOLMAN' AND PROD_REL = '40' AND OsFAName = 'SOLARIS_X86_64').
Any suggestion on this is welcome
regards,
sen

Hi
solution for this error is as below
Oracle, SOLARIS_X86_64: Error message: found no server version
Symptom:
You get an error message like the following:
found no server version for this where clause: WHERE PRODUCT = 'SOLMAN' AND PROD_REL = '40' AND OsFAName = 'SOLARIS_X86_64'
Solution:
Proceed ad follows:
 1. Stop SAPinst.
 2. Go to the installation directory sapinst_instdir.
 3. Edit the ORADBPAR.XML file.
 4. In the ORADBPAR.XML file, search for the following:
 <row>
 <fld name="PRODUCT">
 <strval><![CDATA[SOLMAN]]>
 </strval>
 </fld>
 <fld name="PROD_REL">
 <strval><![CDATA[70]]>
 </strval>
 </fld>
 <fld name="UNICODE">
 <strval><![CDATA[]]>
 </strval>
 </fld>
 <fld name="OsFAName">
 <strval><![CDATA[SOLARIS_X86_64]]>
 </strval>
 </fld>
 <fld name="serverVersion">
 <strval><![CDATA[102]]>
 </strval>
 </fld>
 5. Replace '70' with '40':
 <row>
 <fld name="PRODUCT">
 <strval><![CDATA[SOLMAN]]>
 </strval>
 </fld>
 <fld name="PROD_REL">
 <strval><![CDATA[40]]> <<<<<<<<<<<<<< change 70 to 40
 </strval>
 </fld>
 <fld name="UNICODE">
 <strval><![CDATA[]]>
 </strval>
 </fld>
 <fld name="OsFAName">
 <strval><![CDATA[SOLARIS_X86_64]]>
 </strval>
 </fld>
 <fld name="serverVersion">
 <strval><![CDATA[102]]>
 </strval>
 </fld>
 6. Save the ORADBPAR.XML file.
 7. Restart SAPinst and choose "Continue with the old option" on the "What do you want to do" screen.
Regards,
Bharathy

Solman EHP1 upgrade Stack 20 - cannot log in to system

Hi all,
I am currently doing a patch of Stack 20 for solman EHP1. I was able to create the queue, was able to continue until import proper phase 2. After a while, i cannot log on the system.
CX_WB_ED_SYNTAX_ERROR is unknown. abap program SAPMSYST had to be terminated. status LIVE of the user interface SAPLSRABAX_EXC missing.
also we found a deadlock in the ora alert trace file.
here are the logs:
SLOG0944.log
ERROR SAPK-701DRINSAPBASIS SOL I 0012 20091027160822 SAPBASISUSER SAPBASIS     cbcsapsolm 20091027142413047
STOP MAIN IMPORT          SOL I      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
ERROR: stopping on error 12 during MAIN IMPORT
START INFORM SAP-SYSTEM OF SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
START tp_getprots          SOL Q      20091027160831              SAPBASIS     cbcsapsolm 20091027142413047
WARNING: System SOL. Warning.        20091027161236 :
WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.
      Please check that the R/3 system is running.
      Please check the system. Use transactions SM21, SM37, SM50.
WARNING:       (This warning is harmless if no further warnings follow.)
WARNING: System SOL. Warning.        20091027170810 :
ERROR:       The following call returned with exit code -100:
ERROR:         sapevt.exe SAP_TRIGGER_RDDIMPDP -t name=SOL
ERROR:       Background jobs cannot be started.
ERROR:       Please check trace file dev_evt.
WARNING:       (This warning is harmless if no further warnings follow.)
STOP imp all              SOL   7006 20091027170857              SAPBASIS     cbcsapsolm 20091027142413047
ERROR: RFC function TRINT_PROGRESS_INDICATOR returned 18
dev_evt
Tue Oct 27 17:08:08 2009
Trace File of External Event Raiser (Level=2, Append=0)
EventID: SAP_TRIGGER_RDDIMPDP
SAP message server host: cbcsapsolm
SAP message server service (new): 3900
SAP message server service (old): sapmsSOL
MsIAttachEx: connect to cbcsapsolm / 3900
NiIInit: allocated nitab (2048 at 0000000002980080)
NiHsLInit: alloc host/serv bufs (100/100 entries)
NiPGetNodeAddrList: got 1 interface(s) from operating system
          [0] IP-Address: 172.20.20.128
NiHsLGetNodeAddr: got hostname 'cbcsapsolm' from operating system
HN='cbcsapsolm.cbcmain.cbc.chinabank.ph'; Add[0]=172.20.20.128
NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
NiIGetServNo: servicename '3900' = port 0F.3C/3900
NiICreateHandle: hdl 0 state NI_INITIAL
NiIInitSocket: set default settings for new hdl 0 / sock 1812 (I4; ST)
NiIBlockMode: set blockmode for hdl 0 FALSE
NiITraceByteOrder: CPU byte order: little endian, reverse network, low val .. high val
NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3900 (timeout=5000)
Tue Oct 27 17:08:09 2009
SiPeekPendConn: connection of sock 1812 broke (10061-WSAECONNREFUSED: Connection refused)
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1812
    (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3900) [nixxi.cpp    2835]
NiICloseHandle: closing initial hdl 0
ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/3900 failed (rc=NIECONN_REFUSED) [msxxi.c      652]
ERROR ***: MsAttach (host=cbcsapsolm, serv=3900), rc = -100
MsIAttachEx: connect to cbcsapsolm / sapmsSOL
NiHsLGetNodeAddr: found hostname 'cbcsapsolm' in cache
NiIGetNodeAddr: hostname 'cbcsapsolm' = addr 172.20.20.128
NiHsLGetServNo: got service name 'sapmsSOL' from operating system
SN='sapmsSOL'; Port=0E.10/3600; PC=tcp
NiIGetServNo: servicename 'sapmsSOL' = port 0E.10/3600
NiICreateHandle: hdl 0 state NI_INITIAL
NiIInitSocket: set default settings for new hdl 0 / sock 1800 (I4; ST)
NiIBlockMode: set blockmode for hdl 0 FALSE
NiIConnectSocket: hdl 0 is connecting to 172.20.20.128:3600 (timeout=5000)
Tue Oct 27 17:08:10 2009
SiPeekPendConn: connection of sock 1800 broke (10061-WSAECONNREFUSED: Connection refused)
NiHsLGetServName: found port number 0E.10/3600 in cache
NiIGetServName: port 0E.10/3600 = servicename 'sapmsSOL'
***LOG Q0I=> NiPConnect2: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 2835]
ERROR => NiPConnect2: SiPeekPendConn failed for hdl 0 / sock 1800
    (SI_ECONN_REFUSE/10061; I4; ST; 172.20.20.128:3600) [nixxi.cpp    2835]
NiICloseHandle: closing initial hdl 0
ERROR => MsIAttachEx: NiBufConnect to cbcsapsolm/sapmsSOL failed (rc=NIECONN_REFUSED) [msxxi.c      652]
ERROR ***: MsAttach (host=cbcsapsolm, serv=sapmsSOL), rc = -100
alert_sol
Tue Oct 27 16:08:17 2009
ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_5280.trc.
Tue Oct 27 16:08:20 2009
Completed checkpoint up to RBA [0x5e7.2.10], SCN: 17756362
Tue Oct 27 16:08:22 2009
ORA-00060: Deadlock detected. More info in file f:\oracle\sol\saptrace\usertrace\sol_ora_188.trc.
hope you can help!
Many thanks!
Edited by: Jeb Barrios on Oct 28, 2009 3:11 AM
Edited by: Jeb Barrios on Oct 28, 2009 3:13 AM
Edited by: Jeb Barrios on Oct 28, 2009 3:15 AM

Hi,
Based on my checks, in my opinion its best to open an OSS msg, as most of the time it will require the message processor on SAP side to apply some internal tool to resolve this. Since it is a matter with package stuck scenario.
You may want to open under BC-UPG-OCS
Hope this helps.
Cheers
SH

SOLMAN EhP1 xml file problem

I am upgrading my Solution Manager 7.0 from stack 17 to stack 18(EHP1) but whenever I try to generate the xml file on the service marketplace, all I get is "The table does not contain any entries"
To recreate...
go to service.sap.com/swdc --> SAP Support Packages --> Support Package Stacks --> SAP Solution Manager 7.0
Then...
Target Stack = SAP SOLUTION MANAGER 7.0 EHP 1-Initial Delivery
Source Stack = 17 (8/2008)
when I click NEXT, it goes straight to page 3 of 3, and I get buttons for Previous Step, Print List, Save as file, Add to download basket, Side Effects report, etc...
Then the table where all the packages should be is empty, except for the message "the table does not contain any entries"
We have tried this with multiple people on multiple machines, all the same result. By the way I just upgraded from abap & java stack 15 to 17.. and I had no issues getting the xml file there. (I downloaded the DVDs of the actual patches so I just need the xml)
Thanks!
Edited by: Bill McCrea on Jan 15, 2009 2:42 PM

After reading your question, I went to the SPstack webpage, and selected a SOLMAN EHp1 stack 16-17, DB2 UDB. when I was on the "Step 3 of 3 Downloadable support packages" I was able to select the Save as File button and I was able to generate the XML. It may have been a temporary problem. Make sure that you don't have a pop-up blocker that would prevent the window from appearing.
Regards
---Bill

How to install diagnostic agent for nw 7.0sp17, with solman ehp1- sp25

Hi Gurus,
we are using NW 7.0 Enterprise portal at SP17, want to configure E2E. So installed solution manager 7.0 EHP1 SPS 25.
Ran the Guided procedure solman_setup successfully. with intitial config, basic config and pending at managed system config.
Here my question is:
do i need to install smd agent on solman? or solman itself comes with agent. i cannot see any agent in mmc on solution manager.
What is SOLMANDIAG and SOLMAN AGENT, SMD Agent and Host agent.
The guide (https://websmp207.sap-ag.de/~sapidb/011000358700000952852009E) says before install SMD agent, install host agent, diagnostics agents are available 7.11 on wards, while installing smd agent sapinst asking SAP Unicode Kernel 711 , but currently my NW Portal system is using kernel 7.0..
Any guide, how to proceed for E2E on nw7.0 SP17 with solman ehp1 sp25( highest availale spack)
Thanks in advance.
Regards
Balaji

Hi Balaji,
As per the SMD agent 7.11 installation guide (https://service.sap.com/~sapidb/011000358700000952852009E) , Page 6 and 8, you would need to download the standard NW 7.11 DVDSs( usually kernel and Installation master) and SMD agent installation packages from the SMP. Location is mentioned in the guide as well.
For your query that Portal is based in i386, these are two different things. The SMD Agent will be installed with its own kernel and also 7.11 kernel is not support edon 32bit. However the SMD agent will use its own 7.11 64bit kernel and Portal will use its i386 kernel. Hopefully your hardware is able to support both. I recommend to proceed with x86_64 7.11 kernel for your SMD installation. Incase the hardwar does not support this, go for alower release of SMD Agent wherein the kernel supports 32 bit hardware.
Best Regards,
Srikishan

Error with ECC 6.0 and Solman Ehp1 on same system

Hi,
I implemented Ecc 6.0 on Windows server 2008 and sql server 2005. Then i installed solman 7.0 ehp1. I had used athe vbscript for solman key which was available online. i Created two seperate SID for them and DBSID but using the same instance of database.
After successfully implementing both of them only one runs fine at the same time. Either ECC or solman will run disp+work.exe of one of them gets stopped.
Can someone help me out with this?
Edited by: Dshah_EnCrisp on Aug 2, 2009 6:28 AM

Hai,
Try to check the Memory requirements, post the dev_disp, dev_w* files for our analysis.
As you said that you have single DB for both the systems, did you follow the installation steps carefully for MCOD systems.
Regards,
Yoganand.V

E2E_EXTRACTOR_CONTROLLER jobs don't run with SOLMAN EhP1

Hi!
I am using SAP Solution Manager 7.0 EhP1 and would like to use Solutio Manager Diagnostics functions there.
I already installed Wily Introscope 8.0, the SMD agent. I configured all the satellite system and can already see some graphics and BI data within Workload Analysis, Change Analysis.
My problem is that since almost one month no E2E_EXTRACTOR_CONTROLLER jobs
are scheduled in SOLMAN.
Question:
Can some one explain how to schedule these jobs in order to see actual data for WA, CA, etc.?
What I already done:
I run several times again the SMD Setup for Managing and Managed system without any errors
I traced the entries in table E2E_ACTIVEEXTR (set for all the entries the "x" flag in field "Active")
I have a look int the table E2E_ACTIVE_WLI. This table is not empty and contains a lot of entries.
I have a look int the table E2E_ECSTATUS . This table is not empty and contains a lot of entries.
It will be great to get some helpful information
Thank you very much

Hi!
Many thanks for your response.
Unfortunately when I access to
http://<host>:<port>/smd I can see only Diagnostic Setup tab.
Question:
Do you know whether with EhP1 the Extractor jobs are also calling "E2E_EXTRACTOR_CONTROLLER"?
How can I manually schedule these jobs?
Thank you very much!
regards
Holger

Error in EHP1 Portal Installation

Dear All,
I am facing a weird error while install EHP1 Portal system. When it comes to phase Install Software units, it always fail with the same error. System details are below:
System: Netweaver Portal EHP1 System (Usage Type: As Java, EP, EP Core and DI)
OS: Linux Red hat 5.2
Database: DB2 9.7 FP 3
JDK: 1.4.2
Please check below error log:
sapinst_dev.log:
ERROR 2011-03-16 14:30:02.174 [iaxxejsbas.cpp:204]
FJS-00003 uncaught exception: nw.sdm.deploymentErrorWithLog:
SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check /usr/sap/trans/instlogdir/sapinst_instdir/NW701/AS-JAVA/DB6/CENTRAL/
/callSdmViaSapinst.log for more information. (in script unknown, line 0: ???)
TRACE 2011-03-16 14:30:02.790 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 2832
TRACE 2011-03-16 14:30:02.914 [syuxctask.cpp:1382]
 CSyTaskImpl::start(bool)
A child process has been started. Pid = 2833
ERROR 2011-03-16 14:30:05.434 [sixxcstepexecute.cpp:950]
FCO-00011 The step enableUsageTypes with step key |NW_Onehost|ind|ind|ind|ind|0|0|SAP_Software_Features_Enablement|ind|ind|ind|ind|5|0|enableUsageTypes was
executed with status ERROR ( Last error reported by the step :uncaught exception: nw.sdm.deploymentErrorWithLog:
SDM deployment failed for at least one of the components to be deployed. SOLUTION: Check /usr/sap/trans/instlogdir/sapinst_instdir/NW701/AS-JAVA/DB6/CENTRAL/
/callSdmViaSapinst.log for more information. (in script unknown, line 0: ???)).
callSdmViaSapinst.log:
Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.
com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [a2zportalprd] with user name: [Administrator]
 Check your login information.
 Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. Root exception is co
m.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.
 at com.sap.engine.services.security.remote.login.RemoteLoginContextExt.<init>(RemoteLoginContextExt.java:34)
 at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:81)
 at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:355)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:675)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:257)
 at javax.naming.InitialContext.init(InitialContext.java:233)
 at javax.naming.InitialContext.<init>(InitialContext.java:209)
 at com.sap.engine.deploy.manager.DeployManagerImpl.checkCredentials(DeployManagerImpl.java:2983)
 at com.sap.sdm.serverext.servertype.inqmy.extern.DeployManagerAuthMethodInvoker.invokeCheckCredentialsInternal(DeployManagerAuthMethodInvoker.java:51
System is running and I am able to login with administrator user id. There is only single server node and there is no error related to expiration time. SDM is also running. Secure store is also correct. Still I am facing same problem. I checked on SDN as well and found many reference of the same problem but none of them resolved my problem.
Please suggest.
Thanks
Sunny

Hi Sunny,
Check note 1313644 and 609603. Hope it helps.. The 1st link seems to have the same issue.
Also Refer:
SDM Problem installing SAP Netweaver EHP2
ERROR: Cannot connect to Host: [SERVER] with user name: [J2EE_ADMIN]
Rgds,
Soujanya

DDIC_ACTIVATION ERROR WHILE APPLYING SUPPORT PACKAGE SAPKW35020 IN ECC5.0

Hi Gurus,
I am getting error DDIC_ACTIVATION while applying support package(BW) SAPKW35020 in ECC5.0 with MSSQL database in Windows server.
I am not able to reset the queue, when i tried to reset the queue the system prompting that " cannot reset queue while DDIC_ACTIVATION" phase".
Can you please help to reset the queue and implementing this support package.
Thank you,
Regards,
Ganesh

Paste the SPAM log here.
Regards,
Nick Loy

DDIC_ACTIVATION error while applying SAPKE60029

Dear all,
i am applying support patch of HR.
having ecc 6.0 with oracle and windows 2003
beforing applying HR patch i had upgrade spam/saint level 35
also upgrade latest kernel and all basis, aba, ap, bw patches had been upgrade.
now when i am importing SAPKE60029 to SAPKE60034 in queue
then facing a problem with DDIC_ACTIVATION phase
i restart the spam and again try to import but fid that there are some objects which had been activated with warrning and some not activated .
INCLUDE TABLE PS9999 is not active
ROUTINE EXPAND (TABLE PB9999 could not be activated)
after seeing log i check the status in se11 then i found
table PS9999 not exsist while PB9999 partialy activated.
also see notes for knowing error and others ..
but not able to get what should i have to do...
Regards
Dik

Its ok
every dependency is ok...
i resolve the problem with the help of HR....
just include PS9999 after creating it...then try to activate PB9999
after that activation phase has been complete sucessfully.
Regards
Dik

Problem with Maintenance Optimizer - Solman EHP1

Hi All,
I have a solution manager 7.0 ehp1 system and maintenance optimizer does not work at all.
Initial configurarion and Basic configuration has been done - Tcode : Solman_Setup
A solution has been created and systems have been assigned to it, however when i launch create new maintenance
transaction it shows us the solution and the systems assigned under it.If i select our Production system and click on next
it comes up an error, saying the table does not contain any data. Do i need to do the SLM configuration for MOPZ to work?
Has anyone seen this error earlier. Any inputs would be of great help.
Regards,
Ershad Ahmed.

Hi,
Though the error does not give much insight. There are some warnings which tells that configuration has to be done
Please find the warnings attached in the email.
Not able to find an active SLM for selected managed systems
No configured SLM
No common SLM system is regsitered for Managed Systems
The system / systems - SID have not beed registered in SLM
Instance -type missing in SMSY for an application server instance of system .
Regards,
Ershad Ahmed

CHECK_GROUPS parameter in SOLMAN_SETUP with SolMan EHP1 SPS19

Hello to everybody!
I'm trying to add a new Java System to the SolMan. Everything in SMSY seems to be ok.
This is my way:
- TA SOLMAN_SETUP -> Configure Managed Systems -> switch to Java Systems -> select new Java system and start the wizard
- After executing the first step (checking prerequisites of Diagnostics) a error message is displayed with a red indicator:
"The result of prerequisite check cannot be analysed". The detailed message says "The checkgroup Managed systems setup prerequisite is unknown. Please check the CHECK_GROUPS parameter."
The last massage causes a lot of question marks. Does anybody know anything about this parameter? Where can I find and how do I configure this parameter?
Looking forward to the light of knowlege!
Sascha

Hello Andreas,
I got the solution of this problem from SAP Support:
Please have a look at the following note #1309758. With the installation via SNOTE the bug was killed and I'm now able to go ahead with the configuration wizard.
Have a nice day!
Sascha

DDIC_ACTIVATION Error during application of Support Pack SAPKH47007

Hi All,
We were trying to apply Support Pack SAPKH47007 and it gave us an error in DDIC_Activation Phase and when i checked the logs it gave us this error
Relationship TMFK-TDID for table TTXS does not exist
Check dependent search help S_TMFK_SETTLE
Search help S_TMFK_SETTLE is consistent
I searched and found one Relevant Note for this SAP Note Num : 625098 and it tells us to delete the following fields
Delete the fields FLG_AK_PAYM_FICA and FLG_AK_PAYM_FIAR from the table
I went to SE11 and i dont see this fields there, and even though if i see them i dont think i can delete them coz it is asking Developer Key.
Upon further checking i found that if we delete the Contents in Pat01 and Pat03 we can go ahead and redo the support packs from begining. Can anyone throw some light on this as to how safe is this?
Regards,
Ershad Ahmed.

Did you read the note I gave you?
The note says:
Symptom: An error occurs in the DDIC_ACTIVATION phase when you import Support Package SAPKH47007. The DDIC activation log records the following error messages:
Relationship TMFK-TDID for table TTXS does not exist
<...>
Solution: A general solution to the problem is available with R/3 Support Package SAPKH47010. To avoid the error, import the Support Packages SAPKH47007 and SAPKH47010 together in a queue.
If you have already encountered this error, the queue must be reset and extended to include Support Package SAPKH47010. Since you cannot reset the queue from the DDIC_ACTIVATION phase using normal means, this must be done by SAP Support (Component BC-UPG-OCS).
Markus

DDIC_ACTIVATION ERROR

While applying support package for SAP_HR, I am getting the following error..Please help me..My system is just upgraded to ECC6..
ERROR in phase: DDIC_ACTIVATION
Reason for error: TP_STEP_FAILURE
Return code:0008
Error message OCS pkgSAPKE60023,tp step A return code 008
Regards,

Hai,
To view the cause of the error in the activation log, choose Goto -- Log -- Queue.
Please post the logs.
If you import two or more Support Packages in a queue, activation errors can result from an incorrect activation sequence for Dictionary objects. If this is the case, the activation errors disappear if the objects are activated again. To do this, choose Support Package -- Import queue.
Check in SAP Market place for some SAP Notes for known problems.
Regards,
Yoganand.V

DDIC_ACTIVATION ERROR SP queue SAPK-70103INPIBASIS-SAPKA70104

Hello all,
I am facing this error during Queue Import
- Error in phase: DDIC_ACTIVATION
- Reason for error: TP_STEP_FAILURE
- Return code: 0008
- Error message: OCS Package SAPK-70103INPIBASIS, tp step A,
 return code 0008
i have a queue of following patches
SAPK-70103INPIBASIS
SAPK-70104INPIBASIS
SAPKB70103
SAPKB70104
SAPKA70103
SAPKA70104
in the transport log file its showing following entries in RED color
Table UMGSIUUC1 could not be activated
(W- Flag: 'Incorrect enhancement category' could not be updated )
Field KEY: Component type or domain used not active or does not exist
Table /1PYXXFO/SAP_PAYSLIP_____L0001 could not be activated
Field KEY: Component type or domain used not active or does not exist
Table /1PYXXFO/SAP_PAYSLIP_____L0020 could not be activated
Function EMINT_GET_NEW_CENTRAL_NEGLIST (S4EM|01) does not fit into the existing function group ((S2EM|10))
I tried to activate them manually but still the same error.
Is it something related to RSA7 (BW delta queue Maintenance)? As a step in deleting setup-up table data i deleted all the BW delta queue maintenance as we are not using it anymore. We built the system from a export image of system which was used to update BW system using BW extractions.
Can any body please shed some light on the same. i allready tried these notes nut in vain.
822379
556962
556972
here is the extract from SLOG file
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165213 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165230 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165231 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165239 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165707 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165713 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165730 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165731 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090527165739 :
WARNING: Background job not running properly. Function: J Jobcount: 15314200 Status: S.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
STOP tp_getprots <SID> Q 20090527165803 <USERNAME> <HOSTNAME> 20090527134327126
STOP INFORM SAP-SYSTEM OF <SID> Q 20090527165803 <USERNAME> <HOSTNAME> 20090527134327126
STOP tp_getprots <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477
START INFORM SAP-SYSTEM OF <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477
START tp_getprots <SID> Q 20090527165809 <USERNAME> <HOSTNAME> 20090527140355477
ERROR SAPK-70103INPIBASIS <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPK-70104INPIBASIS <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70103 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> Q 20090527170454 <USERNAME> <HOSTNAME> 20090527140355477
STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170454 <USERNAME> <HOSTNAME> 20090527140355477
ERROR SAPKA70104 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70103 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70104 <SID> A 0008 20090527170451 SAPUSER <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> J 20090527170457 <USERNAME> <HOSTNAME>
STOP DD ACTIVATION <SID> A 20090527170457 <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224
START INFORM SAP-SYSTEM OF <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224
START tp_getprots <SID> Q 20090527170500 <USERNAME> <HOSTNAME> 20090527135646224
STOP tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847
START INFORM SAP-SYSTEM OF <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847
START tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135046847
STOP tp_getprots <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135646224
STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170501 <USERNAME> <HOSTNAME> 20090527135646224
STOP tp_getprots <SID> Q 20090527170502 <USERNAME> <HOSTNAME> 20090527135046847
STOP INFORM SAP-SYSTEM OF <SID> Q 20090527170502 <USERNAME> <HOSTNAME> 20090527135046847
thanks
Mani

Well there is no other option is just halting the operation no 'CONTINUE' or 'SKIP' Button. i dont know what is *.ECO file but i have *.<SID> file.
i executed RDDNEWPP as suggested by some people using user DDIC in client 000 but i dont know what to do next.
I am updating my Support Package not implementing Enhancement package 4, i alllready have EHP 4 ECC^ system in place, i want to implement TREX EMBEDDED SEARCH functionality into our system and that require Support package 4 for some functionality. that what i am stuck into.
I imlpemented note 71353, 26966 and note 11677 but no luck.
Can i know if we can import transport queue from OS level on Windows plateform.
but now i am getting different error in SLOG file.
SLOGXXXX.<SID> log is
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090528181849 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090528182349 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090528182849 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090528183349 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
WARNING: System <SID>. Warning. 20090528183850 :
WARNING: Background job RDDIMPDP could not be started or terminated abnormally.
 Please check that the R/3 system is running.
 Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This warning is harmless if no further warnings follow.)
STOP tp_getprots <SID> J 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853
STOP DD ACTIVATION <SID> A 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853
START DISTRIBUTION OF DD-O <SID> S 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> S 20090528184210 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> S 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853
STOP DISTRIBUTION OF DD-O <SID> S 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853
START TBATG CONVERSION OF <SID> N 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> N 20090528184515 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> N 20090528184730 <USERNAME> <HOSTNAME> 20090528173755853
STOP TBATG CONVERSION OF <SID> N 20090528184730 <USERNAME> <HOSTNAME> 20090528173755853
START MOVE NAMETABS <SID> 6 20090528184731 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> P 20090528184731 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> P 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853
STOP MOVE NAMETABS <SID> 6 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853
START MAIN IMPORT <SID> I 20090528191116 <USERNAME> <HOSTNAME> 20090528173755853
STOP MAIN IMPORT <SID> I 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853
START TBATG CREATION OF EN <SID> n 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> Y 20090528191310 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> Y 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853
STOP TBATG CREATION OF EN <SID> n 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853
START SET VERSION FLAGS <SID> V 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> V 20090528191605 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> V 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853
STOP SET VERSION FLAGS <SID> V 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853
START EXECUTION OF REPORTS <SID> R 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> R 20090528191755 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> R 20090528191940 <USERNAME> <HOSTNAME> 20090528173755853
STOP EXECUTION OF REPORTS <SID> R 20090528191940 <USERNAME> <HOSTNAME> 20090528173755853
START GENERATION OF REPORT <SID> G 20090528191941 <USERNAME> <HOSTNAME> 20090528173755853
START tp_getprots <SID> G 20090528191941 <USERNAME> <HOSTNAME> 20090528173755853
STOP tp_getprots <SID> G 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853
STOP GENERATION OF REPORT <SID> G 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853
STOP imp single <SID> 0004 20090528192146 <USERNAME> <HOSTNAME> 20090528173755853
START DD ACTIVATION <SID> A 20090528235747 <USERNAME> <HOSTNAME>
START tp_getprots <SID> J 20090528235747 <USERNAME> <HOSTNAME>
ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70103 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70104 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70103 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70104 <SID> A 0008 20090529000418 SAPUSER <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> J 20090529000423 <USERNAME> <HOSTNAME>
STOP DD ACTIVATION <SID> A 20090529000423 <USERNAME> <HOSTNAME>
START DD ACTIVATION <SID> A 20090529105521 <USERNAME> <HOSTNAME>
START tp_getprots <SID> J 20090529105521 <USERNAME> <HOSTNAME>
ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70103 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70104 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70103 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70104 <SID> A 0008 20090529110126 SAPUSER <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> J 20090529110127 <USERNAME> <HOSTNAME>
STOP DD ACTIVATION <SID> A 20090529110127 <USERNAME> <HOSTNAME>
START DD ACTIVATION <SID> A 20090529121729 <USERNAME> <HOSTNAME>
START tp_getprots <SID> J 20090529121729 <USERNAME> <HOSTNAME>
ERROR SAPK-70103INPIBASIS <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPK-70104INPIBASIS <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70103 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKA70104 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70103 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
ERROR SAPKB70104 <SID> A 0008 20090529122901 SAPUSER <USERNAME> <HOSTNAME>
STOP tp_getprots <SID> J 20090529122905 <USERNAME> <HOSTNAME>
Mandeep

DDIC_ACTIVATION Error solman EHP1

Similar Messages

Maybe you are looking for