Table of Contents
Locate C:\Program Files\TriVium\cdm.ini file to look for SQLEXPRESS restart delay value.
Locate C:\Program Files\TriVium\cdm.ini file to set value to 11 for low level logs to enable.
The different logs are MSPM, MSDM, MSRCDM, ASAdvPrs and by default these value are set to
3.
Now all log related files are placed under one folder called Logs under TriVium folder. Locate
C:\Program Files\TriVium\Logs folder, which contains MSRCDM, MSDM, MsAdvPrs &
MSDM_FialedToWriteDB log files.
The directory in which this log file is kept is also configurable so that an install can select a
location with sufficient space for the amount of data it wants to keep just in case it needs to
recover from data loss.
Once MSRCDM reads the raw CDR it goes to SMDR for parsing. In case of any failure in parsing,
the error is logged along with the raw CDR that failed. The error is clear indicative of the exact
failure and any failure of parsing should result in only that CDR being ignored and MSRCDM
continuing normally.
The MSRCDM then sends the parsed structured CDR to either a buffer (for purposes of collation)
or to the MSDM via a UDP socket connection. Also, any socket error, CES is handled in a way
that the MSRCDM continues normally and moves on to the next data.
Click Start->Program Files->TriVium->CES, select Tools->Import Raw CDR and Import Raw CDR
window will open.
Browse to the location where Raw CDRs are available, click Import button to proceed and
you will see a Finished Importing Call Records window to confirm raw CDRs are imported into
the CES.
Browse to the location where Structured CDRs are available, click Import button to proceed
and you will see an Import Structured Data window to confirm Structured CDRs are imported
into the CES.
10
Once the record set is populated, a DB bulk update is done. The bulk update is actually a nontransactional bulk insert. In case bulk update fails for any reason, typically either because data
has characters, which should normally be escaped or SQL has problems and database is
unavailable, we go back sanitize the data for use with SQL in the array, close the DB
connection, re-open the DB connection and retry the bulk.
If failure repeats, then the array is dumped (appended) into another log file,
msdm_FailedToWriteToDB<date>.txt, and MSDM then proceeds as normal to get more data
from MSRCDM.
Locate C:\Program Files\TriVium\Logs\MSDM_FailedToWriteToDB111809.txt file to view the logs.
11
In case of failure to do bulk update to the DB, there is an entry in the std. MSDM log file to
indicate this along with the information that the records are available in the following <file>, i.e.,
the msdm_FailedToWriteToDB<date>.txt .
12
Browse to the location where MSDM_FailedToWriteToDB log files are available, click Import
button to proceed and you will see an Import Structured Data window to confirm Structured
CDRs are imported into the CES.
Note:
1. Currently we are not able to import msdm_baddata<date>.txt file using import tool
available in the CES.
14