{"id":8739,"date":"2016-08-29T13:47:00","date_gmt":"2016-08-29T11:47:00","guid":{"rendered":"https:\/\/www.dbi-services.com\/blog\/oda-x6-database-classes-and-shapes\/"},"modified":"2016-08-29T13:47:00","modified_gmt":"2016-08-29T11:47:00","slug":"oda-x6-database-classes-and-shapes","status":"publish","type":"post","link":"https:\/\/www.dbi-services.com\/blog\/oda-x6-database-classes-and-shapes\/","title":{"rendered":"ODA X6 database classes and shapes"},"content":{"rendered":"

By Franck Pachot<\/h2>\n

.
\nOn the Oracle Database Appliance, like on the Oracle public Cloud, you define the CPU capacity with ‘shapes’. On the latest ODA, the X6, we have a new interface to provision a database. Let’s look at the different shapes available.<\/p>\n

ODACLI<\/h3>\n

You can provision a new database with the command line ODACLI which replaces the OAKCLI you used in ODA X5:<\/p>\n

\n[root@odax6m ~]# odacli create-database\nUsage: create-database [options]\n  Options:\n  * --adminpassword, -mm\n       Password for SYS,SYSTEM and PDB Admin\n    --cdb, -c\n       Create Container Database\n       Default: false\n    --dbclass, -cl\n       Database Class OLTP\/DSS\/IMDB\n       Default: OLTP\n    --dbconsole, -co\n       Enable Database Console\n       Default: false\n    --dbhomeid, -dh\n       Database Home ID (Use Existing DB Home)\n  * --dbname, -n\n       Database Name\n    --dbshape, -s\n       Database Shape{odb1,odb2,odb3 etc.}\n       Default: odb1\n    --dbstorage, -r\n       Database Storage  {ACFS|ASM}\n       Default: ACFS\n    --dbtype, -y\n       Database Type {SI|RAC}\n       Default: SI\n    --help, -h\n       get help\n       Default: false\n    --instanceonly, -io\n       Create Instance Only (For Standby)\n       Default: false\n    --json, -j\n       json output\n       Default: false\n    --pdbadmin, -d\n       Pluggable Database Admin User\n       Default: pdbadmin\n    --pdbname, -p\n       Pluggable Database Name\n       Default: pdb1\n    --targetnode, -g\n       Node Number (for single-instance databases)\n       Default: 0\n    --version, -v\n       Database Version\n       Default: 12.1.0.2\n<\/code><\/pre>\n
ODA WebConsole<\/h3>\n
But the ODA X6 has also a small graphical interface from the web console.<\/p>\n
\"CaptureODACreate\"<\/a><\/p>\n
12c multitenant is the default, but you can choose.<\/p>\n
Edition<\/h3>\n
You don’t have the choice when you create the database. You install the ODA in Standard or Enterprise and then you cannot change.<\/p>\n
Versions<\/h3>\n
Two database versions are available: 11.2.0.4 and 12.1.0.2<\/p>\n
\"CaptureODAVersions\"<\/a><\/p>\n
You choose ODA to get a stable, certified and supported system so it make sense to run only supported versions with latest PSU. If you have older versions, you must upgrade. Set optimizer_features_enable to previous if your application was not tuned for newer versions. Very often, when an ISV do not certify his software it’s because of optimizer regressions. With proper testing and optimizer settings you should be able to upgrade any application without the risk of regression.<\/p>\n
Templates<\/h3>\n
There are four DBCA templates available<\/p>\n