User guide

$ dccmd forget all
d. Use the following command to find the process identifiers (pids) associated
with the DataChannel visual processes:
$ findvisual
e. Use the following commands to stop each DataChannel visual process:
$ kill -9 <cnsw_pid>
$ kill -9 <logw_pid>
$ kill -9 <amgrw_pid>
$ kill -9 <cmgrw_pid>
f. Use the following commands to restart each DataChannel visual process:
$ cnsw
$ logw
$ amgrw
$ cmgrw
g. Use the dccmd command to start all DataChannel applications:
$ dccmd start all
h. Use the dccmd command to verify that all of the DataChannel applications
started properly:
$ dccmd status all
More specifically, make sure that the UBA application associated with the
DataChannel that you configured for the Alcatel-Lucent SAM 5620
LogToFile Technology Pack is running.
i. Watch the output of the status switch to verify that all the necessary
processes are running. If these processes are running, run the tail utility on
the log file for the UBA by issuing a command similar to the following
command:
tail -f DATA_CHANNEL_HOME/log/proviso.log | grep UBA.<channel_number>.
<collector_number> | more
where:
Variable Meaning
<channel_number> Specifies the channel number.
<collector_number> Specifies the collector number (for example,
100) that you specified when you configure
this UBA Bulk Collector.
The trailing dash (–) after <collector_number> Removes extraneous log messages from your
view. That is, the trailing dash guarantees
that the command displays only those
messages that are generated by your
application. The first set of messages relate
to syntax checks.
The following table identifies some events to watch for during the syntax
check:
Event Meaning
The UBA application starts successfully, but
then stops running.
Typically, this event occurs because of a
licensing issue.
The bulk adapter design file might be
corrupted.
This event causes a syntax error before the
UBA application connects to the database.
48 Alcatel-Lucent 5620 SAM LogToFile 2.3.0.0 Technology Pack Installation and User Guide