ARTIFACTORY: Evidence Service Fails to Start After Upgrade with Oracle Error ORA-00955

Overview

After upgrading a JFrog Artifactory environment that uses an Oracle database, the JFrog Evidence service may fail during startup while attempting to run its initial database migration.

The failure occurs during the first Evidence migration, v001_evd_evidence.sql, when the service attempts to create the evd_evidence table. Because the migration cannot complete, the Evidence service exits, and the platform may not become fully healthy. This can result in Router/UI-dependent components reporting unhealthy status or returning HTTP 503 responses.


Symptoms

During startup, the Evidence service logs errors similar to the following:

[jfevd] [WARN ] [database.go:277] - Error executing query: ORA-00955: name is already used by an existing object [database]

[jfevd] [WARN ] [database_migration.go:236] - This error occurred when upgrading the database : 'ORA-00955: name is already used by an existing object'. [database]

[jfevd] [WARN ] [database_migration.go:237] - The failing statement is 'CREATE TABLE evd_evidence
(
    evidence_id NUMBER(19, 0) NOT NULL,
    evidence_predicate_type VARCHAR2(255) NOT NULL,
    evidence_created_at NUMBER(19, 0) NOT NULL,
    evidence_created_by VARCHAR2(64) NOT NULL,
    evidence_verified NUMBER(5, 0) NOT NULL,
    evidence_sha256 CHAR(64) NOT NULL,
    evidence_name VARCHAR2(255) NOT NULL,
    subject_name VARCHAR2(255) NOT NULL,
    subject_path VARCHAR2(1024),
    subject_repository VARCHAR2(64) NOT NULL,
    subject_sha256 CHAR(64) NOT NULL,
    CONSTRAINT evd_evidence_pk PRIMARY KEY (evidence_id)
)'. [database]

[jfevd] [ERROR] [database_migration.go:229] - Migration v001_evd_evidence.sql failed ! Rollback to latest successful migration. Err: ORA-00955: name is already used by an existing object [database]

[jfevd] [PANIC] [database_tenant_provider.go:84] - Failed to initialize single-tenant database failed to migrate tables of tenant: default, ORA-00955: name is already used by an existing object

You may also observe that the platform does not become fully healthy and that Router or UI requests fail with HTTP 503 responses.


Cause

The Evidence service is able to connect to Oracle successfully, but the initial Evidence database migration fails because an object named EVD_EVIDENCE already exists in the database.

This is typically caused by a partial Evidence schema creation from a previous startup or upgrade attempt. In this state, the database contains one or more Evidence-related objects, but the Evidence migration bookkeeping tables do not indicate that the initial migration completed successfully.

As a result, when the Evidence service restarts, it retries v001_evd_evidence.sql, attempts to create evd_evidence again, and fails with:

ORA-00955: name is already used by an existing object

Because the migration cannot complete, the Evidence service panics and exits.


Resolution

To resolve the issue, remove the partially created Evidence schema objects from the Artifactory database, then restart the platform services.

Before making any database changes, take a database backup or snapshot according to your organization’s backup procedure.

Connect to the Artifactory Oracle database as the Artifactory database user and run the following SQL statements:

DROP TABLE evd_sys_db_migration CASCADE CONSTRAINTS;
DROP TABLE evd_sys_db_lock CASCADE CONSTRAINTS;
DROP TABLE evd_evidence CASCADE CONSTRAINTS;
COMMIT;
EXIT;

After the tables are dropped, restart the Artifactory platform services.

On the next startup, the Evidence service should recreate the required schema objects and proceed beyond the v001_evd_evidence.sql migration. Once the Evidence service initializes successfully, Router and UI-dependent services should become healthy.


Validation

After restarting the platform, review the Evidence service logs and confirm that:

1. The Evidence service no longer fails with ORA-00955.

2. The migration v001_evd_evidence.sql completes successfully.

3. The Evidence service remains running.

4. Router and UI health checks return healthy status.

5. The platform no longer returns HTTP 503 due to unhealthy routing.

Additional Notes

This issue is specific to environments where the Evidence schema was only partially created, which can happen if Artifactory was stopped mid-migration due to a timeout, OOM kill, or manual intervention. The ORA-00955 error surfaces when Evidence retries that migration on the next startup and attempts to create an object that Oracle already has on record from the incomplete prior run.

If the issue persists after dropping the tables and restarting, review the Evidence service logs for additional Oracle errors, such as permission issues, object ownership mismatches, or database connectivity problems.