Table /BOBF/0BM_B0 Error in SUM Stack Update

[Former Member]

I am applying a stack update from ERP60/EHP7 stack 2 to stack 5 using SUM and getting the following error in phase, MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSUMOD10_SPAU_SHD

Last error code set: Batchjob 'RSUMOD10' with id '18304700' aborted

The job log refers to an ABAP dump which has the error:

DBSQL_SQL_ERROR, SQL error 208 while accessing table /BOBF/0BM_B0  invalid object name

The system log shows it is actually attempting to access a table named /BOBF/OBM_R/3 which does not exist in the ABAP dictionary.  Running SE16 on table /BOBF/0BM_B0  to show the contents results in an ABAP dump, DBSQL_TABLE_UNKNOWN, yet the table shows consistent and exists using SE11/SE14.  I have created a problem ticket with SAP but just thought I would check to see if anyone has come across this.

Thanks,

Doug

[Former Member · Accepted solution]

SAP has replied that this is a known error in this version of the SUM tool, 1.0 SP12, version 1.0 and should be fixed in the next available patch for SP12.  

  Thanks, 

  Doug 

[Former Member · Accepted solution]

Hi Doug,

I have the same issue during my upgrade from EHP6 for ECC6 U to EHP7 for ECC7 on NW7.40 and i use SUM tool: 1.0 SP12 patch level 2!!

SAP alse replied that will be fixed in the next patch 3.

So, has you fixed you issue with patch Level 2? if yes, how?

Thanks

[Former Member · Accepted solution]

Hi Lhoussain,

We also tried again with patch 2 last week and hit the error again, SAP had to modify the SUM tool directly on our system, we are putting pressure on them to get patch 3 ASAP since we have more systems to update but they have not committed to a date yet.  Sorry I could not give better news.

Regards,

Doug

[Former Member · Accepted solution]

Hi Lhoussain,

SUM12 patch level 3 is now available on SAPNET but I will not be doing another stack update for at least a week with this patch level.

Regards,

Doug

[Former Member · Accepted solution]

Hi Doug,

I started the upgrade with SUM SP12 patch 3 sonce monday.

i'm not in phase where j have the issue, but il will do a feedback about it.

regards,

Lhoussain

[maurizio_dautilia]

Hi

Here the solution from SAP:

SAP provide us with a transport with the correct version of program rsumod10, which we had to import directly into shadow instance: SAPup importshd LMXK005159

The only other solution is to donwload the SUM 1.0 SP13 and start the upgrade again.

This is the explanation from SAP-Dev to this issue wiht SUM 1.0 SP12 Patchlevel 12:

We had a similar issue a while back but missed to check if the issue

can occur in updates from older start releases as well.

The reason for this issue is, that the program invoked was previously

part of the SAP_BASIS delivery and was moved to SUM. When the report

was changed to support new SUM functionality it was missed to check if

older SAP_BASIS packages can corrupt the SUM tool delivery.

If you want to complete the update in your landscape with this SUM

version, please perform the following steps:

- (1) finish the update of this system

- (2) create in this system a transport of copies containing R3TR PROG

RSUMOD10, and export this transport

- (3) use the transport created in (2) and include this as single

change request into all further updates of the system landscape using

this SUM version.

Regards

[jonasmeyer1]

I am the colleague of Maurizio, we were in charge of the productive upgrade of our "Promotion Management for Retail" System last weekend, going from NW 7.02 to NW 7.40, using SUM SP12 Patch 12.

After having those problems in Preprocessing (mentioned above), again the following error occured in downtime phase MAIN_NEWBAS/TABIM_UPG:

sql error 904 performing SEL on table /BOBF/OBM_BO

ORA-00904: "CUSTOMER_BO": invalid identifier

We could only finish Downtime after manually inserting the field into the table with the SQL-command that we found in the relevant log file of QAS system, where this error never appeared, SAPI-731BWINSAPBSFND.QA1:

ALTER TABLE "/BOBF/OBM_BO" ADD CUSTOMER_BO VARCHAR2(3) DEFAULT ' ' NOT

NULL ENABLE;

Comparing the log files including ALTER TABLE statements from QA1 and PA1, the major difference was, that this ALTER TABLE for inserting the field CUSTOMER_BO never happened in production!

Through SAP Support we got this statement from a Head of Development SAP:

"At this moment in the upgrade, there is no other option than taking manual action in your database. Nevertheless, there is no guarantee of successfully finishing the phase or the upgrade with no further related errors."

In our case, no other errors occured and we could finish downtime successfully.

[jonasmeyer1]

just to clarify: all we did in productive upgrade was a workaround, because there was no time to reset the procedure. According to SAP, this error won't happen with SUM 1.0 SP13...

[maurizio_dautilia]

Hallo

We have the same issue using SUM 1.0 SP12 Patch 12.

What was the solution in your case?

regards,

Maurizio

[Former Member]

Hi,

The SAP's response was:

"I checked with the development team regarding the issue and it seems

that the issue will be resolved in Patch 3 of SUM SP12.

It is still not released in the service market place yet, but should

be available in some days.

Thanks & Regards,"

The patch level 3 of SUM 1.0 SP12 (released 9th January) was good to finish the upgrade.

File name:SUM10SP12_3-20006681.SAR, but i suggest that you use the latest release.

Regards

[maurizio_dautilia]

Hallo

Thanks for your answer.

We are in the phase MAIN_SHDIMP/SUBMOD_SHD2_RUN/RUN_RSUMOD10_SPAU_SHD.

What would it mean to reset the upgrade at this moment?

or is it possible to replace the SUM-executables and continue this phase?

Regards

[Former Member]

