Instance startup / shutdown (Solaris 9 Oracle 9i)

Morning Guys, How was the weekend? Hope everybody enjoyed.
I have 2 instances running in one machine. I have just performed a shutdown but only 1 intance is down the other one is still running, how do I shutdown the other one as well. The same goes for Startup can I perform the startup for both of the instances seperately.
Thank you.

Hi,
Are the 2 instances running on 2 databases?
if yes simply connect to each database by user sys@service_name and shut it down.
conn sys/sys_pass@service_name1 as sysdba
shutdown immediate;
conn sys/sys_pass@service_name2 as sysdba
shutdown immediate;
Regards;

Similar Messages

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

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

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

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

Oracle 10g automatic startup in Solaris 10

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

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

While startup ora -01092: ORACLE instance terminated. Disconnection forced

Hi all,
I'm using Enterprise Linux Red hat 5 (OS), oracle 10g Release 2 (10.2.0.1.0)
while startup the database I'm getting below error message.
SQL> startup pfile='/opt/oracle/admin/ssharp/pfile/init.ora.33201013513' mount;
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size 1220432 bytes
Variable Size 486539440 bytes
Database Buffers 1644167168 bytes
Redo Buffers 15556608 bytes
Database mounted.
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01092: ORACLE instance terminated. Disconnection forced
In alert log file having message, Redo log file s corrupted.
I try to recover the redo log,using
allow_resetlogs_corruption=True parameter in pfile.
and start the DB in mount stage,and
restore database;
alter database open resetlogs;
Using this method i got the same error ora - 01092
and tried to rman incomplete recovery i cant solve issue
*RMAN> run
2> {
3> set until sequence 2284 thread 1;
4> restore database;
5> recover database;
6> alter database open resetlogs;
7> }
executing command: SET until clause
using target database control file instead of recovery catalog
Starting restore at 25-APR-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=761 devtype=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: sid=760 devtype=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: sid=758 devtype=DISK
creating datafile fno=20 name=/northeast/oradata/ssharp/main/main03.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 04/25/2011 13:42:35
ORA-01119: error in creating database file '/northeast/oradata/ssharp/main/main03.dbf'
ORA-27038: created file already exists
Additional information: 1
RMAN> shut immediate
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, connect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, library, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, validate"
RMAN-01008: the bad identifier was: shut
RMAN-01007: at line 1 column 1 file: standard input*
and also i cleared that redolog content,after that also i tried to up the database with resetlog option.but i can't solve...
can any one guide me
Thanks in advance

Hi user;
Please see below note which could be helpful on your issue:
database not starting up with errors ORA-01092 ORA-24324 ORA-01041 [ID 779356.1]
Regard
Helios

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

Automatic startup/shutdown script - 3 Oracle Home

Hi All,
We have a server which has 3 Oracle Home - 8i/9i/10g.
So i am confused about configuring automatic startup/shutdown scripts.
Can you guys please let me know how to setup automatic startup/shutdown for these multiple Oracle Homes.
Thanks,
Kumar.

Bellow is a HP-UX script that can help. Create three scripts like oracle8, oracle9, oracle10 with correct path values. and than decide the runlevels and create soft links for the scripts you created, for example;
Under /sbin/rc3.d
ln -s /sbin/init.d/oracle10 S999oracle10
Under /sbin/rc1.d and /sbin/rc2.d
ln -s /sbin/init.d/oracle10 C9oracle10
AUTOMATIC STARTUP/SHUTDOWN SCRIPT
$vi /sbin/init.d/oracle10
#!/sbin/sh
# NOTE: This script is not configurable! Any changes made to this
# scipt will be overwritten when you upgrade to the next
# release of HP-UX.
# WARNING: Changing this script in any way may lead to a system that
# is unbootable. Do not modify this script.
# NOTE:
# For ORACLE:
PATH=/usr/sbin:/usr/bin:/sbin
export PATH
ORA_HOME="/oracle/app/oracle/product/10.2.0"
ORA_OWNR="oracle"
rval=0
set_return() {
x=$?
if [ $x -ne 0 ]; then
echo "EXIT CODE: $x"
rval=1
fi
case $1 in
start)
# Oracle listener and instance startup
echo -n "Starting Oracle: "
su - $ORA_OWNR -c "$ORA_HOME/bin/dbstart /oracle/app/oracle/product/10.2.0"
echo "OK DB started"
stop)
# Oracle listener and instance shutdown
echo -n "Shutdown Oracle: "
su - $ORA_OWNR -c "$ORA_HOME/bin/dbshut /oracle/app/oracle/product/10.2.0"
echo "OK DB shutdown"
reload|restart)
$0 stop
$0 start
echo "usage: $0 {start|stop}"
esac
exit $rval

