Database halted during shutdown

Hi All,
When I am shutting down the database , the process is getting halted at license high water mark , what is the reason behind that ? What action should be taken care to overcome this issue

saiisakapalli wrote:
Hi All,
When I am shutting down the database , the process is getting halted at license high water mark , what is the reason behind that ? What action should be taken care to overcome this issue
What do you mean, exactly?
Show us the extract from the alert log that shows the behavior .. not just a single line, but the entire sequence starting with the recognition of the shutdown command.

Similar Messages

What happen during shutdown oracle database

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

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

What happen during shutdown database

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

First of all shutdown has 4 options
1.Normal
2.Immediate
3.Transactional
4.Abort
Default is normal
Normal: No new connections are allowed. Database and redo buffers are written into disk.Database is closed.
     Backgroud process are terminated.SGA is deallocated. Until and unless all users disconnect, database wont be closed.
Transactional: No client can start a new transaction. Clients get disconnected once their transactions are completed.
     Database and redo buffers are written into disk.Database is closed.Backgroud process are terminated.SGA is deallocated.
Immediate: Current running SQL are not completed. Oracle does not wait for users to disconnect.
     All active transactions are rolled back.Database and redo buffers are written into disk.
     Database is closed.Backgroud process are terminated.SGA is deallocated.
Abort: All users are disconnected.Database and redo buffers are NOT written into disk.
All background processes are killed instantly and instance is abruptly terminated.

Database doesn't shutdown during shutting down the server

Dear Friends ,
I have to use the following dcript to use Auto startup and shutdown my Oracle Database in RHEL 4 .
step 1:
#!/bin/bash
# chkconfig: 345 99 10
# description: Oracle auto start-stop script.
# Set ORACLE_HOME to be equivalent to the $ORACLE_HOME
# from which you wish to execute dbstart and dbshut;
# Set ORACLE_OWNER to the user id of the owner of the
# Oracle database in ORACLE_HOME.
ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
ORACLE_OWNER=oracle
if [ ! -f $ORACLE_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case "$1" in
'start')
# Start the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl start"
su - $ORACLE_OWNER -c $ORACLE_HOME/bin/dbstart
'stop')
# Stop the Oracle databases:
# The following command assumes that the oracle login
# will not prompt the user for any values
su - $ORACLE_OWNER -c $ORACLE_HOME/bin/dbshut
su - $ORACLE_OWNER -c "$ORACLE_HOME/bin/lsnrctl stop"
esac
step 2:
cat /etc/inittab
*:/u01/app/oracle/product/10.2.0/db_1:N
orcl:/u01/app/oracle/product/10.2.0/db_1:Y
step 3:
Keep "dbora" in following path :
/etc/rc.d/rc3.d/dbora
/etc/rc.d/rc5.d/dbora
/etc/rc.d/init.d/dbora
And also ,
chmod 750 /etc/init.d/dbora
chkconfig --level 345 dbora on
Now ,The script works fine and ORacle Database and Listener service starts automatically during startup the server .But during shutdown the server, I cannot understand or can't recognize that the Oracle Database & listener service are shutdown auto . I think it does not work properly..... So i need to know that Oracle Database & listener service are stop automatically during shutting down the server . Using the above scripts , How can I do it ? Is there any wrong then plz advice me .......Thx ...

step 3:
Keep "dbora" in following path :
/etc/rc.d/rc3.d/dbora
/etc/rc.d/rc5.d/dbora
/etc/rc.d/init.d/dbora
And also ,
chmod 750 /etc/init.d/dbora
chkconfig --level 345 dbora on
Check following links are there
# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/K01dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/K01dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora
Script/link start with "K" , is responsible for shutdown database.
Check following Oracle Documentation link , it explain all in details
Starting and Stopping Oracle Software
- Virag Sharma
http://viragsharma.blogspot.com
http://virag.sharma.googlepages.com

Suggestion: how to unfreeze during shutdown/logout

Hi all,
From time to time, my iMac freezes during shutdown/logout. I cant really find out the actual cause. May be it was due to the .Mac mirroring, or some external USB devices fail to shutdown properly, whatever the reason is. My question is other than pressing the magic button to shut down, what else can I do to unfreeze it? Please suggest.
Thanks in advance,
Derek.

