This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:grid:creation:oacomp [2009/11/13 19:10] els |
admin:grid:creation:oacomp [2012/10/26 14:27] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | <html><div align="center"><span style="color:red">DRAFT</span></div></html> | ||
| + | |||
| ====== Creating an Omnidex Grid using OACOMP ====== | ====== Creating an Omnidex Grid using OACOMP ====== | ||
| Line 57: | Line 59: | ||
| </code> | </code> | ||
| - | Here is an example of an ENVIRONMENT declaration with several nodes: | + | Here is an example of an ENVIRONMENT declaration on an Omnidex Grid. |
| <code> | <code> | ||
| Line 85: | Line 87: | ||
| </code> | </code> | ||
| - | :!: Note that environment variables are sometimes allowed in the syntax. The following example below uses the automatic environment variable "OMNIDEX_NODE" in the index prefix for the database. The variable $OMNIDEX_NODE will be replaced by the node name. | + | Here is an example of a DATABASE statement on an Omnidex Grid. |
| <code> | <code> | ||
| Line 91: | Line 93: | ||
| node NODE01 | node NODE01 | ||
| type flatfile | type flatfile | ||
| - | indexprefix "{idx/$OMNIDEX_NODE/LIST_}" | + | indexprefix "{idx/node01/LIST_}" |
| node NODE02 | node NODE02 | ||
| type flatfile | type flatfile | ||
| - | indexprefix "{idx/$OMNIDEX_NODE/LIST_}" | + | indexprefix "{idx/node02/LIST_}" |
| node NODE03 | node NODE03 | ||
| type flatfile | type flatfile | ||
| - | indexprefix "{idx/$OMNIDEX_NODE/LIST_}" | + | indexprefix "{idx/node03/LIST_}" |
| node NODE04 | node NODE04 | ||
| type flatfile | type flatfile | ||
| - | indexprefix "{idx/$OMNIDEX_NODE/LIST_}" | + | indexprefix "{idx/node04/LIST_}" |
| </code> | </code> | ||
| Line 114: | Line 116: | ||
| [OPTIONS "options"] | [OPTIONS "options"] | ||
| [CARDINALITY n] | [CARDINALITY n] | ||
| - | [INDEXMAINTENANCE {AUTOMATIC | MANUAL | NONE}] | + | [INDEXMAINTENANCE <AUTOMATIC | MANUAL | NONE>] |
| - | [DATA CACHING …] | + | [DATA CACHING <NONE | DYNAMIC>] |
| [PARTITIONED BY "sql_predicates"] | [PARTITIONED BY "sql_predicates"] | ||
| </code> | </code> | ||
| - | :!: Note that environment variables are sometimes allowed in the syntax. The following example below uses the automatic environment variable "OMNIDEX_NODE" in the index prefix for the database. The variable $OMNIDEX_NODE will be replaced by the node name. | + | Here is an example of TABLE statements on an Omnidex Grid. |
| <code> | <code> | ||
| Line 137: | Line 139: | ||
| node NODE03 | node NODE03 | ||
| - | physical "{dat/$OMNIDEX_NODE/pro*.dat}" | + | physical "{dat/node03/pro*.dat}" |
| partition by "STATE in ('IN','MI','IA','MN','MT','ND','SD', | partition by "STATE in ('IN','MI','IA','MN','MT','ND','SD', | ||
| 'WI','IL','KS','MO','NE','AR','LA', | 'WI','IL','KS','MO','NE','AR','LA', | ||
| Line 144: | Line 146: | ||
| node NODE04 | node NODE04 | ||
| - | physical "{dat/$OMNIDEX_NODE/pro*.dat}" | + | physical "{dat/node04/pro*.dat}" |
| partition by "STATE in ('AZ','CO','ID','NM','NV','UT','WY', | partition by "STATE in ('AZ','CO','ID','NM','NV','UT','WY', | ||
| 'CA','HI','AK','OR','WA') and | 'CA','HI','AK','OR','WA') and | ||
| Line 163: | Line 165: | ||
| node NODE03 | node NODE03 | ||
| - | physical "{dat/$OMNIDEX_NODE/pro*.dat}" | + | physical "{dat/node03/pro*.dat}" |
| partition by "HOUSEHOLDS.HOUSEHOLD = INDIVIDUALS.HOUSEHOLD" | partition by "HOUSEHOLDS.HOUSEHOLD = INDIVIDUALS.HOUSEHOLD" | ||
| node NODE04 | node NODE04 | ||
| - | physical "{dat/$OMNIDEX_NODE/pro*.dat}" | + | physical "{dat/node04/pro*.dat}" |
| partition by "HOUSEHOLDS.HOUSEHOLD = INDIVIDUALS.HOUSEHOLD" | partition by "HOUSEHOLDS.HOUSEHOLD = INDIVIDUALS.HOUSEHOLD" | ||
| </code> | </code> | ||
| Line 183: | Line 185: | ||
| Omnidex network services must be started on every machine that contains grid nodes. No special options are required. | Omnidex network services must be started on every machine that contains grid nodes. No special options are required. | ||
| - | See how to [[admin:network:overview | configure and start the Omnidex Network Services (OdxNet)]]. | + | See how to configure and start the [[admin:network:overview | Omnidex Network Services]]. |