Skip to Main Content

SQLcl: MCP Server & SQL Prompt

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

debuggin Sql developer

3833528Nov 15 2018 — edited Nov 16 2018

When trying to debug a database package this does not allow it because it shows the following error:

Conectando a la base de datos XXX_AC_XXX_LXXX.

Ejecutando PL/SQL: CALL DBMS_DEBUG_JDWP.CONNECT_TCP( 'xxx.xxx.xxx.xxx', 'xxxxx' )

ORA-28031: se ha excedido el máximo de 150 roles activados

ORA-06512: en "SYS.DBMS_DEBUG_JDWP", línea 68

ORA-06512: en línea 1

El proceso ha terminado.

Desconectando de la base de datos XXX_AC_XXX_LXXX.

The point is that the number of roles that I have assigned to the user are the necessary and several users that even exceed the 350 roles which is normal within my business.

In my concept I think these validations should not be necessary to perform a simple debug, is there any way to suppress this validation without having to delete the roles to users who have more than 150 roles?

Thanks for the attention lent.

Comments

Mike Kutz

TAG using JSON value might be more flexible.

This would then allow template based code generators (eg ) to automatically identify which tables need to be combined together to create a specific Transactional API (XAPI).  (eg an API that must work with >1 tables)

MK

Jeffrey Kemp

Tags for table columns, constraints, etc. would also be useful.

Matheus Boesing

TAG using JSON value might be more flexible.

This would then allow template based code generators (eg ) to automatically identify which tables need to be combined together to create a specific Transactional API (XAPI).  (eg an API that must work with >1 tables)

MK

Great Mike!
It really should be done with JSON syntax. It allows to create different kinds of tags in a single 'tag column', like:
[...]TAGS ('{Use:Transactional, SensitiveData:false, Version1.0:MatheusDBA, Version2.0:AnotherDBA}');


Or even tags hierarchies/subtypes... Anyway, it's way more flexible.
Thanks for this insight!

Matheus Boesing

Tags for table columns, constraints, etc. would also be useful.

Exactly... I just used some kind of objects for this example... but I believe it can apply for any king of object, including schemas... like (using Mike's contribution):
CREATE USER USER_EXAMPLE TAGS ('{Use:AdHocReports, Accountable:InternalBusinessTeam}');

Gbenga Ajakaye

This would definitely be useful.

1 - 5

Post Details

Added on Nov 15 2018
3 comments
201 views