Oracle Database 12c Anger Management for DBAs. Hans Forbrich Forbrich Consulting Ltd.

Transcription

1 Oracle Database 12c Anger Management for DBAs Hans Forbrich Forbrich Consulting Ltd.

2 Who am I Hans Forbrich Principal consultant, Forbrich Consulting Ltd. Programming since 1969 Oracle developer and DBA since 1984 (v4) Nortel, DLGL Ltee Oracle (Canada) employee Oracle consultant and trainer since 2003 Oracle and Oracle University partner Oracle ACE Director since 2007

3

4 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

5 Why Anger Management During DB 12c Beta w/ Dan Morgan Multi-tenant architecture difference Backward compatibility not guaranteed First version since forever Scripts and Processes not working We felt that DBAs will get a surprise and possibly even get angry about the number of scripts that will break

6 But it is an extra priced option I ll never use it Multi-Tenant is optional for now It is not [only] an option From the DB 12c Licensing manual (

7 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

8 One Instance (to Bind Them)

9 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

10 Operating System Considerations This is Instance and Schema Consolidation MORE PRE-PLANNING One Instance Take that instance down to add resources?

11 Previous Rule SGA/PGA Memory Sum ( SGA_MAX ) + Sum (PGA_AGGREGATE) <= 85% Phys Mem New Rule: One Instance / Machine Predefine before that instance is created Memory_Target <= 85% Phys Mem (All assuming > 4GB physical memory)

12 Set at DB Creation Huge Pages SHMEM./hugepages_settings.sh This script is provided by Doc ID Allocate SHMALL = 85% of Physical Eg: (RAM * 0.85 * (1024^3)) / Page_Size SHM Max Seg size should allow for PGA Eg: SHMMAX = SHMALL / 4

13 Semaphores System needs 1 semaphore per process Background, Dedicated and Shared Server Fewer background than before But may create work processes Consolidate all possible database users

14 Implications More up front planning Preconfigure for theoretical max Avoid down time

15 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

16 Login Changes SYS, SYSTEM in each PDB C## users in root, non-c## in!root OS Authentication only goes to root sqlplus / as sysdba sqlplus sys as sysdba Tools do not update TNSNAMES.ora sqlplus sys@pdb1 as sysdba

17 Which Container? When logged in Which database are you using? SHOW CON_NAME SHOW CON_ID Move between containers user in all CONNECT ALTER SESSION SET CONTAINER = PDB1

18 TCP access host:port:sid host:port//service SID!= SERVICE Many applications use SID Many JEE Connection Pools use SID Many people never heard of Service Many Applications will break

19 Implications Many scripts use OS Authetication Many scripts assume SID = Service Not many scripts use Service Service often not updated in TNSNAMES May start to use EZConnect

20 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

21 Create Instance vs Database Traditional method concentrate assume Single node DB = Single node Instance Script, DBCA, Clone Now instance includes Root & Seed CDB User DB separate

22 Root (first DB) Core SYS, SYSAUX Public UNDO Public TEMP Root Service What gets created? Your DB Local SYS, SYSAUX Optional TEMP (highly recommended) Your DB s Service

23 Create DB Methods Can use scripts, command line, or DBCA Create new PDB (from seed) Clone existing PDB within instance Create PDB from non-cdb 11gR2, 12cR1 XML-based metadata Similar in concept to Transportable Tbspc Export

24 DBCA understands PDB

25 DBCA Many different Modes

26 Implications Review scripts to create/clone DBs Many of our scripts use DBA_ views Do not understand Container May need to upgrade to see CDB_ views Brush up your XML skills

27 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

28 UserId Same user name in different DBs Different privs or Same privs Different password schedule No common names in Root C##name in Root only

29 Central UNDO One UNDO tablespace across all PDBs How big does that need to be? Use resource manager to manage?

30 One TEMP or two? By default, root owns TEMP tablespace If temp locking occurs, PDB may have own Use TEMP groups

31 Where did Tablespace come from?

32 This one: CDB_ views

33 Which is context sensitive

34 Open/Close Database or Instance? ALTER PLUGGABLE DATABASE pdb1 OPEN; ALTER DATABASE OPEN; SHUTDOWN DATABASE; ALTER PLUGGABLE DATABASE pdb1 CLOSE;

35 Implications Early every aspect of user management Creation, Drop, Passwords, Privs Open/Close/Startup/Stop New verbs, new adjectives Most objects CDB_ views

36 Agenda Why Anger Management Review of Multi-Tenant Architecture Operating System Considerations Login Changes Create Database Changes Administration Changes Conclusion

37 Conclusion Multi-tenant is the future, embrace it Multi-tenant breaks a number of traditions Multi-tenant will cause my hear to turn grey Multi-tenant is a good thing

38 Thank You Hans Forbrich Mailto: