Edit D:\app\Administrator\product\11.2.0\dbhome_1\ord\im\admin\README.txt
Copyright (c) 1998, 2009, Oracle and/or its affiliates. All rights reserved. NAME README.txt - ORACLE Multimedia (formerly known as interMedia) RELEASE INFORMATION RELEASE 11.2 README FILE ======================= Contents ======== Feature Name Change Getting Started Oracle Multimedia Release 11.2 Oracle Technology Network Oracle Multimedia Documentation Warning Oracle Multimedia Installed Users and Privileges Important Install and Upgrade Considerations Upgrade Notes Installing Oracle Multimedia Verfying the Oracle Multimedia Installation Running the Sample Applications Downgrade Notes Deinstall Notes Using Oracle Multimedia Java API Using Oracle Multimedia Mid-Tier Java API Problems Fixed in This Release Features Added in This Release Known Problems in This Release Documentation Omissions and Corrections Deprecated Features New Features Feature Name Change =================== The name Oracle interMedia was changed to Oracle Multimedia in Release 11.1. The feature remains the same, only the name was changed. References to Oracle interMedia were 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 Oracle Database documentation library for 11g Release 2 (11.2). Getting Started =============== This document describes release information for Oracle Multimedia. Oracle Multimedia Release 11.2 ============================== Oracle Multimedia enables Oracle Databases to store, manage, and retrieve image, medical images and other objects (DICOM), audio, and video data in an integrated fashion with other enterprise information. Oracle Multimedia extends Oracle Database reliability, availability, and data management to multimedia content in traditional, medical, Internet, electronic commerce, and media-rich applications. Oracle Multimedia provides image services for the storage, retrieval, metadata extraction, and processing of two-dimensional, static, bit-mapped images. Images are stored efficiently using popular compression schemes in industry-standard image formats for desktop publishing. Oracle Multimedia provides Digital Imaging and Communications in Medicine (DICOM) support for the storage, retrieval, metadata extraction, processing, writing, conformance validation, and making anonymous of medical images and other DICOM binary data. Oracle Multimedia provides audio and video services for the storage, retrieval, and metadata extraction of popular audio and video file formats. Oracle Technology Network ========================= For the most recent information about Oracle Multimedia, and for free downloads of Oracle Multimedia examples and plug-ins, go to the Oracle Multimedia section of the Oracle Technology Network web site at: http://www.oracle.com/technology/products/multimedia/ Oracle Multimedia Documentation =============================== Complete online documentation is available with Oracle Database. Check the Oracle Technology Network web site for updates to Oracle Multimedia documentation. A new Javadoc, Oracle Multimedia Mid-Tier Java API Reference, is available in this release. Oracle Locator provides location-based services for Oracle. For information on Oracle Locator see Oracle Spatial User's Guide and Reference. WARNING: ========= Ignoring this warning and performing any of these prohibited actions could cause internal errors and security violations in the database management system. Oracle Multimedia is installed under the database users ORDSYS, ORDPLUGINS, SI_INFORMTN_SCHEMA, and ORDDATA. These users are created during database installation and are subject to change in future releases. These users must not be deleted. Oracle Multimedia Locator is installed under the database user MDSYS if Oracle Spatial is not installed. This user is created during database installation and is subject to change in future releases. This user must not be deleted. Customers must not connect to these users or modify these users or their contents. The functions, packages, types, views, and documents supplied by Oracle Multimedia are reserved by Oracle and are subject to change in future releases. Note: User defined packages may be added to the ORDPLUGINS schema. See Oracle Multimedia User's Guide for more information on extending Oracle Multimedia. Note: User defined DICOM data model documents are stored in the ORDDATA schema using the DICOM data model repository API. See the Oracle Multimedia DICOM Developer's Guide for more information on inserting documents into the data model repository. ======================= Oracle Multimedia Installed Users and Privileges ================================================ The Oracle Multimedia installation creates the users ORDSYS, ORDPLUGINS, SI_INFORMTN_SCHEMA, ORDDATA, and MDSYS with the privileges required for Oracle Multimedia. These users are created with default passwords, and the installation then locks the accounts and marks the default passwords as expired. During installation the default password for the user ORDSYS is 'ORDSYS', for ORDPLUGINS it is 'ORDPLUGINS', for SI_INFORMTN_SCHEMA it is 'SI_INFORMTN_SCHEMA', for ORDDATA it is 'ORDDATA', and for MDSYS it is 'MDSYS'. NOTE: Oracle does not recommend logging into these user accounts directly. The installation process also grants the EXECUTE privilege to the user group PUBLIC for the Oracle Multimedia packages and objects installed in the ORDSYS, ORDPLUGINS, SI_INFORMTN_SCHEMA, and MDSYS schemas. Important Install and Upgrade Considerations ============================================ A new database security measure introduced in this release requires additional configuration steps for Oracle Multimedia applications using HTTP sources for media content. You can use the following query to determine if a media column contains HTTP sources. The query assumes that the table name is MEDIA_TABLE and column name is MEDIA_COLUMN. SELECT count(*) FROM MEDIA_TABLE m WHERE m.MEDIA_COLUMN.source.srcType = 'HTTP' AND m.MEDIA_COLUMN.source.local IS NOT NULL AND m.MEDIA_COLUMN.source.local <> 1 Oracle Multimedia uses the PL/SQL package UTL_HTTP to access media content for HTTP sources. You must grant a privilege to the application user to enable a network connection to be made to the remote host. For example, to grant the user SCOTT permission to access HTTP content located at the host wwww.oracle.com:80, the database administrator should execute the following: SQL> REM Creates a new ACL and adds SCOTT the privilege to the ACL to make SQL> REM TCP connections SQL> EXECUTE DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('acl_for_oracle.xml', - > 'ACL for www.oracle.com', 'SCOTT', TRUE, 'connect') SQL> REM Assigns the new ACL to www.oracle.com for TCP/IP port 80 (HTTP) SQL> EXECUTE DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL('acl_for_oracle.xml', - > 'www.oracle.com', 80) SQL> REM Commits to make the ACL take effect SQL> COMMIT For more information on configuring privileges for network access, see the documentation for the DBMS_NETWORK_ACL_ADMIN and UTL_HTTP packages. Upgrade Notes: ============== If you upgrade a database from an earlier release of Oracle Database, Oracle Multimedia will be upgraded automatically if it is detected in the source database. See Oracle Database Upgrade Guide for detailed instructions. Installing Oracle Multimedia ============================ Oracle Multimedia is installed and configured with Oracle Database. If you need to configure Oracle Multimedia manually, follow the instructions in this section. 1 Installation Decisions 2 Pre-Installation Steps 3 Installation Steps 1 Installation Decisions ------------------------ The installation procedure creates the users ORDSYS, ORDPLUGINS, SI_INFORMTN_SCHEMA, ORDDATA, and MDSYS. These user are created with the privileges required for Oracle Multimedia. Decision 1: Decide which tablespace to use for Oracle Multimedia users (ORDSYS, ORDPLUGINS, SI_INFORMTN_SCHEMA, and ORDDATA), and which tablespace to use for the Oracle Spatial/Oracle Multimedia Location Services user (MDSYS). Oracle recommends using the SYSAUX tablespace for both. 2 Pre-Installation Steps ------------------------ For more instructions on installing on your system and setting up your environment, see the Oracle Installation Guide for your operating system. Perform the following pre-installation tasks prior to manually installing and configuring Oracle Multimedia: 2.1 Install Oracle Database, including PL/SQL, Oracle JVM, Oracle XML Database, and Oracle XDK. 2.2 Create the database. 2.3 Start the database. 2.4 Verify that required software is installed and valid. To verify that required software is correctly installed, run SQL*Plus, connect AS SYSDBA, and enter the following queries: SQL> select version, status from dba_registry where comp_id='JAVAVM'; SQL> select version, status from dba_registry where comp_id='XDB'; SQL> select version, status from dba_registry where comp_id='XML'; Ensure that the versions are correct and the status values are 'VALID'. 3 Installation Steps -------------------- Perform the following mandatory configuration steps. These steps are required ONLY if you are configuring Oracle Multimedia manually. You do NOT need to perform these steps if you use the Database Configuration Assistant. References to <ORACLE_HOME> in these instructions represent the Oracle home directory. 3.1 Use the Oracle Universal Installer to install the files that make up Oracle Multimedia on your system. 3.2 Create the users and grant the appropriate privileges. 1) Start SQL*Plus and connect as SYSDBA. 2) Invoke ordinst.sql with two parameters for the Oracle Multimedia tablespace and the Oracle Location Services tablespace. SQL> @<ORACLE_HOME>/ord/admin/ordinst.sql SYSAUX SYSAUX (on Linux/UNIX) @<ORACLE_HOME>\ord\admin\ordinst.sql SYSAUX SYSAUX (on Windows) 3.3 Install Oracle Multimedia types and packages. 1) Start SQL*Plus and connect as SYSDBA. 2) Invoke catim.sql SQL> @<ORACLE_HOME>/ord/im/admin/catim.sql (on Linux/UNIX) @<ORACLE_HOME>\ord\im\admin\catim.sql (on Windows) After these mandatory installation steps have been completed, Oracle Multimedia is ready for use. ======================= Verifying the Oracle Multimedia Installation ============================================ After you have installed or upgraded Oracle Multimedia, you can verify the Oracle Multimedia installation by invoking the Oracle Multimedia validation procedure. To run the Oracle Multimedia validation procedure, connect as SYSDBA and execute the procedure validate_ordim as follows: 1) Start SQL*Plus and connect AS SYSDBA. 2) Execute SYS.validate_ordim SQL> execute SYS.validate_ordim; The validation procedure silently sets the Oracle Multimedia registry entry to 'VALID' if Oracle Multimedia is valid. If there are invalid objects detected, the validation procedure lists the first few invalid objects and sets the registry entry to 'INVALID'. To query the registry entry for Oracle Multimedia, run SQL*Plus, connect AS SYSDBA, and enter the following query: SQL> select version, status from dba_registry where comp_id='ORDIM'; Ensure that the version is correct and the status is 'VALID'. Running the Sample Applications =============================== After you have installed Oracle Multimedia, you can run the Oracle Multimedia sample applications. The sample applications are available on the Oracle Database Examples media, which is available for download from the Oracle Technology Network. References to <ORACLE_HOME> in these instructions represent the Oracle home directory. After installing the Oracle Database Examples media, the Oracle Multimedia sample applications are located in the following directory: <ORACLE_HOME>/ord/im/demo (on Linux/UNIX) <ORACLE_HOME>\ord\im\demo (on Windows) Oracle Multimedia Java Sample Application ----------------------------------------- For the Oracle Multimedia Java Sample Application, see the README.txt file at: <ORACLE_HOME>/ord/im/demo/java/README.txt (on Linux/UNIX) <ORACLE_HOME>\ord\im\demo\java\README.txt (on Windows) Oracle Multimedia ORDImage Sample Application --------------------------------------------- For the Oracle Multimedia ORDImage OCI sample application, see the README.txt file at: <ORACLE_HOME>/ord/img/demo/README.txt (on Linux/UNIX) <ORACLE_HOME>\ord\img\demo\README.txt (on Windows) Oracle Multimedia Java Servlet Photo Album Sample Application ----------------------------------------------- For the Oracle Multimedia Java Servlet Photo Album sample application, which illustrates using Oracle Multimedia Java API for servlets and JSP to upload and retrieve multimedia data from a Java servlet, see the README.txt file at: <ORACLE_HOME>/ord/http/demo/servlet/README.txt (on Linux/UNIX) <ORACLE_HOME>\ord\http\demo\servlet\README.txt (on Windows) Oracle Multimedia JavaServer Pages Photo Album Sample Application ----------------------------------------------------------------- For the Oracle Multimedia JavaServer Pages Photo Album sample application, which illustrates using Oracle Multimedia Java API for servlets and JSP to upload and retrieve multimedia data from a JSP, see the README.txt file at: <ORACLE_HOME>/ord/http/demo/jsp/README.txt (on Linux/UNIX) <ORACLE_HOME>\ord\http\demo\jsp\README.txt (on Windows) Oracle Multimedia PL/SQL Web Toolkit Photo Album Sample Application ------------------------------------------------------------------- For the Oracle Multimedia PL/SQL Web Toolkit Photo Album sample application, which illustrates how to upload and retrieve multimedia data using Oracle PL/SQL Web Toolkit and Oracle PL/SQL Gateway, see the README.txt file at: <ORACLE_HOME>/ord/http/demo/plsqlwtk/README.txt (on Linux/UNIX) <ORACLE_HOME>\ord\http\demo\plsqlwtk\README.txt (on Windows) Oracle Multimedia Code Wizard for the PL/SQL Gateway ---------------------------------------------------- For the Oracle Multimedia Code Wizard for the PL/SQL Gateway, which is an example of a tool that lets you create PL/SQL procedures for the PL/SQL Gateway to upload and retrieve media data stored in the database using any of the Oracle Multimedia object types, see the sample SQL scripts and README.txt file at: <ORACLE_HOME>/ord/http/demo/plsgwycw (on Linux/UNIX) <ORACLE_HOME>\ord\http\demo\plsgwycw (on Windows) Downgrade Notes =============== Oracle Multimedia is automatically downgraded when you downgrade Oracle Database with the Oracle Multimedia feature installed. See Oracle Database Upgrade Guide for detailed instructions. WARNING Do not modify your DICOM data model repository until you are sure you that will not downgrade from Oracle Database 11g Release 2 (11.2) back to the source release. Changes made to the Oracle Multimedia DICOM data model repository (such as document insertions or deletions) that you make after a database upgrade will be lost after a database downgrade. Deinstall Notes =============== Oracle Multimedia ships an installation removal script. The database component removal script (catcmprm.sql) should be used to invoke the Oracle Multimedia removal script to ensure there are no components installed that depend on Oracle Multimedia. Follow these steps to deinstall Oracle Multimedia: 1) Start SQL*Plus and connect as SYSDBA. 2) Invoke the component removal script, catcmprm.sql, with parameter ORDIM to remove Oracle Multimedia if no other components that depend on Oracle Multimedia are installed: -> SQL> @<ORACLE_HOME>/rdbms/admin/catcmprm.sql ORDIM (on Linux/UNIX) @<ORACLE_HOME>\rdbms\admin\catcmprm.sql ORDIM (on Windows) If a component that depends on Oracle Multimedia is installed, for example, Oracle Spatial, the following message will be displayed and the Oracle Multimedia removal script will not be invoked: ORDIM cannot be removed as it has the following dependencies: Component: SDO Namespace: SERVER If no dependent components are installed, the Oracle Multimedia removal script will check whether Oracle Multimedia is being used. A message will be displayed indicating whether or not Oracle Multimedia is being used. For example: Oracle Multimedia is not being used or Oracle Multimedia object types are being used You will then be asked: Are you sure you want to remove Oracle Multimedia (Y/N): If the first character of your response is 'Y' or 'y', Oracle Multimedia will be removed with force regardless of whether or not it is being used. Using Oracle Multimedia Java API ==================================== To use Oracle Multimedia Java API, your Java environment must be set up correctly to compile and run Java programs. In addition, the following setup is required. The environment variable CLASSPATH must be specified and it must include the following Oracle Java libraries: the Oracle Multimedia Java API library, the Oracle Multimedia DICOM Java API library if you are using the DICOM feature, the XDB Java classes library if you are using the DICOM feature or Oracle Multimedia metadata extraction, and the Oracle JDBC library. If you are writing a servlet or JSP application, you must also include the Oracle Multimedia Java API library for servlets and JSP library. The Oracle Java libraries are located as follows: Unix: JDK 5 or later: <ORACLE_HOME>/ord/jlib/ordim.jar <ORACLE_HOME>/ord/jlib/orddicom.jar (for DICOM only) <ORACLE_HOME>/ord/jlib/ordhttp.jar (for servlets and JSP only) <ORACLE_HOME>/jdbc/lib/ojdbc5.jar <ORACLE_HOME>/rdbms/jlib/xdb.jar (for DICOM and metadata extraction) <ORACLE_HOME>/jlib/orai18n.jar (optional, see note) Windows: JDK 5 or later: <ORACLE_HOME>\ord\jlib\ordim.jar <ORACLE_HOME>\ord\jlib\orddicom.jar (for DICOM only) <ORACLE_HOME>\ord\jlib\ordhttp.jar (for servlets and JSP only) <ORACLE_HOME>\jdbc\lib\ojdbc5.jar <ORACLE_HOME>\rdbms\jlib\xdb.jar (for DICOM and metadata extraction) <ORACLE_HOME>\jlib\orai18n.jar (optional, see note) See your JDK documentation for information about other Java libraries that may be required. Note: If NLS character set conversion is required between the client application and the database, you must include the file orai18n.jar in the CLASSPATH variable. See Oracle Database JDBC Developer's Guide and Reference for more information on NLS character set conversion. If NLS character set conversion is required, but the appropriate library is not specified, then character-based attributes of Oracle Multimedia object types may be returned as hexadecimal-encoded strings. If you are using the JDBC OCI driver, the location of the JDBC OCI shared library must be specified in the variable LD_LIBRARY_PATH (for Linux or UNIX) or the variable PATH (for Windows). Note: Because this library path is shared, it may have been specified previously to enable the use of other client applications, such as SQL*Plus. Unix: <ORACLE_HOME>/lib (for libocijdbc11.so) Windows: <ORACLE_HOME>\bin (for ocijdbc11.dll) Using Oracle Multimedia Mid-Tier Java API ==================================== To use Oracle Multimedia Mid-Tier Java API, your Java environment must be set up correctly to compile and run Java programs. In addition, the following setup is required. The environment variable CLASSPATH must be specified and it must include the following Oracle Java libraries: the Oracle Multimedia Java API library, the Oracle Multimedia Mid-Tier Java API library, the Oracle Multimedia DICOM server-side JAVA library, and the XML Java API library. The Oracle Java libraries are located as follows: Unix: <ORACLE_HOME>/ord/jlib/ordim.jar <ORACLE_HOME>/ord/jlib/orddcmmt.jar <ORACLE_HOME>/ord/jlib/ordimdcm.jar <ORACLE_HOME>/lib/xmlparserv2.jar Windows: <ORACLE_HOME>\ord\jlib\ordim.jar <ORACLE_HOME>\ord\jlib\orddcmmt.jar <ORACLE_HOME>\ord\jlib\ordimdcm.jar <ORACLE_HOME>\lib\xmlparserv2.jar See your JDK documentation for information about other Java libraries that may be required. Problems Fixed in This Release ============================== Modified IPTC-IIM Metadata Schema --------------------------------- The IPTC-IIM metadata schema is modified to allow the <recordVersion> tag to be optional. This tag was previously required and if the tag was not present in the image then no XML metadata document was produced. This affects the getMetadata() methods of ORDSYS.ORDImage. It was requested by customer bug: 6934848. Modified EXIF Metadata Schema ----------------------------- The EXIF metadata schema is modified to allow the <GPSVersionID> element tag to be optional. This tag was previously required and if the tag was not present in the image then no <GpsIfd> element was produced. This affects the getMetadata() methods of ORDSYS.ORDImage. Fixed Problem Parsing Certain MP4 Videos ---------------------------------------- The Oracle Multimedia MP4 parser is enhanced to allow it to parse non-standard MP4 video files which begin with an MSNV atom. This fixes customer bug: 6342823. Fixed Problem Parsing New Format Quicktime Videos ------------------------------------------------- The Oracle Multimedia Quicktime parser is corrected to allow it to parse the new version of Quicktime video with the file type atom in the header. This fixes customer bug: 7196021. Modified DICOM Datatype Schema ------------------------------ The datatype schema is modified to allow any XML tag of type "VALUE_LOCATOR_T" to have any character. The type "VALUE_LOCATOR_T" used to have a pattern restriction that only allowed certain characters in a locator path. This affects the insertDocument() method of the ORDSYS.ORD_DICOM_ADMIN package. The datatype schema is also modified to allow any XML tag of type "DATASET_T" to be optional (minOccurs='0'). Previously any XML tag of type "DATASET_T" must be present in the XML metadata document otherwise it lead to schema validation errors. This affects the extractMetadata() method of the ORDSYS.OrdDicom object and ORDSYS.ORD_DICOM package. Finally, the datatype schema is modified to allow the optional attribute "number" for all the datatypes. For multi-valued DICOM attributes, the "number" attribute of each datatype in an XML metadata document is used to specify the order of the multiple values. This affects the setProperties() and extractMetadata() methods of the ORDSYS.OrdDicom object, and the extractMetadata() function of ORDSYS.ORD_DICOM package. Private Attribute Definer Names in DICOM Mapping and Anonymity Documents ------------------------------------------------------------------------ In this release, the processing of DICOM files that contain private attribute definer names consisting of the characters: "()[]{}$#*" is supported. In order to reference DICOM metadata tags that refer to private attribute definers using these characters, this release also extends the syntax for value locators used in the DICOM configuration documents to allow the expression of such definers. For more information on administering DICOM configuration documents, refer to Chapters 10, 11, and 12 of the Oracle Multimedia DICOM Developer's Guide. For more information on the value locator syntax, see chapter 10 of the Oracle Multimedia DICOM Developer's Guide. This fix was requested by customer bug: 8250789. Certain Invalid DICOM Files Can Now be Handled ---------------------------------------------- The default behavior for parsing binary DICOM files is now relaxed in order to accept attribute values with a VR of OB defined with a tag other than Pixel Data (7FE0,0010). When the parser encounters such attribute values, a warning is now issued instead of raising an error. This fix was requested by customer bug: 7629948. DICOM Metadata Extraction Creating Documents with Illegal XML Characters ------------------------------------------------------------------------ DICOM metadata extraction sometimes created XML documents with illegal XML characters. The operation would fail with error LPX-00216: invalid character. Input data with illegal XML characters is now excluded from the metadata document. This fix was requested by customer bug: 7615475. Features Added in This Release ============================== Image Sharpening ------------------ A new image processing operator 'SHARPEN' is added to the image process() and processCopy() methods. This operator can be used to sharpen images. This new function is requested by a customer bug: 6445241. The sharpen operator can be used with or without image scaling. For best image sharpening quality, Oracle recommends using the operator with image scaling. Fill PNG Format Image Transparency Region With the Specified Color ------------------------------------------------------------------ A new image processing operator 'transparencyFillColor' is added to the image process() and processCopy() methods. This operator can be used to fill the PNG format image transparency region with the specified color. This new function is requested by a customer bug: 7678517. The transparencyFillColor operator can be used with or without other image processing operators. Image Processing Operator nometadata ------------------------------------- A new image processing operator 'nometadata' is added to the image process() and processCopy() methods. This operator can be used to remove metadata when creating thumbnail images in order to create the smallest possible image thumbnail. Image Watermarking ------------------- Oracle Multimedia now includes new applyWatermark() methods to add an image or text watermark to any supported image. Support for the CMYK Content Format ------------------------------------ The setProperties(), process() and processCopy() methods are now supported for TIFF and JFIF images with pixel data stored in the CMYK content format. During processing, CMYK data is converted to standard RGB data according to standard formulas. New Constructor Functions for BLOBs and Other Sources for Object Types ----------------------------------------------------------------------- New constructor functions have been added to ORDSYS.ORDAudio, ORDSYS.ORDDoc, ORDSYS.ORDImage and ORDSYS.ORDVideo object types to construct objects from BLOBs and other sources such as local files. DICOM Metadata Extraction Enhancements --------------------------------------- Any portion of a DICOM attribute can now be extracted (for example, extraction of just the Last Name portion of the Patient Name attribute). In addition, Oracle Multimedia now allows extraction of a subset of DICOM metadata attributes as requested by a user or an application, without first extracting all DICOM attributes from the DICOM content. DICOM Constraint Definition Enhancements ----------------------------------------- The following enhancements have been added to Oracle Multimedia DICOM constraint definitions: - Recursive calls within constraint definitions are now supported. - Wildcard character syntax has been added to enable iteration through all the components in a single predicate. DICOM Content Processing Enhancements -------------------------------------- The following enhancements have been added to Oracle Multimedia DICOM: - DEFLATE transfer syntax support has been added. - RLE compression is now supported. - Encoding of multi-bit monochrome raw content is now supported. - YBR photometric interpretation is now supported. - DICOM to AVI and DICOM to MPEG conversions are now supported. - MPEG encapsulated into DICOM format is now supported. Oracle Data Pump Utilities Support for the DICOM Data Model Repository ----------------------------------------------------------------------- Oracle Multimedia DICOM now supports import and export operations of the DICOM data model repository using the Oracle Data Pump Import and Export utilities on the ORDDATA schema. The DICOM data model repository is now stored in the ORDDATA schema, a schema that is not excluded from import and export operations. Importing and Exporting of Data Model Documents ----------------------------------------------- The ORD_DICOM_ADMIN data model repository API now includes procedures for exporting and importing a set of documents from/to the data model repository to/from a ZIP archive file. Oracle Multimedia Mid-Tier Java API ------------------------------------ Oracle Multimedia Mid-Tier Java API enables users to write Java applications for extracting DICOM metadata outside of Oracle Database. To facilitate partitioning on DICOM metadata attributes, it is desireable to extract attributes on which data is partitioned before the data is loaded into the database. Oracle Multimedia Mid-Tier Java API enables users to extract this metadata before the data is loaded. Specifying Character Sets when SPECIFIC_CHARACTER_SET Tag is Missing --------------------------------------------------------------------- Strings in DICOM files that lack the SPECIFIC_CHARACTER_SET tag (00080005) are, by default, decoded using the ASCII character encoding. You can override this behavior by adding a preference document with a tag <SPECIFIC_CHARACTER_SET> that specifies an alternate character set. For more information, see the Oracle Multimedia DICOM Developer's Guide. This behavior was requested by customer bug: 7670599. Known Problems in This Release ============================== Must Recompile Java Applications -------------------------------- If you are using Oracle Multimedia Java Classes release 8.1.7, you must recompile your Java applications after installing Oracle Database. If you do not recompile, you may see an error similar to the following in OrdImageBase, OrdAudioBase, or OrdVideoBase when you use the new ordim libraries: java.lang.NoSuchMethodError: oracle.ord.im.OrdImageBase: method getUpdateTime()Ljava/sql/Timestamp; not found at ord89.main(ord89.java:32) Not All JSP Engines Support the Delivery of Multimedia Data from a JSP ---------------------------------------------------------------------- JSP engines are not required to support access to the servlet binary output stream. Therefore, not all JSP engines support the delivery of multimedia data from a JavaServer Page using the OrdHttpJspResponseHandler class. See Oracle Multimedia Servlets and JSP Java API Reference for more detailed information about the delivery of multimedia data from a JavaServer Page. Documentation Omissions and Corrections ======================================= Image Processing Limits ----------------------- This information represents the best understanding of Oracle Multimedia engineering at this time. The characterization of the limits for image processing is ongoing and may result in updated information. Updates will be posted on the Oracle Multimedia section of the Oracle Technology Network web site at: http://www.oracle.com/technology/products/multimedia/ Summary This section describes the capabilities and limitations of managing large images within Oracle database. Specifically, it addresses the limits for image storage and image processing. Image storage Practically speaking, there are no size restrictions on the image content that Oracle Multimedia can store and retrieve, both within database storage structures (BLOB) and outside of database storage structures (BFILE). Oracle Multimedia can manage individual images of up to 128TB in size for BLOB storage and up to 4GB for BFILE storage. Note: Most image file formats do not support file sizes larger than 4GB. In addition to storing and retrieving large images, Oracle Multimedia can also extract image attributes such as height, width, and compression format for images that contain up to two billion pixels or resolution up to 46000x46000. For any image for which metadata extraction is supported, Oracle Multimedia can extract and manage embedded metadata (IPTC-IIM, EXIF, XMP) for any size image that it can store. Oracle Multimedia can extract metadata, check the conformance, generate an anonymous copy, and produce a new DICOM object with updated metadata for any supported DICOM content that is capable of being stored. Image processing 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 Oracle Multimedia to interpret the pixel values of the image, which is often processor and memory intensive. Subsequently, Oracle Multimedia may not be able 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. Table 1 shows the maximum image size, expressed in pixel dimensions of width x height, that Oracle Multimedia can process for various image formats on a 32-bit platform. Table 2 shows the same limits for a 64-bit platform. Table 3 shows the maximum image size, expressed in pixel dimensions of width x height, that Oracle Multimedia can process for the DICOM image format on a 32-bit platform. Table 4 shows the same limits for a 64-bit platform. In these four tables, a limit of 3300x3300 means that any image can be processed so that the product of its width and height is less than or equal to the product of 3300 and 3300 (10890000). Note: The values in these four tables are conservative limits. They do not reflect the fact that the space required is a function of image format, content format, and compression format nor do they reflect future product development efforts. For example, it may be possible to process larger monochrome or grayscale images than the sizes mentioned in these four tables. Table 1. Maximum image size for processing, 32-bit platform. ------------------------------------------------------------- ImageFormat decoding(reading) encoding(writing) BMP 4700 x 4700 Unlimited (subject to resource constraints) FPIX 4700 x 4700 No write support GIFF 8000 x 8000 4700x4700 JFIF 46000 x 46000 4700x4700 J2K 46000 x 46000 4700x4700 PCXF 4700 x 4700 No write support PGMF 8000 x 8000 Unlimited (subject to resource constraints) PICT 4700 x 4700 10000x10000 PNGF 4700 x 4700 4700x4700 PNM/PPM 4700 x 4700 Unlimited (subject to resource constraints) RASF 4700 x 4700 No write support TGAF 4700 x 4700 10000x10000 TIFF 26700 x 26700 26700 x 26700(subject to resource constraints) Table 2. Maximum image size for processing, 64-bit platform. ------------------------------------------------------------- ImageFormat decoding(reading) encoding(writing) BMP 9000 x 9000 Unlimited (subject to resource constraints) FPIX 9000 x 9000 No write support GIFF 16000 x 16000 9000 x 9000 JFIF 46000 x 46000 9000 x 9000 J2K 46000 x 46000 9000 x 9000 PCXF 9000 x 9000 No write support PGMF 16000 x 16000 Unlimited (subject to resource constraints) PICT 9000 x 9000 20000x20000 PNGF 9000 x 9000 9000 x 9000 PNM/PPM 9000 x 9000 Unlimited (subject to resource constraints) RASF 9000 x 9000 No write support TGAF 9000 x 9000 20000x20000 TIFF 26700 x 26700 26700 x 26700(subject to resource constraints) Table 3. Maximum image size for DICOM processing, 32-bit platform. ------------------------------------------------------------------ Compression decoding(reading) encoding(writing) RAW/NONE Unlimited Unlimited (subject to resource constraints) JPEG 46000x46000 4700x4700 J2K 46000x46000 4700x4700 RLE 4700x4700 4700x4700 Table 4. Maximum image size for DICOM processing, 64-bit platform. ------------------------------------------------------------------- Compression decoding(reading) encoding(writing) RAW/NONE Unlimited Unlimited (subject to resource constraints) JPEG 46000x46000 9000x9000 J2K 46000x46000 9000x9000 RLE 9000x9000 9000x9000 Deprecated Features =================== Deprecated Object Types and APIs Are No Longer Supported -------------------------------------------------------- The deprecated image object types ORDImgB and ORDImgF have been removed and are no longer supported. The deprecated image indexing object types and operators ORDImageIndex, IMGSimilar, and IMGScore have been removed and are no longer supported. Any user defined indexes of type ORDImageIndex will be deleted on upgrade from an earlier release to Oracle Database 11g, Release 2 (11.2). In Oracle Database 11g, Release 1 (11.1), Oracle Multimedia introduced new and substantially enhanced features to support DICOM content. As a result, beginning with Oracle Database 11g, Release 2 (11.2), the DICOM support in ORDImage objects that was introduced in Oracle Database 10g, Release 2 (10.2) will not be enhanced, and may be deprecated in a future release. The ORDImage support for DICOM will continue to be available in Oracle Database 11g, Release 2. However, Oracle recommends writing new medical imaging applications to use the DICOM support that was introduced in Oracle Database 11g Release 1 (ORDDicom objects). Oracle also recommends migrating existing applications from the DICOM support in Oracle Database 10g, Release 2 (ORDImage objects) to the DICOM support in Oracle Database 11g, Release 1 (ORDDicom objects) at your convenience. See "Migrating from Release 10.2 DICOM Support" in Oracle Multimedia DICOM Developer's Guide for instructions. ======================= END OF README.txt
Ms-Dos/Windows
Unix
Write backup
jsp File Browser version 1.2 by
www.vonloesch.de