JSON support was introduced in Oracle Database Release 2 (220.127.116.11) 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
Transaction Recovery is a feature of Oracle database that allows DBAs to recover from transactions which have undesirable effects. Sometimes it happens that a transaction performs an undesirable effect, and we determine later that this transaction should not have been committed. In this case, we do not want to perform database point-in-time recovery as the rest of database is working fine. We only have a problem with one transaction. Oracle allows us to provide approximate times of the problematic transaction and search the archived and online redo log files for transactions performed during said time. Then we can identify the transaction and roll it back. Transaction recovery is very easy to use from Oracle Enterprise Manager, but it requires some setup to perform before we can use it.
Oracle Database creates text files to help you diagnose session and server activities. Some of them are generated by the database itself automatically and others can be generated on demand by database administrators or developers. This post will address how to trace Oracle sessions and how to gather information to perform troubleshooting.