-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
7
-
In our company we use Golden Gate to replicate databases. Our DBAs found following issues which prevent Golden Gate from replicating schema used by Stash:
1. Indexes and constraints with system generated names are not supported
CONSTRAINT_TYPE TABLE_NAME
------------------------------- ------------------------------
P AO_CFE8FA_BUILD_STATUS
P AO_FB71B4_PUBLIC_KEY
P AO_6978BB_RESTRICTED_REF
P AO_6978BB_PERMITTED_ENTITY
U WEIGHTED_PERMISSION
P PLUGIN_SETTING
P - Primary Key
U - Unique Key
Solution: Primary/Unique keys and indexes assigned to them should be named
2. Tables With No Primary Key or Unique Index
Table Rows
------------------------ --------
CS_ATTRIBUTE 906
HIBERNATE_UNIQUE_KEY 1
HT_STA_PR_ACTIVITY
ID_SEQUENCE 14
Solution: Primary or Unique keys should be created for those tables.
- is related to
-
BSERV-2699 Cannot initialize Oracle schema
-
- Closed
-
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-3385] Enable Oracle Golden Gate replication
This would be incredibly helpful to our company based on local performance vs clones to other sites globally. Ultimately we would like stash to handle replication with multiple masters but if we can handle it by being able to use tools like GG for the DB and other means to replicate the repos on disk then that is a step in the right direction.
Hi Stanisław,
We are still gauging interest in this issue. We have received very few requests for supporting replicated databases. It is not on any roadmap as of 23/09/2014. As with any feature request many different factors are weighed up when choosing to implement and support a feature. More information can be found in our implementation of new features policy.
Regards,
Jason Hinch
Stash Developer
Stanislaw Kodzis
added a comment - When can we expect this issue resolved?
Regards,
Stanisław
Is there any resolution to this issue? My company would love to put Golden Gate in place, but the PK issue makes it more of a customer one-off then a clean install of Jira.