grouper-users - RE: [grouper-users] composite group runs out of TEMP tablespace
Subject: Grouper Users - Open Discussion List
List archive
- From: "Hyzer, Chris" <>
- To: "Morgan, Andrew Jason" <>, "" <>
- Subject: RE: [grouper-users] composite group runs out of TEMP tablespace
- Date: Thu, 3 Oct 2019 01:42:59 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=isc.upenn.edu; dmarc=pass action=none header.from=isc.upenn.edu; dkim=pass header.d=isc.upenn.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zEkwGwRgs8gQrOEG0CBCxbbMtE1PJIoyWS9692T/4zM=; b=DL1420t+8+EVUJFg4GfNKdmr/RmecGRHmcnOaVuWV5zoeiteVSR9c9HS5/DJhdo+U4fRDmdjzIrh2R+/WBtLEAdo9E5ozggD7dXCMFlS8TrYSLi41NMCZmKIlm/Vc8ZbTC6IgVUYbLHCRFej0rKJZ/3EWDi/duC4C6xMdCRKnrvoq5WJms8gugFpxce742dSx/A7X5dTXHOH7vy3UmmtkbWOfC0dgI7yEDJlL0x3QSwNZxeGZw/QdaE2gkdQBgbNsy8xHCBoUKZi8+v9PqOSs6Tr1oxdd0hY+SGp8QyqOelusjOncCSKxTiIBGQd8U6ilOEEQoa7nmoveXt8uXWkaw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fnEi77qIVa5KahkXPhhkRJhLfXYGjJtQyq3ord7laasJ8zniY/sBCNEmsqCWgPMEGQ8c1gbdhqtfZRx/t094zTNQ5BvNrQ8E/gOUsV9USmz8LDdj3kfFXGgK2BGe339guYpRVeRGitrsMYo2mcxo2JPEPfO6dW38nAyLBf+uP10fGlhdC+alybGIpUs4olPvWeSrE/tkd1r+Zzh+xwAa15xGMy3N+dONkePOHso1IasCWWKq7isAYUDuWj/SMz5hUKaEWApWVi5FohHW1lRleIZw/jdwrTj5ofnsTocEbR3O2NVrH4VYONAORM+09FuKK3OH6h4BVjsFy2nO0bLsQA==
I only have one full table scan and you have two. Would gathering stats help? Shilen do you have ideas? 😊
From: <>
On Behalf Of Morgan, Andrew Jason
When creating a composite that is an intersection (AND) of 2 groups, we get a SQLexception:
ERROR spi.SqlExceptionHelper: ORA-01652: unable to extend temp segment by 1024 in tablespace TEMP
The groups we are intersecting have approximately 37k and 12k members.
Our Oracle DBA showed that the following SQL query ended up consuming all 32GB of the TEMP tablespace doing a sort operation:
select distinct member0_.id as col_0_0_ cross join grouper_memberships_all_v membership1_
and membership2_.owner_group_id=:2 and member0_.id=membership1_.member_id and member0_.id=membership2_.member_id and membership1_.field_id=:3 and membership2_.field_id=:4 and membership1_.immediate_mship_enabled='T' and membership2_.immediate_mship_enabled='T' and member0_.subject_source<>:5
I have attached a screenshot of the execution plan.
We are running Grouper v2.3 api patch 70 on Oracle database.
Is this a known issue? Is there any additional data I can provide that will help us understand why this query is so bad? 🙂
Thanks,
Andy Morgan Systems Administrator, Identity & Access Management Information Services | Oregon State University |
- [grouper-users] composite group runs out of TEMP tablespace, Morgan, Andrew Jason, 10/03/2019
- RE: [grouper-users] composite group runs out of TEMP tablespace, Hyzer, Chris, 10/03/2019
- <Possible follow-up(s)>
- Re: [grouper-users] composite group runs out of TEMP tablespace, Shilen Patel, 10/03/2019
- RE: [grouper-users] composite group runs out of TEMP tablespace, Hyzer, Chris, 10/04/2019
Archive powered by MHonArc 2.6.19.