RE: Peoplesoft & Oracle

[Dawtrey, Lindsay L]

Title: Peoplesoft & Oracle

HI Lisa

Don't worry too much about fixing up the database it will only benefit the application.

You can spread the tablespaces around, I have also found that the default install scripts shove all the indexes into one tablespace, you can go ahead and add more and spread the indexes across disks if you are getting contention on them.

You can also change the tablespaces to LMTs no problem and you can us autoextend as you see fit, it won't affect PeopleSoft (unless you switch it off and the datafiles fill up of course).

You can also change SYSADM's default/sort tablespace.

Redo logs can be multiplexed and moved to seperate disks.

In short you can employ most of the good Oracle DBA standards without hurting Peoplesoft, it is quite flexible, some issues to be aware of are when changing default storage parameters for tables and indexes such as tablespace and initial and next extents etc, these changes also need to be made within Peoplesoft, the app will function just fine if you don't, but the next time a change (ddl) is made to that table from within PeopleSoft, it will revert back to the old settings when the table is re-created. Peoplesoft alters tables structures such as column changes, adds etc by creating and populating a 'temporary' table, dropping the original and then renaming the temporary one. I always check the generated alter script before running it anyway just to be sure that all is OK.

As far as the users accounts are concerned, they are there for two tier connections via sqlnet and apply to PeopleSoft versions prior to version 8, the app connects via the userid, gets some info from ps.psdbowner, psoprdefn and pslock, it then disconnects and re-connects as the schema owner usually SYSADM if default install values were used.

If the user connects via an application server, the userid in Oracle is not used as the appserver is already connected and does it's own password checking etc BUT the user still needs to exist in Oracle in the event of a password change being done, PeopleSoft issues an 'alter user' to Oracle which will choke if the user does not exist.

From PeopleSoft 8 all users excetp developers connect via a webserver/app server and the Oracle accounts are no longer needed, with the exception of developers, they still connect via a generic user, usually called 'people' which then re-connects as sysadm.

If the app was upgraded from 7 to 8 the users will not automatically have been deleted, also true is that when a user is removed from PeopleSoft prior to V8 the Oracle user is also not dropped, some cleaning up needs to be done here.

I have worked with PeopleSoft and Oracle for 8 years now, if you have any other problems feel free to contact my direct on [EMAIL PROTECTED]

 

Hope this helps.

Lindsay    

 

-----Original Message-----
From: Koivu, Lisa [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 11:09 PM
To: Multiple recipients of list ORACLE-L
Subject: Peoplesoft & Oracle

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 your 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

______________________________________________

Disclaimer and confidentiality note

Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the company. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of Standard Bank.

The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way.

Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference.

             _______________________________________________