Oracle startup

What are the tasks that a dba can perform when.
Database is in shutdown mode, NOMOUNT stage,Mount stage.

You seems to be a beginner, also read the concepts here,
http://www.dba-oracle.com/concepts/shutdown_commands.htm
http://www.dba-oracle.com/t_oracle_shutdown_immediate_abort.htm

Similar Messages

  • Running Oracle startup or shutdown bat file from Java code

    I have two bat files for the startup and shutdown of Oracle instance which works fine from the command prompt. But my requirement is to run it through a Java program. Please reply with full Java code. Also mention how I would get the status of the bat files that it is successfully executed or not and if not what is the error.

    Your program is working fine, but there is another problem. What's happening now is I have to open the Login screen after the startup of oracle server is complete, but the next line of my program after Runtime.exec is the LoginScreen.show which immediately shows the login screen after executing Runtime.exec and when I am giving the login name and password and press enter, it shows Oracle not available exception, because the startup process is still in progress. I want to stop the execution of my next line of code until and unless my process of Oracle startup is complete.

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

    Hi All,
    I have oracle 9i Enterprise Edition 9.2.0.8.0 installed on server.
    I have change large pool size and shared pool size parameters in init.ora file and i have shutdown the database using shutdown immediate.
    I have restarted the server and since then when i try to stratup the database i am getting the error as
    ORA-24324: service handle not initialized
    ORA-01041: internal error. hostdef extension doesn't exist.
    Can anyone help on this?
    Thanks,
    Ravi

    Don't cross post in many forum, check response from your Oracle startup issue

  • HA Oracle startup/shutdown question

    Environment:
    2 Sunfire V890's running solaris 2.9 and SC3.1U4
    Hello All,
    I am having a problem with oracle startup and shutdown in my cluster. In order to get oracle to startup after a failover, shutdown what have you, I need to implement the following procedure as a pre/post oracle startup operation/script. Can anyone tell me if there is a place or hook in the HAOracle agent where I can add my own operation? I would rather avoid having to write a GDS agent in order to do this, if it is at all possilble.
    Thanks,
    George Cebulka
    PS
    Please Note: (This is a DBA thing, not mine!)
    ************** Begin *********************
    After a failover or startup we need following to avoid the �authentication error�
    1. remove the sqlnet.ora soft link from $ORACLE_HOME/network/admin
    1. rm /global/oracle/oracledb/oraclev10201/network/admin/sqlnet.ora
    2. Create a new soft link to sqlnet.ora in $ORACLE_HOME/network/admin as following
    1. ln �s /global/pitt/dba/network/net8/sqlnet.ora /global/oracle/oracledb/oraclev10201/network/admin/sqlnet.ora
    3. startup the database and listeners (using cluster database).
    4. Now database is up and running and we need to turn on radius authentication for which we need this post stuff
    5. Remove the sqlnet.ora link
    1. rm /global/oracle/oracledb/oraclev10201/network/admin/sqlnet.ora
    6. Create a new soft link to replace sqlnet.ora with radius sqlnet.ora
    1. ln �s /global/pitt/dba/network/net8/sqlnet.ora.radius /global/oracle/oracledb/oraclev10201/network/admin/sqlnet.ora
    *************** End ******************

    You could also try the following:
    Create two GDS agents, where you need to include the steps to disable the pmf action script, which I describe in a blog at
    http://blogs.sun.com/TF/entry/disabling_pmf_action_script_with .
    This is needed since your scripts will not leave a process running for PMF.
    1. GDS resource (for this example I call it ora-prestart-rs):
    Start_command: It will do the steps to implement the original sqlnet.ora file + the steps from the blog
    Probe_command: /bin/true
    Stop_command: not needed
    2. GDS resource (for this example I call it ora-poststart-rs):
    Start_command: It will do the steps to setup the link for the radius sqlnet.ora file + the steps from the blog
    Probe_command: /bin/true
    Stop_command: It will do the steps to re-implement the original sqlnet.ora file
    Then you create the following resource dependencies (here I assume the name for the SUNW.oracle_server resource is ora-rs):
    scrgadm -c -j ora-rs -y Resource_dependencies=ora-prestart-rs
    scrgadm -c -j ora-poststart-rs -y Resource_dependencies=server-dwdd-rs
    Maybe you need to setup the same dependencies to include the SUNW.oracle_listerner resource. You did not mention which of those is facing problems.
    Of course, I never tried this. But this would enable you to use the HA Oracle agent unchanged.
    Greets
    Thorsten
    PS: I forgot to also mention that you need to set the Restart_type extension property for the SUNW.oracle_server resource to RESOURCE_GROUP_RESTART:
    scrgadm -c -j ora-rs -y Restart_type=RESOURCE_GROUP_RESTART
    That way a triggered restart by ora-rs will allways force the RG to go through stop/start - and only then the link will get set back to the sqlnet.ora the SUNW.oracle_server needs to work correctly.
    Note again - this is theory and needs proper testing.
    Message was edited by:
    Thorsten.Frueauf

  • Oracle Startup Scripts for AIX

    Does anyone have experience setting up automatic Oracle startup scripts for AIX?
    Any help would be greatly appreciated!
    Thanks,
    Mike

    Some recommandation here :
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b15658/strt_stp.htm#sthref255
    Nicolas.

  • PerfMon reporting dramatic disk access time increase on Oracle startup

    Hi,
    My oracle 10g (10.2.0.4) database is hosted on a windows 2003 server.
    The datafiles are stored on a RAID1 disk array, on a dedicated partition : currently 30 gigs free out of 180, wich should not be a concern unless i'm wrong, because the datafiles were created as 10 Go files with no autogrowth. I add a new datafile whenever i need more room for my tables (alerts when 80% used).
    Since 2 days i experience a dramatic performance loss :
    The EM console reports nothing special (no alarms related to storage) apart from the need for more paginated memory.
    I issue a reorg when the segmentation advisor suggests it.
    My optimizer statistics are calculated by the default scheduled job.
    The weird thing I noticed is that as soon as I start the database, there's a huge increase in disk activity even though no query at all is submitted to the database.
    PerfMon reports Current Disk Queue Length > 1000 and disk access time > 3000 ms
    CPU is 2% activity on the 4-cpus server.
    I have plenty of spare memory (currently 3 Go used out of 16).
    This is only a dev server for ETL processes, it has very few concurrent connections.
    Any suggestions welcome.
    AWR report is available here
    http://min.us/mqnXQhd5Z
    Edited by: user10799939 on 22 mars 2012 09:30

    Cache Sizes
    ~~~~~~~~~~~                       Begin        End
                   Buffer Cache:     1,296M     1,296M  Std Block Size:         8K
               Shared Pool Size:       160M       160M      Log Buffer:    14,364K
    Load Profile
    ~~~~~~~~~~~~                            Per Second       Per Transaction
                      Redo size:            460,955.72 ;         2,477,358.63
                  Logical reads:              3,392.16 ;            18,230.80
                  Block changes:              6,451.93 ;            34,675.22
                 Physical reads:                  2.92 ;                15.67
                Physical writes:                394.52 ;             2,120.28
                     User calls:                  1.69 ;                 9.08
                         Parses:                  3.31 ;                17.81
                    Hard parses:                  0.17 ;                 0.90
                          Sorts:                  1.32 ;                 7.09
                         Logons:                  0.06 ;                 0.31
                       Executes:                  7.01 ;                37.68
                   Transactions:                  0.19
      % Blocks changed per Read:  190.20 ;   Recursive Call %:    96.23
    Rollback per transaction %:    0.30 ;      Rows per Sort:    14.41
    Instance Efficiency Percentages (Target 100%)
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                Buffer Nowait %:   99.98 ;      Redo NoWait %:   99.86
                Buffer  Hit   %:   99.92 ;   In-memory Sort %:  100.00
                Library Hit   %:   96.30 ;       Soft Parse %:   94.96
             Execute to Parse %:   52.74 ;        Latch Hit %:   99.07
    Parse CPU to Parse Elapsd %:    0.35 ;    % Non-Parse CPU:   99.30
    Shared Pool Statistics        Begin    End
                 Memory Usage %:   75.48 ;  75.51
        % SQL with executions>1:   79.92 ;  85.03
      % Memory for SQL w/exec>1:   77.07 ;  70.09
    Top 5 Timed Events                                         Avg %Total
    ~~~~~~~~~~~~~~~~~~                                        wait   Call
    Event                                 Waits    Time (s)   (ms)   Time Wait Class
    db file sequential read               9,052      17,688   1954   51.3 ;  User I/O
    log file switch (checkpoint in        5,303       4,649    877   13.5 Configurat
    log file switch completion            4,245       4,023    948   11.7 Configurat
    wait for a undo record               32,393       3,531    109   10.3 ;     Other
    db file parallel write               18,771       3,437    183   10.0 System I/O Havent seen this much wait on average. For example 877ms for "log file switch" is over threshold. And other wait events too..
    Time Model Statistics                DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> Total time in database user-calls (DB Time): 34446.5s
    -> Statistics including the word "background" measure background process
       time, and so do not contribute to the DB time statistic
    -> Ordered by % or DB time desc, Statistic name
    Statistic Name                                       Time (s) % of DB Time
    sql execute elapsed time                              4,008.5 ;        11.6
    parse time elapsed                                      352.9 ;         1.0
    hard parse elapsed time                                 352.7 ;         1.0
    PL/SQL compilation elapsed time                         120.1 ;          .3
    DB CPU                                                   61.8 ;          .2
    failed parse elapsed time                                21.3 ;          .1
    PL/SQL execution elapsed time                             8.0 ;          .0
    connection management call elapsed time                   0.0 ;          .0
    hard parse (sharing criteria) elapsed time                0.0 ;          .0
    repeated bind elapsed time                                0.0 ;          .0
    hard parse (bind mismatch) elapsed time                   0.0 ;          .0
    DB time                                              34,446.5 ;         N/A
    background elapsed time                              14,889.7 ;         N/A
    background cpu time                                      39.0 ;         N/A
    Wait Class                            DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> s  - second
    -> cs - centisecond -     100th of a second
    -> ms - millisecond -    1000th of a second
    -> us - microsecond - 1000000th of a second
    -> ordered by wait time desc, waits desc
                                                                      Avg
                                           %Time       Total Wait    wait     Waits
    Wait Class                      Waits  -outs         Time (s)    (ms)      /txn
    User I/O                       10,515     .1           17,785    1691      15.8
    Configuration                  10,186   79.5 ;           8,865     870      15.3
    System I/O                     27,619     .0            8,774     318      41.6
    Other                          57,768   98.3 ;           6,915     120      87.0
    Commit                          2,634   88.6 ;           2,481     942       4.0
    Concurrency                     2,847   75.4 ;           2,240     787       4.3
    Application                       219    2.3 ;              23     105       0.3
    Network                         4,790     .0                0       0       7.2
              ------------------------------------------------------------- again seen, there is very high wait on User IO
    Wait Events                          DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> s  - second
    -> cs - centisecond -     100th of a second
    -> ms - millisecond -    1000th of a second
    -> us - microsecond - 1000000th of a second
    -> ordered by wait time desc, waits desc (idle events last)
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    db file sequential read               9,052     .0      17,688    1954      13.6
    log file switch (checkpoint           5,303   78.0 ;      4,649     877       8.0
    log file switch completion            4,245   89.2 ;      4,023     948       6.4
    wait for a undo record               32,393   99.8 ;      3,531     109      48.8
    db file parallel write               18,771     .0       3,437     183      28.3
    wait for stopper event to be         24,203   99.8 ;      2,634     109      36.5
    log file sync                         2,634   88.6 ;      2,481     942       4.0
    control file sequential read          7,356     .0       2,431     330      11.1
    buffer busy waits                     2,513   83.1 ;      2,173     865       3.8
    log file parallel write                 520     .0       1,566    3012       0.8
    control file parallel write             840     .0       1,334    1588       1.3
    rdbms ipc reply                         172   91.3 ;        330    1916       0.3
    enq: CF - contention                    309   23.0 ;        268     867       0.5
    log buffer space                        638   28.5 ;        192     301       1.0
    enq: PS - contention                     52   23.1 ;         71    1362       0.1
    db file scattered read                  113     .0          67     590       0.2
    os thread startup                        76   77.6 ;         63     834       0.1
    reliable message                         57   78.9 ;         50     878       0.1
    enq: RO - fast object reuse              22   22.7 ;         23    1038       0.0
    latch free                              537     .0          16      30       0.8
    Streams AQ: qmn coordinator               3  100.0 ;         15    5005       0.0 Overstepping
    Background Wait Events               DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> ordered by wait time desc, waits desc (idle events last)
                                                                       Avg
                                                 %Time  Total Wait    wait     Waits
    Event                                 Waits  -outs    Time (s)    (ms)      /txn
    db file parallel write               18,772     .0       3,437     183      28.3
    events in waitclass Other            24,367   99.5 ;      3,010     124      36.7
    control file sequential read          6,654     .0       2,333     351      10.0
    log file parallel write                 520     .0       1,566    3012       0.8
    control file parallel write             840     .0       1,334    1588       1.3
    buffer busy waits                       899   94.2 ;        884     984       1.4
    log file switch (checkpoint             206   82.0 ;        185     898       0.3
    os thread startup                        76   77.6 ;         63     834       0.1
    log file switch completion               46   93.5 ;         45     982       0.1
    log buffer space                        158   31.0 ;         12      77       0.2
    db file sequential read                  62     .0           7     111       0.1
    db file scattered read                   20     .0           6     318       0.0
    direct path read                        660     .0           5       7       1.0
    log file sequential read                 66     .0           4      65       0.1
    log file single write                    66     .0           1      16       0.1
    enq: RO - fast object reuse               2     .0           0      38       0.0
    latch: cache buffers chains               3     .0           0       6       0.0
    direct path write                       660     .0          -5      -8       1.0
    rdbms ipc message                     9,052   87.5 ;     21,399    2364      13.6
    pmon timer                            1,318   90.4 ;      3,562    2703       2.0
    Streams AQ: qmn coordinator             633   97.6 ;      3,546    5602       1.0
    Streams AQ: waiting for time             77   61.0 ;      3,449   44795       0.1
    PX Deq: Join ACK                         21     .0           0       0       0.0 Again overshooting
    Tablespace IO Stats                  DB/Inst: MDMPRJ/MDMPRJ  Snaps: 2840-2841
    -> ordered by IOs (Reads + Writes) desc
    Tablespace
                     Av      Av     Av                       Av     Buffer Av Buf
             Reads Reads/s Rd(ms) Blks/Rd       Writes Writes/s      Waits Wt(ms)
    UNDOTBS1
               914       0 ######     1.0 ;   1,368,515      383      2,534  863.2
    MDMREF_INDICES
             6,918       2 ######     1.0 ;      11,086        3          0    0.0
    SYSAUX
               626       0 ######     1.1 ;       1,804        1          0    0.0
    SYSTEM
               850       0 ######     1.7 ;         296        0          0    0.0
    MDMREF_DATA
               293       0  712.3 ;    1.0 ;         274        0          0    0.0
    MDMPRJ_ODS
               198       0   72.1 ;    1.0 ;         198        0          0    0.0
    FEU_VERT
                33       0   61.5 ;    1.0 ;          33        0          0    0.0
    USERS
                33       0   31.5 ;    1.0 ;          33        0          0    0.0
              ------------------------------------------------------------- Now have a serious look at it. Av Rd(ms). Now for some tablespace value cannot event fit in window thats why its showing ##
    According to oracle recommendation Av Rd(ms) shouldn't be greater then 20, if its goes over 20 then its considered to be an issue with IO subsystem. But as its seen that in your case its overshooting.
    Now the question from my side
    Have done any configuration changes?
    I would suggest you to revert these changes asap and contact storage admin guys...
    Hope this helps

  • Automated Oracle Startup & Shutdown

    I am trying to get make my Oracle database shutdown and startup
    automatically at boot, but am having a hard time getting this to
    work properly. I have created a file in /etc/rc.d/init.d called
    dbora:
    case "$1" in
    'start')
    su - oracle -c $ORACLE_BASE/admin/bin/dbstart.sh &
    'stop')
    su - oracle -c $ORACLE_BASE/admin/bin/dbshut.sh &
    esac
    I also created the following links in EVERY (out of frustration)
    /etc/rc.d/rc#.d directory:
    lrwxrwxrwx 1 root root 22 Jul 1 10:12 S99dbora -
    /etc/rc.d/init.d/dboralrwxrwxrwx 1 root root 22 Jul 1 10:12 K30dbora -
    /etc/rc.d/init.d/dboraThe problem does not really appear to be linked to the actual
    database shutdown or startup, but rather with LINUX. I have
    replaced the contents of dbstart.sh & dbshut.sh with a simple
    echo redirect to file to prove this out. Specifically, here is
    what is happening:
    * Running "dbora start" or "dbora stop" manually always works.
    * Neither "dbora start" or "dbora stop" work when booting or
    switching runlevels, although the message STARTING DBORA does
    scroll past the console.
    I have several people look at this here and no one can figure
    out why this isn't working. Can you assist?
    null

    Peter,
    Normally the problem here is that the environment is not set, or
    is not being set correctly OR that things that Oracle needs to be
    available have already been killed (lower run level) or have not
    been started (higher run level).
    Check that the environment is OK when the dbora script is run and
    check that your scripts are called in the right order of things
    when moving between run levels.
    Regards,
    Mark
    Pete Petersen (guest) wrote:
    : I am trying to get make my Oracle database shutdown and startup
    : automatically at boot, but am having a hard time getting this
    to
    : work properly. I have created a file in /etc/rc.d/init.d called
    : dbora:
    : case "$1" in
    : 'start')
    : su - oracle -c $ORACLE_BASE/admin/bin/dbstart.sh &
    : 'stop')
    : su - oracle -c $ORACLE_BASE/admin/bin/dbshut.sh &
    : esac
    : I also created the following links in EVERY (out of
    frustration)
    : /etc/rc.d/rc#.d directory:
    : lrwxrwxrwx 1 root root 22 Jul 1 10:12 S99dbora
    : > /etc/rc.d/init.d/dbora
    : lrwxrwxrwx 1 root root 22 Jul 1 10:12 K30dbora
    : > /etc/rc.d/init.d/dbora
    : The problem does not really appear to be linked to the actual
    : database shutdown or startup, but rather with LINUX. I have
    : replaced the contents of dbstart.sh & dbshut.sh with a simple
    : echo redirect to file to prove this out. Specifically, here is
    : what is happening:
    : * Running "dbora start" or "dbora stop" manually always works.
    : * Neither "dbora start" or "dbora stop" work when booting or
    : switching runlevels, although the message STARTING DBORA does
    : scroll past the console.
    : I have several people look at this here and no one can figure
    : out why this isn't working. Can you assist?
    null

  • Oracle startup/shutdown triggers

    Hi,
    I have a scenerion appreciated the inputs/suggestions.
    We have 750 db's from oracle 8i to 11g .
    i will take one db as test db and i will create a table in this db and from all db's a trigger has to fire whenever database is down or up and update this test table in test db.
    may be test table structure contains hostname, db name , db status(1 for down, 0 for up), timestamp
    Thanks in advance .
    Prakash

    Hi thanks for all the inputs.
    We use OEM grid still we want this project to execute.
    The steps we need to do is .
    1.     Determine how/if we can create a system-level trigger on all of our Oracle databases (we currently have versions as low as 8.1.7 and up to 11.2).
    2.     The trigger will update a remote table before a shutdown or after a startup.
    3.     The remote database (which we will use for testing) is test.
    4.     The table to be updated is test.DB_STATUS
    SQL> desc p201710.db_status
    Name Null? Type
    SERVER_NAME VARCHAR2(50)
    DB_NAME VARCHAR2(50)
    DB_STATUS CHAR(1)  '1' = down, '0' = up
    STATUS_TS DATE
    5.     Create a dynamic link at the time the trigger fires to connect to this database. Do not use a TNS alias in the connector.
    6.     Query the table first to see if a record already exists with that servername+dbname combination.
    7.     If not, add a record and record the status and the sysdate. If so, just update that record. (We do not want more than 1 record for each database.)
    8.     Determine risks involved with this activity and devise a strategy to mitigate them.
    apprecited the inputs.
    Thanks
    Prakash
    Edited by: user9356823 on Jun 17, 2010 3:07 AM

  • 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 with some specific tablespaces

    I am trying to start a oracle 9i database in Linux(Redhat 8.0). During startup it says, one datafile of one of the tablespaces is missing.It can't open the database.
    How to start oracle with out that tablespace, i.e., I want to startup the database where every other tablespace except that tablespace will be up.
    I dont have any backup, neither have a archivelog .
    Can anybody suggests what to do?
    Sayan

    You can add the clause immediate if you want that the controlfile does not check the existency of that file.
    If you want to startup a database without any datafiles online you so this:
    1.- Mount the database
    2.- for each datafile that you want to set offline you have to so this : "ALTER DATABASE DATAFILE .... offline immediate"
    and so you will be able to startup the database.
    Joel Pérez

  • Oracle startup with Windows

    We have Oracle 10g (x64) installed on a Windows XP Pro x64 computer, along with ASM. When the computer reboots, both instances start up, but the database instance doesn't actually open the database on startup. So far, I've checked some registry settings (HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraDb10g_home2) to make sure that autostart was set to true (which it was). I don't know of anything else to check or change to get the database to actually fully start with Windows. We're having this problem with several computers and I'm hoping somebody can help.

    jbo5112 wrote:
    We have Oracle 10g (x64) installed on a Windows XP Pro x64 computer, along with ASM. When the computer reboots, both instances start up, but the database instance doesn't actually open the database on startup. So far, I've checked some registry settings (HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraDb10g_home2) to make sure that autostart was set to true (which it was). I don't know of anything else to check or change to get the database to actually fully start with Windows. We're having this problem with several computers and I'm hoping somebody can help.My word you've had some interesting answers. Oracle provides the ORADIM utility as mentioned already to manage oracle database services on windows. You can see the syntax by issuing the command on it's own in a cmd window - eg
    ORADIM: <command> [options].  Refer to manual.
    Enter one of the following command:
    Create an instance by specifying the following options:
         -NEW -SID sid | -SRVC srvc | -ASMSID sid | -ASMSRVC srvc [-SYSPWD pass]
    [-STARTMODE auto|manual] [-SRVCSTART system|demand] [-PFILE file | -SPFILE]
    [-SHUTMODE normal|immediate|abort] [-TIMEOUT secs] [-RUNAS osusr/ospass]
    Edit an instance by specifying the following options:
         -EDIT -SID sid | -ASMSID sid [-SYSPWD pass]
    [-STARTMODE auto|manual] [-SRVCSTART system|demand] [-PFILE file | -SPFILE]
    [-SHUTMODE normal|immediate|abort] [-SHUTTYPE srvc|inst] [-RUNAS osusr/ospass]
    Delete instances by specifying the following options:
         -DELETE -SID sid | -ASMSID sid | -SRVC srvc | -ASMSRVC srvc
    Startup services and instance by specifying the following options:
         -STARTUP -SID sid | -ASMSID sid [-SYSPWD pass]
    [-STARTTYPE srvc|inst|srvc,inst] [-PFILE filename | -SPFILE]
    Shutdown service and instance by specifying the following options:
         -SHUTDOWN -SID sid | -ASMSID sid [-SYSPWD pass]
    [-SHUTTYPE srvc|inst|srvc,inst] [-SHUTMODE normal|immediate|abort]
    Query for help by specifying the following parameters: -? | -h | -helpThe above from a 10.2 database install gives you the clue that
    1) You don't need to delete and recreate, you'll be able to edit the service.
    2) The current parameter for the password for sysdba access is -SYSPWD though in older versions it was -INTPWD.
    In addition you should certainly check the Oracle alert log for errors on attempted startup, and the oradim.log for errors encountered when the database itself is started by oardim (you'll find this in %ORACLE_HOME%\database . If I were guessing then I'd hazard a guess that the ASM instance was not fully open before the database was started. The alert log will tell you that.
    If you do find it's the ASM problem then a couple of solutions present themselves.
    1) don't rely on automatic start, but set the services to manual and then schedule a shell script at startup that starts the services using "net start servicename"
    2) Edit the OracleServiceSID to make it dependent on the ASM service using the procedure in http://support.microsoft.com/kb/193888
    Niall Litchfield
    http://www.orawin.info/

  • Oracle startup guidence reqd

    I am running Oracle 11g on 64 Windows platform.
    1 . I shutdown the database with the shutdown immediate. And i hadn't stopped the Oracle services .
    2. Then is stopped server.
    3. When I restarted the server , databases were up is tht due to not stopping Oracle services. I want to conform it.

    to change the service stop/start and automatic/manual startup of services, follow the steps
    1. Logon to Windows with Administrator rights.
    2 Click Start > Control Panel.
    3 Double-click Administrative Tools.
    4 Double-click the Services icon.
    5 Double-click the service that you want to stop or start.
    6 When the Service Properties window appears, do one of the following:
    * If the service is running, click Stop the service.
    * If the service is not running, click Start the service.
    Change the startup type which includes Automatic, Manual and Disabled:
    * Automatic starts the services at system logon,
    * Manual starts a service as required or when called from an application (according to definition, but only some of the time in practice, depending on the service),
    * Disabled completely disables the service and prevents it and its dependencies from running.
    7 Click OK.

  • Oracle StartUp Screen

    Hi,
    Windows xp.
    Database 10g,
    Forms 10g.
    I create a startup form . in when -new form instance there is on procedure take a time to execute suppose the name is P_1_StartUp;
    before this procedure the cursor go to wait window to acknowledge user that the system under running but when the system go throw this procedure the wait window hidden and oracle gray screen come up.
    The code like this.
    go_item('Blk_Wait.Dummy');
    Show_Window('Wnd_Wait');
    P_1_StartuP;
    My question is : if i can't create a progress bar at least i need to create waiting window for the user
    Thanks for help...
    Regards,

    if i can't create a progress barTake a look at the Oracle Forms 10g Demo Pack. It is a little hard to find on Oracles web site, but I've provided a direct link to the demo download. Once you've downloaded and configured the demos take a look at the "Progress Bar" demo. It utilizes a Java Bean to produce the progress bar.
    Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.

  • Oracle startup/security question

    I am new to Oracle and am being tasked with a security lockdown. One of the questions I am being asked is if this:
    The DBMS opens data files and reads configuration files at system startup. If the DBMS does
    not verify the trustworthiness of the files at startup, it is vulnerable to malicious alterations of its
    configuration or unauthorized replacement of data.
    I have searched around and cannot find anything about this. Does anyone know if there is an integrity check or other procedure that Oracle does (or can be configured to do) at startup to make sure the files are as expected?
    Thanks
    Jim

    In my opinion, if Oracle DB opens, then files are intact & can be trusted.

Maybe you are looking for