Jobs - suggestions

[Jonathan Taylor]

When I open up the Jobs branch, I'm presented with just the job numbers.

However, 99% of the time I do not know what the job number is of the job I want to view/edit.

Therefore, I have to query USER_JOBS/ALL_JOBS (rather than inspect the properties of all the jobs) to discover which job number I am interested in (by looking at the WHAT column).

Could there be a better way to identify jobs in the list? Such as showing the next run date? Maybe a portion of the PL/SQL block (which is often short) could be shown as a tooltip when the mouse is hovered over a job?

Another idea is to have a filter (one that can easily be turned on/off) at the Jobs folder level - therefore if I filter on "CTX_DDL", it will look for this text in ALL the properties associated with Jobs, e.g. what, next_date etc.

This idea could be extended to all folders - for example searching in "Tables" would look at the table_name, columns, indexes etc.

 

[Marco Kalter]

Good idea. I have added this to the list of enhancement requests.

 

[rbrooker]

i agree, numbers mean squat.

as a workaround using the browser extender, you can add some "on right click" menu entries for jobs only.

i have :
what it does
when it last ran
when the interval is

this means i dont have to query all_jobs/user jobs tables.

 

[Jonathan Taylor]

Another small point - I think that the "interval" field should support multiple lines (just like the "what" field).

This is because I often have quite complicated criteria for interval (such as run at 12PM & 5PM), that includes lots of nested DECODEs etc., which are better formatted over several lines.

 

[Marco Kalter]

I have added this as well.