Database auto-startup script

Hi Team,
How can I check whether the auto startup script is scheduled for the database after the server reboot
OS version:Linux server1 2.6.18-194.11.1.el5 #1 SMP Tue Jul 24 05:45:06 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
DB version :11.2.0.2
/etc/oratab entry is set to Y.
But the database did not startup after the server reboot. How to verify that the auto startup script is available?

http://www.oracle-base.com/articles/linux/automating-database-startup-and-shutdown-on-linux.php
HTH
Anand

Similar Messages

Auto startup script in 10g rel2

According to the Grid Control release 2 documentation, the out-of-the-box installation is supposed to configure and startup the database, OMS, listener and agent automatically when the server reboots. This is not the case when I reboot my server (RHEL 3 and 4). None of the processes were started automatically. I do not see any entries in rc*.d either. Where are these scripts located?
Installation type - Enterprise Manager Using new database
Anyone experience similar issue? Are there any further configurations that I may have missed?
thanks.

Mine are in /etc/rc.d/init.d/gcstartup.
Basically a bunch of shell calls like:
if [ -f /opt/app/oracle/product/agent10g/install/unix/scripts/agentstup ]; the
n
. /opt/app/oracle/product/agent10g/install/unix/scripts/agentstup
fi
if [ -f /opt/app/oracle/product/agent10g/install/unix/scripts/agentstup ]; the
n
. /opt/app/oracle/product/agent10g/install/unix/scripts/agentstup

How to let database(10.2) auto startup when linux reboot?

Hi all,
I installed oracle database 10.2 in linux (x86),and created a database.
I can startup the database manually. But database can not be started up automatic when linux starts up.
How to let database startup automatic when OS starts up?
the details shell scripts for auto startup would be appreciated!
Thanks

I don't know LINUX but I know Solaris. In Solaris, you have a startup and shutdown script in $ORACLE_HOME/bin. Setting the field to Y in oratab means you startup/shutdown the instance when executing the scripts. However, it does not mean the startup script will be
executed upon reboot. In solaris, we place a script in /etc/rc3.d. Then the script will be executed upon reboot. Guess you have similar features in Linux.

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!

Setup problem - sql server 2014 - "could not find the database engine startup handle" - 0x851a0019

I tried to install ,deleted and re-installed several times and no help at all.
visual studio 2013 with update 2 rc and adk installed in my computer.
error code: 0x851a0019
error messege in setup: could not find the database engine startup handle
edition: Microsoft SQL Server 2014 Enterprise (Evaluation)
logs:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 13:53:29
End time: 2014-04-03 14:47:48
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for RS: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for DQ: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for FullText: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Next step for Replication: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: ARIELUBA-PC
Machine processor count: 8
OS version: Windows 8
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS Database Engine Services 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 SQLEXPRESS MSSQL11.SQLEXPRESS SQL Server Replication 1033
Express Edition 11.1.3128.0 No Yes
SQL Server 2012 ADK MSSQL11.ADK Database Engine Services
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 ADK MSSQL11.ADK SQL Server Replication
1033 Express Edition 11.0.2100.60 No Yes
SQL Server 2012 LocalDB
1033 Express Edition 11.1.3412.0 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Arie Luba\Downloads\WS2012R2DC\SQLServer2014-x64-ENU\x64\setup\
Installation edition: Evaluation
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT Service\SQLSERVERAGENT
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup
ASCOLLATION: Hebrew_CI_AS
ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config
ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data
ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: NT Service\MSSQLServerOLAPService
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME:
CLTRESULTDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir\
CLTSTARTUPTYPE: Manual
CLTSVCACCOUNT: NT Service\SQL Server Distributed Replay Client
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir\
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
CTLRSTARTUPTYPE: Manual
CTLRSVCACCOUNT: NT Service\SQL Server Distributed Replay Controller
CTLRSVCPASSWORD: <empty>
CTLRUSERS: ARIELUBA-PC\Arie Luba
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, RS_SHP, RS_SHPWFE, DQC, CONN, IS, BC, SDK, BOL, SSMS, ADV_SSMS, DREPLAY_CTLR, DREPLAY_CLT, MDS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT Service\MsDtsServer120
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: SharePointFilesOnlyMode
RSSVCACCOUNT: NT Service\ReportServer
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Hebrew_CI_AS
SQLSVCACCOUNT: NT Service\MSSQLSERVER
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: ARIELUBA-PC\Arie Luba
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Client Tools SDK
Status: Passed
Feature: Client Tools Backwards Compatibility
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Reporting Services - Native
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A0019
Error description: Could not find the Database Engine startup handle.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4025
Feature: Master Data Services
Status: Passed
Feature: Distributed Replay Client
Status: Passed
Feature: Distributed Replay Controller
Status: Passed
Feature: Integration Services
Status: Passed
Feature: Data Quality Client
Status: Passed
Feature: Analysis Services
Status: Passed
Feature: Reporting Services - SharePoint
Status: Passed
Feature: Reporting Services Add-in for SharePoint Products
Status: Passed
Feature: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_135327\SystemConfigurationCheck_Report.htm
2014-04-03 14:14:28.01 Server Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
2014-04-03 14:14:28.01 Server UTC adjustment: 3:00
2014-04-03 14:14:28.01 Server (c) Microsoft Corporation.
2014-04-03 14:14:28.01 Server All rights reserved.
2014-04-03 14:14:28.01 Server Server process ID is 7148.
2014-04-03 14:14:28.01 Server System Manufacturer: 'Dell Inc.', System Model: 'Inspiron N5110'.
2014-04-03 14:14:28.01 Server Authentication mode is WINDOWS-ONLY.
2014-04-03 14:14:28.01 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-04-03 14:14:28.01 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2014-04-03 14:14:28.01 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-04-03 14:14:28.01 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
-m "SqlSetup"
-Q
-q "Hebrew_CI_AS"
-T 4022
-T 4010
-T 3659
-T 3610
-T 8015
2014-04-03 14:14:28.28 Server SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2014-04-03 14:14:28.28 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-04-03 14:14:28.28 Server Detected 8099 MB of RAM. This is an informational message; no user action is required.
2014-04-03 14:14:28.28 Server Using conventional memory in the memory manager.
2014-04-03 14:14:28.31 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2014-04-03 14:14:28.34 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-04-03 14:14:28.36 Server Query Store settings initialized with enabled = 1,
2014-04-03 14:14:28.36 Server The maximum number of dedicated administrator connections for this instance is '1'
2014-04-03 14:14:28.36 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-04-03 14:14:28.38 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-04-03 14:14:28.39 Server Database Mirroring Transport is disabled in the endpoint configuration.
2014-04-03 14:14:28.39 spid8s Warning ******************
2014-04-03 14:14:28.39 spid8s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-04-03 14:14:28.40 spid8s Starting up database 'master'.
2014-04-03 14:14:28.42 Server Software Usage Metrics is disabled.
2014-04-03 14:14:28.48 Server CLR version v4.0.30319 loaded.
2014-04-03 14:14:28.56 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2014-04-03 14:14:28.62 spid8s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.63 spid8s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-04-03 14:14:28.64 spid8s SQL Trace ID 1 was started by login "sa".
2014-04-03 14:14:28.64 spid8s Server name is 'ARIELUBA-PC'. This is an informational message only. No user action is required.
2014-04-03 14:14:28.65 spid16s Password policy update was successful.
2014-04-03 14:14:28.66 spid16s Error: 17190, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2014-04-03 14:14:28.66 spid16s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2014-04-03 14:14:28.66 spid16s Error: 17182, Severity: 16, State: 1.
2014-04-03 14:14:28.66 spid16s TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2014-04-03 14:14:28.66 spid16s Error: 17826, Severity: 18, State: 3.
2014-04-03 14:14:28.66 spid16s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-04-03 14:14:28.67 spid16s Error: 17120, Severity: 16, State: 1.
2014-04-03 14:14:28.67 spid16s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
________________________________________________________________________________________________