Hi,

Yes! you have to reset the upgrade! no choice!

Good luck!

Regards,

[Former Member]

Hi,

SAP had to provide a quick fix for us but we eventually used SUM 1.0 SP12 patch 5, which resolved the issue, if you are using patch 12 and still got this error, maybe it is a different issue.

Regards,

Doug

[Reagan]

>>The system log shows it is actually attempting to access a table named /BOBF/OBM_R/3 which does not exist in the ABAP dictionary.<<

In such a case use function module DD_NAMETAB_DELETE to correct it.

If the table is present at the DB level and is empty then drop the table.

Cheers

RB

[Former Member]

Thanks RB, I did check the DDNTT and DDNTF tables first, expecting not to find an entry in DDNTF but there was an entry in both per the below, so does running DD_NAMETAB_DELETE still apply?

Regards,

Doug

[srinivasan_vinayagam]

Hi Doug,

Check table whether activated or not in SE16, if not activate.

Regards,

V Srinivasan

[Former Member]

Hi,

Yes, it already shows as active in SE11 and just for good measure I did an activate and adjust in SE14 using the option to save data but I still get the error when trying to view in SE16.

Regards,

Doiug

[srinivasan_vinayagam]

Hi Doug,

Go to Transaction SE38 and run this report 'RSUMOD10.

and also check in SPDD transaction

Regards,

V Srinivasan

[Former Member]

RSUMOD10 runs quickly with no output and a re-run of the SUM phase results in the same error/dump.

Regards,

Doug

[srinivasan_vinayagam]

Hi Doug,

share the SUM log files or error screen.

Regards,

V Srinivasan

[Former Member]

Below is the error in the AMODSPAU log but not very helpful, I've also included an extract from the dump file, job log and system log entries below.

Regards,

Doug

AMODSPAU:

34 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ010 Date & Time: 20141215152416 

2 ETQ373 parameter "JOBSTATUS" = "A"

2 ETQ374 parameter "RC_CHECK" = "0"

2 ETQ373 parameter "JOBENDDATE" = "20141215"

2 ETQ373 parameter "JOBENDTIME" = "152353"

2EETQ262 Batchjob "RSUMOD10" aborted

1EETQ399 Last error code set is: Batchjob 'RSUMOD10' with id '15234600' aborted

1EETQ204 Upgrade phase "RUN_RSUMOD10_SPAU_SHD" aborted with severe errors ("20141215152416")

RSUMOD10 job log:

Job started

Step 001 started (program RSUMOD10, variant SAP_UPG_SPAU, user ID DDIC)

Internal session terminated with a runtime error DBSQL_TABLE_UNKNOWN (see ST22)

Job cancelled

System log entries:

Table /BOBF/OBM_R/3 does not exist on the database with ID dbdbslst

Runtime error "DBSQL_TABLE_UNKNOWN" occurred.

> Short dump "141215 152353 DEEH11EAY1016_DN1_41 DDIC" created.

Transaction Canceled 00 671 ( DBSQL_TABLE_UNKNOWN 20141215152353DEEH11EAY1016_DN1_41 DDIC 000 )

Dump Extract:

Category	Installation Errors
Runtime Errors	DBSQL_SQL_ERROR
Date and Time	14.12.2014 18:31:27

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Short Text	|
|	SQL error 208 occurred while accessing table "/BOBF/OBM_BO".	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What happened?	|
|	Database error text: "Invalid object name '/BOBF/OBM_BO'."	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|What can you do?	|
|	Note which actions and entries caused the error to occur.	|
|	|
|	Consult your SAP administrator.	|
|	|
|	Using transaction ST22 for ABAP dump analysis, you can view, manage,	|
|	and retain termination messages for longer periods.	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Error analysis	|
|	Database error text: Invalid object name '/BOBF/OBM_BO'.	|
|	Return value of the database layer: 103	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|User and Transaction	|
|	Client................. 000	|
|	User.................. DDIC	|
|	Language key.......... E	|
|	Transaction.........	|
|	Transaction ID...... 51BF83E4F1DAF1C0B50000505600317A	|
|	|
|	EPP whole context ID...... 34383731334245353438373133424535	|
|	EPP connection ID........ 00000000000000000000000000000000	|
|	EPP call counter......... 0	|
|	|
|	Program.............. /BOBF/CL_CONF_VERSION_ADAPTER=CP	|
|	Screen.............. SAPMSSY0	1000	|
|	Screen line.......... 6	|
|	Active debugger..... "none"	|

----------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------

|Information on where terminated	|
|	The termination occurred in ABAP program "/BOBF/CL_CONF_VERSION_ADAPTER=CP",	|
|	in "GET_OBJECT_HEADER_FROM_REPO". The main program	|
|	was "RSUMOD10".	|
|	|
|	In the source code, the termination point is in line 21 of (Include)	|
|	program "/BOBF/CL_CONF_VERSION_ADAPTER=CM003".	|
|	Program "/BOBF/CL_CONF_VERSION_ADAPTER=CP" was started as a background job.	|
|	|
|	Job name....... RSUMOD10	|
|	Job initiator.. DDIC	|
|	Job number...... 18304700	|

[srinivasan_vinayagam]

Hi Doug,

You can try to run this job with client 000 and DDIC user.

Regards,

V Srinivasan

[srinivasan_vinayagam]

Hi Doug,

The execute the report TOUCHTAB in SE38 transaction and give /BOBF/0BM_B0

Regards,

V Srinivasan

[Former Member]

No joy, TOUCHTAB runs quickly with no output and a repeat of the phase results in the same error.  Everything has been run in client 000, user DDIC since this is on the shadow system.

Regards,

Doug