Database

A self-hosted Cascade CMS instance keeps all of its content and configuration in one relational database. These articles cover creating that database on each supported vendor, backing it up, and keeping its size under control.

Cascade CMS ships a database to import rather than a schema to create, so each of these starts from the supplied file.

• MySQL
• SQL Server — also needs its isolation level set to snapshot.
• Oracle

• Creating a database backup — the vendor commands, and when to take one.
• Database size management tips — what tends to grow (file uploads, asset versions, messages) and which settings bound it.

Specific errors you might hit when starting Cascade CMS, upgrading it, or running it against each vendor. Search the exact text of your error if it isn't listed here.

Startup and upgrade

• Could not acquire change log lock — left behind by an ungraceful shutdown; clear the lock row.
• Error executing SQL DELETE FROM cxml_history_item — upgrading to Cascade 8 on MySQL older than 5.7.11.

MySQL

• Can't create table — the database collation is wrong.
• Can't create/write to file — usually anti-virus on-access scanning.
• Packet for query is too large — raise max_allowed_packet.
• MySQL 8: Public Key Retrieval is not allowed — after moving to MySQL 8.

SQL Server

• Could not establish a secure connection (PKIX path building failed) — the driver can't validate the server certificate.
• Could not establish a secure connection: "Unexpected rethrowing" — add sslProtocol=TLSv1.2 to the connection string.

Oracle

• ORA-22275: invalid LOB locator specified — an Oracle bug; apply the patch set update.

For the tools that run against a live database from inside the CMS, see Database Tools.