Is it okay? (see below)
;SQL Server 2014 Configuration File
[OPTIONS]
; Specifies a Setup work flow, like INSTALL, UNINSTALL, or UPGRADE. This is a required parameter.
ACTION="Install"
; Detailed help for command line argument ROLE has not been defined yet.
ROLE="AllFeatures_WithDefaults"
; Use the /ENU parameter to install the English version of SQL Server on your localized Windows operating system.
ENU="True"
; Parameter that controls the user interface behavior. Valid values are Normal for the full UI,AutoAdvance for a simplied UI, and EnableUIOnServerCore for bypassing Server Core setup GUI block.
UIMODE="Normal"
; Setup will not display any user interface.
QUIET="False"
; Setup will display progress only, without any user interaction.
QUIETSIMPLE="False"
; Specify whether SQL Server Setup should discover and include product updates. The valid values are True and False or 1 and 0. By default SQL Server Setup will include updates that are found.
UpdateEnabled="True"
; Specify if errors can be reported to Microsoft to improve future SQL Server releases. Specify 1 or True to enable and 0 or False to disable this feature.
ERRORREPORTING="False"
; If this parameter is provided, then this computer will use Microsoft Update to check for updates.
USEMICROSOFTUPDATE="False"
; Specifies features to install, uninstall, or upgrade. The list of top-level features include SQL, AS, RS, IS, MDS, and Tools. The SQL feature will install the Database Engine, Replication, Full-Text, and Data Quality Services (DQS) server. The Tools feature
will install Management Tools, Books online components, SQL Server Data Tools, and other shared components.
FEATURES=SQLENGINE,REPLICATION,FULLTEXT,DQ,AS,RS,RS_SHP,RS_SHPWFE,DQC,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,DREPLAY_CTLR,DREPLAY_CLT,MDS
; Specify the location where SQL Server Setup will obtain product updates. The valid values are "MU" to search Microsoft Update, a valid folder path, a relative path such as .\MyUpdates or a UNC share. By default SQL Server Setup will search Microsoft Update
or a Windows Update service through the Window Server Update Services.
UpdateSource="MU"
; Displays the command line parameters usage
HELP="False"
; Specifies that the detailed Setup log should be piped to the console.
INDICATEPROGRESS="False"
; Specifies that Setup should install into WOW64. This command line argument is not supported on an IA64 or a 32-bit system.
X86="False"
; Specify the root installation directory for shared components. This directory remains unchanged after shared components are already installed.
INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server"
; Specify the root installation directory for the WOW64 shared components. This directory remains unchanged after WOW64 shared components are already installed.
INSTALLSHAREDWOWDIR="C:\Program Files (x86)\Microsoft SQL Server"
; Specify a default or named instance. MSSQLSERVER is the default instance for non-Express editions and SQLExpress for Express editions. This parameter is required when installing the SQL Server Database Engine (SQL), Analysis Services (AS), or Reporting Services
(RS).
INSTANCENAME="MSSQLSERVER"
; Specify that SQL Server feature usage data can be collected and sent to Microsoft. Specify 1 or True to enable and 0 or False to disable this feature.
SQMREPORTING="False"
; Specify the Instance ID for the SQL Server features you have specified. SQL Server directory structure, registry structure, and service names will incorporate the instance ID of the SQL Server instance.
INSTANCEID="MSSQLSERVER"
; The computer name that the client communicates with for the Distributed Replay Controller service.
CLTCTLRNAME="SQLDRC"
; The Windows account(s) used to grant permission to the Distributed Replay Controller service.
CTLRUSERS="ARIELUBA-PC\Arie Luba"
; The account used by the Distributed Replay Controller service.
CTLRSVCACCOUNT="NT Service\SQL Server Distributed Replay Controller"
; The startup type for the Distributed Replay Controller service.
CTLRSTARTUPTYPE="Manual"
; The account used by the Distributed Replay Client service.
CLTSVCACCOUNT="NT Service\SQL Server Distributed Replay Client"
; The startup type for the Distributed Replay Client service.
CLTSTARTUPTYPE="Manual"
; The result directory for the Distributed Replay Client service.
CLTRESULTDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\ResultDir"
; The working directory for the Distributed Replay Client service.
CLTWORKINGDIR="C:\Program Files (x86)\Microsoft SQL Server\DReplayClient\WorkingDir"
; RSInputSettings_RSInstallMode_Description
RSINSTALLMODE="DefaultNativeMode"
; RSInputSettings_RSInstallMode_Description
RSSHPINSTALLMODE="SharePointFilesOnlyMode"
; Specify the installation directory.
INSTANCEDIR="C:\Program Files\Microsoft SQL Server"
; Agent account name
AGTSVCACCOUNT="NT Service\SQLSERVERAGENT"
; Auto-start service after installation.
AGTSVCSTARTUPTYPE="Manual"
; Startup type for Integration Services.
ISSVCSTARTUPTYPE="Automatic"
; Account for Integration Services: Domain\User or system account.
ISSVCACCOUNT="NT Service\MsDtsServer120"
; The name of the account that the Analysis Services service runs under.
ASSVCACCOUNT="NT Service\MSSQLServerOLAPService"
; Controls the service startup type setting after the service has been created.
ASSVCSTARTUPTYPE="Automatic"
; The collation to be used by Analysis Services.
ASCOLLATION="Hebrew_CI_AS"
; The location for the Analysis Services data files.
ASDATADIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Data"
; The location for the Analysis Services log files.
ASLOGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Log"
; The location for the Analysis Services backup files.
ASBACKUPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Backup"
; The location for the Analysis Services temporary files.
ASTEMPDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Temp"
; The location for the Analysis Services configuration files.
ASCONFIGDIR="C:\Program Files\Microsoft SQL Server\MSAS12.MSSQLSERVER\OLAP\Config"
; Specifies whether or not the MSOLAP provider is allowed to run in process.
ASPROVIDERMSOLAP="1"
; Specifies the list of administrator accounts that need to be provisioned.
ASSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Specifies the server mode of the Analysis Services instance. Valid values are MULTIDIMENSIONAL and TABULAR. The default value is MULTIDIMENSIONAL.
ASSERVERMODE="MULTIDIMENSIONAL"
; CM brick TCP communication port
COMMFABRICPORT="0"
; How matrix will use private networks
COMMFABRICNETWORKLEVEL="0"
; How inter brick communication will be protected
COMMFABRICENCRYPTION="0"
; TCP port used by the CM brick
MATRIXCMBRICKCOMMPORT="0"
; Startup type for the SQL Server service.
SQLSVCSTARTUPTYPE="Automatic"
; Level to enable FILESTREAM feature at (0, 1, 2 or 3).
FILESTREAMLEVEL="0"
; Set to "1" to enable RANU for SQL Server Express.
ENABLERANU="False"
; Specifies a Windows collation or an SQL collation to use for the Database Engine.
SQLCOLLATION="Hebrew_CI_AS"
; Account for SQL Server service: Domain\User or system account.
SQLSVCACCOUNT="NT Service\MSSQLSERVER"
; Windows account(s) to provision as SQL Server system administrators.
SQLSYSADMINACCOUNTS="ARIELUBA-PC\Arie Luba"
; Provision current user as a Database Engine system administrator for %SQL_PRODUCT_SHORT_NAME% Express.
ADDCURRENTUSERASSQLADMIN="True"
; Specify 0 to disable or 1 to enable the TCP/IP protocol.
TCPENABLED="1"
; Specify 0 to disable or 1 to enable the Named Pipes protocol.
NPENABLED="0"
; Startup type for Browser Service.
BROWSERSVCSTARTUPTYPE="Automatic"
; Specifies which account the report server NT service should execute under. When omitted or when the value is empty string, the default built-in account for the current operating system.
; The username part of RSSVCACCOUNT is a maximum of 20 characters long and
; The domain part of RSSVCACCOUNT is a maximum of 254 characters long.
RSSVCACCOUNT="NT Service\ReportServer"
; Specifies how the startup mode of the report server NT service. When
; Manual - Service startup is manual mode (default).
; Automatic - Service startup is automatic mode.
; Disabled - Service is disabled
RSSVCSTARTUPTYPE="Automatic"
; Add description of input argument FTSVCACCOUNT
FTSVCACCOUNT="NT Service\MSSQLFDLauncher"

