Reference Architecture to store large files with scanned images?

Oracle can be used to store image files:

https://forums.oracle.com/forums/thread.jspa?threadID=1036105

The below EMC use case white paper demontrates the ease of use and flexibility of EMC unified storage platform within Oracle environment, providing a single platform for both block and file storage:

h8124 - Oralce Deployment Agility Enabled by Unified Storage and VMware

I look through oracle forums and not sure as a DBMS Oracle can offer a whole solution on large files with scanned images. But other option comes out -- EMC Documentum available with Capativa.

As Documentum is wise enough to separate a file to two part,  one is metadata stored in table to Oracle and the other is physical big files to storage area(EMC better). I believe it will a good resource utilized solution for scanned images store.  

What I'm thinking is if land records are the meta data for these picture files which stored information like file name, location, size, etc. It's not likely these pictures are stored in Oracle as BLOB for their huge size and quantity. What do Oracle experts think of this?

I did searching on the internet about the Land Record, here is the example:

Most Public Land Records are organized by township. To find a Master Title Plat, Historical Index, Use Plat or Rectangular Survey Plat, the user must first select a township or in the case of a multiple township search, select the starting and ending townships.

The Public Land Records for the selected township(s) is identified by its Township, Range, Meridian, Record Type (Type), Record Sub Type (Sub Type), and Detail Report (Detail), as well as other columns specific to the type of record displayed

So I think the land records are structured database data managed by Oracle database in this case, which is also link to the large image files.  We need to confirm it with ATC.

Well, if that's the case, Isilon should be the product to select considering of its scalability and capacity. Customer wants the 1T block storage as well, maybe we can recommend Ision + VNX5100.

Good reference for using Isilon to improve data storage performance and reduce costs for multimedia massive files in the M & E.

http://info.isilon.com/forms/media_entertainment?campaign=70170000000BbzT

General speaking, Oracle does not store large objects in its database files, that would highly impact with its performance, although it does support it, BLOG type.

There are two methods to deal with this in normal cases,

Store Absolute Path of objects on storage (local or network) on table, and FE application service combined the presentation when dialogue execution.

Leveraging 3rd content management service, like opentxt and Land Record, and in this case, @ some degree, the service manage objects and storage repository by own self, therefore it does not matter with oracle much, the conversation between content management service is how to allocate and access object with a unique id.

When you look at this kind cases, you might need to know not only capacity, but also about data retention, storage type supported with this content manager, etc.

FYI, thanks

Eddy

How to store images into Oracle database through forms

Use READ_IMAGE_FILE to read a image file stored on the machine with the form is executing.  The image will become 'visible' on screen.  When the user saves into the database, the image will go into the database.

Use WRITE_IMAGE_FILE to export an image that exists in the database to the users machine.  They would query a record up, get the image they wanted and you would give them a button or something to 'export' the image.  The when-button-pressed trigger would invoke wirte_image_file to save the contents of the image to disk

As we haven't got more information from customer side, graph database might be also a choice due to its character of NoSQL  - document-oriented databases, key-value stores and graph databases. Graph databases apply graph theory to the storage of information about the relationships between entries. The relationships between people in social networks is the most obvious example. The relationships between items and attributes in recommendation engines is another.  Short version: among other things, relationship queries in RDBSes can be complex, slow and unpredictable. Since graph databases are designed for this sort of thing, the queries are more reliable.

http://www.readwriteweb.com/cloud/2011/04/5-graph-databases-to-consider.php