Thursday Jan 16, 2014

Database Failover Questions

In the post about installing Ops Center, one of the steps is setting up the database that Ops Center will use. You can use a co-located database on the EC system, or you can set up your own database and configure Ops Center to use it.

On that second option, I saw a couple of questions:

Can Ops Center be installed using a Data Guard customer managed database?

Data Guard is an Oracle tool for providing high availability and disaster recovery for an Oracle database. It can be used with Ops Center. The only thing to keep in mind is that, if your database fails over to a system with different connection parameters, you need to direct Ops Center to use the new system using the Changing the Customer-Managed Database Location procedure.

Can the RemoteDBProps.txt contain entries for both the active and standby databases?

No. The RemoteDBProps.txt file is used for the initial configuration. If you have a standby database in a separate location, you have to switch using the procedure described above.

Thursday Oct 10, 2013

Using a RAC Database

I got a question about the Ops Center database:

"What versions of Oracle Database (with or without Real Application Clusters) are supported in Ops Center 12.1.4?"

The answer is 11gR1 (without RAC) or 11gR2 (with or without RAC). There's more information in the Certified Systems Matrix.

Tuesday Aug 13, 2013

Database locations

I got a question about customer-managed database locations:

"We are preparing to install Ops Center with ECHA. The install docs say that ECHA uses a customer-managed database on a separate system. What if I partitioned a system, and had the EC node and DB node on separate partitions? Could that work?"

Theoretically yes, although I don't think we've tested that kind of setup.

The reason we say that the database should be on a separate system is because an Enterprise Controller failover doesn't include failover for the database. We assume that, with a customer-managed database, you'll have your own methods for protecting the DB from system failures. ECHA, then, just focuses on the Enterprise Controller, and assumes that the database will still be accessible when the new EC node comes up.

Wednesday Aug 29, 2012

Database commands

Ops Center has two database options - you can have Ops Center automatically install a database on the Enterprise Controller system, or you can use your own database on any system you choose. If you use your own database, it's obviously important to make sure that this database is running smoothly. You have a few tools that can help you do this.

The first is the ecadm command. This command has a variety of subcommands that let you view and control the status of the Enterprise Controller. Two subcommands in particular are relevant to the database:

ecadm verify-db: This subcommand verifies that the database is reachable and that the schemas are configured with the proper permissions. Use the -v option if you want more details; the command is normally terse if the DB is configured correctly.

ecadm sqlplus -r: This subcommand opens an sqlplus console connection to the database. The -r option makes this console read-only, which isn't necessary, but is generally a good idea.

You can also view the database contents using Oracle SQL Developer or other tools. The Accessing Core Product Data how-to describes this process.

About

This blog discusses issues encountered in Ops Center and highlights the ways in which the documentation can help you

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
5
6
7
8
9
11
12
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today