DW custom schema

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

DW custom schema

Laurel
This post was updated on .
Hi  Dear Erman!
Questions :)
We have 12.2.8 EBS and now there is project for Datawarehouse cloud where they massload all financial data. The  business logic will be in DWarehouse.

Options:
a) custom user  in EBS xxdwh  and select only  access to the bunch of  fina tables required

b) custom user in EBS xxdwh  and create apps.xx_customviews that will do select * from the base tables ( like apps.xx_ap_invoices as select * from ap_invoices_all)
create synonyms for the xxdwh user for those views
and grant select only  access to those views apps_xx_customviews  the xxdw..


For me option a) is more straighforward and no extra views in APPS schema ... I think option a) would be better for performance as well than b)


Q2)
for the cloud connections to db i was thinking that  we need to create a new db listener with TLS enabled,
as the inhouse EBS itself  we use db listener  port 1521 TCP without TLS .

2 listeners on db tier  with TLS and not TLS should be possible/supported  in  EBS ?  Need only custom IFILE  manually configured  for the custom listener. Any pointers  to  documents how to do it would be appreciated :)

What are your reccomendations ?
Thx alot! :)
best wishes,Laurel
Reply | Threaded
Open this post in threaded view
|

Re: DW custom schema

ErmanArslansOracleBlog
Administrator
Hi Laurel,

I'm fine. I hope all good on your side as well.

Option A seems simple and suitable. It will give you direct table access: , so minimizing query complexity.
In terms of Performance, it will be potentially better, especially due to simple queries, and no-overhead of view processing. You can also have fine-tuned grant access capabilities with that.

Having multiple listeners on EBS database shouldn't be unsupported.
For TLS/SSL database listener related question check ->

Enabling SSL or TLS in Oracle E-Business Suite Release 12.2 (Doc ID 2143101.1)
section 6: Encrypting Database Network Traffic Using ANO/ASO (Optional)