"rebuildIndexes"
JSON DB "rebuildIndexes"
action rebuilds all indexes or specified indexes
The "rebuildIndexes"
action rebuilds all indexes or specified indexes. It can optionally return a list of indexes that need to be rebuilt.
Request examples
Minimal request
{ "api": "db", "authToken": "replaceWithValidAuthtoken", "action": "rebuildIndexes", "params": { "tableName": "athlete" } }
{ "api": "db", "apiVersion": "1.0", "requestId": "2", "authToken": "replaceWithValidAuthtoken", "action": "rebuildIndexes", "params": { "tableName": "test1" } }
{ "api": "db", "apiVersion": "1.0", "requestId": "3", "authToken": "replaceWithValidAuthtoken", "action": "rebuildIndexes", "params": { "databaseName": "ctreeSQL", "ownerName": "admin", "tableName": "athlete" }, "responseOptions": { "binaryFormat": "hex", "dataFormat": "objects", "numberFormat": "string" }, "debug": "max" }
{ "authToken": "replaceWithValidAuthtoken", "errorCode": 0, "errorMessage": "" }
{ "authToken": "replaceWithValidAuthtoken", "requestId": "2", "errorCode": 0, "errorMessage": "" }
{ "authToken": "replaceWithValidAuthtoken", "requestId": "3", "debugInfo": { "request": { "authToken": "replaceWithValidAuthtoken", "api": "db", "action": "rebuildIndexes", "params": { "databaseName": "ctreeSQL", "ownerName": "admin", "tableName": "athlete" }, "apiVersion": "1.0", "requestId": "3", "responseOptions": { "binaryFormat": "hex", "dataFormat": "objects", "numberFormat": "string" }, "debug": "max" }, "serverSuppliedValues": { "databaseName": "ctreeSQL", "ownerName": "admin" }, "errorData": { "errorData": null }, "warnings": [] }, "errorCode": 0, "errorMessage": "" }
Use the rebuildIndexes API action to rebuild all indexes or specified indexes
The "params"
property is an object that contains an action's parameters. Each action defines its own required and optional properties.
Property summary
"params"
property summariesProperty | Description | Default | Type | Limits (inclusive) |
---|---|---|---|---|
specifies the name of a database | Defaults to the | string | 1 to 64 bytes | |
specifies the unique name of a schema in a database |
| string | 1 to 64 bytes | |
specifies the name of a table | Required - No default value | string | 1 to 64 bytes |
The "databaseName"
property is an optional string that specifies the database that contains the tables. It defaults to the database name supplied at login.
Note
In the API Explorer, "defaultDatabaseName"
is set to "ctreeSQL"
in the "createSession"
action that happens at login.
A zero-length
"databaseName"
is invalid.Its limits are from 0 to 64 bytes.
If the
"databaseName"
property is omitted or set tonull
, the server will use the default database name specified at login.If no default database is specified during
"createSession"
,"defaultDatabaseName"
will be set to the"defaultDatabaseName"
value that is specified in theservices.json
file.
The "ownerName"
property is an optional string from 1 to 64 bytes that specifies the account that owns an object.
The "tableName"
property is a string containing the name of a table.
A table name may contain up to 64 ASCII characters and must not start with a number.
Properties summary
You cannot modify a table while it is in use. When a table has no activity for a default of 2 seconds, it will be closed so you can modify it.
When a table is in use, the following actions return an error, such as -8 or 4012:
"alterTable"
"rebuildTables"
"deleteTables"
"createIndex"
"deleteIndexes"
"rebuildIndexes"
"runSqlStatements"
A table is in use when any account is performing one or more of the following actions with the table:
"insertRecords"
"updateRecords"
"deleteRecords"
"truncateRecords"
"getRecords..."
Has open cursors on the table.
Has open transactions on the table (such "createTransaction").
Modify the
SQL_IDLE_WAKE
startup configuration setting to change the number of seconds the server waits before closing a table. A larger number keeps the table open longer for better performance. A smaller number allows you to modify the table sooner.Modify the
SQL_IDLE_WAKE
startup configuration setting to change the number of tables the server keeps open after they are no longer being actively used. A larger number caches more tables and improves performance. A smaller number allows you to modify tables sooner.