I download version toad for oracle xpert db admin mode 16.3.231.2085, when i consulte oracle database version 18 or 19c, i can check tab run logs at scheduler jobs, but oracle database version 10, i cant, because the tables/views is using for this query, has new columns added in newer versions of oracle. last version of toad works fine at this point.
how can i fix my toad, as i still have oracle 10 in production mode? do i have to downgrade my toad instalation?
i include the query Toad is using
SELECT l.log_id "Log ID",
l.log_date "Log Date",
L.operation "Operation",
L.job_subname "Subname",
L.STATUS "Status",
L.user_name "User Name",
L.CLIENT_ID "Client ID",
L.global_uid "Global UID",
R.REQ_START_DATE "Required Start Date",
R.ACTUAL_START_DATE "Actual Start Date",
R.RUN_DURATION "Run Duration",
R.INSTANCE_ID "Instance ID",
R.SESSION_ID "Session ID",
R.SLAVE_PID "Slave PID",
TO_CHAR (R.CPU_USED) "CPU Used",
R.ADDITIONAL_INFO "Additional Info (Run)",
R.Errors "Errors",
R.Output "Output"
FROM DBA_SCHEDULER_JOB_LOG L, DBA_SCHEDULER_JOB_RUN_DETAILS R
WHERE l.Owner = :o AND l.job_name = :nm AND l.log_id = r.log_id(+)
ORDER BY 9 ASC NULLS LAST
Which column causes the problem?
We have code in there that only includes the columns R.Errors and R.Output if you are connected to Oracle version 12 or newer.
When I remove these columns from the SQL and run it on 10gR2, I don't have any problems.
those ones exacly, i guess in oracle 10 didnt exist, those are for newer versions
im using schema browser --> schedule jobs --> tab "run log" the error is
ORA-00904: "L"."JOB_SUBNAME": invalid identifier
Oh, I guess you are using Oracle version 10.1. For me, it works fine on 10.2.
I'm sorry, there is nothing that you can do in Toad to modify that query. You can, however, have multiple Toad versions installed, if you are not using the subscription version.
I will fix that for next Toad version. Sorry about that.
yeap, im using oracle 10g
i guess i can do that or uninstall the last version, the one before 16.3.231.2085 works fine with this ... but have other bugs.
thank you for your answer
Actually, there is a workaround you can do. The Schema Browser has a feature that allows you to program in your own queries to work on the selected objects. See video below on how to set it up and use it.
This is the SQL that I pasted into the Custom Query dialog:
SELECT l.log_id "Log ID",
l.log_date "Log Date",
L.operation "Operation",
L.STATUS "Status",
L.user_name "User Name",
L.CLIENT_ID "Client ID",
L.global_uid "Global UID",
R.REQ_START_DATE "Required Start Date",
R.ACTUAL_START_DATE "Actual Start Date",
R.RUN_DURATION "Run Duration",
R.INSTANCE_ID "Instance ID",
R.SESSION_ID "Session ID",
R.SLAVE_PID "Slave PID",
TO_CHAR (R.CPU_USED) "CPU Used",
R.ADDITIONAL_INFO "Additional Info (Run)"
FROM
<DA>SCHEDULER_JOB_LOG L,
<DA>SCHEDULER_JOB_RUN_DETAILS R
WHERE l.Owner = <ObjectOwner>
AND l.job_name in <ObjectList>
AND l.log_id = r.log_id(+)
ORDER BY 9 ASC NULLS LAST
-John
Thank you John, im going to try that