TABLESPACE ERROR - unable to extend table SAPSR3.DDPRS by 1024 in tablespace PSAPSR3"

Category               ABAP Server Resource Shortage
Runtime Errors         DBIF_RSQL_SQL_ERROR
Except.                CX_SY_OPEN_SQL_DB
Date and Time          06.11.2011 23:34:07
Short text
	SQL error 1653 while accessing table "DDPRS".
What happened?
	Database error text: "ORA-01653: unable to extend table SAPSR3.DDPRS by 1024 in
	tablespace PSAPSR3"
What can you do?
	Please make a note of the actions and input which caused the error.
	-
	To resolve the problem, contact your
	SAP system administrator.
	Using transaction ST22 for ABAP dump analysis you can see and
	administrate termination messages and retain them for longer periods.
	Please make a note of the actions and input which caused the error.
	-
	To resolve the problem, contact your
	SAP system administrator.
	Using transaction ST22 for ABAP dump analysis you can see and
	administrate termination messages and retain them for longer periods.
Error analysis
	An exception occurred that is explained in detail below.
	The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
	in
	procedure "WRITE_TABLE_DDPRS" "(FORM)", nor was it propagated by a RAISING
	clause.
	Since the caller of the procedure could not have anticipated that the
	exception would occur, the current program is terminated.
	The reason for the exception is:
	Database error text: "ORA-01653: unable to extend table SAPSR3.DDPRS by 1024 in
	tablespace PSAPSR3"
How to correct the error
	Internal call code.........: "[RSQL/INSR/DDPRS ]"
	Please check the entries in the system log (Transaction SM21).
	You may able to find an interim solution to the problem
	in the SAP note system. If you have access to the note system yourself,
	please use the following search criteria:
	"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
	"SAPLSLOG" bzw. "LSLOGF05"
	"WRITE_TABLE_DDPRS"
	If you cannot solve the problem yourself, please send the
	following documents to SAP:
	1. A hard copy print describing the problem (short dump).
	To obtain this, select "System->List->Save->Local File (unconverted)"
	on the current screen.
	2. A suitable hardcopy printout of the system log.
	To obtain this, call the system log with Transaction SM21
	and set the time interval to 10 minutes before and 5 minutes after
	the short dump. In the display choose "System->List->Save->
	Local File (unconverted)"
	3. If the programs are your own programs or modified SAP programs,
	supply the source code.
	To do this, choose "More Utilities->Upload/Download->Download" in the
	Editor.
	4. Details regarding the conditions under which the error occurred
	or which actions and input led to the error.
	You may able to find an interim solution to the problem
	in the SAP note system. If you have access to the note system yourself,
	please use the following search criteria:
	"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
	"SAPLSLOG" bzw. "LSLOGF05"
	"WRITE_TABLE_DDPRS"
	If you cannot solve the problem yourself, please send the
	following documents to SAP:
	1. A hard copy print describing the problem (short dump).
	To obtain this, select "System->List->Save->Local File (unconverted)"
	on the current screen.
	2. A suitable hardcopy printout of the system log.
	To obtain this, call the system log with Transaction SM21
	and set the time interval to 10 minutes before and 5 minutes after
	the short dump. In the display choose "System->List->Save->
	Local File (unconverted)"
	3. If the programs are your own programs or modified SAP programs,
	supply the source code.
	To do this, choose "More Utilities->Upload/Download->Download" in the
	Editor.
	4. Details regarding the conditions under which the error occurred
	or which actions and input led to the error.
	The exception must either be prevented, caught within proedure
	"WRITE_TABLE_DDPRS" "(FORM)", or its possible occurrence must be declared in
	the
	RAISING clause of the procedure.
	To prevent the exception, note the following:
System environment
	SAP Release..... 730
	SAP Basis Level. 0000
	Application server... "BOE"
	Network address...... "192.168.10.93"
	Operating system..... "Windows NT"
	Release.............. "6.1"
	Hardware type........ "8x AMD64 Level"
	Character length.... 16 Bits
	Pointer length....... 64 Bits
	Work process number.. 4
	Shortdump setting.... "full"
	Database server... "BOE"
	Database type..... "ORACLE"
	Database name..... "BOE"
	Database user ID.. "SAPSR3"
	Terminal.......... "DAMA-PC"
	Char.set.... "C"
	SAP kernel....... 720
	created (date)... "Oct 20 2010 01:56:25"
	create on........ "NT 5.2 3790 S x86 MS VC++ 14.00"
	Database version. "OCI_10201_SHARE, 10.2.0.4.0 "
	Patch level. 68
	Patch text.. " "
	Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
	SAP database version. 720
	Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
	NT 6.0, Windows NT 6.1"
	Memory consumption
	Roll.... 0
	EM...... 58657088
	Heap.... 0
	Page.... 90112
	MM Used. 47998624
	MM Free. 6463312
User and Transaction
	Client.............. 100
	User................ "HCL4"
	Language key........ "E"
	Transaction......... "RSA1 "
	Transaction ID...... "9CA108E1DA7DF1079B98E61F13AD0907"
	EPP Whole Context ID.... "E61F13AD09071ED1829432A9FA699B98"
	EPP Connection ID....... 00000000000000000000000000000000
	EPP Caller Counter...... 0
	Program............. "SAPLSLOG"
	Screen.............. "SAPLRSD_GUI_IOBJ_MAINT 1200"
	Screen Line......... 31
	Debugger Active..... "none"
Information on where terminated
	Termination occurred in the ABAP program "SAPLSLOG" - in "WRITE_TABLE_DDPRS".
	The main program was "RSAWBN_START ".
	In the source code you have the termination point in line 314
	of the (Include) program "LSLOGF05".
	The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
	procedure "WRITE_TABLE_DDPRS" "(FORM)", but it was neither handled locally nor
	declared
	in the RAISING clause of its signature.
	The procedure is in program "SAPLSLOG "; its source code begins in line
	226 of the (Include program "LSLOGF05 ".

Procedure To Resolve:
Drop the mail to BASIS Consultant.

For me, this is my responsibility in this organization.
Goto the T-Code DB02, check for database overview and segment overview, check the Top Growth monthly. You can find the object taking more tablespace and the usage % here.

Using the BRTools u can increase the tablespace with ease.

Excute brtools at the OS level (command prompt), make sure that u have logged in as ORA<SID> or <SID>adm and proceed as follows

brtools --> 2 - Space management --> 1 = Extend tablespace --> c(ontinue) --> c(ontinue) --> 1 = Extend tablespace --> Select the required tablespace and then proceed accordingly.

You have to ensure that there is enough space available in the disk before u start extending the tablespace. Else the brspace program will fail.