Monday Jun 27, 2016

Full Transportable Export/Import - Migrating an 11.2.0.4 database to Oracle Database 12c- into the Oracle Cloud

Full Transportable Export/Import - one of the coolest features in Oracle Database 12c 

We blogged about Full Transportable Export/Import a while back. It is - no doubt - one of the coolest features in Oracle Database 12c. And it is part of our Hands-On Lab exercise (Hands On Lab - Upgrade, Migrate, Consolidate to Oracle Database 12c) as well.

It utilizes the technique of Transportable Tablesspaces - cross-platform, cross- Endianness, cross-version - but lets Oracle Data Pump do all the "dirty" work of rebuilding everything kept in your SYSTEM and SYSAUX tablespace including views, synonyms, public objects, grants, sequences etc etc etc.

You can even combine it with RMAN Incremental Backups - of course cross-platform and cross-Endianness as well - in order to decrease the downtime for large databases.
Please find our presentation about the combination of these feature here in the Slides Download Center to the right:

In addition: You can use this Oracle Database 12c feature with your source database Oracle 11.2.0.3 or 11.2.0.4. Just the destination database you are upgrading or migrating to must be at least an Oracle 12.1.0.1 database (or newer of course). 

See the feature in action

Roy recorded a 20 minute video demonstrating how to:

  • Migrate an Oracle Database 11.2.0.4 database into an Multitenant's pluggable database using
  • Full Transportable Export/Import
  • into the Oracle DBaaS Cloud
    .

And of course the feature works also without migrating into a Container database environment - and without migrating to the Oracle DBaaS Cloud. 

If you need to migrate a database from Oracle 11.2.0.3 or newer to Oracle Database 12c Full Transportable Export/Import can become your best friend.

--Mike

Friday Apr 29, 2016

Upgrade to Oracle Database 12c: We don't insist :-)

It's so funny - for years I discuss with customers minimal downtime upgrade strategies back and forth, up and down. I saw DBAs really hunting to save a few seconds potential downtime - and I always take this serious as there is usually a real reason behind that. Just to learn a few days later by repeating experience that my work Windows7 laptop goes down to apply upgrades ... and this takes looooooooong .... sometimes it takes a lengthy +30 minutes of quiet time. Whereas my OL6 VBox image applies upgrades in the background and needs a simple restart to be back in less than a minute or so.
Different strategies of course. 

For those who think I'm writing nonsense about the upgrade of my Win7 on my Lenovo x230 with 16GB of RAM, an i5-320M cpu and a 5400rpm WD spinning disk here's a screenshot taken from one of those upgrades where I sat already 15 minutes waiting ... waiting ... waiting ...

As Win7 had to configure the upgrades afterwards, once it was done with restarting I had to wait another 10 minutes for completion. And no, my laptop is not broken (not that I know) - it's 3 years old and heavily used of course. But all running fine usually ... :-) 

Anyhow ... 

Of course I discussed with a ton of people why you should upgrade now to Oracle Database 12.1.0.2 now! - and stay away from that "we go live on the 2nd release only" thinking as there's no such thing as THE 2nd release anymore.

But whatever my position on upgrades is, I can ensure that we don't discuss methods like this internally to force you to upgrade ...

MS Win10 Forced Upgrade Message

... not yet *haha* !!!
.

--Mike

PS: The picture is not a fake - you can watch the 41 seconds youtube video here :-) 
.

Tuesday Mar 08, 2016

Parameter Recommendations for Oracle Database 12c - Part II


Best Practice Hint

Time for a new round on Parameter Recommendations for Oracle Database 12.1.0.2. The focus of this blog post settles on very well known parameters with interesting behavior. This can be a behavior change or simply something we'd like to point out. And even if you still work on Oracle Database 11g some of the below recommendations may apply to your environment as well.

Preface

Again, please be advised - the following parameter list is mostly based on personal experience only. Some of them are officially recommended by Oracle Support. Always use proper testing mechanisms.

We strongly recommend Real Application Testing, especially the SQL Performance Analyzer but also Database Replay to verify the effect of any of those parameters. 
.

