Is it possible for data corruption to occur to an oracle schema for RTC if the tablespace fills up or the db filesystem is full?
Problem Description: "Now the issue " Is it possible for data corruption to occur to an oracle schema for RTC if the tablespace fills up or the db filesystem is full? "
***Above issue will be taken care by Oracle Database itself automatically, but If the Oracle Database filesystem increases 100% or oracle schema for RTC if the tablespace fills up 100% does it have impact on the data in oracle database ( database inconsistency) from the RTC application if the Oracle database fixes the above issue itself.
like: having problem with the query and indexing or slowness ?
Index Files:In addition to the data mentioned above, JTS and CCM in RTC 3.x use index files for various query and search operations ?
JFS Index Files ?
Fulltext Index Files?
Does it impact or just it depends on the database itself ?
|
One answer
|
They will definitely encounter problem with the transactions for saving the data to the database at the time of DB condition when the filesystem fills up.
It depends on the database configuration with AUTOEXTEND enabled? 1. Inconsistency can not happen considering there is no space to store the data. RTC will not recover from this inconsistency if there is any created in DB. DB transactions from the RTC to write DB will fail until the database is recovered and operational. Ideally they should be doing regular backups and also maintain the filesystem of the DB on regular basis. 2. SELECT queries should be able to execute to fetch the data from the DB provided it is operational at the time of no space left. transactions to DB might be slow but that slowness will not be inflicted by RTC rather from DB side. 3. Index files are stored in the location configured in teamserver.properites file. Which can be recreated by repotools command.Its not stored on DB. Inconsistency should not occur for that due to DB filesystem being full. However if you are restoring the DB from backup then index might not match and then have to be recreated. This might cause problems with dashboard , searches , errors in the log of indexing being ahead if DB and hence result in some inconsistency. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I've had this happen on occasion, but the end result was that the pending transactions were rolled back. It's worse if the indexes maintained by the application are on the file system that hits 100%. That can damage dashboard storage which are difficult to recover.
As such, for our servers we keep a good deal of headroom on the file systems and check them several times / hour to maintain that threshold.
Hi Kevin, thanks for sharing the information.
Will wait if any other comments and answer.