Oracle Enterprise Manager 13c Release 3 Cloud Control installation with Oracle 18c

Checkout this post by Skant Gupta!

Oracle Enterprise Manager 13c Release 3 Cloud Control installation with Oracle 18c

Advertisements

EM13.3 is here – get your copy today

Today Oracle announced the release of Oracle Enterprise Manager Cloud Control 13c Release 3 (13.3.0.0).

Oracle Enterprise Manager 13.3 introduces many new features for database, cloud and middleware management, such as:

  • Support for monitoring and management of Oracle Database 18c
  • Onboarding non-cloud DB/PDB to DBaaS Cloud
  • Relocation of service instances across cloud pools
  • PDB upgrade using Fleet Maintenance
  • Modernization of UI stack for key database performance diagnostics capabilities like ASH Analytics and Real-time SQL Monitoring
  • Support for Oracle Identity Management 12.2.x Management
  • Support for Cloning of SOA or OSB-based Domains Versioned 12.2.1.3 and later
  • JVMD enhancements to support large scale deployments & ALL request monitoring
  • Uptake of JDK 7u171 and WLS April 2018 CPU for enhanced security

You can get your copy here OTN.

For new feature please check New Features In Oracle Enterprise Manager Cloud Control 13c.

 

 

Organizing Jobs in EM13c, centralize or leave it to the team…

Using the EM Job System, especially for ‘house keeping’ jobs makes sense to many of the EM using organizations.

Requirements

  • Team members should be able to schedule jobs
  • Team members should be able to create library jobs
  • Team members should be able to see, stop, resume jobs that were scheduled by other members in the team

We will discuss two possible approaches:

  • Centralized
  • Leave it to the team

Centralized

I have seen organizations that prefer to work with a central EM account to locate Jobs (as well as for deployment procedures and reports). For this a ‘Non personal account’ is created, that is used to created, maintain and schedule library jobs.

A clear disadvantage of this approach would be that it is unknown which user actually modified or scheduled a specific job.  Something, your security officer will have a strong opinion about…

A clear advantage of this approach would be that all job definitions are to be found in one and the same account, which makes maintenance of library jobs easy. Job logs will be found at the same location and anyone having access to the central account can start, stop and resume jobs running in the account.

In order to get more team involvement, you could decide on creating a central account per team. So the Sales team would have a different account as the Human Resource team.

Leave it to the team

As working in Agile/Scrum teams is a standard way of working for many organizations, another approach could be: allow individual team members to create, maintain and schedule library jobs using their personal EM account.

This approach will make your security officer much happier as now it is clear who did exactly what.

Some disadvantages of this approach include:

  • The necessity of working with private roles
  • Jobs are scattered over multiple owners (team members)
  • You need to think of who is going to be the next logical owner whenever a team member leaves the team or even the organization. When removing this member as an EM user, EM will for another EM user to become the owner of the EM objects that are owned by the EM user you are trying to delete.

Advantages of using this approach include:

  • The team is responsible for creation, maintenance and scheduling itself and because of this fully self serviced
  • It is clear who did what and when

Using private roles

In order to allow other team members to view the logs and schedule and maintain the jobs, job privileges need to be granted. As the granting must be per administrator this could be a tedious job. For this using private roles could be a solution.

The private role should be created by a Super administrator or an administrator with the ‘Create role’ privilege.

This private role then should be granted to all team members once (and whenever a new member joins the team). Granting job privileges is than limited to the private role, in order to implement requirements as described above.