11gR2 database startup/shutdown sequences..

Hi All,
I would like to know how can we startup/shutdown the 11gr2 rac/standalone database in production environment,bcoz in 11gr2 the ocr and voting disk
are resides in ASM.In general we follow some sequence to start/stop the database like below.
SHutdown DB
+++++++++++
1.stop the application
2.stop the listener
3.stop the database
4.stop the asm and cluster services
Startup
+++++++++
1.startt the clusterservices and asm
2.start the db
3.start the listener
4.start the application
SO in 11gr2 how can we stop/start the database?
Regards,
Mugunth

Correct
Stop on each node :
emctl stop dbconsole
srvctl stop database -d db_name
srvctl stop asm -n node_name
srvctl stop nodeapps -n node_name --> in 11.2 stops only ONS and eONS because of some dependencies.
crsctl stop crs --root
Or stop csr on all nodes of clusterware:
crsctl stop cluster -all
Start : start from bottom to up

Similar Messages

How to automate database startup/shutdown in RHEL4

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

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

Services Startup/Shutdown order for system 9.2

Hi,
Can anybody provide me with the startup/shutdown sequence for the entire Hyperion Products of system 9.2.
I could find for system 9.3 in this document: hsys9_install_start_here.pdf(page 127)
But couldnt find it for system 9.2.
Regards,
James

Hi,
As you have already sequence for 9.3 on specified page, i think sequence of service start will be remain the same.
even at the time of installation you can check the service box and it will automatically start all services in correct order
Thanks
Focusthread Hyperion Trainer
[http://focusthread.com/training]

Oracle Automatic Startup & Shutdown

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

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

ORACLE DATABASE의 AUTOMATIC STARTUP/SHUTDOWN

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

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

Oracle 11gr2 Cluster startup Sequences

Hi,
What is the Sequences of starting Oracle RAC 11gr2 services?

Hi,
The Oracle 11gR2 clusterware startup sequence starting by Oracle High Availability Services Daemon ohasd
see this link for more details :)
http://www.oracle-home.ro/Oracle_Database/RAC/11gR2-Clusterware-Startup-Sequence.html
Or
From Metalink ID 1053147.1: 11gR2 Clusterware and Grid Home

Startup and shutdown sequence in RAC on Linux

I am trying to understand the start-up and shutdown sequence in 11g R2 RAC on Linux(OEL5.8).
can you please share me docs or sequence.

Hi Friend,
Example : Two node RAC. RAC1 and RAC2 instances.
Stopping RAC2 Instance :
=========================
1. Shutdown the Instance running on RAC2
2. ./srvctl stop asm -n csbppmaadbs02
3. ./srvctl stop nodeapps -n csbppmaadbs02
4. ./srvctl stop listener -n csbppmaadbs02
5. Check "./crs_stat -t"
Note 1 : Check the following also for healthy status & If any service of RAC that also we have to check.
6./crsctl check crs
CSS appears healthy
CRS appears healthy
EVM appears healthy
Starting RAC2 Instance
=========================
1 ./srvctl start nodeapps -n csbppmaadbs02
2 ./crs_stat -t
3 ./srvctl start listener -n csbppmaadbs02
4 ./srvctl start asm -n csbppmaadbs02
5. Start the Instance of RAC2
6. ./crs_stat -t
Hope it helps...
Thanks
LaserSoft

11gr2 database compatible parameter

I have a 11g r2 database and the compatible parameter was originally set to 11.2.0.0.0. I did an alter system set compatible='10.2.0.4' scope=spfiile;
Now when I try to start the database, it says control file version 11.2.0.0.0 incompatible with ORACLE version.
When I do a startup nomount and try to alter system set compatible='11.2.0.0.0' scope=spfile, I get ORA-32012: SPFILE format is inconsistent with value of COMPATIBLE parameter.
I also tried doing a create pfile from spfile and it gives me the same error. Is there anyway to fix this?
On another note, the reason why I tried this was because I tried installing Grid Control 10.2.0.3 using an existing database with this 11gr2 database. It doesn't let me proceed saying the database must be 10.2 or higher. It seems to not like my 11gr2 database version so that's why I tried changing the compatible parameter. Anyway to get around this?
Thanks for your help.

