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.

APPS.FEM_DATABASE_UTIL_PKG dependencies on FEM_DDL_LOG

Line 24: of the SQL error message to FEM_DDL_LOG for

20: Greg Hall 21-Jun-2005 Bug# 4445212: Added calls to Get_PB_Param_Value
21: for data-driven tablespace and storage parameters.
22: Greg Hall 13-Jul-2005 Bug# 4491889: Fixed bug in the Exec procedure.
23: Greg Hall 19-Jul-2006 Bug# 5146586: Fixed bug that prevented logging
24: of the SQL error message to FEM_DDL_LOG for
25: failed SQL statements.
26: Greg Hall 19-Jul-2006 Bug# 5212287: for all four temp object
27: procedures, added Oracle error message into
28: the error message that is returned on the message

Line 154: -- p_object_id = 'ON' then tt logs the DDL operation into FEM_DDL_LOG.

150: -- DESCRIPTION
151: -- Executes the DDL SQL statement passed to it, using EXECUTE IMMEDIATE.
152: -- It logs the DDL operation in the Apps debug log.
153: -- If the FEM Process Behavior parameter setting that is in effect for
154: -- p_object_id = 'ON' then tt logs the DDL operation into FEM_DDL_LOG.
155: -- Note that since DDL statements perform an implicit COMMIT, there is no
156: -- point in trying to honor the p_commit parameter received by any of the
157: -- calling procedures, so this procedure doesn't even bother taking it,
158: -- and all inserts into FEM_DDL_LOG are commited.

Line 158: -- and all inserts into FEM_DDL_LOG are commited.

154: -- p_object_id = 'ON' then tt logs the DDL operation into FEM_DDL_LOG.
155: -- Note that since DDL statements perform an implicit COMMIT, there is no
156: -- point in trying to honor the p_commit parameter received by any of the
157: -- calling procedures, so this procedure doesn't even bother taking it,
158: -- and all inserts into FEM_DDL_LOG are commited.
159: -- If the DDL statement fails, the error is re-raised, to be trapped by the
160: -- calling program.
161: -- This procedure should only be used for executing DDL or other SQL that
162: -- must be built "on-the-fly". All other SQL statements should be executed

Line 166: -- used for logging the DDL operation in FEM_DDL_LOG.

162: -- must be built "on-the-fly". All other SQL statements should be executed
163: -- directly or in a declared cursor.
164: -- PARAMETERS
165: -- The SQL statement in p_command is executed. All other parameters are
166: -- used for logging the DDL operation in FEM_DDL_LOG.
167: -- HISTORY
168: -- Greg Hall 23-May-2005 Bug# 4301983: created.
169: -- Greg Hall 13-Jul-2005 Bug# 4491889: moved SUBSTR function outside
170: -- of the INSERT commands, into a separate

Line 178: -- of the SQL error message to FEM_DDL_LOG for

174: -- inserts, in case the latter fails it won't
175: -- prevent the former, and added error handlers
176: -- for DDL log insert statements.
177: -- Greg Hall 19-Jul-2006 Bug# 5146586: fixed bug that prevented logging
178: -- of the SQL error message to FEM_DDL_LOG for
179: -- failed SQL statements.
180: -- ==========================================================================
181:
182: v_command_short VARCHAR2(4000);

Line 206: INSERT into fem_ddl_log

202: IF p_ddl_logging = 'ON' THEN
203:
204: BEGIN
205:
206: INSERT into fem_ddl_log
207: (request_id,
208: object_id,
209: exec_seq,
210: timestamp,

Line 223: fem_ddl_log_s.nextval,

219: last_update_login)
220: VALUES
221: (p_request_id,
222: p_object_id,
223: fem_ddl_log_s.nextval,
224: TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'),
225: p_proc_name,
226: 'S',
227: NULL,

Line 278: INSERT into fem_ddl_log

274: IF p_ddl_logging = 'ON' THEN
275:
276: BEGIN
277:
278: INSERT into fem_ddl_log
279: (request_id,
280: object_id,
281: exec_seq,
282: timestamp,

Line 295: fem_ddl_log_s.nextval,

291: last_update_login)
292: VALUES
293: (p_request_id,
294: p_object_id,
295: fem_ddl_log_s.nextval,
296: TO_CHAR(SYSDATE, 'YYYY-MM-DD HH24:MI:SS'),
297: p_proc_name,
298: 'F',
299: v_sqlerrm,

Line 605: -- synonym creation, is logged in FEM_DDL_LOG. This logging can be toggled

601: -- concurrent process.
602: -- A synonym for the table is created in the APPS schema. The table is
603: -- logged by REQUEST_ID and OBJECT_ID in FEM_PL_TEMP_OBJECTS, so that it
604: -- can be undone by the Undo engine in case of failure. All DDL, including
605: -- synonym creation, is logged in FEM_DDL_LOG. This logging can be toggled
606: -- on/off by the process parameter 'DDL_LOGGING' in Admin=>Tuning Options.
607: -- Parameters:
608: -- p_api_version:
609: -- Optional OA-compliance parameter.

Line 970: -- is logged in FEM_DDL_LOG. This logging can be toggled on/off by the

966: -- to be dropped by a call to Drop_Temp_DB_Objects before the end of the
967: -- concurrent process.
968: -- The index is logged by REQUEST_ID and OBJECT_ID in FEM_PL_TEMP_OBJECTS,
969: -- so that it can be undone by the Undo engine in case of failure. All DDL
970: -- is logged in FEM_DDL_LOG. This logging can be toggled on/off by the
971: -- process parameter 'DDL_LOGGING' in Admin=>Tuning Options.
972: -- Parameters:
973: -- p_api_version:
974: -- Optional OA-compliance parameter.

Line 1297: -- of failure. All DDL is logged in FEM_DDL_LOG. This logging can be toggled

1293: -- p_view_def. Views created by this procedure are expected to be temporary,
1294: -- i.e. to be dropped by a call to Drop_Temp_DB_Objects before the end of the
1295: -- concurrent process. The view is logged by REQUEST_ID and OBJECT_ID in
1296: -- FEM_PL_TEMP_OBJECTS, so that it can be undone by the Undo engine in case
1297: -- of failure. All DDL is logged in FEM_DDL_LOG. This logging can be toggled
1298: -- on/off by the process parameter 'DDL_LOGGING' in Admin=>Tuning Options.
1299: -- Parameters:
1300: -- p_api_version:
1301: -- Optional OA-compliance parameter.