Error in Support Patch Installation

[Former Member]

Hi Experts,

We are getting below issue while doing Patc hupgrade on PI 7.1 server, if someone has faced the similar issue, please share the resolution-

1. SUpport Patch - KB71008

2. Support Patch hung at IMPORT_PROPER phase

3. Background Job RDDDIS0L being cancelled

4. Job canceled because there is one Runtime error occuring -

Runtime Errors DBIF_DSQL2_SQL_ERROR

Exception CX_SY_NATIVE_SQL_ERROR

5. No processes running in SM50

Please help us out.

Regards,

Sabita

[Former Member]

Hi

Please check the import log and see where exactly is the problem,paste the trans log to analyse

Regards

Uday

[Former Member]

ST22 Dump

Runtime Errors DBIF_DSQL2_SQL_ERROR

Exception CX_SY_NATIVE_SQL_ERROR

Date and Time 29.09.2010 17:13:54

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_NATIVE_SQL_ERROR', was not

caught in

procedure "TABSTORAGE_DBS_GET" "(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:

In a SELECT or FETCH command, the INTO clause contains more

variables than the SELECT list fields.

How to correct the error

Database error text........: "ORA-01007: variable not in select list"

Error code of database.....: 1007

Triggering SQL statement...: "FETCH NEXT "

Internal call code.........: "[DBDS/NEW DSQL]"

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_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"

"SDB2FORA" bzw. "SDB2FORA"

"TABSTORAGE_DBS_GET"

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.

User and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Transaction ID...... "4CA2ECE6D7F23AA8E1000000AC1F723F"

Program............. "SDB2FORA"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

Debugger Active..... "none"

Information on where terminated

Termination occurred in the ABAP program "SDB2FORA" - in "TABSTORAGE_DBS_GET".

The main program was "RDDDISTY ".

In the source code you have the termination point in line 1444

of the (Include) program "SDB2FORA".

The program "SDB2FORA" was started as a background job.

Job Name....... "RDDDIS0L"

Job Initiator.. "DDIC"

Job Number..... 17135400

The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred

in

procedure "TABSTORAGE_DBS_GET" "(FORM)", but it was neither handled locally nor

declared

in the RAISING clause of its signature.

The procedure is in program "SDB2FORA "; its source code begins in line

1403 of the (Include program "SDB2FORA ".

Trans Log SLOG-

Final Log-

1 ED0306 "Statistics on Activated and Deleted Objects"

1 ED0301 *************************************************************************

1 EDO601XNumber of objects to be activated............: "346"

1 EDO605 Objects not activated........................: "0"

1 EDO606 Activated objects with errors in dependencies: "0"

1 EDO604 Objects activated with warning...............: "34"

1 EDO603 Successfully activated objects...............: "312"

1 EDO602 Number of objects to be deleted..............: "20"

1 EDO608 Objects not successfully deleted.............: "0"

1 EDO607 Successfully deleted objects.................: "20"

1 EDO609 Tables/views with DROP/CREATE................: "0"

1 EDO610 No. of them marked for DROP/CREATE: "0"

1 EDO611 Not marked for DROP/CREATE: "0"

1 EDO620 Number of nametabs to be deleted.............: "0"

1 EDO622 Successfully deleted nametabs................: "0"

1 EDO621 Nametabs that were not successfully deleted..: "0"

1 ED0301X*************************************************************************

1 ED0306 "Statistics on Activated and Deleted Objects"

1 ED0322 End phase "003" ***********************************************************

1 ED0302X=========================================================================

1 ED0314 Mass Activation

1 ED0302 =========================================================================

1 ED0327 Process..................: "htlsxiq_14"

1 ED0319 Return code..............: "4"

1 ED0313 Phase 001..................: 00:00:45 (Object Activation)

1 ED0314 Phase 002..................: < 1 sec. (Final log)

1 ED0314 Phase 003..................: < 1 sec. (Statistics on Activated and ...)

1 ED0309 Program runtime..........: "00:00:54"

1 ED0305 Date, time...............: "29.09.2010", "11:53:54"

1 ED0318 Program end==============================================================

1 ETP155 ACTIVATION OF DD-OBJECTS

1 ETP110 end date and time : "20100929115354"

1 ETP111 exit code : "4"

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

The phase IMPORT_PROPER is in hung state and background job beling canceled and Runtime error keep coming.

Regards,

Sabita

[Former Member]

please go through blog /people/lars.breddemann/blog/2010/04/26/ora-01007-in-abap-stack-and-what-to-do-about-it

[Former Member]

Hi,

Looks similar issue, but as stated by Lars, for import issues we must consult SAP.

Also changing in SAP codes by us is not a good idea...

We had alreayd opened a message with SAP. But as trying to resolve the issue, we had reset the queue and tried to import ABAP patch 7 so SAP came with answer that now they cant help after these steps.

We had to finally restore the backup !!

Thanks for your reply ...the blog is really excellent...

Sabita

[ashish_mishra2]

Hi,

DBIF_DSQL2_SQL_ERROR comes because of multiple reasons. Please chek in ST22, Error analysis, that will give you exact error logs.

Also please make sure that you have enough space available in you tablespaces.

Cheers !!!

Ashish Mishra