Oracle Automatic Startup & Shutdown

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

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

Linux - Shutdown instance - startup instance problems.

Hello,
I am not sure if somebody has had this problem before, I read through some posts and didnt find a solution.
I have install Oracle 11g on a Fedora Box and a Ubuntu Box. In both i have the same situation.
After installing Oracle I can work with it without any problems, create table, users, views, store procedures, etc, etc...
I do have a problem when I try to shutdown the instance. When I do this the listener stops working, and hence, I can not start the instance again. The only way I can do it is by starting EM and starting the instance with it...
Here is what I have:
*1. I check the listener:*
oracle@hp:/u01/app/oracle/product/11.2.0/dbhome_1/bin$ ./lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 24-AUG-2010 12:52:34
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 24-AUG-2010 10:08:01
Uptime 0 days 2 hr. 44 min. 32 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/hp/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
Services Summary...
Service "orcl" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully
oracle@hp:/u01/app/oracle/product/11.2.0/dbhome_1/bin$
Then I start sqlplus and connect as sysdba:
oracle@hp:/u01/app/oracle/product/11.2.0/dbhome_1/bin$ ./sqlplus /nolog
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 24 12:53:15 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> connect sys@orcl as sysdba
Enter password:
Connected.
SQL>
And I shutdown the instance
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
I check the listener again (notice that it no longer has my service):
oracle@hp:/u01/app/oracle/product/11.2.0/dbhome_1/bin$ ./lsnrctl status
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 24-AUG-2010 12:54:43
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 24-AUG-2010 10:08:01
Uptime 0 days 2 hr. 46 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File /u01/app/oracle/diag/tnslsnr/hp/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
The listener supports no services
The command completed successfully
and hence, when i try to startup again:
SQL> startup
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
SQL>
=========================
Some more information:
*/etc/oratab:*
orcl:/u01/app/oracle/product/11.2.0/dbhome_1:Y
ORACLE_HOME/network/admin/tnsname.ora
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
LISTENER_ORCL =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl)
ORACLE_HOME/network/admin/listener.ora
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
ADR_BASE_LISTENER = /u01/app/oracle
Any help will be greatly appreciated!!!!

Dear user1707138,
You have two options to try;
1) Enter the ip address in to the HOST parameter in the listener and tnsnames entries.
2) Edit the hosts file and put the hostname and the ip address in there than edit the listener and tnsnames files to set the hostname in to the HOST parameter.
ORA-12514:
     TNS:listener does not currently know of service requested in connect descriptor
Cause:      The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
- Check for an event in the listener.log file.You can also see the listener.log file for further information.
Regards.
Ogan

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

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

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

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

Database Instance Installation Problem on Oracle 8.1.7

Dear gurus,
I'm having problem when installing Database Central Instance on Solaris 10 - Oracle 8.1.7 (32bit) - SAP 4.6c.
Here's the error log:
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
Echo                            ON
SVRMGR> SET TERMOUT ON;
Termout                         ON
SVRMGR> SHUTDOWN ABORT;
ORACLE instance shut down.
SVRMGR> STARTUP NOMOUNT PFILE=init.ora;
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 3
SVRMGR> CREATE DATABASE PRD
     2> CONTROLFILE REUSE
     3> MAXDATAFILES 254
     4> MAXLOGFILES   255
     5> MAXLOGHISTORY 1000
     6> MAXLOGMEMBERS 3
     7> MAXINSTANCES 50
     8> CHARACTER SET "WE8DEC"
     9> DATAFILE
    10> '/oracle/PRD/sapdata1/system_1/system.data1' SIZE 300M REUSE
    11> NOARCHIVELOG
