Hey Tobias,
Seth Hiatt is correct, the cause of the issue is related to the publishing database account not having the CREATE TABLE privilege.
The database user needs to have CREATE TABLE in order to create the SDE_UUID_TEMP$ table. This table is required for replication in an Oracle geodatabase. It is used to discover the lineage of a given object via its GlobalID value. This is why you receive the error "No path for delta changes."
The table is created in the users' schema when synchronization is performed. After the sync, the rows are deleted, but the table remains. So you can revoke the CREATE TABLE privilege from the database user after running through the sync workflow one time. You don't have to do this for each service you publish, just once for the publishing user.
This issue does not occur when publishing as the data owner, because the data owner typically has CREATE TABLE.
http://desktop.arcgis.com/en/arcmap/10.6/manage-data/gdbs-in-oracle/replica-storage-oracle.htm
"When a geodatabase is synchronized with its relative geodatabase, a table is created in the user's schema of the replica geodatabase (the one that is sending the changes to the relative geodatabase) to track the lineages of altered datasets.
The SDE_UUID_TEMP$ table is used to discover the lineage of a given object via its GlobalID value.
The SDE_UUID_TEMP$ table is not removed when the session exits because the table will likely be reused in another session."
To resolve this issue, grant CREATE TABLE to the publishing database user. If you would like for that user to not have CREATE TABLE, revoke it after running the sync workflow successfully.
