DB startup & shutdown in 10g DB on Linux

Hi all,
I have installed Oracle 19g DB. Now i don't know how to start that database when linux boots up. when i switch to oracle user by [ su oracle ] and start sqlplus, it starts but asks for a username / pwd and since db is not started so it doesn't let me login and says Oracle Not Available ! I have heard that after Oracle 9i Oracle has stopped Server Manager and all admin is done through sql*plus. Now if i can't start sqlplus then how can i start databse ? tell me if i can start the DB at system bootup or some other way through which i can start database ! I need the urgently ! thanx in advance !
Ahmed.

sorry, links are:
# cd /etc/init.d/rc5.d
# ln -sf ../dbora S97oracle
# ln -sf ../dbora K03oracle
# ln -sf ../misc_stuff S03misc_stuff
The contents (copy-paste from the script). Put this someway in the 'dbora' file, values are default for 10g:
#!/bin/sh
# Original scripts from http://otn.oracle.com/
# 10-08-2001 MiKu Oracle8i (8.1.6r2) startup script
# 15-11-2002 MiKu Oracle9i (v9.1) startup sctip
# 14-02-2004 MiKu Oracle10g (v10.1.0.2) startup script
# Set ORA_HOME to the equivalent off $ORACLE_HOME
# (from which you wish to execute dbstart and dbshut)
# Set ORA_OWNER to the user id of the owner of the
# Oracle database in ORA_HOME
ORA_HOME=/u01/app/oracle/product/10.1.0/db_1
ORA_OWNER=oracle
ORA_GROUP=oinstall
ORA_LOG=/home/oracle/log/startup.log
ORA_LASTLOG=/home/oracle/log/last_startup.log
case "$1" in
'start')
:>$ORA_LOG
echo "Starting Oracle"
echo "Starting Oracle `date +%d-%m-%Y_%H:%M:%S`" >> $ORA_LOG
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start LISTENER" >> $ORA_LOG 2>&1
su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart" >> $ORA_LOG 2>&1
chown $ORA_OWNER:$ORA_GROUP $ORA_LOG
'stop')
echo "Shutting down Oracle"
echo "Shutting down Oracle `date +%d-%m-%Y_%H:%M:%S`" >> $ORA_LOG
su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl stop LISTENER" >> $ORA_LOG 2>&1
su - $ORA_OWNER -c "$ORA_HOME/bin/dbshut" >> $ORA_LOG 2>&1
rm -f $ORA_LASTLOG >/dev/null 2>&1
cp $ORA_LOG $ORA_LASTLOG
chown $ORA_OWNER:$ORA_GROUP $ORA_LASTLOG
esac
# end of script
The contents for misc_stuff [cont]

Similar Messages

Startup Scripts for OBIEE 11g on Linux

