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

Similar Messages

ORACLE DATABASE의 AUTOMATIC STARTUP/SHUTDOWN

제품 : ORACLE SERVER
작성날짜 : 1995-11-21
오라클 database의 AUTOMATIC STARTUP/SHUTDOWN
============================================
시스템이 startup 하면서 오라클도 함께 startup하거나 시스템을 shutdown
할 때 오라클도 같이 shutdown 하는 것이 가능하다. 그 방법은 OS마다 차이가
있는데 여기서는 UNIX 에 기반한 여러 플랫폼에 대해서 알아보기로 한다.
본 내용에서 가장 많이 사용되는 화일은 다음과 같다.
$ORACLE_HOME/bin/dbstart
$ORACLE_HOME/bin/dbshut
/etc/oratab 또는 /var/opt/oracle/oratab
dbstart 와 dbshut 은 오라클을 startup/shutdown 시키는 스크립트인데
이것은 automatic startup/shutdown 시에만 사용하도록 하고 평상 시의
경우에는 사용하지 않도록 한다.
oratab 화일은 일반 텍스트 화일로서 시스템에 설치된 오라클 인스턴스에
대한 정보를 가지고 있는데 보통 3개의 필드로 이루어져 있으며 첫번재
필드는 ORACLE_SID, 두번째 필드는 ORACLE_HOME, 세번째 필드는 Y 또는 N
으로 구성되어 있다. 해당 인스턴스를 autostartup 시키려면 꼭 Y로
세팅되어 있어야 한다.
SYSTEM V
System V 에 기반한 시스템은 /etc/rc<n>.d 디렉토리에 초기화 스크립트를
가지고 있다. 여기서 <n> 은 해당 스크립트의 run-level 을 의미한다.
일반적으로 run-level 0은 power shutdown mode 이고 run-level 2는 multi-user
mode 이다. 각각의 디렉토리에 들어있는 초기화 스크립트는 다음과 같은 형태의
이름을 갖고 있다.
K{two-digit number][descriptive filename]
예를 들면 S75cron, K30tcp 등이 있을 수 있다.
S로 시작되는 스크립트는 startup 시에 실행되는 것이고 K 로 시작하는 것은
shutdown 시에 실행된다.
two-digit number가 의미하는 것은 스크립트가 실행되는 순서인데 숫자가 작은
것부터 먼저 실행된다. 따라서 오라클 스크립트는 보통 다음과 같은 이름을 갖게 된다.
S99oracle, K01oracle
이와 같이 설정하면 시스템이 startup 될 때 모든 초기화가 끝난 후 마지막으로
오라클이 startup 되며 시스템을 shutdown 할 때에는 오라클을 가장 먼저 shutdown
하게 된다.
BSD UNIX
BSD 에 기반한 시스템은 시스템이 startup 될 때 초기화 화일로
/etc/rc*(예를 들면, /etc/rc, /etc/rc.local) 를 사용한다.
시스템을 shutdown 할 때에는 보통은 /etc/shutdown 만 실행하게 되므로
특별히 실행되는 스크립트가 없지만 /etc/rc.shutdown 이 실행되는
플랫폼도 있다.
이제 각 플랫폼별로 자세히 알아보기로 한다.
주의 : <oracle_owner> 는 oracle owner id 로 대체
<$ORACLE_HOME> 은 oracle home directory 명으로 대체
(1)SunOS 4.1.3
SunOS 4.1.3 에서는 /etc/rc.local 을 startup 스크립트로 사용한다. 즉
시스템이 startup 되면서 /etc/rc.local 이 실행된다. 따라서 이 화일의 끝에
다음과 같은 라인을 추가하면 된다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
예를 들어 oracle owner 가 oracle7 이고 $ORACLE_HOME 이 /home/oracle
이라면 다음과 같이 해주면 된다.
su oracle7 -c /home/oracle/bin/dbstart
여기서 /home/oracle 대신에 $ORACLE_HOME 과 같은 환경변수를 이용하여
세팅하면 안된다.
SunOS 에서는 시스템이 shutdown 될 때 실행되는 스크립트는 따로 없다.
따라서 dbshut 을 실행시키는 방법은 다음과 같은 스크립트를 만들어서
시스템을 shutdown 시킬 때 /etc/shutdown 을 실행시키지 말고 대신
이것을 실행시켜야 한다.
#!/bin/csh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
만약 오라클을 shutdown 하지 않고 시스템을 shutdown 하면 다음에
오라클을 startup 하려고 할 때 startup이 되지 않는다. 이 경우에는
$ORACLE_HOME/dbs/sgadef<SID>.dbf 화일을 지우고 startup 시키면 된다.
(2)OSF/1(DIGITAL UNIX)
/etc/inittab : 초기화 과정을 콘트롤
/sbin/rc3 : run-level 3 에서 사용되는 script
/sbin/rc0 : run-level 0 에서 사용되는 script
/sbin/rc3.d/S99oracle : /sbin/init.d/oracle 로 link
/sbin/rc0.d/K01oracle : /sbin/init.d/oracle 로 link
/etc/initab 화일에는 초기화 과정에 대한 정보가 들어 있다.
예를 들면 다음과 같다.
s3:3:wait:/sbin/rc3 < /dev/console > /dev/console 2>&1
이렇게 설정하면 run-level 3 일 경우 /sbin/rc3 스크립트가 실행된다.
/sbin/rc3 은 /sbin/rc3.d 디렉토리에 들어있는 스크립트를 실행한다. 만약
스크립트 이름이 K 로 시작하면 이것은 stop 파라미터를 갖고 실행되어서 이
스크립트에 지정된 프로세스를 정지시킨다. 한편, 스크립트가 S 로 시작하면
/sbin/rc3 는 이 스크립트에 startup 파라미터를 부여하고 여기서 지정된
프로세스를 실행시킨다. 따라서 /sbin/rc3.d/S99oracle 을 사용하여
dbstart를 실행한다.
shutdown 과정도 거의 비슷하다. /etc/inittab 에 다음과 같은 라인을 추가
한다.
s0:0:wait:/sbin/rc0 off < /dev/console > /dev/console 2>&1
이것은 /sbin/rc0 를 실행시키는데 /sbin/rc0 는 /sbin/rc0.d 디렉토리에
들어있는 스크립트를 실행시킨다. 스크립트의 이름이 S 로 시작하면 run
time parameter 로 start 를 사용하게 되고 K 로 시작하면 stop 을
사용한다.
따라서 /sbin/rc0.d/K01oracle 스크립트는 stop 파라미터를 갖고
실행되며 이 스크립트는 $ORACLE_HOME/bin/dbshut 스크립트를 실행시켜서
오라클을 shutdown 시킨다.
/sbin/rc3.d/S99oracle과 /sbin/rc0.d/K01oracle은 모두 /sbin/init.d/oracle
에 대한 symbolic link 이다. /sbin/init.d/oracle 에 대한 symbolic link 는
이들 외에 더 있을 수 있다.
(3)Solaris 2.3 & SCO UNIX
/etc/inittab : 초기화 과정을 콘트롤
/etc/rc2 : run-level 2 에서 사용되는 스크립트
/etc/rc0 : run-level 0 에서 사용되는 스크립트
/etc/rc2.d/S99dbstart : /etc/init.d/dbstart 에 대한 link
/etc/rc0.d/K01dbshut : /etc/init.d/dbshut 에 대한 link
/var/opt/oracle/oratab
Solaris 의 경우는 OSF/1 과 매우 유사하다. 차이점이라고 한다면 /sbin
디렉토리 대신에 /etc 디렉토리에 필요한 스크립트가 들어있다는 것이다.
rc0.d, rc2.d 같은 디렉토리는 실제로 /etc 디렉토리에 위치하고 있으며
rc0, rc2 와 같은 스크립트는 /etc/init.d 에 존재하는 같은 이름의 스크립트에
대한 symbolic link이다.
/etc/init.d/dbstart 와 /etc/init.d/dbshut 스크립트의 내용은 각각 다음과
같이 한줄로 구성되어 있다.
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
Solaris 에서는 start, stop 같은 파라미터는 /etc/init.d/dbstart,
/etc/init.d/dbshut 에서는 무시된다.
/etc/init.d/dbstart, /etc/init.d/dbshut 화일은 owner가 oracle owner id
이여야 한다.
/etc/init.d/README 를 읽어보면 좀 더 자세한 내용이 설명되어 있으니 참조하기
바란다.
(4)AIX
/etc/inittab : 시스템 초기화 화일
/etc/rc : 시스템 초기화 스크립트
/etc/mkitab : /etc/inittab 을 수정하는 유틸리티
/etc/shutdown : 시스템 shutdown 스크립트
AIX 에서는 오라클 autostartup 방법은 여러가지가 가능하지만 shutdown 은
한가지만 가능하다. 우선 autostartup 은 다음과 같은 방법 가운데 하나를
사용하면 된다.
a)/etc/mkitab 를 사용하여 /etc/inittab 에 entry 를 추가한다. 즉,
/etc/mkitab "<oracle_owner>:2:wait:/bin/su <oracle_owner> -c
<$ORACLE_HOME>/bin/dbstart > /dev/console 2>&1"
이렇게 하면 /etc/inittab 화일에 dbstart 기능이 추가된다. 이렇게 하면
시스템이 뜨면서 run-level 2일 경우 오라클이 자동으로 startup 된다.
b)다음과 같은 방법도 가능하다.
/etc/mkitab "rcoracle:2:wait:/etc/rc.oracle > /dev/console 2>&1"
그리고, root 소유의 /etc/rc.oracle 스크립트를 다음과 같이 작성한다.
su <oracle_owner> <<EOF
<$ORACLE_HOME>/bin/dbstart
EOF
c)/etc/rc 스크립트의 마지막에 다음을 추가한다.
/bin/su <oracle_owner> - c <$ORACLE_HOME>/bin/dbstart
AIX 에서 시스템 shutdown 은 /etc/shutdown 에 의한다. 시스템을 내릴 때
오라클을 shutdown 하려면 별도의 시스템 shutdown 스크립트(root 소유로)를
다음과 같이 만들어서 /etc/shutdown 을 사용하지 말고 이것을 사용해야 한다.
#!/bin/sh
/bin/su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
/etc/shutdown $*
(5)HP/UX
/etc/rc : 시스템 startup 화일
/etc/shutdown : 시스템 shutdown 실행 화일
/etc/shutdown.d : 시스템 shutdown 디렉토리
HP/UX 에서는 시스템 startup 시에 /etc/rc 가 실행된다. 따라서 다음 라인을
/etc/rc 스크립트의 마지막에 추가하면 auto startup 이 가능해진다.
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
시스템의 shutdown 은 /etc/shutdown 화일을 실행하여 수행된다. 이 프로그램은
/etc/shutdown.d 디렉토리에 들어있는 스크립트를 실행시키는데 다음과 같은
세 가지 방법 가운데 하나로 auto shutdown 을 세팅할 수 있다.
a)$ORACLE_HOME/bin/dbshut 화일을 /etc/shutdown.d 디렉토리 아래에 copy
b)/etc/shutdown.d/dbshut 을 $ORACLE_HOME/bin/dbshut 으로 symbolic link 지정
c)다음과 같은 스크립트 작성
#!/bin/sh
su <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
단,이 스크립트는 root의 소유이고 root에 의해서만 실행 가능해야 한다.
만약 V6 와 V7 을 동시에 사용하는 경우라면 V7 에서 제공하는 dbshut을
사용하도록 한다.

Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps!

