Note that 10g R2 won't fit on a single CD since it has over 780MB.
Oracle says that the system must have at least 512MB of RAM and 1GB of swap space or twice the size of RAM.
Table of Contents: * Downloading Oracle10g Software and Burning Oracle10g CDs * Checking Memory and Swap Space * Checking /tmp Space * Checking Software Packages (RPMs) * Checking Kernel Parameters * Sizing Disk Space for Oracle10g * Creating Oracle User Accounts * Setting Shell Limits for the Oracle User * Creating Oracle Directories Optimal Flexible Architecture (OFA) for 10g (10.1.0.2) * Setting Oracle Environments * Installing Oracle10g Installing Oracle10g on a Remote Linux Server Starting Oracle Universal Installer Using Oracle Universal Installer Updates after Running Oracle Universal Installer * Oracle Post-installation Tasks Startup and Shutdown of the Oracle10g Database Shutdown of other Oracle 10g Background Processes * Tips and Hints for Oracle10g on Linux * Oracle10g/Linux Errors and Problems * References Download Oracle 10g (32-bit and 64-bit) for Linux from OTN to install linux 10g oracle: To install a Oracle Database 10g (without RAC) you only need to download the database file Disk1/stage/Components/oracle.server/10.1.0.3.0/1 Disk1/stage/Components/oracle.server/10.1.0.3.0 Disk1/stage/Components/oracle.server Disk1/stage/Components/oracle.tg/10.1.0.3.0/1/Data Files Disk1/stage/Components/oracle.tg/10.1.0.3.0/1 Disk1/stage/Components/oracle.tg/10.1.0.3.0 Disk1/stage/Components/Disk1/stage/Components/oracle.assistants.dbca/10.1.0.3.0/1/Data Files/doc.3.1Disk1/stage/Components/oracle.assistants.dbca/10.1.0.3.0/1/Data Files/...
The process of adding the new column with a default NOT NULL value is now much more easy, and faster.That user is updating\inserting\deleting a lot of database records without committing.Oracle clears out any unneeded transactions in the rollback segment but eventually it fills up and the error occurs. User B logs into the data base and is updating\inserting\deleting a lot of database records, but is committing every 100 records.I've been dealing with this error off and on for the last 3 years and I just wanted to verify that my understanding of its cause is accurate.Cause 1) There is only one user logged into the database.Therefore, commiting every so often would fix cause 1, but can do nothing about cause 2.