Issue Summary

After initially creating then deleting an Oauth 2.0 app link to Jira, then replacing it with an Oauth 1.0 app link, an error caused by ORA-00001 occurs. This occurs when using Confluence 10.2.11 with an Oracle 19c database.

Steps to Reproduce

1. Deploy Confluence 10.2.11 with Oracle 19c as the database.

2. Deploy Jira 11.3.5 with postgres (i.e. a totally separate database).

3. In Jira, start creating an Oauth 2.0 app link. Incorrectly set the redirect URI to https://host.docker.internal/jira, and selected READ permission. Then I copied the client ID & secret provided on the 'Incoming Link Details' screen. But I clicked 'Cancel' when I reached the 'Create outgoing link' screen.

4. In Confluence, start creating an Oauth 2.0 app link to Jira. Again, I set the redirect URI to https://host.docker.internal/jira and selected READ permission. When I got to the 'Incoming link details' screen, I clicked 'Close' instead of 'Configure Outgoing'.

5. I then deleted the app link from Confluence, then from Jira.

6. Then, starting from the Confluence side, I created an Oauth 1.0 app link to Jira (2-way), selecting the option "The servers have the same set of users and usernames". This is created successfully without any errors in the UI. I get redirected to Jira to complete the link, then back to Confluence. 

Expected Results

The app link is configured correctly with no errors surfacing in the atlassian-confluence.log.

Actual Results

Although the app link appears to get configured/created correctly, an error occurs in the atlassian-confluence.log:

2026-05-26 16:57:40,313 ERROR [http-nio-8090-exec-3 url: /confluence/rest/mywork/latest/status/notification/count; user: admin] [mywork.host.rest.ExceptionLogger] toResponse Exception thrown from REST resource
 -- url: /confluence/rest/mywork/latest/status/notification/count | userName: admin | referer: https://host.docker.internal/confluence/admin/listapplicationlinks.action | traceId: 6c19be120258c805
org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint [ATLUSER.SYS_C0058699]
...
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (ATLUSER.SYS_C0058699) violated 

Workaround

N/A, since there is no noticeable bad behavior. But this error should not occur. This also occurs in the 11.0.0-m148 pre-release (as this was first discovered in UAT testing a few weeks ago). Support Zips from both Confluence and Jira are attached.