AIX 6.1 Auto Startup / Shutdown Oracle

Hello,
I'm fairly new to Oracle and AIX so bear with me, the newbie. I have a AIX 6.1 blade running Oracle 11g (11.1.0.6) and I'm trying to automate the database startup and shutdown procedure as outlined in the Admin Reference for Linux and Unix.
I have 7 databases running on this one machine. I have started on page 2-7, mofified the oratab file to include a Y at the end of each entry, then i have created the dbora file with the oracle_home and oracle=user parameters.
In trying to troubleshoot, I did noticed that there is a shutdown.log file in the ORACLE_HOME folder but no startup.log...
Any ideas on what / where to check?
Thanks

Probably this would help,
http://oracle-base.com/articles/linux/AutomatingDatabaseStartupAndShutdownOnLinux.php
HTH
Aman....

Similar Messages

  • (V7.3 ~ V8.X) ORACLE DB AUTO STARTUP/SHUTDOWN ON SUN SOLARIS 2.6/2.7

    제품 : ORACLE SERVER
    작성날짜 : 2003-06-02
    (V7.3 ~ V8.X) ORACLE DB AUTO STARTUP/SHUTDOWN ON SUN SOLARIS 2.6/2.7
    ====================================================================
    PURPOSE
    이 자료는 O/S startup 시에 Oracle RDBMS 서비스를 자동으로 startup하
    는 방법에 대한 자료이다.
    Explanation
    sun solaris 부팅 시 oracle DB를 auto startup하도록 하는 데 관련된 화일들이다.
    /etc/inittab : o/s의 초기화 과정을 조절하는 화일
    /etc/rc2 : 부팅 run-level 2 에서 사용되는 스크립트
    /etc/rc0 : 부팅 run-level 0 에서 사용되는 스크립트
    /etc/rc2.d/S99dbstart : /etc/init.d/dbstart 에 대한 symbolic link
    /etc/rc0.d/K01dbshut : /etc/init.d/dbshut 에 대한 symbolic link
    /var/opt/oracle/oratab : 시스템에 설치된 오라클 인스턴스에 대한 정보.
    (참고)
    /etc/init.d/dbstart, dbshut 화일은 super user(root)로 생성하시고,
    symbolic link도 super user로 만드시기 바랍니다.
    이 화일들은 super user가 owner가 되도록 하고, super user(root)만이
    실행 가능하도록 해야 합니다.
    1. 먼저 vi /etc/inittab 화일을 열어보십시오.
    ap::sysinit:/sbin/autopush -f /etc/iu.ap
    fs::sysinit:/sbin/rcS >/dev/console 2>&1 </dev/console
    is:3:initdefault:
    p3:s1234:powerfail:/usr/sbin/shutdown -y -i5 -g0 >/dev/console 2>&1
    s0:0:wait:/sbin/rc0 >/dev/console 2>&1 </dev/console
    s1:1:wait:/usr/sbin/shutdown -y -iS -g0 >/dev/console 2>&1 </dev/console
    s2:23:wait:/sbin/rc2 >/dev/console 2>&1 </dev/console
    s3:3:wait:/sbin/rc3 >/dev/console 2>&1 </dev/console
    s5:5:wait:/sbin/rc5 >/dev/console 2>&1 </dev/console
    s6:6:wait:/sbin/rc6 >/dev/console 2>&1 </dev/console
    fw:0:wait:/sbin/uadmin 2 0 >/dev/console 2>&1 </dev/console
    of:5:wait:/sbin/uadmin 2 6 >/dev/console 2>&1 </dev/console
    rb:6:wait:/sbin/uadmin 2 1 >/dev/console 2>&1 </dev/console
    sc:234:respawn:/usr/lib/saf/sac -t 300
    co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login: " -T
    sun
    -d /dev/console -l console -m ldterm,ttcompat
    s1부터 s6까지 os file들에 대해 위와 같이 device redirection이 연결되어
    있으면 됩니다.
    s2:23:wait:/sbin/rc2 >/dev/console 2>&1 </dev/console
    위와 같이 설정하면 run-level 2일 경우 /sbin/rc2 스크립트가 실행된다.
    /sbin/rc2 는 /etc/rc2.d 디렉토리에 들어있는 스크립트를 실행한다.
    만약 스크립트가 S 로 시작하면 /sbin/rc2 는 이 스크립트에 startup 파라미
    터를 부여하고 여기서 지정된 프로세스를 실행시킨다.
    따라서 /etc/rc2.d/S99dbstart 화일을 사용하여 dbstart를 실행한다.
    shutdown 과정도 거의 비슷하다. /etc/inittab 에 다음과 같은 라인을 보자.
    s0:0:wait:/sbin/rc0 >/dev/console 2>&1 </dev/console
    이것은 /sbin/rc0 를 실행시키는데 /sbin/rc0 는 /etc/rc0.d 디렉토리에
    들어있는 스크립트를 실행시킨다.
    스크립트 이름이 K 로 시작하면 이것은 stop 파라미터를 갖고 실행되어서 이
    스크립트에 지정된 프로세스를 정지시킨다.
    따라서 /etc/rc0.d/K01dbshut 스크립트는 stop 파라미터를 갖고 실행되며
    이 스크립트는 $ORACLE_HOME/bin/dbshut 스크립트를 실행시켜서 오라클을
    shutdown 시킨다.
    2. 그 다음에 vi /etc/rc2 화일을 한번 열어보세요.
    이 스크립트 화일은 run-level 2에서 사용되는 스크립트입니다.
    특별히 수정할 내용은 없으나, 이 화일이 존재하는지 확인해 보십시오.
    PATH=/usr/sbin:/usr/bin
    set `/usr/bin/who -r`
    if [ x$9 = "xS" -o x$9 = "x1" ]
    then
    echo 'The system is coming up. Please wait.'
    BOOT=yes
    3. 그 다음에 vi /etc/rc0 화일을 한번 열어보세요.
    이 스크립트 화일은 run-level 0에서 사용되는 스크립트입니다.
    특별히 수정할 내용은 없으나, 이 화일이 존재하는지 확인해 보십시오.
    PATH=/usr/sbin:/usr/bin
    echo 'The system is coming down. Please wait.'
    # make sure /usr is mounted before proceeding since init scripts
    # and this shell depend on things on /usr file system
    /sbin/mount /usr > /dev/null 2>&1
    # The following segment is for historical purposes.
    # There should be nothing in /etc/shutdown.d.
    if [ -d /etc/shutdown.d ]
    then
    for f in /etc/shutdown.d/*
    if [ -s $f ]
    then
    /sbin/sh ${f}
    fi
    fi
    4. /etc/init.d/dbstart 와 /etc/init.d/dbshut 스크립트를 만들어야 합니다.
    그 내용은 각각 다음과 같이 한 줄로 작성합니다.
    /etc/init.d/dbstart 화일은 다음과 같이 만듭니다.
    su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbstart
    /etc/init.d/dbshut 화일은 다음과 같이 만듭니다.
    su - <oracle_owner> -c <$ORACLE_HOME>/bin/dbshut
    5. /etc/rc2.d/S99dbstart 화일을 /etc/init.d/dbstart에 대한 link로 생성합니다.
    ln -s /etc/init.d/dbstart /etc/rc2.d/S99dbstart
    6. /etc/rc0.d/K01dbshut 화일을 /etc/init.d/dbshut에 대한 link로 생성합니다.
    ln -s /etc/init.d/dbshut /etc/rc0.d/K01dbshut
    7. /var/opt/oracle/oratab 화일을 엽니다.
    oratab 화일은 일반 텍스트 화일로서 시스템에 설치된 오라클 인스턴스에 대한
    정보를 가지고 있는데 보통 3개의 필드로 이루어져 있으며,
    첫번재 필드는 ORACLE_SID, 두번째 필드는 ORACLE_HOME, 세번째 필드는 Y 또는
    N으로 구성되어 있습니다. 해당 인스턴스를 auto startup 시키려면 세번째
    필드가 반드시 Y로 세팅되어 있어야 합니다.
    아래에 예를 참조하세요.
    ORA805:/oracle4/ora8/app/oracle/product/8.0.5:Y
    ORA815:/oracle4/ora8i/app/oracle/product/8.1.5:Y
    (주)
    만약, <$ORACLE_HOME>/bin/dbstart 수행에 오류가 있으면 기존의 dbstart 화
    일을 다른 path에 rename하고, 아래 내용만 가지고 <$ORACLE_HOME>/bin/ 아래
    에 dbstart 화일을 다음과 같이 만든다.
    svrmgrl <<EOF
    connect internal
    startup
    exit
    EOF
    Example
    none
    Reference Documents
    none

    Hi Frank,
    This is a bug in 9.0.1. It is fixed in 9.2 and
    backported to 9.0.1.2 (rdbms 9.0.1.2 patch). Note that you
    need to specify the sdo_indx_dims=2 in the parameter clause.
    As a workaround in 9.0.1.0 you could do:
    (1) remove the z coordinate (as you mentioned),
    (2) set the srid to null (instead of 8307) both in
    the geometries as well as the index metadata,
    (3) set geodetic=false in the create-index parameters.
    Hope that helps,
    Ravi.

  • Startup / Shutdown Oracle R12 EBS Linux Server How To?

    Hi All,
    I finally have a linux box (x86) running with the R12 EBS.
    Now, I wanted to get some input if I shut down this box when not in use, what is the best way to do that?
    And when I restart, what is the best way to kick it up so its up and running again.
    Basically - need some input on what measures to take and which commands to run.
    Thanks!

    This is the results from:
    /d01/oracle/VIS/db/tech_st/11..1.0/lib
    [oravis@oracle lib]$ ls -lrt
    total 550872
    -rw-r--r-- 1 oravis dba 56899 Sep 25 2000 jdev-rt.zip
    -rw-r--r-- 1 oravis dba 280984 Oct 23 2001 mail.jar
    -rw-r--r-- 1 oravis dba 45386 Oct 23 2001 activation.jar
    -rw-r--r-- 1 oravis dba 139516 Jun 5 2003 xmldemo.jar
    -rw-r--r-- 1 oravis dba 232488 May 23 2005 http_client.jar
    -rw-r--r-- 1 oravis dba 142 Oct 17 2005 credentials.reg
    -rw-r--r-- 1 oravis dba 103 Oct 17 2005 clusters.reg
    -rw-r--r-- 1 oravis dba 37948 Jun 9 2006 jcr-1.0.jar
    -rw-r--r-- 1 oravis dba 2702 Sep 19 2006 fetchlets.reg
    -rw-r--r-- 1 oravis dba 7370 Jan 17 2007 asmcmd_disk_header_format
    -rw-r--r-- 1 oravis dba 11701 Jun 4 2007 asmcmdglobal.pm
    -rwxr-xr-x 1 oravis dba 253559 Jul 10 2007 libexpat.so.0.5.0
    -rwxr-xr-x 1 oravis dba 253559 Jul 10 2007 libexpat.so.0
    -rwxr-xr-x 1 oravis dba 253559 Jul 10 2007 libexpat.so
    -rwxr-xr-x 1 oravis dba 743 Jul 10 2007 libexpat.la
    -rwxr-xr-x 1 oravis dba 442746 Jul 10 2007 libexpat.a
    -rw-r--r-- 1 oravis dba 388 Aug 3 2007 recvlets.reg
    -rw-r--r-- 1 oravis dba 179758 Sep 5 2007 libocijdbc11.so
    -rw-r--r-- 1 oravis dba 15505 Sep 5 2007 libheteroxa11.so
    -rw-r--r-- 1 oravis dba 423502 Sep 8 2007 libirc.a
    -rw-r--r-- 1 oravis dba 26086 Sep 8 2007 libipgo.a
    -rw-r--r-- 1 oravis dba 4351658 Sep 8 2007 libimf.a
    -rw-r--r-- 1 oravis dba 3848 Sep 8 2007 libcxaguard.so.5
    -rw-r--r-- 1 oravis dba 394232 Sep 9 2007 ojcr.jar
    -rw-r--r-- 1 oravis dba 83020 Sep 21 2007 asmcmdshare.pm
    -rw-r--r-- 1 oravis dba 13159 Oct 4 2007 libskgxn2.so
    -rw-r--r-- 1 oravis dba 0 Oct 14 2007 libclntst11.a
    -rw-r--r-- 1 oravis dba 3098 Nov 16 2007 facility.lis
    -rw-r--r-- 1 oravis dba 24240 Dec 7 2007 libslax11.a
    -rw-r--r-- 1 oravis dba 71767 Feb 6 2008 asmcmddisk.pm
    -rw-r--r-- 1 oravis dba 167306 Mar 28 2008 asmcmdbase.pm
    -rw-r--r-- 1 oravis dba 38 Jul 31 2008 sysliblist
    -rw-r--r-- 1 oravis dba 330384 Aug 6 2008 libwwg.a
    -rw-r--r-- 1 oravis dba 56782 Aug 18 2008 asmcmdambr.pm
    -rw-r--r-- 1 oravis dba 12514 Aug 26 2008 libOsUtils.so
    -rw-r--r-- 1 oravis dba 1440458 Aug 27 2008 libldapclnt11.a
    -rw-r--r-- 1 oravis dba 39208 Aug 27 2008 libldapjclnt11.a
    -rw-r--r-- 1 oravis dba 74594 Aug 27 2008 libzt11.a
    -rw-r--r-- 1 oravis dba 2713966 Aug 27 2008 libztkg11.a
    -rw-r--r-- 1 oravis dba 11899122 Aug 27 2008 libnnz11.a
    -rw-r--r-- 1 oravis dba 8387704 Aug 27 2008 libnnz11.so
    -rw-r--r-- 1 oravis dba 188108 Aug 27 2008 libowm2.so
    -rw-r--r-- 1 oravis dba 133781 Aug 27 2008 libldapjclnt11.so
    -rw-r--r-- 1 oravis dba 808740 Aug 27 2008 libordim11.a
    -rw-r--r-- 1 oravis dba 203610 Aug 27 2008 libordimt11.a
    -rw-r--r-- 1 oravis dba 584320 Aug 27 2008 libordim11.so
    -rw-r--r-- 1 oravis dba 193150 Aug 27 2008 xsu12.jar
    -rw-r--r-- 1 oravis dba 3567 Aug 27 2008 xsqlserializers.jar
    -rw-r--r-- 1 oravis dba 131646 Aug 27 2008 xschema.jar
    -rw-r--r-- 1 oravis dba 1436312 Aug 27 2008 xmlparserv2.jar
    -rw-r--r-- 1 oravis dba 646807 Aug 27 2008 xmlmesg.jar
    -rw-r--r-- 1 oravis dba 565119 Aug 27 2008 xml.jar
    -rw-r--r-- 1 oravis dba 92141 Aug 27 2008 xmlcomp.jar
    -rw-r--r-- 1 oravis dba 11114 Aug 27 2008 xmlcomp2.jar
    -rw-r--r-- 1 oravis dba 117441 Aug 27 2008 transx.zip
    -rw-r--r-- 1 oravis dba 148664 Aug 27 2008 oraclexsql.jar
    -rw-r--r-- 1 oravis dba 36686 Aug 27 2008 classgen.jar
    -rw-r--r-- 1 oravis dba 5578314 Aug 27 2008 libordsdo11.a
    -rw-r--r-- 1 oravis dba 2050282 Aug 27 2008 libsqlplus.a
    -rw-r--r-- 1 oravis dba 1481762 Aug 27 2008 libsqlplus.so
    -rw-r--r-- 1 oravis dba 2408 Aug 27 2008 sscoreed.o
    -rw-r--r-- 1 oravis dba 2736 Aug 27 2008 scorept.o
    -rw-r--r-- 1 oravis dba 4352 Aug 27 2008 s0main.o
    -rw-r--r-- 1 oravis dba 139966 Aug 27 2008 liboraz.a
    -rw-r--r-- 1 oravis dba 1751103 Aug 27 2008 libcorejava.so
    -rw-r--r-- 1 oravis dba 119187 Aug 27 2008 lclasses14.zip
    -rw-r--r-- 1 oravis dba 119187 Aug 27 2008 lclasses12.zip
    -rw-r--r-- 1 oravis dba 84898 Aug 27 2008 libons.so
    -rw-r--r-- 1 oravis dba 74601 Aug 27 2008 libonc.so
    -rw-r--r-- 1 oravis dba 85590 Aug 27 2008 libmgwagent.so
    -rw-r--r-- 1 oravis dba 206574 Aug 27 2008 libunls11.a
    -rw-r--r-- 1 oravis dba 283488 Aug 27 2008 libsnls11.a
    -rw-r--r-- 1 oravis dba 2332486 Aug 27 2008 libnls11.a
    -rw-r--r-- 1 oravis dba 85848 Aug 27 2008 liblxled.a
    -rw-r--r-- 1 oravis dba 215608 Aug 27 2008 libncrypt11.a
    -rw-r--r-- 1 oravis dba 4284 Aug 27 2008 nautab.o
    -rw-r--r-- 1 oravis dba 3944 Aug 27 2008 nautab_std.o.dbl
    -rw-r--r-- 1 oravis dba 27008 Aug 27 2008 libnhost11.a
    -rw-r--r-- 1 oravis dba 39564 Aug 27 2008 libntns11.a
    -rw-r--r-- 1 oravis dba 10480 Aug 27 2008 libnoname11.a
    -rw-r--r-- 1 oravis dba 339956 Aug 27 2008 libnldap11.a
    -rw-r--r-- 1 oravis dba 4696 Aug 27 2008 nigtab.o
    -rw-r--r-- 1 oravis dba 4872 Aug 27 2008 osntabst.o
    -rw-r--r-- 1 oravis dba 16912 Aug 27 2008 nigcon.o
    -rw-r--r-- 1 oravis dba 3026 Aug 27 2008 libnsslb11.a
    -rw-r--r-- 1 oravis dba 1112022 Aug 27 2008 libnl11.a
    -rw-r--r-- 1 oravis dba 213228 Aug 27 2008 libnsgr11.a
    -rw-r--r-- 1 oravis dba 159594 Aug 27 2008 libnus11.a
    -rw-r--r-- 1 oravis dba 261226 Aug 27 2008 libntcp11.a
    -rw-r--r-- 1 oravis dba 106352 Aug 27 2008 libnbeq11.a
    -rw-r--r-- 1 oravis dba 6924 Aug 27 2008 libntcps11_std.a.dbl
    -rw-r--r-- 1 oravis dba 309074 Aug 27 2008 libntcps11.a
    -rw-r--r-- 1 oravis dba 865102 Aug 27 2008 libnro11.a
    -rw-r--r-- 1 oravis dba 6758 Aug 27 2008 libnzjs11.a
    -rw-r--r-- 1 oravis dba 4669674 Aug 27 2008 libnjssl11.so
    -rw-r--r-- 1 oravis dba 11845 Aug 27 2008 libntcpaio11.so
    -rw-r--r-- 1 oravis dba 56806 Aug 27 2008 libnque11.so
    -rw-r--r-- 1 oravis dba 216420 Aug 27 2008 libnjni11.so
    -rw-r--r-- 1 oravis dba 15332 Aug 27 2008 naeet.o
    -rw-r--r-- 1 oravis dba 3996 Aug 27 2008 naedhs.o
    -rw-r--r-- 1 oravis dba 5996 Aug 27 2008 naect.o
    -rw-r--r-- 1 oravis dba 5964 Aug 27 2008 naect_std.o.dbl
    -rw-r--r-- 1 oravis dba 15300 Aug 27 2008 naeet_std.o.dbl
    -rw-r--r-- 1 oravis dba 108324 Sep 2 2008 env_emagent.mk
    -rw-r--r-- 1 oravis dba 5623 Sep 2 2008 ins_emagent.mk
    -rw-r--r-- 1 oravis dba 99460 Sep 2 2008 libnmcbuf.a
    -rw-r--r-- 1 oravis dba 45880 Sep 2 2008 libnmccol.a
    -rw-r--r-- 1 oravis dba 4856 Sep 2 2008 snmccolm.o
    -rw-r--r-- 1 oravis dba 21502 Sep 2 2008 libnmcfsga.a
    -rw-r--r-- 1 oravis dba 12250 Sep 2 2008 libnmcfhc.a
    -rw-r--r-- 1 oravis dba 4117694 Sep 4 2008 libctx11.a
    -rw-r--r-- 1 oravis dba 163388 Sep 4 2008 libctxs11.a
    -rw-r--r-- 1 oravis dba 856442 Sep 4 2008 libctxc11.a
    -rw-r--r-- 1 oravis dba 552006 Sep 4 2008 libgx11.a
    -rw-r--r-- 1 oravis dba 208718 Sep 4 2008 libzx11.a
    -rw-r--r-- 1 oravis dba 3731455 Sep 4 2008 libinlxs11.so
    -rw-r--r-- 1 oravis dba 22817190 Sep 5 2008 libjavavm11.a
    -rw-r--r-- 1 oravis dba 1472828 Sep 9 2008 liboevm.a
    -rw-r--r-- 1 oravis dba 33878 Sep 9 2008 libclsrx11.a
    -rw-r--r-- 1 oravis dba 194048 Sep 9 2008 libocrutl11.so
    -rw-r--r-- 1 oravis dba 1759806 Sep 9 2008 libocrb11.so
    -rw-r--r-- 1 oravis dba 1062133 Sep 9 2008 libocr11.so
    -rw-r--r-- 1 oravis dba 1870114 Sep 9 2008 libuini11.so
    -rw-r--r-- 1 oravis dba 2513705 Sep 9 2008 libhasgen11.so
    -rw-r--r-- 1 oravis dba 1617080 Sep 9 2008 libclsr11.a
    -rw-r--r-- 1 oravis dba 170868 Sep 9 2008 libdbcfg11.so
    -rw-r--r-- 1 oravis dba 76181 Sep 9 2008 libclsra11.so
    -rw-r--r-- 1 oravis dba 981908 Sep 11 2008 libsql11.a
    -rw-r--r-- 1 oravis dba 79280 Sep 11 2008 utility.a
    -rw-r--r-- 1 oravis dba 1042396 Sep 11 2008 sqoci.a
    -rw-r--r-- 1 oravis dba 308276 Sep 11 2008 sqora.a
    -rw-r--r-- 1 oravis dba 695666 Sep 11 2008 libskgxpr.so
    -rw-r--r-- 1 oravis dba 21674 Sep 11 2008 libskgxpd.so
    -rw-r--r-- 1 oravis dba 22926 Sep 11 2008 libnnet11.a
    -rw-r--r-- 1 oravis dba 1029197 Sep 11 2008 libsqora.so.11.1
    -rw-r--r-- 1 oravis dba 1313816 Sep 11 2008 libagent11.a
    -rw-r--r-- 1 oravis dba 201420 Sep 11 2008 libplc11.a
    -rw-r--r-- 1 oravis dba 22926 Sep 11 2008 libnnetd11.a
    -rw-r--r-- 1 oravis dba 8795474 Sep 11 2008 libclient11.a
    -rw-r--r-- 1 oravis dba 26750 Sep 11 2008 libavstub11.a
    -rw-r--r-- 1 oravis dba 11007314 Sep 11 2008 libpls11_pic.a
    -rw-r--r-- 1 oravis dba 363374 Sep 11 2008 libpsa11.a
    -rw-r--r-- 1 oravis dba 72114 Sep 11 2008 libnid.a
    -rw-r--r-- 1 oravis dba 5235610 Sep 11 2008 libplp11.a
    -rw-r--r-- 1 oravis dba 202632 Sep 11 2008 libplc11_pic.a
    -rw-r--r-- 1 oravis dba 400868 Sep 11 2008 libcell11.a
    -rw-r--r-- 1 oravis dba 5301906 Sep 11 2008 libplp11_pic.a
    -rw-r--r-- 1 oravis dba 4960 Sep 11 2008 libmm.a
    -rw-r--r-- 1 oravis dba 385350 Sep 11 2008 libhgosh11.a
    -rw-r--r-- 1 oravis dba 2239366 Sep 11 2008 libocci11.a
    -rw-r--r-- 1 oravis dba 3769470 Sep 11 2008 libcommon11.a
    -rw-r--r-- 1 oravis dba 12755 Sep 11 2008 libodmd11.so
    -rw-r--r-- 1 oravis dba 54764 Sep 11 2008 libnfsodm11.so
    -rw-r--r-- 1 oravis dba 423560 Sep 11 2008 libxdb.so
    -rwxr-xr-x 1 oravis dba 47459 Sep 11 2008 libhgotrace11.so
    -rw-r--r-- 1 oravis dba 695636 Sep 11 2008 libskgxpg.so
    -rw-r--r-- 1 oravis dba 8386 Sep 11 2008 libvsn11_std.a.dbl
    -rw-r--r-- 1 oravis dba 8446 Sep 11 2008 libvsn11.a
    -rw-r--r-- 1 oravis dba 13191 Sep 11 2008 libskgxns.so
    -rw-r--r-- 1 oravis dba 315024 Sep 11 2008 libqsmashr.so
    -rw-r--r-- 1 oravis dba 16235836 Nov 10 2008 liboraolap11.a
    -rw-r--r-- 1 oravis dba 29760784 Nov 10 2008 libolapapi11.so
    -rwxr-xr-x 1 oravis dba 42924 Jan 14 2009 libnmuc.so.0
    -rwxr-xr-x 1 oravis dba 42924 Jan 14 2009 libnmuc.so
    drwxr-xr-x 2 oravis dba 4096 Mar 26 2009 stubs
    -rwxr-xr-x 1 oravis dba 145888 Mar 26 2009 libnmefojmx.so.0
    -rwxr-xr-x 1 oravis dba 45302 Mar 26 2009 libnmefdms.so.0
    -rwxr-xr-x 1 oravis dba 37079 Mar 26 2009 libnmevsp.so.0
    -rwxr-xr-x 1 oravis dba 13508 Mar 26 2009 libnmefpfa.so.0
    -rwxr-xr-x 1 oravis dba 52372 Mar 26 2009 libnmefsqlt.so.0
    -rwxr-xr-x 1 oravis dba 27703 Mar 26 2009 libnmefsp.so.0
    -rwxr-xr-x 1 oravis dba 24892 Mar 26 2009 libnmefport.so.0
    -rwxr-xr-x 1 oravis dba 73465 Mar 26 2009 libnmcfsga.so.0
    -rwxr-xr-x 1 oravis dba 45796 Mar 26 2009 libnmcfhc.so.0
    -rwxr-xr-x 1 oravis dba 69739 Mar 26 2009 libsrvmocr11.so0
    -rwxr-xr-x 1 oravis dba 1691901 Mar 26 2009 libsrvmhas11.so0
    -rwxr-xr-x 1 oravis dba 1632963 Mar 26 2009 libocci.so.11.1
    -rw-r--r-- 1 oravis dba 7085106 Mar 26 2009 libxml11.a
    -rw-r--r-- 1 oravis dba 27150788 Mar 26 2009 libgeneric11.a
    -rw-r--r-- 1 oravis dba 11077402 Mar 26 2009 libpls11.a
    -rw-r--r-- 1 oravis dba 4278296 Mar 26 2009 libcore11.a
    -rw-r--r-- 1 oravis dba 181560214 Mar 26 2009 libserver11.a
    lrwxrwxrwx 1 oravis dba 59 Nov 5 23:52 libclntsh.so.10.1 -> /d2/R12/ab/apps/R1211XB9/db/tech_st/11.1.0/lib/libclntsh.so
    lrwxrwxrwx 1 oravis dba 12 Nov 5 23:52 libodm11.so -> libodmd11.so
    lrwxrwxrwx 1 oravis dba 15 Nov 5 23:58 libocci.so -> libocci.so.11.1
    -rw-r--r-- 1 oravis dba 111 Nov 5 23:59 ldflagsO
    -rw-r--r-- 1 oravis dba 111 Nov 5 23:59 ldflags
    -rwxr-xr-x 1 oravis dba 9904424 Nov 5 23:59 libagtsh.so.1.0
    lrwxrwxrwx 1 oravis dba 15 Nov 5 23:59 libagtsh.so -> libagtsh.so.1.0
    -rw-r--r-- 1 oravis dba 2264 Nov 5 23:59 ntcontab.o
    -rw-r--r-- 1 oravis dba 1912 Nov 5 23:59 nnfgt.o
    -rw-r--r-- 1 oravis dba 8572884 Nov 5 23:59 libn11.a
    -rwxr-xr-x 1 oravis dba 2610320 Nov 5 23:59 libnmemso.so.0
    -rwxr-xr-x 1 oravis dba 63592 Nov 6 00:00 libnmeoci.so.0
    -rwxr-xr-x 1 oravis dba 23903 Nov 6 00:00 libnmefw.so.0
    -rwxr-xr-x 1 oravis dba 47734 Nov 6 00:00 libnmefsql.so.0
    -rwxr-xr-x 1 oravis dba 50281 Nov 6 00:00 libnmefos.so.0
    -rwxr-xr-x 1 oravis dba 28830 Nov 6 00:00 libnmefud.so.0
    -rwxr-xr-x 1 oravis dba 199975 Nov 6 00:00 libnmefut.so.0
    -rwxr-xr-x 1 oravis dba 145253 Nov 6 00:00 libnmefojmx.so
    -rwxr-xr-x 1 oravis dba 44419 Nov 6 00:00 libnmefdms.so
    -rwxr-xr-x 1 oravis dba 35900 Nov 6 00:00 libnmevsp.so
    -rwxr-xr-x 1 oravis dba 107145 Nov 6 00:00 libnmevq.so.0
    -rwxr-xr-x 1 oravis dba 14368 Nov 6 00:00 libnmefvr.so.0
    -rwxr-xr-x 1 oravis dba 12801 Nov 6 00:00 libnmefpfa.so
    -rwxr-xr-x 1 oravis dba 15627 Nov 6 00:00 libnmastk.so.0
    -rwxr-xr-x 1 oravis dba 15601 Nov 6 00:00 libnmalk.so.0
    -rwxr-xr-x 1 oravis dba 33331 Nov 6 00:00 libnmadm.so.0
    -rwxr-xr-x 1 oravis dba 24751 Nov 6 00:00 libnmadbg.so.0
    -rwxr-xr-x 1 oravis dba 51665 Nov 6 00:00 libnmefsqlt.so
    -rwxr-xr-x 1 oravis dba 26204 Nov 6 00:00 libnmefsp.so
    -rwxr-xr-x 1 oravis dba 24817 Nov 6 00:00 libnmefport.so
    -rwxr-xr-x 1 oravis dba 22923 Nov 6 00:00 libnmasf.so.0
    -rwxr-xr-x 1 oravis dba 27141 Nov 6 00:00 libnmarl.so.0
    -rwxr-xr-x 1 oravis dba 73374 Nov 6 00:00 libnmcfsga.so
    -rwxr-xr-x 1 oravis dba 45457 Nov 6 00:00 libnmcfhc.so
    -rwxr-xr-x 1 oravis dba 63592 Nov 6 00:00 libnmeoci.so
    -rwxr-xr-x 1 oravis dba 2610320 Nov 6 00:00 libnmemso.so
    -rwxr-xr-x 1 oravis dba 23903 Nov 6 00:00 libnmefw.so
    -rwxr-xr-x 1 oravis dba 50281 Nov 6 00:00 libnmefos.so
    -rwxr-xr-x 1 oravis dba 14368 Nov 6 00:00 libnmefvr.so
    -rwxr-xr-x 1 oravis dba 199975 Nov 6 00:00 libnmefut.so
    -rwxr-xr-x 1 oravis dba 28830 Nov 6 00:00 libnmefud.so
    -rwxr-xr-x 1 oravis dba 47734 Nov 6 00:00 libnmefsql.so
    -rwxr-xr-x 1 oravis dba 107145 Nov 6 00:00 libnmevq.so
    -rwxr-xr-x 1 oravis dba 15601 Nov 6 00:00 libnmalk.so
    -rwxr-xr-x 1 oravis dba 33331 Nov 6 00:00 libnmadm.so
    -rwxr-xr-x 1 oravis dba 24751 Nov 6 00:00 libnmadbg.so
    -rwxr-xr-x 1 oravis dba 15627 Nov 6 00:00 libnmastk.so
    -rwxr-xr-x 1 oravis dba 22923 Nov 6 00:00 libnmasf.so
    -rwxr-xr-x 1 oravis dba 27141 Nov 6 00:00 libnmarl.so
    -rwxr-xr-x 1 oravis dba 48333396 Nov 6 00:00 libclntsh.so.11.1
    -rw-r--r-- 1 oravis dba 4739091 Nov 6 00:00 clntsh.map
    lrwxrwxrwx 1 oravis dba 17 Nov 6 00:00 libclntsh.so -> libclntsh.so.11.1
    -rwxr-xr-x 1 oravis dba 68304 Nov 6 00:00 libsrvmocr11.so
    -rwxr-xr-x 1 oravis dba 79849 Nov 6 00:00 libsrvm11.so0
    -rwxr-xr-x 1 oravis dba 1696482 Nov 6 00:00 libsrvmhas11.so
    -rwxr-xr-x 1 oravis dba 79849 Nov 6 00:00 libsrvm11.so
    -rwxr-xr-x 1 oravis dba 10353690 Nov 6 00:00 liborasdkbase.so.11.1
    lrwxrwxrwx 1 oravis dba 21 Nov 6 00:00 liborasdkbase.so -> liborasdkbase.so.11.1
    -rwxr-xr-x 1 oravis dba 39093373 Nov 6 00:00 liborasdk.so.11.1
    lrwxrwxrwx 1 oravis dba 17 Nov 6 00:00 liborasdk.so -> liborasdk.so.11.1
    -rw-r--r-- 1 oravis dba 695636 Nov 6 00:00 libskgxp11.so

  • Auto startup/shutdown virtualbox and the machine running in it ?

    i am trying to use the phpvirtualbox to control the running of the virtualbox. although i am still using the rc.conf start the phpvirtualbox, i saw there was a way to start it up by  systemd. the question is, in order to start phpvirtualbox, you need to start the a virtualbox first (am i right ?), but how. also, when i want to shutdown the server, i have to stop the phpvirtualbox, the vm (which is xp in my case) inside the virtualbox and then the virtualbox, but how ?

    Robert Kempner wrote:
    Do I need to have "Time Machine" running in the background all the time ...
    It is how it is designed to be used. How Time Machine Works its Magic
    Robert Kempner wrote:
    ... can I turn it off and on say, once a week?
    Why..?
    Perhaps TM is not for you... See Time Machine vs. Clones and Archives
    More Info here >  http://www.reedcorner.net/guides/backups/ch2.php

  • 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!

  • Here's a solution to Oracle Startup / Shutdown on RH6

    I had a hard time getting Red Hat 6.0 to startup and shutdown
    Oracle properly. Red Hat's slick rc scripts look cool, but hide
    the problem unless you do some serious reading.
    This script still isn't perfect, mainly because it can't
    shutdown if oracle users are still logged in. This is a problem
    with the dbshut scripts. I try to avoid hacking Oracle's bin
    directory, but if you really want to go down, change the
    shutdown lines to shutdown immediate. Oracle, please provide an
    option to dbshut to fix this! :-)
    My changes to the book version fix the following:
    1. It creates a file /var/log/dbora to log the startup output to
    give you some visibility after the fact.
    2. Creating the /var/lock/subsys/dbora file after startup makes
    the shutdown work. Otherwise rc won't even try. Deleting it
    makes changes between run levels work right.
    3. The startup is NOT backgrounded so that if you are watching
    it boot you can at least gauge the time it takes before the
    startup.
    4. It starts the listener too.
    5. It checks the log file for startup errors and makes the
    screen say FAILED in red if it sees any errors.
    5. It allows dbshut some time to finish before unmounting. My
    dual xenon machine goes down do fast dbshut wouldn't finish
    downing both of my sids.
    # dbora -start/stop Oracle
    #action
    ORA_HOME=/home/oracle;export ORA_HOME
    ORA_OWNER=oracle;export ORA_OWNER
    if [ ! -f $ORA_HOME/bin/dbstart -o ! -d $ORA_HOME ]
    then
    echo "Oracle startup: cannot start"
    exit
    fi
    case "$1" in
    'start')
    su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart" >
    /var/log/dbora.log
    su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start" >>
    /var/log/dbora.log
    touch /var/lock/subsys/dbora
    'stop')
    su - $ORA_OWNER -c $ORA_HOME/bin/dbshut &
    sleep 15
    rm -f /var/lock/subsys/dbora
    esac
    if egrep -q "ORA-" /var/log/dbora.log; then
    exit -1
    else
    exit 0
    fi
    Note that the links prescribed by the book are also incorrect.
    Linux's rc levels do NOT run sequentially. Therefore, you need a
    start and stop on the same level. If you want to save some RAM
    on the serve by not running X, you'll want level 4 scripts and
    level 5 scripts. So, Create all these links (as ROOT).
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc4.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc4.d/S99dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc5.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc5.d/S99dbora
    To be really safe also create these links. This way there is no
    escaping a proper oracle shutdown.
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc0.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc1.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc2.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc3.d/K10dbora
    ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc6.d/K10dbora
    Have fun!
    null

    It isn't necessary to create the symlinks for the rc scripts
    manually--that's what the "chkconfig" command is for.
    Mike Mitchell (guest) wrote:
    : I had a hard time getting Red Hat 6.0 to startup and shutdown
    : Oracle properly. Red Hat's slick rc scripts look cool, but hide
    : the problem unless you do some serious reading.
    : This script still isn't perfect, mainly because it can't
    : shutdown if oracle users are still logged in. This is a problem
    : with the dbshut scripts. I try to avoid hacking Oracle's bin
    : directory, but if you really want to go down, change the
    : shutdown lines to shutdown immediate. Oracle, please provide
    an
    : option to dbshut to fix this! :-)
    : My changes to the book version fix the following:
    : 1. It creates a file /var/log/dbora to log the startup output
    to
    : give you some visibility after the fact.
    : 2. Creating the /var/lock/subsys/dbora file after startup makes
    : the shutdown work. Otherwise rc won't even try. Deleting it
    : makes changes between run levels work right.
    : 3. The startup is NOT backgrounded so that if you are watching
    : it boot you can at least gauge the time it takes before the
    : startup.
    : 4. It starts the listener too.
    : 5. It checks the log file for startup errors and makes the
    : screen say FAILED in red if it sees any errors.
    : 5. It allows dbshut some time to finish before unmounting. My
    : dual xenon machine goes down do fast dbshut wouldn't finish
    : downing both of my sids.
    : # dbora -start/stop Oracle
    : #action
    : ORA_HOME=/home/oracle;export ORA_HOME
    : ORA_OWNER=oracle;export ORA_OWNER
    : if [ ! -f $ORA_HOME/bin/dbstart -o ! -d $ORA_HOME ]
    : then
    : echo "Oracle startup: cannot start"
    : exit
    : fi
    : case "$1" in
    : 'start')
    : su - $ORA_OWNER -c "$ORA_HOME/bin/dbstart" >
    : /var/log/dbora.log
    : su - $ORA_OWNER -c "$ORA_HOME/bin/lsnrctl start" >>
    : /var/log/dbora.log
    : touch /var/lock/subsys/dbora
    : 'stop')
    : su - $ORA_OWNER -c $ORA_HOME/bin/dbshut &
    : sleep 15
    : rm -f /var/lock/subsys/dbora
    : esac
    : if egrep -q "ORA-" /var/log/dbora.log; then
    : exit -1
    : else
    : exit 0
    : fi
    : Note that the links prescribed by the book are also incorrect.
    : Linux's rc levels do NOT run sequentially. Therefore, you need
    a
    : start and stop on the same level. If you want to save some RAM
    : on the serve by not running X, you'll want level 4 scripts and
    : level 5 scripts. So, Create all these links (as ROOT).
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc4.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc4.d/S99dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc5.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc5.d/S99dbora
    : To be really safe also create these links. This way there is no
    : escaping a proper oracle shutdown.
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc0.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc1.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc2.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc3.d/K10dbora
    : ln -s /etc/rc.d/init.d/dbora /etc/rc.d/rc6.d/K10dbora
    : Have fun!
    null

  • Oracle Startup/Shutdown with SQLPLUS and ORADIM in Windows...

    I am a newbie to the Windows platform. SQLPLUS will not allow me to issue a STARTUP command. This is what I get when I attempt to SHUTDOWN IMMEDIATE and subsequently issue a STARTUP MOUNT/NOMOUNT or any STARTUP command for that matter. The SHUTDOWN command works successfully but the subsequent startup fails with an ORA-12514: TNS:listener does not currently know of service requested in connect descriptor message.
    D:\>set ORACLE_SID=NMPC00
    D:\>set ORACLE_HOSTNAME=TAX-DEV-ORA-01
    D:\>set ORACLE_HOME=D:\app\oracle\product\11.2.0\dbhome_1
    D:\>sqlplus sys@NMPC00 as sysdba
    SQL*Plus: Release 11.2.0.1.0 Production on Sat Oct 23 11:41:56 2010
    Copyright (c) 1982, 2010, Oracle. All rights reserved.
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> shutdown immediate
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    SQL>
    When I look at the Windows service, it still reports 'Started' despite the fact that I shutdown the instance. What is the proper protocol for shutting down and starting up an Oracle instance in Windows. Do I have to coordinate these activities with the ORADIM -STARTUP / -SHUTDOWN commands?

    I am also newbie to oracle and running into the similar problem when trying to start oracle database using windows command prompt and getting the below error:
    Command prompt is being run as administrator on windows7 O/S
    C:\ORACLE\product\11.2.0\dbhome_1\BIN>oradim -SHUTDOWN -SID O22BVGI -SHUTTYPE srvc,inst -SHUTMODE nornal
    ORA-01031: insufficient privileges
    The reason behind this to do it is , I need a batch script for stopping and restarting the oracle database instance using a Pfile which will contain the initialization parameters.
    Please can someone help!
    sqlnet.ora is:
    SQLNET.AUTHENTICATION_SERVICES= (NTS)
    NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
    Kind Regards
    Sam
    Edited by: 808116 on Nov 7, 2010 4:21 PM

  • 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

  • Oracle Startup/Shutdown Procedure

    Hi All,
    We have Oracle 10G R2 on AIX 5 with ASM managed storage.
    My question is what are the steps to shutdown oracle database. I mean should we stop the ASM instance first or simple shutdown database command will do all work. Similarly what are the steps to start the database. How ASM instance will be started and how listner will be up?
    Thanks

    Hi,
    Below link may help you
    http://www.dba-oracle.com/art_dbazine_ault_start_stop_db.htm
    Thanks,

  • 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.

  • How to let database(10.2) auto startup when linux reboot?

    Hi all,
    I installed oracle database 10.2 in linux (x86),and created a database.
    I can startup the database manually. But database can not be started up automatic when linux starts up.
    How to let database startup automatic when OS starts up?
    the details shell scripts for auto startup would be appreciated!
    Thanks

    I don't know LINUX but I know Solaris. In Solaris, you have a startup and shutdown script in $ORACLE_HOME/bin. Setting the field to Y in oratab means you startup/shutdown the instance when executing the scripts. However, it does not mean the startup script will be
    executed upon reboot. In solaris, we place a script in /etc/rc3.d. Then the script will be executed upon reboot. Guess you have similar features in Linux.

  • Database auto-startup script

    Hi Team,
    How can I check whether the auto startup script is scheduled for the database after the server reboot
    OS version:Linux server1 2.6.18-194.11.1.el5 #1 SMP Tue Jul 24 05:45:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
    DB version :11.2.0.2
    /etc/oratab entry is set to Y.
    But the database did not startup after the server reboot. How to verify that the auto startup script is available?

    http://www.oracle-base.com/articles/linux/automating-database-startup-and-shutdown-on-linux.php
    HTH
    Anand

  • What happen during shutdown oracle database

    Dear All,
    i have a questions and i enclosed some suggestions for the answer because I'm confused about the answers :
    What happens during shutdown oracle database :
    and the suggested answer :
    1- When shutdown the database with NORMAL or IMMEDIATE option : the database system writes check point before shutting down the database .
    2- when you shutdown the database with the IMMEDIATE , option , open transaction are rolled back before the database is shutdown .
    3- shutting down the database with abort always requires an instance recovery at the next startup .
    please suggest the right answer .
    Regards

    Hi Anwar,
    When you close a database, Oracle writes all database data and recovery data in the SGA to the datafiles and redo log files, respectively. Next, Oracle closes all online datafiles and redo log files.
    When you terminate the instance of an open database/use abort command to close and completely shut down the database the writing of all data in the buffers of the SGA to the datafiles and redo log files is skipped. The subsequent reopening of the database requires recovery, which Oracle performs automatically.
    I hope this will help you out to understand the process.

Maybe you are looking for