I also experience hangups during shutdown. Very often I might add, and this is really annoying. I've reinstalled my Mac Pro from scratch twice in the last month, thinking it was an error on my part. Last night, as I shut down (using CTRL-Option-Command-Eject), this is the log I got (I have no halt line, which is strange):
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: LaunchCFMApp [422]:34567 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: System Events [428]:38727 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: LCCDaemon [423]:42755 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: iCalAlarmScheduler [420]:40603 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: iTunesHelper [387]:36611 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: AppleModemOnHold [380]:34059 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: MirrorAgent [375]:33027 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: Finder [374]:31491 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: SystemUIServer [372]:30979 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: SystemUIServer [372]:30467 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: loginwindow [113]:18243 not responding.
Aug 14 23:27:51 freds-computer diskarbitrationd[69]: ATSServer [112]:20227 not responding.
Aug 15 00:39:33 freds-computer kernel[0]: PCI sleep prevented by comaja_iokitkonalh (5)
Aug 15 00:39:33 freds-computer kernel[0]: PCI sleep prevented by PXS4 (1)
Aug 15 03:15:01 freds-computer cp: error processing extended attributes: Operation not permitted
I understand why you can't recover from a hangup when the shutdown process started, as services started to close, but there must be a way to "jolt" the system to force quit hanged or rogue/zombie processes in order to properly shutdown the system. Each time I push the power button to close down the computer, I fear I may corrupt something in the OS or the system disk.
Any thoughts?

Strange icon during shutdown...

Does anyone else have a strange icon flash on the display for a fraction of a second during shutdown? I running 10.5.1 on my 15" MBP 2.16 Core Duo and have noticed a real weird icon that only shows up occasionally during shutdown. It usually blinks on and off too fast to really see what it is, but I think it is sort of like the symbol on the command key and has a red X across it. I don't have any issues with the MBP with the exception of some files that Disk Utility is having trouble with when I repair permissions which seems to take a long time. It gets to a point where it says time remaining is less than a minute, but keeps going and going for another 3-5 minutes after displaying this:
Repairing permissions for “Macintosh HD”
Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
Permissions repair complete
Anyone seen this before or have any thoughts?

Thanks for the tip.
I did as you suggested and the permissions issue is fully resolved. Never had an issue using the Software Update pane, but I'll file the in my overloaded brain for another time.
I haven't seen the strange icon during shutdown again, but I did identify it as the icon for a piece of software called KeyCue. It shows keyboard shortcuts for the active application by holding down the Command key for about 2 seconds.
Thanks again!

IMac hangs up during shutdown

My iMacs (2006 + late 2007) occasionally lockup during shutdown. After the desktop icons are gone but the desktop photo remains with the spinning pinwheel. Eventually I force a shutdown by holding down the power button. On restart, everything is back to normal. Sometimes I have waited for 2 hours and the machine has not shut down - only gone to sleep.

Same problem here, but it hangs all the time, not only 10-20% of the shutdown. I let it there for about 2 hours, nothing changed.
I have no idea if this is time machine related, but if it is, it's a bug. Apple can't wan't me to check the sys prefs every time i shut down my iMac...
By the way it's a two week old iMac which replaced my older one. I moved all the data by reinstalling leopard on the new iMac and telling the installer to rebuilt the system from the time machine data of my old iMac... Maybe something went wrong there.

System freeze during shutdown

I have noticed a couple of times that during shutdown immediately when plymouth kicks in the system just freezes. It is not leaving behind any logs. And it does not occur often. I use kde 4.4 rc2 from kde-mod. But this occurs after kdm quits and plymouth kicks in.
Anyone else facing the same issue? Any ideal how I can debug this?

Welcome to Apple Discussions!
To follow on from the advice re ensuring the driver is the latest version before attempting any other fix, if the problem continues, it is by far better to have the system shutdown gracefully by pulling the USB connection than to shutdown by removing power! At worst, disconnecting the USB cable would do no more than cause problems to the system's printer setup files or print queues, but disconnecting the power COULD cause significant damage to directory and file structure on the hard drive, and actually result in the system being unable to boot.

10.1.0.4 SUN solaris 8 Database does not shutdown normally

