logminer

偶然发现dbmslm.sql里对logminer介绍还挺丰富，顺便记录一下

create or replace PACKAGE dbms_logmnr IS
--------------------
-- OVERVIEW
--
-- This package contains the procedures used by LogMiner ad-hoc query
-- interface that allows for redo log stream analysis.
-- There are three procedures and two functions available to the user:
-- dbms_logmnr.add_logfile() : to register logfiles to be analyzed
-- dbms_logmnr.remove_logfile() : to remove logfiles from being analyzed
-- dbms_logmnr.start_logmnr() : to provide window of analysis and
-- meta-data information
-- dbms_logmnr.end_logmnr() : to end the analysis session
-- dbms_logmnr.column_present() : whether a particular column value
-- is presnet in a redo record
-- dbms_logmnr.mine_value() : extract data value from a redo record
-- PROCEDURE INFORMATION:
-- #1 dbms_logmnr.add_logfile():
-- DESCRIPTION:
-- Registers a redo log file with LogMiner. Multiple redo logs can be
-- registered by calling the procedure repeatedly. The redo logs
-- do not need to be registered in any particular order.
-- Both archived and online redo logs can be mined. If a successful
-- call to the procedure is made a call to start_logmnr() must be
-- made before selecting from v$logmnr_contents.
--
-- CONSTANTS:
-- dbms_logmnr.NEW: Starts a new list. Any file registered prior to
-- this call is discarded.
-- dbms_logmnr.ADDFILE: Adds the redo log to the existing
-- list. LogMiner checks to make sure that the redo log is from
-- the same database (DB_ID and RESETLOGS_SCN) incarnation as the
-- ones previously added.
-- #2 dbms_logmnr.remove_logfile()
-- DESCRIPTION:
-- Unregisters a redo log file from LogMiner. Multiple redo logs can be
-- unregistered by calling the procedure repeatedly. The redo logs
-- do not need to be unregistered in any particular order. If a
-- successful call to the procedure is made a call to start_logmnr()
-- must be made before selecting from v$logmnr_contents.
-- #3 dbms_logmnr.start_logmnr()
-- DESCRIPTION:
-- Loads the data dictionary used by LogMiner to translate internal
-- schema object identifiers to names. The redo stream does not
-- contain names of schema objects and columns. The data dictionary
-- extract can be provided in three ways:
-- (i) use Oracle's online catalog. This is only valid when the
-- mining of redo logs is done in the same system that generated
-- them.
-- (ii) use data dictionary extract taken to a flat file.
-- (See description of dbms_logmnr_d.build())
-- (iii) use data dictionary extracted in the redo stream. This
-- option can ONLY be used when LogMiner is being run on an open
-- database, and the source and the mining database instances are
-- Oracle9i or higher.
-- The user can also restrict the analysis inside an SCN range or a
-- time range. If both SCN range and time range are specified, only
-- the SCN range is used.
-- The user needs to be mindful of the fact that use of time range
-- can be imprecise. If a start_time or start_scn is specified, it
-- must be contained in a redo log added by a previous call to
-- dbms_logmnr.add_logfile(). If a start_time and start_scn is not
-- specified, LogMiner will set it based on the earliest added redo
-- log. If a end_time or end_scn is specified and it is beyond the
-- latest added redo log, LogMiner will overwrite the end_time and
-- and end_scn with information from the latest added redo log. When
-- the CONTINOUS_MINE option is in use the semantics of
-- start and end time/scn ranges may be different.
-- See additional documentation below.
--
-- CONSTANTS (used in options parameter)
-- dbms_logmnr.NO_DICT_RESET_ONSELECT: (will be deprecated soon)
-- dbms_logmnr.COMMITED_DATA_ONLY: Groups DMLs belonging to the
-- same transaction. Transactions are shown in their commit order.
-- Internal redo records (those related to index operations, space
-- management etc) are filtered out. So are rolled back
-- transactions, rollback to savepoints and in-flight transactions.
-- dbms_logmnr.SKIP_CORRUPTION: Usually LogMiner returns an error
-- on encountering corrupt redo records. With this option set
-- LogMiner will skip the corrupted redo records and continue
-- mining. LogMiner can not handle a redo log that has a corrupt
-- header.
-- dbms_logmnr.DDL_DICT_TRACKING: LogMiner will apply the DDL
-- statements encountered in the redo stream to its internal
-- dictionary. Only available with Oracle9i redo logs and later.
-- Mining database needs to be open.
-- dbms_logmnr.DICT_FROM_ONLINE_CATALOG: Use the online data
-- dictionary for SQL reconstruction. Mining database must be the
-- same one that generated the redo logs. User should expect to
-- see "Dictionary Version Mismatch" in SQL_REDO if the current
-- object version is newer than the ones encountered in the redo
-- stream.
-- dbms_logmnr.DICT_FROM_REDO_LOGS: Use the dictionary extract logged
-- in the redo stream.
-- dbms_logmnr.NO_SQL_DELIMITER: By default, the SQL_REDO and SQL_UNDO
-- statements are delimited with a ';'. However, this is
-- inconvenient for applications that want to open a cursor and
-- execute the reconstructed statements. With this option set,
-- the SQL_DELIMITER is not placed at the end of reconstructed
-- statements.
-- dbms_logmnr.NO_ROWID_IN_STMT: By default, the SQL_REDO and SQL_UNDO
-- statements for UPDATE and DELETE operations contain a 'ROWID = '
-- in the where clause. However, this is inconvenient for
-- applications that want to re-execute the SQL statement. With
-- this option set, 'ROWID' is not placed at the end of reconstructed
-- statements. Note: The onus is on the user to ensure that
-- supplemental logging was enabled in the source database at the
-- appropriate level and that no duplicate rows exist in tables of
-- interest. LogMiner Adhoc Query does NOT make any quarantee
-- regarding uniqueness of logical row identifiers.
-- dbms_logmnr.PRINT_PRETTY_SQL: Useful for basic report for
-- analysis. With large number of columns the reconstructed
-- SQL statements become visually busy. With this option set
-- LogMiner formats the reconstructed SQL statements for ease
-- of reading. The reconstructed SQL statements look as follow:
-- insert into "SCOTT"."EMP" values
-- EMPNO: 101010,
-- ENAME: "Valued Employee",
-- SAL: 101010,
-- DEPT: NULL;
-- update "SCOTT"."EMP"
-- set
-- "EMPNO" = 101011 and
-- "SAL" = 101011
-- where
-- "EMPNO" = 101010 and
-- "SAL" = 101010 and
-- ROWID = AABBCEXFGHA;
-- dbms_logmnr.CONTINUOUS_MINE: Need to mine in the same instance
-- that is generating the redo logs. The user needs to register
-- only one archived log file. LogMiner will automatically add
-- and mine subsequent archived redo logs, and eventually
-- mine online logfiles.
-- dbms_logmnr.STRING_LITERALS_IN_STMT: By default, the SQL_REDO and
-- SQL_UNDO statements honor a database session's NLS setting
-- (e.g. NLS_DATE_FORMAT, NLS_NUMERIC_CHARACTERS, etc.) when
-- formating the reconstructed SQL statements. With this option,
-- the reconstructed SQL statements will be formatted using ANSI/ISO
-- string literal formats.
-- #4 dbms_logmnr.end_logmnr()
-- DESCRIPTION:
-- Ends the LogMiner session. Releases all PGA memory allocated
-- to stage internal data structures etc.
--
-- EXCEPTIONS:
-- ORA: 1307 No LogMiner session is currently active.
-- Attempt to end_logmnr() without calling
-- add_logfile() or start_logmnr()
--
-- #5 dbms_logmnr.mine_value()
-- DESCRIPTION:
-- This facilitates query by data value. For instance, the user
-- can formulate a query that says "Show me all updates to
-- SCOTT.EMP where the SAL column is updated to twice its
-- original value"
-- select sql_redo from v$logmnr_contents where
-- operation = 'UPDATE" and
-- owner_name = 'SCOTT' and seg_name = 'EMP' and
-- dbms_logmnr.mine_value(redo_value, 'SCOTT.EMP.SAL') >
-- 2* dbms_logmnr.mine_value(undo_value, 'SCOTT.EMP.SAL');
-- The function returns NULL if the column does not exist in
-- the redo record or if the column value is actually null.
-- To decipher between the two different null possibilities
-- use dbms_logmnr.column_present() function.
--
-- PARAMETERS:
-- sql_redo_undo: which column in v$logmnr_contents to
-- extract data value from
-- column_name: fully qualified column name of the
-- column that needs to be extracted
--
-- EXCEPTIONS:
-- ORA 1302: Specified table or column does not exist
--
-- #6 dbms_logmnr.column_present()
-- DESCRIPTION:
-- Can be used to decipher null returns from mine_value function
-- The query described above can be rewritten to filter out
-- redo records that do not contain update to the 'SAL'
-- columns
-- select sql_redo from v$logmnr_contents where
-- operation = 'UPDATE"
-- owner_name = 'SCOTT' and seg_name = 'EMP' and
-- dbms_logmnr.mine_value(redo_value, 'SCOTT.EMP.SAL') >
-- 2* dbms_logmnr.mine_value(undo_value, 'SCOTT.EMP.SAL') and
-- dbms_logmnr.column_present(redo_value, 'SCOTT.EMP.SAL');
--
-- PARAMETERS:
-- sql_redo_undo: which column in v$logmnr_contents to
-- extract data value from
-- column_name: fully qualified column name of the
-- column that needs to be extracted
-- Constants for add_archivelog options flag
NEW CONSTANT BINARY_INTEGER := 1;
REMOVEFILE CONSTANT BINARY_INTEGER := 2;
ADDFILE CONSTANT BINARY_INTEGER := 3;
--
-- Constants for start_logmnr options flag
NO_DICT_RESET_ONSELECT CONSTANT BINARY_INTEGER := 1;
COMMITTED_DATA_ONLY CONSTANT BINARY_INTEGER := 2;
SKIP_CORRUPTION CONSTANT BINARY_INTEGER := 4;
DDL_DICT_TRACKING CONSTANT BINARY_INTEGER := 8;
DICT_FROM_ONLINE_CATALOG CONSTANT BINARY_INTEGER := 16;
DICT_FROM_REDO_LOGS CONSTANT BINARY_INTEGER := 32;
NO_SQL_DELIMITER CONSTANT BINARY_INTEGER := 64;
PRINT_PRETTY_SQL CONSTANT BINARY_INTEGER := 512;
CONTINUOUS_MINE CONSTANT BINARY_INTEGER := 1024;
NO_ROWID_IN_STMT CONSTANT BINARY_INTEGER := 2048;
STRING_LITERALS_IN_STMT CONSTANT BINARY_INTEGER := 4096;
--
-- Constants for STATUS column of v$logmnr_contents
-- NOTE: Make sure that new ones match the values defined
-- in the krvfsri struct in krv0.h
VALID_SQL CONSTANT BINARY_INTEGER := 0;
INVALID_SQL CONSTANT BINARY_INTEGER := 2;
UNGUARANTEED_SQL CONSTANT BINARY_INTEGER := 3;
CORRUPTED_BLK_IN_REDO CONSTANT BINARY_INTEGER := 4;
ASSEMBLY_REQUIRED_SQL CONSTANT BINARY_INTEGER := 5;
HOLE_IN_LOGSTREAM CONSTANT BINARY_INTEGER := 1291;
---------------------------------------------------------------------------
-- Initialize LOGMINER
--
-- Supplies LOGMINER with the list of filenames and SCNs required
-- to initialize the tool. Once this procedure completes, the server is ready
-- to process selects against the v$logmnr_contents fixed view.
--
---------------------------------------------------------------------------
PROCEDURE start_logmnr(
startScn IN NUMBER default 0 ,
endScn IN NUMBER default 0,
startTime IN DATE default '',
endTime IN DATE default '',
DictFileName IN VARCHAR2 default '',
Options IN BINARY_INTEGER default 0 );
PROCEDURE add_logfile(
LogFileName IN VARCHAR2,
Options IN BINARY_INTEGER default ADDFILE );
PROCEDURE end_logmnr;
FUNCTION column_present(
sql_redo_undo IN NUMBER default 0,
column_name IN VARCHAR2 default '') RETURN BINARY_INTEGER;
FUNCTION mine_value(
sql_redo_undo IN NUMBER default 0,
column_name IN VARCHAR2 default '') RETURN VARCHAR2;
PROCEDURE remove_logfile(
LogFileName IN VARCHAR2);

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

