Oracle 21c introduces a new feature called Blockchain Tables, which allows users to store and query data stored on a blockchain network directly in the database. This feature makes it easy to integrate blockchain data into Oracle-based applications, and enables users to leverage the security and immutability of blockchain technology while still using familiar SQL commands to access and manipulate the data.
This article presents how to install and configure Apex 21.2 with standalone ORDS 21.2
This article presents how to install Oracle 21C on Oracle Enterprise Linux 8 (OEL8) in silent mode.
This article presents how to install Oracle 21C on Oracle Enterprise Linux 8 (OEL8) using rpm
This article show simple coding standard that I use for coding. Simple rules clean code.
If you are working as developer/DBA probably you are quite often asked to migrate some rows from one database to another – usually people reference to the rows as “metadata” rows. Rows that driving your business !
If you need to prepare such rows for migrations there are a lot of methods to do it
just copy the rows using database link from one database to another
export/import the rows using tools like expdp/impdp
prepare manually scripts with INSERT statements
I would like to focus on the last method. It’s very popular to keep metadata in some files as number of INSERTs for backup/migrations/versioning etc.
This article presents how to install Fedora 25 – Live Workstation version.
I assume you have already downloaded Fedora 25 64 bit Live Workstation(about 1,3 G) and you know how to use VirtualBox 64 bit(100M). Create virtual machine with default settings for Linux Fedora 64 bit. 2GB ram and 64G(includes extra space for Oracle installations) for disk is enough plus increase video memory to 128M. Rest of options you can keep default.
You can find original user password in table USER$. Because of security improvements it is not exposed in DBA_USERS view anymore since version 10G. Moreover password is hashed so once set you are not able to know original value. Access to USER$ is as well very restricted.
Hakan factor
The Hakan factor is used to unique map rows in a Bitmap Index to the rows in the base table. This factor is related to the max number of rows that can be stored in a single block of a table. Several factors like the column type and not null constraints influence the Hakan factor. The factor will also be recalculated when a table is modified until there is the first bitmap Index is created. Than the Hakan factor has to be protected for the existing bitmap indexes.
If a new table created to exchange data with the partitioned table, with a table layout, that include columns added after the bitmap index creation on the partitioned table, will most likely result in a different Hakan factor.
Errors
If the Hakan Factor do not match during exchange partitions, the prognosis is either of the error messages below:
The error can appear only if you exchange a partition with bitmap indexes
Autonomous transaction – is an independent transaction called from another transaction which is the main transaction.
Features of autonomous transaction
Special pragma AUTONOMOUS_TRANSACTION is introduced in PL/SQL. The pragma instructs the database that executed code is to be executed as new autonomous transaction independent from main transaction.