Oracle 8i Automatic Startup/shutdown on NT

After installing Oracle 8.1.6 on Win NT/2000 and creating a database a new service is created too (OracleServiceSID). My problem is that this new service (which works like oradim starting srvc,inst) does not startup the db when rebooting the machine. I need always manual startup/shutdown with a script that uses svrmgrl while in Oracle guides it seems that would be enough to start the service. Every parameter in the registry is set according to these guides to permit automatic startup/shutdown but only the service, not the db, starts and stops automatically. Where is my error?
Thanks
Alex
null

Dear Alexdelarg,
First launch the "Services" applet from the Windows NT Control Panel. Double-click on the "OracleService<SID>" service and verify that "Startup Type" is set to "Automatic", "Log On As" is set to "System Account", and that the "Allow Service to Interact with Desktop" check box is disabled.
Then launch REGEDIT and check that the Value String ORA_<SID>AUTOSTART within the key My Computer\HKEYLOCAL_MACHINE\SOFTWARE\ORACLE is set to "TRUE".
If the above does not rectify your startup problem, try issuing the following command from the Command Prompt:
<ORACLE_HOME>\bin\oradim -edit -sid <SID> -startmode auto
where <ORACLE_HOME> is the full path of your Oracle8i Server software and <SID> is the Service Identifier of your database.
Hope this helps!

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