Hi, I originally spent many hours trying to find a startup/shutdown script for OBIEE on linux, in the end I compiled a new one based on notes in the install manual and other posts on the subject until I got it working consistantly
Please add comments or improvements :)
Note: you need to create the boot.properties file (in /security) for each server, and provide the username/password so WebLogic won't prompt for it when starting automatically (otherwise it doesn't start :p) ....refer to the install manual or [weblogic boot.properties|http://onlineappsdba.com/index.php/2010/08/21/weblogic-startup-prompting-from-username-password-bootproperties/]
#!/bin/bash
# /etc/init.d/obiee
# Run-level Startup script for OBIEE
# set required paths
export ORACLE_BASE=/opt/oracle
export ORACLE_HOME=/opt/oracle/product/11.1.0/db_1
export ORACLE_OWNR=oracle
export ORACLE_FMW=/opt/oracle/product/fmw
export PATH=$PATH:$ORACLE_FMW/bin
case "$1" in
start)
echo -e "Starting Weblogic Server...."
su $ORACLE_OWNR -c "$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/startWebLogic.sh > /dev/null 2>&1 &"
sleep 30
echo -e "Starting Node Manager..."
su $ORACLE_OWNR -c "$ORACLE_FMW/wlserver_10.3/server/bin/startNodeManager.sh > /dev/null 2>&1 &"
sleep 30
echo -e "Starting Managed Server: bi_server1..."
su $ORACLE_OWNR -c "$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/startManagedWebLogic.sh bi_server1 [url for admin console] > /dev/null 2>&1 &"
sleep 30
echo -e "Starting Components...."
su $ORACLE_OWNR -c "$ORACLE_FMW/instances/instance1/bin/opmnctl startall > /dev/null 2>&1 &"
sleep 30
stop)
echo -e "Stopping Components...."
su $ORACLE_OWNR -c "$ORACLE_FMW/instances/instance1/bin/opmnctl stopall > /dev/null 2>&1 &"
sleep 30
echo -e "Stopping Managed Server: bi_server1..."
su $ORACLE_OWNR -c "$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopManagedWebLogic.sh bi_server1 [url for admin console] [weblogic user] [weblogic pass] > /dev/null 2>&1 &"
sleep 30
echo -e "Stopping Weblogic Server...."
su $ORACLE_OWNR -c "$ORACLE_FMW/user_projects/domains/bifoundation_domain/bin/stopWebLogic.sh > /dev/null 2>&1 &"
sleep 15
status)
echo -e "Component Status...."
su $ORACLE_OWNR -c "$ORACLE_FMW/instances/instance1/bin/opmnctl status"
restart)
$0 stop
$0 start
echo "Usage: `basename $0` start|stop|restart|status"
exit 1
esac
exit 0
Hopefully this helps others in the same situation
Cheers

HI,
Is this script for Enterprise Install on a single computer? For Simple install I think there is no concept of nodemanager and managedserver.
--Joe

Startup/Shutdown script for OBIEE 11g on Linux

