on 10-17-2007 2:13 PM
Hello
When a table on SAP is created with a name > 10 char., the resulting Phys.Filename will be generated by in a special way.
E.g. I create table ZTABLETOOLONG in SE11. The created Physical file will be named something like ZTABL00001.
If I change the layout of the table (e.g. changing primkey) in a way that a table conversion is required, SAP (SE14) will decide to unload/reload the table.
After that operation, the Physical filename is renamed to QCM8Z00001.
Why is the file after the conversion not renamed back to the original name ZTABL00001 ?
Hi Jo,
because SAP is doing urnder the cover lots of things (e.g. rename to QCM<table name>) !
If you prefer, you could rename it back yourself - but that is not necessary the AS/400 name is of no interest ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jo,
as you should use ODBC with long names, it should work ...
why is it different ? don't know ...
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
QCM tables may be temporary copies that SAP (or the underlying DB engine) did not delete.
The same kind of thing can happen with a system copy.
The procedure recommended is the following, in the case where the file is a temp file that wasn't cleaned up. (This is a paraphrase from the SAP System Copy documentation. Check the link for more info: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f022aa7d-0c01-0010-20a5-c247330d47fa">Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP NetWeaver 2004s Document Version 1.20 - March 29, 2006</a>.):
1. Check the following
- The tables must be consistent no restart log or conversion procedure
termination must be displayed
- The data of the original table must be legible
- Application programs that use the affected original table should be verified. If they do not run correctly, do not yet delete the QCM table. Further investigation will be required.
2. Start transaction SE14.
3. Choose Extras → Invalid temp. table
All QCM tables that can be deleted are displayed.
4. Mark the tables and delete them.
If this does not work, you may have to look further.
You may have to open a note with SAP, if the behavior that you describe occures consistently, since the file <u>should</u> be renamed from the QCM name when the file conversion is complete.
Good luck
Brian
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.