New answers tagged plsql
The actions you're performing on the data is technically different between the insert/update portions, but what about the business logic difference? IMO, your best bet is to contain a functional unit of work inside of a trigger, so that there is no discrepancy in what that trigger does. In my experience, Developers/Business Analysts often tend to think in ...
The JOB_OVER_MAX_DUR event isn't listed in docs until 11.2, even though MAX_RUN_DURATION is available in versions earlier than that. Compare 11.2 and 11.1. Additionally: DBMS_SCHEDULER.JOB_ALL_EVENTS on 11.2 does not include JOB_OVER_MAX_DUR (despite the name). Setting the RAISE_EVENTS attribute will neither set nor remove the JOB_OVER_MAX_DUR event. ...
Beware that the two commands will be run in the current schema, which is usually the schema that you logged in to. CREATE GLOBAL TEMPORARY TABLE tt_RptRCRsn CREATE OR REPLACE PROCEDURE RptRCByRsn These 6 tables must exist in the same schema ReturnChk ChecksWires BatchSummary RCReason RCResolution Comments Also, UTILS.CONVERT_TO_CHAR must exist. ...
Instead of the string literal VAR1 and VAR2, use the variables in your EXECUTE IMMEDIATE statement: execute immediate 'CREATE DATABASE LINK try_lnk CONNECT TO ' || VAR1 || ' IDENTIFIED BY ' || VAR1 || ' USING ''' || VAR2 || '''';
You can't embed DDL in a stored procedure like this. Either use execute immediate and your DDL statement passed to it as a string, or, better, remove the stored procedure entirely an execute the DDL directly.
Top 50 recent answers are included