
 Copyright (c) 1998, 2013, Oracle and/or its affiliates. All rights reserved. 

  NAME
        README.txt -  ORACLE Multimedia (formerly known as interMedia)
                      RELEASE INFORMATION

        RELEASE 12.1 README FILE
 
                        =======================

Contents
========
        Feature Name Change
        Getting Started
        Oracle Multimedia Release 12.1
        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
        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 this release.

Getting Started
===============
This document describes release information for Oracle Multimedia.


Oracle Multimedia Release 12.1
==============================

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/technetwork/database/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.

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 Oracle Database 11g Release 2
(11.2) 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 Use the catcon.pl Perl script to run the Oracle Multimedia installation
    scripts. The catcon.pl Perl script is in the $ORACLE_HOME/rdbms/admin
    directory.

    1) Create the users and grant the appropriate privileges.

       If you are using a tablespace other than SYSAUX, replace the 
       '--pSYSAUX' parameters with the tablespace you have chosen.  
       The first parameter is the tablespace to be used for Oracle
       Multimedia, the second is the tablespace to be used for Oracle
       Spatial and Graph.

    (On Linux/UNIX)
       perl catcon.pl -u SYS -d $ORACLE_HOME/ord/admin -b ordinst ordinst.sql '--pSYSAUX' '--pSYSAUX'

    (On Windows)
       perl catcon.pl -u SYS -d %ORACLE_HOME%\ord\admin -b ordinst ordinst.sql '--pSYSAUX' '--pSYSAUX'


    2) Install the Oracle Multimedia types and packages.

    (On Linux/UNIX)
       perl catcon.pl -u SYS -d $ORACLE_HOME/ord/im/admin -b catim catim.sql

    (On Windows)
       perl catcon.pl -u SYS -d %ORACLE_HOME%\ord\im\admin -b catim catim.sql

 
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 this release of Oracle Database 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 
may be lost after a database downgrade.  


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 JDBC library, the XDB Java classes library and the XML Java
API library, if you are using the DICOM feature or Oracle Multimedia metadata 
extraction, and the Oracle Multimedia DICOM Java API library if you are using
the DICOM feature.

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 6 or later:
        <ORACLE_HOME>/ord/jlib/ordim.jar
        <ORACLE_HOME>/jdbc/lib/ojdbc6.jar
        <ORACLE_HOME>/rdbms/jlib/xdb.jar  (for DICOM and metadata extraction)
        <ORACLE_HOME>/lib/xmlparserv2.jar (for DICOM and metadata extraction)
        <ORACLE_HOME>/ord/jlib/orddicom.jar (for DICOM only)
        <ORACLE_HOME>/ord/jlib/ordhttp.jar (for servlets and JSP only)
        <ORACLE_HOME>/jlib/orai18n.jar (optional, see note)


    Windows:
      JDK 6 or later:
        <ORACLE_HOME>\ord\jlib\ordim.jar
        <ORACLE_HOME>\jdbc\lib\ojdbc6.jar
        <ORACLE_HOME>\rdbms\jlib\xdb.jar  (for DICOM and metadata extraction)
        <ORACLE_HOME>\lib\xmlparserv2.jar (for DICOM and metadata extraction)
        <ORACLE_HOME>\ord\jlib\orddicom.jar (for DICOM only)
        <ORACLE_HOME>\ord\jlib\ordhttp.jar (for servlets and JSP only)
        <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 libocijdbc12.so)
    Windows:
        <ORACLE_HOME>\bin (for ocijdbc12.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 
==============================


 
Features Added in This Release
==============================

DICOM Protocol Support
----------------------
The DICOM standard specifies both an imaging file format and a
networking protocol to be used in the medical imaging domain.  Picture
Archving and Communication Systems (PACS) are designed to store and
transfer medical images in the DICOM format using the DICOM network
protocol.  Medical imaging devices such as CT scanners and MR machines
communicate with one or more PACS to store images.  Health care
professionals then review images using DICOM viewer applications which
query PACS to retrieve relevant patient information and images.

In previous versions, Oracle Multimedia DICOM has supported only the
imaging file format.  Beginning with Oracle Database 12c Release 1
(12.1), Oracle Multimedia DICOM adds support for the DICOM networking
protocol. This support allows Oracle Database to retrieve and manage
images originally stored in PACS or on the local file system. It also
allows DICOM viewers to view images stored and managed by Oracle
Database.

See the Oracle Multimedia DICOM Developer's Guide for a detailed 
description of this feature. 

Support for DICOM Content in Oracle WebCenter Content
-----------------------------------------------------
Oracle Multimedia DICOM support has been integrated into Oracle WebCenter
Content.  With this support, Oracle WebCenter Content can now be used to
store and manage DICOM content.

See Oracle Multimedia DICOM Developer's Guide for more information.

Support for Full Mode Database Export and Import
------------------------------------------------
Full database export and full database import using the Oracle Data Pump
utilities are now supported for Oracle Multimedia.

See Oracle Multimedia DICOM Developer's Guide for more information.

Support for Oracle Multimedia in Pluggable Databases
----------------------------------------------------
A container database (CDB) is a single physical database that contains at
least one pluggable database (PDB). A PDB is a set of schemas within a CDB
that appears to applications as a separate database. A non-CDB is a 
traditional Oracle database that cannot contain a PDB.  Oracle Multimedia
is supported in both environments.

See Oracle Database Concepts and Oracle Database Administrator's Guide for
more information about Pluggable Databases.


Known Problems in This Release
==============================

Processing JPEG-LOSSLESS and JPEG_LS DICOM images on Solaris:
--------------------------------------------------------------------
The DBA should grant the following permissions to the ORDSYS schema:
     dbms_java.grant_permission('ORDSYS', 'SYS:java.io.FilePermission', '/bin/isalist', 'execute' );

     dbms_java.grant_permission
        ('SYS',
         'SYS:oracle.aurora.rdbms.security.PolicyTablePermission',
        '0:java.lang.RuntimePermission#loadLibrary.clib_jiio_vis',
         null);

     dbms_java.grant_permission
        ('SYS',
         'SYS:oracle.aurora.rdbms.security.PolicyTablePermission',
         '0:java.lang.RuntimePermission#loadLibrary.clib_jiio_vis2',
         null);

     dbms_java.grant_permission( 'ORDSYS', 'SYS:java.lang.RuntimePermission',
        'loadLibrary.clib_jiio_vis', '' );

     dbms_java.grant_permission( 'ORDSYS', 'SYS:java.lang.RuntimePermission',
       'loadLibrary.clib_jiio_vis2', '' );


Documentation Omissions and Corrections
=======================================

Oracle Multimedia Procedure to Move Out of or Into SYSAUX Tablespace
--------------------------------------------------------------------
Oracle Multimedia depends on a number of pre-defined tables used 
internally by the Oracle Multimedia functions and procedures. These 
tables are typically stored in the SYSAUX tablespace. However, it is 
possible to relocate these tables to another tablespace using the 
ORDSYS.ORD_ADMIN.move_ordim_tblspc procedure. For example, in order 
to move these tables to a tablespace, TBSNEW, the user could issue 
the following command:

    exec ordsys.ord_admin.move_ordim_tblspc('TBSNEW');

Note that when running this procedure in CDB mode, special precautions 
must be taken. First, the user must make sure that the destination 
tablespace exists in all CDB containers (root, seed, and all PDBs). 
Then, the user must execute the command to move the tablespace using 
the "catcon.pl" script to run the command on all CDB containers.

See the Oracle Database Administrator's Guide for more information 
about the SYSAUX tablespace and moving occupants into and out of the 
SYSAUX tablespace, and for information about the catcon.pl script.

Defining the CONFORMANCE_LEVEL Preference Parameter
------------------------------------------------------------
The CONFORMANCE_LEVEL preference parameter is used to specify which types of
errors and exceptions Oracle Multimedia DICOM ignores or reports when
processing DICOM content. The following XML fragment shows how to define 
this preference parameter in a preference document.

  <PREFERENCE_DEF>
    <PARAMETER>CONFORMANCE_LEVEL</PARAMETER>
    <DESCRIPTION>
      Ignore selected exceptions.
    </DESCRIPTION>
    <VALUE>ignoreException</VALUE>
  </PREFERENCE_DEF>

Valid values are: leastConform, ignoreException, and mostConform.
The default is ignoreException.

The default value ignoreException instructs all functions to ignore the types
of exceptions specified in the preference parameter IGNORED_EXP_LIST.

The value leastConform instructs all functions to ignore errors and exceptions
to maximize the processing of DICOM content.

If the value is set to mostConform, all functions throw an exception when
encountering DICOM content that does not conform to the DICOM standard. (This
behavior does not include backward compatibility cases that are allowed by the
DICOM standard.)

For more information refer to the Preference Document Schema: ordcmpf.xsd in
the ord/xml/xsd directory under <ORACLE_HOME>.

Defining the IGNORED_EXP_LIST Preference Parameter
---------------------------------------------------
The IGNORED_EXP_LIST preference parameter is used to specify the types of
exceptions that Oracle Multimedia DICOM ignores when processing DICOM content.
This preference parameter is effective only when the value of the
CONFORMANCE_LEVEL preference parameter is set to ignoreException.

The following XML fragment shows how to define this preference parameter in a
preference document.

  <PREFERENCE_DEF>
    <PARAMETER>IGNORED_EXP_LIST</PARAMETER>
    <DESCRIPTION>
      Do not throw exceptions if: mandatory attributes are missing
      from the DICOM content (MISSING_ATTR), the DICOM file magic number
      "DICM" is missing (MISSING_MAGIC), an attribute has an invalid value
      representation value (INVALID_VR), an attribute has an incorrect
      value multiplicity (INVALID_VM), or a DICOM Part 10 file contains
      invalid data (PARSE_ERR).
    </DESCRIPTION>
    <VALUE>MISSING_ATTR MISSING_MAGIC INVALID_VR INVALID_VM PARSE_ERR</VALUE>
  </PREFERENCE_DEF>

For more information refer to the Preference Document Schema: ordcmpf.xsd in
the ord/xml/xsd directory under <ORACLE_HOME>.

createDicomImage() Now Removes Original DICOM Metadata
------------------------------------------------------
If the source content that is input to the createDicomImage() procedure is
DICOM content, the resulting destination DICOM content contains only the
metadata that was input to this procedure. Thus, in the destination DICOM
content, the metadata in the source DICOM content is removed and replaced by
the metadata that was input.


Custom Metadata XML Schemas for Mapping Documents Can be Local Schemas
------------------------------------------------------------------------
The custom metadata XML schemas associated with user-defined mapping documents
can now be registered with Oracle XML DB as local schemas. Register your custom
metadata XML schema with Oracle XML DB as a local schema to prevent other users
from using it for validation. Or, register your custom metadata XML schema with
Oracle XML DB as a global schema to allow other users to validate against it.

When the extractMetadata() operation is performed with validation turned on
(the preference value VALIDATE_METADATA is true), the ORA-53259 error will be
raised if the metadata namespace in the mapping document is not available to
the current user.

DICOM Protocol Image Versioning
-------------------------------
The DICOM protocol adapter supports retaining multiple versions of an image
(instead of discarding the duplicate images) in the event that multiple images
with the same SOP Instance UID are sent to the DICOM protocol adapter.
Versioning works by making use of a "version" column specified by the user for
each table supplied in the database protocol configuration document. A sequence
(strictly increasing) is used to assign a version number to each image on
storage. Thus, each image is uniquely identified by its corresponding SOP
Instance UID-Version Number pair. On retrieval, the image with the largest
version number is returned.

The following is a sample configuration document for a deployment that uses
versioning:

    <?xml version="1.0"?>
    <DICOM_PROTOCOL xmlns="http://xmlns.oracle.com/ord/dicom/protocol_1_0"
      xmlns:dt="http://xmlns.oracle.com/ord/dicom/datatype_1_0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://xmlns.oracle.com/ord/dicom/protocol_1_0 http://xmlns.oracle.com/ord/dicom/protocol_1_0">
      <STORAGE table='test.dicom_orcl_meta' id_col="sop_instance_uid" ver_col="image_ver">
        <ATTRIBUTE column='"STUDY_INSTANCE_UID"' tag="0020000D"/>
        <ATTRIBUTE column='"SERIES_INSTANCE_UID"' tag="0020000E"/>
      </STORAGE>
      <STORAGE table='test.dicom_orcl_dcm' id_col="sop_instance_uid" ver_col="image_ver">
        <DICOM column="blob_data" type="BLOB" retain="true"/>
      </STORAGE>
    </DICOM_PROTOCOL>

Note that the name of the version column can be different for each table.
However, in order to enable versioning support, all tables in the configuration
must specify a version column.


DICOM Extraction with Private Tag Group and Name
------------------------------------------------
The DICOM protocol adapter supports the extraction of private tags based
on group number and tag name (without having to know the tag element number).
In order to configure this, it is necessary to first create a private
dictionary document that describes the private attribute and to insert the
document into the DICOM data model repository of Oracle Database (see Oracle
Multimedia DICOM Developer's Guide). The following is a sample private
dictionary document that describes a private attribute, (0031,XX00), where X
is a wildcard matching any hexadecimal digit:

    <?xml version="1.0"?>
    <DICOM_PRIVATE_ATTRIBUTES
      xmlns="http://xmlns.oracle.com/ord/dicom/privateDictionary_1_0"
      xmlns:dt="http://xmlns.oracle.com/ord/dicom/datatype_1_0"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://xmlns.oracle.com/ord/dicom/privateDictionary_1_0 http://xmlns.oracle.com/ord/dicom/privateDictionary_1_0">
      <PRIVATE_ATTRIBUTE_DEFINITION>
        <TAG>0031XX00</TAG>
        <NAME>LINKED ATTRIBUTES 1.0</NAME>
        <DEFINER>LINKED ATTRIBUTES 1.0</DEFINER>
        <VR>UN</VR>
        <VM>1</VM>
      </PRIVATE_ATTRIBUTE_DEFINITION>
    </DICOM_PRIVATE_ATTRIBUTES>

Once the private dictionary document is inserted into the DICOM data model
repository, it is possible to configure the DICOM protocol adapter to use the
private attribute:

   ?xml version="1.0"?>
   <DICOM_PROTOCOL xmlns="http://xmlns.oracle.com/ord/dicom/protocol_1_0"
     xmlns:dt="http://xmlns.oracle.com/ord/dicom/datatype_1_0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://xmlns.oracle.com/ord/dicom/protocol_1_0 http://xmlns.oracle.com/ord/dicom/protocol_1_0">
     <STORAGE table='test.dicom_orcl_meta' id_col="sop_instance_uid">
       <ATTRIBUTE column='"STUDY_INSTANCE_UID"' tag="0020000D"/>
       <ATTRIBUTE column='"SERIES_INSTANCE_UID"' tag="0020000E"/>
       <SPECIAL_TAG column='"DICOM_00311000"' tag_name="LINKED ATTRIBUTES 1.0" 
         definer="LINKED ATTRIBUTES 1.0"/>
     </STORAGE>
     <STORAGE table='test.dicom_orcl_dcm' id_col="sop_instance_uid">
       <DICOM column="blob_data" type="BLOB"/>
     </STORAGE>
   </DICOM_PROTOCOL>

Note that the values of the tag_name and definer attributes of <SPECIAL_TAG>
in the DICOM protocol adapter configuration document must match the values of
<NAME> and <DEFINER> tags, respectively, in the <PRIVATE_ATTRIBUTE_DEFINITION>
section of the private dictionary document.


DICOM Metadata Extraction with BLOB and Mapping Document
--------------------------------------------------------
In order to improve metadata extraction performance when using BLOB storage,
it is possible to specify a DICOM mapping document to use during metadata
extraction (see Oracle Multimedia DICOM Developer's Guide). Only those
attributes specified in the mapping document will be extracted. This provides
performance improvements similar to inserting a stored tag list document for
use with ORDDicom storage. The following is a sample configuration document
for a deployment that specifies a DICOM mapping document:

   <?xml version="1.0"?>
   <DICOM_PROTOCOL xmlns="http://xmlns.oracle.com/ord/dicom/protocol_1_0"
     xmlns:dt="http://xmlns.oracle.com/ord/dicom/datatype_1_0"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://xmlns.oracle.com/ord/dicom/protocol_1_0 http://xmlns.oracle.com/ord/dicom/protocol_1_0">
     <ADMIN_DOC doc_type='MAPPING' doc_name="ordcmmp.xml" doc_option="STANDARD"/>
     <STORAGE table='test.dicom_orcl_meta' id_col="sop_instance_uid">
       <ATTRIBUTE column='"STUDY_INSTANCE_UID"' tag="0020000D"/>
       <ATTRIBUTE column='"SERIES_INSTANCE_UID"' tag="0020000E"/>
     </STORAGE>
     <STORAGE table='test.dicom_orcl_dcm' id_col="sop_instance_uid">
       <DICOM column="blob_data" type="BLOB"/>
     </STORAGE>
   </DICOM_PROTOCOL>


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 12c, Release 1 (12.1).
 
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 12c, Release 1.  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).  See "Migrating from Release 10.2 DICOM Support" in 
Oracle Multimedia DICOM Developer's Guide for instructions.

=======================
END OF README.txt





