MINI MINI MANI MO
Copyright (c) 1998, 2016, Oracle and/or its affiliates. All rights reserved.
NAME
README.txt - ORACLE Multimedia (formerly known as interMedia)
RELEASE INFORMATION
RELEASE 12.2 README FILE
=======================
Contents
========
Getting Started
Oracle Multimedia Release 12.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
Problems Fixed in This Release
Features Added in This Release
Known Problems in This Release
Documentation Omissions and Corrections
Getting Started
===============
This document describes release information for Oracle Multimedia.
Oracle Multimedia Release 12.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 several audio and video file
formats.
Oracle Technology Network
=========================
For the most recent information about Oracle Multimedia, go to the Oracle
Multimedia section of the Oracle Technology Network web site at:
http://www.oracle.com/technetwork/index.html
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 about Oracle Locator see "Oracle Spatial And Graph Developer's
Guide".
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 "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 support 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 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 "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 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 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.
Problems Fixed in This Release
==============================
Multimedia Invalid After Upgrade
--------------------------------
Oracle Multimedia will no longer be invalid in the registry after upgrade
when there are no invalid Oracle Multimedia related objects, but there
are warning messages that XML DB or other dependent products were
INVALID before the upgrade. This fix applies to Bug 21683341
Processing FAX3 Encoded TIFF File Fails with IMG-00002
------------------------------------------------------
Using the processCopy() method on FAX3 encoded TIFF images, Oracle
Multimedia can now successfully decode and process the images. This fix
applies to Bug 21167961.
Processing BMPRLE Compressed File to PNG Fails with IMG-00002
-------------------------------------------------------------
Using the processCopy() method on a BMP image with RLE4 encoding and an odd
number width, Oracle Multimedia can now successfully decode and process the
image. This fix applies to Bug 21155045.
Invalid XML Generated When Processing Images From Panasonic DMC-ZS10
--------------------------------------------------------------------
Using the getMetadata() method, Oracle Multimedia can now extract metadata
correctly from JPEG images generated with a Panasonic DMC-ZS10. In previous
releases, this method returned an XML document that contained a NULL value,
making it invalid. This fix applies to Bug 17458637.
Incoming DICOM Storage Commitment Request Specifying Unknown AE
---------------------------------------------------------------
When receiving an incoming DICOM Storage Commitment request, if the target
AE is not specified in the AE map (defined in "ordim_adapter_config.xml"),
the DICOM protocol adapter will now output an appropriate error message to
the log indicating that it is not possible to send a storage commitment
response to an unknown AE. The adapter will also return an error status in
the N-ACTION-RSP message. The DICOM protocol adapter will no longer throw
an exception. This fix applies to Bug 16203709.
Features Added in This Release
==============================
PL/SQL Package Interface
------------------------
For users who do not wish to use the Oracle Multimedia object types for
storage, this release adds new PL/SQL packages that include the features
of Oracle Multimedia. Users who store multimedia data directly in BLOBs
and BFILEs can use these new PL/SQL packages to take advantage of the
features of Oracle Multimedia such as metadata extractions, image processing,
and image watermarking. The new packages are ORDSYS.ORD_AUDIO, ORDSYS.ORD_DOC,
ORDSYS.ORD_IMAGE, and ORDSYS.ORD_VIDEO.
For information on how to use these new packages, see the package
specifications in ORACLE_HOME:
<ORACLE_HOME>/ord/im/admin/ordarpsp.sql - ORD_AUDIO
<ORACLE_HOME>/ord/im/admin/orddrpsp.sql - ORD_DOC
<ORACLE_HOME>/ord/im/admin/ordirpsp.sql - ORD_IMAGE
<ORACLE_HOME>/ord/im/admin/ordvrpsp.sql - ORD_VIDEO
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
=======================================
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
=======================
END OF README.txt
OHA YOOOO