|
preupgrade
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -action preupgrade [-mwHome <middleware home>]-pluginDepList "<pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>" -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 the comma-separated list of plugin-information according to dependency to be deployed. You can pass a file with this option, the contents being the comma-separated list of plugin-information according to dependency to be deployed. If the pluginDepList is missing or has a value of empty list i.e. "{}", $<OMS_HOME>/sysman/admin/emdrep/plugininfo/pluginDepList is read, by default, to get plugin dependency list.
-
Specify the comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being the comma-separated locations for DLF files from platform/plugins. If the dlfSources option is missing or has a value of empty list i.e., "{}", $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources is read, by default, to get dlf resource locations. 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 example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action preupgrade -mwHome /scratch/weblogic/middleware -pluginDepList <pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>
|
|
upgrade
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -action upgrade [-mwHome <middleware home>]-pluginDepList "<pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>" -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 the comma-separated list of plugin-information according to dependency to be deployed. You can pass a file with this option, the contents being the comma-separated list of plugin-information according to dependency to be deployed. If the pluginDepList is missing or has a value of empty list i.e. "{}", $<OMS_HOME>/sysman/admin/emdrep/plugininfo/pluginDepList is read, by default, to get plugin dependency list.
-
Specify the comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being the comma-separated locations for DLF files from platform/plugins. If the dlfSources option is missing or has a value of empty list i.e. "{}", $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources is read, by default, to get dlf resource locations. If this option is missing and default dlfSources file is not present, only dlf files for Platform would be picked. If this is present, only the DLFs under these sources will be picked up.
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action upgrade -mwHome /scratch/weblogic/middleware -pluginDepList <pluginid1>=<pluginid1 home>,<pluginid2>=<pluginid2 home>
|
|
transX
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -reposName sysman -reposPassword <password of sysman user> -action transx [-mwHome <middleware home>] -dlfSources "<oms home>,<plugin1 home>,<plugin2home>"
Note: You can also run -do transX. 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 the comma-separated locations for DLF files from platform/plugins. You can pass a file with this option, the contents being the comma-separated locations for DLF files from platform/plugins. If the dlfSources option is missing or has a value of empty list i.e. "{}", $<OMS_HOME>/sysman/admin/emdrep/plugininfo/dlfSources is read, by default, to get dlf resource locations. If this option is missing and default dlfSources file is not present, only dlf files for Platform would be picked. If this is present, only the DLFs under these sources will be picked up.
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -reposName sysman -action transx -mwHome /scratch/WLS/middleware
|
|
resume
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -resume retry -checkpointLocation <directory where schemamanager stores checkpoints> [-mwHome <middleware home>]
|
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
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -action drop [-mwHome /scratch/weblogic/middleware]
Note: Ensure that there are no active SYSMAN sessions, scheduler jobs, and dbms_jobs running, and no SYSMAN users logged in. To ensure this, stop the OMS using the command emctl stop oms -all on all OMSes.
|
Use this action to drop the SYSMAN schema as follows:
-
Specify the host, port, and SID to connect to Oracle RDBMS from which the SYSMAN schema is to be dropped.
-
Specify the database user and password, repository name (SYSMAN) and password for the SYSMAN user, and middleware home.
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager example.com 1521 db3 -dbUser sys -dbRole sysdba -reposName sysman -action drop -mwHome /scratch/weblogic/middleware
|
|
dropall
|
$<OMS_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -action dropall [-mwHome <middleware home>] [-mwOraHome <Oracle Home>]
Note: Ensure that there are no active sessions for SYSMAN, SYSMAN_MDS SYSMAN_OPSS, and SYSMAN_APM. To ensure this, stop the OMS using the command emctl stop oms -all on all OMSes.
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.
|
$<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 <repository_database_host> <repository_database_port> <repository_database_sid> -dbUser sys -dbPassword <sys password> -dbRole sysdba -reposName sysman -reposPassword <password of sysman user> -action pluginpurge -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.
-
To specify the comma-separated list of plugin-information 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.1.0=/scratch/weblogic/middleware/plugins/oracle.sysman.myyempwpax.oms.plugin_12.1.0.1.0" -mwHome /scratch/weblogic/middleware
|
