New object manager pointing to different database than enterprise DB
Hi Team,
We are going to have archiving enabled in our Production database and would like to access archive data(which would eventually reside in different Oracle database than production Oracle database) as per need basis. We are contemplating on two approaches and would like to know its pros and cons:-
1) EBC which is classic approach to configure views in our production application.
a) Benefit:- Authentication to access data is completely transparent to user.Unified experience to user.
b) Overhead:- Problem of creating EBC based views.
2) Create separate Object Manager in our production enterprise and point it to Archive Database. We would leverage same authentication(SSO Based) and would use same authorization model(Party/position/etc) in archive database as main production database using synonymns in archived database.