Oracle Unbreakable Linux (Red Hat Enterprise)

When installing, put the GRUB1 bootload onto the same partition or it will replace the Ubuntu GRUB2 bootloader.

When launching enter 'c' at grub menu to go into command line. Enter chainloader (hd0, and hit tab to list the partition options.

Select the Red Hat partition # (label it for easy identification) and close the command with )+1

chainloader (hd0, msdos4)+1
boot

The firewall is not open for port 1521.
Make sure to set ORACLE_HOME and ORACLE_HOME_LISTENER in oracle .bash_profile
Use dbstart and dbshut to start and shutdown the database
Have to edit /etc/hosts to associate the host name and IP address, have to update it when DHCP changes.
Have to edit tns listener config file to point to the correct hostname or IP or it won't start.


Customizing Grub2 menu:

Edit: /etc/grub.d/40_custom

Add:
menuentry "Redhat" {
insmod ext2
set root=(hd0,3)
linux /boot/vmlinuz-2.6.32-24-generic root=/dev/sda3 ro
initrd /boot/initrd.img-2.6.32-24-generic
}


Update grub2 menu:
sudo update-grub


Comments

Post a Comment

Popular posts from this blog

Sites, Newsletters, and Blogs

BLOGS Java.net Weblogs Martin Fowler's blog Paul Graham Ruminations of a Programmer Form Follows Function Newsletters Core Java Tech Tips Enterprise Java Tech Tips JavaSpecialists.EU TheServerSide.com Sites Java.net Today Hot Java Sites CSS Zen Garden Evernote Hacker News Pragmatic Programmer
Read more

Oracle JDBC ReadTimeout QueryTimeout

If a query exceeds the oracle.jdbc.ReadTimeout without receiving any data, an exception is thrown and the connection is terminated by the Oracle driver on the client. Unfortunately the session will still be queued on the database and continue to wait for locks, hold any current locks, and complete any DML/PL*SQL procedures that are pending on the server-side of the orphaned connection. If an application, on a another connection, due to ReadTimeout exception, retries DML/PL*SQL  which requires locks, those queries will queue behind the initial DML/PL*SQL. This will increase the workload exacerbating the situation. On applications with retries, this can be observed by querying the v$session table  or gv$session on RAC and noting new sessions started periodically based on the ReadTimeout interval. The sessions may often have the same SQL_ID and/or SQL_HASH_VALUE. If stmt.setQueryTimeout(Seconds) is issued and the statement exceeds the timeout, it will atte...
Read more

Locks held on Oracle for hours after sessions abnormally terminated by node failure

If a session holds db locks and is abnormally terminated (no fin/ack), the locks will persist until the db session is closed, typically around 2 hours and 12 minutes with default network tcp_keepalive settings. Abnormally terminated does not include CTRL C or kill -9. The ojdbc6 driver apparently has a shutdown hook thread that closes the connections in graceful shutdowns. The OS apparently closes the connections when processes are killed. Abnormally terminated might include power failure, firewall failures, Out Of Memory, OS/kernel crash, network connection failure, JBoss or other server node failure, etc. This was easily reproduced by creating a  process that connected to the db and updated a record but did not commit. While the first process was waiting, a second process with a contending update was started which blocked on the first update. The first clients network cable was then disconnected. The second clients transaction waited for approximately 2 hours until the databa...
Read more