Database emergency startup
We have a Oracle9i database on RHEL ver.4.
After installed new storage, our disk partition was broken and database was shutdown.
Question 1.
When File system was broken cause of media failure, we want know how startup database by force even though we lost our data.
Purpose of Our system is temporarily to manage data.
We want startup database emergency at either event that tablespace and data files exist or not.
Question 2.
In above situation, we acknowledge status of our database in nomount but control file was broken cause of media failure.
So we don't startup our database immediately.
I wonder if we create new control file, whether we startup database or not.
Please, be hurry.
We are in very emergency situation.
Thanks.
Message was edited by:
user636366
Hi,
Database shutdown was unexpected.
It was not clean shutdown.
We had not control file backup.(Actually, We had not any backup; COLD & HOT.)
So you don't have any backups in hand at the moment?Well prayers may help then.I shall suggest that you contact support for the issue.Its a prod db and you don't have a backup,I wont suggest you play around with it for any trial-see methodology.Let support take over the charge.
Aman....
Similar Messages
-
Could not find the Database Engine startup handle.
Why can't Microsoft make software that "Just Works" any more.
This is Sooooo frustrating! I'm a developer. I want to write database software and I'd like to use SQL Server. But I can't even get the damn thing to install on a fresh Windows 8.1 installation.
MySQL - installs no problem - it just works.
Oracle - Installs no problem - It just works.
I downloaded SQL Server 2012 Express with SP1, ran the Install, took most of the defaults, and I get:
Install Failed:
The following error has occurred:
Could not find the Database Engine startup handle.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254025
Of course, clicking on the link takes me to a non existing web page - what else? Just incompetence everywhere. This is Microsoft's own operating system yet they can't even get their own database to install while their competitors can.
How can they let this happen!
Then I googled the above error message. - Hundreds of hits and a lot of them are threads in forums and lots of civilians saying "try this try that" none of which works. Not a single Microsoft Employee to be found in any of the
discussions or answers. And this same problem has been happening since 2008! Yet Microsoft can't be bothered to fix it.
This kind of buggy software shouldn't have made it past Alpha testing.
Come on Microsoft, you just have to try harder. I can understand bugs that happen in unusual circumstances, after all I'm a developer too. But this won't even install on a clean Windows 8. It's tantamount to releasing a "Hello
World" program that crashes on startup!Hi Bob,
If you make sure all your hardware and software requirements are met for installation of SQL Server 2012 on window 8.1 Its highly unlikely you will face issue.I can understand your situation so let me help you.As Kalman pointed can you paste output
of setup log file which was generated due to failed installation using Kalman's link.
Did you went thorugh below link
How to install SQL server on Win 8.1
Hardware and software requirements for SQL Server 2012
Please first read above links understand how it works and then proceed
Regarding startup handle error .AFAIK its because of Account with which you are trying to install SQL server somehow is not able to start it up after installation.Basically a righst issue.Can be different in some cases.Now whenever you install SQL server
alsway RK on Setup file and select run as administrator.When you reach page window where you need to select startup account for SQL Server please select NT Authority\System( or local system account) .
Details with steps
http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
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" -
SQL Server Express 2014 on Win8.1: Could not find the Database Engine startup handle
Hello,
I tried to follow all the similarly titled posts in this forum, yet no solution seems to work, so I hope I can find some up-to-date suggestion here (most of the older posts refer to versions from 2008 to 2012...).
I have installed Visual Studio 2013 (with the latest Update 2 RC) on a freshly installed development workstation with Win 8.1 with all its updates. Now I'd want to install SQL Server 2014 Express, but the setup keeps failing with the dreaded "Could
not find the Database Engine startup handle" error (the log follows below).
What I tried:
1) download again and repair. Same error.
2) completely uninstall by launching setup.exe /Action=uninstall (success), then rebooting the OS, then installing again. Same error. I did this twice, the second time I also manually removed any directory left out in C:\Program Files etc.
When I launch the setup, I select all the components for installation in the package SQLEXPRADV_x64_ENU.exe (1.12 GB, last downloaded today -Apr 3, 2014-), and accept all the defaults including the proposed services accounts. There is no preexisting
SQL Server instance, as expected.
The setup takes its time, and finally fails with the error quoted above. I really do not want to reformat my HD and fully reconfigure my workstation, which took about 3 days... Could anyone suggest a solution to have SQL Server 2014 setup so I can start
developing instead of wasting time in administering the system?
Thanks to all! The log follows.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893607
Start time: 2014-04-03 18:30:58
End time: 2014-04-03 19:04:41
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 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: DIOMEDES
Machine processor count: 4
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
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: C:\Users\Daniele\Downloads\SQLEXPRADV_x64_ENU\x64\setup\
Installation edition: Express
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: true
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE, REPLICATION, FULLTEXT, RS, CONN, BC, SDK, BOL, SSMS, ADV_SSMS, LOCALDB
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$SQLEXPRESS
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: SQLEXPRESS
INSTANCENAME: SQLEXPRESS
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: NT Service\ReportServer$SQLEXPRESS
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQLEXPRESS
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: DIOMEDES\Daniele
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140403_183057\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: 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: SQL Browser
Status: Passed
Feature: Documentation Components
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
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_183057\SystemConfigurationCheck_Report.htmThank you, it worked! I suppose that it was really your nr.3 which made the difference. I changed NT Service\MSSQL$SQLEXPRESS to NT AUTHORITY\System for the Data service. I'll then change it again as suggested (any suggestion about a "standard"
account to be used here?), even if this is a development workstation using SQL Server Express only as a local database for debugging, so security is not really a big concern.
Thanks for the feedback.Ya I know No3 was real step but just added more info so as to rule out any other possibility.
No not as such, you wont believe,quite few pf my clients I have worked for keep it with local system and they have not complained yet ,they are afraid to change account as few of them faced issue SQL Server not coming online due to logon failure( after changing
startup account to some domain a and that was happening due to some AD policy.But if you have nay plans to move Critical database in production which would be act as Database to some Internet facing application please follow my suggestion
of running SQL Server with Least privileged domain account.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers -
Good morning,
I'm experiencing the following issue when installing Microsoft SQL Server Express 2012 (with tools, SQLEXPRWT_x86_ENU.exe) on the laptop of my company;
Installation goes plain until around the end of the progress bar, it stops on the setup of
SqlEngineDBStartConfigAction_install_configrc_Cpu32
giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
I've put in my SkyDrive the error log I received after the install;
I'm at full disposal if you need further information,
thank you in advance
Best regards
FrancescoWell, i just ran into this issue and the problem was lack of admin rights. It was my company's laptop so got the setup initiated by my company's IT team with admin rights. However, the upon completion of setup, i go the same error messages as stated above:
SqlEngineDBStartConfigAction_install_configrc_Cpu32
giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
Also, if you open SQL Server Configuration, the status of the service is "Change Pending" and you would not be able to set the startup login type to Local Service/System/Network.
Then, I just got my account added as Local Admin and then tried to start the service and was able to.
However, I am not sure whether same was the case for you.
Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana -
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! -
DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐
제품 : ORACLE SERVER
작성날짜 : 2002-04-10
DATABASE SHUTDOWN 후 STARTUP시 ORA-7445가 발생하면서 OS PROMPT로 빠짐
=====================================================================
Server Platform : Sparc Sunw Ultra Enterprise 10000
(CPU 44개, Main Memory 9 Megabytes)
ORACLE RDBMS 7.3.3.4
ORACLE PARALLEL SERVER 환경
Sun Cluster Volume Manager 2.0
DB size : 약 1.2 Terabytes (=1200 Gigabytes)
관련 TAR : 9168089.7
조치 내역 :
1. init.ora에 다음의 event와 hidden parameter를 설정
1) event="10210 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21184.1)
2) event="10211 trace name context forever, level 10"
(Data Block Integrity를 check, Refer to Note 21185.1
3) dbblock_cache_protect = true (Refer to note18144.1)
corrupt된 block이 memory에 load되는 것을 방지
2. Startup mount 후 recover database를 실행
ORA-600[6593] [26]발생 - Detection of block corruption
3. alter database open 실행
ORA-1578 file#88 block #172628 발생 하였으나
ORA-7445 없이 open됨
(문제가 되는 특정 테이블과 데이타 블럭 발견)
4. 위의 file block에 data를 확인하기 위하여 block dump를 함
"Alter session set events 'immediate trace name
blockdump level xxxxx"
( xxxxx는 Data Block Address 값의 decimal 값)
- Block dump에 있는 hexa값을 ascii로 변환
5. corrupt된 block을 제외한 data를 recover하기 위하여 새로운
tablespace를 생성 후 다음 실행.
"Insert into (TABLEA) select * from (TABLEB)
where index_column > ' '
and rowid not like 'corrupt된 row의 rowid들';"
(TABLEA는 corrupt되지 않은 row들을 제외한 나머지 row들을
포함할 새로운 테이블이고, TABLEB는 corrupt된 row들을 갖고
있었던 기존의 테이블)
6. 새로 생성한 테이블의 데이타 확인한 후 기존의 corrupt된
테이블 drop시킴
7. 새 테이블을 rename하여 기존의 테이블 이름과 같게 함. -
Dear all,
10.2.0.3 on Solaris 10.
When shutting down the database, shutdown hangs after database mounted as you can see below
SQL> startup
ORACLE instance started.
Total System Global Area 1073741824 bytes
Fixed Size 2133800 bytes
Variable Size 435843288 bytes
Database Buffers 624951296 bytes
Redo Buffers 10813440 bytes
Database mounted.In one more session, I checked the alert log
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN
^C
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$
bash-3.00$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Jan 7 10:16:28 2011
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL>
SQL> select open_mode from v$database;
OPEN_MODE
READ WRITEAny idea ?.
KaiThere is no error message . Anyway alert log
Fri Jan 7 10:13:08 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =88
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.3.0.
System parameters with non-default values:
_trace_files_public = TRUE
processes = 400
sessions = 800
timed_statistics = TRUE
shared_pool_size = 419430400
shared_pool_reserved_size= 41943040
sga_target = 1073741824
control_files = /erp/u01/medh/db/apps_st/data/cntrl01.dbf, /erp/u01/medh/db/apps_st/data/cntrl02.dbf, /erp/u01/medh/db/apps_st/data/cnt
rl03.dbf
db_block_checksum = TRUE
log_archive_dest = /oracle/arch/medh_ARCH
log_archive_format = medh%t_%s_%r.arc
log_buffer = 10485760
log_checkpoint_interval = 100000
log_checkpoint_timeout = 1200
db_files = 512
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
dml_locks = 10000
undo_management = AUTO
undo_tablespace = APPS_UNDOTS1
db_block_checking = FALSE
session_cached_cursors = 500
utl_file_dir = /usr/tmp, /usr/tmp, /erp/u01/medh/db/tech_st/10.2.0/appsutil/outbound/medh_sed04, /usr/tmp
plsql_native_library_dir = /erp/u01/medh/db/tech_st/10.2.0/plsql/nativelib
plsql_native_library_subdir_count= 149
plsql_code_type = INTERPRETED
plsql_optimize_level = 2
job_queue_processes = 2
cursor_sharing = EXACT
parallel_min_servers = 0
parallel_max_servers = 8
background_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/bdump
user_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/udump
max_dump_file_size = 20480
core_dump_dest = /erp/u01/medh/db/tech_st/10.2.0/admin/medh_sed04/cdump
db_name = medh
open_cursors = 600
ifile = /erp/u01/medh/db/tech_st/10.2.0/dbs/medh_sed04_ifile.ora
_sort_elimination_cost_ratio= 5
_b_tree_bitmap_plans = FALSE
_fast_full_scan_enabled = FALSE
_sqlexec_progression_cost= 2147483647
_like_with_bind_as_equality= TRUE
pga_aggregate_target = 1073741824
workarea_size_policy = AUTO
optimizer_secure_view_merging= FALSE
aq_tm_processes = 1
olap_page_pool_size = 4194304
PMON started with pid=2, OS id=12494
PSP0 started with pid=4, OS id=12496
MMAN started with pid=6, OS id=12499
DBW0 started with pid=8, OS id=12511
DBW1 started with pid=3, OS id=12544
DBW2 started with pid=10, OS id=12574
LGWR started with pid=5, OS id=12604
CKPT started with pid=12, OS id=12628
SMON started with pid=14, OS id=12653
RECO started with pid=16, OS id=12680
CJQ0 started with pid=18, OS id=12712
MMON started with pid=20, OS id=12738
MMNL started with pid=22, OS id=12761
Fri Jan 7 10:13:10 2011
ALTER DATABASE MOUNT
Fri Jan 7 10:13:14 2011
Setting recovery target incarnation to 2
Fri Jan 7 10:13:14 2011
Successful mount of redo thread 1, with mount id 3947812854
Fri Jan 7 10:13:14 2011
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Fri Jan 7 10:13:15 2011
ALTER DATABASE OPEN
Fri Jan 7 10:13:15 2011
Beginning crash recovery of 1 threads
parallel recovery started with 8 processes
Fri Jan 7 10:13:15 2011
Started redo scan
Fri Jan 7 10:13:15 2011
Completed redo scan
0 redo blocks read, 0 data blocks need recovery
Fri Jan 7 10:13:15 2011
Started redo application at
Thread 1: logseq 16761, block 30591, scn 30945234899
Fri Jan 7 10:13:15 2011
Recovery of Online Redo Log: Thread 1 Group 2 Seq 16761 Reading mem 0
Mem# 0: /erp/u01/medh/db/apps_st/data/log02b.rdo
Mem# 1: /erp/u01/medh/db/apps_st/data/log02a.rdo
Fri Jan 7 10:13:15 2011
Completed redo application
Fri Jan 7 10:13:15 2011
Completed crash recovery at
Thread 1: logseq 16761, block 30591, scn 30945254900
0 data blocks read, 0 data blocks written, 0 redo blocks read
Fri Jan 7 10:13:15 2011
LGWR: STARTING ARCH PROCESSES
ARC0 started with pid=34, OS id=14889
Fri Jan 7 10:13:15 2011
ARC0: Archival started
ARC1: Archival started
LGWR: STARTING ARCH PROCESSES COMPLETE
ARC1 started with pid=15, OS id=14921
Fri Jan 7 10:13:15 2011
Thread 1 advanced to log sequence 16762
Thread 1 opened at log sequence 16762
Current log# 3 seq# 16762 mem# 0: /erp/u01/medh/db/apps_st/data/log03b.rdo
Current log# 3 seq# 16762 mem# 1: /erp/u01/medh/db/apps_st/data/log03a.rdo
Successful open of redo thread 1
Fri Jan 7 10:13:15 2011
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Jan 7 10:13:15 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
Fri Jan 7 10:13:15 2011
ARC1: Becoming the heartbeat ARCH
Fri Jan 7 10:13:15 2011
SMON: enabling cache recovery
Fri Jan 7 10:13:16 2011
Successfully onlined Undo Tablespace 1.
Fri Jan 7 10:13:16 2011
SMON: enabling tx recovery
Fri Jan 7 10:13:16 2011
Database Characterset is AR8MSWIN1256
Fri Jan 7 10:13:16 2011
Incremental checkpoint up to RBA [0x417a.3.0], current log tail at RBA [0x417a.87.0]
Fri Jan 7 10:13:16 2011
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=36, OS id=15146
Fri Jan 7 10:13:19 2011
Completed: ALTER DATABASE OPEN -
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 -
Eclipse Error during Database Studio startup
I have some MaxDB 7.7 and 7.8 databases on SLES11 x86_64. There is no Windows machine nearby so I cannot use good old (stable!) DBMGUI but I have to switch over to this fancy Databse Studio tool. Installation was no problem, but during there startup I get some error messages:
cd /sapdb/clients/DatabaseStudio/DatabaseStudio/
setenv PATH /sapdb/clients/DatabaseStudio/DatabaseStudio:$PATH
./dbstudio -vm /usr/java/jre1.5.0_11/bin/java
Xlib: extension "RANDR" missing on display "localhost:1.0".
(%appName:15081): Gdk-CRITICAL **: gdk_draw_drawable: assertion `GDK_IS_DRAWABLE (drawable)' failed
Xlib: extension "RANDR" missing on display "localhost:1.0".
I get a small pop-up window with this information text:
"An error has occurred. See the log file /sapdb/D93/sdb/DatabaseStudio/.metadata/.log."
The contents of this logfile are:
!SESSION 2011-03-29 13:03:02.301 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86_64
!ENTRY org.eclipse.ui 4 4 2011-03-29 13:03:11.856
!MESSAGE Plug-in 'com.sap.sdb.tools.ui' contributed an invalid Menu Extension (Path: 'org.eclipse.search.menu' is invalid): com.sap.sdb.tools.ui.dbstudiosearchaction
!ENTRY org.eclipse.ui.workbench 4 0 2011-03-29 13:03:14.271
!MESSAGE Widget disposed too early!
!STACK 0
java.lang.RuntimeException: Widget disposed too early!
at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1163)
at org.eclipse.swt.widgets.Widget.release(Widget.java:1026)
at org.eclipse.swt.widgets.Control.release(Control.java:3217)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184)
at org.eclipse.swt.widgets.Widget.release(Widget.java:1029)
at org.eclipse.swt.widgets.Control.release(Control.java:3217)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184)
at org.eclipse.swt.widgets.Widget.release(Widget.java:1029)
at org.eclipse.swt.widgets.Control.release(Control.java:3217)
at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1184)
at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:211)
at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:466)
at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1948)
at org.eclipse.swt.widgets.Widget.release(Widget.java:1029)
at org.eclipse.swt.widgets.Control.release(Control.java:3217)
at org.eclipse.swt.widgets.Widget.dispose(Widget.java:442)
at org.eclipse.swt.widgets.Shell.dispose(Shell.java:1893)
at org.eclipse.swt.widgets.Display.release(Display.java:3083)
at org.eclipse.swt.graphics.Device.dispose(Device.java:237)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:129)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Now what does this error message mean? Or how could I fix this problem?
Regards,
MarkAddendum: This was also in the log file, forgot to post it in my initial post:
!ENTRY org.eclipse.osgi 2 0 2011-03-29 13:03:16.633
!MESSAGE One or more bundles are not resolved because the following root constraints are not resolved:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-03-29 13:03:16.633
!MESSAGE Bundle update@eclipse/plugins/com.sap.sdb.tools.ui.report_7.8.1.v201007081836/ was not resolved.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.633
!MESSAGE Missing required bundle org.eclipse.birt.report.engine_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.633
!MESSAGE Missing required bundle org.eclipse.birt.report.viewer_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.634
!MESSAGE Missing required bundle org.eclipse.birt.report.model_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.634
!MESSAGE Missing required bundle org.eclipse.birt.core_0.0.0.
!ENTRY org.eclipse.osgi 2 0 2011-03-29 13:03:16.635
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2011-03-29 13:03:16.636
!MESSAGE Bundle update@eclipse/plugins/com.sap.sdb.tools.ui.report_7.8.1.v201007081836/ [167] was not resolved.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.636
!MESSAGE Missing required bundle org.eclipse.birt.core_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.636
!MESSAGE Missing required bundle org.eclipse.birt.report.engine_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.636
!MESSAGE Missing required bundle org.eclipse.birt.report.model_0.0.0.
!SUBENTRY 2 com.sap.sdb.tools.ui.report 2 0 2011-03-29 13:03:16.636
!MESSAGE Missing required bundle org.eclipse.birt.report.viewer_0.0.0. -
Hi all!
I have an IBM server (2 Xeon CPUs 16 GGb RAM) SAP DB platform version 7.4.3.27, OS Windows 2003 server x86
I have started database 30.01.2012 at 5:00 AM during 2 days database stops with emergency shutdown this is the log
Date Time TID(hex) Typ MsgID Label Message-Text
2012-01-30 04:59:06 --- Starting GMT 2012-01-30 04:59:06 7.4.3 Build 027-123-048-452
2012-02-01 11:09:50 0xC70 ERR 12 DATACACH ASSERTION FAILED; 35
2012-02-01 11:09:50 0xC70 ERR 18196 DBCRASH vabort:Emergency Shutdown, vgg01.c: 2261
Please anybody can enplane why it shutdown, after this error I started database normally
Regards
Edited by: rextazy on Feb 1, 2012 7:35 AMDoes it means CACHE SIZE value? Is size of the cache depends from size of the data or from quantity of the volumes?
I have 150000 pgs cache size, 15 volumes (20 ggd) Data about 70%
regards
Andrey
Edited by: rextazy on Feb 3, 2012 5:01 AM -
Prevent JDdeveloper connect to the database at Startup
Jdeveloper is trying to establish a database connection at the startup...I would want to establish a connection only when trying to lauch a project.Is there any means of disabling this setting at the startup??
... in fact, many times I start and work with JDeveloper without my database being up. So what you describe sounds strange to me.
Frank -
The observer only reinstate the old primary database after startup it twice
I use Oracle 11g r2 configure a data guard and fast_start fail over (using data guard broker) environment on linux.
The data guard works fine, and the fail over too.
The problem is that after fail over, the observer can't reinstate the old primary database to new standby database after start up it to mount, and what strange is that if shutdown (immediate) it again, and start up it to mount again, the reinstating can be completed automatically and successfully.
I use 'shutdown abort' to simulate the database crash.
Any one have some advice? Thanks in advance!
Edited by: user1665703 on 2011-7-27 下午4:33There are some strange log in drcorcl.log,
2011-07-27 16:30:57.702 RSM0: HEALTH CHECK ERROR: ORA-16808: primary database is not open
2011-07-27 16:30:57.844 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.844 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property LogXptMode found
ORA-16777 error
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.845 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property DelayMins found O
RA-16777 error
2011-07-27 16:30:57.845 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.846 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.846 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property Binding found ORA
-16777 error
2011-07-27 16:30:57.846 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.847 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.847 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property MaxFailure found
ORA-16777 error
2011-07-27 16:30:57.847 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.848 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.848 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property MaxConnections fo
und ORA-16777 error
2011-07-27 16:30:57.848 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.849 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.849 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property ReopenSecs found
ORA-16777 error
2011-07-27 16:30:57.849 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.849 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property NetTimeout found
ORA-16777 error
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb
y database in V$ARCHIVE_DEST
2011-07-27 16:30:57.850 RSM Warning: cannot find the destination setting in v$archive_dest for database 'orclSt
d'.
2011-07-27 16:30:57.850 RSM0: HEALTH CHECK WARNING: ORA-16728: consistency check for property RedoCompression f
ound ORA-16777 error
2011-07-27 16:30:57.851 RSM0: HEALTH CHECK WARNING: ORA-16777: unable to find the destination entry of a standb -
Database Studio startup Error after installing MaxDB 7.7 on MS-Windows
After installing MaxDB 7.7 the following error occurs when starting up Database Studio:
!ENTRY org.eclipse.osgi 4 0 2008-01-22 11:39:00.636
!MESSAGE An error occurred while automatically activating bundle com.sap.sdb.tools.ui.application (50). !STACK 0
org.osgi.framework.BundleException: The activator com.sap.sdb.tools.ui.application.ApplicationPlugin for bundle com.sap.sdb.tools.ui.application is invalid
Caused by: java.lang.UnsupportedClassVersionError: com/sap/sdb/tools/ui/application/ApplicationPlugin (Unsupported major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
... 31 more
What could be the problem here?
Any help will be appreciated greatly.
Context info:
=========
A clean install: Old MaxDB 7.6 was first uninstalled.
OS: Windows Server 2003 Standard Edition R2 on VMWare
2x Xeon 3.66 Ghz
3,75 GB memory
The install log indicates no problems other than the following:
WRN: cannot execute command: "C:/DOCUME1/ADMINI1/LOCALS~1/Temp/1/Max6.tmp\vcredist_x86.exe" /Q:a /c:"msiexec.exe /qn /i vcredist.msi": cannot create process, The system cannot find the file specified.Hi Simon,
The error message:
> Caused by: java.lang.UnsupportedClassVersionError: com/sap/sdb/tools/ui/application/ApplicationPlugin (Unsupported major.minor version 49.0)
usually indicates that a wrong Java Version was used to run Database Studio. Database Studio needs Java 1.5 to run.
Please check your Java installation and your JAVA_HOME environment variable to point to the Java 1.5 installation.
Cheers,
Daniel -
Hello,
when I tried to access SQL*Plus it give me following error
ORA -01033:Oracle initilization or shut down in progress
When I tried to access the database alert log following are the notes
Tue Jun 09 17:40:14 2009
starting up 1 shared server(s) ...
PSP0 started with pid=3, OS id=3164
MMNL started with pid=12, OS id=3536
Tue Jun 09 17:40:20 2009
alter database mount exclusive
Tue Jun 09 17:40:34 2009
Errors in file c:\oracle\product\10.2.0\admin\orcl\udump\orcle_ora_3768.trc:
ORA-00202: control file: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL'
ORA-27091: unable to queue I/O
ORA-27070: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 23) Data error (cyclic redundancy check).
Tue Jun 09 17:40:39 2009
ORA-204 signalled during: alter database mount exclusive...
Kindly tell me what is the error as I'm new to Oracle and I ahven't study yet how to read database alert log
Regards,
D.AbbasiHi Anand,
Yes it seems that control file CONTROL01.CTL got corrupted as it is also not opening in notepad. As far as multipled control files are concern there are other control file as well and they are two more CONTROL02.CTL and CONTROL03.CTL.
Are those step which you describe is for creating new control file?
you said "create pfile from spfile;" is it really necessary. I mean if pfile is already present then what should do?
and what is this "shutdown immediate";
what to shutdown, if it is DB then how is it possible as it is not starting?
Kindly answer my these questions and one thing more as I have created only single database during installation of ORACLE Database then why there are multiple files.
Looking for reply
Regards,
D.Abbasi
Maybe you are looking for
-
Lorex Edge Client Software Crashing, OS-X 10.7.4
Greetings, Has anyone had any issues with Lorex video security application "Edge Client Software"? Every time it is launched it crashed (dump below). Any input greatly appreciated. Thank you, Lyman Process: Edge Client Software [2684] Path:
-
experts, Can i know any FM /BAPI to create Move in ,i have Installation & Contract Account available with me. Tried using ISU_S_MOVE_IN_CREATE & BAPI_ISUMOVEIN_CREATEFROMDATA , but dont know what parameters to be passed. Please help me out in this. T
-
Mapping Entity beans to existing database tables.
Hi All, I am using the RI of the J2EE (1.3.1) server provided by SUN. While deploying an entity bean I don't want to create a table by default, I want it to map to an existing table in the database. I find no DB column/EJB field mapping facility in t
-
I get this message when i try to log onto my home pc account "The user Profile Service, service failed the lofon. User profile cannot be loaded" can I recover my data from another/new user account from my iCloud account??
-
My iWOW SRS plug-in for iTunes stopped working after the Leopard upgrade,I hope i can get it working it makes my system sound sooo much better. along with a few other apps I use. anyone have the same problem? I guess the App developers have to provid