This chapter explains how to deinstall Oracle Utilities Data Model:
Backing up and recovering Oracle Utilities Data Model involves a two-step process to 1) backup or recover the relational objects, and 2) backup or recover the analytic workspace that is part of Oracle Utilities Data Model. These steps are outlined in the following topics:
Take the following steps to backup Oracle Utilities Data Model:
Backup the OUDM_SYS schema by executing the expdp utility.
This utility exports all physical tables containing the data and trained mining models. For more information, see Oracle Database Utilities.
Backup the analytic workspace that is part of the Oracle Utilities Data Model. The analytic workspace is backed up as an EIF file, named OUDM_BAK.EIF, which is generated under the ORACLE_HOME/oudm/pdm/olap directory.
Connect to the database with OUDM_sys.
Issue the following SQL statements.
exec dbms_aw.execute('AW ATTACH OUDM');
exec dbms_aw.execute('CDA OUDM_OLAP_DIR');
exec dbms_aw.execute('EXPORT ALL TO EIF FILE ', 'OUDM_BAK.EIF', ' NOTEMPDATA');
exec dbms_aw.execute('AW DETACH OUDM');
Take the following steps to restore Oracle Utilities Data Model from the backup files:
Restore the OUDM_SYS schema by executing the impdp utility.
This utility imports all physical tables containing the data and trained mining models. For more information, see Oracle Database Utilities.
Connect to the database with OUDM_sys, and import the analytic workspace that was saved as an EIF file, named OUDM_BAK.EIF, under the ORACLE_HOME/oudm/pdm/olap directory.
exec dbms_aw.execute('IMPORT ALL TO EIF FILE ','OUDM_BAK.EIF');
To deinstall Oracle Utilities Data Model, you do not simply run Oracle Universal Installer in deinstall mode. Instead, you perform the following tasks:
Backup Oracle Utilities Data Model, as described in "Exporting Oracle Utilities Data Model".
Stop any sessions that use the Oracle Utilities Data Model schemas, as described in "Before you Remove the Software".
Execute the deinstallation script, as described in "Deinstallation Script Execution".
If you are deinstalling the sample reports, perform the tasks described in "After you Remove the Software".
Note:
To deinstall Oracle Utilities Data Model, you do not simply run the Oracle Universal Installer in deinstall mode.The deinstallation script removes the OUDM_sys schema. Consequently, before you run the deinstallation script, ensure that there are no active sessions that connect to the OUDM_sys schema.
Identifying if the OUDM_sys schema is active
To identify if there are active sessions connecting to the schema take the following steps:
Sign in as DBA.
Execute the following SQL statements:
select SID,SERIAL# from v$session where USERNAME='OUDM_SYS';
If this query returns a session ID, then there is an active session.
Ending an active OUDM_sys schema session
To end an active session execute the following statement in which you replace sid and serial that are the session ID and serial number returned by the earlier queries.
alter system kill session 'sid,serial' ;
The following rules for tnsnames.ora are mandatory for Oracle Utilities Data Model deinstallation.
For a non Oracle RAC environment, the installer sets the SID to the value of the lowercase tnsnames entry chosen by the user during installation (as the Net Service Name). Thus, during deinstallation the tnsnames entry must accurately reflect the Net Service Name supplied as a parameter during installation.
For example, if the SID is orcl11203, you cannot set the tnsnames entry to OUDM_Test. If SID is orcl11203, then tnsnames entry must be set to orcl11203.
For an Oracle RAC environment, the Oracle System Identifier (SID) is set to lowercase tnsnames.ora entry chosen by the user during installation (as the Net Service Name). Thus, the tnsnames.ora entry should accurately reflect the SID for the system on which product is deinstalled in an Oracle RAC environment.
Modify the tnsnames.ora entry name to match the SID of the database node for the system. After the deinstallation, revert the tnsnames entry to the previous entry.
For example, if the SID is orcl2, you cannot set the tnsnames entry to localhost_orcl. In this case, if the SID is orcl2, then the tnsnames entry must be set to orcl2.
To execute the Oracle Utilities Data Model deinstallation script:
Set the ORACLE_HOME to the location of the database on which to deinstall Oracle Utilities Data Model.
For example, suppose that Oracle home is in the directory /loc/app/oracle/product/dbhome
In a Bourne, Bash, or Korn shell, use these commands to set ORACLE_HOME:
$ ORACLE_HOME=/loc/app/oracle/product/dbhome $ export ORACLE_HOME
In a C shell, use this command to set ORACLE_HOME
% setenv ORACLE_HOME /loc/app/oracle/product/dbhome
Execute the Oracle Utilities Data Model deinstallation script:
$ORACLE_HOME/oudm/OUDM_deinstall.sh
When prompted, enter the SYSTEM password.
The script deconfigures Oracle Utilities Data Model and executes the Oracle Universal Installer in deinstall silent mode.
If you are deinstalling the sample reports, after the deinstallation script runs, perform the tasks described in "After you Remove the Software".
If you are deinstalling the Oracle Utilities Data Model sample reports, follow these steps to perform additional cleanup:
Delete oudm.rpd in the directory BIHome/Server/Repository.
Delete the OUDMwebcat folder in BIDataHome/web/catalog.
Delete the following line from BIHome/Server/Config/NQSConfig.INI:
Star = oudm.rpd, DEFAULT