create or replace PACKAGE dbms_logmnr IS

--------------------

-- OVERVIEW

-- This package contains the procedures used by LogMiner ad-hoc query

-- interface that allows for redo log stream analysis.

-- There are three procedures and two functions available to the user:

-- dbms_logmnr.add_logfile() : to register logfiles to be analyzed

-- dbms_logmnr.remove_logfile() : to remove logfiles from being analyzed

-- dbms_logmnr.start_logmnr() : to provide window of analysis and

-- meta-data information

-- dbms_logmnr.end_logmnr() : to end the analysis session

-- dbms_logmnr.column_present() : whether a particular column value

-- is presnet in a redo record

-- dbms_logmnr.mine_value() : extract data value from a redo record

-- PROCEDURE INFORMATION:

-- #1 dbms_logmnr.add_logfile():

-- DESCRIPTION:

-- Registers a redo log file with LogMiner. Multiple redo logs can be

-- registered by calling the procedure repeatedly. The redo logs

-- do not need to be registered in any particular order.

-- Both archived and online redo logs can be mined. If a successful

-- call to the procedure is made a call to start_logmnr() must be

-- made before selecting from v$logmnr_contents.

-- CONSTANTS:

-- dbms_logmnr.NEW: Starts a new list. Any file registered prior to

-- this call is discarded.