Info: DBCREATEDB_IND_ORA SvrmgrDoDummy 2 349
    12> LOGFILE
    13> GROUP 11 (
    14> '/oracle/PRD/origlogA/log_g11m1.dbf',
    15> '/oracle/PRD/mirrlogA/log_g11m2.dbf'
    16> ) SIZE 20M REUSE
    17> ,GROUP 13 (
    18> '/oracle/PRD/origlogA/log_g13m1.dbf',
    19> '/oracle/PRD/mirrlogA/log_g13m2.dbf'
    20> ) SIZE 20M REUSE
    21> ,GROUP 12 (
    22> '/oracle/PRD/origlogB/log_g12m1.dbf',
    23> '/oracle/PRD/mirrlogB/log_g12m2.dbf'
    24> ) SIZE 20M REUSE
    25> ,GROUP 14 (
    26> '/oracle/PRD/origlogB/log_g14m1.dbf',
    27> '/oracle/PRD/mirrlogB/log_g14m2.dbf'
    28> ) SIZE 20M REUSE
    29> ;
CREATE DATABASE PRD
ORA-01034: ORACLE not available
SVRMGR> EXIT
Server Manager complete.
Error: DBCREATEDB_IND_ORA InternalInstallationDo 2 349
Create Database failed errorcode = 27123.
Error: DBCREATEDB_IND_ORA InstallationDo 2 349
Phase failed.
Error: Main {} 2 349
Installation aborted.
I have tweaked the shared memory max as suggested in Oracle Manual / SAP Installation Guide, to no avail.
The listener is up already.
When I logged in as user ORA<SID>, and go to svrmgrl > startup nomount pfile=init.ora, it can startup without hassle.
Although the Product is not supported in PAM, we have another machine running smoothly for years with this product combination, so it's not the product compatibility issues.
But when using R3SETUP -f DATABASE.R3S, the phase stopped with the log pasted above.
Any ideas, gurus?
Thanks for help.
Best Regards,