After SAN crash the 10.1.04 database does not shutdown immediate (hanging or..)
I shutdown abort and startup is smooth.
I checked the leftover OS processes looks like none left...
Any sugestion?
TIA

in the alert :12:27:06 2007
Waiting for Job queue slaves to complete
Wed Feb 14 12:28:15 2007
Job queue slave processes stopped
Wed Feb 14 12:33:18 2007
Active call for process 9247 user 'oracle' program 'oracle@solars23 (J000)'
SHUTDOWN: waiting for active calls to complete.
Wed Feb 14 12:47:00 2007
KTSMG_UPDATE_MQL(): MMNL absent for 1201 secs; Foregrounds taking over
oracle 9295 9274 0 12:25:03 ? 0:00 oracle102 (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))

Update Database Statistics during System Export

hi All,
I am getting following error on step (Update Database Statistics ) during system export.
WARNING 2011-06-17 15:13:35
Execution of the command "E:\usr\sap\PRD\SYS\exe\uc\NTAMD64\
brconnect.exe -u / -c -o summary -f stats -o SAPSR3 -t all -m +I -s
P10 -f allsel,collect,method,precision,space,keep -p 4"
finished with return code 5.
Output: BR0801I BRCONNECT 7.00 (31)BR0805I Start of BRCONNECT processing:
cegczbfe.sta 2011-06-17 15.12.02BR0484I BRCONNECT log file:
G:\oracle\PRD\sapcheck\cegczbfe.sta
ERROR 2011-06-17 15:13:35
CJS-30023 Process call 'E:\usr\sap\PRD\SYS\exe\uc\NTAMD64\
brconnect.exe -u / -c -o summary -f stats -o SAPSR3 -t all -m +I -s P10
-f allsel,collect,method,precision,space,keep -p 4'
exits with error code 5. For details see log file(s) brconnect.log.
there is small part of brconnect.log is:
BR0204I Percentage done: 27.88%, estimated end time: 15:16
BR0001I **************____________________________________
BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCL_STAT"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14830
ORA-06512: at "SYS.DBMS_STATS", line 14851
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCL_STAT
BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCL_STATT"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14830
ORA-06512: at "SYS.DBMS_STATS", line 14851
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCL_STATT
BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCMVWOBJ"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14830
ORA-06512: at "SYS.DBMS_STATS", line 14851
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCMVWOBJ
BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.31
BR0301E SQL error -20003 in thread 2 at location stats_tab_collect-20, SQL statement:
'BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCMVWOBPR"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14830
BEGIN DBMS_STATS.GATHER_TABLE_STATS (OWNNAME => '"SAPSR3"', TABNAME => '"/BEV3/CHCTLVAR"', ESTIMATE_PERCENT => NULL, METHOD_OPT => 'FOR ALL COLUMNS SIZE 1', DEGREE => NULL, CASCADE => TRUE, NO_INVALIDATE => FALSE); END;'
ORA-20003: Specified bug number (5099019) does not exist
ORA-06512: at "SYS.DBMS_STATS", line 14830
ORA-06512: at "SYS.DBMS_STATS", line 14851
ORA-06512: at line 1
ORA-06512: at line 1
BR0886E Checking/collecting statistics failed for table SAPSR3./BEV3/CHCTMSTFUB
BR0280I BRCONNECT thread 2: time stamp: 2011-06-17 15.13.34
BR0844E 100 errors occurred in thread 2 - terminating processing of the thread...
BR0280I BRCONNECT time stamp: 2011-06-17 15.13.34
BR0848I Thread 2 finished with return code -1
BR0280I BRCONNECT time stamp: 2011-06-17 15.13.34
BR0879I Statistics checked for 0 tables
BR0878I Number of tables selected to collect statistics after check: 0
BR0880I Statistics collected for 639/0 tables/indexes
BR0889I Structure validated for 0/749/0 tables/indexes/clusters
BR1308E Collection of statistics failed for 68292/0 tables/indexes
BR0806I End of BRCONNECT processing: cegczbfe.sta 2011-06-17 15.13.34
BR0280I BRCONNECT time stamp: 2011-06-17 15.13.35
BR0804I BRCONNECT terminated with errors
how can I resolve this issue?
Regards,
majamil

