Skip to Main Content
Forums

Oracle Database Discussions

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!

Creating a Scheduler job for another user

LauryApr 22 2021

Hi,
I am working with Oracle RDBMS 19c.
I can create an Oracle Scheduler job for another session when at session level I set current_schema=<username>.
If I well understood, this alter session command places a user in a different schema making it easier to access the objects in this schema without having to qualify the object with the actual schema name.
This method does not change the current user and also does not give any privileges that this new schema has.
This is fine if as user SYSTEM I want to create a job for <username>.
Does someone know if there is a way to achieve this result without gving a password?
Kind Regards
This post has been answered by GregV on Jul 29 2021
Jump to Answer

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

1 person found this helpful
Jeffrey Kemp

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

1 person found this helpful
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 Apr 22 2021
#general-database-discussions, #pl-sql
6 comments
9,587 views