Frank Schimmelpfennig wrote : >when I droped and re-created a database procedure then a database role which was granted exectution >priviledge became invalid. I did not recognize the invalidity of this role. So when a user called >this database procedure - he got the execute priviledge >on the dbproc through this certain now invalid db role - the database (v 7.3.0.18) crashed: It went >"simply" offline without any message.
>This situation was reproducable. It was cleared when this certain invalid db role was also droped and recreated. >Is this a known bug? Is there a patch available? No, its no known bug and therefore no patch is available yet. But I could reproduce the situation and think that the correction will be available with 7.3.0 build 22. >Is there a possibility to indicate an invalid db role (maybe some select on domain.roleprivileges) A role should never become invalid, i.e. there is no need to indicate. Thomas --- Thomas Anhaus SAPDB, SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