sb92075 wrote:
alter system set compatible='11.2.0.0.0' scope=spfile
I also tried doing a create pfile from spfile
As for shutdown abort and create the spfile, Why are you trying to CREATE SPFILE???????
it can't find the spfile in the dbs directory because I'm using ASM.Please make up your mind.
Either spfile exists or it does not.
Are you having a problem with the ASM instance or "normal" (OLTP?) instance?
Too bad CUT & PASTE are broken for you!Why the hostility? It was a typo. I was creating a pfile, not spfile.
Let me clarify. I am using ASM for this "normal" 11gr2 instance, so my spfile is located in a diskgroup called +DATA. When you shutdown the database and try to create a pfile from spfile, it looks for the spfile in the default directory under $ORACLE_HOME/dbs. So since I'm using ASM, my spfile is not located in this directory and oracle can't find the file.
Anyways, after some googling I answered my own question. I had to use create pfile from spfile='+DATA/emrep/spfileemrep.ora';
Thanks anyways...
But any direction on installing Grid Control using a 11gr2 existing database for the repository is appreciated.

Database startup after reboot of RAC server

Hello,
My config : 2 nodes w2k3 with 15 dbs . Oracle 10.2.0.3
I started to scheduled my rac server reboot so i follow the oracle doc to shutdown properly all db,asm,service,listener,etc...
Today one the server reboot, but some instance doesn't start (only five , and the last five in alphabetic order)
In the log :
db log : nothing just the shutdown
crs_log : the start of the 10 db but nothing for the last five !!
just a trace on one listener service :
StartResource error for ora.sqyora01.LISTENER_1522_SQYORA01.lsnr error code = 1
2010-08-11 02:56:08.000: [ CRSRES][3008]32Start of `ora.sqyora01.LISTENER_1522_SQYORA01.lsnr` on member `sqyora01` failed.
2010-08-11 02:56:08.125: [ CRSRES][3008]32Skip online resource: ora.sqyora01.LISTENER_SQYORA01.lsnr
On windows services : the OracleServiceSID service isn't started.
Any help is welcome to understand this problem.
Thanks.

user4511076 wrote:
IMO : (i am not a great oracle dba, because i have not enough time to spend with, and my collegue need really simple think to do, like startup/shutdown a database, no more investigation)Why startup/shutdown a database? I have databases that work 24x7 and uptimes of over a year. The record so far, has been over 24 months uptime (1st downtime were caused by a powerfailure to the rack cabinet). And for a database instance that runs a number of processes and deals with 100's to 1000's of inserts per second.
it's easier to view that an oracle process take more cpu and so investigate in that database what's appens. Rather than search in my v$sql table to find witch schema doing wrong thinksNot sure what you are trying to say here. Single or multiple database instances do not change how a session looks like, or how SQLs are executed.. and thus not how you troubleshoot problems. Nor does it change resource requirements, or how you address these. But multiple instances do impact resource availability and requires one to split resources amongst instances - the end result of this is less flexibility.
It's easier to affect cpu ressource to a process, rather than configuring it in oraclePlease explain.
It's easier to stop a database rather than "put offline a schema"This is a "silly" statement to make IMO. Why do you want to offline a schema? Availability of applications and data are a critical feature in today's information system landscape. So why argue the complete opposite and say it is now more complex to make something less available?
By the same token, why do you want to offline a database? A down database is even less useful than a downed server - at least you can use the downed server as a doorstop.. ;-)
And if a database crash it only affect one application.Yeah.. and these happens when? Every few minutes? Every hour? Once a day?
This is not a valid argument. Oracle instances very seldom crashes just for the heck of it. Most often it is due to incorrect o/s configuration, problematic hardware, uncertified components, old drivers, etc. Or plain old application abuse of Oracle.
There is the theorical approach and practical one : I'm not alone is that case :
http://oracledoug.com/serendipity/index.php?/archives/1339-The-Reality-Gap-3-A-Single-Instance-per-Server.html
http://www.dba-oracle.com/art_dbazine_server_consolidation.htm
I have never done RDBMS as a theoretical thing. The most dynamic table (ito SQLs against it) I have, grows by more than 450 million rows per day. This is as real world as real world gets. And that is what shapes my experience and opinion. And Burleson and I have never seen eye to eye on a number of subjects - so quoting his views on consolidation does little to persuade me to change my opinion.
have you any ideas where can i found an error message that explain why my database doesn't start ? (like not enough ressource ;-) )Troubleshooting a problem starts with a very basic principle - isolation. Isolate the layer or moving part where the problem occurs. As the other instances are running, it means that the CRS software layer is up and running, that the storage layer is up and running and so on. So the problem should be with the instance that for some reason refuses to start? Confirm this by using sqlplus to start a down instance and looking at what its alert log file says. It should have some kind of pointer to what dependency that has not been met.

