JSON support was introduced in Oracle Database Release 2 (188.8.131.52) allowing you to store and retrieve data between the applications and the database engine. This post expands upon a previous post about basic JSON support by detailing the performance effects of different JSON notations. In production scenarios, large JSON documents or large numbers of JSON documents can challenge a database’s ability to perform.
Viewing entries tagged
With Database 12c, Oracle has provided a handy feature, Queryable Patch Inventory, which allows for a SQL and PL/SQL interface to the product patch inventory. Previously, this information was only accessible through the OS command: OPatch. Now, with the DBMS_QOPATCH package, you can monitor distributed Opatch repositories from a central location.
OPatch now supports inventory in XML format and inventory data is stored in database tables. So as data is stored in database tables, you can view installed database patches performing interactive queries using SQL*Plus. Oracle database 12c provides DBMS_QOPATCH package to manage this interface. It is installed by default during instance creation or by executing “dbmsqopi.sql” SQL script.
JSON database implementation allows you store and retrieve data between the applications and the database engine conforming to the JSON standard avoiding the need of writing custom procedures and special code.