|
not applicable in this situation! if the system is going down...it's going down. trying to build a report to show you that will only speed up the crash!...but if you have to peddle your wares...when disk space climbs that fast then there's no way your product (or any other i know of) can help in the situation presented.
Thanks,
Tommy Holden
From:
Spencer Elliott <spencer@xxxxxxxxxxxxxxx>
To:
midrange-l@xxxxxxxxxxxx
Date:
08/12/2008 12:35 PM
Subject:
Re: Take your system down with Cartesian Joins
Funny, I just posted this same note on another thread!
Vendor Plug!
We offer a product (DiskHunter) that will continually monitor you disk usage based of percent increase over time or absolute increase in disk usage. The product will then automatically analyze what is going on and produce reports that (in most cases) point to the culprit. Alerts and emails are sent which contain the results of the analysis. This product can catch, analyze and notify you of the findings before your system crashes... cheap insurance
Spencer Elliott
Vendor
http://www.s4isystems.com
elehti@xxxxxxxxxxxxxxxxxx wrote:
How to fill up your disk (system auxiliary storage pool) and take down
your system. Create a query to output to a file. Join two or more
tables but neglect to join the tables. This will produce a Cartesian
join. http://www.orafaq.com/wiki/Cartesian_join
You will get this message before your system goes down.
Additional Message Information
Message ID . . . . . . : CPF0907 Date sent . . . . . . : 08/07/08 Time sent . . . . . . : 07:23:47
Message . . . . : Serious storage condition may exist. Press HELP.
Cause . . . . . : The amount of available auxiliary storage in the
system auxiliary storage pool has reached the threshold value. This is a potentially serious system condition. The auxiliary storage capacity is 210,990,268,416 bytes. The auxiliary storage used is 191,498,387,456
bytes. The
threshold is 90.000000 percent. The auxiliary storage available is
9.23828
percent. Recovery . . . : Use the WRKSYSSTS command to monitor the amount of
storage
used. The use of storage can be reduced by the following actions: Save objects by specifying STG(*FREE); delete any unused objects. Save the
old log versions of QHST that are not currently used and then delete them; either write or delete spooled files on the system. Failure to reduce
the More..
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.