Auto-startup EM for Solaris 10

Hi all,
I'd like to put the Enterprise Manager to auto-startup when rebooting the server.
The database version are 10g and 11g, and the OS is Solaris 10.
Basically the manual command is: emctl start dbconsole
I'd like to setup automatically to execute the same command.
Thanks in advance everybody.
Alex

Hi,
I checked the Note 222813.1 you mentioned, but it says about to restart the database, also it's already done this setup, but it's not included the Enterprise Manager.
Furthermore, I checked the oratab and its fine.
Any other clue to proceed on that?
Thanks.
Alex

Where to put EM db console startup script?

I have 2-node RAC on Linux servers. All the services including database/listeners come up automatically after the Node reboot.
Oracle support confirmed that "db console" is not a part of auto-start script.
So I have to put together a script basically to do "emctl start dbconsole".
Need to know what is the best place/file to call this script, keeping in mind the CRS/database take sometime to comeup.
Thanks

Oh sorry. No, RAC don't use dbstart.
You probably have to come up with a simple script that just do emctl start.
For example, call this file oraem
modify based on the sample dbora script from Oracle doc.
#! /bin/sh -x
# Change the value of ORACLE_HOME to specify the correct Oracle home
# directory for your installation.
ORACLE_HOME=/u01/app/oracle/product/10.2.0/db_1
# Change the value of ORACLE to the login name of the
# oracle owner at your site.
ORACLE=oracle
PATH=${PATH}:$ORACLE_HOME/bin
HOST=`hostname`
PLATFORM=`uname`
export ORACLE_HOME PATH
case $1 in
'start')
        $ORACLE_HOME/bin/emctl start dbconsole &
