Skip Headers
Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide
12c Release 3 (12.1.0.3)

E24089-27
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

E Using the RepManager Utility

This appendix describes the RepManager utility. In particular, this appendix covers the following:

E.1 Overview

RepManager is a utility that enables you to upgrade and drop Oracle Management Repository, selectively purge plug-ins, and load dlf messages to Oracle Management Repository. This utility is available in the Oracle Management Service (OMS) home:

For UNIX operating systems:

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager

For Microsoft Windows operating systems:

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager.bat

This utility is invoked by Repository Configuration Assistant while installing a complete Enterprise Manager system, and by Repository Upgrade Configuration Assistant while upgrading to Enterprise Manager Cloud Control.

Note:

If you want to drop the Enterprise Manager schema completely, then use the RepManager available in the OMS home. Do not use the one in database home because it cannot remove the Enterprise Manager schema completely.

E.2 Supported Actions and Commands

Table E-1 shows the list of actions and their associated commands supported by the RepManager utility.

WARNING:

The RepManager in drop mode puts the database in quiesce mode by "ALTER SYSTEM QUIESCE RESTRICTED;" command.

Table E-1 Actions and Commands Supported by RepManager

Action Command Description Example

preupgrade

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action preupgrade <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman [-mwHome <Middleware home>] -pluginDepList "<pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>" -runAsReposUser <TRUE/FALSE> -dlfSources "<oms home>,<plugin1 home>,<plugin2home>"

Use this action to perform steps before upgrading an Oracle Management Repository with the following parameters:

  • Specify the host, port, and SID to connect to Oracle RDBMS where Oracle Management Repository is to be upgraded.

  • Specify the database user and password, repository name (SYSMAN) and password for SYSMAN user, and Middleware home to upgrade the Oracle Management Repository.

  • Specify a comma-separated list of plug-ins to be deployed according to the dependency. You can pass a file with this option, the contents being a comma-separated list of plug-in IDs. If the -pluginDepList parameter is not set, or is left with an empty list (for example, "{}"), then the following is read, by default, to retrieve the plug-in dependency list:

    $<OMS_HOME>/sysman/admin/emdrep/plugininfo/pluginDepList

  • Depending on how the plug-ins can be deployed, specify whether they must be deployed as SYS or SYSMAN, which is the repository user. To deploy them as SYSMAN, set the -runAsReposUser parameter to TRUE. If you do not pass this parameter, by default, the plug-ins will be deployed as SYS user.

  • Specify a comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being comma-separated locations for DLF files from platform/plugins. If the -dlfSources parameter is not set, or is left with an empty list (for example, "{}"), then the following is read, by default, to retrieve the dlf resource locations:

    $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources

    If this option is missing and default dlfSources file is not present, only dlf files for platform will be picked. If this is present, only the DLFs under these sources will be picked up.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action preupgrade example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -mwHome /scratch/weblogic/middleware -pluginDepList <pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>

upgrade

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action upgrade <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman [-mwHome <Middleware home>]-pluginDepList "<pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>" -runAsReposUser <TRUE/FALSE> -dlfSources "<oms home>,<plugin1 home>,<plugin2home>"

Note: Run preupgrade before performing upgrade action.

Use this action to upgrade an Oracle Management Repository with the following parameters:

  • Specify the host, port, and SID to connect to Oracle RDBMS where Oracle Management Repository is to be upgraded.

  • Specify the database user and password, repository name (SYSMAN) and password for SYSMAN user, and Middleware home to upgrade the Oracle Management Repository.

  • Specify a comma-separated list of plug-ins to be deployed according to the dependency. You can pass a file with this option, the contents being a comma-separated list of plug-in IDs. If the -pluginDepList parameter is not set, or is left with an empty list (for example, "{}"), then the following is read, by default, to retrieve the plug-in dependency list:

    $<OMS_HOME>/sysman/admin/emdrep/plugininfo/pluginDepList

  • Depending on how the plug-ins can be deployed, specify whether they must be deployed as SYS or SYSMAN, which is the repository user. To deploy them as SYSMAN, set the -runAsReposUser parameter to TRUE. If you do not pass this parameter, by default, the plug-ins will be deployed as SYS user

  • Specify a comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being comma-separated locations for DLF files from platform/plugins. If the -dlfSources parameter is not set, or is left with an empty list (for example, "{}"), then the following is read, by default, to retrieve the dlf resource locations:

    $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources

    If this option is missing and default dlfSources file is not present, only dlf files for platform will be picked. If this is present, only the DLFs under these sources will be picked up.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action upgrade example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -mwHome /scratch/weblogic/middleware -pluginDepList <pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>

