Cisco 3.3 User Manual
Page 360
Chapter 9 System Configuration: Advanced
RDBMS Synchronization
9-32
User Guide for Cisco Secure ACS for Windows Server
78-16592-01
•
Oracle 7—Contains the files
accountActions.sql
and
testData.sql
.
The
accountActions.sql
file contains the Oracle 7 SQL procedure needed
to generate an accountActions table. The
testData.sql
file contains Oracle
7 SQL procedures for updating the accountActions table with sample
transactions that CSDBSync can process.
•
Oracle 8—Contains the files
accountActions.sql
and
testData.sql
.
The
accountActions.sql
file contains the Oracle 8 SQL procedure needed
to generate an accountActions table. The
testData.sql
file contains Oracle
8 SQL procedures for updating the accountActions table with sample
transactions that CSDBSync can process.
•
SQL Server 6.5—Contains the files
accountActions.sql
and
testData.sql
.
The
accountActions.sql
file contains the Microsoft SQL Server 6.5 SQL
procedure needed to generate an accountActions table. The
testData.sql
file contains Microsoft SQL Server 6.5 SQL procedures for updating the
accountActions table with sample transactions that CSDBSync can process.
Cisco Secure ACS Database Recovery Using the accountActions
Table
Because the RDBMS Synchronization feature deletes each record in the
accountActions table after processing the record, the accountActions table can be
considered a transaction queue. The RDBMS Synchronization feature does not
maintain a transaction log/audit trail. If a log is required, the external system that
adds records to the accountActions table must create it. Unless the external system
can recreate the entire transaction history in the accountActions table, we
recommend that you construct a transaction log file for recovery purposes. To do
this, create a second table that is stored in a safe location and backed up regularly.
In that second table, mirror all the additions and updates to records in the
accountActions table.
If the database is large, it is not practical to replay all transaction logs to
synchronize the CiscoSecure user database with the third-party system. Instead,
create regular backups of the CiscoSecure user database and replay the transaction
logs from the time of most recent backup to bring the CiscoSecure user database
back in synchronization with the third-party system. For information on creating
backup files, see