AIK uses same database ID from both Test and Production (if on same server)
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Description
Almost 2 months after upgrading production to version 22, our DBA team just figured out why we've been having trouble with the RMAN backup process since the upgrade.
They found that the database ID is the exact same number for both the test and production databases. Both were built from the standard AIK menu, so cloned from your pre-configured database.
They've fix this locally for our database (by changing the database ID's to be unique).
Resolution
This could be prevented in the AIK (or noted in the AIK document), but it seems that, at this late stage of Aleph, that is not going to happen.
- Article last edited: 6-Apr-2017