Oracle Tidbits – June 2016

Oracle *daily* TidBits” (#oratidbit) published at https://www.facebook.com/oraclenotes on weekdays in June 2016. You will also see these tidbits, one tidbit at a time, for each page refresh on the right side of this blog as well… Hope you find these helpful to learn something new or to remind you of its existence and use…

TidBit
#oratidbit The Oracle #APEX session state is managed in the database tables within Oracle Application Express. APEX does not use a dedicated database connection. Instead, each request is made through a separate database session, consuming minimal CPU resources.
#oratidbit Oracle #APEX three-tier architecture has 1) A web browser 2) Oracle HTTP Server (Apache) with mod_plsql or Oracle Application Express Listener 3) An Oracle database containing Oracle Application Express.
#oratidbit Oracle #APEX two-tier architecture has 1) A web browser 2) An Oracle database containing the embedded PL/SQL gateway and Oracle Application Express. The embedded PL/SQL gateway runs in the Oracle XML DB Protocol Server in the Oracle database and includes the core features of mod_plsql.
#oratidbit In Oracle #APEX, the area where you develop applications is called a workspace. A workspace is a virtual private database that enables multiple users to work within the same Oracle Application Express installation while keeping their objects, data, and applications private.
#oratidbit The hostname in the #APEX login URL will depend on the type of setup. 1) name of the system where Oracle Application Express Listener is installed 2) name of the system where Oracle HTTP Server is installed 3) name of the system where Oracle XML DB Protocol Server is installed.
#oratidbit Configure Oracle DB Smart Flash Cache using parameters DB_FLASH_CACHE_FILE and DB_FLASH_CACHE_SIZE. To configure multiple devices, comma separate each device and each device size in same order.
#oratidbit Oracle recommends to configure DB Smart Flash Cache on all RAC nodes (or none), and the total size be approximately same on all nodes.
#oratidbit The In-Memory (IM) column store is a static pool in the SGA. Data in the IM column store does not reside in the traditional row format but instead in a columnar format.
#oratidbit In-Memory column store can be enabled at a column, table, materialized view, tablespace or partition level. For a partitioned table, you can populate all of the partitions in the IM column store or a subset of the partitions.
#oratidbit INMEMORY_SIZE sets the size of the IM column store in a database instance. Value for CDB$ROOT determines the total IM size for CDB. Each PDB can set this parameter to limit the IM size for PDB. If this parameter is not specifically set for a PDB, the PDB inherits the CDB value.
#oratidbit For maximum speed and efficiency, Oracle Big Data Appliance can be connected to Oracle Exadata Database Machine, which can be connected to Oracle Exalytics In-Memory Machine. All connections use Infiniband that enables high speed data transfer.
#oratidbit Apache Hive is an open-source data warehouse that supports data summarization, ad hoc querying, and data analysis of data stored in HDFS (Hadoop Distributed File System). It uses a SQL-like language called HiveQL.
#oratidbit Oracle NoSQL (“Not Only SQL”) Database is typically used to store customer profiles and similar data for identifying and analyzing big data.
#oratidbit Oracle Big Data SQL supports queries against vast amounts of big data stored in multiple data sources, including Apache Hive, HDFS (Hadoop Distributed File System), Oracle NoSQL Database, and Apache HBase. You can view and analyze data from various data stores together, as if it were all stored in an Oracle database.

Leave a Reply

%d bloggers like this: