STARTUP/SHUTDOWN의 PROCEDURE와 종류

제품 : ORACLE SERVER
작성날짜 : 2002-04-12
STARTUP/SHUTDOWN의 PROCEDURE와 종류
===================================
Purpose
가장 기본적인 Oracle의 startup/shutdown 각 mode와 그 특징에 대해 알아보자.
Explanation
ORACLE을 사용하려면 먼저 데이타베이스를 기동하여야 한다.
ORACLE의 기동은 startup, 기동 중인 ORACLE을 사용하지 못하도록
운영을 중지하도록 하는 것은 shutdown command를 이용해 이루어진다.
여기에서는 startup, shutdown 시의 procedure와 startup, shutdown의
종류에 대해 설명한다.
1. STARTUP PROCEDURE
stratup은 3단계의 procedure로 구성된다.
1) 인스턴스 start
ORACLE을 운영하기 위한 background process(dbwr, lgwr, smon, pmon 등)를
생성하며 또한 init<SID>.ora의 parameter 값들을 읽어 SGA도 allocate한다.
startup 시 이 procedure까지 수행하기 위하여는 sqldba(v7.2까지) 또는
svrmgrl(v7.3 이상)에서 startup nomount를 하면 된다.
2) mount the database
인스턴스 start 후 데이타베이스를 mount하는 단계로 mount에서는 control
file을 open한다. 이 단계까지만 start하는 경우에는 특별한 데이타베이스
유지 보수 작업이 필요시 수행한다. 특별한 데이타베이스 유지 보수 작업이란
redo log의 add, rename, media recovery의 수행 등의 작업을 의미한다.
startup 시 mount 단계까지 수행하려면 startup mount를 수행하면 된다.
1)에서 인스턴스를 start한 후 mount 단계로 넘어가려면 alter database
mount를 수행하면 된다.
3) open the database
데이타베이스의 open은 mount 후 데이타베이스를 사용할 수 있는 환경으로
만들어 주는 단계로서 모든 online datafile과 online redo log file을 open하고
사용할 수 있도록 하여 준다. 데이타베이스가 중지된 상태에서 한번에 open까지
모두 수행하기 위해서는 startup만 하면 된다. 2)에서처럼 데이타베이스를 mount
후 open 시에는 alter database open을 수행하면 된다. (단, 인스턴스 start에서
바로 database open을 수행할 수 없다.)
2. STARTUP의 종류
startup은 sqldba(v7.2까지) 또는 svrmgrl(v7.3 이상)에서 수행한다.
1) startup
이는 일반적인 ORACLE 기동 방법으로 startup이 완료되면 모든 user가
데이타베이스를 access할 수 있다.
2) startup restrict
일반 user의 ORACLE 사용을 제한하기 위하여 startup하는 방법으로
ORACLE user중 create session+restricted session이라는 system privilege를
갖고 있는 user만이 데이타베이스를 사용 할 수 있다. 이는 데이타베이스 구조를
조정하거나 data의 export, import시 등 일반 user의 사용을 제한하는 경우에
사용한다.
3) startup force
shutdown normal 또는 shutdown immediate시 정상적으로 종료되지 않는 경우
데이타베이스의 인스턴스를 강제로 kill시키고 startup하도록 한다.
4) startup parallel
OPS 환경으로 데이타베이스를 운영하는 경우 하나의 데이타베이스를 여러 개의
node에서 공유한다. 이때 여러 인스턴스에서 데이타베이스를 공유하기 위해서는
startup parallel로 기동 하여야 한다. 1)의 startup은 exclusive mode로서
OPS로 데이타베이스 환경이 되어 있더라도 startup만 하면 여러개의 인스턴스가
하나의 데이타베이스를 공유할 수 없다. 이는 데이타베이스가 exclusive mode로
기동되었기 때문이다. OPS에서 데이타베이스를 공유하기 위해서는 반드시
startup parallel로 기동하여야 한다.
3. SHUTDOWN PROCEDURE
shutdown은 데이타베이스의 운영을 중단하기 위해 수행하는 것으로 startup
procedure와는 반대로 작동한다. 즉 먼저 데이타베이스를 close하고 두번째
데이타베이스를 dismount하며 마지막으로 인스턴스를 shutdown 한다.
4. SHUTDOWN의 종류
shutdown도 startup처럼 sqldba(v7.2까지), svrmgrl(v7.3 이상)에서 수행한다.
1)shutdown
이는 일반적인 shutdown 방법으로 shutdown이 진행 중에는 새로운 user가
데이타베이스에 세션을 맺을 수 없으며 또한 기존에 connect되어 있는 user가
있는지 확인하여 connect된 user가 없다면 데이타베이스를 shutdown하고 user가
있다면 connect된 user가 disconnect될 때까지 shutdown을 하지 않고 기다린다.
2) shutdown immediate
현재 데이타베이스를 사용 중인 user가 있지만 데이타베이스를 shutdown해야
하는 경우 shutdown immedaite를 수행한다. shutdown immediate를 수행하면
현재 진행 중인 SQL이 중단되고 commit되지 않은 transaction을 rollback하고
connect되어 있던 user를 강제로 disconnect시키고 shutdown을 수행하게 된다.
단, 다량의 data를 update하는 작업을 수행 중 shutdown immediate를 수행하면
곧바로 database가 shutdown되지 않는다.
이는 rollback하는 데 많은 시간을 소비하기 때문이다.
3) shutdown abort
connect된 user가 long transaction을 수행하고 있지만 급하게 데이타베이스를
shutdown 하여야 하는 경우 shutdown abort를 하게 된다. shutdown abort를
수행하면 ORACLE 인스턴스를 바로 shutdown하므로 shutdown immediate와는 달리
commit되지 않은 transaction들을 rollback하지 않고 데이타베이스를 shutdown
한다. 그러므로, long transaction이 있더라도 빨리 shutdown 할 수 있다.
단, shutdown abort는 rollback하지 않고 shutdown하므로 데이타베이스에
이상 현상을 초래할 가능성을 가지고 있다.

