Differences

This shows you the differences between two versions of the page.

Link to this comparison view

admin:optimization:config:diagnostics [2012/02/13 22:43]
doc created
admin:optimization:config:diagnostics [2016/06/28 22:38]
Line 1: Line 1:
-~~NOTOC~~ 
  
-{{page>:​top_add&​nofooter&​noeditbtn}} 
- 
-====== Administration:​ Optimizing Queries ====== 
- 
-===== Configuring Omnidex ===== 
- 
- 
-[[admin:​optimization:​config:​home|Overview]] | 
-[[admin:​optimization:​config:​optimizations|Optimizations]] | 
-[[admin:​optimization:​config:​thresholds|Thresholds]] | 
-[[admin:​optimization:​config:​timeouts|Timeouts]] | 
-**[[admin:​optimization:​config:​diagnostics|Diagnostics]]** 
- 
----- 
- 
-==== Diagnostics ==== 
- 
-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.  ​ 
- 
-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.  ​ 
- 
-<​code>​ 
-set debug on 
-</​code>​ 
- 
-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. 
- 
-<​code>​ 
-Linux: 
- 
-export OMNIDEX_DEBUG="​on"​ 
- 
-Windows: 
- 
-set OMNIDEX_DEBUG=on 
- 
-</​code>​ 
- 
-=====  ===== 
----- 
-\\ 
-**[[admin:​optimization:​config:​timeouts|Prev]]** ​ 
- 
- 
-====== Additional Resources ====== 
-See also: 
-{{page>:​admin:​optimization:​see_also&​nofooter&​noeditbtn}} 
- 
-{{page>:​bottom_add&​nofooter&​noeditbtn}} 
 
Back to top
admin/optimization/config/diagnostics.txt ยท Last modified: 2016/06/28 22:38 (external edit)