Friday, July 25, 2014

Pre-Built Developer VMs (for Oracle VM VirtualBox)

If you need to download virtual machine, then use the links:


http://www.oracle.com/technetwork/community/developer-vm/index.html

http://www.oracle.com/technetwork/server-storage/vm/database-templates-12c-11gr2-1972804.html

Friday, July 18, 2014

Патч 12.1.1.1.1



На днях вышел квартальный патч на Экзадату, версия 12.1.1.1.1.
Эта версия поддерживает 4Т-диски и может быть установлена на Х2 и Х3.
Это означает, что владельцы Х2 и Х3 Экзадат могут заменить свои диски на 4Т с целью увеличения дискового пространства.
 

Capacity-On-Demand on Oracle Exadata Database Machine



Вышел квартальный Июльский патч на Экзадату (версия образа 12.1.1.1.1), в котором включена возможность
«Capacity-On-Demand on Oracle Exadata Database Machine»
Т.е. появилась возможность включить не все ядра в Экзадате, и таким образом сэкономить на лицензиях на СУБД. Условия, на которых оно возможно:
  • Capacity-on-demand is available for Oracle Exadata Database Machine X4-2 and Oracle Exadata Database Machine X4-8 Full Rack systems.
  • Oracle Exadata Database Machine X4-2 Eighth Rack is excluded from capacity-on-demand.
  • Reducing the number of active cores lowers the initial software licensing cost. It does not change the hardware cost.
  • The minimum number of processor cores that must be enabled is half of the physical cores on each processor. For Oracle Exadata Database Machine X4-2 systems, the minimum is 6 per processor (12 per database server). For Oracle Exadata Database Machine X4-8 Full Rack, the minimum is 8 per processor (64 per database server).
  • Additional cores are increased in 2-core increments per server on Oracle Exadata Database Machine X4-2, and in 8-core increments on Oracle Exadata Database Machine X4-8 Full Rack. Database servers in the same system can enable a different number of cores.
  • Capacity-on-demand may only be used to decrease the number of active processor cores during initial installation. After initial configuration, the processor core count can only increase on a system, up to the maximum. It is the customer's responsibility to acquire the additional software licenses.
  • Oracle Exadata Database Machine must use Oracle Configuration Manager or Oracle Platinum Services to qualify for capacity-on-demand.
  • Oracle Exadata Database Machine purchased under Infrastructure as a Service (IaaS) is not eligible for capacity-on-demand.

Tuesday, July 15, 2014

Exadata X4 multipathing with active-active infiniband

The X4 Exadata has the new feature "active-active" ports on the IB HCA.
As a result the v$asm_disk.PATH shows the 2 IP for the each disk path:

SQL> select path from v$asm_disk;

PATH
-------------------------------------------------------
o/192.168.11.9;192.168.11.10/RECOC1_CD_06_ed02celadm03
o/192.168.11.9;192.168.11.10/DATAC1_CD_09_ed02celadm03
o/192.168.11.9;192.168.11.10/DBFS_DG_CD_04_ed02celadm03
o/192.168.11.9;192.168.11.10/DBFS_DG_CD_03_ed02celadm03
o/192.168.11.9;192.168.11.10/DATAC1_CD_00_ed02celadm03
o/192.168.11.9;192.168.11.10/RECOC1_CD_02_ed02celadm03



[oracle@ed02dbadm01 ~]$ /sbin/ifconfig -a

ib0       Link encap:InfiniBand  HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 
          inet addr:192.168.11.1 


ib1       Link encap:InfiniBand  HWaddr 80:00:00:49:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 
          inet addr:192.168.11.2


As you can see above the DB node host 'ed02dbadm01' has the IPs 11.1 and 11.2, but disks have IPs 11.9 and 11.10. Therefore the disks are addressed with cell IP addresses, in our case 'ed02celadm03'. Let look its ifconfig:
[root@ed02celadm03 ~]# ifconfig -a

ib0       Link encap:InfiniBand  HWaddr 80:00:00:48:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 
          inet addr:192.168.11.9

ib1       Link encap:InfiniBand  HWaddr 80:00:00:49:FE:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 
          inet addr:192.168.11.10


Yes,

And let's look to cellip.ora on DB nodes, it now has 2 IPs because active-active ports (old version has 1 IP because active-passive ports):

[root@ed02dbadm01 ~]# cat /etc/oracle/cell/network-config/cellip.ora
cell="192.168.11.5;192.168.11.6"
cell="192.168.11.7;192.168.11.8"
cell="192.168.11.9;192.168.11.10"


Does DEALLOCATE UNUSED or SHRINK SPACE will free space occupied by LOB segment?

Lets check how it works. My env is DB 19.20@Linux-x64 1) I created the table with 4 LOB columns of 4 different LOB types: BASICFILE BLOB, BA...