Similar Messages

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,

Startup and shutdown procedure of OBIEE in linux

I'm new to OBIEE. Can you please tell me the procedure of startup and shutdown procedure of OBIEE services?
After starting the OBIEE services, what are the checklist I've to go through to make sure that OBIEE is up and running
Thanks
Edited by: 998932 on May 20, 2013 6:24 AM

You can follow the steps mentioned at http://lamont-consulting.com/index.php/blog/obiee/11g/117-stop-and-start-obiee-11g-linux.
Pls mark correct or helpful.

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

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

HOWTO: Startup/Shutdown Sounds in Openbox

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

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

I am getting this iCloud error message at pc startup: The procedure entry point_objc_init_image could not be found in the dll

I am getting an iCould error message at PC startup: The procedure entry point_objc_init_image could not be found in the dynamic.....

i ahve same problem

Automating Weblogic Startup/Shutdown on Linux

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

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

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!

Grepping for startup/shutdown in the logs

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

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

Slow startup/shutdown on WL

Hi,
We're having a performance issue starting/shutting down weblogic 8.1.1 on Solaris 8 on a Sunfire V240 with 4Gb of memory. it takes an average of 15-20 minutes to start the application using command line start.
Here is some background on the environment:
A. Start with java args :
-Xms1536m -Xmx1536m MaxPermSize=128m NewSize=256m MaxNewSize=256m SurvivorRation=8.
B. There is a cron job that starts/stops then imports at night. The shutdown is also slow, so after 2 minutes of attempted FORCESHUTDOWN, we do a 'kill -9' on the process. My guess is that there is still a transcation that needs to finish ( some are fairly large ), and so FORCESHUTDOWN doesnt complete in 2min.
C. There are multiple applications on the server, but even if we remove one of them ( the second ), startup/shutdown takes the same time to start. The second app depends on the first, so we havent removed the first one
D. There have been some database issues as well, running out of database connections. This is due to Connections not being closed, and we are correcting that issue right now, and is not complete.
E. Most of the time, the logs hang on the last statement below in the logs. However, I don't see any consistency in what follows the BEA-101133 message in the logs.
I apologize in advance for asking more than one item in a post, but I have multiple questions that I believe might be related to the slow startup:
1. Will running 'kill -9' on the process have an impact on the startup of WL, as it is trying to recover or restore connections or resources?
2. Once the database connection issues are cleared up ( working on them now), should startup time increase?
3. Any other suggestions to increase the startup time of WL?
####<Apr 26, 2008 6:44:13 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:13 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:14 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:16 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for
connection in specified pool "ds.oem".>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool
"ds.oem", out of which "10" are available and "0" are unavailable.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.oem.>
####<Apr 26, 2008 6:44:17 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.im for
Pool ds.im.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.nice for Pool ds.nice.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.core for Pool ds.core.>
####<Apr 26, 2008 6:44:18 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.oem for Pool ds.oem.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.wf for
Pool ds.wf.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory
"jms.ds.TopicConnectionFactory" is started.>
####<Apr 26, 2008 6:44:19 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040054> <JMSServer "JMServ". No persistent store
configured.>
####<Apr 26, 2008 6:44:20 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040321> <JMSServer "JMServ" is resuming.>
####<Apr 26, 2008 6:44:21 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040010> <JMSServer "JMServ" configured no session pools.>
####<Apr 26, 2008 6:44:22 AM EST> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040109> <JMSServer "JMServ" is started.>
####<Apr 26, 2008 6:44:22 AM EST> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mysrv.>
tializing Web server mysrv.>