hi SM,
I have applied these patches with Opatch which successfully applied.
is it ok or i had to use the MOpatch for these?
one more thing for your information , when i execute Delete Harmful Statistics under Database Statistics in brtools then i got following
BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
BR0818I Number of tables found in DBSTATC for owner SAPSR3: 390
BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
BR0807I Name of database instance: PRD
BR0808I BRCONNECT action ID: cegfjniv
BR0809I BRCONNECT function ID: dst
BR0810I BRCONNECT function: stats
BR0812I Database objects for processing: HARMFUL
BR0852I Number of tables to delete statistics: 0
BR0856I Number of indexes to delete statistics: 0
BR0863W No tables/indexes found to update/delete statistics or validate structur
e
BR0806I End of BRCONNECT processing: cegfjniv.dst 2011-06-30 08.10.53
BR0280I BRCONNECT time stamp: 2011-06-30 08.10.53
BR0803I BRCONNECT completed successfully with warnings
BR0292I Execution of BRCONNECT finished with return code 1
BR0668I Warnings or errors occurred - you can continue to ignore them or go back
to repeat the last action
BR0280I BRTOOLS time stamp: 2011-06-30 08.10.53
BR0670I Enter 'c[ont]' to continue, 'b[ack]' to go back, 's[top]' to abort:
c
why i am getting this return code 1?
Regards,
Edited by: majamil on Jun 30, 2011 8:20 AM

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!

After 10.6.2 update system halts during boot

After having installed the 10.6.2 update via software update my Mac halts during boot. It boots right up to the grey screening displaying the Apple logo and the grey status wheel but doesn't go on from there. It just keeps displaying that screen forever with the status wheel still moving but not hard disk activity anymore after a few minutes.
I've already tried (via booting from the Snow Leopard DVD), to no avail:
- repairing permissions
- repairing the drive
- resetting the SMC

