"H�bschen, Peter" wrote:
> 
> Hello, 
> 
> I've executed 'Select case when exists (SELECT 
> lfd_Rueckfragenummer FROM
> tbl_StaffelRueckm WHERE Lfd_Rueckfragenummer = <integer>) 
> Then 1 Else -5678
> End from tbl_Staffelrueckm' on my database in SQL Studio 
> (7.4.3.28) with a
> Sapdb 7.4.3.25 on a Redhat 9 Box and afterwards I got 
> "General error: -9210
> POS(1) System error: KB Stack op illegal". In the 
> documentation I found that
> I should make a call at the Local Support (I'm doing this 
> with this E-Mail
> right now ;-)) and I should attach a trace of my last 
> database activities.
> But I don't know what is meant by this. So which files should 
> I attach? Can
> I attach files or get they stripped of by the Mailinglistsystem?

Please do the following steps:
0 start SqlStudio
1 Start the trace: dbmcli -d <dbname> -u <dbm,dbm> util_execute diagnose vtrace 
default select on 
2 Execute your SQL 
3 Flush the trace: dbmcli -d <dbname> -u <dbm,dbm> sql_execute vtrace 
4 Create the text representation: dbmcli -d <dbname> -u <dbm,dbm> trace_prot akbm 
5 Copy the text representation to a local file: dbmgetf -d <dbname> -u <dbm,dbm> -k 
KNLTRCPRT -f <local file name> 
6 Stop writing of the trace: dbmcli -d <dbname> -u <dbm,dbm> util_execute diagnose 
vtrace default select off. 

Be sure to do this after you found the problem. Writing the VTrace will degrade the 
performance. Note that the VTrace options will survive a restart. 

if the file resulting from step 4 only includes 4-6 lines, then you creashed in a 
problem another guy had today:

Then please go into the Rundirectory of your database
and do 
 xkernprot -f knltrace akbm
The resulting file is what we are looking for.

And we are looking for the table definition.

And... I do not feel comfortable with the EXISTS-clause
in the CASE. I have no time at the moment to check exactly,
but I think you should avoid this.
use a from-select or the easier select mentioned below.

The select given above looks a little bit, well, strange.

Select case when exists (
                             SELECT lfd_Rueckfragenummer 
                                FROM tbl_StaffelRueckm 
                             WHERE Lfd_Rueckfragenummer = <integer>) 
                 Then 1 
                 Else -5678 
                 End 
from tbl_Staffelrueckm

The outer select runs trough the whole table  tbl_Staffelrueckm to return
the same result for each row in that table?!

Or are you looking for a 
SELECT DECODE (COUNT(*), 0, 1, -5678) 
  FROM tbl_StaffelRueckm 
WHERE Lfd_Rueckfragenummer = <integer>

Or do we have the well known problem of shortening an example up
to the state where it does not make sense and could be written much
easier, perhaps without causing trouble,...?

Elke
SAP Labs Berlin

> 
> Here are my last 2 entries from knldiag.err:
> 2003-09-01 06:30:40                          --- Starting GMT 
> 2003-09-01
> 04:30:40           7.4.3
>  Build 025-121-046-179
> 2003-09-02 11:31:56  1041 ERR 51080 SYSERROR -9210 KB Stack op illegal
> 
> One question remains: Is it convenient to work with this database any
> further or should I wait 'til this problem is solved? I'm 
> glad that I'm
> using the database at the moment for development purposes only.
> 
> So any help is appreciated.
> 
> Peter 
> 
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
> 
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to