Known Parameters - Interesting Behavior

  • parallel_min_servers
    • What it does?
    • Default:
      • CPU_COUNT * PARALLEL_THREADS_PER_CPU * 2
    • Behavior Change:
      • Setting it to a value below the default will let the database ignore it.
      • In Oracle Database 11g the default was 0
      • Compare 11.2.0.4 vs 12.1.0.2 on the same box:
        • 11g:
          SQL> show parameter parallel_min_servers
          NAME                  TYPE     VALUE
          --------------------- -------- ------
          parallel_min_servers  integer  0

        • 12c:
          SQL> show parameter parallel_min_servers
          NAME                  TYPE     VALUE
          --------------------- -------- ------
          parallel_min_servers  integer  8
    • Explanation:

  • job_queue_processes
    • What it does?
      • See the Oracle Documentation - value specifies the maximum number of job slaves to be created to execute jobs started by either DBMS_JOBS or DBMS_SCHEDULER
    • Default:
      • 1000
    • Recommendation:
      • Set it to a rough equivalent of 2 * CPU cores
    • Explantion:
      • In Oracle Database 12c we introduced the automatic stats gathering during CTAS and IAS (into an empty table only) operations. This can potentially lead to too many jobs doing the stats gathering. Furthermore issues can happen due to the default of concurrent stats gathering.
        Therefore a limitation of this parameter seems to be a good idea. 
      • Be aware when switching it to 0 - this will block all recompilation attempts. Furthermore generally no jobs can be executed anymore with  DBMS_JOBS or DBMS_SCHEDULER.
      • Multitenant behavior change:
        In 12.1.0.1, job_queue_process was a Container Database (CDB) modifiable parameter (ie. at a global level). However, in 12.1.0.2, the job_queue_process parameter is not CDB modifiable; instead it's PDB modifiable which means each PDB can have its own job_queue_process value.  
    • More Information:
    • Annotation:
      I've had an email exchange with Stefan Köhler about the stats behavior for CTAS. As I couldn't myself reproduce the behavior we say at two customer with job_queue_processes=1000 and an heavy CTAS activity (which could be remedied by setting JQP to a lower value) I would put a question mark behind my above statement.

      .
      .
  • recyclebin
    • What it does?
      • See the Oracle Documentation - controls whether the Flashback Drop capability is turned on or off. If the parameter is set to OFF, then dropped tables do not go into the recycle bin. If this parameter is set to ON, then dropped tables go into the recycle bin and can be recovered.
    • Default:
      • ON
    • Recommendation:
      • If the recyclebin is ON (the default) in your environment then empty it at least once per week. Create a default job in all your environments emptying the recycle bin every Sunday morning at 3am for instance:
        SQL> purge DBA_RECYCLEBIN;
    • Explantion:
      • The recycle bin is on in every database by default since Oracle 10g. The danger is that it may not be emptied but especially on developer databases many objects may be created and dropped again. As a result the dropped objects and its dependents still stay in the database until the space needs to be reclaimed. That means, they exist in the data dictionary as well, for instance in TAB$. Their name is different now starting with "BIN$..." instead of "EMP" - but they will blow up your dictionary. And emptying it not often enough may introduce a performance dip to your system as the cleanup of many objects can be quite resource intense
      • Check your current recycle bins:
        SQL > SHOW RECYCLEBIN;
        ORIGINAL NAME RECYCLEBIN NAME              OBJECT TYPE DROP TIME
        ------------- ---------------------------- ----------- -------------------
        TEST_RBIN     BIN$2e51YTaSK8TL/mPy+FuA==$0 TABLE       2010-05-27:15:23:45
        TEST_RBIN     BIN$5dF60S3GSEOSSYREaqCg==$0 TABLE       2010-05-27:15:23:43
        TEST_RBIN     BIN$JHCDN9YwQRXjXGOJcCIg==$0 TABLE       2010-05-27:15:23:42
    • More Information:
.
.

  • deferred_segment_creation
    • What it does?
      • See the Oracle Documentation - set to the default (TRUE), then segments for tables and their dependent objects (LOBs, indexes) will not be created until the first row is inserted into the table
    • Default:
      • TRUE
    • Recommendation:
      • Set it to FALSE unless you plan to create a larger number of tables/indexes knowing that you won't populate many of them.
    • Explantion/Risk:
      • If my understanding is correct this parameter got introduced with Oracle Database 11.2 in order to save space when applications such as EBS, Siebel or SAP create tons of tables and indexes which never may get used as you don't work with the matching module of the software
      • The risk can be that certain query check DBA_SEGMENTS and/or DBA_EXTENTS - and if there's no segment allocated you won't find an indication about the existence of the object in there - but it actually exists. Furthermore we have seen issues with Data Pump workers getting contention, and some other things. 
    • More Information:
      • The documentation has become now pretty conservative as well since Oracle 11.2.0.4 and I'll second that:
        Before creating a set of tables, if it is known that a significant number of them will not be populated, then consider setting this parameter to true. This saves disk space and minimizes install time.
        ..
 --Mike

Friday Mar 04, 2016