-- dbms_logmnr.ADDFILE: Adds the redo log to the existing

-- list. LogMiner checks to make sure that the redo log is from

-- the same database (DB_ID and RESETLOGS_SCN) incarnation as the

-- ones previously added.

-- #2 dbms_logmnr.remove_logfile()

-- DESCRIPTION:

-- Unregisters a redo log file from LogMiner. Multiple redo logs can be

-- unregistered by calling the procedure repeatedly. The redo logs

-- do not need to be unregistered in any particular order. If a

-- successful call to the procedure is made a call to start_logmnr()

-- must be made before selecting from v$logmnr_contents.

-- #3 dbms_logmnr.start_logmnr()

-- DESCRIPTION:

-- Loads the data dictionary used by LogMiner to translate internal

-- schema object identifiers to names. The redo stream does not

-- contain names of schema objects and columns. The data dictionary

-- extract can be provided in three ways:

-- (i) use Oracle's online catalog. This is only valid when the

-- mining of redo logs is done in the same system that generated

-- them.

-- (ii) use data dictionary extract taken to a flat file.

-- (See description of dbms_logmnr_d.build())

-- (iii) use data dictionary extracted in the redo stream. This

-- option can ONLY be used when LogMiner is being run on an open

-- database, and the source and the mining database instances are

