DB13 - RAISE_EXCEPTION

Question

Hi,
I've just finished upgrading the MaxDB 7.5 build 32 to MaxDB 7.8.01 build
19.
I've already followed the prerequisite of upgrading MaxDB which
includes switching the SAP kernel from 640 to 640_EX2, apply SAP note
1002641, 916795.
After database upgrade, the MaxDB database and SAP started successfully.
But, when I executed transaction DB13 I received runtime
error RAISE_EXCEPTION - Exception condition "TABLE_NOT_FOUND" raised.
Quotation from the error:
============================================================
Runtime Errors         RAISE_EXCEPTION
       Occurred on     24.01.2011 at 12:47:31
Exception condition "TABLE_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
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.
Error analysis
A RAISE statement in the program "SAPLSADB" raised the exception
condition "TABLE_NOT_FOUND".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
How to correct 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,
use the following search criteria:
"RAISE_EXCEPTION" C
"SAPLSADB" or "LSADBU35"
"SEL_EXTENDED_VERSION_SDB"
or
"SAPLSADB" "TABLE_NOT_FOUND"
or
"RSSDBADM " "TABLE_NOT_FOUND"
============================================================
I found the following SAP Notes 794512, 1510231, 382312 but they
all couldn't be implemented in the system.
Would you please let me know if there is any workaround than patching
SAP_BASIS. Currently SAP_BASIS SP is SAPKB62034.
Regards,
Fausto

Answer 1

Hello Fausto,
From the mentioned notes:
Note 794512
The problem is eliminated with the following Basis Support Packages:
6.20 SP47
Note 1510231
o  6.20: Import SAP_BASIS Support Package 70. Alternatively, if you are using Support Packages 67 to 69, you can implement the corrections contained in this note.
Note 382312
SAP WebAS Basis 6.20
SAP MaxDB Version 7.8:
The adjustments are provided in Basis Support Package 67. For DB13, refer to Note 1510231.
The solution to your case will be to implement SAP_BASIS SP70.
Regards,
Eduardo Rezende