Hi, I had to face very strange effect with on of my database instances (v7.3.0.18): When I called a dbproc that I droped and re-created with an user that got his access privileges on this dbproc through a database role the database instance did an unintended shutdown (see extract of knldiag file below). The status of the database instance after this "crash" was 'OFFLINE'. The instance was consistent, and I was able to bring her up to warm status again.
Is there someone who can give a hint what causes this strange behaviour? I was able to reproduce this behaviour, and tried to generate output to a vtrace file. But there was no output in this file (except the file header) :-( There was no output in the knldiag.err either. knldiag: [...] --------------------------------------- current write position ------------------- +++++++++++++++++++++++++++++++++++++++ Kernel Exit ++++++++++++++++++++++++++++ 2002-05-28 15:18:53 1 12844 DBSTATE Kernel exited with core and exit status 0x8b 2002-05-28 15:18:53 1 12848 DBSTATE Kernel exited due to signal 11(SIGSEGV) 2002-05-28 15:18:53 1 12808 CRASH Creating tracewriter emergency dump sh: /data/users/sapdb/depend/bin/x_cons: not found 2002-05-28 15:18:54 1 11987 dump_rte 'cd /data/users/sapdb/indep_data/wrk/S_LUNA2/rtedump_dir; /data/users/sapdb/depend/bin/x_cons S_LUNA2 sh all > rtedump' failed 2002-05-28 15:18:54 1 12696 DBSTATE Change DbState to 'KILL_ALL'(23) 2002-05-28 15:18:55 1 12696 DBSTATE Change DbState to 'OFFLINE '(28) --------------------------------------- current write position ------------------- Thanks in advance! Frank Schimmelpfennig PHILIPS Semiconductors Hamburg ATO-Hamburg IT&DataSupport Tel.: +49 40 5613 -1835, Fax: -3020 _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