'stop')
        $ORACLE_HOME/bin/emctl stop dbconsole &
        echo "usage: $0 {start|stop}"
        exit
esac
exit# chgrp dba oraem
# chmod 750 oraem
Test run it manually a couple of time make sure it works.
then link,
# ln -s /etc/init.d/oraem /etc/rc.d/rc3.d/K01dbora
# ln -s /etc/init.d/oraem /etc/rc.d/rc3.d/S99dbora

**SOLVED** TrueCrypt - Why would you add it to startup script?

Hi Guys,
This might be a stupid question, but...
I read the wiki entry on TrueCrypt (http://wiki.archlinux.org/index.php/TrueCrypt). I'm assuming the use-case for TrueCrypt would be if someone management to get hold of the hard-disk, the contents would be encrypted, so they stil couldn't be read?
However the tutorial mentions you can add the mount procedure to your startup scripts so it will auto-mount if the machine is rebooted.
My question is; if someone has your hard disk (say they plugged it in as a second drive on their laptop, which they did have root access to); wouldn't they be able to read the startup script file and then they would know the password to decrypt the fs?
Am I missing something..? :S
--Solved--
Last edited by tommed (2010-06-04 09:13:57)

that is true, but if your password is actually a keyfile, and that keyfile is stored on a usb, whenever you boot up with the usb connected, you can automout your encrypted volume.
this is also a matter of comfort vs security, since if you believe your machine can be compromised, you can remove it from begin auto mounted or leave it when you know your system is currently safe.

Oracle11r2/Solaris10 Problem startup script "insufficient privileges"

Hi,
I have a problem with my startup script. i think that is the permissions but i dont know.
When i run the script as oracle user, the script runs ok. But when i reboot the system the log showme error with "insufficient privileges".
This is my script.
+# more dbora+
+#!/usr/bin/bash -x+
+#/bin/sh -x+
+#+
+# Change the value of ORACLE_HOME to specify the correct Oracle home+
+# directory for your installation.+
ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
+#+
+# Change the value of ORACLE to the login name of the+
+# oracle owner at your site.+
+#+
ORACLE=oracle
+PATH=${PATH}:$ORACLE_HOME/bin+
HOST=`hostname`
PLATFORM=`uname`
ORACLE_SID="orcl"
export ORACLE_HOME PATH ORACLE_SID
case $1 in
+'start')+
sleep 3
+# rsh $HOST -l $ORACLE -n "$ORACLE_HOME/bin/dbstart $ORACLE_HOME &"+
+# su - oracle -c "$ORACLE_HOME/bin/dbstart"+
+# $ORACLE_HOME/bin/dbstart "+
+$ORACLE_HOME/bin/dbstart $ORACLE_HOME &+
+$ORACLE_HOME/bin/lsnrctl start &+
+$ORACLE_HOME/bin/emctl start dbconsole &+
+;;+
+'stop')+
+$ORACLE_HOME/bin/dbshut $ORACLE_HOME &+
+$ORACLE_HOME/bin/lsnrctl stop &+
+$ORACLE_HOME/bin/emctl stop dbconsole &+
+;;+
+*)+
+echo "usage: $0 start"+
+exit+
+;;+
+esac+
+exit+
+#+
+# ll /etc/init.d/dbora+
+-rwxr-x--- 1 root dba 1185 Apr 20 10:33 /etc/init.d/dbora+
+#+
+# ll /etc/rc3.d/+
+total 42+
+...+
+...+
+lrwxrwxrwx 1 root root 17 Apr 20 10:30 K01dbora -> /etc/init.d/dbora+
+lrwxrwxrwx 1 root root 17 Apr 19 17:04 S99dbora -> /etc/init.d/dbora+
+#+
+# more /var/opt/oracle/oratab+
+orcl:/u01/app/oracle/product/11.2.0/db_1:Y+
+other:/u01/app/oracle/product/11.2.0/db_1:Y+
+#+
+# more /etc/group+
+...+
+...+
+oinstall::100:oracle+
+dba::101:oracle+
+#+
I try with su - oracle -c "command" in the script but doesnt work (the oracle doesnt startup and startup log dont show nothing).
I dont know whats the problem. I will thank you for your help.
Thanks.
========
startup log from the init.d:
++ export ORACLE_SID+
++ PATH=/u01/app/oracle/product/11.2.0/db_1/bin:/bin:/usr/bin:/etc:/usr/sbin:/usr/bin:/u01/app/oracle/product/11.2.0/db_1/bin+
++ export PATH+
++ LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/db_1/lib:+
++ export LD_LIBRARY_PATH+
++ PFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora+
++ SPFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora+
++ SPFILE1=/u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora+
++ echo ''+
++ echo '/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"'+
+/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"+
++ date+
+Tue Apr 20 10:34:25 CDT 2010+
++ echo ''+
++ checkversionmismatch+
++ '[' 11 ']'+
+++ sqlplus -V+
+++ grep 'Release '+
+++ cut '-d ' -f3+
+++ cut -d. -f1+
++ VER10INST=11+
++ '[' 11 -lt 11 ']'+
++ VERSION=undef+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/sqldba ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/svrmgrl ']'+
++ SQLDBA='sqlplus /nolog'+
++ STATUS=1+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.dbf ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.ora ']'+
+++ ps -ef+
+++ grep -w ora_pmon_orcl+
+++ grep -v grep+
++ pmon=+
++ '[' '' '!=' '' ']'+
++ '[' 1 -eq -1 ']'+
++ '[' 1 -eq 1 ']'+
++ '[' -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora ']'+
++ case $VERSION in+
++ sqlplus /nolog+
+SQL*Plus: Release 11.2.0.1.0 Production on Tue Apr 20 10:34:26 2010+
+Copyright (c) 1982, 2009, Oracle. All rights reserved.+
+SQL> + export ORACLE_SID+
++ PATH=/u01/app/oracle/product/11.2.0/db_1/bin:/bin:/usr/bin:/etc:/usr/sbin:/usr/bin:/u01/app/oracle/product/11.2.0/db_1/bin+
++ export PATH+
++ LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/db_1/lib:+
++ export LD_LIBRARY_PATH+
++ PFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora+
++ SPFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora+
++ SPFILE1=/u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora+
++ echo ''+
++ echo '/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"'+
+/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"+
++ date+
+Tue Apr 20 10:34:27 CDT 2010+
++ echo ''+
++ checkversionmismatch+
++ '[' 11 ']'+
+++ sqlplus -V+
+++ grep 'Release '+
+++ cut '-d ' -f3+
+++ cut -d. -f1+
++ VER10INST=11+
++ '[' 11 -lt 11 ']'+
++ VERSION=undef+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/sqldba ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/svrmgrl ']'+
++ SQLDBA='sqlplus /nolog'+
++ STATUS=1+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.dbf ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.ora ']'+
+++ ps -ef+
+++ grep -w ora_pmon_orcl+
+++ grep -v grep+
++ pmon=+
++ '[' '' '!=' '' ']'+
++ '[' 1 -eq -1 ']'+
++ '[' 1 -eq 1 ']'+
++ '[' -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora ']'+
++ case $VERSION in+
++ sqlplus /nolog+
+SQL*Plus: Release 11.2.0.1.0 Production on Tue Apr 20 10:34:27 2010+
+Copyright (c) 1982, 2009, Oracle. All rights reserved.+
+SQL> ERROR:+
+ORA-01031: insufficient privileges+
+SQL> ORA-01031: insufficient privileges+
+SQL> + '[' 0 -eq 0 ']'+
++ echo ''+
++ echo '/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Database instance "orcl" warm started.'+
+/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Database instance "orcl" warm started.+
=============
if i run the script as oracle user this is the log:
++ export ORACLE_SID+
++ PATH=/u01/app/oracle/product/11.2.0/db_1/bin:/bin:/usr/bin:/etc:/usr/sbin:/usr/bin:/opt/csw/bin:/usr/openwin/bin:/u01/app/oracle/product/11.2.0/db_1/bin+
++ export PATH+
++ LD_LIBRARY_PATH=/u01/app/oracle/product/11.2.0/db_1/lib:+
++ export LD_LIBRARY_PATH+
++ PFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora+
++ SPFILE=/u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora+
++ SPFILE1=/u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora+
++ echo ''+
++ echo '/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"'+
+/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Starting up database "orcl"+
++ date+
+Tue Apr 20 10:39:17 CDT 2010+
++ echo ''+
++ checkversionmismatch+
++ '[' ']'+
++ VERSION=undef+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/sqldba ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/bin/svrmgrl ']'+
++ SQLDBA='sqlplus /nolog'+
++ STATUS=1+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.dbf ']'+
++ '[' -f /u01/app/oracle/product/11.2.0/db_1/dbs/sgadeforcl.ora ']'+
+++ ps -ef+
+++ grep -w ora_pmon_orcl+
+++ grep -v grep+
++ pmon=+
++ '[' '' '!=' '' ']'+
++ '[' 1 -eq -1 ']'+
++ '[' 1 -eq 1 ']'+
++ '[' -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfileorcl.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/spfile.ora -o -e /u01/app/oracle/product/11.2.0/db_1/dbs/initorcl.ora ']'+
++ case $VERSION in+
++ sqlplus /nolog+
+SQL*Plus: Release 11.2.0.1.0 Production on Tue Apr 20 10:39:17 2010+
+Copyright (c) 1982, 2009, Oracle. All rights reserved.+
+SQL> Connected to an idle instance.+
+SQL> ORACLE instance started.+
+Total System Global Area 3374866432 bytes+
+Fixed Size 2152768 bytes+
+Variable Size 1845495488 bytes+
+Database Buffers 1493172224 bytes+
+Redo Buffers 34045952 bytes+
+Database mounted.+
+Database opened.+
+SQL> Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production+
+With the Partitioning, OLAP, Data Mining and Real Application Testing options+
++ '[' 0 -eq 0 ']'+
++ echo ''+
++ echo '/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Database instance "orcl" warm started.'+
+/u01/app/oracle/product/11.2.0/db_1/bin/dbstart: Database instance "orcl" warm started.+