-- Oracle9i or higher.

-- The user can also restrict the analysis inside an SCN range or a

-- time range. If both SCN range and time range are specified, only

-- the SCN range is used.

-- The user needs to be mindful of the fact that use of time range

-- can be imprecise. If a start_time or start_scn is specified, it

-- must be contained in a redo log added by a previous call to

-- dbms_logmnr.add_logfile(). If a start_time and start_scn is not

-- specified, LogMiner will set it based on the earliest added redo

-- log. If a end_time or end_scn is specified and it is beyond the

-- latest added redo log, LogMiner will overwrite the end_time and

-- and end_scn with information from the latest added redo log. When

-- the CONTINOUS_MINE option is in use the semantics of

-- start and end time/scn ranges may be different.

-- See additional documentation below.

-- CONSTANTS (used in options parameter)

-- dbms_logmnr.NO_DICT_RESET_ONSELECT: (will be deprecated soon)

-- dbms_logmnr.COMMITED_DATA_ONLY: Groups DMLs belonging to the

-- same transaction. Transactions are shown in their commit order.

-- Internal redo records (those related to index operations, space

-- management etc) are filtered out. So are rolled back

-- transactions, rollback to savepoints and in-flight transactions.

-- dbms_logmnr.SKIP_CORRUPTION: Usually LogMiner returns an error

-- on encountering corrupt redo records. With this option set

-- LogMiner will skip the corrupted redo records and continue

-- mining. LogMiner can not handle a redo log that has a corrupt

-- header.

-- dbms_logmnr.DDL_DICT_TRACKING: LogMiner will apply the DDL

-- statements encountered in the redo stream to its internal

