inconsisteny db - ddic

[Former Member]

Hi all -

have the following problem on a just upgraded and unicode converted BI system

dump on table

seems that datatype RSRLLINKNO change from NUM2 to NUM4

it did that ok in DDIC, but not on database (MSSQL 2005) - activating through SE14 does not update the table on MSSQL correctly

any ideas how to get the inconsistency between DDIC and DB resolved (without losing any data)

thanks

Paul

[Former Member]

Hi,

I'm also facing the same issue. Let me know, if you could solve this issue.

Thanks in advance.

Regards,

-Pankaj Kapote

[Former Member]

Hi,

hierachy tables like /BI0/KMATERIAL, /BI0/KCUST_SALES, ... are the problem

dump extract:

Runtime Errors DBIF_RSQL_INVALID_REQUEST

Date and Time 13.11.2008 12:10:26

-

---

-

---

Short text

Invalid request.

-

---

-

---

What happened?

The current ABAP/4 program terminated due to

an internal error in the database interface.

-

---

-

---

What can you do?

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

-

---

-

---

Error analysis

An invalid request was made to the SAP database interface in a statement

in which the table "/BI0/KCUST_SALES " was accessed.

-

---

-

---

How to correct the error

Start the work process involved and repeat the action that lead to the

error.

If the error position is in a program that you can change, you can try

to create preliminary solution: Reformulate the database command by

varying the properties such as individual record access instead of

input/output via internal tables, the structure of the selection

conditions (WHERE clause), nested SELECT loops instead of FOR ALL

ENTRIES and other such variations.

Please check the entries in the system log (Transaction SM21).

Check the entries in the developer trace of the work process involved

(transaction ST11).

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"DBIF_RSQL_INVALID_REQUEST" " "

"SAPLRRSI" or "LRRSIF03"

"NEW_NODESID_SAVE"

-

---

-

---

System environment

SAP-Release 700

Application server... "**********"

Network address...... "195.213.49.152"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "*********"

Database type..... "MSSQL"

Database name..... "PBD"

Database user ID.. "pbd"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Jan 24 2008 01:15:15"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 144

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 16759360

Heap.... 0

Page.... 40960

MM Used. 4933744

MM Free. 3443088

-

---

-

---

User and Transaction

Client.............. 410

User................ "*****"

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

Transaction......... "SE38 "

Transactions ID..... "A773B1DDF1E9F1DB8E0D00142208CDB9"

Program............. "SAPLRRSI"

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

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

-

---

-

---

Information on where terminated

Termination occurred in the ABAP program "SAPLRRSI" - in "NEW_NODESID_SAVE".

The main program was "RRINCLTAB_REBUILD ".

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

of the (Include) program "LRRSIF03".

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

302	l_r_tdescr_curr = cl_abap_typedescr=>describe_by_data( <l_s_nodesid_curr> ).
303	l_r_sdescr_curr ?= l_r_tdescr_curr.
304
305	l_r_tdescr = cl_abap_typedescr=>describe_by_data( l_s_nodesid ).
306	l_r_sdescr ?= l_r_tdescr.
307
308	IF l_r_sdescr->components = l_r_sdescr_curr->components.
309	e_ok = rs_c_true.
310	ELSE.
311	e_ok = rs_c_false.
312	ENDIF.
313	ENDFORM. "check_types
314
315	&----
316	*& Form NEW_NODESID_SAVE
317	&----
318	FORM new_nodesid_save USING i_hsitab TYPE rsd_tablnm
319	i_th_nodesid TYPE rrsi_th_nodesid
320	CHANGING e_th_nodesid_err TYPE rrsi_th_nodesid.
321	Achtung: mit DB_COMMIT
322	DATA: l_s_nodesid TYPE rrsi_s_nodesid,
323	l_s_nodesid_o TYPE rsdmhsitab, " old structure of k-tab
324	l_ok TYPE rs_bool.
325	PERFORM check_types USING i_hsitab
326	CHANGING l_ok.
327	LOOP AT i_th_nodesid INTO l_s_nodesid.
328	IF l_ok = rs_c_true.
329	INSERT INTO (i_hsitab) VALUES l_s_nodesid.
330	ELSE.
331	MOVE-CORRESPONDING l_s_nodesid TO l_s_nodesid_o.
>>>>>	INSERT INTO (i_hsitab) VALUES l_s_nodesid_o.
333	ENDIF.
334	IF sy-subrc NE 0.
335	ein anderer Prozess hat fuer diesen Eintrag schon eine andere
336	SID vergeben
337	INSERT l_s_nodesid INTO TABLE e_th_nodesid_err.
338	ENDIF.
339	ENDLOOP.
340	CALL FUNCTION 'DB_COMMIT'.
341	ENDFORM. " NEW_NODESID_SAVE
342
343
344	&----
345	*& Form NODESIDS_CORRECT
346	&----
347	FORM nodesids_correct USING i_th_nodesid_err TYPE rrsi_th_nodesid
348	i_hsitab TYPE rsd_tablnm
349	CHANGING c_th_nodesid TYPE rrsi_th_nodesid.
350	DATA: l_th_nodesid_cor TYPE rrsi_th_nodesid,
351	l_s_nodesid_cor TYPE rrsi_s_nodesid.

-

---

[Former Member]

Hi,

yes, I came across those notes but unfortunately we're on BI 7.0 SR3 (SP14) - so these notes do not apply

guess we'll have to go to SAP support for this

regards

Paul

[Former Member]

Hi,

On which table you get dump? provide dump log

regards,

kaushal

[Former Member]

please check notes 707715, 929259

[Former Member]

like I said, SE14 activation does not work

it does not give an error or anything, but the incosistency stays

[Former Member]

No, no need for that, MSSQL 2005 SP2 running...

[clas_hortien]

Hi,

you can use the database utility for that. Open the table in se11 and choose tools->database utility (the path might be a little different). There you can activate the table with saving the data.

Regards

Clas

[Former Member]

did you also upgrade the SQL SERVER?