tag:blogger.com,1999:blog-13265058.post7928961568919070216..comments2023-10-28T23:33:56.980+11:00Comments on Sydney Oracle Lab: Big BLOBs being greedy in TEMP tablespaceSydOraclehttp://www.blogger.com/profile/08828771074492585943noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13265058.post-2824785031612104992013-01-29T08:34:09.490+11:002013-01-29T08:34:09.490+11:00Given we typically have around 20 APEX database se...Given we typically have around 20 APEX database sessions, to allow for any and all of those sessions to deal with 500MB files (about our maximum size), then we'd need about a 10GB TEMP space.<br />Our whole database is around 50 GB (actually about half that is real data) and those files don't actually live in the database. <br />Considering the volume of data in those files, 10GB isn't big. It just feelds that way for the size of DB.<br /><br />We'll look at it as an optionSydOraclehttps://www.blogger.com/profile/08828771074492585943noreply@blogger.comtag:blogger.com,1999:blog-13265058.post-90552138115277436042013-01-29T02:05:44.404+11:002013-01-29T02:05:44.404+11:00Hi Gary,
You haven't listed the first solutio...Hi Gary,<br /><br />You haven't listed the first solution I thought about while reading your post: increasing temp space. <br /><br />Since 2 GB is tiny compared to today's HDDs capacities, is there a reason why you don't want to let the application grow its temp space? Would there be downsides beside lost HDD free space? <br /><br />Cheers,<br /><br />-- <br />Vincent MalgratAnonymousnoreply@blogger.com