Oracle datafile maximum size

To find out how big your datafile can grow, you should first know how much your OS/filesystem supports.

Maximum OS file size:
===============
Maximum OS file size is determined by the type of filesystem where you are creating the file.
On Linux, type of filesystem can be determined using command df -T

e.g. ext3 filesystem supports maximum 2^32 blocks. (http://en.wikipedia.org/wiki/Ext3)

Now how to find size of a OS block (Block size for a filesystem)?
On linux, it can be found using tune2fs or dumpe2fs.
e.g.

dumpe2fs /dev/sda1 | grep -i 'Block size'
Block size:               4096

So,

Maximum ext3 "filesystem" size with 4k blocksize can be 2^32*4k i.e. 16TB
Maximum size of single file created on that filesystem can be 2TB (Haven't figured out how is this limit calculated).


Oracle Database Maximum size for datafiles:
==============================
Reference: Oracle Documentation
11gR2: http://docs.oracle.com/cd/E11882_01/server.112/e25513/limits002.htm#i287915

It depends on:
1. Database block size (db_block_size)
2. Maximum database blocks per datafile. This is platform dependent.
3. Limited by maximum operating system file size

For smallfile tablespaces:
11gR2 : Operating system dependent. Limited by maximum operating system file size; typically 2^22(i.e. 4194304) or 4 MB blocks
i.e. for 8k db_block_size database, the maximum size of the datafile on ext3(4k OS block size) filesystem could be 32GB.

For bigfile tablespaces:
11gR2: Single datafile upto 2^32 blocks i.e. for 8k db_block_size, the maximum size of bigfile tablespace/datafile would be 32TB. But ext3(4k OS block size) file/filesystem would not support this big datafile. And it would be limited to 2TB for ext3 filesystem.

Reading Expert Oracle Exadata

"Expert Oracle Exadata" by Kerry Osborne, Randy Johnson, Tanel Põder

I have started reading this book keeping a target in mind i.e. Oracle Exadata Implementation Specialist certification...

Already have read the first chapter and very impressed with the way the authors have explained the concepts.

I would recommened everyone who are looking forward to make career in Exadata but doesnt know much about it to start with the first chapter of this book...this chapter touches on history, need, hw components, sw components, etc.

I will keep posting as I go on reading this book...

Pointers on what first chapter covers briefly:
-Database servers
-Storage servers
-X2-2 (quarter, half and full rack)
-X2-8
-HP Disks (High Performance)
-HC Disks (High Capacity)
- Spine switch (for exadata expansions)
- ILOM (Integrated lights out manager)
- Intel based SUN servers
-Unbreakable Enterprise Kernel of linux (UEK)
- Solaris express too
- Infiniband switches
-384GB Flash drives per storage server
-iDB protocol
-RDS protocol
-cellsrv
-MS and RS
-OSW on storage server

and many more....

httpd.worker consumes 100% CPU when FMW control accessed

After successful installation of :
Weblogic (10.3.4)
WebTier Utilities (11.1.1.4.0)

Created domain using config.sh at
$ORACLE_HOME/common/bin/
$ORACLE_HOME/bin/

Everything looked ok until we tried to access httpd.conf/dads.conf files from Fusion Middleware Control under ohs1=>Configuration=>Advanced Configuration. FMW control would just hang and would not show the .conf file. On the server top showed httpd.worker process consuming lot of resources. CPU was 100% and it was taking up memory as well.

At one point it consumed swap also and there was no other option than to power reboot the server.

2-3 times we were able to kill the httpd.worker process which was consuming 100% cpu and strangely fmw control would show the file as soon as the process is killed.


There was no error reported in any of the logs e.g. syslog, AdminServer logs, & ohs/webcache logs.

The only problem we noticed was the way /etc/hosts was configured.

It was configured in below format:

<ip address> <shortname> <fully qualified hostname>

We changed it to below format:

<ip address> <fully qualified hostname> <shortname>

Uninstalled Oracle software i.e. weblogic and webtier. And reinstalled.

And this time the problem went away.

We tried the same solution other 2 servers where we had same issue and /etc/hosts was configured wrongly. The solution worked on them too.

Hope this helps.

FRM-92120: Registry file Registry.dat is missing

After 11g installation sungard banner app(INB) wouldnt launch. It was giving this error consistently:

It was complaining about missing Registry.dat.

In 10g:
Registry.dat is located at $ORACLE_HOME/forms/java/oracle/forms/registry

In 11g
-Registry.dat was NOT present at $ORACLE_HOME/forms/java/oracle/forms/registry
-So we searched under MW_HOME

$ find . -name Registry.dat
./fmw11g/forms/templates/config/Registry.dat
./user_projects/domains/INB/config/fmwconfig/servers/WLS_FORMS/applications/formsapp_11.1.1/config/forms/registry/oracle/forms/registry/Registry.dat

 - We copied the one under DOMAIN_HOME to $ORACLE_HOME/forms/java/oracle/forms/registry  but that did NOT help, we received same error

BTW, same server has 10g installation and was being used for long time. Also frmall.jar points to actual location of Registry.dat

Since we had 10g installation on the same servers and our laptops(clients) has cached 10g stuff, it was not loading 11g frmall.jar and thats why it was looking at wrong location.

To solve the problem, we deleted JRE cache and it loaded 11g frmall.jar and the error vanished.

To delete JRE cache:
Go to your computer(client) Control Panel=> Java => Settings under Temporary Internet Files => Delete Files

Hope this helps.

config.sh hangs at 0% (creating domain) step

I have below install:
Weblogic 10.3.4
PFR&D 11.1.1.4.0 (Install only, configure later)

Now for domain creation I executed $ORACLE_HOME/bin/config.sh

The config.sh seemed to have stopped at 0% (domain creation step).

After waiting for almost one and half hour, it failed and suddenly jumped to 8%:

Check the screenshot below:



The install log showed:

Error while starting the domain.
Cause:
Starting the Admin_Server timed out.

Cause: There are multiple installations of JAVA on the system. The java used by weblogic install was just JRE and was not complete JDK.

Solution: Uninstall PFRD and weblogic and redo the installation after setting below parameters:
JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH

That solved my problem and I was able to do the domain configuration.