Answer / guest

Cause: The user attempted to enable too many roles.

Action: Enable fewer roles.

Please add more information about this Error

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.

ORA-27207: syntax error in device PARMS - parentheses mismatch or missing

1 Answers  

---

LPX-00230: invalid character ~1u (~2x) found in a Name or Nmtoken

1 Answers  

---

NCR-03025: NCRO: Failed to make LIST connection(s)

1 Answers  

---

NNL-00240: Starting "string"...

1 Answers  

---

TNS-01406: ID: string

1 Answers  

---

ORA-27250: OS system call failure

1 Answers  

---

ORA-16134: invalid MANAGED recovery FINISH option

1 Answers  

---

ORA-06431: ssaio: Invalid Block number

1 Answers  

---

ORA-36714: (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.

1 Answers  

---

NNL-00851: Renames refused, name is not a leaf name: number

1 Answers  

---

LSX-00135: invalid min/max Occurs for <all> element, must be 0/1

1 Answers  

---

ORA-01280: Fatal LogMiner Error.

1 Answers  

---