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

Similar Messages

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 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

Error "Event Queue Overflowed" with the "Write file to Citadel Server"

Hello,
I can import data from a file and I can see the data
in the historical database without troubling.
But I always have this error "Event Queue Overflowed", that don't perturb my data and my application (I have just this boring message).
I have tried many things :
- increasing the size of my input buffer (-> 1.000.000, no change) : I don't think so that it's important because I've tried with a value of 100 and anyway sometimes my application works with this small value of 100.
- increasing the File_location tag size (-> 260). No change.
- My write to Citadel.cfg is in the LabVIEW folder.
Can you help me ?
Thank you.

Hi,
What version of LabVIEW DSC are you using? if it is 6.1, have you applied fixes linked below.
http://digital.ni.com/softlib.nsf/websearch/513AA4A0BB60D10086256B48006D44B5?opendocument
I have seen a similar issue at the link below.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RNAME=ViewQuestion&HOID=5065000000080000008C640000&ECategory=LabVIEW.Datalogging+and+Supervisory+Control
Please let me know if you have read it through?
Best Regards,
Remzi A.

CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery

Today, I changed a Tuxedo application (server) to the product systems(One master and two slaves). Only a small changes in code. But after a period of running, there are many errors in ULOG:
CMDTUX_CAT:1380: ERROR: Message queue blocking prevented delivery, Qaddr = 583902
And then, the server is died. After restart the server, this will happen again later.
I don't know why this happens? Thx.

Hi Bill,
This is happening because the BRIDGE process received a message from the network and was unable to place the message on the intended IPC queue. This could be because the server handling that message is backed up, or the system IPC resource settings are too low. Please check the recommended actions in:
http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/messages/cdtux/cdtux013.html
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Cannot reset the queue from import phase by DDIC_ACTIVATION error in SAINT

Dear All,
The add-on installation terminated during phase DDIC_ACTIVATION in SAINT.
I cannot reset the queue from import phase after import the SAPK-600AGINP3A and SAPK-60001INAFS.
How can I do to reset it ???
Please help
Thanks

> Table J_3ACSIZ could not be activated
> (E- J_3ACSIZ-ZZAUFMENG (combination reference table/field J_3ACSIZ-ZZME does not exist) )
> Table J_3APVAS could not be activated
> Table KOMP could not be activated
> (E- KOMP-ZZAUFMENG (combination reference table/field KOMP-ZZME does not exist) )
> Table J_3ACSIZ could not be activated
> (E- Table J_3ACSIZ does not exist )
You added apparently some fields to a table (ZZ*) and you did not maintain that modification when SPAM requested you to do so. Now the tables should be activated but the field is missing.
Markus

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

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 - Table /NFM/A_KNVVEXIT does not exist

Hello,
I'm getting a DDIC_ACTIVATION/TP_STEP_FAILURE error while importing ECC6 SP12-14 to my QAS system. In the log it's giving an error 'Table /NFM/A_KNVVEXIT does not exist'. This table does exist in DEV, but not in QAS.
Does anyone have an idea of how I can get this structure into my QAS system? Or why it isn't already there?
I have tried rerunning the queue in case it was just an order of operation error, but that doesn't seem to be the case this time.
Thank you,
Michael

Opened an customer message with SAP and they fixed logged in and fixed it.

SAPKH60008 DDIC_ACTIVATION error (SAP APPL)

Hi,
I have defined queue for SAPKH60008-SAPKH60012. Encountered error DDIC_ACTIVATION on SAPKH60008.
Need your advice on the resolution.
Thank you very much.
Rgds
Shese

Hi Shese,
Please pase here error details so that we can provide solution.
Regards,
Anil

Help in resolving the error - Incident Queue is full

I've been given a 4.2.4 system to look into since the previous admin left some time ago.
I have found we are seeing the following
Error pn datax IncidentXmlNotificationServlet PN-1100: Java message: Error sending XML Notification. Incident Queue is full.
and we no longer get the previously configured XML emailed actions when a rule gets hit.
I have been looking trying to determine what and how needs to be cleared.
Any insight would be appreciated.

Thanks,
Actually that is what I did (reboot) and functionality has returned.
Thanks for suggesting something so obvious that I didn't think about that. I guess I wanted to make the issue and resolution more complex that it needed to be.

Response message error in queue when using ABAP proxy

