|Oracle® Multimedia User's Guide
11g Release 1 (11.1)
|PDF · Mobi · ePub|
This document summarizes the changes to this guide since the previous release as well as the new features introduced in the current release.
The following changes have been made to this guide since Oracle Database 10g Release 2 (10.2):
In Oracle Database 11g Release 1 (11.1), the name Oracle interMedia has been changed to Oracle Multimedia. The feature remains the same, only the name has changed. References to Oracle interMedia will be replaced with Oracle Multimedia, however some references to Oracle interMedia or interMedia may still appear in graphical user interfaces, code examples, and related documents in the Documentation Library for Oracle Database 11g Release 1 (11.1).
Title page - Added DICOM to the list of supported media in the summary description.
Chapter 1 - Added a new subsection about medical imaging under Section 1.5 "Image Concepts" that mentions the major DICOM features. Added cross-references to the new DICOM documentation. Replaced references to 4GB BLOB limits with new limits (8 TB to 128 TB, depending on the block size). Included a cross-reference to Oracle Database SecureFiles and Large Objects Developer's Guide. Removed Section 1.5.7 (content-based retrieval). Removed information about image matching from Section 1.5.8. (This feature is deprecated in the current release.)
Chapter 2 - Updated information about Oracle Java libraries.
Chapter 3 - Removed the documentation for the Code Wizard sample application from this chapter. Updated examples to use SecureFile LOBs.
Chapter 4 - Created a new chapter that includes the documentation for the Code Wizard sample application, which had been in Chapter 3. Updated examples to use SecureFile LOBs. Updated examples to follow the new security requirement for case-sensitive passwords.
Chapter 6 - Slightly reorganized this chapter to downplay information about DICOM in this manual. Added cross-references to the new DICOM documentation. Updated examples to use SecureFile LOBs.
Chapter 7 - Removed the content-based retrieval concepts chapter from the book (This feature is deprecated in the current release).
Chapter 8 - Replaced references to 4GB BLOB limits with new limits (8 TB to 128 TB, depending on the block size). Included a cross-reference to Oracle Database SecureFiles and Large Objects Developer's Guide. Revised chapter to include information about improvements in performance and scalability using SecureFile LOBs.
Chapter 9 - Updated descriptions for table creation examples to remove references to data files that will no longer ship with the kits. Updated examples to use SecureFile LOBs.
Appendix B - Included minor updates to install procedure. Added new subsection about removing Oracle Multimedia.
Glossary - Added a new glossary of Oracle Multimedia-specific terminology, highlighting it in a central location within the Oracle Multimedia documentation set.
Index - Added new index entries and improved existing entries.
Ongoing minor improvements and bug fixes
Oracle Database 11g Release 1 (11.1) includes several new features for Oracle Multimedia DICOM and improvements in the area of performance and scalability.
Oracle Multimedia DICOM was introduced in release 10.2. Release 11.1 adds the following Oracle Multimedia DICOM features:
Creation of DICOM objects
DICOM image processing
DICOM object conformance validation
DICOM metadata extraction
DICOM format support
Making DICOM objects anonymous
ORDDicom object type
Run-time, updatable DICOM data model
Release 11.1 also includes performance and scalability improvements. This release provides improvements for applications that require increased throughput in certain image processing operations as well as the ability to manage very large media objects.
In this release, the size limit of media data that can be stored and retrieved within database storage structures (BLOB) in an Oracle Multimedia object type in the database is extended to the BLOB size limit, which is between 8 terabytes (TB) and 128 terabytes depending on the block size.
In addition to storing and retrieving large images, Oracle Multimedia can also extract image attributes including height, width, and compressionFormat for images that contain up to two billion pixels, or with a resolution of up to 46000x46000. For images that support metadata extraction (IPTC, EXIF and XMP), Oracle Multimedia can extract and manage embedded metadata for any size image that it can store.
Oracle Multimedia provides image processing functions that change image content. For example, you can scale and crop an image or convert it to a different file format. Processing an image requires interpreting the pixel values of the image, an operation that often impacts system performance and memory. As a result, Oracle Multimedia may be unable to successfully process images that it can successfully store. The maximum image size that Oracle Multimedia can process depends on the image format and the system platform. See the Oracle Multimedia
README.txt file for guidelines on image processing limits for each supported format.
Performance and scalability improvements have been made for the most popular image processing operation, generating a thumbnail image. Significant performance improvements have been made for generating these images from TIFF and JPEG sources, as well as from DICOM sources with JPEG encoding. In addition, improvements in scale-down operations enable the fast generation of thumbnail images from very large source images (JPEG, TIFF, and DICOM with JPEG or RAW encoding.)
In this release, Oracle Multimedia also supports the next generation of LOBs, which is called Oracle SecureFiles. SecureFiles introduces a completely reengineered large object (LOB) to dramatically improve performance and significantly strengthen the native content management capabilities of Oracle Database. Oracle Multimedia object types, methods, and packages have been tested to ensure correct operation with SecureFiles. Oracle recommends using SecureFiles to store media content within Oracle Multimedia object types to reap the performance benefits of this new BLOB implementation.