on 05-03-2014 2:27 AM
Hello,
While upgrading ST-PI component 2008_1_700 from 0007 to 0009 in our quality system, we got error to activate table DDXTF in se11 in stage CHECK_REQUIREMENT.
In development system we were able to successfully upgrade the components without any error
Activating the table DDXTF gives error as shown below and on checking the db and runtime object I found below inconsistency
I have reset the queue for time being but the inconsistency of table DDXTF its now creating problem when we try to transport few objects.
Kindly request your help to solve the inconsistency with the table DDXTF
We reproduced the error with table in our sandbox system and have tried to solve following these steps :
1. Imported DDXTF table from dev system to sandbox, didnt help
2.Dropped the table DDXTF and reconstructed it in sandbox ,didnt help
Thanks
Shradha
Hi Shradha,
Reason for asking number of entries in DDXTF table is just to confirm that you've should not have any inactive nametab but at your end there are 31 no. of inactive nametabs as per SAP Note 932779 - Unicode conversion - analysis of nametab problems
Here i would suggest you to first take backup of this table or perform the activities under your other test system for successful upgrade of ST-PI :
1.Take backup of DDXTF.
2.Clear entries from table DDXTF table.There should be 0 entries in this table.
3.Try to upgrade ST-PI component again.
Hope this will help you.
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shradha,
Have you tried deleting and recreating the table using SE14? Usually there will only be entries in this table during an upgrade or transport, and once the transported objects have been successfully activated, the entries in DDXTF get cleared. Do you have other objects in your QAS system that are inactive and shouldn't be? Perhaps from a transport or earlier stage of your upgrade that didn't finish successfully?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Matt,
We tried below query and were able to make the table DDXTF consistent in our sandbox table. But not sure if anything else would get affected by deleting these, do you think deleting these would break anything ?
I think you meant I should check these tables for inactive objects :
I see tables with status L in table DD02L but DDXTF is in A status
I see NO programs/FM with status I in table REPOSRC
Deleting the fieldname called “FIELD” in DD03L
DELETE FROM SAPR3.DD03L WHERE DD03L.TABNAME='DDXTF' AND DD03L.FIELDNAME='FIELD' AND
DD03L.AS4LOCAL='A' AND DD03L.AS4VERS='0000' AND DD03L.POSITION='0004' AND
DD03L.ROLLNAME='DDNTFIELD' AND DD03L.CHECKTABLE=' ' AND DD03L.REFTABLE=' ' AND
DD03L.PRECFIELD=' ' AND DD03L.REFFIELD=' ' AND DD03L.DOMNAME='DDNTFIELD' ;
COMMIT;
Deleting column “Field” from table DDXTF
ALTER TABLE SAPR3.DDXTF DROP (FIELD)
/
Thanks
Shradha
Actually, I meant delete and recreate the table using SE14. In normal processing, this table should be empty. It only temporarily has entries during import of transports or support packs, or during an upgrade. At the end of successful activation of imported objects, the entries in this table for those objects should be cleared. So, if you have 31 objects in the table in QAS, but 0 in DEV, then you probably had some prior failed import in QAS. Assuming you don't actually have a problem with other inactive objects, then very likely the only real problem is the presence of this data in the table.
So, try this in your sandbox system to ensure it works and doesn't cause any other issues. Go into tcode SE14. Enter DDXTF as the object name, select 'Tables' for dictionary objects, and click Edit. On the next screen press Delete database table. There will likely be a few warnings and 'are you sure' type messages. When that process is complete, then press Create database table. This should create a new DDXTF table, active and empty, on your database using the DDIC definition as a template.
If that works, and you have a successfully activated DDXTF table with no entries in it, then try running the ST-PI update on your sandbox and see if you get the error you got in QAS. If not, then I would say you have a solution.
Hello Matt,
We had tried recreating the table the way you explained above before carrying out these deletions.
But after recreating database table, the runtime object was still inconsistent with same error as shown above.
So we tried activating and adjusting it with database but it generated abap error "LOAD_TYPE_VERSION_MISMATCH"
**************************************************************************************
Runtime Errors | LOAD_TYPE_VERSION_MISMATCH |
Date and Time | 05/05/2014 11:36:25 |
Short text
Change of a Dictionary structure at runtime of a program. |
What happened?
Runtime error |
The current ABAP program "SAPLSDNT" had to be terminated because one | |
of the statements could not be executed at runtime. |
What can you do?
Restart the program. | |
If the error persists, contact your SAP administrator. | |
You can use the ABAP dump analysis transaction ST22 to view and manage | |
termination messages, in particular for long term reference. |
Error analysis
The ABAP runtime system detected that the Dictionary-type "DDXTF" changed | |
during the flow of the transaction. | |
As the type was already used in the old version | |
and in the new type should be used in the same transaction in the new | |
version, the transaction had to be cancelled to avoid inconsistencies. Information on where terminated Termination occurred in the ABAP program "SAPLSDNT" - in "DD_PUT_NAMETAB". The main program was "SAPMSGTB ". In the source code you have the termination point in line 71 of the (Include) program "LSDNTU10". |
Thanks for your quick response !!
Shradha
Hi Shradha
During the upgrade time are you getting any dump?
BR
SS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check the status of the table DDXTF in Tx SE11.
If is not active then activate the table
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shradha,
Are you able to check the entries under DDXTF via SE16 transaction.Please share no. of entries if exists under the table .
Kindly check SAP Note 932779 - Unicode conversion - analysis of nametab problems
Regards,
Gaurav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Gaurav,
No. of entries in table are 31 in DDXTF of quality system.
But in Dev system there are no entries and we faced no problem in Dev.
The problem to me looks more related to table structure rather than data.
The note is for Unicode conversion,we are just upgrading ST-PI component.
Thanks
Shradha
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.