Archive

Archive for the ‘cloud control1 2c’ Category

EM12c will not delete database system targets after dropping database

May 23, 2014 Leave a comment

Had an issue where I dropped a few database and i wanted to remove these from em12c , Once I deleted the databases from EM12c , I was left with the database system targets in am unknown state

grid3

When I tried deleting these targets in EM12c it threw the following error

grid2

Found a solution to delete these target using emcli

make sure all the targets belonging to the system are removed successfully.

Setup -> Manage Cloud Control -> Health Overview -> click on ‘Deleted Targets’ link -> ‘Time Deleted Column’ should have a date.

grid1

/u01/app/oracle/middleware12.1.0.3/oms/bin/emcli login -username=SYSMAN -password=xxxxx
/u01/app/oracle/middleware12.1.0.3/oms/bin/emcli  sync 
/u01/app/oracle/middleware12.1.0.3/oms/bin/emcli  delete_target -name="APPSH3.cpp_sys" -type="oracle_dbsys"
/u01/app/oracle/middleware12.1.0.3/oms/bin/emcli  delete_target -name="DBAH3.cpp_sys" -type="oracle_dbsys"
/u01/app/oracle/middleware12.1.0.3/oms/bin/emcli delete_target -name="H3PRE.cpp_sys" -type="oracle_dbsys"
Categories: cloud control1 2c

Job step scheduler showing as down in EM12c

October 25, 2013 Leave a comment

Image


a)Ensure that OS level timezone and the Timezone value set in the Database are in Sync.

Verify it with the following commands:

$date

This gives the timestamp on the Machine with Timezone.

b)Connect to the repository Database and run the following query to check the value set in the Database.

SQL> select dbms_scheduler.stime from dual;

If there is any difference, run the following as SYS user:

SQL> exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('default_timezone','TimeZone');

For example:

SQL> exec DBMS_SCHEDULER.SET_SCHEDULER_ATTRIBUTE('default_timezone','Europe/London');

If there is no difference in the Time Zone values, proceed with the below Action plan.
 c)Connect as SYS user and Set the job_queue_processes to zero.

SQL>alter system set job_queue_processes=0 scope=BOTH;

SQL> commit;

d) Connect as SYSMAN user and execute the following:
 SQL>exec emd_maintenance.remove_em_dbms_jobs;

SQL> commit;

e) Reset the value of the following parameter to 1000 as SYS user:

SQL>alter system set job_queue_processes=1000 scope=BOTH;

f) Submit DBMS_SCHEDULER jobs. (Connect as SYSMAN user and execute the following:)

SQL>exec emd_maintenance.submit_em_dbms_jobs;

SQL>commit;

g)Verify the status of job on the console now

Categories: cloud control1 2c

Changing the heap size of the OMS in EM12c

October 18, 2013 1 comment
      version 12.1.0.3

We had an issue where oracle management server ( OMS) was restarted on a daily basis  during the hourrs of 2 – 6 am , after numerous support updates with Oracle got no further forward , All they could suggest was increase the RAM of the machine as it was set to 8GB and they wanted me to increase it to 12GB

the error message being reported in the logs was

HealthMonitor 16-Oct-2013 03:38:18 OMS Heartbeat Recorder: error: Zero rows updated for this oms
during heartbeat
Critical error err=3 detected in module OMS Heartbeat Recorder:
OMS will be restarted.
A full thread dump will be generated in the log file

/u01/app/oracle/gc_inst1/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out

to help Oracle Support analyse the problem.

Please consult My Oracle Support Note 964469.1 for additional information.

The above error message could be related to a number of things but after speaking
with our system admin he did some investigation and notice that the JVM out of the box
was set to an initial size of 256 MB and a maximum size of 1750 MB which meant it
will have been constantly resizing itself and getting fragmented

So during garbage collection it would start impacting the performance of your Enetrprise manager

backup the startEMServer.sh script, then increase the Java heap size

cd /u01/app/oracle/middleware/oms12c/gc_inst1/user_projects/domains/GCDomain/bin
cp startEMServer.sh startEMServer.sh.bak
vi startEMServer.sh

Look for the first USER_MEM_ARGS reference within the file and change from

if [ "${SERVER_NAME}" != "EMGC_ADMINSERVER" ] ; then
USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=612M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing
-XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled"
if [ "${JAVA_VENDOR}" = "Sun" ] ; then
if [ "${PRODUCTION_MODE}" = "" ] ; then
 USER_MEM_ARGS="-Xms256m -Xmx1024m -XX:MaxPermSize=612M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing
-XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -XX:CompileThreshold=8000 -XX:PermSize=128m"

to this , we are fixing the size to 2560M

if [ "${SERVER_NAME}" != "EMGC_ADMINSERVER" ] ; then
USER_MEM_ARGS="-Xms2560m -Xmx2560m -XX:MaxPermSize=612M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing
-XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled"
if [ "${JAVA_VENDOR}" = "Sun" ] ; then if [ "${PRODUCTION_MODE}" = "" ] ; then
 USER_MEM_ARGS="-Xms2560m -Xmx2560m -XX:MaxPermSize=612M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing
-XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -XX:CompileThreshold=8000 -XX:PermSize=128m"

restart your OMS to the changes to take effect:


export OMS_HOME= /u01/app/oracle/middleware12.1.0.3/oms12c/oms
$OMS_HOME/bin/emctl stop oms
$OMS_HOME/bin/emctl start oms

Check that your OMS has started up with the correct memory settings:

grep "JAVA Memory arguments" /u01/app/oracle/middleware/oms12c/gc_inst1/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out

JAVA Memory arguments: -Xms2056m -Xmx2056m -XX:MaxPermSize=1024M -XX:-DoEscapeAnalysis -XX:+UseCodeCacheFlushing -XX:ReservedCodeCacheSize=100M -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:+CMSClassUnloadingEnabled -XX:CompileThreshold=8000 -XX:PermSize=128m#

this vastly improved performance and stopped the daily restarts

Categories: cloud control1 2c

EM12c upgrade from 12.1.0.2 to 12.1.0.3

October 18, 2013 Leave a comment
Categories: cloud control1 2c

cleaning up my oracle recommendation from Oracle enterprise manager 12c

October 4, 2013 Leave a comment

recommedations

login as sysman into repository database and clean up the recommendations by running

delete from mos_pa_final_recom;
commit;

reset the checksums so we  need do a full re-computation


exec em_intsdk_patch_central.set_patch_recom_flag('N');

commit;
exec em_intsdk_patch_central.set_patch_recom_flag('Y');

commit

Run the Refresh From My Oracle Support  job from Enterprise Manager to Evaluate the recommendation

Categories: cloud control1 2c

Download and install EM CLI 12c

April 16, 2012 Leave a comment

Requirements

Before installing EM CLI, you will need the following:

Java version 1.6.0_25 or greater

Workstation running Solaris, Linux, HPUX, Tru64, AIX, or Windows with NTFS (client installation)

Installing the EM CLI Client

Download the EM CLI Kit to your workstation.

https://<oms_url&gt;:7801/em/console/emcli/download

Set your JAVA_HOME environment variable and ensure that it is part of your PATH. You must be running Java 1.6.0_25 or greater. For example

setenv JAVA_HOME /usr/local/packages/j2sdk1.6.0_25
setenv PATH $JAVA_HOME/bin:$PATH

Install the EM CLI Client. You can install the client portion of EM CLI in any directory either on the same machine as the OMS or on any machine on your network (download the emclikit.jar to that machine).

java -jar emclikit.jar client -install_dir=<emcli client dir>

Execute “emcli help setup” from the EM CLI Client for instructions on how to use the “setup” verb to configure the client for a particular OMS.

EM CLI Client can be configured to work with multiple OMS by doing multiple setups. For example

Setup EM CLI client for OMS1 at location dir1
emcli setup -dir=<dir1> -url=<Url of OMS1> -user=<EM Username for OMS1>

Eg
./emcli setup -url=http://myworkstation.example.com:em_port/em -username=em_user

Setup EM CLI client for OMS2 at location dir2

emcli setup -dir=<dir2> -url=<Url of OMS2> -user=<EM Username for OMS2>

Set the environment variable EMCLI_STATE_DIR to point to the setup dir for the OMS1

setenv EMCLI_STATE_DIR <dir1>

Above will set EM CLI Client to work with OMS1
Set the environment variable EMCLI_STATE_DIR to point to the setup dir for the OMS2
setenv EMCLI_STATE_DIR <dir2>
Above will set EM CLI Client to work with OMS2

Categories: cloud control1 2c

12c Cloud Control: How to Modify the Password for SYSMAN

March 29, 2012 Leave a comment

If the current SYSMAN password is known


1. Stop all the OMS:

cd <OMS_HOME>/bin
emctl stop oms
Execute the same command on all the OMS machines including the primary OMS machine. Do not include '-all' as the Admin Server needs to be up during this operation.

2. Modify the SYSMAN password:

cd <OMS_HOME>/bin
emctl config oms -change_repos_pwd

3. Stop the Admin server on the primary OMS machine and re-start all the OMS:
cd <OMS_HOME>/bin
emctl stop oms -all
emctl start oms

If the current SYSMAN password is unknown but the password has not been changed manually at the Database


1. Stop all the OMS:

cd <OMS_HOME>/bin
emctl stop oms
Execute the same command on the primary OMS machine as well. Do not include '-all' as the Admin Server needs to be up during this operation.

2. Modify the SYSMAN password:

cd <OMS_HOME>/bin
emctl config oms -change_repos_pwd -use_sys_pwd -sys_pwd <sys user password> -new_pwd <new sysman password>

3. Stop the Admin server on the primary OMS machine and re-start all the OMS:

cd <OMS_HOME>/bin
emctl stop oms -all
emctl start oms

Categories: cloud control1 2c