You could try [these grey sceen, etc., troubleshooting steps|http://support.apple.com/kb/TS2570] ignoring any duplicaion of what you already have don. And, you could try [these general troubleshooting steps|http://support.apple.com/kb/TS1394] again ignoring duplication.
If all above fails, then I suggest you do a repair install of Sno by installing Sno over Sno as in an upgrade install. Such an install, while usually very safe, still is an install so be appropriated backed up if you proceed.

ERP database did not shutdown

Hi
We have Oracle ERP R12.0.6 running on single node configuration. Usually we take full offline backups on friday morning. Even after issuing the command > shutdown immediate, database did not shutdown for 2 hours as some 'Create accounting' concurrent program was running for past 44 hours. Why database did not kill this session? Is our SGA or redolog files size are not proper?
How to diagnose this issue?
Regards
Ariz

Hi
I reviewed the alert log. When this shutdown immediate was running i was watching alert log and few of them as follows:
Fri May 6 07:04:12 2011
Starting background process EMN0
EMN0 started with pid=24, OS id=1904666
Fri May 6 07:04:12 2011
Shutting down instance: further logons disabled
Fri May 6 07:04:14 2011
Stopping background process QMNC
Fri May 6 07:04:14 2011
Stopping background process CJQ0
Fri May 6 07:04:19 2011
Stopping background process MMNL
Fri May 6 07:04:20 2011
Stopping background process MMON
Fri May 6 07:04:23 2011
Shutting down instance (immediate)
License high water mark = 262
Fri May 6 07:04:23 2011
Stopping Job queue slave processes
Fri May 6 07:04:23 2011
Job queue slave processes stopped
Fri May 6 07:09:22 2011
Active call for process 2142404 user 'oramgrl' program 'oracleSCC@ebsprod'
Active call for process 995354 user 'oramgrl' program 'oracleSCC@ebsprod'
SHUTDOWN: waiting for active calls to complete.
Fri May 6 07:13:56 2011
Incremental checkpoint up to RBA [0xb28.185c2e.0], current log tail at RBA [0xb28.185c3b.0]
Fri May 6 07:23:48 2011
MMNL absent for 1206 secs; Foregrounds taking over
Fri May 6 07:34:01 2011
Incremental checkpoint up to RBA [0xb28.185d1c.0], current log tail at RBA [0xb28.185d1c.0]
Fri May 6 07:47:56 2011
Beginning log switch checkpoint up to RBA [0xb29.2.10], SCN: 3320888564
Thread 1 advanced to log sequence 2857
Current log# 2 seq# 2857 mem# 0: /scclive/oracle/db/apps_st/data/log02a.dbf
Current log# 2 seq# 2857 mem# 1: /scclive/oracle/db/apps_st/data/log02b.dbf
Fri May 6 07:48:46 2011
Completed checkpoint up to RBA [0xb29.2.10], SCN: 3320888564
Fri May 6 07:54:36 2011
Incremental checkpoint up to RBA [0xb29.3372a.0], current log tail at RBA [0xb29.4ba21.0]
Yes, you are right. Using the other session, i had issue shut abort and it has resolved the issue. We have job_queue_processes = 2 and aq_tm_processes=1.
But my concern is, i cannot add >shut abort command in my script. What is the other alternative or what parameter to be tuned? Please guide me.
Regards
Ariz

"Ignore Sessions During Shutdown" and "Graceful Shutdown Sequence"

Hi
I have J2EE application consisting of WEB and EJB layers deployed on WL 8.1
I start the Graceful Shutdown Sequence with Ignore Sessions During Shutdown option set. sessionDestroyed() method of registered HttpSessionListener is fired but at this moment JNDI tree is already empty, EJB module undeployed and the listener is not able to get to application's EJBs.
In the documentation (http://e-docs.bea.com/wls/docs81/adminguide/overview_lifecycle.html#1045901) Ignore Sessions During Shutdown option is explained as follows:
"If you enable this option WebLogic Server will drop all HTTP sessions immediately, rather than waiting for them to complete or timeout."
What does "drop" mean here? Is this some exception to Graceful Shutdown Sequence and the following excerpt from the documentation? : "During a graceful shutdown, subsystems complete in-flight work and suspend themselves in a specific sequence and in a synchronized fashion, so that back-end subsystems like JDBC connection pools are available when front-end subsystems are suspending themselves."
Regards

Hi,
You can use tcodes
SMQR --> To register a queue
SMQS --> To register a destination in Queue Schedular
SMQ1 --> OutBound Queue Details
SMQ2 --> Inbound Queue Details
SXMB_ADMIN --> Manage Queue to register,deregister and activate the queue.
Check the link for more details : http://help.sap.com/saphelp_nw04/helpdata/en/59/d9fa40ee14f26fe10000000a1550b0/frameset.htm
For step details for server start/stop you can search on google for more details. And for an idea check the section Managing the SAP Start-Up Service via the SAP MMC Snap-In in the link https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3e3fad90-0201-0010-2f91-c8907db40bfe
Thanks!
Edited by: sudhir tiwari on Nov 12, 2008 12:00 PM

4400 halts during bootup asking for updated installer - why?

I'm rebuilding a 4400/200, which shows great promise but halts during boot up with a dialogue asking for an updated installer disk. The only button is "restart".
I want to run the 4400 on OS7.5.3 which it supports so I've installed it on an external scsi HD. It starts to boot, the little happy Mac icon shows then the dreaded dialogue box appears. I've tried to boot from CD (Gen Apple OS7.5.3 CDROM) zapped the PRAM, taken the internal IDE drive out (that has OS9.2 - planning to erase it).
My concern is the 4400 also stops when booting from "Disk Tools 2" on floppy, my other 4400 (OS9.1) works fine from that.
Any ideas why the 4400 should start to boot correctly then throw up the "correct installer disk needed" dialogue?

You may be out of luck, because System Enabler 827 is probably only found on the 4400's OS 7.5.3 Restore disk. Because the 4400 had a different architecture from the other Power Macs, OS 7.5's built-in, universal System enabler doesn't fully cover it. OS 7.5.5 and 7.6 aren't supported on the 4400/200, but OS 7.6.1 is, which has a universal enabler. You might want to try eBay for the full-install OS 7.6.1 retail/universal installer disk. I think that there was an OS 7.6.1 Update disk, which merely updated OS 7.6 to 7.6.1. If you're interested, here's the full 7.6.1 installer disk. Otherwise, try to find the 4400 Restore disk.

Database halted during shutdown

Similar Messages

Maybe you are looking for