Hi all,
as a follow-up to [url http://forums.oracle.com/forums/thread.jspa?messageID=4546010]an earlier thread by some fine gentleman, I have improved the original startup/shutdown script for Linux a bit, making sure that all processes are handled correctly. The script has been tested and works fine on CentOS 5.5 with Oracle BI 11.1.1.3.0 in a clustered configuration. Instructions:
Manual start/stop:
> service obiee start
> service obiee stop
> service obiee status
Automatic start/stop during boot sequence:
> chkconfig --add obiee
> chkconfig obiee on
Note that in order for the procedure to go through smoothly, you need to provide the admin credentials (username/password, defaulting to weblogic/weblogic) in three different places:
1. In configuration file <FMW_HOME>/user_projects/domains/<domain name>/servers/AdminServer/security/boot.properties for the administration server;
2. In script <FMW_HOME>/user_projects/domains/<domain name>/bin/startManagedWebLogic.sh (variables WLS_USER and WLS_PW) for the managed server;
3. In the startup script itself (variables BIEE_USER and BIEE_PASSWD) for shutting down the managed server.
Complete logs are available in /var/log/obiee-start (-stop).log files.
Please comment as necessary,
Chris
#!/bin/bash
# File:    /etc/init.d/obiee
# Purpose: Start and stop Oracle Business Intelligence 11g components.
# chkconfig: 2345 99 10
# description: Manage OBIEE service.
# These values must be adapted to your environment.
ORACLE_OWNR=oracle                  # Local Unix user running OBIEE
ORACLE_FMW=/home/oracle/biee        # Deployment root directory
BIEE_USER=<username>                # BIEE administrator name
BIEE_PASSWD=<password>              # BIEE administrator password
BIEE_DOMAIN=<domain name>           # Domain name
BIEE_INSTANCE=instance1             # Instance name
BIEE_SERVER=bi_server1              # Server name
BIEE_MANAGER_URL=<hostname>:7001    # Admin server URL (hostname:port)
# These should require no change.
WL_PATH=$ORACLE_FMW/wlserver_10.3/server/bin
BIEE_PATH=$ORACLE_FMW/user_projects/domains/$BIEE_DOMAIN/bin
ORACLE_INSTANCE=$ORACLE_FMW/instances/$BIEE_INSTANCE
export ORACLE_INSTANCE
START_LOG=/var/log/obiee-start.log
STOP_LOG=/var/log/obiee-stop.log
SUBSYS=obiee
start() {
    echo "********************************************************************************"
    echo "Starting Admin Server on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/startWebLogic.sh" &
    wait_for "Server started in RUNNING mode"
    echo "********************************************************************************"
    echo "Starting Node Manager on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$WL_PATH/startNodeManager.sh" &
    wait_for "socket listener started on port"
    echo "********************************************************************************"
    echo "Starting Managed Server $BIEE_SERVER on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/startManagedWebLogic.sh $BIEE_SERVER http://$BIEE_MANAGER_URL" &
    wait_for "Server started in RUNNING mode"
    echo "********************************************************************************"
    echo "Starting BI components on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl startall"
    echo "********************************************************************************"
    echo "OBIEE start sequence completed on $(date)"
    echo "********************************************************************************"
stop() {
    echo "********************************************************************************"
    echo "Stopping BI components on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl stopall"
    echo "********************************************************************************"
    echo "Stopping Managed Server $BIEE_SERVER on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/stopManagedWebLogic.sh $BIEE_SERVER t3://$BIEE_MANAGER_URL $BIEE_USER $BIEE_PASSWD"
    echo "********************************************************************************"
    echo "Stopping Node Manager on $(date)"
    echo "********************************************************************************"
    pkill -TERM -u $ORACLE_OWNR -f "weblogic\\.NodeManager"
    echo "********************************************************************************"
    echo "Stopping Admin Server on $(date)"
    echo "********************************************************************************"
    su $ORACLE_OWNR -c "$BIEE_PATH/stopWebLogic.sh"
    echo "********************************************************************************"
    echo "OBIEE stop sequence completed on $(date)"
    echo "********************************************************************************"
wait_for() {
    res=0
    while [[ ! $res -gt 0 ]]
    do
        res=$(tail -5 "$START_LOG" | fgrep -c "$1")
        sleep 5
    done
case "$1" in
    start)
        echo "********************************************************************************"
        echo "Starting Oracle Business Intelligence on $(date)"
        echo "Logs are sent to $START_LOG"
        echo "********************************************************************************"
        start &> $START_LOG &
        touch /var/lock/subsys/$SUBSYS
    stop)
        echo "********************************************************************************"
        echo "Stopping Oracle Business Intelligence on $(date)"
        echo "Logs are sent to $STOP_LOG"
        echo "********************************************************************************"
        stop &> $STOP_LOG
        rm -f /var/lock/subsys/$SUBSYS
    status)
        echo "********************************************************************************"
        echo "Oracle BIEE components status...."
        echo "********************************************************************************"
        su $ORACLE_OWNR -c "$ORACLE_INSTANCE/bin/opmnctl status"
    restart)
        $0 stop
        $0 start
        echo "Usage: $(basename $0) start|stop|restart|status"
        exit 1
esac
exit 0

You can use WLST to start/stop BI Services and it works on both Linux and Windows.
Following link has the sample -
http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10541/admin_api.htm#CDEFAHDD

Startsap & stopsap on Linux startup & shutdown

Hy everyone!
I have a simple question: does anyone use startsap/stopsap scripts on Linux startup/shutdown run levels? I mean, when Linux starts up (init 5 run level) it must start SAP using startsap and stopsap on init 0 as well.
It seems to be no problem at all to do that but once that is not set up by default on Linux systems (not in mine for sure) I have decided to ask for a second opinion.
Thanx in advance for any help.
Paulo

Eric,
my goal is a little bit different that that: I'm looking for a way to quick shutdown or startup SAP system with the mininum possible effort during an emergency situation.
Let me explain the situation: we are constantly affected by power down issues, especially in summer time. When such situations occur, we have to quickly shut down as many servers as possible before the power turns completely off (by nobreak).
We are currently working on power infrastructure to avoid those "downs" issues, but until we have fully reached that, we need to get some safe systems shutdowns (at least for production servers).
So I was considering to include at least the stopsap script in init 0 run level on Linux.
What do you think about that?
Thanx for your help until now. It's good to have someone to discuss something like that and exchange experiences/ideas.
Paulo