Hi,
thanks for your reply.
I found the problem.
In my script, i change this:
# su - oracle -c "$ORACLE_HOME/bin/dbstart"
by this and its work (without "-")
# su oracle -c "$ORACLE_HOME/bin/dbstart"
Thanks...

Startup Scripting

Can I issue startup script from the command line so that sqldeveloper connects to a database, runs some commands and drops the developer into a window with the code ready to be edited and run?

As the Kris, of the SQL Developer team, is foreseen for release 1.1.
See:
Ability to run script on start of connection

Wicd works, network startup scripts don't

Title tells the story. Using wicd-1.7 I can connect to wireless networks and the connection remains stable. Using various combinations of rc.conf settings, netcfg, /etc/conf.d/wireless getting a connection is impossible at boot time and problematic after boot. The problem occurs on every system I've tested arch on. Wicd works, network startup scripts don't or only occasionally if some magic spell is properly cast. I'm positive I've configured the settings in rc.conf correctly as I've been able to connect using those by some combination of rmmod WLAN_MODULE, modprobe WLAN_MODULE, /etc/rc.d/network restart or netcfg ESSID. The requirement is that I am willing to go through the sequence multiple times.
I have just started testing arch and don't know if the network scripts worked before, but I assume they must have. Were there changes in the network startup scripts recently? I'm seeing many topics in the forums related to wireless problems.

When I say that netcfg ESSID works after startup, I mean that it works sometimes and that net-auto-wireless failed along with all other options that had the wireless start during boot. I'm not sure which version I tried but this was a new install in December or January and I was ready to remove arch by the end of February. A new version of wicd was released with some bug fixes that kept arch on the systems. Had that failed this laptop would likely have a BSD on it. Probably OpenBSD as I haven't tested that yet.
My current settings are configured for wicd and not causing any significant issues, other than having to reload the wireless driver when resuming from suspend.