-- dictionary. Only available with Oracle9i redo logs and later.

-- Mining database needs to be open.

-- dbms_logmnr.DICT_FROM_ONLINE_CATALOG: Use the online data

-- dictionary for SQL reconstruction. Mining database must be the

-- same one that generated the redo logs. User should expect to

-- see "Dictionary Version Mismatch" in SQL_REDO if the current

-- object version is newer than the ones encountered in the redo

-- stream.

-- dbms_logmnr.DICT_FROM_REDO_LOGS: Use the dictionary extract logged

-- in the redo stream.

-- dbms_logmnr.NO_SQL_DELIMITER: By default, the SQL_REDO and SQL_UNDO

-- statements are delimited with a ';'. However, this is

-- inconvenient for applications that want to open a cursor and

-- execute the reconstructed statements. With this option set,

-- the SQL_DELIMITER is not placed at the end of reconstructed

-- statements.

-- dbms_logmnr.NO_ROWID_IN_STMT: By default, the SQL_REDO and SQL_UNDO

-- statements for UPDATE and DELETE operations contain a 'ROWID = '

-- in the where clause. However, this is inconvenient for

-- applications that want to re-execute the SQL statement. With

-- this option set, 'ROWID' is not placed at the end of reconstructed

-- statements. Note: The onus is on the user to ensure that

-- supplemental logging was enabled in the source database at the

-- appropriate level and that no duplicate rows exist in tables of

-- interest. LogMiner Adhoc Query does NOT make any quarantee

-- regarding uniqueness of logical row identifiers.

-- dbms_logmnr.PRINT_PRETTY_SQL: Useful for basic report for

-- analysis. With large number of columns the reconstructed

-- SQL statements become visually busy. With this option set

-- LogMiner formats the reconstructed SQL statements for ease

-- of reading. The reconstructed SQL statements look as follow:

-- insert into "SCOTT"."EMP" values

-- EMPNO: 101010,

-- ENAME: "Valued Employee",

-- SAL: 101010,

-- DEPT: NULL;

-- update "SCOTT"."EMP"

-- set

-- "EMPNO" = 101011 and

-- "SAL" = 101011

-- where

-- "EMPNO" = 101010 and

-- "SAL" = 101010 and

-- ROWID = AABBCEXFGHA;

-- dbms_logmnr.CONTINUOUS_MINE: Need to mine in the same instance

-- that is generating the redo logs. The user needs to register

-- only one archived log file. LogMiner will automatically add

-- and mine subsequent archived redo logs, and eventually

-- mine online logfiles.

-- dbms_logmnr.STRING_LITERALS_IN_STMT: By default, the SQL_REDO and

-- SQL_UNDO statements honor a database session's NLS setting

-- (e.g. NLS_DATE_FORMAT, NLS_NUMERIC_CHARACTERS, etc.) when

-- formating the reconstructed SQL statements. With this option,

-- the reconstructed SQL statements will be formatted using ANSI/ISO

-- string literal formats.

-- #4 dbms_logmnr.end_logmnr()

-- DESCRIPTION:

-- Ends the LogMiner session. Releases all PGA memory allocated

-- to stage internal data structures etc.

-- EXCEPTIONS:

-- ORA: 1307 No LogMiner session is currently active.

-- Attempt to end_logmnr() without calling

-- add_logfile() or start_logmnr()

-- #5 dbms_logmnr.mine_value()

-- DESCRIPTION:

-- This facilitates query by data value. For instance, the user

-- can formulate a query that says "Show me all updates to

-- SCOTT.EMP where the SAL column is updated to twice its

-- original value"

-- select sql_redo from v$logmnr_contents where

-- operation = 'UPDATE" and

-- owner_name = 'SCOTT' and seg_name = 'EMP' and

-- dbms_logmnr.mine_value(redo_value, 'SCOTT.EMP.SAL') >

-- 2* dbms_logmnr.mine_value(undo_value, 'SCOTT.EMP.SAL');

-- The function returns NULL if the column does not exist in

-- the redo record or if the column value is actually null.

-- To decipher between the two different null possibilities

-- use dbms_logmnr.column_present() function.

-- PARAMETERS:

-- sql_redo_undo: which column in v$logmnr_contents to

