Bug 506516
Summary: | Oracle db error when navigating to event history | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | wes hayutin <whayutin> |
Component: | Server | Assignee: | Justin Sherrill <jsherril> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | wes hayutin <whayutin> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 530 | CC: | bperkins, jsherril, mmraka, msuchy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://riverraid.rhndev.redhat.com/network/systems/details/history/history.pxt?sid=1000010023 | ||
Whiteboard: | |||
Fixed In Version: | sat530 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-10 18:16:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 456985, 486216 |
Description
wes hayutin
2009-06-17 15:46:13 UTC
So I ran: db-control gather-stats on riverraid and the problem went away. I think the DB just needed to do some analysing to run that query effectively. to run gather stats: # su - oracle # db-control gather-stats gather-stats resolved the issue. in addition I installed a fresh sat, let it sit for a day, and did not recreate the problem. resolved Just FYI: Original database error was ORA-01652: unable to extend temp segment by 128 in tablespace TEMP_TBS. Which means there is no space left in temporary tablespace. I can't imagine how gathering stats may help to free TEMP_TBS. The other way round - gather-stats consume temp space itself so it can make things worse. In this case I assume a session which held temp space ended so database released it and gathering stats was just a placebo. Michael, Is it not possible that the query that the DB was running before gather stats had been run was so unoptimized that it was using more temp space ? While after running gather stats, oracle was able to more efficiently run the query thereby using less tempspace. -Justin You're right, I can imagine that. E.g. unoptimized query does full scan of two huge tables and then merges them so it needs a lot of space for merge sort and then filter nearly all rows out while optimized one uses indexes so it merges only several rows together. But it's so artificial example... I've never seen such behaviour even on very large and heavy loaded databases. --mm I could not reproduce it. I even think that it was never been bug per se. Anyway moving to verified in stage. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html |