I am using an abap proxy for the first time, and some of the response messages are getting stuck in the sender's (R/3) inbound queue. To resolve them, I have to either reset the status or execute the LUW. Sometimes, this doesn't even work.
Here is my "asynchronous" scenario:
R/3 -> <proxy> -> PI -> <file adapter> -> File
The R/3 system that I'm using has not used PI before, so I'm thinking something is missing from the set-up on the R/3 side. On the errors I finally do get to process, I get the following error in the SXMB_MONI on the sender (R/3) side (the PI SXMB_MONI shows successful). Can someone help me understand what a response message is and how it is different from an acknowledgement? Also, help me to understand what could be causing the response messages to get stuck in the R/3 queue.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
   - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
    <SAP:Context />
    <SAP:Code p1="MessageId"
                      p2="4962B2EDB60A003BE1008000A2844D1A"
                      p3="00000000000000000000000000000000"
                      p4="">PROTOCOL.WRONG_HEADER_IN_RESPONSE</SAP:Code>
    <SAP:Text language="EN">Response message header contains the value 00000000000000000000000000000000 in element MessageId instead of the expected value 4962B2EDB60A003BE1008000A2844D1A</SAP:Text>
</SAP:ErrorHeader>

Ultimate testing tool for services is soapUI (Freeware)
http://www.soapui.org/
If you can invoke your service from soapUI and you receive a response, then PeopleSoft is working fine and the request handling in the calling system is incorrect.
Try downloading soapUI and try invoking your service (not that a fan of SendMaster).
Hakan

TREX - Search Failure - HTTP Server error: 503 - Queue Server down

Hello,
I've got a problem with TREX, the following tasks results in erros:
Default Search
Search Failure
Error during search occurred - com.sapportals.wcm.WcmException: HTTP server error: 503 (Errorcode 7266)
An unexpected severe error occurred during the search call. If the situation persists, inform your system administrator.
Creating Index
Error 503
- On Index Administration: indexes status are green
- On TREX Monitor: Takes long time to loa. HTTP Server and Name Server are green. There is no entry for Queue Server
- On TREX Monitor > Display Queues: Takes a long time and then no queues are displayed
- On Portal Monitor > Request Overview: Requests for TREX takes pretty long time
Starting Time: 9:16:23 AM
Starting Date: May 19, 2010
Request Name: NW:J2E:SRV:HTTP
User ID: <my user>
Outbound Data: n/a
Duration: 395671
CPU Time: 5812
Component Entries: 26
Component with Largest Net Time: EP:KM:TREX:HTTP:<host>:30205
Largest Net Time: 38867
Component with Largest Net CPU Time: EP:PRT_render:.../com.sap.km.TrexMonitor
Net CPU Time: 5674
Could you help me with procedures or guides on how to solve the problem and start the queue server?
kind regards,
Rafael

BASIS team reseted TREX and it's working again

Full Export/Import Errors with Queue tables and ApEx

I'm trying to take a full export of an existing database in order to build an identical copy in another database instance, but the import is failing each time and causing problems with queue tables and Apex tables.
I have used both the export utility and Data Pump (both with partial and full exports) and the same problems are occurring.
After import, queue tables in my schema are unstable. They cannot be dropped using the queue admin packages as they throw ORA-24002: QUEUE_TABLE <table> does not exist exceptions. Trying to drop the tables causes the ORA-24005: must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables error
As a result, the schema cannot be dropped at all unless manual data dictionary clean up steps (as per metalink) are done.
The Apex import fails when creating foreign keys to WWV_FLOW_FILE_OBJECTS$PART. It creates the table ok, but for some reason the characters after the $ are missing so the referencing tables try to refer to WWV_FLOW_FILE_OBJECTS$ only.
I am exporting from Enterprise Edition 10.2.0.1 and importing into Standard edition 10.2.0.1, but we are not using any of the features not available in standard, and I doubt this would cause the issues I'm getting.
Can anyone offer any advice on how I can resolve these problems so a full import will work reliably?

Thanks for the lead!
After digging around MetaLink some more, it sounds like I'm running into Bug 5875568 (MetaLink Note:5875568.8) which is in fact related to the multibyte character set. The bug is fixed in the server patch set 10.2.0.4 or release 11.1.0.6.

DDIC_ACTIVATION ERROR SP queue SAPK-70103INPIBASIS-SAPKA70104

Similar Messages

Maybe you are looking for