Database startup issue

Dear all
when i am going to startup the database i am getting this
below mentioned issue
database is mounted for your information.
Unix process pid: 5402, image: [email protected] (TNS V1-V3)
*** SERVICE NAME:(SYS$USERS) 2010-05-23 23:04:28.988
*** SESSION ID:(159.3) 2010-05-23 23:04:28.988
Error in executing triggers on database startup
*** 2010-05-23 23:04:28.988
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-06521: PL/SQL: Error mapping function
ORA-06512: at "LBACSYS.LBAC_EVENTS", line 34
ORA-06512: at line 2
*** 2010-05-23 23:04:48.636
*** 2010-05-23 23:04:48.636 60679 kcrr.c
ARCH: Archival disabled due to shutdown: 1089
*** 2010-05-23 23:04:49.638 60679 kcrr.c
ARCH: Archival disabled due to shutdown: 1089
pls. let me reason for the issue.
Tks/regs
Sunrise~

Error in executing triggers on database startup
*** 2010-05-23 23:04:28.988
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-06521: PL/SQL: Error mapping function
ORA-06512: at "LBACSYS.LBAC_EVENTS", line 34
ORA-06512: at line 2
*** 2010-05-23 23:04:48.636
*** 2010-05-23 23:04:48.636 60679 kcrr.c
ARCH: Archival disabled due to shutdown: 1089
It appears that a startup trigger has a bug.
01089, 00000, "immediate shutdown in progress - no operations are permitted"
// *Cause: The SHUTDOWN IMMEDIATE command was used to shut down
// a running ORACLE instance, so your operations have been
// terminated.
// *Action: Wait for the instance to be restarted, or contact your DBA.

Database got shutdown reason unknown

