ORA-28031: maximum of string enabled roles exceeded

Answers were Sorted based on User's Feedback



ORA-28031: maximum of string enabled roles exceeded..

Answer / guest

Cause: The user attempted to enable too many roles.

Action: Enable fewer roles.

Please add more information about this Error

Is This Answer Correct ?    0 Yes 0 No

ORA-28031: maximum of string enabled roles exceeded..

Answer / cvbb

At first time you can think about max_enabled_roles
parameter but max_enabled_roles parameter has nothing to do
if you enable 148 user-defined roles.

In fact this parameter is deprecated. It is retained for
backward compatibility only. You can see this parameter
settings by,

SQL> show parameter max_enable

NAME TYPE VALUE
———————————— ——————————— ——————————
max_enabled_roles integer 150

Though this parameter is set to 150 and you have enabled 148
user defined roles but additional user-defined roles can’t
be enabled because of the actual number of roles that users
can enable is 148. So max_enabled_roles is 2 plus 148,
because each user has two additional roles, PUBLIC and the
user’s own role.

As there is limit to 148 so you have to disable fewer roles
or drop some roles and reorganize your database role policy.

You can enable or disable roles by using the SET ROLE
statement for your current session.

If you want to enable all roles except manager and clerk
role then use,

SET ROLE ALL EXCEPT manager, clerk;

Remember roles listed in the EXCEPT clause must be roles
granted directly to you. They cannot be roles granted to you
through other roles.

Is This Answer Correct ?    0 Yes 0 No

Post New Answer

More Oracle Errors Interview Questions

QSM-02114: no GROUP BY clause, no aggregates and not >= 9.0 compatibility

1 Answers  


TNS-12679: Native services disabled by other process but required

1 Answers  


ORA-09851: soacon: Archmon unable to lock named pipe.

1 Answers  


ORA-01936: cannot specify owner when creating users or roles

1 Answers  


ORA-02173: invalid option for DROP TABLESPACE

1 Answers  






O2I-00121: No value was specified for the CODE option

1 Answers  


KUP-03010: OCI error getting database column type.

1 Answers  


TNS-00241: Connection Manager: Logging is now OFF

1 Answers  


ORA-26681: command type not supported

1 Answers  


ORA-29374: resource plan string in top-plan string has no plan directives

1 Answers  


ORA-00403: %s (string) is not the same as other instances (string)

1 Answers  


RMAN-06204: Changed string objects to UNAVAILABLE status

1 Answers  


Categories