Documente Academic
Documente Profesional
Documente Cultură
Administration Tips
LIMIT
You then have to assign the right profile to the right user, like this:
Copyright Howard Rogers 2001 10/18/2001 Page 1 of 2
Administration Tips
ALTER ALTER
and so on. Next time Fred tries to log on multiple times, hell get the following error message on his fourth attempt: ERROR:ORA-02391:
EXCEEDED SIMULTANEOUS
SESSIONS_PER_USER
LIMIT
There is one extremely important point to know about resource profiles, however: they take no effect whatsoever until you switch them on. That is, even though they have been created, and properly assigned to all Users, no-one will have any connection limits until you tell the database to actually start enforcing the limits. Thats done with the following command: ALTER
SYSTEM SET RESOURCE_LIMIT=TRUE;
That switches on profile limits for the duration of the Instance, and for new connections only. A more permanent fix is to edit your init.ora, and enter the line resource_limit=true there. That way, every time you bounce the Instance, youll find resource profile limit being enforced. (Incidentally, any sessions a User already has running when you assign him the new profile and switch resource limiting on with the alter system command are counted against his allowed total. So if a User already has 4 connections when you suddenly start limiting him to just 3, he will immediately not be able to make a fifth connection. However, the original 4 are not disconnected, and are allowed to proceed as normal).
10/18/2001
Page 2 of 2