RE: PeopleSoft DBA Forum Re: How to make PeopleSoft read only
- There are various ways to make either the database or the tables in the
PeopleSoft schema read-only, but in some cases this is going to cause
problems in PeopleSoft.
You won't be able to
* log in via the PIA (because log-ins are logged to the database)
* submit and run jobs through the process scheduler (even if you could log
* run the process scheduler.
You need to be able to run DML against some tables.
Another method is to make the application read-only by making components
You can set this across the board by updating DISABLESAVE on PSPNLGRPDEFN,
but there are going to be some components that you do want to permit save,
and you will need to work this out.
(If you use the two schema approach suggested below - you could selectively
grant update access on the few tables that use still need to update, and
replace PSPNLGRPDEFN with a view in the mostly-read-only schema and manage
which components are not read-only in a data driven manner).
Go-Faster Consultancy Ltd.
tel: +44 (0)7771 760660
fax: +44 (0)7092 348865
Book: PeopleSoft for the Oracle DBA: http://www.psftdba.com
DBA Blogs: PeopleSoft: http://blog.psftdba.com, Oracle:
PeopleSoft DBA Forum: http://groups.yahoo.com/group/psftdba
>From: email@example.com [mailto:firstname.lastname@example.org]
>On Behalf Of Andy
>Sent: Thursday, January 17, 2008 9:27 PM
>Subject: PeopleSoft DBA Forum Re: How to make PeopleSoft read only
>I did this for a client a few versions back using PSoft 7.5 on Oracle.
> It'd probably still work, but no promises.
>High-level game plan:
>Add an entry in PSDBOWNER, so that it looks something like this:
>12:58:33 SYSADM @ fsprd @ 17-JAN-08 12:58:33 > select * from
>1 row selected.
>Create synonyms in the SYSREAD schema for all the objects in
>the SYSADM schema.
>Grant "SELECT" (only!) for all the SYSADM objects to the
>Iterate for a few failed logins -- to determine which tables
>need to be writable for the PSoft login -- and then drop the
>synonyms for that handful or tables. Create copies of those
>tables in the SYSREAD table. You might also need to do this
>for some other tools tables if you setup the process scheduler
>on the FSREAD DB (PSPRCSRQST, for example).
>Voila, now you have a read only copy (FSREAD) of your real DB (FSPRD).
>We also turned off global_names in Oracle and created a 2nd
>tnsnames.ora entry for the FSPRD database, so that "FSREAD.world"
>connected to the ORACLE_SID FSPRD.
>Hope that helps get you on the right track,
>acassidy at celerity-solutions.com
>--- In email@example.com, H NG <psoftneto@...> wrote:
>> Hi all,
>> Is it possible to put PeopleSoft read only?
>> What are the different scenarios?
>> Thanks for your help.
>> Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers
>PeopleSoft for the Oracle DBA is published by Apress - see
>The PeopleSoft DBA Forum is managed by http://www.go-faster.co.uk.
>Yahoo! Groups Links