Oracle

Filter posts by category

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 »

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 »

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 »

Oracle

Oracle 12c DBUA and Datapatch

upgrade12c 1

Meanwhile all customers applying Oracle databases should work on switching their database to Oracle 12c. While for Standard Edition Users there still is the restriction that only version 12.1.0.1 is available, Enterprise Edition Users can apply version 12.1.0.2. It is matter of course that besides the Basic release the current PSU (Patch Set Unit) is loaded. Performing an installation last week as part of a project, I noticed a small but important commit: If you perform the Upgrade from 11g to 12c with the dbua (Database Upgrade Assistant), the command datapatch is not performed automatically (even though the documentation says

Oracle 12c DBUA and Datapatch Blogbeitrag lesen »

Oracle

Move Partitions between Tables

You might wonder why you should move a partition from one table to another but actually there are several reasons. The following one came up in a session I had with a customer who wants to archive “old” data. The actual data is partitioned (INTERVAL) and initially his idea was to move the rows to the archive table with INSERT AS SELECT. The archive table has to stay for a minimum of 10 years but is very seldom used. As there are global indexes on the current table with about 300 million rows we couldn’t simply keep the old data

Move Partitions between Tables Blogbeitrag lesen »

Oracle

Caution, 12c Oracle Home User cannot be changed!

01 Oracle LRM-00109

Be careful when installing Oracle 12c on Windows. The first stumbling block, the Oracle Home User could produce a lot of trouble for you later. If you are used to running your Instance and Listener with an extra Account for Exports to Windows Shares, NAS devices or RMAN Backups to external storages for example with Avamar, a toughtless click at software installation could destroy all your work and efforts. It only remains to set up everything from scratch because the once selected user is not changeable.

Caution, 12c Oracle Home User cannot be changed! Blogbeitrag lesen »

Oracle

Oracle 12c Unified Auditing – Part 2

Bild1

Unified Auditing was introduced with Oracle 12c 12.1.0.1 and one idea is to combine standard auditing (AUD$) with fine grained auditing (FGA_LOG$). AUD$ and FGA_LOG$ still exists and if you like you can use your existing and well accepted auditing procedures. Some documents stated that the same auditing which was introduced with Oracle 11g is still running but that’s not one hundred percent true. If you don’t change the standard database setup the “old” AUD$ table exist but will stay empty in contrast to 11g. A new partitioned table with a somewhat cryptic name (CLI_SWP$2dc5e8db$1$1) is populated in the schema

Oracle 12c Unified Auditing – Part 2 Blogbeitrag lesen »

Oracle

Oracle 12c Unified Auditing – Part 1

With Oracle 12c it is all getting better! And that includes the new auditing possibilities as well, which can be grouped as “Unified Auditing”. First of all unified auditing basically does not mean anything more but the previous functions, standard auditing and fine-grained auditing, being combined. This means that we are dealing with three (!) different methods now, because the “former” ones still exist, even if they are disabled by default – despite what is said in several documents. I can also just partly agree on the claim, that the same commands as in Oracle 11g are being recorded. Only

Oracle 12c Unified Auditing – Part 1 Blogbeitrag lesen »

Oracle

Manage Audit Data

SYSTEM Tablespace Size

Over the last couple of years I was asked repeatedly because the SYSTEM Tablespace is constantly growing. The reason is pretty simple: Since Oracle 11.2 DDL commands not executed with SYSDBA privilege and all logins (failed or successful) are logged in the AUD$ table. And against some documentation this table is located in the SYSTEM tablespace and not in SYSAUX.

Manage Audit Data Blogbeitrag lesen »

Oracle

Extended Data Types with VARCHAR2(32767)

JA-Blog-042514-1

In the Oracle 12 New Features Guide you will find this sentence: “The maximum size of the VARCHAR2, NVARCHAR2, and RAW data types has been increased from 4,000 to 32,767 bytes“ Increasing the allotted size for these data types allows users to store more information in character data types before switching to large objects (LOBs). This is especially useful for brief textual data types and the capabilities to build indexes on these types of columns.” ( Oracle® Database New Features Guide 12c Release 1 (12.1) E17906-16 Page 1-13 What great news! Especially if you want to upgrade your database to

Extended Data Types with VARCHAR2(32767) Blogbeitrag lesen »

Scroll to Top