Hi,
My database got shutdown. We are unable to know the reason behind this.
Its 10g database on AIX 5.3 server.
Below is the entry from alert log.
Thread 1 advanced to log sequence 264605 (LGWR switch)
Current log# 5 seq# 264605 mem# 0: /oracle/redolog/neonprd/redo05a.log
Current log# 5 seq# 264605 mem# 1: /oracle/redolog02/neonprd/redo05b.log
Mon Sep 10 14:04:01 2012
Immediate Kill Session#: 1870, Serial#: 17917
Immediate Kill Session: sess: 7000005835afb08 OS pid: 5845450
Mon Sep 10 14:04:01 2012
Process OS id : 5845450 alive after kill
Errors in file
Mon Sep 10 14:04:21 2012
Immediate Kill Session#: 1998, Serial#: 27337
Immediate Kill Session: sess: 7000005875c6cc0 OS pid: 6263044
Mon Sep 10 14:04:21 2012
Process OS id : 6263044 alive after kill
Errors in file
Mon Sep 10 14:04:32 2012
alter database commit to switchover to primary
Mon Sep 10 14:04:32 2012
ALTER DATABASE SWITCHOVER TO PRIMARY (neonprd)
Mon Sep 10 14:04:32 2012
ORA-16109 signalled during: alter database commit to switchover to primary...
Mon Sep 10 14:04:32 2012
ALTER SYSTEM SET log_archive_dest_state_2='enable' SCOPE=BOTH;
Starting background process EMN0
Shutting down instance: further logons disabled
EMN0 started with pid=159, OS id=5444040
Mon Sep 10 14:04:37 2012
Completed checkpoint up to RBA [0x4099d.2.10], SCN: 43879290652
Mon Sep 10 14:04:37 2012
Stopping background process CJQ0
Mon Sep 10 14:04:37 2012
Stopping background process QMNC
Mon Sep 10 14:04:38 2012
Stopping background process MMNL
Mon Sep 10 14:04:39 2012
Stopping background process MMON
Mon Sep 10 14:04:40 2012
Shutting down instance (immediate)
License high water mark = 399
Mon Sep 10 14:04:40 2012
Stopping Job queue slave processes, flags = 7
Mon Sep 10 14:04:40 2012
Process OS id : 7172580 alive after kill
Errors in file /oracle/admin/neonprd/udump/neonprd_ora_6672700.trc
Mon Sep 10 14:04:44 2012
Waiting for Job queue slaves to complete
Mon Sep 10 14:04:44 2012
Job queue slave processes stopped
Mon Sep 10 14:05:49 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:06:14 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:06:21 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:07:02 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:07:46 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:08:46 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:09:23 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:10:01 2012
Starting ORACLE instance (normal)
Mon Sep 10 14:10:07 2012
Incremental checkpoint up to RBA [0x4099d.62afd.0], current log tail at RBA [0x4099d.62b0c.0]
Mon Sep 10 14:15:27 2012
Shutting down instance
License high water mark = 399
Instance terminated by USER, pid = 7000574
Mon Sep 10 14:15:49 2012
Starting ORACLE instance (normal)
sskgpgetexecname failed to get name
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =242
LICENSE_MAX_USERS = 0
SYS auditing is enabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 2000
sessions = 2205
sga_max_size = 23622320128
__shared_pool_size = 3674210304
shared_pool_size = 3674210304
__large_pool_size = 16777216
large_pool_size = 16777216
__java_pool_size = 117440512
java_pool_size = 50331648
__streams_pool_size = 16777216
streams_pool_size = 16777216
nls_date_format = MM-DD-YYYY HH24:MI:SS
nls_length_semantics = BYTE
filesystemio_options = setall
resource_manager_plan =
sga_target = 22548578304
control_files = /oracle/data/neonprd/control01.ctl, /oracle/data/neonprd/control02.ctl, /oracle/data/neonprd/control03.ctl
db_block_size = 8192
__db_cache_size = 18656264192
db_cache_size = 8002732032
db_writer_processes = 16
compatible = 10.2.0.3.0
log_archive_dest_1 = location=use_db_recovery_file_dest
log_archive_dest_2 = service=standby reopen=120 max_connections=3
log_archive_dest_state_1 = ENABLE
log_archive_dest_state_2 = enable
log_archive_max_processes= 10
log_archive_min_succeed_dest= 1
standby_archive_dest =
log_archive_trace = 0
fal_client = PRIMARY
fal_server = STANDBY
log_buffer = 63009792
archive_lag_target = 0
db_files = 200
db_file_multiblock_read_count= 16
db_recovery_file_dest = /oracle/flash_recovery
db_recovery_file_dest_size= 1181116006400
standby_file_management = AUTO
fast_start_mttr_target = 300
log_checkpoints_to_alert = TRUE
undo_management = AUTO
undo_tablespace = UNDOTBS1
undo_retention = 3600
remote_login_passwordfile= EXCLUSIVE
audit_sys_operations = TRUE
db_domain = in.startv.com
service_names = neonprd.in.startv.com
shared_servers = 0
job_queue_processes = 10
cursor_sharing = EXACT
parallel_max_servers = 0
background_dump_dest = /oracle/admin/neonprd/bdump
user_dump_dest = /oracle/admin/neonprd/udump
core_dump_dest = /oracle/admin/neonprd/cdump
audit_file_dest = /oracle/admin/neonprd/adump
audit_trail = NONE
db_name = neonprd
open_cursors = 1500
parallel_adaptive_multi_user= TRUE
optimizer_index_cost_adj = 25
optimizer_index_caching = 90
query_rewrite_enabled = TRUE
pga_aggregate_target = 6442450944
skip_unusable_indexes = TRUE
allowlevel_without_connect_by= TRUE
aq_tm_processes = 1
awrflush_threshold_metrics= TRUE
PMON started with pid=2, OS id=1204390
PSP0 started with pid=3, OS id=966732
MMAN started with pid=4, OS id=1003604
DBW0 started with pid=5, OS id=946294
DBW1 started with pid=6, OS id=909508
DBW2 started with pid=7, OS id=7000332
DBW3 started with pid=8, OS id=897104
DBW4 started with pid=9, OS id=7233880
DBW5 started with pid=10, OS id=5828952
DBW6 started with pid=11, OS id=7213314
DBW7 started with pid=12, OS id=7139790
DBW8 started with pid=13, OS id=6844750
DBW9 started with pid=14, OS id=6648146
DBWa started with pid=15, OS id=851976
DBWb started with pid=16, OS id=872484
DBWc started with pid=17, OS id=815254
DBWd started with pid=18, OS id=790652
DBWe started with pid=19, OS id=774152
DBWf started with pid=20, OS id=745636
LGWR started with pid=21, OS id=573668
CKPT started with pid=22, OS id=1171514
SMON started with pid=23, OS id=553024
RECO started with pid=24, OS id=1159352
CJQ0 started with pid=25, OS id=6639948
MMON started with pid=26, OS id=6394246
MMNL started with pid=27, OS id=1028254
Mon Sep 10 14:15:51 2012
ALTER DATABASE MOUNT
Mon Sep 10 14:15:55 2012
Setting recovery target incarnation to 1
Mon Sep 10 14:15:55 2012
Successful mount of redo thread 1, with mount id 863646487
Mon Sep 10 14:15:55 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Mon Sep 10 14:15:55 2012
ALTER DATABASE OPEN
Mon Sep 10 14:15:56 2012
Beginning crash recovery of 1 threads
parallel recovery setup failed: using serial mode
Mon Sep 10 14:15:56 2012
Started redo scan
Mon Sep 10 14:15:56 2012
Completed redo scan
0 redo blocks read, 0 data blocks need recovery
Mon Sep 10 14:15:56 2012
Started redo application at
Thread 1: logseq 264605, block 404238, scn 43879394962
Mon Sep 10 14:15:56 2012
Recovery of Online Redo Log: Thread 1 Group 5 Seq 264605 Reading mem 0
Mem# 0: /oracle/redolog/neonprd/redo05a.log
Mem# 1: /oracle/redolog02/neonprd/redo05b.log
Mon Sep 10 14:15:56 2012
Completed redo application
Mon Sep 10 14:15:56 2012
Completed crash recovery at
Thread 1: logseq 264605, block 404238, scn 43879414963
0 data blocks read, 0 data blocks written, 0 redo blocks read
Mon Sep 10 14:15:56 2012
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=29, OS id=1200370
ARC1 started with pid=30, OS id=6341016
ARC2 started with pid=31, OS id=6271472
ARC3 started with pid=32, OS id=1130568
ARC4 started with pid=33, OS id=6234458
ARC5 started with pid=34, OS id=1179696
ARC6 started with pid=35, OS id=1106070
ARC7 started with pid=36, OS id=5890556
ARC8 started with pid=37, OS id=1089544
Mon Sep 10 14:15:57 2012
ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC3: Archival started
ARC4: Archival started
ARC5: Archival started
ARC6: Archival started
ARC7: Archival started
ARC9 started with pid=38, OS id=1036378
Mon Sep 10 14:15:57 2012
ARC8: Archival started
ARC9: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
Mon Sep 10 14:15:57 2012
Thread 1 advanced to log sequence 264606 (thread open)
Thread 1 opened at log sequence 264606
Current log# 6 seq# 264606 mem# 0: /oracle/redolog/neonprd/redo06a.log
Current log# 6 seq# 264606 mem# 1: /oracle/redolog02/neonprd/redo06b.log
Successful open of redo thread 1
Mon Sep 10 14:15:57 2012
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Mon Sep 10 14:15:57 2012
ARC3: Becoming the heartbeat ARCH
Mon Sep 10 14:15:57 2012
SMON: enabling cache recovery
Mon Sep 10 14:15:57 2012
db_recovery_file_dest_size of 1126400 MB is 4.99% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon Sep 10 14:15:58 2012
Successfully onlined Undo Tablespace 1.
Mon Sep 10 14:15:58 2012
SMON: enabling tx recovery
Mon Sep 10 14:15:58 2012
Database Characterset is WE8MSWIN1252
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 28
replication_dependency_tracking turned off (no async multimaster replication found)
Mon Sep 10 14:16:00 2012
Incremental checkpoint up to RBA [0x4099e.3.0], current log tail at RBA [0x4099e.a3.0]
Mon Sep 10 14:16:00 2012
Starting background process QMNC
QMNC started with pid=40, OS id=5837066
Mon Sep 10 14:16:02 2012
Completed: ALTER DATABASE OPEN
Mon Sep 10 14:18:57 2012
Immediate Kill Session#: 2016, Serial#: 77
Immediate Kill Session: sess: 70000058f5d0698 OS pid: 6582596
Mon Sep 10 14:18:57 2012
Process OS id : 6582596 alive after kill
Errors in file
Mon Sep 10 14:24:30 2012
Beginning log switch checkpoint up to RBA [0x4099f.2.10], SCN: 43879588218
Mon Sep 10 14:24:30 2012
Thread 1 advanced to log sequence 264607 (LGWR switch)
Current log# 1 seq# 264607 mem# 0: /oracle/redolog/neonprd/redo01a.log
Current log# 1 seq# 264607 mem# 1: /oracle/redolog02/neonprd/redo01b.log
Mon Sep 10 14:29:33 2012
Completed checkpoint up to RBA [0x4099f.2.10], SCN: 43879588218
Mon Sep 10 14:32:01 2012
Beginning log switch checkpoint up to RBA [0x409a0.2.10], SCN: 43879769830
Mon Sep 10 14:32:01 2012
Thread 1 advanced to log sequence 264608 (LGWR switch)
Current log# 2 seq# 264608 mem# 0: /oracle/redolog/neonprd/redo02a.log
Current log# 2 seq# 264608 mem# 1: /oracle/redolog02/neonprd/redo02b.log

