[EMAIL PROTECTED] wrote:

> when calling a stored procedure via a C/C++-precompiler 
> program we got a -9111 system error.  An implicit database 
> shutdown did not occur (as mentioned in the documentation). 
> What is the meaning of this system error? How can it be avoided?
> 
> Is there the possibility of a connection to a minor system 
> upgrade (v7.3.0.18 --> v7.3.0.21) we performed short time ago?
> 
> We use SAP DB v7.3.0.21.
> 
> I searched the knldiag file but did not find any entries 
> which relate the -9111 error (even no 'SYSERROR' entry). 
> Attached You find the source code of the stored procedure and 
> the ddl script of the schema tables.

Hi,

it it astonishing that a -9111 returned to the user should not be findable
in knldiag.
Ok, sometimes knldiag is written to fast to see things happened some hours
ago.
But I think you looked only few moments after seeing the error ?

Did you find any line

a[b] --> c[d] len:e
where a-e are integer

if you did not find -9111. Did you find 'move'  or 'fill' ?

It is not that easy to reproduce your case, because at least 
sequence seq_lot was missing (ok, I created one) and 
dbproc snr_put_system_log is missing (there I stopped trying)
and because in your dbproc one will only reach the lower part if 
the beginning will return results --> data would be needed.
Ok, that is not the way to be gone.

Did this procedure work in 7.3.0.18 ????
I do not believe this, because in older releases dbprocs had some other
problems.

And I know, that in the meantime (after 7.3.0.21) we found at least one
-9111 reason
for dbprocs in our code which will be fixed with the next version. But I am
not able
to reproduce (see above). I would be able to check, if those funny lines
were in the
knldiag and you would send those to us.

Elke
SAP Labs Berlin

P.S. the meaning of -9111: the kernel tries to put more bytes to a place
where 
       is only room for a smaller number of bytes
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general

Reply via email to