I've been told that when running Oracle 220.127.116.11 on a Sun server with Solaris 2.6 as the operating system that large...
files, meaning files greater than 2 GB in size, are not supported (because Sol. 2.6 is a 32-bit OS). So far there are .dbs and .dbf files as large as 2.4 GB in size, and I'm being told by some that as long as the database comes "up" that there is no corruption to the files. On the other hand, I'm being told that to enable large file support I have to go to Sol. 2.8 w/64-bit turned "on" in order to protect the integrity of the data since there are large files involved. Using the Sol 2.6 and files > 2.09 GB, should I be wary of file corruption? And if so, will making the files smaller help? Can you recomend any caveats to look for? Any tips?
Before 64-bit OS's, vendors were able to create files larger than 2 GB by implementing large file support in software, rather than hardware. If you have files that are larger than 2 GB, then your Solaris server is using software to implement large files, greater than 2 GB. If you did not have this feature enabled, then your 2.4 GB file would not exist. So you should be safe. I worked with files larger than 2 GB on Solaris long before we ever had 64-bit Solaris installed on our servers.
For More Information
- Dozens more answers to tough Oracle questions from Brian Peasland are available.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical Oracle and SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our PL/SQL, database administration and data warehousing gurus are waiting to answer your toughest questions.
Dig Deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.