transX

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action transx <repository_database_host> <repository_database_port> <repository_database_sid> -reposName sysman [-mwHome <Middleware home>] -dlfSources "<oms home>,<plugin1 home>,<plugin2home>"

Note: You can also run -doTransX. By default, it is set to true. If you set the value to false, no translation bundles are loaded. This is applicable for -dlfSources for preupgrade and upgrade actions.

Use this action to load the translation resources to the Oracle Management Repository with the following parameters:

  • Specify the host, port, and SID to connect to Oracle RDBMS to load translation resources to Oracle Management Repository.

  • Specify the database user and password, repository name (SYSMAN) and password for SYSMAN user, and Middleware home to load translation resources to Oracle Management Repository.

  • Specify a comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being comma-separated locations for DLF files from platform/plugins. If the -dlfSources parameter is not set, or is left with an empty list (for example, "{}"), then the following is read, by default, to retrieve the dlf resource locations:

    $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources

    If this option is missing and default dlfSources file is not present, only dlf files for platform will be picked. If this is present, only the DLFs under these sources will be picked up.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action transx example.com 1521 db3 -reposName sysman -mwHome /scratch/WLS/middleware

resume

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -resume retry <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman [-mwHome <Middleware home>] -checkpointLocation <directory where schemamanager stores checkpoints>

Use this action to resume the last failed action, for example, upgrade.

  • Specify the host, port, and SID to connect to Oracle RDBMS where the action is to be resumed.

  • Specify the database user and password, repository name (SYSMAN) and password for SYSMAN user, and Middleware home where the action is to be resumed.

  • Specify the location at which to resume the step. The checkpoint location is $<OMS_HOME>/sysman/log/schemamanager.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -resume retry -checkpointLocation /scratch/weblogic/middleware/oms/sysman/log/schemamanager -mwHome /scratch/weblogic/middleware

drop

OR

dropall

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action drop <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman [-mwHome <Middleware home>] [-mwOraHome <Oracle Home>]

OR

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action dropall <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman [-mwHome <Middleware home>] [-mwOraHome <Oracle Home>]

Ensure that there are no active sessions, scheduler jobs, and dbms_jobs running for SYSMAN, SYSMAN_MDS SYSMAN_OPSS, and SYSMAN_APM. Ensure that none of these users are logged in. To ensure this, stop the OMS using the command emctl stop oms -all on all OMS instances.

Note: If BI Pubilsher (BIP) had been installed and configured, then BIP should be stopped using the Admin Server before running this command.

Use this action to remove all Enterprise Manager repository schemas as follows:

  • Specify the host, port, and SID to connect to Oracle RDBMS from which all schemas are to be dropped.

  • Specify the database user and password, repository name (SYSMAN) and password for SYSMAN user, and Middleware home.

At the end, a confirmation message appears to confirm the status of this operation. If all the schemas were successfully dropped, then a message confirming the same appears. Otherwise, a message providing details on each of the schemas appears.

For example,

SYSMAN_OPSS schema is not cleaned. 
EM_X synonyms are not dropped.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action drop -mwHome /scratch/weblogic/middleware

OR

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action dropall -mwHome /scratch/weblogic/middleware -mwOraHome /scratch/weblogic/middleware

pluginpurge

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager -action pluginpurge <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -pluginPurgeList "<plugin_name>=<plugin_location>" [-mwHome <Middleware home>] -mwOraHome <Oracle Home>

Note: To purge multiple plug-ins, for the -pluginPurgeList argument, enter the plug-ins separated by a command. For example, <pluginid1>=<pluginid1 home>, <pluginid2>=<pluginid2 home>

Use this action to deinstall a plug-in from the repository as follows:

  • Specify the host, port, and SID to connect to Oracle RDBMS from which the plug-in is to be deinstalled.

  • Specify a comma-separated list of plug-ins to be purged from Enterprise Manager Repository with EM-EXT model.

$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action pluginpurge -pluginPurgeList "oracle.sysman.myyempwpax.oms.plugin_12.1.0.2.0=/scratch/weblogic/middleware/plugins/oracle.sysman.myyempwpax.oms.plugin_12.1.0.2.0" -mwHome /scratch/weblogic/middleware


Note:

RepManager 12.1 supports -action dropall and -action drop, which drop SYSMAN, SYSMAN_MDS, SYSMAN_APM, SYSMAN_OPSS , and SYSMAN_RO. RepManager 11.1 supports -action dropall, which drops only SYSMAN and SYSMAN_MDS, and -action drop, which drops only SYSMAN. RepManager 10.2.0.5 supports -action drop, which drops only SYSMAN.

Note:

If you do not specify passwords during RepManager actions, you will be prompted to do so.