RDB Error Codes
NOTE
This topic describes only module-specific error codes. For details about universal error codes, see Universal Error Codes.
14800000 Internal Error
Error Message
Inner error.
Description
This error code is reported if an internal error is thrown.
Possible Causes
View the error log to determine the cause of the error. Possible causes include the following:
- The SQL statement fails to be executed.
- The internal state is abnormal.
- There is API that is incorrectly used.
- A system error, such as null pointer, insufficient memory, unexpected restart of data service, I/O error, IPC exception, and JS engine exception, occurs.
Solution
- Check whether SQL statements and predicates are correctly used.
- Check whether a closed object is reused.
- Check whether the APIs are correctly used.
- If the problem persists, ask the user to restart or upgrade the application or upgrade the device version.
14800001 Invalid Arguments
Error Message
Invalid arguments. Possible causes: 1. Parameter is out of valid range; 2. Missing GROUP BY clause.
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
Modify the arguments according to the API reference.
14800010 Invalid Database Path
Error Message
Failed to open or delete the database by an invalid database path.
Description
This error code is reported if the database fails to be opened or deleted due to invalid database path.
Possible Causes
The RDB store path is invalid.
Solution
Check the RDB store path.
14800011 Database File Corrupted
Error Message
The current operation failed because the database is corrupted.
Description
The operation failed due to a database exception.
Possible Causes
The database file is damaged and incomplete, the database FD is incorrectly operated, or the database memory is illegally accessed.
Solution
If data loss is acceptable, delete the RDB store and create a new one. Otherwise, restore the RDB store from the backup file. For details, see Database Backup and Restore.
14800012 Empty Result Set or Invalid Position
Error Message
ResultSet is empty or pointer index is out of bounds.
Description
This error code is reported if the result set is empty or the specified location is invalid.
Possible Causes
The result set is empty, or the specified row number in the result set is out of range [0, m - 1]. m is ResultSet.rowCount.
Solution
Check whether the result set is empty or whether the specified row number is out of range.
14800013 Null Column Value or Column Data Type Incompatible With the API Called
Error Message
Column index is out of bounds.
Description
This error code is reported if the column value is null, or the column data type is incompatible with the API called.
Possible Causes
- The column number is out of the range [0, n - 1]. n is ResultSet.columnCount.
- The API called does not support the type of the column data.
Solution
- Check whether the column number of the result set is out of range.
- Check whether the column data type is supported.
14800014 Target Instance Closed
Error Message
The target instance is already closed.
Description
The target instance is closed.
Possible Causes
The instance was not opened successfully, or the owning instance has been closed (for example, the close method has been called on a ResultSet/RdbStore object, or the commit/rollback method has been called on a Transaction object).
Solution
Open the RDB store or obtain the result set.
14800015 RDB Store Not Respond
Error Message
The database does not respond.
Description
This error code is reported if the RDB store does not respond.
Possible Causes
A read, write, attach, or detach operation is being performed, and cannot be complete within the specified time (2s by default).
Solution
- Try again later.
- If the attach or detach API is used, modify the value of waitTime to increase the waiting duration.
14800016 Duplicate RDB Alias
Error Message
The database alias already exists.
Description
This error code is reported if the RDB store alias already exists.
Possible Causes
The RDB store alias already exists.
Solution
Stop the attach operation or change the RDB store alias.
14800017 Key Configuration Changed
Error Message
StoreConfig is changed.
Description
This error code is reported if the key configuration of the RDB store has been modified.
Possible Causes
Key configuration, such as area, securityLevel, or the read/write permission of the RDB store is changed.
Solution
Restore the original configuration if required. Otherwise, delete the old RDB store, use the new configuration to create a new RDB store, and import the data to the new RDB store.
Check whether the read/write permission on the database file is modified using chmod. Ensure that the current user has sufficient permissions to read and write the database file.
14800018 No Match
Error Message
No data meets the condition.
Description
This error code is reported if no data matching the search criteria is found.
Possible Causes
The SQL statement used for query is incorrect, or the data does not exist.
Solution
Use the correct query statement or add data.
14800019 SQL Query Statement Required
Error Message
The SQL must be a query statement.
Description
This error code is reported if the SQL statement used is not a query statement.
Possible Causes
The SQL statement used for query does not meet specifications.
Solution
Use SQL statements that comply with specifications.
14800020 Key Damaged or Lost
Error Message
The secret key is corrupted or lost.
Description
This error code is reported if obtaining the secret key fails.
Possible Causes
The root key is lost, the application does not have the permission to read the key file, or the key file is damaged.
Solution
- Check the permission for accessing the key file and the content of the key file.
- Rebuild or restore the database.
14800021 SQLite: Generic Error
Error Message
SQLite: Generic error. Possible causes: Insert failed or the updated data does not exist.
Description
This error code is reported if an SQLite generic error occurs.
Possible Causes
An SQL statement is executed to perform any of the following operations:
- Insert or update data in a table that is not created.
- Insert or update data in a column that does not exist.
- Call an undefined function. For details, see SQLITE_ERROR.
Solution
Analyze the SQL statement and identify the error.
14800022 SQLite: Asynchronous Callback Request Aborted
Error Message
SQLite: Callback routine requested an abort.
Description
This error code is reported if the asynchronous callback request is aborted.
Possible Causes
- The callback in a custom function in SQLite is aborted.
- See SQLITE_ABORT.
Solution
Check that the hook functions (callbacks) of SQLite are implemented correctly.
14800023 SQLite: Access Denied
Error Message
SQLite: Access permission denied.
Description
This error code is reported if the SQLite access is denied.
Possible Causes
- SQLite does not have the required permission to access or modify a file.
- See SQLITE_PERM.
Solution
- Ensure that the file is not read-only. If the file is read-only, remove the read-only property.
- Check that the caller has the required permissions to access the file or folder.
- Check whether the file system is read-only. If yes, change it to writable.
- Check that the database file is not being used by another process. Terminate the process that is using the file.
- When handling permission issues, ensure that you have the permission to change the permissions on the file or folder.
14800024 SQLite: Database File Locked
Error Message
SQLite: The database file is locked.
Description
This error code is reported if the SQLite database file is locked.
Possible Causes
- Two processes of the same application, for example, UIAbility and DataShareExtensionAbility, perform addition, deletion, and modification operations in the same database, or processes in the same group of different applications perform addition, deletion, and modification operations in the same database via the group.
- See SQLITE_BUSY.
Solution
- Avoid concurrent database operations from processes.
- Wait for a while and try again.
14800025 SQLite: Database Table Locked
Error Message
SQLite: A table in the database is locked.
Description
This error code is reported if an SQLite database table is locked.
Possible Causes
- The database file to write has been locked by another process. A transaction is being performed in the RDB store, or the write attempt is blocked by a lock mechanism.
- See SQLITE_LOCKED.
Solution
- Check that the database file is not being written by another process or thread.
- Check that no write operation is performed after a transaction is started and before the transaction is committed.
- Check whether the write operation is blocked by other lock mechanisms (such as file locks).
- Check that the database connection instance is closed after the database operation is complete.
- In a multi-thread environment, ensure that synchronization mechanisms, such as locks, are used to prevent data races.
14800026 SQLite: Insufficient Database Memory
Error Message
SQLite: The database is out of memory.
Description
This error code is reported if the database memory is insufficient.
Possible Causes
The data volume is too large or the memory allocated is insufficient.
Solution
Reduce the data volume or increase the memory allocated.
14800027 SQLite: Attempt to Write a Read-only Database
Error Message
SQLite: Attempt to write a readonly database.
Description
This error code is reported if a write operation is invoked on a read-only database.
Possible Causes
- An attempt is made to write an SQLite database file that is opened in read-only mode. The access is denied because the target file is in a read-only file system or the database is marked as read-only.
- See SQLITE_READONLY.
Solution
- Ensure that the caller has the permission to write data to the database file.
- If the file system is read-only, change it to read/write.
- Check that no read-only parameter is used when the database is opened.
14800028 SQLite: I/O Error
Error Message
SQLite: Some kind of disk I/O error occurred.
Description
This error code is reported if a disk I/O error occurs.
Possible Causes
The possible causes include the following:
- The target file does not exist.
- The target file is read-only.
- The disk space is insufficient.
- The target file is damaged.
- See SQLITE_IOERR.
Solution
- Check whether the file path is correct and whether the file exists.
- Check that the file is not read-only.
- Delete unnecessary files to ensure sufficient disk space.
- Check that the caller has permissions to read and write the file.
14800029 SQLite: Database Is Full
Error Message
SQLite: The database is full.
Description
This error code is reported if the SQLite database is full.
Possible Causes
The data volume is too large or the disk space is insufficient.
Solution
Reduce the data volume or increase the disk space.
14800030 SQLite: Unable to Open the Database File
Error Message
SQLite: Unable to open the database file.
Description
This error code is reported if the database file fails to be opened.
Possible Causes
- The file does not exist, and the RDB store fails to be created.
- The file exists, but the database file is damaged.
- The caller does not have the permission to access the file using SQLite.
- The disk space is insufficient.
- See SQLITE_CANTOPEN.
Solution
- Check that the database file path is correct and the caller has the permission to read and write the file.
- Check that the disk space is sufficient.
14800031 SQLite: TEXT or BLOB Exceeds the Limit
Error Message
SQLite: TEXT or BLOB exceeds size limit.
Description
This error code is reported if the size of the text or BLOB exceeds the limit.
Possible Causes
- The result set returned exceeds the size limit that SQLite can process.
- See SQLITE_TOOBIG.
Solution
Divide the query operation into multiple small queries, which process part of the data each time.
14800032 SQLite: Abort Due to Constraint Violation
Error Message
SQLite: Abort due to constraint violation.
Description
This error code is reported if the database operation violates the constraint rule and is aborted.
Possible Causes
- The data write operation violates the constraints on the database integrity.
- See SQLITE_CONSTRAINT.
Solution
Check whether the data to be inserted or updated violates the constraints.
14800033 SQLite: Data Types Mismatch
Error Message
SQLite: Data type mismatch.
Description
This error code is reported if the data types mismatch.
Possible Causes
- The data type specified in an SQL statement does not match the type of the data stored in the database.
- See SQLITE_MISMATCH.
Solution
Check the type of the data in the specified column in the SQL statement and ensure that the type of the data to be inserted, updated, or queried matches the data type of the column.
14800034 Incorrect Use of SQLite Library
Error Message
SQLite: Library used incorrectly.
Description
This error code is reported if the SQLite interface is used incorrectly.
Possible Causes
- The database operation or context is incorrect. This error usually occurs in the following cases:
- The next operation is performed before a database operation is complete.
- A database operation is performed on a closed database connection.
- A released or invalid database object is used to perform data operation.
- See SQLITE_MISUSE.
Solution
- Check that proper synchronization mechanisms like locks are used between database operations.
- Check that a database connection is opened before use and closed after the operation is complete.
- Check that all database objects are correctly released after being used.
14800041 Type Conversion Failure
Error Message
Type conversion failed.
Description
Type conversion failed.
Possible Causes
The data type of the specified column does not match the type of the data obtained from resultSet.
Solution
Ensure the data type of the specified column matches the type required by the corresponding API.
14800047 WAL File Size Exceeds the Default Limit
Error Message
The WAL file size exceeds the default limit.
Description
This error code is reported if the WAL file exceeds 512 MB, which is the default limit.
Possible Causes
Data is added, deleted, and modified continuously without closing the read transaction or result set.
Solution
Check for unclosed result sets or transactions.
Close all result sets or transactions.
14800050 Failed to Obtain the Subscription Service
Error Message
Failed to obtain the subscription service.
Description
The error code is reported if the subscription service failed to be obtained.
Possible Causes
The platform does not support service subscription.
Solution
Deploy the subscription service on the platform.
14801001 Stage Model Required
Error Message
The operation is supported in the stage model only.
Description
This error code is reported if this operation is not performed on the stage model.
Possible Causes
The context is not a stage model.
Solution
Perform the operation on the stage model.
14801002 Invalid dataGroupId in storeConfig
Error Message
Invalid data group ID.
Description
This error code is reported if the dataGroupId parameter is invalid.
Possible Causes
The dataGroupId is not obtained from the AppGallery.
Solution
Obtain dataGroupId from the AppGallery and pass it to storeConfig correctly.
14800051 Inconsistent Distributed Table Type
Error Message
The type of the distributed table does not match.
Description
This error code is reported if different distributed table types are set for the same database table.
Possible Causes
The same database table is set with different DistributedType.
Solution
A database table can be synchronized either between devices or between device and cloud.