Automating Weblogic Startup/Shutdown on Linux

hello and hope you fine
im using weblogic 10.3 with oracle db 11g on CentoOS 5.5
everything is working fine
but my problem is that i want to startup/shutdown weblogic on system start/shutdown
i defined weblogic as service ( i tried all levels) and it works but the problem is
when the system is booting it start weblogic but it stops continue system boot!
i also tries put the start weblogic on the .bash_profile
the system boot but when im trying to login it stops because the same problem
(weblogic startup and prevent contitnue the loginin )
i also tried to add startWeblogic in /etc/rc.d/rc.local
and the same problem when weblogic start system cant continue booting
i also tried using nohup
also the same problem
so how can i start/shutdown weblogic ?
and thanks for help
Edited by: user13113692 on Aug 2, 2010 3:22 AM

thank you for your replay
but its the same
when server is booting
the weblogic start and goes to the running state
it stops continue the other services and
the server boot could not continue
here is some of my script
#!/bin/sh
WEBLOGIC_HOME=/root/Oracle/Middleware/user_projects/domains/mydomain/
# source function library
. /etc/rc.d/init.d/functions
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh &
i also tried something like this to grape all the output to a log file
but the problem here is that the weblogic give me a exception about the paths
case "$1" in
start)
echo "Starting weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/startWebLogic.sh ALL > ${WEBLOGIC_HOME}/logz/start.log 2>&1 &
stop)
echo "Stopping weblogic..."
     cd $WEBLOGIC_HOME
     su root $WEBLOGIC_HOME/bin/stopWebLogic.sh ALL >${WEBLOGIC_HOME}/logz/stops.log 2>&1 &
i also tried this with the standalone weblogic and its the same
any help will be appreciated

How to automate database startup/shutdown in RHEL4

Dear All
I have Oracle 10gR2 database on RHEL4.
If i want to automate database startup/shutdown with OS startup/shutdown,
Then where i need to update about dbstart.sh & dbshut.sh
I have already made entry in /etc/oratab as Y for database SID.
I am using Bourn Shell.
Thanks

