TECHNICAL COMMUNICATION No. TC0419 Ed.
01
OmniPCX 4400 Nb of pages : 7 Date : 10-02-2003
URGENT
NOT URGENT TEMPORARY PERMANENT
SUBJECT : DATA BASE TRACE TOOLS
This technical communication is to be used on issues related to OmniPCX 4400 and OmniPCX
Enterprise data base.
1
OmniPCX 4400
DATA BASE TRACE TOOLS
CONTENTS
1. GENERAL.....................................................................................3
2. TOOLS.........................................................................................3
2.1. checkdb .................................................................................................... 3
2.2. checkinitrem trace .................................................................................... 3
2.3. traced ....................................................................................................... 3
2.4. srvtrace..................................................................................................... 4
2.5. mao .......................................................................................................... 4
2.6. multitool ................................................................................................... 5
2.7. ps –ef ........................................................................................................ 5
3. LOG FILES....................................................................................6
3.1. Translations .............................................................................................. 6
3.2. cmisd ........................................................................................................ 6
3.3. Exceptions................................................................................................. 6
Ed. 01 / 10-02-2003 1 TC0419
OmniPCX 4400
DATA BASE TRACE TOOLS
TC0419 2 Ed. 01 / 10-02-2003
OmniPCX 4400
DATA BASE TRACE TOOLS
1. GENERAL
This technical communication is to be used on issues related to OmniPCX 4400 and OmniPCX
Enterprise data base.
The types of issues are:
− incidents of type 2666 (on Main or Stand-By CPU),
− incidents of type 4351 on telephone application start-up ("initrem" phase: allocation of
remanents in memory),
− management errors with a "sql code",
− others issues : contact the Technical Support.
The collected informations with these tools must be attached with the database in an observation
sheet.
The database must be saved by using swinst. Copy the file:
− mao-dat in /usr4/BACKUP/DAYxx or WEEKxx or MONTHxx generated by a periodic backup or,
− mao-acc in /usr4/BACKUP/IMMED by an immediate backup.
These files are already compressed by swinst.
All tools described in this technical communication operate on the CPU on which they have been
launched. In case of duplication, these tools must also be launched on the Twin CPU.
2. TOOLS
You must be logged in mtcl account for using the tools described hereafter.
2.1. checkdb
This tool edits all the inconsistencies of the database. It simulates "initrem" on telephone application
launching.
2.2. checkinitrem trace
Go to the /usr3/mao directory.
Idem "checkdb" but with more traces.
2.3. traced
This tool is the tracor which will edit the informations depending on filters to be set. It is bit eqivalent
to "mtracer" used for telephone application traces. Therefore it must be used with other filter tools
described hereafter.
Ed. 01 / 10-02-2003 3 TC0419
OmniPCX 4400
DATA BASE TRACE TOOLS
Syntaxes
• traced
Run without option, the console is blocked. Stop it with the "Suppr" key on the console. The
traces are displayed on the console on which traced has been launched.
• traced &
The console is not blocked. Stop it with kill –9 xxx (xxx is its Pid).
• traced –d –1 <file_name> -s <size> -f <files_number>
♦ -d changes the tool to "daemon" mode i.e. it does not kill itself when the shell is finished
(return to login).
♦ –1 <file_name> : give a file name with its complete path to save the traces in this file
(no more screen display).
♦ –s <size> : size of log file in KB.
♦ –f <files_number> : number of traces to be stored.
This syntax is used regarding not reproducible/random issues. Several log files will be saved
with the same size defined by the option "-s".
To stop the tool, enter kill –9 on ist Pid.
Example
If the file name is trc and if the maximum number of files is 35, the name of these files will
be "trc-00" up to "trc-34". If there is a 36th file, it takes the place of the first one "trc-00" with
erasing of previous data and so on.
2.4. srvtrace
It must be used with traced. Each access to data base will be traced. The memory access are
ignored.
If informations of "rollback" type are displayed then there is a problem: the required modification is
denied.
If no information is displayed then there were only memory requests.
The informations correspond to sql commands transmitted to the data base server through the
telephone application/management and the cmisd process.
This tool operates in "flip-flop" mode. To stop the la trace, launch the tool. Some informations of
"service trace on" or "service trace off" type will be displayed even the traces were routed on files.
2.5. mao
The "mao" tool is also a filter. It must be launched with various options. Enter mao - ? to view these
options.
• Option trace +obj
• Option trace +gen
• Option -a acs all
TC0419 4 Ed. 01 / 10-02-2003
OmniPCX 4400
DATA BASE TRACE TOOLS
This option edits the status of table audited by the audit mao process ("access in progress"
and "locks").
Contact the Technical Support to define the options which must be launched in case of problem.
2.6. multitool
This tool can diagnose data base or memory errors regarding supervision keys or user MLA.
Run without option; only data are edited. Run with option, it can detect errors and repair them. It is
not really a trace tool but rather a diagnostics tool.
− "CHECK" option.
Select the [ 8] - Check Supervision and MLA menu.
This option checks the multiline and set supervision keys. The results are saved in the
/usr3/mao/superv.out text file.
This file is intended for Technical Support and R&D.
− "REPAIR" option.
First suppress any data base access: enter mao off.
Select the [ 8] + Repairing Supervision ou [ 9] + Repairing MLA menu.
Then choose the type of repair (memory or memory and disk).
The results are saved in the /usr3/mao/repairing.out file.
Check the access to data base with mao on.
The supervisions regarding the network users are not described.
2.7. ps –ef
This command is used to check if each process relative to data base is available. Up to Release 5.0
Ux, the following processes appear in the system start order (an evolution is possible):
− 1 cmisd process: manages the events in CMIP/CMISE format coming from applications,
− 1 sqlsrv process: is the father of several other ones,
− 1 maoagent process,
− 3 sqlsrv process: are started by maoagent (but they are its sons). They manage the read/write in
the data base. They are traced by srvtrace,
− 1 sqlsrv process: run for each hotel application,
− 1 sqlsrv process for phonebook application.
Ed. 01 / 10-02-2003 5 TC0419
OmniPCX 4400
DATA BASE TRACE TOOLS
3. LOG FILES
Various log files can be used except the ones supplied by traced.
3.1. Translations
Use swinst/7-Database tools/5-About last database operation for viewing the translations.
3.2. cmisd
Several SRVLOG.x files are located /tmpd. These files gives informations about the sqlsrv process
activity (process the requests to the data base).
3.3. Exceptions
The excvisu command edits the exceptions generated by the two main processes related to data
base: cmisd and maoagent.
TC0419 6 Ed. 01 / 10-02-2003