Oracle Automatic Startup & Shutdown

My automatic Database startup/Shutdown script won't work while system reboot. I have Oracle 8.1.7/Sun solaris. When I ran the script by hand it works fine both for startup and shutdown but not while system reboot. I am putting the script in the proper run levels rc0.d and rc3.d.
even /etc/rc0.d/K01oracle and /etc/rc3.d/S90oracle is working fine.
Could someone please tell me what am i missing.
Appreciate your help
-Jay

Hi,
Have you settled your issue? I would think the problem was caused by the environment under which the script was run. Normally the rc scripts are run as root and the PATH will not be set to run Oracle executables. So inside the script if you run the startup script as the user who has execute permission to the Oracle executables and whose path is SET in .profile then it should work.

Automate startup/shutdown thru script on windows

WIndows 2003
oracle 9.2.0.7
I am new to oracle on windows.
Is there way to automated startup/shutdown database thru script on windows?
I want to schedule this task at perticuler time.
Thanks

You have to come up with your own script to shutdown.
There's a sample here
[Start / Shut Oracle with a Click (Windows Script) |http://it.toolbox.com/wiki/index.php/Start_/_Shut_Oracle_with_a_Click_(Windows_Script)]
Edited by: yingkuan on Oct 9, 2008 5:05 PM

Automatic startup/shutdown failed. Running the script manual..works...

Hi,
DB: Oracle9i
Os: solaris 9
/etc/rc0.d K05oracle -> /etc/init.d/oracledb
/etc/rc3.d SS85oracle -> /etc/init.d/oracledb
Oratab: i have put yes.
Please help to resolve this issue...where can i check the startup log?
what else i need to check?
Thanks,
Siva.

Thanks for your reply....
Script:
#!/bin/sh
case "$1" in
'start')
# Sets ORACLE_HOME to latest version on machine
# ORACLE_HOME="`cut -d ":" -f 2 /var/opt/oracle/oratab | sort | tail -1`"
ORACLE_HOME=`grep -v "^#" /var/opt/oracle/oratab|grep -v "^$"|cut -d ":" -f 2 | sort | tail -1`
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME:$ORACLE_HOME/bin
# If you are running Oracle's Multi-Threaded Server, the SQL*Net
# listener service must be started before the database is started.
# If it is not, your dispatcher(s) will not start.
if [ -f $ORACLE_HOME/bin/dbstart ]
then
echo "Starting up Oracle databases."
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/lsnrctl start"
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/dbstart"
else
echo "Can't find Oracle startup file."
fi
'stop')
# Sets ORACLE_HOME to latest version on machine
ORACLE_HOME="`cut -d ":" -f 2 /var/opt/oracle/oratab | sort | tail -1`"
export ORACLE_HOME
PATH=$PATH:$ORACLE_HOME:$ORACLE_HOME/bin
if [ -f $ORACLE_HOME/bin/dbshut ]
then
echo "Shutting down Oracle databases."
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/dbshut"
su oracle -c "LD_LIBRARY_PATH=$ORACLE_HOME/lib;export LD_LIBRARY_PATH;$ORACLE_HOME/bin/lsnrctl stop"
else
echo "Can't find Oracle shutdown file."
fi
echo "Usage: /etc/init.d/database { start | stop }"
esac