Atiq wrote:
How can i get the os user, db user, ip address of machine from where shutdown was issued???I can't say that I ever actually did this, but DBMS_LOGMNR might provide clues.
The list of possible culprits is limited to those can login AS SYSDBA or SYSOPER.
SYSDBA logins are audited for V10+ by default

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

New 11gR2 DB Startup Problem In Finding pfile

I created a new 11gR2 database yesterday. First I installed the grid infrastructure and chose the followed the instructions for "Installing and Configuring Grid Infrastructure For a Standalone Server". The ASM DATA disk group was successfully created. Then I successfully used the asmca tool to add a FRA disk group.
Here' s the current crs status, with me logged in as user "grid":
-bash-3.00$ crs_stat -t -v
Name Type R/RA F/FT Target State Host
ora.DATA.dg ora....up.type 0/5 0/ ONLINE ONLINE hostsrv1
ora.FRA.dg ora....up.type 0/5 0/ ONLINE ONLINE hostsrv1
ora....ER.lsnr ora....er.type 0/5 0/ ONLINE ONLINE hostsrv1
ora.asm ora.asm.type 0/5 0/ ONLINE ONLINE hostsrv1
ora.cssd ora.cssd.type 0/5 0/5 ONLINE ONLINE hostsrv1
ora.diskmon ora....on.type 0/10 0/5 ONLINE ONLINE hostsrv1
Looks good.
Then I try to bring up the database that successfully created last night. I log in as user "oracle" and try to bring the DB up:
ORACLE_SID=hostsrv1
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db
-bash-3.00$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Wed May 12 11:06:43 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup;
ORA-01078: failure in processing system parameters
LRM-00109: could not open parameter file '/u01/app/oracle/product/11.2.0/db/dbs/inithostsrv1.ora'
SQL>
It's true, the pfile is missing from that directory. If I understand correctly (new to R2) it should be there and be pointing to an spfile in the +DATA diskgroup. Does that sound right? I guess I should try to create a pfile that points to the location of the spfile but I need to know how to obtain that information (location of spfile) from the ASM instance.
Thanks for any help :-)