You can refer to my post in my Blog
[Automatically StartUp and Shutdown an Oracle Database in Linux OS|http://kamranagayev.wordpress.com/2008/12/22/automatically-startup-and-shutdown-database-in-linux-os/]
Kamran Agayev A. (10g OCP)
http://kamranagayev.wordpress.com
[Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]

Grepping for startup/shutdown in the logs

Hello,
I've been asked to provide a script that parses the oracle logs and can determine if there were some errors. So far I can find the numerical errors in my script (like ORA-00600) but I also need to be able to tell when a db has been shut down, started or restarted. What can I look for in the logs that would determine that?
Thanks
Tim

EdStevens wrote:
918944 wrote:
sb92075 wrote:
918944 wrote:
Hello,
I've been asked to provide a script that parses the oracle logs and can determine if there were some errors. So far I can find the numerical errors in my script (like ORA-00600) but I also need to be able to tell when a db has been shut down, started or restarted. What can I look for in the logs that would determine that?
Realize that a shutdown may not precede a startup; since the cleaning lady could just unplug the box
Also you can treat the alert_SID.log file as EXTERNAL TABLE; eliminating the need for grep & similar OS utilities by doing everything in SQL or PL/SQL.Very interesting idea. However we're trying to be alerted to such events using nagios without logging into the box. The idea it if a startup/shutdown occors, or a numerical event such as an ORA-00600 occurs, nagios will detect that via a perl script and shoot off an email to the team and send a page to a pager. So I still need to know what in the logs would indicate a startup or shutdown. We are using oracle 10g by the way.
That shouldn't be hard at all to do. All I would need to know is what in the logs indicates a startup or a shutdown. I've tried grepping for the terms in the ${SID}_alert.log(s) but found nothing as of yet.
ThanksWell, as said earlier, a 'shutdown' could be a hard shutdown (the cleaning lady plugged a vacuum cleaner into the ups and blew the circuit, killing the server .... yes, I've seen it happen) so the db does not get an opportunity to log it.
But for the more common ones, what are you currently grepping for? Looking at one of my alert logs I see likely strings "Shutting down instance" and "Starting ORACLE instance".Thanks found it! Fixed grep.. we're now monitoring for this. Appreciate the advice!

Oracle Startup/Shutdown

Having trouble with EM in a windows server environment running 10G
When i startup/shutdown my server do i need to stop the listener, dbconsole and agent?
Everytime i reboot my TEST server EM stops working. I have checked the windows services start ok - all do with no errors. but i get the listeneer starting sometimes and sometime not. The agent and DB instance connection instances show failed on the http://myserver:1158/em page.
I have checked tnsnames and listener.ora.
Is there a process of things to start/stop when rebooting my server?
Also whe i try to start them manually a page is displayed saying enter logon credential but the credentials i enter .e.g. sys-password123 are not accepted. Does anyone have any idea what the credential i should be inputting here is it oracle-oralce or something?
Please note i have done loads of reading but can't find a solution to my problem thanks to all who take time to read/reply to what may seem a very basic question

By default the Oracle services are set to automatically start. When you reboot your server the services start and you should be able to connect. However if you try to connect right after the reboot, most probably this error will show up since the Enterprise Manager requires the database to be already registered against the listener, which may take a while (not more than 60 sec),
Verify this checklist:
1. The listener is up and running. LSNRCTL STATUS
2. The database is registered against the listener. You may issue the command LSNRCTL SERVICES.
3. You may force the database to be registered against the listener by issuing the ALTER SYSTEM REGISTER; command from a sqlplus prompt.
One more things you should take care of is the IP assignment method, if you have a dynamic IP address assignment you should configure a loopback adapter and and have the Loopback Adapter's IP address registered at the hosts file along with the hostname. If you fail to do so you may find EM will be requesting you for the logon credentials when you attempt to access the Performance tab or any other administrative task.
You may read this reference for further Enterprise Manager troubleshooting --> Enterprise Manager DB Control Console.
~ Madrid

Automatic Startup/shutdown

Hi All
Please I am trying to enable this feature, startup automatically with the system startup
I am using Oracle enterprise linux, the user with it we startup weblogic is root
it's impossible to add something in .profile_bash of oracle user (oracle user exists)
either in /etc/rc.local , nothing occured when I add the startup command on the bottom of the file
Any idea please?
Thanks

Hi,
Follow the below procedure,
1. Create a startup script like startWebLogicAdmin which would contain the below
       su - wlsadmin -c "<DOMAIN_HOME>/bin/startWebLogic.sh"
      Remember to replace the <DOMAIN_HOME> directory with the actual directory
2. Now place the script in /etc/init.d/ and make sure to give the full execute permission to this file
3. Now create a soft link point to the run level of your system
    ln -s /etc/init.d/startWebLogicAdmin /etc/rc2.d/S28startWebLogicAdmin
Remember S is used for startup and K is used during shutdown
4. You can then check if the startup service is properly configured using corresponding unix level flavor
chkconfig --list startWebLogicAdmin
Regards
Rosario

Automatic startup/shutdown script - 3 Oracle Home

Hi All,
We have a server which has 3 Oracle Home - 8i/9i/10g.
So i am confused about configuring automatic startup/shutdown scripts.
Can you guys please let me know how to setup automatic startup/shutdown for these multiple Oracle Homes.
Thanks,
Kumar.

Bellow is a HP-UX script that can help. Create three scripts like oracle8, oracle9, oracle10 with correct path values. and than decide the runlevels and create soft links for the scripts you created, for example;
Under /sbin/rc3.d
ln -s /sbin/init.d/oracle10 S999oracle10
Under /sbin/rc1.d and /sbin/rc2.d
ln -s /sbin/init.d/oracle10 C9oracle10
AUTOMATIC STARTUP/SHUTDOWN SCRIPT
$vi /sbin/init.d/oracle10
#!/sbin/sh
# NOTE: This script is not configurable! Any changes made to this
# scipt will be overwritten when you upgrade to the next
# release of HP-UX.
# WARNING: Changing this script in any way may lead to a system that
# is unbootable. Do not modify this script.
# NOTE:
# For ORACLE:
PATH=/usr/sbin:/usr/bin:/sbin
export PATH
ORA_HOME="/oracle/app/oracle/product/10.2.0"
ORA_OWNR="oracle"
rval=0
set_return() {
x=$?
if [ $x -ne 0 ]; then
echo "EXIT CODE: $x"
rval=1
fi
case $1 in
start)
# Oracle listener and instance startup
echo -n "Starting Oracle: "
su - $ORA_OWNR -c "$ORA_HOME/bin/dbstart /oracle/app/oracle/product/10.2.0"
echo "OK DB started"
stop)
# Oracle listener and instance shutdown
echo -n "Shutdown Oracle: "
su - $ORA_OWNR -c "$ORA_HOME/bin/dbshut /oracle/app/oracle/product/10.2.0"
echo "OK DB shutdown"
reload|restart)
$0 stop
$0 start
echo "usage: $0 {start|stop}"
esac
exit $rval