Oracle 10g automatic startup in Solaris 10

Good afternoon,
I've installed Oracle 10g Enterprise Edition Server on a server with Solaris 10. I'm trying to configure the automatic startup/shutdown. I've changed dbstart script. I've prepared dbora script and I've created the necessary link to this script in the rc*.d directories.
When I launch dbora start or dbora stop everything is ok, but when I reboot my machine nothing happens.
My dbora script is as follow:
#!/bin/sh
ORA_HOME=/u01/app/oracle/product/10.2.0/Db_1
ORA_OWNER=oracle
if[ ! -f $ORA_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start')
su - $ORA_OWNER -c "ORA_HOME/bin/dbstart"
su - $ORA_OWNER -c "ORA_HOME/bin/emctl start dbconsole"
su - $ORA_OWNER -c "ORA_HOME/bin/isqlplusctl start"
'stop')
su - $ORA_OWNER -c "ORA_HOME/bin/isqlplusctl stop"
su - $ORA_OWNER -c "ORA_HOME/bin/emctl stop dbconsole"
su - $ORA_OWNER -c "ORA_HOME/bin/lsnrctl stop"
su - $ORA_OWNER -c "ORA_HOME/bin/dbshut"
esac
Thanks in advance.
Best regards,
Mabel

I think that I've found the problem but I need your help. The problem is related to the listener. The file listener.ora doesn't exist!!! In fact the listener starts perfectly when I type the command lsnrctl start, but I don't understand why this file doesn't appear :-O. And of course neither the file sqlnet.ora exists.
I've create these files and I'm going to check. But could you tell how to configure sqlnet.ora to get the file listener.trc?
Thanks in advance.
Regards,
Mabel

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/]

