Omnidex has a rich set of diagnostics that can be used to diagnose problems. Most diagnostic files are created and send under the direction of Technical Support, as they often contain information that is difficult to read.
Omnidex writes diagnostics to a file named odxdebug.log, which is located in the same directory as the Omnidex Environment File. This can be overridden if needed.
The following diagnostics settings can be set, depending on the type of problem:
| Setting | Description |
|---|---|
| ON | Show the entrances and exits from the main Omnidex API routines. |
| OFF | Disable all diagnostics |
| ALL | Enable all diagnostics |
| CONNECT | Show diagnostics valuable when experiencing problems with connection to an Omnidex environment. |
| DATABASE | Show diagnostics valuable when experiencing problems accessing the underlying database. |
| EXCEPTION | Show diagnostics for any exceptional condition. |
| FILESYSTEM | Show diagnostics valuable when experiencing problems accessing the underlying filesystem. |
| FLATFILE | Show diagnostics valuable when experiencing problems accessing raw data files. |
| NETWORK | Show diagnostics valuable when experiencing problems with network connections. |
| OPTIMIZER | Show diagnostics valuable when experiencing problems with optimizing queries. |
| QUALIFY | Show diagnostics valuable when experiencing problems with qualifying against Omnidex indexes. |
| GRID | Show diagnostics valuable when experiencing problems on an Omnidex Grid. |
| FILE=<filename> | Write diagnostics to the named file, rather than the default file, “odxdebug.log”. |
Diagnostics can be set by using the SET DEBUG statement.
set debug on
Alternatively, diagnostics can be set through the OMNIDEX_DEBUG environment variable in the operating system. This environment variable must be set prior to launching the Omnidex program, such as OdxSQL or Omnidex Network Services.
Linux: export OMNIDEX_DEBUG="on" Windows: set OMNIDEX_DEBUG=on
See also: