eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

SYS.DBMS_DDL dependencies on DBMS_SQL

Line 264: * If you call dbms_sql.parse() on the result of dbms_ddl.wrap(), please

260: * This API has three overload candidates. The first candidate accepts
261: * VARCHAR2 input. The second and third candidates accept collection-
262: * of-VARCHAR2 input allowing larger DDL statements.
263: *
264: * If you call dbms_sql.parse() on the result of dbms_ddl.wrap(), please
265: * note that you must set the LFFLG parameter to FALSE. If you set LFFLG
266: * to TRUE, the additional newlines in the middle of the obfuscated unit
267: * will confuse the PL/SQL compiler and cause the unit to be created with
268: * errors.

Line 271: FUNCTION wrap(ddl dbms_sql.varchar2s, lb PLS_INTEGER, ub PLS_INTEGER)

267: * will confuse the PL/SQL compiler and cause the unit to be created with
268: * errors.
269: */
270: FUNCTION wrap(ddl VARCHAR2) RETURN VARCHAR2;
271: FUNCTION wrap(ddl dbms_sql.varchar2s, lb PLS_INTEGER, ub PLS_INTEGER)
272: RETURN dbms_sql.varchar2s;
273: FUNCTION wrap(ddl dbms_sql.varchar2a, lb PLS_INTEGER, ub PLS_INTEGER)
274: RETURN dbms_sql.varchar2a;
275:

Line 272: RETURN dbms_sql.varchar2s;

268: * errors.
269: */
270: FUNCTION wrap(ddl VARCHAR2) RETURN VARCHAR2;
271: FUNCTION wrap(ddl dbms_sql.varchar2s, lb PLS_INTEGER, ub PLS_INTEGER)
272: RETURN dbms_sql.varchar2s;
273: FUNCTION wrap(ddl dbms_sql.varchar2a, lb PLS_INTEGER, ub PLS_INTEGER)
274: RETURN dbms_sql.varchar2a;
275:
276: /*

Line 273: FUNCTION wrap(ddl dbms_sql.varchar2a, lb PLS_INTEGER, ub PLS_INTEGER)

269: */
270: FUNCTION wrap(ddl VARCHAR2) RETURN VARCHAR2;
271: FUNCTION wrap(ddl dbms_sql.varchar2s, lb PLS_INTEGER, ub PLS_INTEGER)
272: RETURN dbms_sql.varchar2s;
273: FUNCTION wrap(ddl dbms_sql.varchar2a, lb PLS_INTEGER, ub PLS_INTEGER)
274: RETURN dbms_sql.varchar2a;
275:
276: /*
277: * NAME:

Line 274: RETURN dbms_sql.varchar2a;

270: FUNCTION wrap(ddl VARCHAR2) RETURN VARCHAR2;
271: FUNCTION wrap(ddl dbms_sql.varchar2s, lb PLS_INTEGER, ub PLS_INTEGER)
272: RETURN dbms_sql.varchar2s;
273: FUNCTION wrap(ddl dbms_sql.varchar2a, lb PLS_INTEGER, ub PLS_INTEGER)
274: RETURN dbms_sql.varchar2a;
275:
276: /*
277: * NAME:
278: * create_wrapped

Line 287: * - DBMS_SQL.PARSE(, DBMS_DDL.WRAP(ddl))

283: * type body, procedure or function.
284: *
285: * DESCRIPTION:
286: * DBMS_DDL.CREATE_WRAPPED(ddl) is equivalent to
287: * - DBMS_SQL.PARSE(, DBMS_DDL.WRAP(ddl))
288: * In other words, it obfuscates the text of the input CREATE OR
289: * REPLACE statement and executes it. This API will provide better
290: * performance than executing the individual operations.
291: *

Line 298: PROCEDURE create_wrapped(ddl dbms_sql.varchar2s, lb PLS_INTEGER,

294: * VARCHAR2 input. The second and third candidates accept collection-
295: * of-VARCHAR2 input allowing larger DDL statements.
296: */
297: PROCEDURE create_wrapped(ddl VARCHAR2);
298: PROCEDURE create_wrapped(ddl dbms_sql.varchar2s, lb PLS_INTEGER,
299: ub PLS_INTEGER);
300: PROCEDURE create_wrapped(ddl dbms_sql.varchar2a, lb PLS_INTEGER,
301: ub PLS_INTEGER);
302:

Line 300: PROCEDURE create_wrapped(ddl dbms_sql.varchar2a, lb PLS_INTEGER,

296: */
297: PROCEDURE create_wrapped(ddl VARCHAR2);
298: PROCEDURE create_wrapped(ddl dbms_sql.varchar2s, lb PLS_INTEGER,
299: ub PLS_INTEGER);
300: PROCEDURE create_wrapped(ddl dbms_sql.varchar2a, lb PLS_INTEGER,
301: ub PLS_INTEGER);
302:
303: malformed_wrap_input EXCEPTION;
304: pragma exception_init(malformed_wrap_input, -24230);