SPAM Error: IMPORT_PROPER TP_STEP_FAILURE

SPAM Error:

During the Patch upgrade Error.

IMPORT_PROPER TP_STEP_FAILURE, Return code : 0008

Solution:

A tp step could not be executed. You can find the details log from /usr/sap/trans/log (DIR_TRANS).

Find the below log.

tp  P<YY><MM><DD>.<SID>

1. Go to OS directory and find the appropriate log file. and open the log file

more P200610.SID

2WETP000 17:15:00: Retcode 1: error in DDL statement for "xxxx " - repeat

2EETP345 17:30:00: Retcode 1: SQL-error "959-ORA-00959: 

tablespace 'xxxx' does not exist" in DDL

2EETP334 18:24:00: error in DDL, nametab for "xxxx" not activated

2. The error is stated that,

SQL-error "959-ORA-00959: tablespace 'xxxx' does not exist"

3. Increase the tablespace size and then repeat upgrade.

 

What is SAP Buffer?

SAP Buffer?

             

             Each SAP instance (application server) has its own buffers. These buffers are also known as client caches because they are implemented on the client, that is, the application server. SAP buffers occupy memory areas that are local to the work process, and in individual shared memory segments that can be accessed by all work processes. These memory areas are executed for the application server.

      SAP Buffer stores frequently accessed business objects and data.When a new set of data is requested by a work process, it is not only fetched from the database and provided to the work process but also stored in the SAP Buffer so that the next time when the same set of data is requested, it is provided from the buffer itself, reducing database access thus reducing the load on the database server and network traffic, thereby improving overall system performance.If the required information is not available in the buffer, it must be paged into the buffer before it can be used, resulting in slower performance.If the SAP Buffer is too small, it cannot hold all of the required information. This shortage of space results in the information being swapped out of the buffers. If the SAP Buffer is too large, the native operating system will start paging because too much memory is taken away and given to SAP, database, or other applications. 

SAP buffers

1. Program Buffer
2. Generic Buffer
3. Screen Buffer
4. Roll Area

Program Buffer:

      This buffer occupies a whole shared memory segment.This buffer occupies a whole shared memory segment.

Generic Buffer & Screen Buffer:

    These buffers are held in a shared memory pool. All work processes can access this pool.

Roll Area:

   Local work process buffers. Only one work process can access these buffers at a time.

    

       

SAP Memory allocation

SAP Memory Allocation.

Here how SAP memory allocation for Work Process.

1. User submits the request.

2. Dispatcher assigns the WP.

3. WP requires memory to Roll-In the user context.

4. WP gets memory from local memory which is defined in the parameter ztta/roll_area. It gets

only a part of it which is defined by parameter ztta/roll_first (20KB).

5. If the allocated memory is not sufficient then it gets allocated from extended memory

ztta/roll_extension.

6. If that is also not sufficient then it uses the remaining ROLL Area.

7. If the Roll Area is also not sufficient then it uses Heap/Private memory and the WP goes into

PRIV (PRIVATE) mode.

8. Heap memory is defined by the parameter 

What is mean by SID in SAP?

SID

        Each R/3 installation (SAP system) of a database server and several app servers running the application logic is uniquely identified by a single SID (SAP System Identification), SAP system name or SAP SID can be of maximum 3 alphanumeric characters and its first character must be an alphabet such as D11,SDK, K56, etc.

There some Reserved SIDs in SAP We unable use this SIDs.

No.	SID	Status	Description
1	ADD	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
2	ADM	Prevented by SWPM.	SQL keyword, when used as SAPSID queries could break.
3	ALL	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
4	AMD	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID.
5	AND	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
6	ANY	Prevented by SWPM. Listed as reserved since SAP NetWeaver 7.0 SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
7	ARE	Prevented by SWPM. Listed as reserved since 4.6C SR2.	ODBC reserved keyword, when used as SAPSID queries could break.
8	ASC	Prevented by SWPM. Listed as reserved since SAP NetWeaver 7.0 SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
9	AUX	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'AUX' is the Windows Pseudofile for Auxilary Device.
10	AVG	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID queries could break.
11	BIN	Prevented by SWPM SP06 and later. Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 or lower with problems to distinguish between 'bin' and 'BIN' on Windows and i5.
12	BIT	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
13	CDC	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Reserved keyword on MS SQL Server, can lead to data loss when used as SAPSID or DBSID.
14	COM	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. 'COM' is the Windows Pseudofile for a communication port.
15	CON	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'CON' is the Windows Pseudofile for Console input/output.

