Oracle

  • All
  • General
  • Oracle
Oracle

Backup and Recovery with RMAN is easy!

About 8 years ago I wrote a blog named: It’s so Easy to use RMAN for Backups. So it’s time for a revisit and to show how easy it is to restore a database. Oracle Managed Files (OMF) Let’s start with some easy tasks: the naming and location of Oracle database files. There might be some few reasons (e.g. Oracle 12.1 with Multitenant) why you want to explicitly name the data files. But for the majority of database its more useful to handle over naming to the Oracle database.There are three parameters: db_create_file_dest: The parameter specifies the location of data […]

Backup and Recovery with RMAN is easy! Blogbeitrag lesen »

By • • 5 minutes of reading
Oracle

No RAC for Standard Edition!

If you read through the actual Oracle 19c documentation, esp. the “Database Licensing Information User Manual” you might notice that for Standard Edition Two (SE2) the feature “Oracle Real Application Clusters” (RAC) is set to “N” (No). Anyone who – like me – thought this was a documentation bug is unfortunately wrong. After talking to some Oracle representatives I was told that starting with version 19 RAC is indeed no longer available for Standard Edition 2. Existing customers using RAC need to stay with version 18 or downgrade to single instance. More critical is that Version 19c is the long

No RAC for Standard Edition! Blogbeitrag lesen »

By • • 2 minutes of reading
Oracle

Oracle 12.2 Grid Inventory without NodeList

As most of you probably already know, the installation of Grid Infrastructure has changed with Oracle 12.2. The software has to be unpacked in the GRID_HOME and installed from there. In conjunction with this change the Oracle Inventory or more precise  inventory.xml file (mostly in the directory /u01/app/oraInventory/ContentsXML) has been changed as well. Up to Version 12.1 the nodes for all installed components (e.g. GI, Database, Client, etc.) have been listed in the NODE_LIST. But since 12.2 this information is no longer available. More information can be found in MOS: 12.2: Oracle inventory does not have references for cluster nodes (Doc ID 2264757.1).

Oracle 12.2 Grid Inventory without NodeList Blogbeitrag lesen »

By • • 2 minutes of reading
Oracle

Data Guard is easy

Data Guard is easy! Every Oracle database with a certain value for the business should be protected with a standby database. How you can set up a standby environment for Standard Edition Two will be covered in a dfiferent blog. Today the goal is to create a Data Guard configuration fast, easy and repeatable.

Data Guard is easy Blogbeitrag lesen »

By • • 7 minutes of reading
General Oracle

Help, where am I? CDB or PDB … and which DB anyway?

About problems with Oracle 12c Multitenant Database Back in the days everything was easier, wasn’t it? Thus far you connect to your database and in doubt you send a query to v$instance or v$database to check you’re actually connected to the right place. But since 12c the world is no more that clear. Meanwhile we’ve got the Multitenant Option and by connecting to a Pluggable Database, maybe you won’t get the desired result. But for what reason it is such a problem?

Help, where am I? CDB or PDB … and which DB anyway? Blogbeitrag lesen »

By • • 4 minutes of reading
Oracle

Data Guard Protection Modes

pic

The availability and consistency of the Standby Database changed evermore throughout the last years and by that the loss of transactions decreased till 0 transactions. Originally only the archived Redolog files were transmitted to the Standby side and loaded there. By this the loss of transactions was in scale of one redolog file. With the 9i version Oracle then introduced the Standby Redologs, so transactions could now be transmitted right from the Online Redologs into the Standby Redologs and loaded immediately. So the loss of transactions was only a few transactions. With the 10g version then the LNS process was

Data Guard Protection Modes Blogbeitrag lesen »

By • • 3 minutes of reading
Oracle

Oracle 12c Datapatch

With Oracle 12c the SQL commands belonging to one patch are not installed by [inlinecode]catbundle.sql[/inlinecode]but by the “datapatch” tool, which is located in the OPatch directory. Other than [inlinecode]catbundle.sql[/inlinecode] datapatch checks before if the requirement for the installation are met and if it is actually necessary running those SQL commands. It is also being checked if the database is in upgrade mode. The result of the “SQL Apply” can queried in the view [inlinecode]dba_registry_sqlpatch[/inlinecode], i.e. like this: SQL> SELECT patch_id, version, status, bundle_id, bundle_series FROM dba_registry_sqlpatch;

Oracle 12c Datapatch Blogbeitrag lesen »

By • • 3 minutes of reading
Scroll to Top