Support Packs

[#1]

Hi there guys.

I am busy on a project for upgrade our Dev R3 SAP System from Support Pack 14 to !9.

We have had a few problems and have come around them like long running Support Packs running upto 4 and a half hours which i have never before, anyway need some help now.

I am importing SAPK60013INISH Package and i have run into a TP_STEP_FAILURE Errors code 008.

I have picke dup a few things on SDN but they have not helped and we are running DB2 version 9.1 Fix pack 7 and Aix 5.3 on SAP R3.

I have an Error log file for you to see and maybe help me out with this problem.

The file is form /usr/sap/trans/log

I have noticed from the log fiel that the Support Pack is trying to update tables GFD#POOLI and GFD#POOLD but these tabes are 4k talbes and what i found on the internet it says that there is no space and believe me there is space in the Table and at OS Leve as well. Min of 5gig and max of 12gig.

I have added the log file below, can you please help me get over this TP_STEP_FAILURE.

I would like to complete my Support Packs as I am about 85% complete until i hit this problem.

Thanks guys.

Sorry could not get the log file on here as my message has gone over the 15000 charters

Edited by: vicstash on Sep 5, 2009 4:42 PM

[Former Member]

Hi there guys. i have sortted out the problem with making a call to SAP very high and giving them a call every few hours to get passed this error as it was holding the project up. We had to get the ABAP Developers to sort out some programs and stop a few that were running when the Support Pack was updating in se18 and se19 BADi programs.

[Former Member]

Hi Vicstash,

I got the same error when i upgade one of my system.At that time, what i remember is that i run the below mention query

update <SID>.[TATAF~]

set PRTEXT = ' '

where PRTEXT like '%WITH ( ONLINE=OFF )%';

update <SID>.[TATAF~]

set PRTEXT = ' '

where PRTEXT like '%WITH ( FILLFACTOR=%)%';

Since my database is SQL Server 2000 so i run these query in MS SQL Server Query Analyzer (or SQL Server Management Studio).When i run these it shows me that numbers of rows are affected.After that when i run the update process it working fine.I got the same error several times & each time i run the same query & get ride of this error.

Thanks,

Rafikul

[Former Member]

Hii there guys.

Thank you for the information i have the Database guys working on it now and we can try this in DB2 as well just change the Query a bit to fit DB2, but thanks and i will update you if i get around this.

Cheers

[Former Member]

Hi there guys. We can not use that SQL commands will not work in DB2. Anway i chane the table names and created a new table same name but 16k size and then the Support Pack started working anf the main import started going through anf the log files where getting updated. Until the last bit of the Support Pack when it compiles and finishes off i got another error and it ended with

XPRA_EXECUTION

This phase executes the XPRAs and after-import methods. This phase may terminate for the following reasons:

¡ TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡ TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡ TP_STEP_FAILURE: The tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, see the method execution log. To view the cause of the error in the log, choose Goto ® Log ® Queue.

¡ CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, see the SLOG log file.

¡ CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, see the SLOG log file.

So i have tried all of this and we are not moving anf then i called SAP South Africa to get the call moved up as we do not have a Development SAP System now and there are over 250 users not working now and we have development that needs to get into Production by Friday but i have about 50 Support Packs to complete before the guys can start testing and then move onto developing on the Dev SAP system again. The Errors log say that the transport SAPK60013INISH is imported sucessfully and return code 0

Please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Edited by: vicstash on Sep 7, 2009 9:19 PM

[Former Member]

pls check this link

http://help.sap.com/saphelp_47x200/helpdata/en/7e/c6c2ad98a711d2b429006094b9ea64/content.htm

[Former Member]

Hi there guys.

i know this link and i have had a look at the logs and that is y i added the log to the call to see if you guys are able to help.

The log tells me that the Support Pack is having a problem updating the POOLI and POOLD tables and indexes and theses tales are a 4k size.

I would like to know is there a way out to stop the import or change the SQL script of the Support Pack if there is a way to do that.

Or

Do i use DB6CONV and more the tables out of the 4k table in to a 32k table and that is going to take forever i might as well trash the server and go back to a off-line back.

So is there anyone out there that has had this problem and came around it.

Thanks.

[Former Member]

Hi,

Please have look at the following note number 1147174 and 1099936 this seems to be a standard bug in the SAP support package.

And for your reference please look into following links...

http://bytes.com/topic/db2/answers/515228-sql0670n-creating-table-250-columns

http://www-01.ibm.com/support/docview.wss?uid=swg21345595

Thanks & Regards,

Balaji.S

[Former Member]

Without log file we can't help you. Please provide the few line from last or the error message only from the log files.

I assume your Kenrel and Spam are updated before you started the supoort packs

Regards,

Subhash

[Former Member]

Hi there and yes all updated before i started. Spam on 35 and the Kernel on all our SAP Systems are run 201.

Log file information that you need.

3 ETP399 IN "GFP#POOLD"

3 ETP399 INDEX IN "GFP#POOLI"

3 ETP399 LONG IN "GFP#POOLD"

3 ETP399

2WETP000 11:47:58: Retcode 1: error in DDL statement for "N2TRANSPORTBCSET " - repeat

2EETP345 11:48:10: Retcode 1: SQL-error "-670-SQL0670N The row length of the table exceeded a limi

2EETP345 t of "4005" bytes. (Table space "GFP#POOLD".) SQLSTATE=54010" in DDL statement for "N2TR

2EETP345 ANSPORTBCSET "

2 ETP399 -

---

DB-ROLLBACK() -

---

2EETP334 11:48:10: error in DDL, nametab for "N2TRANSPORTBCSET" not activated

2 ETP301 -

---

3 ETP361 "0" Shadow-Nametabs activated, DDL executed

2 ETP362 "1" Shadow-Nametab activations failed

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/09/05 11:47:58")

2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/09/05 11:48:10")

2 ETP301 -

---

2 ETP301 -

---

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/09/05 11:48:10")

2 ETP301 -

---

2 ETP399 processing modeflag 'V'

2 ETP301 -

---

2 ETP330XActivation of Shadownametabs with DDL

2 ETP301 -

---

2 ETP301 -

---

3 ETP361 "0" Shadow-Nametabs activated, DDL executed

3 ETP362 "0" Shadow-Nametab activations failed

2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/09/05 11:48:10")

2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/09/05 11:48:10")

2 ETP301 -

---

1 ETP172 MOVE OF NAMETABS

1 ETP110 end date and time : "20090905114811"

1 ETP111 exit code : "8"

1 ETP199 ######################################