Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> Re: Peoplesoft & Oracle

Re: Peoplesoft & Oracle

From: david davis <>
Date: Tue, 28 Jan 2003 19:53:38 -0800
Message-ID: <>


What you have described is a PeopleSoft database with bad habits. The usage of dictionary managed tablespaces is normal but will probably change over time. While the PeopleSoft installation guide and delivered scripts create using the older method, you can certainly using the locally managed approach.

There is a document "red paper" on PeopleSoft customer connection titled PeopleSoft 8 Batch Performance on Oracle Database that is probably worth downloading. Path to the documents is products|peopletools|peopletools resource library.

Alas, documentation from the vendor is weak. Or as I have discovered postively brilliant in comparison to other vendors who say nothing "configure Oracle the same as SQL Server {doh}".

Can't really comment on the autoextend. Use it myself to delay going through change mgmt process. :-) PeopleSoft does deliver a script to autoextend but it is not the default. So that was a deliberate choice of the DBA.

It is normal for all application users to connect via the schema owner. The users Oracle account is used during the logon process for cross authentication with application security and the database. This changes to certain degree in PeopleTools 8 family.

I believe at some point in PeopleSoft 8, you will have the possibilty of losing the individuals Oracle userid and connection is via the app server (tuxedo) and connection id.

The user when accessing PeopleSoft is only connected to Oracle using their userid for an extremely brief time so it is really what is set for the SYSADM account that is key. I have as standard practice set the the default tablespace and temp tablespace after userids are created. Just being tidy besides shows up on my monitoring reports.

The entire database on one disk. That isn't the vendor's fault. They state before installing the database to modify the scripts to specify the filesystem locations. One disk or a hundred, that is the DBA's responsibility.

You can certainly move tablespaces, redo logs around as needed. On the other hand there are things you should be careful with (eg.).

Don't just change the password for SYSADM except via the PeopleSoft security administration (unless you wanted to be hunted down by users).

Also applies to user accounts.

Moving tables to other tablespaces should first be done via the application designer tool first which updates the meta-data (peopletools tables).

Objects that maintain PeopleTools meta-data should be first created in App Designer and then built using the generated SQL script.

I would suggest reading the Administration guide which covers things such as the DDL Model, security administration etc. Also, the installation guide has some stuff for "tuning" (snicker).

A couple of reports available for the application "DDDAUDIT" & "SYSAUDIT".

Our environment is very stable.

PeopleSoft HRMS 7.51, PeopleTools 7.58
HP/UX 10.20, Oracle 7.3.4

{Hoping to upgrade to 9i and HP/UX 11i this year}

All batch processing is via Control-M scheduler and not the vendor delivered program launcher aka process scheduler. All access via external processes connect using their own userid (O/S authenticated for batch) with explicit grants. Nobody (clients/developers/support staff) has direct access to SYSADM except for the DBA's.

Our reporting environment is a hybrid of 3.22, 7.0, 7.51 custom structures based on PeopleTools 7.58. The environment is populated via SQL Server DTS (el cheapo ETL)and database links. We have previously used Oracle Replication (lots of problems on Oracle 7 (maybe it was the 600 snapshots)) but now use custom triggers etc.

If you can dream of it, you can do it. Its just the administration can be a bit of work until you understand it and have things setup in a fashion that makes sense for you.


David Kurtz posted a document "PeopleSoft for the Oracle DBA" on customer connection. Check out his site He may have a more current document (mine is 1999, but then I am used to out of date software).


I have looked at them but don't generally rely on them. I do believe there is a Peoplesoft list that might be worth joining.

Ensure you have access to customer connection. You might as well be tortured like the rest of us trying to find things.

David Davis, DBA
Manulife Financial

>From: "Koivu, Lisa" <>
>To: Multiple recipients of list ORACLE-L <>
>Subject: Peoplesoft & Oracle
>Date: Tue, 28 Jan 2003 13:08:59 -0800
>Hello everyone,
>My apologies for bombarding the list with more questions than answers as of
>late. This one is pretty desparate.
>For those of you who support Peoplesoft databases - Are there any websites
>that you frequent to check for quirks, weird anomalies, etc. related to
>specific Peoplesoft/Oracle combination?
>I've just inherited this environment. It's Oracle 8.1.7 on AIX. I don't
>know the version of AIX and I don't know the version(s) of the Peoplesoft
>modules being used. However I am seeing some very weird things - not the
>least of which is every tablespace is dictionary managed, all are on
>autoextend, there are 600 open database accounts but it looks like the app
>only connects as SYSADM, all users have SYSTEM for default/temp ts, the
>entire freaking database is on one disk, all redologs (one in each group)
>are on one disk, etc., etc., etc. The list goes on. I'm afraid to turn
>this environment upside down and fix it because management is only
>interested in keeping the system alive, not improving it. The previous DBA
>is elusive at best, probably because I yelled at him last year after
>catching him creating objects on the fly in my databases :)
>I'll do the obvious things like add redologs and check backup and recovery,
>etc. User error is extraordinarily high in this environment. Everything
>else I am afraid to touch without doing my homework first. Any websites,
>suggestions, comments, etc. would be greatly appreciated.
>The only good thing to come of all this is I'M BAAAAAAAAAAAAAACK in Unix
>again !!! Woo Hoo!!!!!!!
>Lisa Koivu
>Oracle Database Administrator
>Fairfield Resorts, Inc.
>5259 Coconut Creek Parkway
>Ft. Lauderdale, FL, USA 33063

MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.
Please see the official ORACLE-L FAQ:
Author: david davis

Fat City Network Services    -- 858-538-5051
San Diego, California        -- Mailing list and web hosting services
To REMOVE yourself from this mailing list, send an E-Mail message
to: (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).
Received on Tue Jan 28 2003 - 21:53:38 CST

Original text of this message