Mr. Markus, there's no file on saptrace/usertrace.
To be sure, here's what I've done:
1. Run oracle listener.
2. Check connection with svrmgrl > connect internal (connected).
3. Modify init.ora with my DB Name:
wef
# replace DEFAULT with your database name
*db_name=PRDDB*
db_files = 80                                                         # SMALL
# db_files = 400                                                      # MEDIUM
# db_files = 1500                                                     # LARGE
db_file_multiblock_read_count = 8                                     # SMALL
# db_file_multiblock_read_count = 16                                  # MEDIUM
# db_file_multiblock_read_count = 32                                  # LARGE
db_block_buffers = 100                                                 # SMALL
# db_block_buffers = 550                                              # MEDIUM
# db_block_buffers = 3200                                             # LARGE
shared_pool_size = 3500000                                            # SMALL
# shared_pool_size = 5000000                                          # MEDIUM
# shared_pool_size = 9000000                                          # LARGE
log_checkpoint_interval = 10000
processes = 50                                                        # SMALL
# processes = 100                                                     # MEDIUM
# processes = 200                                                     # LARGE
parallel_max_servers = 5                                              # SMALL
# parallel_max_servers = 4 x (number of CPUs)                         # MEDIUM
# parallel_max_servers = 4 x (number of CPUs)                         # LARGE
log_buffer = 32768                                                    # SMALL
# log_buffer = 32768                                                  # MEDIUM
# log_buffer = 163840                                                 # LARGE
# audit_trail = true            # if you want auditing
# timed_statistics = true       # if you want timed statistics
max_dump_file_size = 10240      # limit trace file size to 5 Meg each
# Uncommenting the line below will cause automatic archiving if archiving has
# been enabled using ALTER DATABASE ARCHIVELOG.
# log_archive_start = true
# log_archive_dest = disk$rdbms:[oracle.archive]
# log_archive_format = "T%TS%S.ARC"
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
# rollback_segments = (name1, name2)
# If using public rollback segments, define how many
# rollback segments each instance will pick up, using the formula
#   # of rollback segments = transactions / transactions_per_rollback_segment
# In this example each instance will grab 40/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = TRUE
# Edit and uncomment the following line to provide the suffix that will be
# appended to the db_name parameter (separated with a dot) and stored as the
# global database name when a database is created. If your site uses
# Internet Domain names for e-mail, then the part of your e-mail address after
# the '@' is a good candidate for this parameter value.
# db_domain = us.acme.com       # global database name is db_name.db_domain
# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE
# vms_sga_use_gblpagfil = TRUE
# FOR BETA RELEASE ONLY. Enable debugging modes. Note that these can
# adversely affect performance. On some non-VMS ports the db_block_cache_*
# debugging modes have a severe effect on performance.
#_db_block_cache_protect = true                       # memory protect buffers
#event = "10210 trace name context forever, level 2" # data block checking
#event = "10211 trace name context forever, level 2" # index block checking
#event = "10235 trace name context forever, level 1" # memory heap checking
#event = "10049 trace name context forever, level 2" # memory protect cursors
# define parallel server (multi-instance) parameters
#ifile = ora_system:initps.ora
# define two control files by default
control_files = (ora_control1, ora_control2)
# Uncomment the following line if you wish to enable the Oracle Trace product
# to trace server activity. This enables scheduling of server collections
# from the Oracle Enterprise Manager Console.
# Also, if the oracle_trace_collection_name parameter is non-null,
# every session will write to the named collection, as well as enabling you
# to schedule future collections from the console.
# oracle_trace_enable = TRUE
# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.
#compatible = 8.1.0
3. set shared memory parameter as in sapnote 724713.
4. executing R3SETUP
and it tells me this error:
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 1034.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Server Manager complete.
Info: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database.
Info: DBCREATEROLLSEGSTART_IND_ORA OracleCmd 2 354
Startup Database with PFILE: init.ora.
Info: DBCREATEROLLSEGSTART_IND_ORA SyCoprocessCreateAsUser 2 354
Creating coprocess /oracle/PRD/817_32/bin/svrmgrl [email protected] as user oraprd and group dba ...
Info: DBCREATEROLLSEGSTART_IND_ORA SyGroupIDGet 2 354
Group id for group dba is 102.
Info: DBCREATEROLLSEGSTART_IND_ORA SyUserIDGet 2 354
User id for user oraprd is 100.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Return from DB: 27123.
Info: DBCREATEROLLSEGSTART_IND_ORA SvrmgrDoDummy 2 354
Oracle Server Manager Release 3.1.7.0.0 - Production
Copyright (c) 1997, 1999, Oracle Corporation. All Rights Reserved.
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
With the Partitioning option
JServer Release 8.1.7.0.0 - Production
Connected.
ORA-27123: unable to attach to shared memory segment
SVR4 Error: 22: Invalid argument
Additional information: 1
Additional information: 2
alter database noarchivelog
ORA-01034: ORACLE not available
alter database open
ORA-01034: ORACLE not available
Server Manager complete.
Error: DBCREATEROLLSEGSTART_IND_ORA InternalInstallationDo 2 354
Startup Database with error: 27123.
Error: DBCREATEROLLSEGSTART_IND_ORA InstallationDo 2 354
Phase failed.
Error: Main {} 2 354
Installation aborted.
It's driving me nuts for the last days.. can't figure out what happened here.

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

Instance startup / shutdown (Solaris 9 Oracle 9i)

Similar Messages

Maybe you are looking for