Re: want solution

It looks like other people have given you some good information already.

If you have applications and/or people logging in as the schema owner that is a situation to be avoided.

If you need to stop exports and imports from occurring ( you don't say what release of the database ) until you address other setup problems, one possibility is using a database level logon trigger and then see what user is logging in ( or attempting to ) and what program is being executed.

This is not an optimal solution since it incurs overhead on each logon attempt.

There's a bunch of example's you can find by doing a google search on ( for example ) say ( database logon trigger kill session ). Received on Tue Apr 18 2006 - 11:46:15 CDT