Oracle® Multimedia User's Guide 11g Release 2 (11.2) Part Number E10777-03 |
|
|
PDF · Mobi · ePub |
This appendix describes the management of Oracle Multimedia.
This appendix includes these sections:
Note:
See the Oracle MultimediaREADME.txt
file located in <ORACLE_HOME>
/ord/im/admin
for the latest information.The Oracle Multimedia installation procedure performs these functions:
Creates the database users shown in Table B-1 with the privileges required by Oracle Multimedia.
Creates the default passwords shown in Table B-2 for the Oracle Multimedia and MDSYS
user accounts, and then locks the accounts and marks their default passwords as expired.
Table B-2 User Accounts and Default Passwords
User Account | Installation Password |
---|---|
|
|
|
|
|
|
|
|
|
|
Caution:
Oracle does not recommend logging in directly to the user accounts shown in Table B-2.Grants the EXECUTE privilege to the user group PUBLIC for the Oracle Multimedia packages and objects installed in these schemas:
ORDSYS
ORDPLUGINS
SI_INFORMTN_SCHEMA
MDSYS
Oracle Multimedia is automatically installed and configured with Oracle Database.
The following subsections describe the steps to perform before manual installation and configuration of Oracle Multimedia, and the steps for manually installing and configuring it:
Caution:
Performing any of these prohibited actions could cause internal errors and security violations in the database management system.These users are created during database installation, and might change in future releases:
Users in which Oracle-supplied Oracle Multimedia is installed: ORDSYS
, ORDPLUGINS
, SI_INFORMTN_SCHEMA
, and ORDDATA
User in which Oracle Multimedia Locator is installed if Oracle Spatial is not installed: MDSYS
Do not delete any of these users.
Do not connect to or modify any of these users or their contents (which are supplied by Oracle Multimedia and reserved by Oracle), with these exceptions:
You can add user-defined packages to the user ORDPLUGINS
(see Chapter 7).
DICOM administrators store user-defined DICOM data model configuration documents in the user ORDDATA, using the DICOM data model repository API. See Oracle Multimedia DICOM Developer's Guide for more information about inserting documents into the data model repository.
Before installing and configuring Oracle Multimedia manually, perform these steps:
Install Oracle Database, including PL/SQL, Oracle JVM, Oracle XML Database, and Oracle XDK.
Create the database.
Start the database.
Verify that the required software is correctly installed and valid, as follows:
Run SQL*Plus, connect as SYSDBA, and enter these 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';
Examine the results of the queries to ensure that each version
value is identical to the version of Oracle Multimedia that you are installing and each status
value is VALID
.
See Also:
Oracle Database Installation Guide for your operating system for more detailed information
These steps are not required if you use the Database Configuration Assistant.
To install and configure Oracle Multimedia manually, perform these steps (<ORACLE_HOME>
represents the Oracle home directory):
Use Oracle Universal Installer to install the files that comprise Oracle Multimedia on your system.
Decide which tablespace to use for the Oracle Multimedia users, and which tablespace to use for the Oracle Spatial/Oracle Multimedia Location Services user (see Table B-1). Oracle recommends using the SYSAUX tablespace for all of these users.
Create the users and grant the appropriate privileges, as follows:
Start SQL*Plus and connect as SYSDBA:
% sqlplus SQL> CONNECT sys as sysdba
Call the script ordinst.sql
, with two parameters for the Oracle Multimedia tablespace and the Oracle Spatial/Oracle Multimedia Location Services tablespace:
On Linux and UNIX:
SQL> @<ORACLE_HOME>/ord/admin/ordinst.sql SYSAUX SYSAUX
On Windows:
SQL> @<ORACLE_HOME>\ord\admin\ordinst.sql SYSAUX SYSAUX
Install the Oracle Multimedia types and packages, as follows:
Call the script catim.sql
, while you are connected as SYSDBA:
On Linux and UNIX:
SQL> @<ORACLE_HOME>/ord/im/admin/catim.sql
On Windows:
SQL> @<ORACLE_HOME>\ord\im\admin\catim.sql
Now Oracle Multimedia is ready for use.
After installing or upgrading Oracle Multimedia, you can verify the Oracle Multimedia installation by calling the Oracle Multimedia validation procedure.
To run the Oracle Multimedia validation procedure, perform these steps:
Start SQL*Plus and connect as SYSDBA:
% sqlplus SQL> CONNECT sys as sysdba
Execute the procedure sys.validate_ordim
:
SQL> execute sys.validate_ordim;
If the validation procedure detects invalid objects, it lists the first few invalid objects and sets the registry entry to INVALID
; otherwise, it silently sets the Oracle Multimedia registry entry to VALID
.
Verify that the registry entry for Oracle Multimedia is correct, as follows:
Enter this query from SQL*Plus, while you are connected as SYSDBA:
SQL> select version, status from dba_registry where comp_id='ORDIM';
Examine the result of the query to ensure that the version
value is correct and the status
value is VALID
.
If you upgrade a database from an earlier release of Oracle Database, Oracle Multimedia is upgraded automatically if it is detected in the source database.
See Also:
Oracle Database Upgrade Guide for detailed upgrading instructions
Oracle Multimedia is automatically downgraded when you downgrade a database with the Oracle Multimedia feature installed.
Caution:
Do not modify your DICOM data model repository until you are sure that you are not going to downgrade from Oracle Database 11g Release 2 (11.2) back to the source release.Changes to the Oracle Multimedia DICOM data model repository (such as document insertions or deletions) that you make after a database upgrade are lost after a database downgrade.
See Also:
Oracle Database Upgrade Guide for detailed downgrading instructions
To remove Oracle Multimedia manually, perform these steps:
Start SQL*Plus, and connect as SYSDBA:
% sqlplus SQL> CONNECT sys as sysdba
Call the script catcmprm.sql
, with the parameter ORDIM
:
On Linux and UNIX:
SQL> @<ORACLE_HOME>/rdbms/admin/catcmprm.sql ORDIM
On Windows:
SQL> @<ORACLE_HOME>\rdbms\admin\catcmprm.sql ORDIM
If one or more components that depend on Oracle Multimedia (such as Oracle Spatial) are installed, this message appears:
ORDIM cannot be removed as it has the following dependencies: Component: SDO Namespace: SERVER
If no dependent components are installed, a message appears, indicating either that Oracle Multimedia is or is not in use.
Then, a prompt asks if you really want to remove Oracle Multimedia.
Reply to the prompt with Y
or y
to remove Oracle Multimedia.
Oracle Multimedia is removed with force (regardless of whether it is in use).