If you are sure you spfile should be in ASM diskgroup, then you can use utility asmcmd for connecting to this ASM instance, and later by browsing ASM catalog structure you can find the location of your spfile.

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

Issue with database startup

hi,
getting below error on database startup.
log is attached from alert log file.
Wed Nov 16 14:24:20 2011
ALTER DATABASE MOUNT
Wed Nov 16 14:24:20 2011
ORA-00202: control file: '/oradata2/ctftdb2/data/controlctftdb201.ctl'
ORA-27086: unable to lock file - already in use
SVR4 Error: 11: Resource temporarily unavailable
Additional information: 8
Additional information: 5457
Wed Nov 16 14:24:20 2011
ORA-205 signalled during: ALTER DATABASE MOUNT...

user12052679 wrote:
SID is ctftdb2
bash-3.00$ ps -ef | grep pmon
oracle 5992 1 0 14:24:19 ? 0:07 ora_pmon_ctftdb2
oracle 1680 1 0 May 25 ? 193:47 ora_pmon_hddb
oracle 5445 1 0 Jul 19 ? 287:57 ora_pmon_ctftdb2
oracle 14334 28506 0 16:28:22 pts/3 0:00 grep pmonyour instance is already up, why trying to start again? are you not aware as it is already running?
First shutdown the current instance which you facing errors to mount database
export ORACLE_SID=ctftdb2
sqlplus / as sysdba
select name,open_mode from v$database;Might it is already either mounted or opened. post output here

11gR2 database startup/shutdown sequences..

Similar Messages

Maybe you are looking for