Re: Multiple (SYSADM) Schemas in a Peoplesoft Database
- From: Karl Arao <karlarao@xxxxxxxxx>
- To: hkchital@xxxxxxxxxxxxxx
- Date: Thu, 21 May 2009 00:05:34 +0800
My client also thought of this idea, and tested it. They reverted to the 1
sysadm schema - 1 database model because of some security issues. I can't
remember the details :)
They're using PeopleSoft as a service, hosting different companies payroll
and related services.
And from the performance standpoint, single cache...more users...more
workload...then at some point you will be hitting some
concurrency/coherency/contention issues.
- Karl Arao
http://karlarao.wordpress.com
On Wed, May 20, 2009 at 10:12 PM, Hemant K Chitale
<hkchital@xxxxxxxxxxxxxx>wrote:
>
> I believe that Peoplesoft does allow multiple schemas (the default is
> SYSADM, so the multiples could be SYSADM_1, SYSADM_2 etc) in a single
> Oracle Database.
> This could support seperate business units in one Oracle instance.
>
> Has anyone implemented this in Production ? Particularly for Financials
> modules -- (GL, Payables, Assets)
>
> (Currently, we do have multiple BUs in the single SYSADM schema but I am
> asked to explore two options :
> a. Seperate Database Instances
> b. Seperate schemas in one Database Instance )
>
>
>
> Hemant K Chitale
>
> http://hemantoracledba.blogspot.com
>
>
>
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
Other related posts:
