Method and mechanism for relational access of recovery logs in a database system6618822Abstract The present invention is directed to a method and mechanism for accessing recovery log information in a database system. The data stored in the recovery log is presented as a relational database "view," which can be queried and accessed using relational database statements even though the underlying recovery log data may be stored in a non-relational format. According to an aspect of the invention, the recovery log data is thus encapsulated by the view presented to users of that data. Claims What is claimed is: Description BACKGROUND OF THE INVENTION
Object ID Timestamp Block Addr.
Note that this example log view has only three columns even though each log record contains four categories of information. As stated above, not all items of data in a log record must necessarily be represented in the log view. To access the information contained in the recovery log, a SQL statement is created to access a relational table having a table schema with the three columns shown. Since the user queries the log view rather than the underlying recovery logs, the user is thus fully insulated from having to know the particular format of the recovery logs. The log access mechanism performs the function of reformatting, for each record desired by the user, the raw recovery log data into the appropriate log view schema. By interposing a log access mechanism between the user and the underlying recovery log data, the SQL statement developed by a user is fully protected from any later changes in the content or data format of the underlying recovery logs. For example, consider if the recovery log format set forth above is changed to include an additional category of information. The format of each log record may be revised to include a "Transaction ID," such that each log record contains the following categories of information: (1) an object ID for the object being changed; (2) a timestamp for each record; (3) the changed data value; (4) the block address of the recovery log file; and (5) transaction ID. If the user does not seek to access the new category of information added to the log records, then the log view definition does not change. The log access mechanism can be configured to ignore the new category of information, but to format the recovery log data into the virtual columns of the existing log view definition. Thus, the user's SQL statement does not change even after the format of the underlying recovery logs are changed. The log view definition can also be changed to allow access to the new category of information. The log view definition can be modified to include an additional virtual column for the new information, as follows:
Object ID Timestamp Block Addr. Trans. ID
To access the new category of information, a user creates a SQL statement that references the "Trans. ID" column of the log view. Note that if a user does not wish to access the new category of information, then the user's existing SQL statement can still access the log view without any modifications. Since the existing column definitions have not been changed, but that only a new column has been added, any SQL statements that structured to access the old log view definition will still be usable. Consider if the recovery log format is changed to remove an existing category of information. The format of each log record may be revised to remove, for example, the "timestamp" category, such that each log record contains only the following categories of information: (1) an object ID for the object being changed; (2) the changed data value; and (4) the block address of the recovery log file. Under this circumstance, the log view definition does not have to change. However, in an embodiment, the log access mechanism will populate each column that corresponds to the deleted information with a NULL symbol. The log view definition could be implemented with unassigned columns to plan for access of recovery logs for which data or column definitions are unknown at present. The following is a revised log view definition which defines several unassigned columns:
Object ID Timestamp Block Addr. PH1 PH2 PH3
Columns PH1, PH2, and PH3 are placeholder columns that are unassigned, although accessible by a user. Placeholder columns are generic columns that can later be associated with additional categories of data e.g., via a separate mapping file. The placeholder columns can be used to select changes to known tables, column names, and values from recovery log streams. FIG. 1 depicts an architecture 100 for accessing recovery log information according to an embodiment of the invention. For each log view available on the system, a corresponding log access mechanism 106 is registered with the database system. Whenever a SQL statement 102 is received which seeks to access a registered log view, the appropriate log access mechanism 106 is called to return the recovery log data. The log access mechanisms 106 reads raw data from the recovery log 108, and returns recovery log data in the proper log view format. In an embodiment of the invention, the log access mechanism is registered with the database management system's "row-source" mechanism 104. The row-source mechanism 104 is a structure within the database system that can be used to retrieve each row of data from a data source in response to a SQL statement. The row source mechanism 104 handles heterogeneous access to the underlying database data. Thus, different types of objects can be accessed by using different types of access functions. Specific access functions are registered for the data object types in the database system. An example of such a row-source mechanism 104 can be found in the Oracle 8i database management system (available from Oracle Corporation of Redwood Shores, Calif.). In an embodiment of the invention, the row source mechanism 104 is responsible for receiving recovery log data that has been formatted into the proper log view format by the log access mechanism 106. The row source mechanism 104 then filters this data, and returns to the user rows of data corresponding to the rows sought by the SQL statement 102 (e.g., based upon the SQL statement's WHERE clause). Alternatively, user-define functions are registered with the database system to create "virtual tables" that create a view of data in the recovery logs. The user-defined functions dynamically retrieve and populate column values for a virtual table from underlying data sources (i.e., recovery logs). An example of a method and mechanism for implementing these user-defined functions is described in co-pending U.S. application Ser. No. 09/476,141, filed on even day herewith, which is hereby incorporated by reference in its entirety. In many database systems, the contents of recovery logs are encoded. For example, recovery log records may use Object IDs to reference objects instead of object names. As another example, recovery log records may use hexadecimal (base 16) or binary (base 2) representations of data values, instead of external data formats. According to an embodiment of the invention, the log access mechanism 106 utilizes a translator 110 to translate such internal data representations into external data formats. Translator 110 references metadata, such as metadata stored in a data dictionary 112, to implement the translation. Metadata is used in a database system to describe other items of data. For example, metadata regarding a database object provides correlation between an Object ID and its object name. Because metadata in a database changes over time, the translator needs to access metadata that corresponds to the correct time frame for the recovery log 108 being accessed. FIG. 2 depicts a process flow of an embodiment of the invention for accessing encoded recovery log information. If the recovery log data is encoded with internal data representations, then metadata is recorded for the recovery log to be accessed. This is performed by generating a dictionary file, which is a snapshot of the database system's data dictionary as of a particular point in time (202). Note that the dictionary file is generated to correspond to a specific time frame of recovery log records to be examined at a later date. Thus, a series of data dictionary snapshots could be taken at intervals over a period of time to ensure that an appropriate set of metadata always exists for any particular time frame of recovery log records. However, even if metadata has not been recorded for a relevant time frame, the contents of the data dictionary for that time frame can be derived based upon redo and undo log entries that have been recorded for the data dictionary. When it is desired to access the recovery logs, a list of the recovery logs to be accessed is generated (204). The time range of the log access can be specified (206) to limit the volume of recovery log records to be accessed. If a time range is not specified, then the entire contents of the named recovery logs are accessed. The invention can be configured to automatically generate a list of recovery logs to be accessed if a time range is specified, thus not requiring process action 204. At this point, the virtual log view table is available to be queried. A SQL statement can be issued to query the contents of the appropriate log view table (208). The requested information is thereafter retrieved from the recovery logs and returned in the proper format (210). FIG. 3 depicts the process flow for actions performed by an embodiment of the log access mechanism of the present invention. The log access mechanism reads a first record from a recovery log (304). Based upon the internal representations of the recovery log record, a determination is made whether a translation is needed (306). If translation is needed, then the appropriate metadata is accessed (308), and retrieved data items are translated into external data formats (310). The log access mechanism then returns the retrieved data in the proper log view format (312). A determination is then made as to whether more recovery log records are to be accessed (314). If so, then the process loops through process actions 304-314 until no more recovery log records are to be accessed. One advantage of the invention is that the "virtual" log view established over the recovery logs is not an actual database table; therefore, database storage is not absolutely required for the log view. In addition, since the log view is accessible similar to any ordinary relational database table, the entire spectrum of relational database query language statements (e.g., declarative joins, opening a cursor, etc.) can be applied against that log view. Thus, complex SQL queries can be effectively issued against the recorded log stream. Moreover, since the log files encompass information for multiple database tables, a single log view can provide accessible data for multiple tables over a broad range of time frames. The following describes column definitions for a recovery log view according to an embodiment of the invention used to access recovery logs in an Oracle 8i database:
COLUMN DATA TYPE DESCRIPTION
SCN NUMBER(15) System Change Number(SCN) that
identifies when a redo record is
generated. SCN is a monotonically
increasing number used to delineate
time
periods of change in the database
system.
TIMESTAMP DATE Date when redo record was generated.
THREAD# NUMBER Identifies thread which generated
the
redo record.
LOG_ID NUMBER Identifies log file which contains
the redo
record.
XIDUSN NUMBER Transaction Id Undo Segment Number.
A Transaction Identifier is
constructed
from the XIDUSN, XIDSLOT, and
XIDSQN and is used to identify the
transaction which generated the
change
XIDSLOT NUMBER Transaction Id Slot Number.
Identifies
the transaction table entry number.
XIDSQN NUMBER Transaction Id Sequence Number.
RBASQN NUMBER Uniquely identifies the log that
contained
the redo record among a group of
redo
logs. An RBA (redo block address) is
composed of the RBASQN, RBABLK,
and RBABYTE fields
RBABLK NUMBER The block number within the log file
RBABYTE NUMBER The byte offset within the block
UBAFIL NUMBER UBA (undo block address) File Number
identifying the file containing the
Undo
Block. The UBA is constructed from
the
UBAFIL, UBABLK, UBASQN, and
UBAREC and used to identify the undo
generated for the change
UBABLK NUMBER UBA Block Number
UBAREC NUMBER UBA Record Index
UBASQN NUMBER UBA Undo Block Sequence Number.
ABS_FILE# NUMBER Data Block Absolute File Number. The
ABS_FILE#, together with the
REL_FILE#, DATA_BLOCK#,
DATA_OBJ#, DATA_DOBJ, identify
the block changed by the transaction
REL_FILE# NUMBER Data Block Relative File Number. The
file number is relative to the
tablespace
of the object
DATA_BLOCK# NUMBER Data Block Number
DATA_OBJ# NUMBER Data Block Object number
DATA_DOBJ# NUMBER Data Block Data object number
identifying the object within the
tablespace
SEG_OWNER VARCHAR2 Name of the user owning the object
(30)
SEG_NAME VARCHAR2(81) Name of the structure the segment
was
allocated for (e.g. table name,
cluster
name etc.). Partitioned tables will
have a
segment name constructed of two
parts,
the table name followed by a comma
separated partition name (e.g.,
TableName,PartitionName).
SEG_TYPE NUMBER The type of the segment - numeric
form.
SEG_TYPE_NAME VARCHAR(17) The type of segment - string form
(e.g.
TABLE, INDEX, etc.)
TABLE_SPACE_NA VARCHAR2 Name of the tablespace
ME (30)
ROW_ID VARCHAR2(18) Row Id
SESSION # NUMBER Identifies session which generated
the
redo. A NULL value will be reported
if
the session number is not available
from
the redo log
SERIAL # NUMBER Serial number of the session which
generated the redo. The Session# and
Serial # can be used to uniquely
identify
the database session. A NULL value
will
be reported if the session number is
not
available from the redo log.
USER_NAME VARCHAR2 Name of the user initiating the
operation
(30) that generated the redo record.
SESSION_INFO VARCHAR2(4000) String containing: Login User Name,
Client Info, OS User Name, Machine
Name, OS Terminal, OS PID, OS
Program Name.
ROLLBACK NUMBER A value of TRUE identifies
operations
and SQL statements that were
generated
as a result of a Rollback request.
Otherwise, value is FALSE.
OPERATION VARCHAR2 Type of SQL Operation, e.g.,
(30) INSERT, DELETE, UPDATE, COMMIT,
and BEGIN_TRANSACTION.
SQL_REDO VARCHAR2 The SQL_REDO and SQL_UNDO
(4000) columns contain SQL compliant
statements that represent the
logical
REDO and UNDO operations decoded
from one or more archive log
records. A
NULL value indicates that no valid
SQL
statement can be generated for the
Redo
record. Some Redo records may not be
translatable. In this case, the
SQL_REDO
and SQL_UNDO will be NULL and the
STATUS column will contain the
string
`UNSUPPORTED`
SQL_UNDO VARCHAR2 SQL Undo. See above description of
(4000) SQL_REDO.
RS_ID VARCHAR2(30) Record Set Id. RS_ID uniquely
identifies
the set of records used to generate
a SQL
statement (a set may be a single
record).
It can be used to determine when
multiple records generate a single
SQL
statement (i.e., chained rows). The
RS_ID will be identical for all
records
within the set. The SQL statement
will
appear only in the last row the
record set.
The SQL_REDO and SQL_UNDO
columns for all other rows, within
the set,
will be NULL.
NOTE: The RS_ID/SSN pair together
provide a unique SQL Identifier for
every
SQL statement generated (see SSN
below).
SSN NUMBER SQL Sequence Number. The SSN can be
used to identify multiple rows, with
valid
SQL_REDO statements, that are
generated from a single Redo record.
All
such rows will have the same RS_ID
but
a unique SSN. The SSN is an
incrementing value starting at 1 for
each
new RS_ID. The RS_ID/SSN pair
together provide a unique SQL
Identifier
for every SQL statement generated by
LogViewR(see RS_ID above)
CSF NUMBER Continuation SQL Flag. CSF set to
True
indicates that a generated REDO_SQL
or
UNDO_SQL statement is larger than
the
maximum allowed size (4000
characters
in an embodiment). SQL statements
exceeding the maximum limit will
span
multiple rows.
When row spillage occurs the next
row
entry will contain the remainder of
the
SQL statement. The RS_ID,SSN pair
will be identical for all continued
rows
corresponding to the same SQL
statement. The last of the continued
rows
will have CSF set to FALSE to
indicate
the end of the SQL continuation.
STATUS VARCHAR2(16) Indicates status of the translation.
Some example values are: (a) NULL
value indicates a successful
translation;
(b) READ_FAILURE indicates an
internal operating system failure to
read
from the log file; (c)
TRANSLATION_ERROR indicates that
translation cannot be completed
(this
may be due to a corrupted log or an
out
of date dictionary file).
PH1_NAME VARCHAR2(32) Place Holder Column Name. Place
Holder Columns are generic columns
that
can be assigned to specified
database
table columns, e.g., via an optional
mapping file. These place holder
columns are used to select changes
to
known tables, column names, and
values
from the redo stream. For example,
"select xidusn, xidsqn, xidslot from
Application Debugging Example Database applications are often complex, and execution problems may arise if application developers or implementers are not be fully aware of all interdependencies between tables, particularly interdependencies caused by triggers or stored procedures. The present invention provides a vehicle for exploring complex interdependencies between different objects in the database, which facilitates the debugging of complex database applications. For purposes of this example, consider a database system used by a university for tracking alumni donations. The database table containing alumni donation information is the DONOR table. It is discovered that certain donor names are being erroneously deleted from the DONOR database. It is suspected that one of the database applications on the system is creating the error, but it is not known which application. The present example illustrates how access to recovery log information can be used to determine the root cause of the error. One approach to debugging this problem is to search the recovery logs for the operations that may have been erroneously performed. Thus, the recovery logs in this example are searched for DELETE operations that have been performed on the DONOR table. A date range and/or log file range can be used to narrow the initial scope of the search. The log view is filtered to find all DELETE within the specified date and log file ranges. If necessary, the appropriate data dictionary file is specified to produce results in the correct data format. Assume that the log view schema is as set forth in the above table. Using the above column definitions for the Oracle 8i database, the following SQL statement can be used to perform this initial search: SELECT XidUsn, XidSlot, XidSqn, sql_redo FROM log_view WHERE seg_name like `DONOR%` and operation=`DELETE`; In this example, "log-view" refers to the view of the recovery logs that has been established for the desired logs/time periods. An example of possible resulting output is as follows:
XIDUSN XIDSLOT XIDSQN SQL_REDO
1 7 1781 delete from UNIV.DONOR where DONORID = 105
AND NAME = `Donor6` AND CURR_AMOUNT =
10700 AND ALUM_REP_ID = 50 AND
ALUM_REP_NAME = `REP1` AND
ROWID = `AAABOKAABAAABOzAAF`;
This result indicates that the transaction referenced by this recovery log record has deleted a donor from the DONOR table. Thus, the next step is to search for all changes made by that same transaction. The following SQL statement can be used to implement this query: Select XidUsn, XidSlot, XidSqn, sql_redo FROM log_view WHERE XidUsn=1 and XidSlot=7 and XidSqn=1781; The following is an example of possible results returned to this query:
XIDUSN XIDSLOT XIDSQN SQL_REDO
1 7 1781 set transaction read write
1 7 1781 update UNIV.DONOR set CURR_AMOUNT = 10700,
LAST_AMOUNT = 7000
where ROWID = `AAABOKAABAAAEOzAAF`;
1 7 1781 insert into
UNIV.EXECDONOR(DONORID,NAME,CURR_AM
OUNT,
LAST_AMOUNT,ALUM_REP_ID,ALUM_REP_NA
ME)
values(105,`Donor6`,10700,7000,0,`CHANGEITNOW`);
1 7 1781 update UNIV.EXECDONOR set ALUM_REP_ID =
500,
ALUM_REP_NAME = `Rep10`where
ROWID = `AAABOLAABAAAEO4AAA`;
1 7 1781 delete from UNIV.DONOR where DONORID = 105
AND NAME = `Donor6` AND CURR_AMOUNT =
10700 AND ALUM_REP_ID = 50 AND
ALUM_REP_NAME = `REP1` AND
ROWID = `AAABOKAABAAAEOzAAF`;
1 7 1781 commit;
This output shows that the donor was deleted after insertion into the EXECDONOR table. Therefore, it follows that either the update to DONOR or the insertion to the EXECDONOR table caused the deletion. This may either occur due to faulty application logic or via a trigger or stored procedure. To find all triggers owned by UNIV the TRIGGERS table can be searched, as follows: Select trigger_name, trigger_event, trigger_body FROM TRIGGERS WHERE trigger_owner=`UNIV`; In this example, this query produces the following result:
TRIGGER_NAME TABLE_NAME TRIGGER_EVENT TRIGGER_BODY
DONOR_TRIG DONOR UPDATE begin
if updating then
if(:new.Curr_Amount
> 10000)
then
insert into
EXECDONOR_T EXECDONO UPDATE begin
RIG R if updating then
if(:old.Alum_Rep_Name =
`CHANGEITNOW`)then
delete from Univ
To obtain the text of the query from the recovery logs, the following SQL statement can be issued: SELECT sql_redo FROM log_view WHERE seg_name like `TRIGGER$` and operation=`INSERT` The following result is produced:
SQL_REDO
insert into
SYS.TRIGGER$(OBJ#,TYPE#,UPDATE$,INSERT$,DELETE$,
BASEOBJECT,REFOLDNAME,REFNEWNAME,DEFINITION,
WHENCLAUSE,REFPRTNAME,ACTIONSIZE,ENABLED,
PROPERTY,SYS_EVTS,NTTRIGCOL,NTTRIGATT,
ACTION #) values (5004,0,0,0,0,0,NULL,
NULL,NULL,NULL,
NULL,213,NULL,0,0,0,0,
`begin
if updating then
if(:new.Curr_Amount > 10000) then
insert into Univ.ExecDonor values(:new.DonorId,
:new.Name,
:new.Curr_Amount,
:new.Last_Amount,0,`CHANGEITNOW`);
end if;
end if;
end;
`);
insert into
SYS.TRIGGER$(OBJ#,TYPE#,UPDATE$,INSERT$,DELETE$,
BASEOBJECT,REFOLDNAME,REFNEWNAME,DEFINITION,
WHENCLAUSE,REFPRTNAME,ACTIONSIZE,ENABLED,
PROPERTY,SYS_EVTS,NTTRIGCOL,NTTRIGATT,
ACTION #) values (5005,0,0,0,0,0,NULL,
NULL,NULL,NULL,
NULL,161,NULL,0,0,0,0,
`begin
if updating then
if(:old.Alum_Rep_Name=`CHANGEITNOW`)then
delete from Univ.Donor where DonorId=:new.DonorId;
end if;
end if;
end;
`);
Reading the trigger body code, it can be determined that any time a donor gives more than $10,000 he/she is moved to the EXECDONOR table with a dummy Alumni representative. Once the alumni representative is assigned (in this case, as part of the same transaction), the old has determined that the deletion of a particular row in the DONOR table is associated with an update trigger on the EXECDONOR table is responsible for the application error. Audit Example The information contained in recovery logs is particularly useful for auditing purposes. Consider a banking database in which it is discovered that a customer's checking account balance is at approximately $20 whereas it should be at approximately $10,000. Using the present invention, the information in the recovery logs can be utilized to perform an audit trail analysis of the customer's bank account transactions. In this example, an initial query can be performed to find transaction involving this customer. A date range and/or log file range can be used to narrow the initial scope of the search. The log view is filtered to find all transaction involving the customer within the specified date and log file ranges. If necessary, the appropriate data dictionary file is specified to produce results in the correct data format. Assume that the log view schema is as set forth in the above table. Using the above column definitions for the Oracle 8i database, the following SQL statement can be used to perform this initial search: SELECT timestamp, scn, operation, xidusn, xidsqn, XidSlot, sql_redo FROM log_view WHERE row_id=`AAABOOAABAAAEPCAAA`; In this example, the row_id `AAABOOAABAAAEPCAAA` corresponds to the customer that is experiencing the error in his bank account balance. The following is an example of the result of this SQL statement:
TIMESTAMP OPERATION XIDUSN XIDSLOT XIDSQN SQL_REDO
03-AUG- UPDATE 1 11 1772 Update
1998: CUST.BANK_ACCOUNT
08:15:23 set
AMOUNT = 14900
where
ROWID =
`AAABOOAABAAAEPC
AAA`;
07-AUG- UPDATE 1 14 1778 Update
1998: CUST.BANK_ACCOUNT
10:20:30 set AMOUNT =
14700
where
ROWID =
`AAABOOAABAAAEPC
AAA`;
09-AUG- UPDATE 1 14 1785 Update
1998: CUST.BANK_ACCOUNT
11:21:31 set AMOUNT = 9700
where
ROWID =
`AAABOOAABAAAEPC
AAA`;
These results show that there were three different transactions to the customer's account. The SQL_UNDO field of the log_view table can be reviewed for the selected rows to find out the amount deducted from the customer's account for the first transaction (it can be seen that the second transaction deducted $200 and the third $14700-9700=$5000). If the account is supposed to contain $20000, then the amount deducted in the first transaction is approximately $20000-$14900-$5100). The following database statement can be issued to retrieve the desired sql_undo and sql_redo fields of the log_view table: SELECT sql_redo, sql_undo FROM log_view WHERE row_id=`AAABOOAABAAAEPCAAA`; This produces the following results:
SQL_REDO SQL_UNDO
update CUST.BANK_ACCOUNT set update CUST.BANK_ACCOUNT
AMOUNT = 14900 where set
ROWID = `AAABOOAABAAAEPCAAA`; AMOUNT = 20200 where
ROWID =
`AAABOOAABAAAEPCAAA`;
update CUST.BANK_ACCOUNT set AMOUNT = update CUST.BANK_ACCOUNT
14700 where set
ROWID = `AAABOOAABAAAEPCAAA`; AMOUNT = 14900 where
ROWID =
`AAABOOAABAAAEPCAAA`;
update CUST.BANK_ACCOUNT set AMOUNT = update CUST.BANK_ACCOUNT
9700 where set
ROWID = `AAABOOAABAAAEPCAAA`; AMOUNT = 14700 where
ROWID=
`AAABOOAABAAAEPCAAA`
Each individual transaction can be examined to determined the cause of the problem: SELECT scn, sql_redo, sql_undo FROM log_view WHERE XidUsn=1 and XidSlot=11 and XidSqn=1772; This statement produces the following:
SCN SQL_REDO SQL_UNDO
462758 set transaction read write;
462758 update CUST.BANK_ACCOUNT set update CUST.BANK_ACCOUNT set
AMOUNT = 14900 where AMOUNT = 20200 where
ROWID = ROWID =
`AAABOOAABAAAEPCAAA`; `AAABOOAABAAAEPCAAA`;
462758 update CUST.BANK_ACCOUNT set update CUST.BANK_ACCOUNT set
AMOUNT = 10500 where AMOUNT = 5200 where
ROWID = ROWID =
`AAABOOAABAAAEPCAAC`; `AAABOOAABAAAEPCAAC`;
462758 update CUST.BANK_ACCOUNT set update CUST.BANK_ACCOUNT
AMOUNT = 5100 where ROWID = set AMOUNT = 10100 where
`AAABOOAABAAAEPCAAB`; ROWID =
`AAABOOAABAAAEPCAAB`;
462758 update CUST.BANK_ACCOUNT set update CUST.BANK_ACCOUNT
AMOUNT = 15500 where set AMOUNT = 10500 where
ROWID = ROWID =
`AAABOOAABAAAEPCAAC`; `AAABOOAABAAAEPCAAC`;
462759 commit;
It can thus be determined that the account with rowid `AAABOOAABAAAEPCAAC` received the money that was deducted from the accounts of this customer and another customer with rowid `AAABOOAABAAAEPCAAB`. This example shows the immense power of the invention in performing auditing functions. Using the invention, a large amount of critical information can be accessed even without enabling the standard auditing feature of the database or of specialized application logic. There is no additional performance or storage penalty (as is the case of auditing) since the information is culled from recovery logs that are already being maintained to support recovery operation in the database system. Recovery Assistance Example The invention can assist in both time-based and change-based recovery by pinpointing the time or the System Commit Number (SCN) when an offending transaction executed. Time-based recovery allows the database to be restored to a particular instant of time. Change-based recovery allows the database to be restored to a particular SCN. In addition, the invention can be utilized to perform fined grained logical recovery. For example, it is possible to undo or redo a single change to the database. The invention can be utilized to undo a sequence of changes to a table, thus providing an undo based recovery mechanism. Recall from the prior example that transaction 1.11.1772 incorrectly transferred funds between accounts in a banking database. The sql_undo column of the log_view table can be accessed to perform an undo of specific changes in the database. The following SQL, selected from the SQL_UNDO column of the log_view table, rolls back the transaction 1.11.1772 to restore the correct balance in customer accounts:
SQL_UNDO
Update CUST.BANK_ACCOUNT set AMOUNT = 10500
where
ROWID = `AAABOOAABAAAEPCAAC`;
update CUST.BANK_ACCOUNT set AMOUNT = 10100
where
ROWID = `AAABOOAABAAAEPCAAB`;
update CUST.BANK_ACCOUNT set AMOUNT = 5200 where
ROWID = `AAABOOAABAAAEPCAAC`;
update CUST.BANK_ACCOUNT set AMOUNT = 20200
where
ROWID = `AAABOOAABAAAEPCAAA`;
Note that in this example, a single undo was performed against a specified data item, without requiring an entire transaction or a sequence of undo records to be applied. System Tuning Example Information in recovery logs can be used to generate a wealth of information for tuning a database. In conventional database systems, tuning and capacity planning procedures normally require that statistics be maintained for system activity of interest. The recorded statistics are later analyzed to determine if the system configuration is adequately set for desired performance characteristics. The drawback to this approach is that additional overhead and costs must be expended to generate and maintain these statistics. In the present invention, recovery logs can be mined to generate information that can be used to tune the system configuration. As an example, to see how the a table has been modified over a period of time (e.g., in a direct marketing database that records how productive customer contacts have been in generating revenues) the following query can be issued against the log_view table, with appropriate time frame and log set parameters set: SELECT seg_owner, seg_name, count(*) as Hits FROM log_view WHERE seg_name not like `% $` GROUP BY seg_owner, seg_name; The following is an example of results produced by this query:
SEG_OWNER SEG_NAME Hits
CUST ACCOUNT 384
SCOTT EMP 12
SYS DONOR 12
UNIV DONOR 234
UNIV EXECDONOR 325
UNIV MEGADONOR 32
These results provide statistics that can be used to tune the system, even if the DBA did not have the forethought to gather such statistics periodically. SYSTEM ARCHITECTURE OVERVIEW Referring to FIG. 4, in an embodiment, a computer system 620 includes a host computer 622 connected to a plurality of individual user stations 624. In an embodiment, the user stations 624 each comprise suitable data terminals, for example, but not limited to, e.g., personal computers, portable laptop computers, or personal data assistants ("PDAs"), which can store and independently run one or more applications, i.e., programs. For purposes of illustration, some of the user stations 624 are connected to the host computer 622 via a local area network ("LAN") 626. Other user stations 624 are remotely connected to the host computer 622 via a public telephone switched network ("PSTN") 628 and/or a wireless network 630. In an embodiment, the host computer 622 operates in conjunction with a data storage system 631, wherein the data storage system 631 contains a database 632 that is readily accessible by the host computer 622. In alternative embodiments, the database 632 may be resident on the host computer, stored, e.g., in the host computer's ROM, PROM, EPROM, or any other memory chip, and/or its hard disk. In yet alternative embodiments, the database 632 may be read by the host computer 622 from one or more floppy disks, flexible disks, magnetic tapes, any other magnetic medium, CD-ROMs, any other optical medium, punchcards, papertape, or any other physical medium with patterns of holes, or any other medium from which a computer can read. In an alternative embodiment, the host computer 622 can access two or more databases 632, stored in a variety of mediums, as previously discussed. Referring to FIG. 5, in an embodiment, each user station 624 and the host computer 622, each referred to generally as a processing unit, embodies a general architecture 705. A processing unit includes a bus 706 or other communication mechanism for communicating instructions, messages and data, collectively, information, and one or more processors 707 coupled with the bus 706 for processing information. A processing unit also includes a main memory 708, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 706 for storing dynamic data and instructions to be executed by the processor(s) 707. The main memory 708 also may be used for storing temporary data, i.e., variables, or other intermediate information during execution of instructions by the processor(s) 707. A processing unit may further include a read only memory (ROM) 709 or other static storage device coupled to the bus 706 for storing static data and instructions for the processor(s) 707. A storage device 710, such as a magnetic disk or optical disk, may also be provided and coupled to the bus 706 for storing data and instructions for the processor(s) 707. A processing unit may be coupled via the bus 706 to a display device 711, such as, but not limited to, a cathode ray tube (CRT), for displaying information to a user. An input device 712, including alphanumeric and other keys, is coupled to the bus 706 for communicating information and command selections to the processor(s) 707. Another type of user input device may include a cursor control 713, such as, but not limited to, a mouse, a trackball, a fingerpad, or cursor direction keys, for communicating direction information and command selections to the processor(s) 707 and for controlling cursor movement on the display 711. According to one embodiment of the invention, the individual processing units perform specific operations by their respective processor(s) 707 executing one or more sequences of one or more instructions contained in the main memory 708. Such instructions may be read into the main memory 708 from another computer-usable medium, such as the ROM 709 or the storage device 710. Execution of the sequences of instructions contained in the main memory 708 causes the processor(s) 707 to perform the processes described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware circuitry and/or software. The term "computer-usable medium," as used herein, refers to any medium that provides information or is usable by the processor(s) 707. Such a medium may take many forms, including, but not limited to, non-volatile, volatile and transmission media. Non-volatile media, i.e., media that can retain information in the absence of power, includes the ROM 709. Volatile media, i.e., media that can not retain information in the absence of power, includes the main memory 708. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise the bus 706. Transmission media can also take the form of carrier waves; i.e., electromagnetic waves that can be modulated, as in frequency, amplitude or phase, to transmit information signals. Additionally, transmission media can take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. Common forms of computer-usable media include, for example: a floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, RAM, ROM, PROM (i.e., programmable read only memory), EPROM (i.e., erasable programmable read only memory), including FLASH-EPROM, any other memory chip or cartridge, carrier waves, or any other medium from which a processor 707 can retrieve information. Various forms of computer-usable media may be involved in providing one or more sequences of one or more instructions to the processor(s) 707 for execution. For example, the instructions may initially be provided on a magnetic disk of a remote computer (not shown). The remote computer may load the instructions into its dynamic memory and then transit them over a telephone line, using a modem. A modem local to the processing unit may receive the instructions on a telephone line and use an infrared transmitter to convert the instruction signals transmitted over the telephone line to corresponding infrared signals. An infrared detector (not shown) coupled to the bus 706 may receive the infrared signals and place the instructions therein on the bus 706. The bus 706 may carry the instructions to the main memory 708, from which the processor(s) 707 thereafter retrieves and executes the instructions. The instructions received by the main memory 708 may optionally be stored on the storage device 710, either before or after their execution by the processor(s) 707. Each processing unit may also include a communication interface 714 coupled to the bus 706. The communication interface 714 provides two-way communication between the respective user stations 624 and the host computer 622. The communication interface 714 of a respective processing unit transmits and receives electrical, electromagnetic or optical signals that include data streams representing various types of information, including instructions, messages and data. A communication link 715 links a respective user station 624 and a host computer 622. The communication link 715 may be a LAN 626, in which case the communication interface 714 may be a LAN card. Alternatively, the communication link 715 may be a PSTN 628, in which case the communication interface 714 may be an integrated services digital network (ISDN) card or a modem. Also, as a further alternative, the communication link 715 may be a wireless network 630. A processing unit may transmit and receive messages, data, and instructions, including program, i.e., application, code, through its respective communication link 715 and communication interface 714. Received program code may be executed by the respective processor(s) 707 as it is received, and/or stored in the storage device 710, or other associated non-volatile media, for later execution. In this manner, a processing unit may receive messages, data and/or program code in the form of a carrier wave. In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention. For example, the reader is to understand that the specific ordering and combination of process actions shown in the process flow diagrams described herein is merely illustrative, and the invention can be performed using different or additional process actions, or a different combination or ordering of process actions. The specification and drawings are, accordingly, to be regarded in an illustrative rather than restrictive sense.
|
Same subclass Same class Consider this |
||||||||||