This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-22. For the latest, interactive version please visit https://mariadb.com/kb/.

Created: 9 months ago
Modified: 9 months ago
Type: article
Status: active
License: CC BY-SA / Gnu FDL

Attachments

No attachments exist

Error 1868: file was not purged because it is the active log file

Error Code	SQLSTATE	Error	Description
1868	HY000	ER_WARN_PURGE_LOG_IS_ACTIVE	file %s was not purged because it is the active log file.

Possible Causes and Solutions

Possible Causes and Solutions

This article doesn't currently contain any content. You can help!

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.

↑ MariaDB Error Codes 1800 to 1899 ↑
Error 1800: Unknown ALGORITHM
Error 1801: Unknown LOCK type
Error 1802: CHANGE MASTER cannot be executed when the slave was stopped with an error or killed in MTS mode
Error 1803: Cannot recover after SLAVE errored out in parallel execution mode
Error 1804: Cannot clean up worker info tables
Error 1805: Column count of is wrong. Expected, found. The table is probably corrupted
Error 1806: Slave must silently retry current transaction
Error 1807: There is a foreign key check running on table
Error 1808: Schema mismatch
Error 1809: Table in system tablespace
Error 1810: IO Read error
Error 1811: IO Write error
Error 1812: Tablespace is missing for table
Error 1813: Tablespace for table exists. Please DISCARD the tablespace before IMPORT
Error 1814: Tablespace has been discarded for table
Error 1815: Internal error
Error 1816: ALTER TABLE IMPORT TABLESPACE failed with error
Error 1817: Index corrupt
Error 1818: YEAR(%lu) column type is deprecated. Creating YEAR(4) column instead.
Error 1819: Your password does not satisfy the current policy requirements
Error 1820: You must SET PASSWORD before executing this statement
Error 1821: Failed to add the foreign key constaint. Missing index for constraint in the foreign table
Error 1822: Failed to add the foreign key constaint. Missing index for constraint in the referenced table
Error 1823: Failed to add the foreign key constraint to system tables
Error 1824: Failed to open the referenced table
Error 1825: Failed to add the foreign key constraint on table. Incorrect options in FOREIGN KEY constraint
Error 1826: Duplicate foreign key constraint name
Error 1827: The password hash doesn't have the expected format
Error 1828: Cannot drop column: needed in a foreign key constraint
Error 1829: Cannot drop column: needed in a foreign key constraint of table
Error 1830: Column cannot be NOT NULL: needed in a foreign key constraint SET NULL
Error 1831: Duplicate index defined on the table. This is deprecated and will be disallowed in a future release.
Error 1832: Cannot change column: used in a foreign key constraint
Error 1833: Cannot change column: used in a foreign key constraint of table
Error 1834: Cannot delete rows from table which is parent in a foreign key constraint of table
Error 1835: Malformed communication packet.
Error 1836: Running in read-only mode
Error 1837: When GTID_NEXT is set to a GTID, you must explicitly set it again after a COMMIT or ROLLBACK
Error 1838: The system variable cannot be set in stored procedures
Error 1839: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_MODE = ON
Error 1840: @@GLOBAL.GTID_PURGED can only be set when @@GLOBAL.GTID_EXECUTED is empty
Error 1841: @@GLOBAL.GTID_PURGED can only be set when there are no ongoing transactions (not even in other clients)
Error 1842: @@GLOBAL.GTID_PURGED was changed from to
Error 1843: @@GLOBAL.GTID_EXECUTED was changed from to
Error 1844: Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT, and both replicated and non replicated tables are written to
Error 1845: is not supported for this operation. Try
Error 1846: is not supported. Reason: Try
Error 1847: COPY algorithm requires a lock
Error 1848: Partition specific operations do not yet support LOCK/ALGORITHM
Error 1849: Columns participating in a foreign key are renamed
Error 1850: Cannot change column type INPLACE
Error 1851: Adding foreign keys needs foreign_key_checks=OFF
Error 1852: Creating unique indexes with IGNORE requires COPY algorithm to remove duplicate rows
Error 1853: Dropping a primary key is not allowed without also adding a new primary key
Error 1854: Adding an auto-increment column requires a lock
Error 1855: Cannot replace hidden FTS_DOC_ID with a user-visible one
Error 1856: Cannot drop or rename FTS_DOC_ID
Error 1857: Fulltext index creation requires a lock
Error 1858: sql_slave_skip_counter can not be set when the server is running with @@GLOBAL.GTID_MODE = ON
Error 1859: Duplicate entry for key
Error 1860: Long database name and identifier for object resulted in path length exceeding characters
Error 1861: cannot silently convert NULL values, as required in this SQL_MODE
Error 1862: Your password has expired. To log in you must change it using a client that supports expired passwords
Error 1863: Found a row in wrong partition
Error 1864: Cannot schedule event, relay-log name, position to Worker thread because its size exceeds of slave_pending_jobs_size_max
Error 1865: Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table
Error 1866: The binary log file is logically corrupted
Error 1867: file was not purged because it was being read by thread(s), purged only out of
Error 1868: file was not purged because it is the active log file
Error 1869: Auto-increment value in UPDATE conflicts with internally generated values
Error 1870: Row events are not logged for statements that modify BLACKHOLE tables in row format
Error 1871: Slave failed to initialize master info structure from the repository
Error 1872: Slave failed to initialize relay log info structure from the repository
Error 1873: Access denied trying to change to user (using password). Disconnecting.
Error 1874: InnoDB is in read only mode
Error 1875: STOP SLAVE command execution is incomplete: Slave SQL thread got the stop signal
Error 1876: STOP SLAVE command execution is incomplete: Slave IO thread got the stop signal
Error 1877: Operation cannot be performed. The table is missing, corrupt or contains bad data
Error 1878: Temporary file write failure
Error 1879: Upgrade index name failed, please use create index(alter table) algorithm copy to rebuild index
Error 1880: "

Error 1868: file was not purged because it is the active log file

Contents

Possible Causes and Solutions

Products

Services

Pricing

Resources

About Us

Download MariaDB