Upload
others
View
4
Download
0
Embed Size (px)
Citation preview
Eric Grancher, CERN IT department
With the help/input of Andrei Dumitru, Chris Roderick, Daniel Gomez
Blanco, Dawid Wojcik, Emil Pilecki, Ignacio Coterillo Coz, Luca Canali
and Ruben Domingo Gaspar Aparicio
Agenda
3
• A few words on CERN and the computing
challenges, Oracle at CERN
• Application Continuity
• Active DataGuard, far sync, fast sync
• Oracle Multitenant Database
• A few additional interesting features
Jürgen Knobloch- cern-it Slide-4
CERN CERN
27 km circumference
Staff members: about 2500
Research community: 10,000 scientists
http://opendays2013.web.cern.ch/
Large Hadron Collider - LHC
The most complex machine on earth
• The world biggest particle accelerator
• 600 million collisions / second
5
• Fundamental physics • Why do fundamental particles weigh the
amount they do? • What is 96% of the Universe made of? • Where did the antimatter go to? • What was the universe like just after the
« Big Bang »? • Are there extra dimensions of space?
ATLAS/CMS, le 1er mars 2013
6
• “Having analysed two and a half times more data than was available for the discovery announcement in July, they find that the new particle is looking more and more like a Higgs boson, the particle linked to the mechanism that gives mass to elementary particles. It remains an open question, however, whether this is the Higgs boson of the Standard Model of particle physics, or possibly the lightest of several bosons predicted in some theories that go beyond the Standard Model. Finding the answer to this question will take time.
• Whether or not it is a Higgs boson is demonstrated by how it interacts with other particles, and its quantum properties. For example, a Higgs boson is postulated to have no spin, and in the Standard Model its parity – a measure of how its mirror image behaves – should be positive.“
• http://home.web.cern.ch/fr/about/updates/2013/03/new-results-indicate-new-particle-higgs-boson
Computing and storage needs
7
• Data volume • 25 PB per year (in files)
• > 5.2 * 1012 rows in an Oracle table (IOT, in one of the databases)
• Computing and storage capacity, world-wide distributed • > 150 sites (grid computing)
• > 260 000 CPU cores
• > 269 Po disk capacity
• > 210 Po tape capacity
• Distributed analysis with costs spread in the different sites (« LHC Computing Grid »)
0
200
400
600
800
1000
1200
MH
EP
Sp
ec06/M
on
th
LHCb
CMS
ATLAS
ALICE
0100002000030000400005000060000700008000090000
100000
Jun
-6-2
00
8
Au
g-2
9-2
00
8
Nov-2
1-2
00
8
Fe
b-1
3-2
00
9
Ma
y-8
-20
09
Jul-
31-2
009
Oct-
23
-200
9
Jan
-15-2
010
Ap
r-9-2
010
Jul-
2-2
01
0
Se
p-2
4-2
01
0
Dec-1
7-2
01
0
Ma
r-1
1-2
01
1
Jun
-3-2
01
1
Au
g-2
6-2
01
1
Nov-1
8-2
01
1
Fe
b-1
0-2
01
2
Ma
y-4
-20
12
Jul-
27-2
012
Oct-
19
-201
2
TB total written
0500000
100000015000002000000250000030000003500000400000045000005000000
Data written to tape, 01/01/2012 to 31/12/2012 (in GB)
ALICE AMSATLAS CMSCOMPASS LHCB
LS1: no stop for the computing !
Activity on 1 January 2013
Running Jobs: 246791
Transfer rate: ~14 GiB/s
CERN Tape Archive
Reaching 100 PB !
Grid CPU Workloads
(HEPSpec06/Month)
~ 250000 CPU cores in
use at any point in time!
2013-2014:
• Data to be reprocessed
• Simulation for higher Energy
• Analysis continuing
…to be repacked on new media
Credit: F. Hemmer
Oracle at CERN
9
• 1982: start
with
Oracle
at CERN
(accelerator
control)
Credit: N. Segura Chinchilla
10
Credit: M. Piorkowski
Agenda
11
• A few words on CERN and the computing
challenges, Oracle at CERN
• Application Continuity
• Active DataGuard, far sync, fast sync
• Oracle Multitenant Database
• A few additional interesting features
Application Continuity - challenge
12
• Continuity of application, difficulty to implement
restart, loss or duplication of data
• Interruptions required (patch) and issues
happen (OS or DB), errors…
• CERN: criticality of database applications for
the accelerator complex -no maintenance
windows-, for the experiments, loss of context
Application Continuity - 12c
13
• 12c Transaction Guard: the application can
know whether the transaction has indeed be
stored, possibility to take the right decision
• 12c Application Continuity: replays the
operations performed before the interruption
in case of error
Application Continuity - example
14
• Example: CERN application, accelerator
data management
• With or without Application Continuity
• Impact on performance
Application Continuity - application
15
LDB
XML
XML XML
XML
XML
JDBC
HTTP~150 GB per day~4 billion records per day
~850’000 signals
Data sent in batches* every 5’
*multiple files up-to 2MB each
Equipment – DAQ – PLC
f f f f f f f f f
f
QPS PIC
SU
Coll
CNGS
Exp
Cryo CIET
WIC
VAC
Servlets
Jetty
~300 data loading processes
Simple Massive instrumentation
On-demand workload capture
Credit: C. Roderick
16
Application Continuity - results
17
Credit: L. Canali, A. Dumitru, C. Roderick
Agenda
18
• A few words on CERN and the computing
challenges, Oracle at CERN
• Application Continuity
• Active DataGuard, far sync, fast sync
• Oracle Multitenant Database
• A few additional interesting features
DataGuard – async / sync challenge
19
• « Synchronous » is the most interesting mode • True guarantee for data consistency
• Risk of data loss with fail-over in asynchronous mode
• But… very often impossible (distance), impact on the primary database even at short distance
• CERN: direction towards synchronous, with long distance
DataGuard – CERN Wigner
20
DataGuard - {fast, far}
21
• 12c fast sync: reduced latency impact thanks to memory acknowledgement • « NOAFFIRM » no wait on the disk write on the standby
• 12c far sync: synchronous replication to a « far sync instance » (repeater) situated at distance /reasonable latency, then asynchronous replication to the final standby • Compression and distribution to multiple remote
DataGuard instances
DataGuard - experience
22
Credit: E. Pilecki
SYNC no FAR SYNC
SYNC with FAR SYNC
DataGuard - experience
23
FAST SYNC
Credit: E. Pilecki
SYNC
Agenda
24
• A few words on CERN and the computing
challenges, Oracle at CERN
• Application Continuity
• Active DataGuard, far sync, fast sync
• Oracle Multitenant Database
• A few additional interesting features
Consolidation and testing - challenge
25
• Consolidation limited by • By putting many application schemas together, one
links all for the future and any operation
• (long) environment copies
• migrations
• CERN: • Major upgrades (patch set, version), all or nothing,
unavailability period
• Database on Demand
Consolidation - Database on Demand
26
Credit: I. Coterillo Coz, R.
Gaspar Aparicio, D. Gomez
Blanco, D. Wojcik
Oracle Multitenant Database
27
Non CDB
List of users / roles
User PL/SQL software
User tables / indexes
Oracle foreground processes
Database and instance parameters
SYS PL/SQL sofware
Oracle background processes
CDB - 1 PDB
Database and instance parameters
SYS PL/SQL sofware
Oracle background processes
CDB - 2 PDBs
Database and instance parameters
SYS PL/SQL sofware
Oracle background processes
List of users / roles
User PL/SQL software
User tables / indexes
Oracle foreground processes
List of users / roles
User PL/SQL software
User tables / indexes
Oracle foreground processes
List of users / roles
User PL/SQL software
User tables / indexes
Oracle foreground processes
Oracle Multitenant Database
28
• Dictionary separation
• root: database metadata only
• PDB: user metadata and user data
Multitenant Database – Capture/Replay
29
Capture
Upgrade to
12.1 and
nonCDB to
PDB
Replay
Copy of the
database
Multitenant Database – Capture/Replay
30
Non CDB,
SQL ordered by Gets
CDB,
SQL ordered by Gets
Multitenant Database - clone
31
• Using ACFS or another supported solution,
fast cloning “snapshot copy”
Multitenant Database - usage
32
• Usage (non exhaustive list!)
• Consolidation
• Database as a Service (DBaaS)
• Regression Testing
• Multiple test environments thanks to cloning
• Easily move applications from one container to
another
Conclusion, Oracle database 12c
33
• Oracle Multitenant Database: logical / physical structure, consolidation, fast clones, move between containers and servers, etc.
• Integration with applications (Application Continuity)
• Better protection thanks to {far, fast} sync DG • And much more: ILM, adaptive execution plans, partitioning, statistics,
Global Data Services, alter database move datafile, DML on temporary tables in ADG, sequences in ADG, DG broker « redoroutes », column default to a sequence, 32kB varchar2, upgrade in parallel, etc.
35
36
37
38
create pluggable database pdb_01 from pdb_ref
snapshot copy;
sudo /sbin/acfsutil snap info /ORA/dbs03/ERICACFS
39
40
alter pluggable database pdb_01 close;
drop pluggable database pdb_01 including datafiles;