Error "602" System error: AK Datapart too short

Question

Hi all,
Ok, I have looked just about everywhere for an answer to this but to no avail...I even tried under a few rocks we have laying around.
Anyway here it is:
While running a compression in BW we get Error "602"  System error: AK Datapart too short.
This is happening while doing a select statement during the compression of the infocube.  It does not happen all the time, just kind like when ever it feels like.  The only note I could find in OSS was one about Live Cache and it does not seem to apply.
Here is the dump which I really hate doing this, but it gives all the info needed :
untime Error          DBIF_DSQL2_SQL_ERROR
Except.                CX_SY_NATIVE_SQL_ERROR
Date and Time          08/15/2007 12:23:09
ShrtText
An SQL error occurred when executing Native SQL.
What happened?
Error "-602" occurred in the current database connection "DEFAULT".
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
How to correct the error
Database error text........: "System error: AK Datapart too short"
Database error code .......: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/EZPSD_C03" ( "KEY_ZPSD_C03P",
"KEY_ZPSD_C03T", "KEY_ZPSD_C03U", "KEY_ZPSD_C031", "KEY_ZPSD_C032",
"KEY_ZPSD_C033", "KEY_ZPSD_C034", "/BIC/ZNET_ASP" ) SELECT ? ,
F."KEY_ZPSD_C03T", F."KEY_ZPSD_C03U", F."KEY_ZPSD_C031", F."KEY_ZPSD_C032","
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,
use the following search criteria:
"DBIF_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"GP31VIZWJDTT90894L1IA5YAC7G" or "GP31VIZWJDTT90894L1IA5YAC7G"
"TRANSFER_ALL"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"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, select the Editor function "Further Utilities->
Upload/Download->Download".
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 the procedure
"TRANSFER_ALL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "sdcbw03"
Network address.......... "10.64.18.76"
Operating system......... "Linux"
Release.................. "2.6.9-55.ELsmp"
Hardware type............ "x86_64"
Character length......... 16 Bits
Pointer length........... 64 Bits
Work process number...... 21
Short dump setting....... "full"
Database server.......... "sdcbw03"
Database type............ "ADABAS D"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "C"
SAP kernel............... "640"
Created on............... "Nov 5 2006 19:46:34"
Created in............... "Linux GNU SLES-9 x86_64 cc3.3.3"
Database version......... "SAPDB 7.5.0.030 "
Patch level.............. "156"
Patch text............... " "
Supported environment....
Database................. "MaxDB 7.5.0"
SAP database version..... "640"
Operating system......... "Linux 2.6"
Memory usage.............
Roll..................... 16192
EM....................... 20949280
Heap..................... 0
Page..................... 24576
MM Used.................. 9235016
MM Free.................. 3331560
SAP Release.............. "640"
User and Transaction
Client.............. 011
User................ "ALEREMOTE"
Language key........ "E"
Transaction......... " "
Program............. "GP31VIZWJDTT90894L1IA5YAC7G"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "GP31VIZWJDTT90894L1IA5YAC7G" in
"TRANSFER_ALL".
The main program was "RSPROCESS ".
The termination occurred in line 573 of the source code of the (Include)
program "GP31VIZWJDTT90894L1IA5YAC7G"
of the source code of program "GP31VIZWJDTT90894L1IA5YAC7G" (when calling the
editor 5730).
The program "GP31VIZWJDTT90894L1IA5YAC7G" was started as a background job.
Job name........ "BI_PROCESS_COMPRESS"
Job initiator... "ALEREMOTE"
Job number...... 12185102
Processing was terminated because the exception "CX_SY_NATIVE_SQL_ERROR"
occurred in the
procedure "TRANSFER_ALL" "(FORM)" but was not handled locally, not declared in
the
RAISING clause of the procedure.
The procedure is in the program "GP31VIZWJDTT90894L1IA5YAC7G ". Its source code
starts in line 557
of the (Include) program "GP31VIZWJDTT90894L1IA5YAC7G ".
Source Code Extract
Line
SourceCde
543
ENDIF.
544
545
COMMIT WORK.   " commit and close cursors
546
547
l_str = i_max_requid.
548
PERFORM msg_append(saplrscondense)
549
USING    'S' '355' l_str space space space
550
CHANGING c_t_msg.
551
552
ENDFORM.                               " CONDENSE_FACTTABLE_NEW
553
554
555
     Form  TRANSFER_ALL
556
557
FORM TRANSFER_ALL USING i_ref_update       TYPE rs_bool
558
i_pdimid           TYPE I
559
i_pdimid_ref_point TYPE rsd_sid
560
i_pdimid_normal    TYPE rsd_sid
561
i_recordtp         TYPE rsd_sid
562
CHANGING e_ref_ins_cnt TYPE I
563
e_ins_cnt     TYPE I
564
c_t_msg       TYPE rs_t_msg.
565
566
CALL FUNCTION 'RSDU_INFOCUBE_INDEXES_DROP'
567
EXPORTING
568
I_INFOCUBE = 'ZPSD_C03'
569
I_FACTTAB  = '/BIC/EZPSD_C03'.
570
571
572
EXEC SQL.
>>>>>
INSERT INTO "/BIC/EZPSD_C03"
574
( "KEY_ZPSD_C03P"
575
, "KEY_ZPSD_C03T"
576
, "KEY_ZPSD_C03U"
577
, "KEY_ZPSD_C031"
578
, "KEY_ZPSD_C032"
579
, "KEY_ZPSD_C033"
580
, "KEY_ZPSD_C034"
581
, "/BIC/ZNET_ASP"
582
583
SELECT :i_pdimid_normal
584
, F."KEY_ZPSD_C03T"
585
, F."KEY_ZPSD_C03U"
586
, F."KEY_ZPSD_C031"
587
, F."KEY_ZPSD_C032"
588
, F."KEY_ZPSD_C033"
589
, F."KEY_ZPSD_C034"
590
, SUM( F."/BIC/ZNET_ASP" )
591
FROM "/BIC/FZPSD_C03" F
592
WHERE F."KEY_ZPSD_C03P" = :i_pdimid
Any thoughts would be helpful,
Thanks,
David

Answer 1

This error usually occurs when there is a database lock or no space in teh database. Got DB02 and Click on Space critical objects to see whether any entries are there. If yes contact your basis to increase the space.
Hope this helps
Thanks,
Satish