And these are the basis for Exascale, the documentation<\/a> has a lot of information about the new services and other details.<\/p>\n To resume, Vault is where your data is stored, and where the Exascale manages it. The Exascale software spreads the database files in all Exadata storage servers and isolates\/secures access between different users\/clusters. The access is done by users using traditional wallets.<\/p>\n The reference and association are similar to an ASM diskgroup. The access is done using the \u201c@\u201d, instead of the \u201c+\u201d of ASM. And it is that. For the database point of view the datafile now will be like this: @hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1\/1958BAD8B27B2F85E0636039010AB112\/DATAFILE\/SYSTEM.OMF.54C2961A<\/em><\/p>\n Inside the Vault exists Datasets, which is the path where the file is stored. For databases, it follows: @Vault-name:GI-cluster-ID:CDB-ID:PDB-ID<\/em>. For other types of data, the path changes. Vault is based on Exadata celldisks exposed as Storage Pools, and they can be created for each media type (EC, HP, Flash). The Vault can mix several Storage Pools, and templates can be created to redirect files to the desired storage pool inside the Vault.<\/p>\n Users can access and administrate in several ways. Traditional users can access to read\/write, and administrators can limit resources like IOPS.<\/p>\n Let\u2019s pick up the datafiles, inside the Vault the Exascale software sees each one of the datafile extents, hash them, and saves information about the disks where they are in one mapping table of storage buckets.<\/p>\n The mapping table is a simple structure inside the Exascale software that tells what is the location for each extent. A hash function determines the bucket and the Exascale software (using the mapping table) defines the locate\/disk where the bucket will be written. By the mirror redundancy, each bucket is stored in several storage cells.<\/p>\n When a database is cloned, the Exascale software identifies the extends for the source database, and the buckets where they are, and shares access to them to the target database. The new blocks created\/modified by the source (and the target database created by the clone) are written in the new places while the original (not modified ones) remain the same and continue to be shared between both databases.<\/p>\n Image extracted from the presentation “Exadata Exascale: Next Generation Architecture and Technology Preview [LRN2724]” of OCW2023<\/p><\/div>\n So, in the end, it is not needed to copy datafiles during database clones. The process is done completely at the storage level it is just extents, buckets, and mapping table share\/access. And since it is the same Vault that stores the data the source database can be in open state, receiving reads\/writes. And it is not needed to create sparse diskgroups to do that.<\/p>\n Image extracted from the presentation “Exadata Exascale: Next Generation Architecture and Technology Preview [LRN2724]” of OCW2023<\/p><\/div>\n In real life this new Exascale snapshot mode works like this<\/strong>:<\/p>\n Explaining what\u2019s happened above:<\/p>\n So, this is the game-changer<\/strong>. Imagine refreshing entire databases in 10 seconds. 100GB cloned, available to open in read and write in 10 seconds. Imagine all the pipelines and CI\/CD that can be done faster. Imagine all DevOps that can create all DEV environments in 10 seconds. Exascale can be renamed to ExaOps machine and still be accurate.<\/p>\n Something important to reinforce is that, now, it is not necessary to use fancy commands or Storage shares\/NFSs to do the snapshot. They can be done directly from the sqlplus with one simple command. And looking at the example above, it is possible to notice that even the traditional clone, was executed online and with one command. Some Exascale optimizations (at the storage level) will help even if the conventional clone is used.<\/p>\n Continuing from above, the pdb FSI1PDB622G has 622GB, and when trying to clone it (as before), Exascale magic does the trick:<\/p>\n The gains are pretty clear. The 622GB clone in the traditional way took 16 minutes and 38 seconds. Using the Exascale SNAPSHOT COPY the same clone took 10 seconds.<\/p>\n Can be argued that works just inside the same CBD, but this works between different CDBs? YES!<\/strong> Look:<\/p>\n So, fast cloning works if PDBs are in the same container and even if they are in different CDB\u2019s. Above, the clone worked in a similar time as doing inside the same container because, when the SNAPSHOT COPY command is triggered, the Exascale software interpretates and clones directly at the storage level. The pointer to the mapping table of extents (the buckets) is added. When the source PDB modifies a datafile block, the new version is created and the cloned PDB(s) continues to see only the old image of block\/extend. This is just a condensed description of what happens internally in Exascale software.<\/p>\n Until this moment, the snapshot clone works (whatever the database) if the CDBs are in the same Exascale Vault. The clone works for the entire full CDB as well, but in this case, more steps are needed (like new nid). The source of the clone can be the Data Gaurd Standby database as well.<\/p>\n As discussed before, with Exascale there is no more ASM, so, no more sqlplus connection with SYSASM and ASMCD. For now, there are two new important tools:<\/p>\n Below are some examples of xsh that can be useful in daily tasks.<\/p>\n List details of Vault (similar to asmcd lsdg command):<\/strong><\/p>\n Checking details of one file:<\/strong><\/p>\n List files for one DataSet (wildcards can be used):<\/strong><\/p>\n Removing files (wildcards can be used to delete several files at the same time):<\/strong><\/p>\n As discussed before, no more ASM, but the CRS still exists. So, the information from VOTEDISK and OCR can be retrieved as before:<\/strong><\/p>\n It is clear, the Exascale is a game-changer. Being possible to clone PDBs and entire CDBs in a fast and secure way will facilitate a lot. Imagine all the actual work to do lift and shift, pipelines, and CI\/CD to release one environment. Even using traditional storage (non-Exadata), a lot of commands are needed to avoid the datafile fuzziness, like the rman \u201csnapshot time<\/em><\/a>\u201d for recovering the database, and other controls to check when the storage snapshot was made.<\/p>\n Now, with Exascale, there is a proper way to do snapshots for Engineered Systems. And this is just one small part of Exascale, a lot of new features are there. Block devices can be created and exported to Linux using iSCSI. Fine-tuned IORM can be deployed to control if one database can use or not flash by example. And environments can be scaled from a few to hundreds of TB\u2019s. The limitation from growing from quarter, half, full, and elastic Exadata does not exist anymore.<\/p>\n Exascale is that, a lot of new features build up over and solid Exadata. With the launch of Exadata Exascale blogs and notes will start to appear, for now, check the:<\/p>\n <\/p>\n Disclaimer<\/strong>: \u201cThe postings on this site are my own and don\u2019t necessarily represent my actual employer positions, strategies, or opinions. The information here was edited to be useful for general purposes, and specific data and identifications were removed to allow reach the generic audience and to be useful for the community. Post protected by copyright.<\/em>\u201d<\/p>\n Disclaimer #2<\/strong>: “This post was possible due to the availability of Exadata Exascale and the participation in the Beta Program. Thank you for the opportunity Oracle Team. This post is not marketing or requested by Oracle. It is a personal opinion”.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Yes, it is a game-changer. It is for DBAs. It is for DevOps. It is for Enterprises too. And it is not because of new internal services, new ways to access data, or the scalability. But because it changes and improves a lot the way that databases can be refreshed, the way that databases are […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[179,29,77,6,186,5],"tags":[180,69,187,65],"class_list":["post-1038","post","type-post","status-publish","format-standard","hentry","category-23ai","category-database","category-engineeredsystems","category-exadata","category-exascale","category-oracle","tag-23ai","tag-exadata","tag-exascale","tag-oracle"],"yoast_head":"\nVault<\/h1>\n
But WHY<\/strong> game-changer?<\/h1>\n
![\"\"](\"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2024\/07\/Exascale-Mapping-Table-01-1024x572.jpg\")
<\/a>![\"\"](\"https:\/\/www.fernandosimon.com\/blog\/wp-content\/uploads\/2024\/07\/Exascale-Mapping-Table-02-1024x575.jpg\")
<\/a>Snapshot Copy<\/h2>\n
SQL> set timing on \r\nSQL>\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 FSI1PDB READ WRITE NO\r\n 5 FSI1PDB114G READ WRITE NO\r\n 8 FSI1PDB622G READ WRITE NO\r\nSQL>\r\nSQL> select con_id, sum(bytes)\/1024\/1024\/1024 as size_gb from v$datafile group by con_id;\r\n\r\n CON_ID SIZE_GB\r\n---------- ----------\r\n 1 5.23925781\r\n 2 .673828125\r\n 3 1.49450684\r\n 5 113.907593\r\n 8 622.129272\r\n\r\nElapsed: 00:00:00.01\r\nSQL> \r\nSQL> create pluggable database FSI1PDB114G_FULL from FSI1PDB114G;\r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:02:32.96\r\nSQL> alter pluggable database FSI1PDB114G_FULL open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:16.18\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 FSI1PDB READ WRITE NO\r\n 4 FSI1PDB114G_FULL READ WRITE NO\r\n 5 FSI1PDB114G READ WRITE NO\r\n 8 FSI1PDB622G READ WRITE NO\r\nSQL>\r\nSQL> create pluggable database FSI1PDB114G_SNAP from FSI1PDB114G snapshot copy;\r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:00:09.97\r\nSQL> alter pluggable database FSI1PDB114G_SNAP open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:10.73\r\nSQL>\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 FSI1PDB READ WRITE NO\r\n 4 FSI1PDB114G_FULL READ WRITE NO\r\n 5 FSI1PDB114G READ WRITE NO\r\n 6 FSI1PDB114G_SNAP READ WRITE NO\r\n 8 FSI1PDB622G READ WRITE NO\r\nSQL>\r\nSQL> select con_id, sum(bytes)\/1024\/1024\/1024 as size_gb from v$datafile where con_id in(4, 5, 6) group by con_id;\r\n\r\n CON_ID SIZE_GB\r\n---------- ----------\r\n 4 113.907593\r\n 5 113.907593\r\n 6 113.907593\r\n\r\nElapsed: 00:00:00.06\r\nSQL><\/pre>\n
\n
SQL> create pluggable database FSI1PDB622G_FULL from FSI1PDB622G;\r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:16:38.27\r\nSQL>\r\nSQL> alter pluggable database FSI1PDB622G_FULL open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:16.86\r\nSQL> \r\nSQL> create pluggable database FSI1PDB622G_SNAP from FSI1PDB622G snapshot copy;\r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:00:10.01\r\nSQL> \r\nSQL> alter pluggable database FSI1PDB622G_SNAP open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:12.45\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 FSI1PDB1 READ WRITE NO\r\n 4 FSI1PDB114G_FULL READ WRITE NO\r\n 5 FSI1PDB114G READ WRITE NO\r\n 6 FSI1PDB114G_SNAP READ WRITE NO\r\n 7 FSI1PDB622G_FULL READ WRITE NO\r\n 8 FSI1PDB622G READ WRITE NO\r\n 9 FSI1PDB622G_SNAP READ WRITE NO \r\nSQL><\/pre>\n
[oracle@lin11 ~]$ export ORACLE_SID=CDB11\r\n[oracle@lin11 ~]$ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 23.0.0.0.0 - Production on Sun Mar 24 00:36:26 2024\r\nVersion 23.3.0.23.09\r\n\r\nCopyright (c) 1982, 2023, Oracle. All rights reserved.\r\n\r\n\r\nConnected to:\r\nOracle Database 23c Enterprise Edition Release 23.0.0.0.0 - Production\r\nVersion 23.3.0.23.09\r\n\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 CDB1PDB1 READ WRITE NO\r\nSQL> \r\nSQL> CREATE DATABASE LINK clone_link CONNECT TO c##remote_clone_user IDENTIFIED BY \"W3lc0m3#W3lc0m3#\" USING 'FSI1';\r\n\r\nDatabase link created.\r\n\r\nSQL> \r\nSQL> set timing on\r\nSQL> create pluggable database CDB1PDB114G_FULL from FSI1PDB114G@clone_link; \r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:02:14.01\r\nSQL> alter pluggable database CDB1PDB114G_FULL open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:16.76\r\nSQL> \r\nSQL> create pluggable database CDB1PDB114G_SNAP from FSI1PDB114G@clone_link SNAPSHOT COPY;\r\n\r\nPluggable database created.\r\n\r\nElapsed: 00:00:12.08\r\nSQL> alter pluggable database CDB1PDB114G_SNAP open;\r\n\r\nPluggable database altered.\r\n\r\nElapsed: 00:00:14.37\r\nSQL>\r\nSQL> show pdbs\r\n\r\n CON_ID CON_NAME OPEN MODE RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n 2 PDB$SEED READ ONLY NO\r\n 3 CDB1PDB1 READ WRITE NO\r\n 4 CDB1PDB114G_FULL READ WRITE NO\r\n 5 CDB1PDB114G_SNAP READ WRITE NO \r\nSQL> \r\nSQL> select con_id, sum(bytes)\/1024\/1024\/1024 as size_gb from v$datafile where con_id in(4, 5) group by con_id;\r\n\r\n CON_ID SIZE_GB\r\n---------- ----------\r\n 4 113.907593\r\n 5 113.907593\r\n\r\nElapsed: 00:00:00.06\r\nSQL><\/pre>\n
Exascale, Management<\/h1>\n
\n
[oracle@lin11 ~]$ xsh ls @hVvMQYTk --detail\r\nname createTime createdBy flashCacheProv flashLogProv iopsProvEF iopsProvHC spaceProvEF spaceProvHC spaceUsedEF spaceUsedHC xrmemCacheProvEF xrmemCacheProvHC acl \r\n@hVvMQYTk Feb 19 22:25:08 2024 escssvcops unlimited true 0 72320 0 6597069766656 0 5613863531100 0 unlimited escssvcops:M;FBDVISTFBQJPGJAN6W2ESPQ:R;WTPND9HCBO5P8QGASKJHJGDPW:R \r\n[oracle@lin11 ~]$<\/pre>\n
[oracle@lin11 ~]$ xsh ls @hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/FSI1\/195C48B6278590A6E0636039010ACC99\/DATAFILE\/TBSLOAD.OMF.53B95414 --detail\r\nname createTime usedBy size blockSize fileType redundancy contentType media \r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/FSI1\/195C48B6278590A6E0636039010ACC99\/DATAFILE\/TBSLOAD.OMF.53B95414 May 26 17:05:16 2024 9fb1bf8ffc57cf4dbfca211a3c47b3d1:SIM1 625991491584 8192 DATAFILE high DATA HC \r\n[oracle@lin11 ~]$<\/pre>\n
[oracle@lin11 ~]$ xsh ls @hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/%CDB1STB% \r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1STB\/0454765FDBD85262E0631C284664D815\/DATAFILE\/SYSAUX.OMF.44140F45 \r\n...\r\n...\r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1STB\/ONLINELOG\/group_8.OMF.57D66C8D \r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1STB\/PARAMETERFILE\/spfile.OMF.1BBE70F8 \r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1STB\/PASSWORD\/pwdCDB1STB.0AF4D3A8 \r\n@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/CDB1STB\/TEMPFILE\/TEMP.OMF.3CBAA28C \r\n[root@lin11 ~]#<\/pre>\n
[oracle@lin11 ~]$ xsh rm @hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/%CDB1STB%\r\n[oracle@lin11 ~]$<\/pre>\n
[oracle@lin11 ~]$ crsctl query css votedisk\r\n## STATE File Universal Id File Name Disk group\r\n-- ----- ----------------- --------- ---------\r\n 1. ONLINE 09244fc460384f82bf1bd0bbf170b28b (@hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/vfile1) []\r\nLocated 1 voting disk(s).\r\n[oracle@lin11 ~]$ \r\n[oracle@lin11 ~]$ ocrcheck\r\nStatus of Oracle Cluster Registry is as follows :\r\n Version : 4\r\n Total space (kbytes) : 569748\r\n Used space (kbytes) : 85000\r\n Available space (kbytes) : 484748\r\n ID : 878048725\r\n Device\/File Name : @hVvMQYTk\/SIM1-CRS-9FB1BF8FFC57CF4DBFCA211A3C47B3D1\/data.ocr\r\n Device\/File integrity check succeeded\r\n\r\n Device\/File not configured\r\n\r\n Device\/File not configured\r\n\r\n Device\/File not configured\r\n\r\n Device\/File not configured\r\n\r\n Cluster registry integrity check succeeded\r\n\r\n Logical corruption check bypassed due to non-privileged user\r\n\r\n[oracle@lin11 ~]$<\/pre>\n
Summary<\/h1>\n
\n