Cisco CRS-1 - Carrier Routing System Router, Руководство администратора

Страница: 298 / 436

Chapter 10 Managing Cisco CRS Historical Reporting
Importing Historical Data from Data Files
10-12
Cisco Customer Response Solutions Administration Guide, Release 4.1(1)
The table that follows lists the options and parameters for the
runTruncateHistDBLogs command.
For example, the following command truncates the db_cra_log.ldf database
transaction log file to 250 MB:
runTruncateHistDBLogs “db_cra” 250
Importing Historical Data from Data Files
If the database on the CRS server is down, historical records are cached to be
written to the database. If the number of records exceeds the cache maximum, the
additional records are written to files stored in the wfaavid\SQLdata directory.
These data files are also generated if the historical record queue is exceeded when
the database on the Expansion server and CRS server are down.
You can import the data from these files into the historical database by running
the osql command for all data files in the wfavvid\SQLData directory.
The syntax for the osql command is:
osql -E -S <server>\CRSSQL -i <datafilename>
The table that follows lists the options and parameters for the osql command on
the CRS server.
Parameter Description
“db_cra” Truncates the db_cra_log.ldf database transaction log file.
“tempdb” Truncates the tempdb.ldf database transaction log file.
size Size in MB to which the file or files will be truncated.
Note
For the ldb_cra_log.ldf file, specify a size value no less than
one-fourth the size of the ldb_cra.mdf database.
Option or Parameter Description
-E -E – Use entrusted source
-S server/CRSSQL -S – Server
server/CRSSQL – Name of your server, appended by ID for CRS SQL