Category: TrivadisContent

Enterprise Manager 13c – Disable the BI Publisher

The BI Publisher will be started automatically during the startup process of the Enterprise Manager 13c. You don’t like the BI Publisher or you don’t use it? Save the resources, speed up your startup process, disable it. The password of the database repository owner SYSMAN is required. Verify the Status – the BI Publisher is up and running [oracle@solothurn ~]$ export OMS_HOME=/u00/app/oracle/product/oms13cr1 [oracle@solothurn ~]$ $OMS_HOME/bin/emctl status oms Oracle Enterprise Manager Cloud Control 13c Release 1 Copyright (c) 1996, 2015 Oracle…

Read More

Enterprise Manager 13c – Change Memory Settings with emctl

In Enterprise Manager Grid Control 11g, changes in the Oracle Management Server JVM memory settings could be done in a file called startEMServer.sh located in a domain subdirectory like /u00/app/oracle/product/gc_inst/user_projects/domains/GCDomain/bin/.  And after an OMS restart, the JVM has used this new settings for the OMS.  Since 12c, it can be done by an emctl command. emctl – Get your actual Settings OMS_HEAP_MAX oracle@solothurn:~/ [oms13cr1] emctl get property -name OMS_HEAP_MAX Oracle Enterprise Manager Cloud Control 13c Release 1 Copyright (c) 1996, 2015 Oracle…

Read More

Hostname in Oracle Enterprise Linux 7 anpassen – hostnamectl

In Oracle Enterprise Linux 6 konnte man den Hostname beispielsweise mit Tools wie system-config-network oder durch editieren vom /etc/sysconfig/network File anpassen. In der Version 7 kann der Hostname mit dem Tool hostnamectl geändert werden. Ein Editieren vom Network-File funktioniert nicht mehr, der Hostname wird aus dem File /etc/hostname abgeleitet. Auszug aus den Oracle Enterprise Linux 7 Release Notes – https://docs.oracle.com/cd/E52668_01/E53499/html/section-bbw-bzj-4n.html: Nebst hostnamectl gibt es mit Tools für den NetworkManager wie nmtui und nmcli weitere Möglichkeiten, den Hostname anzupassen. Anzeigen vom Hostname mit…

Read More

Oracle Enterprise Manager 13c – KILL SESSION for Application Administrators – Part 1

Basically to execute a ALTER SYSTEM KILL SESSION command you have to be a) a DBA or b) you need the ALTER SYSTEM privilege. Granting the ALTER SYSTEM privilege to a Non-DBA has big risks. This user is now able to change a lot of parameters like memory parameters, NLS settings etc. In one of my projects, a small team of well known application administrators is having a read-only account in Enterprise Manager 12c to verify the performance, see the user sessions…

Read More