AIX Startup Scripts

Dear All
Can I have a IBM AIX DB Startup Scripts ?
Regards
Lakmal

put
Orastart:2:wait:/usr/local/bin/changedbstatus_ora start all FORCE> /dev/console 2>&1
at the end of /etc/inittab
and
/usr/local/bin/changedbstatus_ora stop all FORCE
in /etc/rc.shutdown
where changedbstatus is similar to the following
[haiti]/db_masters $ cat changedbstatus_ora
#!/bin/sh
# usage: changedbstatus_ora start|stop
# This script is used to start or stop ORACLE
# $1 = Start, Stop, or reset_logs
# $2 = SID to start or stop (can be all)
# $3 = FORCE Force a shutdown or startup
# if $2 is not specified it defaults to all. this allows autostart/stop during
# system startup/shutdown
# Written by Graham Myers, Coda plc, (c) 2001
# fn_determine_version
# returns VERSION (7.3.4, 8.1.7, 9.2.0 etc)
fn_determine_version() {
set +x
if [ -f ${ORACLE_HOME}/bin/sqldba ]
then
VERSION=`sqldba command=exit | \
awk '/SQL\*DBA: (Release|Version)/ {split($3, V, ".") ; print V[1]}'`
elif [ -f ${ORACLE_HOME}/bin/svrmgrl ]
then
VERSION=`$ORACLE_HOME/bin/svrmgrl command=exit | awk '
/PL\/SQL (Release|Version)/ { print substr($3,1,5); exit }
/Oracle7 Server (Release|Version)/ { print substr($4,1,5); exit }
/Oracle8i Enterprise Edition (Release|Version)/ { print substr($5,1,5); exit }
/Oracle8i (Release|Version)/ { print substr($3,1,5); exit }'`
else
VERSION=`$ORACLE_HOME/bin/sqlplus -? | awk '/SQL\*Plus: Release/ {print substr($3,1,5); exit }'`
fi
VERSION_MAJOR=`echo ${VERSION} | cut -d. -f1`
# fn_determine_os - determine whioh operating system we're using, returns:
# BITS - no of processor bits 32 or 64
# ORATAB - set to correct path of oratab file
fn_determine_os() {
set +x
ORATAB=/etc/oratab
case `uname` in
SunOS)
BITS=`isainfo -kv | cut -d"-" -f 1`
ORATAB=/var/opt/oracle/oratab;;
HP-UX)
BITS=`/bin/getconf KERNEL_BITS`;;
AIX)
BITS=`/usr/sbin/bootinfo -K`;;
OSF1)
BITS=64;;
esac
# fn_check_status - check instance status
# Returns STATUS (1=running, 0=not running)
fn_check_status() {
set +x
#Check to see if instance shutdown cleanly (or is still running)
STATUS=0
if [ ${VERSION_MAJOR} -ge 8 ]
then
[ "`ps -ef | egrep pmon_${ORACLE_SID} | grep -v grep`" != "" ] && STATUS=1
else
[ -f ${ORACLE_HOME}/dbs/sgadef${ORACLE_SID}.dbf -o \
-f ${ORACLE_HOME}/dbs/sgadef${ORACLE_SID}.ora ] && STATUS=1
fi
# fn_cmd_file - Create a UNIX command script
# inputs $1 command - begin create a new command file
# begin_agent start an angent comamnd file
# command actual comamnds to place in command file
# start_sql run up the relevent SQL processor
# stop_sql exit out of SQL processor
# end finish off command file
fn_cmd_file() {
set +x
case $1 in
begin | begin_agent)
CMD_FILE=/tmp/changedbstatus.tmp$$
RDBMS_HOME=`grep oracle /etc/passwd | awk -F: '{print $6}'`
# Make sure the correct verion of Oracle is defined at login
if [ "$1" = "begin" ]
then
echo "Oracle_${VERSION}(${ORACLE_SID})" > ${RDBMS_HOME}/.rdbms_defaults
else
echo "Oracle_10.1.0(agent)" > ${RDBMS_HOME}/.rdbms_defaults
fi
echo "unset TWO_TASK" >> ${CMD_FILE};;
start_sql)
case "${VERSION}" in
"7") SQL_COMMAND="sqldba";;
"7.3.4"|"8.0.5") SQL_COMMAND="svrmgrl";;
*) SQL_COMMAND="sqlplus /nolog";;
esac
echo "${SQL_COMMAND}<<EOF" >> ${CMD_FILE}
echo "connect / as sysdba" >> ${CMD_FILE};;
command)
shift
echo "$*" >> ${CMD_FILE};;
end_sql)
echo "EOF" >> ${CMD_FILE};;
end)
chmod 755 ${CMD_FILE};;
esac
# fn_execute_cmd_file
# PLEASE NOTE the strange way of eching the session to the display rather than
# using tee. For some reason agentctl does not "let go" of the session and
# tee hangs. This is a documented "non-bug" for tnslsnr on 8i but nobody has
# has reported it for agentctl for 9i
# $1 should be a message to write to the screen prior to execution so the user
# has an indication something is happening
fn_execute_cmd_file() {
set +x
echo $1
su - oracle -c ${CMD_FILE} > ${CMD_FILE}.log 2>&1
RETURN_STATUS=$?
cat ${CMD_FILE}.log
# Scrap the defaults file after the command script has run
rm ${RDBMS_HOME}/.rdbms_defaults ${CMD_FILE}
# fn_reset_logs - rename existing log, create a new one, and purge old ones
# if $1 is non blank then it is assumed to be embedded in another command
# and so will not start a new command file (or execute it)
fn_reset_logs() {
set +x
if [ "$1" = "" ]
then
fn_cmd_file begin
fn_cmd_file command set +x
fi
if [ ${VERSION_MAJOR} -ge 9 ]
then
fn_cmd_file command "dmp_dest=\`grep background_dump_dest $PFILE|awk -F\"'\" '{print \$2}'\`"
else
fn_cmd_file command "dmp_dest=\`grep background_dump_dest $PFILE|awk '{print \$3}'\`"
fi
fn_cmd_file command "cd \${dmp_dest}"
fn_cmd_file command "dmp=alert_\${ORACLE_SID}.log"
fn_cmd_file command "new_dmp=\${dmp}.\`date +%y%m%d\`"
fn_cmd_file command "if [ -f \${new_dmp}.Z ]"
fn_cmd_file command "then"
fn_cmd_file command " zcat \${dmp} >> \${new_dmp}"
fn_cmd_file command " rm \${dmp} \${new_dmp}.Z"
fn_cmd_file command "else"
fn_cmd_file command " mv \${dmp} \${new_dmp}"
fn_cmd_file command "fi"
fn_cmd_file command "compress \${new_dmp}"
fn_cmd_file command "find ./ -name "\${dmp}.*" -mtime +30 -print -exec rm {} \\\+"
fn_cmd_file command "find ./ -name "/tmp/changdbstatus*" -mtime +2 -print -exec rm {} \\\+"
if [ "$1" = "" ]
then
fn_cmd_file end
fn_execute_cmd_file "reseting log files..."
fi
# fn_start_agent - Start the 10g intelligent agent
# This is only done once and only if a 64-bit server
fn_start_agent() {
set +x
fn_cmd_file begin_agent
fn_cmd_file command emctl start agent
fn_cmd_file end
fn_execute_cmd_file "Starting Intelligent Agent..."
# fn_stop_agent - Stop the 9i intelligent agent
# This is only done once and only if 64-bit server
fn_stop_agent() {
set +x
fn_cmd_file begin_agent
fn_cmd_file command emctl stop agent
fn_cmd_file end
fn_execute_cmd_file "Stopping Intelligent Agent..."
# fn_start_database - Start database
fn_start_database() {
set +x
fn_cmd_file begin
fn_cmd_file command set +x
fn_reset_logs include
fn_determine_listener
[ "`ps -ef | egrep ${LISTENER_NAME} | grep -v grep`" = "" ] && fn_cmd_file command lsnrctl start ${LISTENER_NAME}
fn_cmd_file start_sql
fn_cmd_file command startup
fn_cmd_file end_sql
#We now use an Oracle 10g Enterprise manager which does not support Oracle 8i agents so don't start them
# if [ ${VERSION_MAJOR} -lt 9 ]
# then
# # start the intelligent agent and data gatherer
# fn_cmd_file command vppcntl -start
# fn_cmd_file command lsnrctl dbsnmp_start
# fi
fn_cmd_file end
fn_execute_cmd_file "Starting instance ${ORACLE_SID}..."
# fn_stop_database - Stop database $1 passed as abort if required
fn_stop_database() {
set +x
fn_cmd_file begin
if [ "${ALL_DATABASES}" = "Y" ]
then
#We now use an Oracle 10g Enterprise manager which does not support Oracle 8i agents so they haven't been started
# if [ ${VERSION_MAJOR} -lt 9 ]
# then
# # stop the data gatherer and agent
# fn_cmd_file command vppcntl -stop
# fn_cmd_file command lsnrctl dbsnmp_stop
# fi
fn_determine_listener
[ "`ps -ef | egrep ${LISTENER_NAME} | grep -v grep`" != "" ] && fn_cmd_file command lsnrctl stop ${LISTENER_NAME}
fi
fn_cmd_file start_sql
fn_cmd_file command shutdown $1
fn_cmd_file end_sql
fn_cmd_file end
fn_execute_cmd_file "Stopping instance ${ORACLE_SID}..."
# fn_determine_listener - work out listener name
# For 8i it will be listener_817
# For 9i it will be listener_<hostname> as we use MTS
# on 9i and only need the listener for OEM.
fn_determine_listener() {
set +x
LISTENER_NAME=`grep "SID_LIST_" ${TNS_ADMIN:-$ORACLE_HOME/network/admin}/listener.ora | \
cut -d "_" -f 3- | cut -d "=" -f 1`
(trap 'exit' 1 2 3
set +x
fn_determine_os
ORIGINAL_ORACLE_HOME=${ORACLE_HOME}
ORIGINAL_ORACLE_PATH=${ORACLE_PATH}
ORIGINAL_LD_LIBRARY_PATH=${LD_LIBRARY_PATH}
ORIGINAL_PATH=${PATH}
if [ "$3" = "FORCE" ]
then
FORCE=Y
else
FORCE=N
fi
if [ "$2" = "all" -o "$2" = "" ]
then
FILTER="tee /dev/null"
ALL_DATABASES=Y
#if $2 is null then we are in system startup/shutdown - so force db start/stop
# this will get around any rogue files maybe due to a previous crash
[ "$2" = "" ] && FORCE=Y
#if we are starting all databases then assume we are starting everthing fresh
# so start the intelligent agent
if [ $ "$1" = "start" -o "$1" = "START" $ -a "${BITS}" = "64" ]
then
fn_start_agent
fi
else
FILTER="grep ^$2:" #Only apply filter if not all
ALL_DATABASES=N
fi
grep -v "^#" ${ORATAB} | ${FILTER} | awk -F: '{print $1,$2,$3}' | \
while read ORATAB_SID ORATAB_HOME ORATAB_START
do
ORACLE_SID=${ORATAB_SID} ;export ORACLE_SID
ORACLE_HOME=${ORATAB_HOME} ;export ORACLE_HOME
PATH=$ORACLE_HOME/bin:/bin:/usr/bin:/etc ;export PATH
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${ORACLE_HOME}/lib ;export LD_LIBRARY_PATH
fn_determine_version #Work out which version of Oracle is required
if [ ${VERSION_MAJOR} -ge 9 ]
then
PFILE=${ORACLE_HOME}/dbs/spfile${ORACLE_SID}.ora
else
PFILE=${ORACLE_HOME}/dbs/init${ORACLE_SID}.ora
fi
if [ -f ${PFILE} ]
then
fn_check_status #See if instance is already running
case $1 in
start | START )
if [ ${STATUS} -eq 1 ]
then
if [ "${FORCE}" = "Y" ]
then
echo Instance ${ORACLE_SID} already running - forcing shutdown
fn_stop_database abort
else
echo Instance ${ORACLE_SID} already running
continue
fi
fi
if [ "${ALL_DATABASES}" = "Y" -o $ "${ORATAB_START}" = "Y" -a "${ALL_DATABASES}" = "N" $ ]
then
fn_start_database
if [ ${RETURN_STATUS} -eq 0 ]
then
echo "Instance ${ORACLE_SID} started."
else
echo "Instance ${ORACLE_SID} NOT started."
fi
else
echo "Instance ${ORACLE_SID} NOT started."
fi;;
stop | STOP)
if [ ${STATUS} -eq 0 ]
then
if [ "${FORCE}" = "Y" ]
then
echo Instance ${ORACLE_SID} already shutdown - forcing shutdown
fn_stop_database abort
else
echo Instance ${ORACLE_SID} already shutdown
continue
fi
else
fn_stop_database IMMEDIATE
if [ ${RETURN_STATUS} -eq 0 ]
then
echo "Instance ${ORACLE_SID} shutdown."
else
echo "Instance ${ORACLE_SID} NOT shutdown."
fi
fi;;
reset_logs)
fn_reset_logs;;
esac
else
echo ""
echo "Cant find init file for instance ${ORACLE_SID}."
fi
done
#if we are shutting down eveything then close down the agents too
if [ "${ALL_DATABASES}" = "Y" -a $ "$1" = "stop" -o "$1" = "STOP" $ -a ${BITS} = 64 ]
then
fn_stop_agent
fi
ORACLE_HOME=${ORIGINAL_ORACLE_HOME};export ORACLE_HOME
ORACLE_SID=${ORIGINAL_ORACLE_PATH};export ORACLE_SID
LD_LIBRARY_PATH=${ORIGINAL_LD_LIBRARY_PATH};export LD_LIBRARY_PATH
PATH=${ORIGINAL_PATH};export PATH
for VARIABLE in FILTER ORATAB_HOME ORATAB_SID ORATAB_START STATUS ORATAB \
PFILE SQL_COMMAND VERSION RETURN_STATUS RDBMS_HOME \
LISTENER_NAME FORCE ALL_DATABASES VERSION_MAJOR \
BITS LISTENER
do
unset ${VARIABLE}
done
unset VARIABLE) 2>&1 | tee /tmp/changedbstatus_ora.log
regards
Graham

Oracle 11gR2 systemd startup script

I would like to write down the systemd startup script here for I can't find any on the internet. wish people don't have to browse around and find nothing.
everything on internet is about 9i and no systemd startup script example.
I hv tried several times that the script runs right and start up oracle at bootup.
Issuing systemctl and it returns the following
oracle.service loaded active exited Oracle database serverthe script is working on my Fedora 18 x86_64.
Please give your input if you find mistake, error, or anything wrong.
Thank you
oracle.service
[Unit]
Description=Oracle database server
After=syslog.target network.target
[Service]
Type=oneshot
User=oracle
Group=oinstall
RemainAfterExit=yes
ExecStart=/bin/oracle.sh;
[Install]
WantedBy=multi-user.targetoracle.sh
#! /bin/bash
# script used by oracle.service
ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1
ORACLE_SID=orcl
ORACLE_BASE=/home/oracle/app/oracle/product/11.2.0
$ORACLE_HOME/bin/lsnrctl start;
$ORACLE_HOME/bin/dbstart $ORACLE_HOME;

newbieRyan wrote:
I would like to write down the systemd startup script here for I can't find any on the internet. wish people don't have to browse around and find nothing.
everything on internet is about 9i and no systemd startup script example.Really??!?!?!
I googled 'start oracle on linux startup" and the very first hit is pretty much the standard reference on the subject: http://www.oracle-base.com/articles/linux/automating-database-startup-and-shutdown-on-linux.php
I hv tried several times that the script runs right and start up oracle at bootup.
Issuing systemctl and it returns the following
{code}
oracle.service loaded active exited Oracle database server
{code}
the script is working on my Fedora 18 x86_64.
Please give your input if you find mistake, error, or anything wrong.
Thank you
oracle.service
{code}
[Unit]
Description=Oracle database server
After=syslog.target network.target
[Service]
Type=oneshot
User=oracle
Group=oinstall
RemainAfterExit=yes
ExecStart=/bin/oracle.sh;
[Install]
WantedBy=multi-user.target
{code}
oracle.sh
{code}
#! /bin/bash
# script used by oracle.service
ORACLE_HOME=/home/oracle/app/oracle/product/11.2.0/dbhome_1
ORACLE_SID=orcl
ORACLE_BASE=/home/oracle/app/oracle/product/11.2.0
$ORACLE_HOME/bin/lsnrctl start;
$ORACLE_HOME/bin/dbstart $ORACLE_HOME;
{code}

Mysql startup line in server startup script

I am trying to create a cron job for my backup of MySQL data. This seemed simple on linux (just a start and stop mysql statement) But I can't seem to figure it out on Mac Server 10.5 I have tried the mysql.server and MySQLCOM but that does not work.
Where is the Mac Server OSX main startup script(s) so I can copy the line that starts MySQL?
Cheers!

Hi,
mysqldump should work. I found it referenced in CCC and elsewhere
http://www.vbulletin.com/forum/showthread.php?t=2978. Unless your database is huge, it does not require stopping/starting the database manually.
Backup the entire database with:
mysqldump -u user_name -p your_password database_name > File_name.sql
Restore with:
mysql - u user_name -p your_password database_name < File_name.sql
HTH,
Harry

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

Database auto-startup script

Similar Messages

Maybe you are looking for