First of all I apologize for the late response, and thank you for the replies.
Here is the WebLogic log file from startup. Note there is a lag of between 10:20 and 11:13. I'm not sure of the cause of this, and any hints or resolutions would be appreciated.
Looks like the slowness is occuring when initializing the web server. Both the Apache web server and Weblogic application server reside on the same machine, so it's not a firewall issue.
####<May 11, 2008 10:11:36 AM GMT> <Notice> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000327> <Starting WebLogic Admin Server "mysrv" for domain "jmssrv">
####<May 11, 2008 10:11:36 AM GMT> <Info> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000214> <WebLogic Server "mysrv" version:
WebLogic Temporary Patch for CR105892 05/29/2003 16:47:19
WebLogic Server 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009
WebLogic XMLX Module 8.1 SP1 Fri Jun 20 23:06:40 PDT 2003 271009 (c) 1995, 1996, 1997, 1998 WebLogic, Inc.
(c) 1999, 2000, 2001 BEA Systems, Inc.>
####<May 11, 2008 10:11:36 AM GMT> <Info> <WebLogicServer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000215> <Loaded License : /opt/oss/bea/license.bea>
####<May 11, 2008 10:11:36 AM GMT> <Info> <RJVM> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000570> <Network Configuration for Channel "mysrv"
Listen Address          *
Public Address          N/A
Http Enabled          true
Tunneling Enabled     false
Outbound Enabled     false
Admin Traffic Enabled     true>
####<May 11, 2008 10:11:37 AM GMT> <Debug> <RJVM> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000571> <Network Configuration Detail for Channel "mysrv"
Channel Weight          50
Accept Backlog          50
Login Timeout          5000ms
Max Message Size     10000000
Message Timeout     60s
Idle Timeout          65s
Tunneling Timeout     40s
Tunneling Ping          45s>
####<May 11, 2008 10:11:39 AM GMT> <Info> <XML> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-130036> <Initializing XMLRegistry.>
####<May 11, 2008 10:11:41 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001135> <Initializing the JDBC service.>
####<May 11, 2008 10:11:48 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001137> <Initialization complete.>
####<May 11, 2008 10:11:51 AM GMT> <Info> <Connector> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-190000> <Initializing J2EE Connector Service>
####<May 11, 2008 10:11:56 AM GMT> <Info> <Connector> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-190001> <J2EE Connector Service initialized successfully>
####<May 11, 2008 10:11:56 AM GMT> <Info> <IIOP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-002014> <IIOP subsystem enabled.>
####<May 11, 2008 10:11:57 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040090> <Deployed 5 default connection factories.>
####<May 11, 2008 10:11:58 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040305> <JMS service is initialized and in standby mode.>
####<May 11, 2008 10:12:00 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101128> <Initializing HTTP services.>
####<May 11, 2008 10:12:00 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101133> <Initializing Web server mysrv.>
####<May 11, 2008 10:12:01 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101052> <[HTTP mysrv] Initialized>
####<May 11, 2008 10:12:01 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101135> <mysrv is the default Web server.>
####<May 11, 2008 10:12:02 AM GMT> <Info> <J2EE> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-160037> <J2EE service initializing.>
####<May 11, 2008 10:12:04 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149207> <Initializing.>
####<May 11, 2008 10:12:05 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:06 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:07 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:10 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module console of application console is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module console of application console successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:12:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:02 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:04 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal2 of application wl_management_internal2 is transitioning from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal2 of application wl_management_internal2 successfully transitioned from unprepared to prepared on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal1 of application wl_management_internal1 is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal1 of application wl_management_internal1 successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:08 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddiexplorer of application uddiexplorer is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:09 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddiexplorer of application uddiexplorer successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module console of application console is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:11 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module console of application console successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module uddi of application uddi is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module uddi of application uddi successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149059> <Module wl_management_internal2 of application wl_management_internal2 is transitioning from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149060> <Module wl_management_internal2 of application wl_management_internal2 successfully transitioned from prepared to active on server mysrv.>
####<May 11, 2008 10:19:14 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149208> <Initialization Complete.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JTA> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-110441> <Opening transaction log with driver version "j1.0" and synchronous write policy "Cache-Flush". For information on synchronous write policies, refer to the weblogic.management.configuration.ServerMBean javadoc or console online help.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001138> <Resuming the JDBC service.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001140> <Resume complete.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultXAConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "QueueConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "MessageDrivenBeanConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "DefaultConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040108> <User connection factory "TopicConnectionFactory" is started.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <JMS> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-040306> <JMS service is active now.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101129> <Initializing the Web application container.>
####<May 11, 2008 10:19:15 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101239> <HTTP log rotation is date based for the Web server: mysrv.>
####<May 11, 2008 10:19:17 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101243> <HTTP log rotation scheduled to begin at: Mon May 12 10:19:17 GMT 2008. Rotation taking place every: 1440 minutes for the Web server: mysrv.>
####<May 11, 2008 10:19:17 AM GMT> <Info> <HTTP> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-101051> <[HTTP mysrv] started>
####<May 11, 2008 10:19:17 AM GMT> <Info> <WebService> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-220031> <The server does not support reliable SOAP messaging.>
####<May 11, 2008 10:19:18 AM GMT> <Info> <WebService> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-220027> <Web Service reliable agents are started on the server.>
####<May 11, 2008 10:19:18 AM GMT> <Info> <Deployer> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-149209> <Resuming.>
####<May 11, 2008 10:19:18 AM GMT> <Notice> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <The SNMP trap version is 1>
####<May 11, 2008 10:19:18 AM GMT> <Info> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <SNMP agent is initializating ...>
####<May 11, 2008 10:19:18 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.core" will be tested every "30" seconds.>
####<May 11, 2008 10:19:19 AM GMT> <Info> <SNMP Agent> <myservername> <mysrv> <SNMP Service Thread> <<WLS Kernel>> <> <000000> <SNMP Agent Initialization Complete.
Sending generic coldStart trap ...>
####<May 11, 2008 10:19:24 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:25 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:26 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:26 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:27 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:28 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:29 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:32 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.core" created.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.core".>
####<May 11, 2008 10:19:33 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.core", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.core.>
####<May 11, 2008 10:19:33 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.wf" will be tested every "30" seconds.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.wf" created.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.wf".>
####<May 11, 2008 10:19:34 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "1" resources for pool "ds.wf", out of which "1" are available and "0" are unavailable.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.wf.>
####<May 11, 2008 10:19:34 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.nice" will be tested every "30" seconds.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:36 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:37 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:37 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:38 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:39 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:39 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:45 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:45 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:46 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:46 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:47 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.nice" created.>
####<May 11, 2008 10:19:47 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.nice".>
####<May 11, 2008 10:19:47 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.nice", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:19:48 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.nice.>
####<May 11, 2008 10:19:48 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.oem" will be tested every "30" seconds.>
####<May 11, 2008 10:19:52 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:52 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:53 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:54 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:56 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:19:57 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:19:57 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:00 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:00 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.oem" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.oem".>
####<May 11, 2008 10:20:01 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.oem", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.oem.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000626> <Free resources in pool "ds.im" will be tested every "30" seconds.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:01 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:02 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:02 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:04 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:08 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:09 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:13 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:14 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:14 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:15 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:16 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001072> <Connection for XA pool "ds.im" created.>
####<May 11, 2008 10:20:16 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001133> <Statement caching not enabled for connection in specified pool "ds.im".>
####<May 11, 2008 10:20:17 AM GMT> <Info> <Common> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-000628> <Created "10" resources for pool "ds.im", out of which "10" are available and "0" are unavailable.>
####<May 11, 2008 10:20:17 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001124> <Created Connection Pool named ds.im.>
####<May 11, 2008 10:20:18 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <>
<BEA-001121> <Created TX Data Source named ds.nice for Pool ds.nice.>
####<May 11, 2008 10:20:19 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <BEA-001121> <Created TX Data Source named ds.wf for Pool ds.wf.>
####<May 11, 2008 10:20:19 AM GMT> <Info> <JDBC> <myservername> <mysrv> <main> <<WLS Kernel>> <> <B

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

How to find history of instance startups/shutdowns?

Hi,
how can i find history of instance startups/shutdowns ?
Thanks in advance.

hi,
You can find instance startup/shutdown history in alert log file.
Follow the below steps.
1. SQL> show parametr back;
background_dump_dest string /u02/oracle/admin/test_db/bdump
This is the location of my bdump folder.
2. Got to the location.
3. ls alert*
alert_test_db.log
Regards,
Ranjan

STARTUP/SHUTDOWN의 PROCEDURE와 종류

Similar Messages

Maybe you are looking for