BFILE Limitations
What limitations need to be considered before deciding to use BFILE for storing information?
- BFILEs are pointers to binary files stored outside the actual database. Because of this BFILEs are read-only. They are also referred to as external LOBs
- Binary file pointed to should be of max size 4GB.
- Net8 will be used for streaming the binary file data to front-end. Enables byte stream I/O access to external LOBs residing on the database server
- BFILE data processing is independent of database transactions and management
- The Oracle database limits the number of concurrent BFILE LOBs that a user session can have open. This limit is set by the server parameter SESSION_MAX_OPEN_FILES.
- The binary file should reside on the same server as the db, same restrictions apply as oracle datafiles.
- BFILE are optimal solutions for files that will be stored along with the db. This way oracle takes care of reading and transfering the file to the required destination, so the client doesn't have to make a separate call to the file. Examples would be company logo's or documents which should be made accessible to all client apps.
- PL/SQL routine dbms_lob and Java routines are available to handle this datatype.
This page was create on 15-dec-2000 and last updated on 15-dec-2000.
please forward all queries to amar_padhi@fastmail.fm