All objects in a PeopleSoft database should explicitly be set NOPARALLEL, so parallel query should not occur during the PeopleSoft application (except when refreshing CBO statistics). regards _________________________ David Kurtz Go-Faster Consultancy Ltd. tel: +44 (0)7771 760660 fax: +44 (0)7092 348865 mailto:david.kurtz@xxxxxxxxxxxxxxx web: www.go-faster.co.uk Book: PeopleSoft for the Oracle DBA: http://www.psftdba.com <http://www.psftdba.com/> DBA Blogs: PeopleSoft: http://blog.psftdba.com <http://blog.psftdba.com/> , Oracle: http://blog.go-faster.co.uk <http://blog.go-faster.co.uk/> PeopleSoft DBA Forum: http://groups.yahoo.com/group/psftdba _____ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Andrew Kerber Sent: Tuesday, September 21, 2010 3:25 PM To: ORACLE-L Subject: instance_groups=<instance name> Importance: High I recently inherited some Peoplesoft databases, and I noted this setting for instance_groups: instance_groups=<instance_name>, These are 10gR2 on windows that we are preparing to migrate to 11gr2 on Linux. According to the documentation, this value was suggested by Oracle Support to prevent parallel query from running on other instances. Can we accomplish the same things just by setting the instances value to 1 at the table level? Also, wouldn't the 11g parameter parallel_force_local accomplish the same purpose? -- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'