16	DAA	Prevented by SWPM 1.0 SP06 and later, for non Diagnostics Agent installations. Used by SAP Solution Manager Diagnostics Agent	In case 'DAA' is already used, the values 'DA1' … 'DA9' are tried and offered in the installer UI when installing an SAP Solution Manager Diagnostics Agent.
17	DBA	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
18	DBM	Prevented by SWPM for DB2 for Windows and Unix.	Cannot be used as DBSID.
19	DBO	Prevented by SWPM. Listed as reserved since SWPM 1.0 SP6.	Reserved keyword/schema on SQL Server, when used as SAPSID or DBSID queries could break.
20	DTD	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server Java. Requested by SUM 1.0 for Application server Java with problems to distinguish between 'dtd' and 'DTD' on Windows and i5.
21	END	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved SQL keyword, when used as SAPSID or DBSID queries could break.
22	EPS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
23	EXE	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 or lower with problems to distinguish between 'exe' and 'EXE' on Windows and i5.
24	FOR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
25	GET	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID.
26	GID	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
27	IBM	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
28	INT	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
29	KEY	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
30	LOG	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'log' and 'LOG' on Windows and i5.
31	LPT	Prevented by SWPM. Listed as	Cannot be used as SAPSID or DBSID.

 

		reserved since ERP 6.0 EHP5.	'LPT' is the Windows Pseudofile for a parallel printer port.
32	LIB	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'lib' and 'LIB' on Windows and i5.
33	MAP	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
34	MAX	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. SQL Server function.
35	MEM	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 with problems to distinguish between 'mem' and 'MEM' on Windows and i5.
36	MIG	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'mig' and 'MIG' on Windows and i5.
37	MIN	Prevented by SWPM.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
38	MON	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
39	NIX	Prevented by SWPM, Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Reserved for internal ABAP transport tools (tp) related to cofiles read error
40	NOT	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
41	NUL	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'NUL' is the Windows Pseudofile for NULL device.
42	OFF	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
43	OLD	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
44	OMS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
45	OUT	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. Reserved future keyword, when used as SAPSID queries could break in future.

 

46	PAD	Prevented by SWPM for MSSQL. Listed as reserved since ERP 6.0 EHP5.	MS SQL Server reserved keyword, when used as SAPSID or DBSID queries could break
47	PRN	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Cannot be used as SAPSID or DBSID. 'PRN' is the Windows Pseudofile for Printer output.
48	RAW	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
49	REF	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
50	ROW	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Reserved future keyword, when used as SAPSID or DBSID queries could break in future.
51	SAP	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID. Requested from ABAP transport tools (tp) related to anonymization. Furthermore sapadm (<sid>adm) is the operating system owner of the SAP Hostagent executables.
52	SET	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SQL keyword, when used as SAPSID or DBSID queries could break.
53	SGA	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
54	SHG	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
55	SID	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
56	SQL	Prevented by SWPM. Listed as reserved since 4.6C SR2.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
57	SUM	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	ODBC reserved keyword, when used as SAPSID or DBSID queries could break.
58	SYS	Prevented by SWPM. Listed as reserved since 4.6C SR2.	SAP internal identifier. Cannot be used as SAPSID or DBSID.
59	TMP	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as SAPSID or DBSID.
60	TOP	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	SQL keyword, when used as SAPSID or DBSID queries could break.
61	TRC	Prevented by SWPM SP06 and later Listed as reserved by SUM on i5 and Windows.	Should not be used for SAP application server ABAP or Java. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'trc' and 'TRC' on Windows and i5.
62	UID	Prevented by SWPM. Listed as	Cannot be used as SAPSID or DBSID.

 

		reserved since 4.6C SR2.	Should not be used for SAP application server ABAP or Java.
63	USE	Prevented by SWPM. Listed as reserved since ERP 6.0 EHP5.	MS SQL Server reserved keyword, when used as SAPSID or DBSID queries could break
64	USR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Cannot be used as DBSID.
65	VAR	Prevented by SWPM. Listed as reserved since 4.6C SR2.	Should not be used as SAPSID for SAP application server ABAP. Requested by SUM 1.0 SP9 and lower with problems to distinguish between 'var' and 'VAR' on Windows and i5.