How to startup/shutdown bootcamp automatic

Hi, is it possible to startup/shutdown bootcamped windows7 automatic/ after schedule?

It's possible but would require scheduling on both operating systems. You can write the boot drive to NVRAM and issue a reboot. That would start windows, what happens there would be controlled by windows. Inside windows you can automate using the control panel to select the mac boot drive and again, issue a reboot.
I think it would be more robust to have a small winbox running 24/7 than try to cobble together something that complicated on a single mac. There must be a reason behind your request. What is the reason, maybe there's another way to achieve the goal.

Automate BIP Startup/Shutdown with OMS

Is there any way to automate the startup/shutdown of BI Publisher when the OMS is started/stopped? This would really come in handy instead of manually having to start/stop these components.
Thanks,
Leighton

Current release does not have auto stop/start of BIP when OMS is bounced.

9iAS R2 Automatic Startup at Boot time on Windows

How to successfully start the 9iAS R2 Application Server at boot time.
Many of you are still struggling with the problem of 9iAS R2 not automatically starting up properly when your system is restarted. I've been fighting this issue for several weeks and have found the problems, and pitfalls, involved with fixing it. It really is a race condition of things trying to start up before something it depends on is fully functioning, or some application starting out of sequence.
There is a bug associated with this problem; BUG 2511270 ( 9IASV2 Need Ability to Restart All Components in Instance After a Reboot). The bug report itself has very little useful information in it other than to say it doesn't work, and manually starting the components is the only known fix. If you're like me. this isn't a good enough answer.
Your mileage may vary.
My configuration has a 9.2.0.1 customer database, and a 9.0.1.3.1 infrastructure database that is also the application server database, including portals, all installed on the same system which is a Pentium 4, Windows 2000 machine, with 1.5GB of memory. I only use a single LISTENER, which runs out of the 9.2 DB ORACLE_HOME.
Chapter 5 (Starting and Stopping the Application Server) of the Oracle9i Application Server Administrator's Guide shows all of the commands necessary, in the proper order, to manually start the infrastructure and application server. Unfortunately, there is also some incorrect information in this document.
Part 1c in the section Starting an Infrastructure Using Commands on Windows, using SQLPlus to connect to and start the database, does not work unless oracle.exe is already running (which means that you recently shutdown the database by command, not with "services>stop"). If your system is rebooting, oracle.exe is not running. This exact same information is documented in the Database Administrators Guide, Chapter 4, Starting a Database. If you don't have these manuals handy the offending commands are as follows:
ORACLE_HOME\bin\sqlplus /nologsql> connect sys/password_for_sys as sysdba
sql> startup
sql> quit
Since we can't put some variant of the above in a command script to manually start the databases and wait for it to open, the only option left is to let the databases come up in "automatic" mode when the system boots, and run the remaining commands when they are open. If your system is like mine, that can take several minutes, even after you've logged on and gotten your first cup of coffee.
If you set up a command script to run at startup, you don't have any control over when the script gets run, more than likely, in this case, before the databases are open. Unfortunately, Microsoft does not have anything resembling a sleep (timer, wait, delay, etc) command that can be used in a script. There may be something somewhere, but I can't find it. So I wrote one in Perl, which does have a sleep command. You can use anything you have available to you that will function as needed. We obtained our Perl distribution from http://aspn.activestate.com/ASPN/Perl.
The next issue has to do with starting the Oracle Internet Directory. The documentation shows two commands to execute, but in reality, only the first one is required, it automatically takes care of the second one. Refer to the command file below for the correct one.
The last issue deals with running the dcmctl commands. If you run these commands one at a time in a command window, you won't notice anything askew. If you run them, as shown, in a script, they will stop execution of the script when they complete, and there will be no indication that anything wrong has happened. The CMD.exe still exists, it just isn't running. They must be run in there own cmd command as shown below.
Now, let's review the steps necessary to get all this to work.
Put the two scripts shown below in there target directories and edit any necessary changes for your system.
In Start>Settings>Control Panel>Administrative Tools>Services set the OracleServiceSID's and the OracleOraHomeTNSListener to Automatic Startup Type. All other Oracle* services should be set to Manual.
In Start>Programs>Accessories>System Tools>Scheduled Tasks double click on the Add Scheduled Task item,
select Next,
Browse to where your startup script resides,
double click the file name,
select "When my computer starts",
select Next,
Enter a user name and password (that has ORA_DBA privileges)
select Next, then Finish.
Uncomment the first exit in the iasStartup.cmd script.
Reboot your system.
Compare the database open time stamp in each database alert log to the time recorded in the iasStartup.log file to determine you first time delay. Add 10-20 seconds or more to this difference just to be safe. If you add services at a later time, this number may need to be increased.
Edit the iasStartup.cmd file to include this time delay for the first sleep command and comment out the first exit command.
Reboot your system.
After several minutes, all infrastructure and application server processes should be up and running. You can check this in several ways; Look at the log file to see if all commands were run, Look at the Windows Task Manager to see if all expected tasks are running, Look at Services to see what is running. Finally, you can look at the Infrastructure Enterprise Manager Website and click on each instance to determine the current status of each system component. On mine, the component Portal:portal:7779 always shows as down but in reality it is functioning.
The following command script only starts the minimum set of processes that I require. Your requirements may be different so refer to the documentation for additional commands.
Enjoy.
******** iasStartup.cmd ********
REM # iasStartup.cmd
REM # Command script to start the infrastructure and application server at system boot
REM # Mike Bukaty
REM # Sandia National Laboratories
REM # [email protected]
REM # set default directory that contains the log and sleep.pl files.
cd E:\Oracle\admin
echo Starting iasStartup.cmd > iasStartup.log
time /t >> iasStartup.log
REM # Uncomment the following command to determine the time delay for your system
REM # exit
REM # This delay is determined by looking at the times from the alert logs
REM # for when the database was opened and the time recorded above.
REM # SLEEP is a perl script to do just that (in seconds) since Windows doesn't have one.
sleep.pl -delay=120
time /t >> iasStartup.log
REM #Start the infrastructure first
REM #The SID for the infrastructure must be set
set ORACLE_HOME=E:\Oracle\as9inf
set ORACLE_SID=iasdb
echo Starting as9inf oidmon >> iasStartup.log
%ORACLE_HOME%\bin\oidmon start
echo Starting as9inf EMWebsite >> iasStartup.log
net start Oracleas9infEMWebsite
REM # Have to wait for all of the website process to finish
sleep.pl -delay=40
REM # All calls to dcmctl must be in there own CMD environment,
REM # or they will halt this one when they complete
echo Starting as9inf dcmctl ohs >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct ohs
sleep.pl -delay=5
echo Starting as9inf dcmctl OC4J_DAS >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -co OC4J_DAS
REM # Start the application server
set ORACLE_HOME=E:\Oracle\ora9ias
echo Starting ora9ias webcachectl >> iasStartup.log
%ORACLE_HOME%\bin\webcachectl start >> iasStartup.log
echo Starting ora9ias dcmctl ohs >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct ohs
sleep.pl -delay=10
echo Starting ora9ias dcmctl OC4J >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl start -ct OC4J
REM # The above command starts all existing OC4J processes.
REM # You can now stop any that aren't necessary.
echo Stopping ora9ias dcmctl OC4J_Demos >> iasStartup.log
cmd /c %ORACLE_HOME%\dcm\bin\dcmctl stop -co OC4J_Demos
time /t >> iasStartup.log
echo Finished iasStartup.cmd >> iasStartup.log
exit
******** sleep.pl ********
#!/usr/local/bin/perl
## Author: Mike Bukaty
## Sandia National Laboratories
## [email protected]
## Program: sleep.pl
$| = 1;
use strict;
use Getopt::Long;
Getopt::Long::Configure("no_ignore_case");
GetOptions(
"delay=s" => \ my $delay,
# Set default options
if( not defined($delay) ) { $delay = 1; }
sleep $delay;
exit 1;

New information:
When I originally wrote this, the command script worked as advertised. That was yesterday. I've since had to add the following lines just BEFORE the call to start the oidmon.
echo Starting as9inf oidctl >> iasStartup.log
%ORACLE_HOME%\bin\oidctl server=oidldapd configset=0 instance=1 start
Sometimes me thinks that Oracle reconfigures itself at night when I'm not watching.
Enjoy.

Oracle 8.1.6 autimatic startup/shutdown on sparc solaris 8

I tried to setup a script in /etc/init.d that should call dbstart to auto-start my DB when I boot my sparc solaris 8 server. I tried to run it in rc3 and then in rc2 to no avail. I'd like to know how to setup the server to automatically startup oracle on boot and automatically stop it on shutdown... Can anyone help please?

Could you tell us how to do that????
We all met the ORA-01034 problem!
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Wile E. Coyote:
Yes, that's no problem
I've installed 8.1.6 on several machines running Solaris 8 without any problem<HR></BLOCKQUOTE>
null

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

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

Similar Messages

Maybe you are looking for