Parameter Recommendations for Oracle Database 12c - Part I

Best Practice Hint

 A few weeks ago we've published some parameter recommendations including several underscores but based on an internal discussion (still ongoing) we decided to remove this entry and split up the tasks. The optimizer team will take over parts of it and I'll post an update as soon as something is published.

.

Preface

Please be advised - the following parameter list is mostly based on personal experience only. Some of them are officially recommended by Oracle Support. Always use proper testing mechanisms.

We strongly recommend SQL Performance Analyzer to verify the effect of any of those parameters. 
.

How to read this blog post?

Never ever blindly set any underscore or hidden parameters because "somebody said" or "somebody wrote on a blog" (including this blog!) or "because our country has the best tuning experts worldwide" ... Only trust Oracle Support if it's written into a MOS Note or an official Oracle White Paper or if you work with a particular support or consulting engineer for quite a long time who understands your environment.
.

Important Parameter Settings

    • _kks_obsolete_dump_threshold
      • What it does?
        • Introduced in Oracle 12.1.0.2 as an enhancement  to improve cursor sharing diagnostics by dumping information about an obsolete parent cursor and its child cursors after the parent cursor has been obsoleted N times. 
      • Problem:
        • Trace files can grow like giant mushrooms due to cursor invalidations
      • Solution:
      • Patches:
        • Fix included in DBBP 12.1.0.2.160216
        • Fix on-top of 12.1.0.2.13DBEngSysandDBIM
        • Since Feb 13, 2016 there's a one-off available but on Linux only - and only on top of a fresh 12.1.0.2 
      • Remarks:
        • The underlying cursor sharing problem needs to be investigated - always
          If you have cursor sharing issues you may set this parameter higher therefore not every invalidation causes a dump, then investigate and solve the issue, and finally switch the parameter to 0 once the issue is taken care of. 
          Please be aware that switching the parameter to 0 will lead to a lack of diagnostics information in case of cursor invalidations.


    • _use_single_log_writer
    • memory_target
      • What it does?
      • Problem:
        • Unexpected failing database upgrades with settings of  memory_target < 1GB where equal settings ofsga_target and pga_aggregate_target didn't cause issues 
        • It prevents the important use of HugePages
      • Solution:
        • Avoid memory_target by any chance
        • Better use sga_target and pga_aggregate_target instead


    • pga_aggregate_limit

    Essential MOS Notes for Oracle Database 12.1.0.2

    --Mike
    .

    Thursday Feb 25, 2016

    What happened to the blog post about "12c parameters"?

    Best Practice Hint

    Two weeks ago I published a blog post about Parameter Recommendations for Oracle Database 12.1.0.2. And I took it down a day later. Why that?

    I've got a lot of input from external sources for the "Parameter" blog post. And I'd like to thank everybody who contributed to it, especially Oracle ACE Ludovico Caldara.

    Generally there was a bit of a misunderstanding internally about whether we should "advertise" underscore parameters to cure some misbehavior of the database. In 99% of all cases I'd agree that underscores are not a good solution - especially when it comes to database upgrades as our slide deck still contains a real world example about what happens when you keep old underscore parameters in your spfile. It can not only slow down the entire upgrade but also makes it very hard for Oracle Support to reproduce issues in case of something going the wrong direction. 

    But in some situations an underscore seems to be the only remedy in cases where a patch is not available for a particular release - the release you are using at the moment. And even if a patch is available or if the fix is available in a future PSU or BP that does not mean necessarily that one can apply it for several reasons.

    We still have a lot of very productive discussions going on internally between many groups. That is very good as it means that we have plenty of smart people around, especially in Oracle's Database Development :-)

    Furthermore we agreed that the Optimizer PM team will take over the part of my (taken down) blog post targeting wrong query results and other optimizer topics. We are in constant exchange and I'll link it as soon as something gets published.

    --Mike

    Tuesday Sep 08, 2015

    MOS Download for Oracle Database 12.1.0.2 including SE2

    Please find all our articles about Oracle Database Standard Edition 12.1.0.2 SE2:

     

    You have 3 options to download Oracle Database Enterprise Edition 12.1.0.2 and Oracle Database Standard Edition 12.1.0.2. SE2.

    Regarding OTN and eDelivery nothing has been changed since Sep 1, 2015 when Oracle Database Standard Edition 12.1.0.2 SE2 got published. But the download from MOS now has changed.

    When you search in the under Patches and Updates tab ...

    Patches And Updates - MOS

    ... and display the Latest Patch Sets ...

    Latest Patch Sets - MOS

    ... check for instance for platform Linux x86-64bit ...

    MOS - 12.1.0.2 Linux

    ... then you'll wonder about the two patch numbers ...

    Patch Numbers Oracle SE2 12.1.0.2

    The only difference of 2.5 GB in size results from two more zip files included in the new patch number 2141921 ...

    ... you'll have to check the README button to find out what's hidden behind each file ...

    Files 3 and 4 contain Oracle Database Standard Edition 12.1.0.2 SE2.

    So please don't get puzzled by the different patch numbers - the only real difference is the inclusion of SE2 into the download package but the included patches etc are exactly the same as in the previous patch number. 

    --Mike

    .

    Tuesday Sep 01, 2015

    Oracle Database 12.1.0.2 Standard Edition (SE2) available for download

    Oracle SE2Finally ...

    Oracle Database 12.1.0.2 Standard Edition (SE2) is available for download.

    Some information is already available in the Oracle Database Licensing Information. And you'll find more here: https://www.oracle.com/database/standard-edition-two/index.html

    Quoting from the pricing document:
    http://www.oracle.com/us/corporate/pricing/databaselicensing-070584.pdf

    "Oracle Database Standard Edition 2 may only be licensed on servers that have a maximum capacity of 2 sockets. When used with Oracle Real Application Clusters, Oracle Database Standard Edition 2 may only be licensed on a maximum of 2 one-socket servers. In addition, notwithstanding any provision in Your Oracle license agreement to the contrary, each Oracle Database Standard Edition 2 database may use a maximum of 16 CPU threads at any time. When used with Oracle Real Application Clusters, each Oracle Database Standard Edition 2 database may use a maximum of 8 CPU threads per instance at any time. The minimums when licensing by Named User Plus (NUP) metric are 10 NUP licenses per server."

    .

    Download Oracle Database 12.1.0.2 Standard Edition (SE2) on OTN

    (12.1.0.2.0) - Standard Edition (SE2)

    Download Microsoft Windows x64 (64-bit) File 1, File 2  (2.6 GB)
    Download Linux x86-64 File 1, File 2  (2.5 GB)
    Download Oracle Solaris (SPARC systems, 64-bit) File 1, File 2  (2.7 GB)
    Download Oracle Solaris (x86 systems, 64-bit) File 1, File 2  (2.5 GB)
    Download HP-UX Itanium File 1, File 2  (3.3 GB)
    Download AIX (PPC64) File 1, File 2  (2.9 GB)
    Download zLinux64 File 1, File 2  (2.5 GB)

    And on the Oracle Software Cloud (edelivery.oracle.com) which is the recommended download location:

    Edelivery.oracle.com SE2


    This location has been a corrected download link pointing to OTN as well:

    https://www.oracle.com/database/standard-edition-two/index.html


    .

    For a good overview about first experiences with Oracle Database Standard Edition 12.1.0.2 (SE2) please see Franck Pachot's excellent blog post here:

    Please find all our articles about Oracle Database Standard Edition 12.1.0.2 SE2:

     

    --Mike 

    Friday Jul 03, 2015

    News on Oracle Database STANDARD EDITION 12.1.0.2

    Standard EditionJust fyi in case you had bookmarked this blog post or found a link to it:

    Oracle Database 12.1.0.2 Standard Edition (SE2) is now available for download.

    Please find the updated information here:
    https://blogs.oracle.com/UPGRADE/entry/oracle_12_1_0_22

    --Mike


    Thursday Jul 02, 2015

    SAP on Oracle Database 12c now with Oracle In-Memory

    Oracle SAPOn March 31, 2015 SAP has been certified to run on Oracle Database 12.1.0.2:
    https://blogs.oracle.com/UPGRADE/entry/sap_is_now_certified_on

    As of June 30, 2015, Oracle Database In-Memory is supported and certified for SAP environments for all SAP products based on SAP NetWeaver 7.x. on Unix/Linux, Windows and Oracle Engineered Systems platforms running Oracle Database 12c - in single instance and Oracle Oracle Real Application Clusters deployments.

    Oracle Database 12c is the database of choice for SAP customers based on In-Memory Technology which is fully supported for SAP BW and SAP OLTP applications.

    For requirements, restrictions, and implementation details see the documents below.

    --Mike

    PS: Fidel, thanks for the correct links - highly appreciated!!! 

    Monday Jun 29, 2015

    Premier Support for Oracle 11.2 has ended months ago

    PLEASE FIND AN UPDATED BLOG POST HERE:

    https://blogs.oracle.com/UPGRADE/entry/no_extra_fee_for_extended


    I have blogged many times about the End of Premier Support for Oracle Database 11.2 and the different stages and regulations for Extended Support for this release. But still I'm getting inquiries almost every day, internally and externally.

    Let me first point out that I'm not a rep of Oracle Support. I'm just a Product Manager with some Oracle Support background. So you'll always have to consult our officially available documents and sources as regulations may change after I published this blog post. I'm just trying to summarize what I know at the moment to help you avoid some of the usual misunderstandings.

    Premier Support for Oracle 11.2 has already ended

    Fact. Premier Support for Oracle 11.2 has ended on Jan 31, 2015. Period. Regardless of the patch level you may be on. No further discussion here please. Just for your notes: this has happened a while ago in case you've missed the date:

    PLEASE FIND AN UPDATED BLOG POST HERE:

    https://blogs.oracle.com/UPGRADE/entry/no_extra_fee_for_extended


    --Mike 

    Tuesday Jun 16, 2015

    New Cloud Control 12.1.0.5 is available

    The new version of Oracle's Cloud Control 12c Release 5 is available for download as of today. Some of the new features include Hybrid Cloud Computing but also the support for RMAN incremental rolling forward backups (cross platform, cross Endianness) to decrease downtime for Transportable Tablespaces and Full Transportable Export/Import migrations.

    Find it here on OTN:

    http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

    Oracle Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) New!


    Enterprise Manager Base Platform
    (Full Installers for OMS, Agent, Repository, Management Plug-ins)


    Download for Linux x86 (32-bit)
    Download for Linux x86-64 (64-bit)
    Download for Windows x86-64 (64-bit)
    Download for Solaris Operating System (SPARC)
    Download for Solaris Operating System (x86-64)
    Download for IBM AIX on POWER Systems (64-bit)
    Download for HP-UX Itanium (64-bit)

    --Mike

    Wednesday Apr 01, 2015

    SAP is now certified on Oracle Database 12.1.0.2

    ORACLE and SAPSAP certified Oracle Database 12.1.0.2 as of March 31, 2015!

    Yes, it's true. Our colleagues in the Oracle/SAP/CompetenceCenter in Walldorf worked really hard to complete the certification for SAP with Oracle Database 12.1.0.2 But finally it happened. Actually it was announced long time before as planned. And it happened right in time.

    Please find the official documents here:

    SAP Service Marketplace ==> Products ==> Installation & Upgrade Guides ==> Database Upgrades (login required) ==> Oracle 

    And here's the link to the official announcement:

     

    Great job by a excellent Oracle team in Walldorf - and please no excuses anymore from anybody saying that you can't certify your application on Oracle Database 12.1.0.2. If SAP can do it, everybody can do it :-)

    If you are looking for more information and useful documents please see this discussion here - scroll down a bit (thanks to Upgrade Expert Andreas Becker from the Oracle-SAP-CC in Walldorf):

    See also the ROADMAP for Oracle/SAP regarding future developments, feature support, In-Memory etc:

    --Mike

    .

    PS:
    I'm expressing my sincere condolences as one of the 5 founders of SAP, Klaus Tschira, died on March 31, 2015 way too early at the age of 74 years. May he rest in piece!

    Tuesday Feb 24, 2015

    Oracle In-Memory Advisor now available

    Oracle In-Memory is such a great feature - but often the challenge you'll face is the tricky question:
    Which of your tables and/or partitions should you mark for In-Memory column store availability? 

    And the answer is now easier to find as the new In-.Memory Advisor is available via download from MyOracle Support:

    The Advisor produces a report identifying the objects that should be placed In-Memory for maximum benefit, along with a SQL*PLUS script which implements those recommendations. It can be run on Oracle Database 11.2.0.3 and above. And of course the recommendations can be implemented on Oracle Database 12.1.0.2. (and newer).

    Important to know: The In-Memory Advisor is licensed as part of the Database Tuning Pack.

    Further information can be found at: OTN

    In case you have obtained a pre-release version of the Advisor, please discard it and replace it with the production version 

    --Mike 

    Thursday Jan 22, 2015

    Non-CDB architecture of Oracle databases is DEPRECATED since Oracle Database 12.1.0.2

    Beginning with Oracle Database 12.1.0.2 a non-CDB architecture is deprecated.

    non-CDB deprecated in Oracle 12.1.0.2

    --

    What does this mean?

    Deprecation first of all does not mean "desupported". It means in this case that you of course can have still stand-alone Oracle databases as you know the architecture from previous releases. But you can also have a single-tenant deployment (a CDB with one PDB - no Multitenant license required) or multitenant databases (a CDB with up to 252 PDBs - Multitenant Option license required).

    But in a future Oracle release single-tenant and multitenant databases only may be allowed. Right now there's no information available when this might happen. --

    Which features are not supported at the moment?

    • Database Change Notification
    • Continuous Query Notification (CQN)
    • Client Side Cache
    • Heat Map
    • Automatic Data Optimization
    • Oracle Streams
    • Oracle Fail Safe
    • Flashback Pluggable Database (Flashback Database works but will flashback CDB$ROOT including all PDBs)
    • DBVERIFY
    • Data Recovery Advisor (DRA)
    • Flashback Transaction Backout 

    -Mike 

    ---

    From the Upgrade Guide:
    By deprecate, we mean that the feature is no longer being enhanced but is still supported for the full life of the 12.1 release. By desupported, we mean that Oracle will no longer fix bugs related to that feature and may remove the code altogether. Where indicated, a deprecated feature may be desupported in a future major release

    Friday Aug 01, 2014

    New (some undocumented) Parameters in Oracle 12.1.0.2

    Every release offers some surprises - even to myself ;-)

    Right now Roy and I are in the final steps to refresh our big slide deck to the new layout, but more important, to have Oracle 12.1.0.2 information included as well (were necessary). So I did my usual "compare parameters" query between releases - getting unusual surprises this time.

    This is the list of new parameters introduced with the patch set Oracle Database 12.1.0.2. Where applicable I have added the link to the doc.

    But as you may recognize not all of them are explained in the doc ;-)

    • DBFIPS_140
      • Default: FALSE
      • DBFIPS_140 enables Transparent Data Encryption (TDE) and DBMS_CRYPTO PL/SQL package program units to run in a mode compliant to the Federal Information Processing Standard (subsequently known as "FIPS mode";)
    • COMMON_USER_PREFIX
      • Default: c##
      • Specifies a prefix that the names of common users, roles, and profiles in a multitenant container database (CDB) must start with. If COMMON_USER_PREFIX is set to an empty string, Oracle will not enforce any restrictions on the names of common or local users, roles, and profiles.
    • DB_PERFORMANCE_PROFILE <<updated Dec 16>>
      • Undocumented
      • See bug17861171, bug18406144 and bug19817284 - IORM feature on Exadata only
    • ENABLE_GOLDENGATE_REPLICATION
      • Default: FALSE
      • Controls services provided by the RDBMS for Oracle GoldenGate (both capture and apply services). Set this to true to enable RDBMS services used by Oracle GoldenGate
      • Introduced with Oracle 11.2.0.4 and Oracle 12.1.0.2
    • EXCLUDE_SEED_CDB_VIEW
      • Undocumented
      • Per feedback by the Multitenant team:
        • Default: TRUE
        • Setting this parameter to FALSE would return results for the seed database when querying against the CDB views
    • INMEMORY_CLAUSE_DEFAULT
      • Default: an empty string
      • Enables you to specify a default In-Memory Column Store (IM column store) clause for new tables and materialized views. If the INMEMORY_CLAUSE_DEFAULT parameter is unset or set to an empty string (the default), only tables and materialized views explicitly specified asINMEMORY will be populated into the IM column store. Setting the value of the INMEMORY_CLAUSE_DEFAULT parameter to NO INMEMORY has the same effect as setting it to the default value.
    • INMEMORY_FORCE
      • Default: DEFAULT
      • Allows you to specify whether tables and materialized view that are specified as INMEMORY are populated into the In-Memory Column Store (IM column store) or not. The default value is DEFAULT. When this value is in effect, the IM column store is populated only with tables and materialized views specified as INMEMORY. If OFF is specified, then even if the IM column store is configured on this instance, no tables or materialized are populated in memory.
    • INMEMORY_MAX_POPULATE_SERVERS
      • DefaultHalf the effective CPU thread count or the PGA_AGGREGATE_TARGET value divided by 512M, whichever is less.
      • Specifies the maximum number of background populate servers to use for In-Memory Column Store (IM column store) population, so that these servers do not overload the rest of the system
    • INMEMORY_QUERY
      • Default: ENABLE
      • Used to enable or disable in-memory queries for the entire database at the session or system level. This parameter is helpful when you want to test workloads with and without the use of the In-Memory Column Store (IM column store)
    • INMEMORY_SIZE
      • Default: 0
      • Sets the size of the In-Memory Column Store (IM column store) on a database instance. If a database does not have automatic memory management enabled, this parameter must be set to a nonzero value that reserves the amount of memory to use for the database's IM column store. The default value is 0, which means that the IM column store is not used. The database must be restarted after setting this parameter to enable the IM column store. The minimum size to which this parameter can be set is 100 MB.
    • INMEMORY_TRICKLE_REPOPULATE_SERVERS_PERCENT
      • Default: 1
      • Limits the maximum number of background populate servers used for In-Memory Column Store (IM column store) repopulation, as trickle repopulation is designed to use only a small percentage of the populate servers. The value for this parameter is a percentage of the INMEMORY_MAX_POPULATE_SERVERS initialization parameter value
    • OPTIMIZER_INMEMORY_AWARE
      • Default: TRUE
      • Enables or disables all of the optimizer cost model enhancements for in-memory. Setting the parameter to false causes the optimizer to ignore the in-memory property of tables during the optimization of SQL statements. This behavior can also be achieved by setting theOPTIMIZER_FEATURES_ENABLE initialization parameter to values lower than 12.1.0.2
    • PDB_LOCKDOWN
      • Undocumented
      • Per feedback by the Multitenant team:
        • Not functional in Oracle 12.1.0.2
    • PDB_OS_CREDENTIAL
      • Undocumented
      • Per feedback by the Multitenant team:
        • Not functional in Oracle 12.1.0.2
        • May be functional with a future PSU allwoing then OS user verfication/validation for PDBs

    -Mike

    PS: Forgot to mention this one as a parameter which had been disappeared in Oracle 12.1.0.2:

    • PARALLEL_FAULT_TOLERANCE_ENABLED
      • Undocumented in Oracle 12.1.0.2
      • Disappeared in Oracle 12.1.0.2 but did exist in Oracle 12.1.0.1 

    Thursday Jul 24, 2014

    Why "We'll wait for the 2nd release!" is a misconception ...

    Oh, how often have I heard this phrase:

    "We'll wait for the second release!"

    And sometimes it makes me really anxious and angry at the same time when I hear that.

    Anxious because it means that somebody has no strategy for the database upgrades/migrations and is just postponing necessary tasks to sometime in the future. Easy deal but not very clever

    Angry because this is a way of thinking from the 90s/00s when Oracle had this "10.1", then later "10.2" strategy in database releases. But we are in 2014 now. And things have changed. Changed a lot in fact.

    I'm probably not the only person who would love to see if we'd remove this "first" and "second" release tags. This has become obsolete with Oracle 11.1. We were telling customers officially that this is the brand new fantastic Oracle Database 11g release. But in fact it was - from the coding perspective - more or less a very stable 10g. In my workshops I did call it Oracle 10.3 with a marketing sticker on it. And as far as I can see the customer's I've had helped with going live on Oracle Database 11.1.0.7 were quite happy. Some really large shops still work with this release today with hundreds of databases in production.

    But honestly most of the changes got introduced with Oracle Database 11.2. And not for a small number of customers this meant waiting for the first patch set (which since then has become a full release). Plenty of people went live with Oracle Database 11.2.0.2. But a lot of the remarkable changes got introduced not in Oracle 11.1 but in Oracle 11.2. Just remember things such as the move from Clusterware to Grid Infrastructure. But also minor things such as DEFERRED_SEGMENT_CREATION and plenty of optimizer news.

    Now with Oracle Database 12c and the first patch set (full release) 12.1.0.2 I have heard this again - and I see it on the mailing list as well once a week:

    "When will Oracle 12.2 be available?"

    Well, that's the misconception. It's true, Oracle Database 12.1.0.2 has new features and extensions. But it has also many fixes over the already very stable Oracle 12.1.0.1. Why should anybody wait for Oracle 12.2 now? Because it's supposed to be THE SECOND release? Forget this - this is thinking from the old days.
    We are in year 2014 now.

    And then spend a minute to look closer to the Support Policy.

    • Oracle Database 11.2 will go out of Premier Support in 6 months. Yes!!! 6 months
    • And correct, we'll give everybody on Oracle 11.2.0.4 more than one full year of Extended Support for free
    • For Oracle 11.2.0.3 Extended Support will end 27-AUG-2015

    That means if you plan to stay on Oracle 11.2.0.3/4 for a longer period you'll either have to calculate 20% extra of your support fee for the 2nd year of Extended Support. Or you prefer to "hope".

    I can't tell you when Oracle 12.2 will be available - and I don't care. Usually people wait for the first patch set anyways which gets releases based on experience from the past 3 databases releases roughly a year and a bit after the initial release. Just do the math and you'll see where you end up with this strategy.

    My recommendations are:

    • Stop thinking about THE SECOND release
    • Evaluate Oracle Database 12.1.0.2 now - not tomorrow
    • Look at the Support Policy - you need to start your upgrades as soon as possible

    PLEASE READ ON:

    https://blogs.oracle.com/UPGRADE/entry/no_extra_fee_for_extended

    -Mike 

    Tuesday Jul 22, 2014

    Oracle Database 12.1.0.2 is available!!!

    Oracle Database 12.1.0.2 is available for download now. It is the most comprehensive patch set we've ever built. Look up the list of inclusions - and it includes the new marquee feature OracleDatabase In-Memory.

    Three things important to mention:

    • It is a full release - no need to get Oracle Database 12.1.0.1
    • Even though it is a patch set it will be available on OTN and eDelivery - and Oracle Database 12.1.0.1 will be removed instantly
    • For now it is an Enterprise Edition install only - SE and SE One may follow later.
      Please see MOS Note:1905806.1 for further details.

    And it contains a bunch of new things and improvements:

    • Oracle Database In-Memory
    • Oracle Big Data SQL
    • Oracle JSON Document Store
    • Oracle REST Data Services
    • Improvements to Oracle Multitenant
    • Advanced Index Compression
    • Zone Maps
    • Approximate Count Distinct
    • Attribute Clustering
    • Full Database Caching
    • Rapid Home Provisioning
    Availability is for the following platforms right now:

    Time to upgrade!!! 

    -Mike

    PS: Kudos to Morohashi-san for alerting me about the link to the internal MOS - exchanged the link address!
    PPS: Updated entry on Sept 30 with links for MS Windows

    Thursday Jan 09, 2014

    Oracle Database 12c for AIX, HP-UX IA and zLinux now available

    It took a while ... but finally Oracle Database 12c is available for:

    Oracle Database 12c Release 1
    Standard Edition, Standard Edition One, and Enterprise Edition

    -Mike

    Monday Jul 29, 2013

    Very cool videos about Upgrade to Oracle 12c

    Sometimes it is by far easier to watch a few short videos instead of reading an entire book :-)

    So enjoy watching Roy talking about Upgrades and Migrations to Oracle Database 12c in short videos covering also the new Upgrade and Migration features in Oracle Database 12c.

    .

    Chapter 1 - Upgrading is Universal

    Chapter 2 - Minimizing Risk and Downtime

    Chapter 3 - Leveraging Consolidation to ease Migration

    Chapter 4 -Why Upgrade?

    Chapter 5 - Automating the Upgrade Process

    -Mike


    Wednesday Jul 10, 2013

    Oracle Database 12c is available on Windows!

    Good things come to those who wait ... and yes, Oracle Database 12c (Oracle 12.1.0.1) is available for download from  OTN/eDelivery for MS Windows as well since last night :-)

    Windows versions being supported: 2008, 2008 R2, 7, 8

    Tuesday Jun 25, 2013

    Oracle Database 12c is available for download now!

    Good things come to those who wait ... finally ... Oracle Database 12c (Oracle 12.1.0.1) is available for download from the Oracle Software Cloud (formerly know as eDelivery) and OTN (Oracle Tech Network) for Linux 64bit (Solaris will follow within the next few hours):

    And yes, it will be supported on Oracle Exadata and SuperCluster as well :-)

    .

    .

    And with the release of Oracle Database 12c we are offering you also our

    NEW
    Upgrade, Migrate and Consolidate to Oracle Database 12c
    slide deck

    with (sorry, we've did it again!) over 500 slides covering:

    • The brand new Parallel Upgrade including new Pre/Post-Upgrade-Fix-Ups
    • The new Full Transportable Export/Import Feature
    • Obviously Oracle Multitenant, which got talked about a lot as Pluggable Databases or Container Databases before
    • Plenty of new parameters, cool and very helpful features and much more ...
    • Download the slides Upgrade, Migrate and Consolidate to Oracle Database 12c

    And of course, the slide deck will see some updates in the near future :-)

    -Mike

    .

    .

    About

    Mike Dietrich - Oracle Mike Dietrich
    Master Product Manager - Database Upgrade & Migrations - Oracle

    Based in Germany. Interlink between customers/partners and the Upgrade Development. Running workshops between Arctic and Antartica. Assisting customers in their reference projects onsite and remotely. Connect via:

    - -

    Search

    Archives
    « June 2016
    SunMonTueWedThuFriSat
       
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    17
    18
    19
    21
    22
    23
    24
    25
    26
    28
    29
    30
      
           
    Today
    Slides Download Center
    Visitors since 17-OCT-2011
    White Paper and Docs
    Workshops
    Viewlets and Videos
    Workshop Map
    x Oracle related Tech Blogs
    This week on my Rega & Pono
    Upgrade Reference Papers