25
What’s is next After Upgrade 12c Anibal Garcia Senior Oracle Database Administration ,Architect , Consultant [email protected]

What's next after Upgrade to 12c

Embed Size (px)

Citation preview

Page 1: What's next after Upgrade to 12c

What’s is next After Upgrade 12c

Anibal Garcia Senior Oracle Database Administration ,Architect , Consultant [email protected]

Page 2: What's next after Upgrade to 12c

2

What is the story behind the scenes

Page 3: What's next after Upgrade to 12c

Over 20 years of experience in Oracle , started in 1996. Vice-President Oracle User group in Guatemala since 2014. Member of LAOUC ( Latin America Oracle User Community) Since 2012 Distinguished Member of Oracle Hispanic community Latin America (http://comunidadoraclehispana.ning.com) Wrote Co-Blog Partner Fernando Garcia –Argentina Oracle Ace (https://oracleconprecision.wordpress.com/about)

…..In summary a self study

Person like you

Page 4: What's next after Upgrade to 12c

Inside the database

Parameters / Resources / Stability

Outside the database

Connectivity / Administration/ Tools

Agenda

Page 5: What's next after Upgrade to 12c

Inside the Database 12c

5

Page 6: What's next after Upgrade to 12c

Double check your initial parameters Select Name,value from V$parameter where isdeprecated=‘TRUE’

Scenario Cursor_sharing = EXACT | Force (12c)

Cursor_sharing = SIMILAR | Exact | Force (11g)

This parameter is not deprecated , but the value SIMILAR is not available in 12c . Review all the parameters you use in the spfile/ init file does not matter id is deprecated or not.

Inside Database Parameters

Page 7: What's next after Upgrade to 12c

Don’t change immediately COMPATIBLE

Review the know issues on each platform/version/vendor suggestion

Source must be Metalink not google.

A

ways verify the effect in your environment

Inside Database Parameters

AIX _use_single_log_writer=TRUE

12.1.0.2 Don’t’ use Memory_target < 1G instead use sga_target and pga_aggregate_target

People Soft _optimizer_aggr_groupby_elim= FALSE

Page 8: What's next after Upgrade to 12c

Inside Database Patches

11g SQL>@catbundle.sql psu apply SQL> !$ORACLE_HOME/OPatch/opatch lsinventory -bugs_fixed | egrep -i 'DATABASE PSU|DATABASE PATCH SET UPDATE‘

12c $ORACLE_HOME/Opatch/datapach –verbose SQL> select patch_id, patch_uid, version, status, description from dba_registry_sqlpatch where bundle_series = 'PSU';

Page 9: What's next after Upgrade to 12c

9

PAYYING ATTENTION ?

Page 10: What's next after Upgrade to 12c

The name of these bundle patches was changed to "Database Proactive Bundle Patch" in April 2016.

Each bundle patch includes the following component patches in separate subdirectories:

• Clusterware component the same as GI PSU

• ACFS component the same as GI PSU

A database bundle component that includes all DB PSU fixes along with additional fixes specifically for Engineered Systems and DB In-Memory

Inside Database Patches

Page 11: What's next after Upgrade to 12c

SQL>select patch_id, patch_uid, version, status, bundle_series, description

from dba_registry_sqlpatch;

Bundle_series column can has the values [ PSU | DBBP ]

Check all the pluggable database has all the patches.

SQL> alter pulggable database all open;

SQL> SELECT s.con_id, s.patch_id, s.patch_uid, s.description FROM cdb_registry_sqlpatch s order by 1,2;

if not all pluggable databases are sync , what can I do ?

./datapatch -verbose -pdbs MY_PLUGDB12C

Inside Database Patches

Page 12: What's next after Upgrade to 12c

12

Oracle 12.1.0.2 New feature in Alert.log

Page 13: What's next after Upgrade to 12c

Outside Database 12c

13

Page 14: What's next after Upgrade to 12c

14

Connection to new 12c SQLNET … With old version Client

ORA-28040: No matching authentication protocol SQLNET.ALLOWED_LOGON_VERSION=8 SQLNET.ALLOWED_LOGON_VERSION_SERVER=8 SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8

Page 15: What's next after Upgrade to 12c

15

SQLCL New SQLPLUS

Why you want to try ? SQLPLUS since 1985 SQL Developer 2006

Page 16: What's next after Upgrade to 12c

17

SQLCL NEW SQLPLUS

Page 17: What's next after Upgrade to 12c

18

SQLCL NEW SQLPLUS

Page 18: What's next after Upgrade to 12c

19

SQLPLUS NEW SQLPLUS

Page 19: What's next after Upgrade to 12c

20

OEM Express 12c Free

Page 20: What's next after Upgrade to 12c

21

OEM Express 12c Free

Page 21: What's next after Upgrade to 12c

22

Configure OEM Express 12c Free

Page 22: What's next after Upgrade to 12c

23

Configure OEM Express 12c Free

Page 23: What's next after Upgrade to 12c

Management Repository (GIMR) The Grid Infrastructure Management Repository is automatically installed with Oracle Grid Infrastructure 12crelease 1 (12.1.0.2). The Grid Infrastructure Management Repository enables such features as Cluster Health Monitor, Oracle Database QoS Management, and provides a historical metric repository that

simplifies viewing of past performance and diagnosis of issues.

The -MGMTDB has now become a single-tenant deployment having a CDB with one PDB

Average growth size per day per node is roughly 650-750 MB. E.g. a 4 node cluster would lead at the default retention of 3 days to an approximate size of 5.9-6.8 GB

ps -ef|grep mdb_pmon

oracle 7580 1 0 04:57 ? 00:00:00 mdb_pmon_-MGMTDB

Oracle Rac New Database …… More Disk/CPU/Memory

Page 24: What's next after Upgrade to 12c

25

Oracle Rac New Database …… More Disk/CPU/Memory

Page 25: What's next after Upgrade to 12c

Atos, the Atos logo, Atos Codex, Atos Consulting, Atos Worldgrid, Worldline, BlueKiwi, Bull, Canopy the Open Cloud Company, Unify, Yunano, Zero Email, Zero Email Certified and The Zero Email Company are registered trademarks of the Atos group. April 2016. © 2016 Atos. Confidential information owned by Atos, to be used by the recipient only. This document, or any part of it, may not be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos.

Thanks For more information please contact: (502) 59512355 [email protected]

@AgarciaDBA