Latest Entries »

Position Responsibilities

• Manage database configurations, schemas, and space • Manage database and system alerts. • Support new application code releases / builds in various production and non-production environments • Provide performance tuning, problem research/resolution, code reviews and deployments, SQL support, and data movement • Manage database changes for releases and new projects • Provide SQL and application tuning assistance • Build Backups / Recovery and High Availability • Manage disaster recovery support and testing • Monitor database health and alerts • Provide production on-call support on rotational basis • Manage database and product deployments and repeated database maintenance and monitoring tasks • Troubleshooting database issues • Open & follow-up on change request tickets for internal users • Open and follow-up on service requests with Oracle vendor support

Position Requirements

• Degree or equivalent experience in either Oracle or Sybase. • BS in Computer Science or equivalent specializing in Oracle or Sybase • Good understanding of relational methodology • Good understanding of SQL Plus or equivalent • Good communication skills and the ability to work as a team member • Good analytical and problem solving skills. • Self starter with willingness to do independent research and trouble shooting. • Willingness to learn new database skills in a fast paced environment • Education or Experience with Unix shell scripts helpful • Good understanding of relational methodology • Must be comfortable in both self-managed and team driven environment • Experience with Microsoft Office Tools helpful

Interested? (say I referred you on the application form)

For those of you that are thinking about using using libvirt/kvm on Linux… here is a discussion on proposed best practices

little annoyed that setting a ‘default’ connect string with virt-top and virsh is different:

virsh uses the environment variable VIRSH_DEFAULT_CONNECT_URI
export VIRSH_DEFAULT_CONNECT_URI=’qemu:///system’

virt-top uses the config file .virt-toprc
connect qemu:///system

for KVM, using an actual network bridge is desired for performance over NAT. There is a virtual bridge used by XEN (virbr0) that you won’t need.
To disable it:

$ virsh net-destroy default
$ virsh net-undefine default

# If Redhat based distro:
$ service libvirt-bin stop
# if Debian/Ubuntu based distro:
$ service libvirtd restart  

$ ifconfig
 

It is likely SELinux trying to keep you safe.  Just run:

$ restorecon /home

It will correct the SELinux flags on the /home directory.