-- extract data value from

-- column_name: fully qualified column name of the

-- column that needs to be extracted

-- EXCEPTIONS:

-- ORA 1302: Specified table or column does not exist

-- #6 dbms_logmnr.column_present()

-- DESCRIPTION:

-- Can be used to decipher null returns from mine_value function

-- The query described above can be rewritten to filter out

-- redo records that do not contain update to the 'SAL'

-- columns

-- select sql_redo from v$logmnr_contents where

-- operation = 'UPDATE"

-- owner_name = 'SCOTT' and seg_name = 'EMP' and

-- dbms_logmnr.mine_value(redo_value, 'SCOTT.EMP.SAL') >

-- 2* dbms_logmnr.mine_value(undo_value, 'SCOTT.EMP.SAL') and

-- dbms_logmnr.column_present(redo_value, 'SCOTT.EMP.SAL');

-- PARAMETERS:

-- sql_redo_undo: which column in v$logmnr_contents to

-- extract data value from

-- column_name: fully qualified column name of the

-- column that needs to be extracted

-- Constants for add_archivelog options flag

NEW CONSTANT BINARY_INTEGER := 1;

REMOVEFILE CONSTANT BINARY_INTEGER := 2;

ADDFILE CONSTANT BINARY_INTEGER := 3;

-- Constants for start_logmnr options flag

NO_DICT_RESET_ONSELECT CONSTANT BINARY_INTEGER := 1;

COMMITTED_DATA_ONLY CONSTANT BINARY_INTEGER := 2;

SKIP_CORRUPTION CONSTANT BINARY_INTEGER := 4;

DDL_DICT_TRACKING CONSTANT BINARY_INTEGER := 8;

DICT_FROM_ONLINE_CATALOG CONSTANT BINARY_INTEGER := 16;

DICT_FROM_REDO_LOGS CONSTANT BINARY_INTEGER := 32;

NO_SQL_DELIMITER CONSTANT BINARY_INTEGER := 64;

PRINT_PRETTY_SQL CONSTANT BINARY_INTEGER := 512;

CONTINUOUS_MINE CONSTANT BINARY_INTEGER := 1024;

NO_ROWID_IN_STMT CONSTANT BINARY_INTEGER := 2048;

STRING_LITERALS_IN_STMT CONSTANT BINARY_INTEGER := 4096;

-- Constants for STATUS column of v$logmnr_contents

-- NOTE: Make sure that new ones match the values defined

-- in the krvfsri struct in krv0.h

VALID_SQL CONSTANT BINARY_INTEGER := 0;

INVALID_SQL CONSTANT BINARY_INTEGER := 2;

UNGUARANTEED_SQL CONSTANT BINARY_INTEGER := 3;

CORRUPTED_BLK_IN_REDO CONSTANT BINARY_INTEGER := 4;

ASSEMBLY_REQUIRED_SQL CONSTANT BINARY_INTEGER := 5;

HOLE_IN_LOGSTREAM CONSTANT BINARY_INTEGER := 1291;

---------------------------------------------------------------------------

-- Initialize LOGMINER

-- Supplies LOGMINER with the list of filenames and SCNs required

-- to initialize the tool. Once this procedure completes, the server is ready

-- to process selects against the v$logmnr_contents fixed view.

---------------------------------------------------------------------------

PROCEDURE start_logmnr(

startScn IN NUMBER default 0 ,

endScn IN NUMBER default 0,

startTime IN DATE default '',

endTime IN DATE default '',

DictFileName IN VARCHAR2 default '',

Options IN BINARY_INTEGER default 0 );

PROCEDURE add_logfile(

LogFileName IN VARCHAR2,

Options IN BINARY_INTEGER default ADDFILE );

PROCEDURE end_logmnr;

FUNCTION column_present(

sql_redo_undo IN NUMBER default 0,

column_name IN VARCHAR2 default '') RETURN BINARY_INTEGER;

FUNCTION mine_value(

sql_redo_undo IN NUMBER default 0,

column_name IN VARCHAR2 default '') RETURN VARCHAR2;

PROCEDURE remove_logfile(

LogFileName IN VARCHAR2);

发表回复取消回复

近期文章

近期评论

logminer

发表回复 取消回复

近期文章

近期评论

发表回复取消回复