Unix startup/shutdown of Livecache

Hi all,
I would like to know how one can startup/shutdown Live cache from the operating system without have to run a RFC to a function module. Is it possible to simply run dbmcli and issue db_offline/db_online? Please assist.
Thanks,
Frank Magliozzi
[email protected]

Frank,
if you want to set up HA for liveCache, SAP note 952783 provides all the info, such as the various options available for HA.
This note points to further notes, which has info on shutdown/restart of liveCache in a HA environment, for e.g.:
Note 319835 : Availability of liveCache on Microsoft Cluster.
For all supported UNIX platforms, the operating system partners offer cluster agents for liveCache. Also, hot standby for liveCache has been implemented for:
- IBM (SVC, ESS, DS8000)
- EMC (Symmetrix)
Contact your hardware partner if you are interested in these options.
For Linux, the product LifeKeeper by Steeleye (<http://www.steeleye.com>), among others, supports liveCache.
Thanks,
Ashwath

HOWTO: Startup/Shutdown Sounds in Openbox

In this tutorial, I will show you how to add startup and shutdown sounds with Openbox, a light-weight window manager. In theory, this should work with any window manager that uses a startup script (or, if you use the startx command, .xinitrc could be used for the same effect); however, I will be focusing on Openbox, so you will have to adapt these instructions for use with other window managers.
We'll start with a quick background story: I was in a "tweaking" mood a few days ago, and I figured I'd try to set up some startup and shutdown noises for use with Openbox. After a few minutes of messing around, I got it working. I searched to see if there were any tutorials like this, and since there weren't, I figured I would share my knowledge--that's what tutorials are for, right?
NOTE: I originally posted this on ubuntuforums.org; therefore, there may be some differences (I tried to fix most of them). Even though I did this on Arch originally, I wrote it targeted toward Ubuntu users. I didn't get much of a response--there must not have been too many Ubuntu/Openbox users looking for that. Please point out any inconsistencies, and I'll fix them as soon as possible.
Now that we have that out of the way, let's get started.
Step 1: Installing the necessary application(s).
First off, we will be using a commandline program called play. It is part of the sox package, so let's install that first (you likely have most of its dependancies already).
# pacman -S sox
If you'd like, you can cd to a directory with music in it and type play name-of-sound-file.extension to test that it is working. If you don't have any files to try it on, you can do this later after downloading your desired sound files in step 3.
I also have sudo set up; you will need to set this up to run the shutdown commands from a script as I have them. There is a section in the ArchWiki that will help in setting it up if you want. As for the commands with sudo in them, you can just run them in a root terminal.
In addition to that, I will be working with obmenu, a program for editing Openbox's menu from a GUI; however, it will work just as well to edit the menu by hand. I assume you already have a preferred method of editing your menu, but if you want to try obmenu, it's only a pacman command away:
# pacman -S obmenu
Step 2: Setting up shutdown privileges.
For this section, I will be adapting a section from a great guide written by urukrama here. We're going to be running a shutdown command from a script, so we need to have it set up to work without any interaction--in this case, that means removing the need for a password for the shutdown command.
To do this, type in the following command into the terminal:
sudo visudo
This will open up the sudoers file, which is used to specifiy user permissions for actions that require root priveleges. For those of you unfamiliar with Vim (I'm with you ), just press i on your keyboard to enter interactive mode, which allows you to edit the file. Then, enter the following line at the end of the file:
%wheel ALL=NOPASSWD:/sbin/shutdown
Then press escape to exit interactive mode. Lastly, type in :wq followed by pressing enter to save and exit. Now you can use the sudo shutdown command without entering a password.
Step 3: Getting the desired sound files.
Now we come to the fun part of the guide--finding the sounds that we want.
There are plenty of startup and shutdown noises floating around the web; I went to gnome- and kde-look to check out theirs (the same are available at both sites). Here's a link to the System Sounds section at gnome-look. You can look through and download the ones that interest you; once you have listened to a few and found one that you like, go on. Just for reference, I chose the Dream pack. It fits very nicely with my current setup and theme.
Step 4: Setting up the shutdown/startup scripts.
If you haven't already (in the last step), extract the sound files from the package that they downloaded in. Then, look through the files and find the startup and shutdown noises. For me, they were titled Dream Intro.ogg and shutdown.ogg, respectively. Move these files into their own folder. I chose ~/.startup--on my Arch install, it was empty. You may want to put it into a different folder/sub-folder, preferably somewhere in your home folder. You can now remove all the other sound files--hypothetically speaking, it probably wouldn't be too hard to get other sounds (such as minimize, maximize, etc., if provided in the sounds package you chose) working with Openbox, but that is beyond the scope of this tutorial. Now, go to the folder in which you placed the startup and shutdown noises. For simplicity's sake, we're going to place the scripts in this same folder.
We're going to be making two scripts here--one for reboot and one for shutdown. Open up your text editor of choice here and enter the following line (replacing the "/path/to/file.extension" with the path to your shutdown sound):
play /path/to/file.extension && sudo shutdown -r now
For me, it looked like this:
play ~/.startup/shutdown.ogg && sudo shutdown -r now
What this does is play the sound file specified and, once that is done, moves on to the reboot process (that's what && does). Save this as reboot.sh. Now make a new file, this time for the actual shutdown. It will be the same as the first except the shutdown command will now be sudo shutdown -h now. Here's what mine looks like:
play ~/.startup/shutdown.ogg && sudo shutdown -h now
Save that one as shutdown.sh. At this point, we have completed the scripts for both shutdown commands. Next, open up your Openbox autostart script (should be in /home/<user>/.config/openbox/autostart.sh, where <user> is your username) with the text editor of your choice. You probably already have a few different things in here; if not, it doesn't really matter. Just add the following line to your autostart file (as you can see, I used quotes around this one because this file had a space in its name--you'll want to do the same. You can also use a backslash before the space):
play "/home/<user>/.startup/Dream Intro.ogg"&
Make sure you keep the ampersand (&) in tact; otherwise, the script will wait until the sound is done playing before completing the rest of the processes. I recommend that you place the sound file at the beginning of the script so that it starts first--the way I have it set up, everything is ready to go by the time the login sound ends (sooner, actually). Now that we've come this far, we're almost done.
Step 5: Adding the shutdown options to the Openbox menu.
At this point, the login sound will be working; however, we still need to set up the shutdown sounds. To do this, we will add a section to the Openbox menu that runs the two scripts we made in the last step.
Either open up obmenu or use your preferred text editor and open up menu.xml (should be in ~/.config/openbox/menu.xml). As I said, we will be adding two items: one for rebooting and another for shutting down. In obmenu, you can add a new submenu wherever you want (I chose the bottom of the menu) and name it Power (or whatever else you'd like). The first we'll add is named Restart. For the execute line, add the following:
bash /path/to/reboot.sh
For me, this path is ~/.startup/reboot.sh. As for the second, name it Shut Down and for the execute command put the following:
bash /path/to/shutdown.sh
Again, for me this is ~/.startup/shutdown.sh. Here is what the section in my obmenu looks like:
As for the pure XML, here it is (I replaced my name with <user> ):
<item label="Restart">
<action name="Execute">
<execute>bash /home/<user>/.startup/reboot.sh</execute>
</action>
</item>
<item label="Shut Down">
<action name="Execute">
<execute>bash /home/<user>/.startup/shutdown.sh</execute>
</action>
</item>
With obmenu, just save it, and your menu will be refreshed. When hand-editing the menu.xml file, you have to remember to Reconfigure Openbox (it will be in your menu unless you've removed it).
And with that, you should have working startup and shutdown sounds. You can test it by right clicking on your desktop and selecting one of your new shutdown options. You should have a sound play followed by the normal shutdown routine. Then when your computer starts back up, you will have a pleasant noise after logging on.
I hope that helped you! Please point out any errors that you see, and I'll correct them as soon as possible.

Nice tutorial. I was wondering, I noticed you have a games tab. Do you know how to properly execute games. I am trying to get steam games working also Call of duty 4 as tabs under obmenu. Could you help me out?
Thanks!

Installation of oracle 10g on RedHat Linux EE 3

Hi,
I am going to Install of oracle 10g on RedHat Linux EE 3, rigth now i am running oracle 9i on windows platform. I need following things:
-I want to export all my data from oracle 9i on windows. For this what is the best way should i transport my tablespace and install oracle 10g on linux and import them after creating db or should i simply export and import it from there.
-Is there any issues that i should look at before i transfer my database.
-We are a Industrial Laboratory and use scientific notation in our database. Would this import export can takecare of all the things or should i set some character set setting before import/export.
-Any thing else if you thing that i should take care.
Thanks & Regard
Rashid K.K

You cannot use transportable tablespace. Platform independent transportable tablespace run only on newer versions (10g). You have to create the tablespaces on you linux machine and than exp/imp (full=y).
Bye, Aron

10g RAC on Linux

All,
I am having strange problem while setting up 10g RAC on Linux box. This is two node cluster (rac1 and rac2) Two probelms..
1. When I install CRS on rac1, it copies the files to rac2 and olsnodes -n works fine from both nodes, But when I run runinstaller on node 2 and try to see installed products, I don't see CRS oracle home there on rac2.
2. When I start installing 10g database on rac1 , at third step "Hardware Cluster Installation Mode:" I see my both nodes listed there, but I don't see "SELECT ALL" button on that screen. So when I finish installation, it doesn't copy files to rac2.
Does Anyone has any idea why it is behaving like this?
Thanks
Puneet

Hi,
I found one thing.. If I change ORACLE_HOME location while running OUI, it doesn't give SELECT ALL button , but if I let Installer to select oracle_HOME, it worrks fine and give SELECT ALL button too.
Don't understand why it is behaving like this?
Puneet

10g RAC with linux 3 AS+ocfs

Hi:
Is anyone install 10g RAC on linux 3AS with ocfs successfully?
I am having problem with CRS installation where installer ask to run root.sh. My first node finished root.sh without any problem but not second node it give me "Failure at final check of Oracle CRS stack." error. Moreover, I found "ERROR: clssnmconnect: failed, rc = 3, node samurai (1), (ADDRESS=(PROTOCOL=tcp)(HOST=racs01-priv1)(PORT=49895))" error in ocssd2.log file. However, I can ping privet and public ip/hostname without any problem. Any input or suggestions are welcome!

Did you ever get a responce to this?
I'm having the very same issue, which I can not find a work around.
Documents for the 10g install have been very few and far between, so any help would be the greatest!

DB startup & shutdown in 10g DB on Linux

Similar Messages

Maybe you are looking for