This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
15100000 Invalid Parameter
Error Message
Parameter error. Possible causes:
- Mandatory parameters are left unspecified.
- Incorrect parameter types.
- Parameter verification failed.
Error description
This error code is reported if the arguments are invalid.
Possible Causes
The input arguments do not meet the API requirements, such as the value range, length, and format.
Solution
Refer to the API parameter description and change the parameters to valid values.
15100001 Maximum Number of Subscriptions or Result Sets Exceeded
Error Message
Over max limits.
Description
The number of database subscriptions or open result sets exceeds the maximum supported limit. The current maximum limit is 8 for both.
Possible Causes
- When on('dataChange') is called to subscribe to database changes, the number of subscriptions to the database has exceeded the maximum limit of 8.
- When getResultSet is called to obtain a database result set, the number of currently open result sets of the database exceeds the maximum limit of 8.
Solution
- If the number of subscriptions to the database has exceeded the maximum limit when on('dataChange') is called to subscribe to database changes, call off('dataChange') to cancel some subscriptions to the database and try again.
- If the number of currently open result sets of the database exceeds the maximum limit when getResultSet is called to obtain a database result set, call closeResultSet to close some open result sets and try again.
15100002 Parameter Configuration Changes
Error Message
Open existed database with changed options.
Description
When getKVStore is called to open an existing database, the options parameter passed in is inconsistent with the options parameter used when the database was created.
Possible Causes
The possible causes are as follows:
- An existing storeId is used to create a KV store.
- You want to change the options parameter of a KV store.
Solution
- When creating a KV store, do not use a duplicate storeId.
- Currently, the options parameter of a KV store cannot be changed. To apply the change, delete the KV store and create a KV store with the required options settings.
15100003 KV Store Corrupted
Error Message
Database corrupted.
Description
This error code indicates that the database is corrupted when APIs such as put, delete, get, and sync are called.
Possible Causes
The target KV store is corrupted.
Solution
- Restore the KV store from a backup file.
- If no backup file is available, delete the corrupted KV store and create a new one.
15100004 Failed to Find Data
Error Message
Not found.
Description
This error code indicates that no related data is found when APIs such as deleteKVStore, sync, and get are called.
Possible Causes
When no related data is found during operations such as deleting a database, querying data, or synchronizing data, the possible causes are as follows:
- The KV store to delete does not exist or has been deleted.
- The data queried does not exist or has been deleted.
- The KV store specified for the data synchronization operation does not exist or has been deleted.
Solution
- Before deleting a KV store, check that the KV store exists.
- When querying data in a KV store, check whether the query keywords are correct.
- Before synchronizing data, check that the related KV store is available.
15100005 KV Store or Result Set Closed
Error Message
Database or result set already closed.
Description
This error code indicates that the database or query result set is in the closed state when an API related to the database or query result set is called.
Possible Causes
The KV store or result set is closed manually before the operation.
Solution
- Obtain the KV store and try again.
- Obtain the result set and try again.
15100006 Failed to Update the Database Encryption Key
Error Message
Failed to update the key.
Error description
Failed to update the database encryption key when calling the rekey API.
Possible Causes
- The database was not created in encrypted mode (that is, encrypt is set to false) when the getKVStore API was called to create it.
- An internal error occurred during the key update.
Solution
- Before using the rekey API to update the key of an encrypted database, ensure that the current database is an encrypted database (that is, encrypt is set to true when the getKVStore API is called to create the database).
- Retry updating the key.