Skip to main content

ToolKit for Oracle Database

OraToolKit is a collection of tools to ease and optimize Oracle setups throughout the whole lifecycle. With its all-purpose usage it can also be called "The Swiss Army Knife for Oracle". Released as open source software it provides to companies using Oracle database technology many benefits. Those can be seen from financial, efficiency as well as from usability point of view. Goal of this open source project is to help reducing total cost of ownership (TCO) when running Oracle on Unix based systems. Supported are currently Linux and Solaris. In Q3/Q4 there there will be a new OTK release which will support IBM AIX as well as HP-UX. Future releases of an OTK light running on Microsoft Windows operating systems may not be excluded.

Benefits for companies
no license costs required for using OTK
occasional free support
increased productivity of employees
low training costs due to free online tutorials and how-tos
ability to prevent outages due to human errors
reduced DBA dependency
satisfied employees

Benefits for employees
ready to be downloaded and installed
hundreds of quick installation guides available, therefore no big training required
flexible configuration, contains only a few constraints
no need to reinvent the wheel for standard tasks
installManager with swReqCheck, osSetup, swInst, cssdConfig, asmSetup, envSetup and dbSetup actions to install Oracle within 60 minutes
cloneManager for mass deployments over the network
backupManager for rman backups
partitionManager for housekeeping tasks incl. faked partitioning
dataPumpManager for easy export, import and sync tasks
appctl to manage Oracle services from command line
sql*plus enhancement with auto-complete and history functionality

https://www.oratoolkit.ch/

Etiketler:

Comments

Post a Comment

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three
Post a Comment
Read more

3 Node (Master Slave Slave) Redis Cluster with Sentinel

It is possible to make your Redis cluster Fault Tolerant and Highly Available by building a replica set and then monitor these nodes using sentinel for automatic failover. I am going to give an example setup to explain it. The structure is built with three nodes running one as a master and two as slaves. Master Node: (Centos 7.2) 192.168.1.11 Slave1 Node: (Centos 7.2) 192.168.1.12 Slave2 Node: (Centos 7.2) 192.168.1.13 Edit System settings on each node: /etc/sysctl.conf Disable transparent hugepage (transparent_hugepage=never) on each node: /etc/default/grub Apply grub config and reboot each node: Master Node: /etc/redis/6379.conf Slave1 Node: /etc/redis/6379.conf Slave2 Node: /etc/redis/6379.conf Master Node: /etc/redis/sentinel.conf Slave1 Node: /etc/redis/sentinel.conf Slave2 Node: /etc/redis/sentinel.conf Each Node: /etc/systemd/system/multi-user.target.wants/redis-server.service Each Node: /etc/
1 comment
Read more