RE: 11gR2 - what patch level?
- From: "Vishal Gupta" <vishal@xxxxxxxxxxxxxxx>
- To: <info@xxxxxxxxxxxxxxx>, <dbvision@xxxxxxxxxxxx>
- Date: Tue, 6 Jul 2010 09:37:18 +0100
There is a slight problem with too many objects. If happen to consolidate many
peoplesoft installations into separate schema in the same database, then it can
create problems while dropping schema in order to refresh is from some other
peoplesoft installation/golden copy.
I have blogged about it at following link.
http://www.vishalgupta.com/blog/2008/08/24/slow-drop-user/
Regards,
Vishal Gupta
http://www.vishalgupta.com
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx on behalf of Go-Faster Consultancy Ltd.
Sent: Tue 06/07/2010 07:37
To: dbvision@xxxxxxxxxxxx
Cc: 'oracle-l'
Subject: RE: 11gR2 - what patch level?
Exactly, and those 61000 objects are going to carry on not being used. If
you had created the tables 'segment creation deferred' and they haven't been
physically created yet, then they aren't going to be created. If you do
occasionally use a new table then it is only a one time overhead.
If you want to force just the tables to be created in PeopleSoft (though I
don't think I would), it is possible to add the 'SEGMENT CREATION IMMEDIATE'
clause the DDL model.
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
DBA Blogs: PeopleSoft: http://blog.psftdba.com, Oracle:
http://blog.go-faster.co.uk
PeopleSoft DBA Forum: http://groups.yahoo.com/group/psftdba
>-----Original Message-----
>From: oracle-l-bounce@xxxxxxxxxxxxx
>[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Nuno Souto
>Sent: Tuesday, July 06, 2010 6:56 AM
>Cc: 'oracle-l'
>Subject: Re: 11gR2 - what patch level?
>Importance: High
>
>That's on a fully populated installation, with all features being used.
>In our HR/Payroll db of which only HCM is being used, we have
>29000 tables and 34000 indexes. Of these only about 2000 have
>any data, everything else is empty. Or at least, that's what a
>full export shows.
>That is my worry.
>
>--
>Cheers
>Nuno Souto
>dbvision@xxxxxxxxxxxx
>
>
>Go-Faster Consultancy Ltd. wrote,on my timestamp of 6/07/2010 7:17 AM:
>> Although I haven't played with this feature in conjunction with
>> PeopleSoft myself, I don't think it would be a huge problem.
>>
>> Most of the empty tables in PeopleSoft are PeopleSoft
>Temporary Records
>> - these are normal database tables used for temporary
>working storage by
>> Application Engine programs. PeopleSoft (since version 8)
>creates many
>> identical temporary tables and allocates different tables to
>different
>> instances of the same program. It is better than multiple
>concurrent
>> processes sharing the same temporary record (and before
>someone askes
>> they don't use Global Temporary Tables because they are
>Oracle specific).
>>
>> You tend to get the same temporary tables reused repeatedly.
> You might
>> have 10 copies of a table, but if you only ever run one
>instance of a
>> program which uses that table at any one time, then normally
>you should
>> only ever access the same temporary table, and you might
>never access
>> the other 9. So, you only create the one physical segment.
>>
>
>--
>//www.freelists.org/webpage/oracle-l
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
