Infrastructure at your Service
What a nice and an interesting new experience… My first ZOUG Event… Interesting opportunities to meet some great persons and hear to some great sessions. I had the chance to participate to Markus Michalewicz sessions. Markus is Senior Director, Database HA and Scalability Product Management by Oracle, and was the special guest to this event.
One of our customer has been initially creating a RMAN catalog on an Oracle database release 12.1.0.2.0 and was now intending to register new Oracle 12.2.0.1.0 databases. Registering the databases will be failing with errors : PL/SQL package RCAT.DBMS_RCVCAT version 12.01.00.02 in RCVCAT database is too old RMAN-06429: RCVCAT database is not compatible with this version of RMAN
Facing an internal inconsistency in the ODA derby database is very painful (see https://blog.dbi-services.com/oda-lite-what-is-this-odacli-repository/ for more info about the derby database). I have recently faced a case where the database deletion was failing and the database remained then in “Deleting” status. Connecting directly to the internal derby database and doing some self cleaning is very risky and should be performed at your own and known risk. So, in most of the case, a database inconsistency issue…
Deploying new ODA X7-2S or 2M, I have been curious how configure-firstnet would interact with the fiber and copper ethernet network interfaces. Reading documentation on the web, I could not clearly understand if it is mandatory to have the ODA connected to the LAN when performing an ODA reimage and/or running the configure-firstnet in additionnal of having ILOM connection. After digging deeper and few tests, I wanted to share my experience in this blog.
Configuring fiber interfaces during an ODA installation can sometime been challenging. The configuration can depend on the kind of gigabit interface converter (GBIC) and switch been used. In this blog, I would like to show a real case faced during one of our customer deployment, and come with a solution.
Dbvisit Standby version 8 comes with a nice feature, a daemon, which gives the benefit to send and apply the archive log automatically in the background. Bypassing the system scheduling, the daemon will facilitate customer RPO (Recovery Point Objective) and RTO (Recovery Time Objective) fine tuning. Monitoring to apply logs to the Standby only when needed, will also optimize use of resources. Originally available for the Linux based environments, the feature has been made available…
To perform some tests in order to determine the accurate number of cores to be used by the database application, I had to increase and decrease the number of CPU cores on an ODA using the DCS stack. When increasing would never be a problem, decreasing number of CPU cores would fail into a DCS-10045 error.
In this post I would like to share how I have been able to troubleshoot and solve a catalog import issue using RMAN debug function. As we can see, the error message provided by RMAN is not very helpful. oracle@vmtestoradg1:/home/oracle/ [RCAT12C] rman catalog rcat/manager Recovery Manager: Release 12.2.0.1.0 connected to recovery catalog database RMAN> import catalog rcat/manager@RCAT11G; Starting import catalog at 05-JAN-2018 14:11:45 connected to source recovery catalog database RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE…
This is a small migration demo of a 11g catalog (RCAT11G) to a new 12c catalog (RCAT12c). Demo databases environments have been easily managed thanks to DBI DMK tool. oracle@vmreforadg01:/home/oracle/ [RCAT11G] sqh SQL*Plus: Release 11.2.0.4.0 oracle@vmtestoradg1:/home/oracle/ [RCAT12C] sqh SQL*Plus: Release 12.2.0.1.0 Current configuration Displaying the list of databases registered in the RCAT11g catalog. SQL> select instance_name from v$instance; INSTANCE_NAME —————- RCAT11G SQL> select * from rcat.rc_database; DB_KEY DBINC_KEY DBID NAME RESETLOGS_CHANGE# RESETLOGS ———-…
In this post, I would like to share how to implement automatic Start and Stop for CONTROL-M/Server, CONTROL-M/Agent and CONTROL-M/EM running on Oracle linux 7 individual servers, by implementing some updates in the existing BMC procedure and script. The CONTROL-M should be running version 9 and we are using the internal PostgreSQL database. The user created for CONTROL-M/Server and CONTROL-M/Agent environment is ctmuser, the user created for CONTROL-M/EM environment is emuser. BMC CONTROL-M Workload Automation…
