About the RAC's startup

when creating database with DBCA,I got the following errors:
PRKP-1040 : Failed to get status of the listeners associated with instance orcl2 on nodelinux2
PRKC-1002 : All the submitted commands did not execute successfully
then I clicked 'OK' to complete the creation.After this:
$>srvctl status database -d orcl
Instance orcl1 is running on node linux1
Instance orcl2 is not running on node linux2
$>srvctl stop database -d orcl
$>srvctl status database -d orcl
Instance orcl1 is not running on node linux1
Instance orcl2 is not running on node linux2
$>srvctl start database -d orcl
PRKP-1040 : Failed to get status of the listeners associated with instance orcl2 on nodelinux2
PRKC-1002 : All the submitted commands did not execute successfully
$>srvctl status database -d orcl
Instance orcl1 is running on node linux1
Instance orcl2 is not running on node linux2
$>srvctl start instance -d orcl -i orcl2
PRKR-1007 : getting of cluster database orcl configuration failed,
PRKC-1020 : Exception while executing the operation on the remote node linux2
PRKO-2005 : Application error: Failure in getting Cluster Database Configuration for: orcl
the oracm and gsdctl are all work well,
I want to know why?
best regards
Message was edited by:
wang_and_yang

please check /etc/hosts on node 2
Example
Cause
~~~~~
The host name is added to the /etc/hosts file for the loopback address.
For example
$cat /etc/hosts
127.0.0.1 stg-rac2 localhost.localdomain localhost
192.168.0.100 stg-rac2 stg-rac2.oracle.com
Fix
~~~~
Change the /etc/hosts file so that the loopback address only points to localhost
For example
127.0.0.1 localhost.localdomain localhost
192.168.0.100 stg-rac2 stg-rac2.oracle.com

Similar Messages

  • Any idea about the pricing of the hardwares for Oracle 10g RAC?

    Hi,
    If I go for 2 nodes RAC using Dell servers and Disk array, any ideas about the prices? (just for the hardwares.)
    Thanks.
    Regards,
    Jason

    It's all about the shared disk(s).
    If you are only ever going to use two (2) nodes a SCSI JBOD solution is cheap. (practical too with ASM as the cluster filesystem / volume manager)
    More than 2 nodes, you step up to certified NFS, iSCSI or FC/AL connected storage. More expensive, faster, more flexible.
    The computers are the cheapest portion of the cost especially with multiple core multiple cpu 64bit linux based servers being so inexpensive.

  • Worries about restarting RAC machines...

    Dear all,
    I have install and configure RAC following hunter_rac10gr2_iscsi document. Everything is ok and running smoothly. BUT I have few doubts in restarting both nodes in RAC. I am not sure after giving a restart to the system, they will run properly or not. As vipca configure virtual IPs at run time only and if I restart the network services or machine the virtual IPs are not pingable and they are only in host file. This might create problems if i restart. There might be others that i might dont know.
    Kindly help me to understand what options must be set and done on permanent basis be4 i give a restart to both machine? Like how to permanently configure virtual IPs and other requirements for RAC.
    Regards,
    Imran

    > I though by giving document reference, like hunter-rac10gr2_iscsi you will have an idea about the
    os and oracle verison
    From the title we can only deduce that you're using 10r2 and SCSI drives. No mention to what patch set version is being used, whether OCFS and/or ASM is used, whether Oracle CRS is used or a vendor CRS stack, or even what o/s is used. Dealing with raw devices for example and not ASMlib, requires different startup settings to ensure that the raw devices are mapped correctly. Using Multipath is again a different config all together. Etc. Etc.
    RAC is a complex s/w stack. Which is why giving a short but accurate breakdown of this stack (with version numbers) is important.

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

    Thank 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

  • Confuse about the document

    Hi,all . From the document ,i had confused about the following .
    Automatic Undo Management in Oracle RAC
    url >> http://docs.oracle.com/cd/B19306_01/rac.102/b28759/adminrac.htm#CHDGAIFJ
    Oracle automatically manages undo segments within a specific undo tablespace that is assigned to an instance. Only the instance assigned to the undo tablespace can modify the contents of that tablespace. However, each instance can read the undo data blocks created by any instance. Also, when performing transaction recovery, any instance can update any undo tablespace, as long as that undo tablespace is not currently being used by another instance for undo generation or transaction recovery
    what's the meaning of above that is bold ?

    Say you're running a 2-node RAC and node 2 dies. The services which were running on node 2 now get re-located to node 1. It is then possible that node 1 will perform transaction rollback/recovery and, when it does so, it will need to be able to read from node 2's undo tablespace (and maybe update the undo segment headers in node 2's undo tablespace, too).

  • What was the point of the race to infinity???

    Why did BT bother with the race to infinity when exchanges that placed near the top will never see infinity, yet exchanges of a similar size that placed near the bottom are getting upgraded within the next few months.  It was just a cheap trick to get peoples hopes up when they had no intention of listening to what people wanted.

    angry2011 wrote:
    So what about other exchanges that placed in the top 50?  My exchange was up there yet I have been told I will never see a fast speed, yet a similar sized exchange that only got 81 votes in the race is due to be upgraded.  How does that work?
    Are you talking about your exchange or your local cabinet
    toekneem
    http://www.no2nuisancecalls.net
    (EASBF)

  • FRM-92101: There was a failure in the forms during startup. this could happend due to invalid configuration

    Dear members,
    I have installed and using developer suite 10g from past 6months in my local desktop windows xp-sp3. i am running the forms using menus in my local desktop.
    But recently all the forms are working fine from menu except one form, when i ran a particular form with out doing any modifications i'm getting the below error.
    FRM-92101: There was a failure in the forms during startup. this could happend due to invalid configuration.
    and the error log at C:\DevSuiteHome_1\j2ee\DevSuite\application-deployments\forms\application.txt is
    13/07/22 12:50:37 formsweb: Forms session <3> aborted: unable to communicate with runtime process.
    13/07/22 12:50:37 formsweb: Forms session <3> exception stack trace:
    java.net.SocketException: Connection reset
      at java.net.SocketInputStream.read(SocketInputStream.java:168)
      at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)
      at java.io.BufferedInputStream.read(BufferedInputStream.java:201)
      at java.io.DataInputStream.readLine(DataInputStream.java:562)
      at oracle.forms.net.HTTPHeaderTool.parseResponseHeader(Unknown Source)
      at oracle.forms.servlet.ListenerServlet.forwardResponseFromRunform(Unknown Source)
      at oracle.forms.servlet.ListenerServlet.doPost(Unknown Source)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:835)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:341)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:816)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
      at com.evermind[Oracle Application Server Containers for J2EE 10g (10.1.2.3.0)].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
      at java.lang.Thread.run(Thread.java:534)
    here is the details of the versions:
    desktop os(no application server): windows xp-sp3.
    forms version: Forms [32 Bit] Version 10.1.2.3.0 (Production)
    im using java version:  Version 6 Update 45 (Build 1.6.0_45-b06)
    the form is using webutil librarys
    getting errors from the browser versions: Internet Explorer 6(xp-sp3) & Google Crome Version 28.0.1500.72 m
    i have tried several times by compiling the form using shft+ctrl+k and create the fmx again using ctrl+t, but still facing the same issue.
    Please help me ASAP, if anyone have any idea about what could be the reason and how could i resolve this issue.
    Thanks,
    Krish.

    Krish,
    Unfortunately, you are dealing with a situation that will require a lot of patients as this type of error is not easy to troubleshoot.
    user7699138 wrote:
    the form is using webutil librarys
    Are any of your other forms that work using WebUtil?  If no - then you may not have completed the WebUtil configuration completely.
    The first troubleshooting step is to display the Java Console (Start => Control Panel => Java => Advanced tab => Java Console node => Show Console) as you may be getting an Java Exception that is not being reported through Forms.
    Craig...

  • After updating to Yosemite, following apps not opening. App Store, Mail, Contacts, Calendars... About the Mac

    After updating to Yosemite, following apps not opening.
    App Store
    Mail
    Contacts
    Calendars
    Reminders
    Maps
    Preview
    About the Mac
    I recently updated to Yosemite and now I am having problems with the above mentioned apps, not opening at all.
    I am unable to check to which version its update to, or even update to next version.

    You ran a defective third-party "utility" such as "CleanMyMac" or "MacCleanse" that purports to "clean up" "junk" files. What it really does is to corrupt the operating system and many applications.   
    The first thing you need to do is remove that software according to the developer's instructions. Never install it, or anything like it, again. Then see below. If you use any iWork applications, you may need to delete them and redownload them from the App Store.
    If you don't already have a current backup, back up all data, then reinstall the OS.* You don't need to erase the startup volume, and you won't need the backup unless something goes wrong. If the system was upgraded from an older version of OS X, you may need the Apple ID and password you used.
    If you use FileVault 2, then before running the Installer you must launch Disk Utility and select the icon of the FileVault startup volume ("Macintosh HD," unless you gave it a different name.) It will be nested below another icon, usually with the same name. Click the Unlock button in the toolbar and enter your login password when prompted. Then quit Disk Utility to be returned to the main Recovery screen.
    There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
    If you installed the Java runtime distributed by Apple and still need it, you'll have to reinstall it. The same goes for Xcode. All other data will be preserved.
    *The linked support article refers to OS X 10.10 ("Yosemite"), but the procedure is the same for OS X 10.7 ("Lion") and later.

  • Interesting discussion about Oracle RAC

    Hi Pros,
    I have 12 servers for database and 2 storages and 2 10Gb switches for interconnect. I organized them into 3 group of servers (RAC dataguard system) that each contains 4 servers where 2 nodes for primary RAC and 2 nodes for standby RAC. Here, 1 storage for primary RACs and 1 storage for strandby RACs (the storage space is divided equally for RACs). Each switch is shared between 3 RAC systems. But later i found out that its recommended that RAC should have dedicated switch.
    Now i have to decide if i need to buy 4 more 10Gb switches or i need to reorganize 3 two-node RACs into 1 six-node RAC system (and also 1 six-node RAC standby).
    I want to discuss pros and cons of separate RAC systems vs one RAC system in a organization. RAC version is 11.2 and not yet any pluggable DB or Cloud DB.
    Thank you in advance

    Thank you for quick and very clear replies.
    I wrote false things about the switches. Its my bad. I asked my sysadmin again and there are 4 switches that each have 16 ports. And switches are redundant to storage and interconnect.
    >Shared infrastructure means running multiple RAC databases on a single cluster. This is known as a policy based RAC. You create a RAC with let's say 8 servers. 2 server pools are created (this is the policy based RAC feature). Pool OLAP contains 5 servers. Pool OLTP contains 3 servers. Each pool runs a RAC database.
    This sound great to me I knew that i need to research about shared infrastructure and server pools
    >The single biggest cons of using this shared infrastructure approach is that an upgrade/patch affects ALL your RAC databases on the cluster. So you cannot plan separate patch rollouts for OLAP and OLTP for example.
    What would be the real need of separating patch? If i need to take down database on upgrade, if separated, i would take down database two database one by one. If shared, i would take down two databases once. To my environment, no difference. (If core database get down, there is no chance to keep working other applications)
    My mind is turning to 1 RAC system for entire organization
    >Depending on the switches used, you can consider partitioning of switch ports - create 4 partitions of 12 ports each for example, for 4 RACs. Or separate private subnets can be used. Etc.
    I'll take a look this too.
    Thank guys

  • Technical reference about the apple system preferences files

    Hi Community,
    is there a technical reference or at least a short description about apples system preferences files in Snow Leopard available? I don't mean the structure of references files as a whole but the meaning and functionality of a specific plist.
    Thx & Bye Tom

    Dave Sawyer wrote:
    [com.apple.loginitems.plist]
    Yes this was my thought too but it didn't drop the login items after I
    threw > the loginitems.plist.
    Some apps may automatically add themselves to this list, controlled by their
    own preferences. But that is indeed the preference that controls that list.
    I'm confused because after this experience I found a lot of tutorials, documentations and forum discussions which describes the loginwindow.plist as the responsible plist for the login items. My suspicion was that the loginitems.plist rebuild process take notice about the content of loginwindow.plist, which is in the root of the matter the same as in loginitems.plist.
    But I couldn't answer this question competent and that's the reason why I'm searching for detailed informations about this "forgotten" loginitems.plist. Forgotten? Try to search for it. Its unbeleavable, 99% of the hits you get belongs to the loginwindow.plist and the description sounds very similar to the functionality of loginitems.plist. But maybe you're right and the applications try to put themselves back into the startup item list. But this doesn't answer the relation between this two plists.
    Thy & Bye Tom

  • About Oracle RAC-CLUSTERS-HTMLDB-APLICATION SERVER

    Im trying to learn about Oracle RAC and its integration with others Oracle tools and have some questions that I want to know .
    1º) I undertand that a Oracle Cluster are vaious computers that store a extensive Database.
    2º) I also understand that a RAC are various computers that keep instances of a ORACLE database, and this database can be store on a CLUSTER.
    Now my questions:
    Can I have others computers with ORACLE TOOLS, by example, HTMLDB ,to serve web pages with information store in that CLUSTER, or ORACLE APPLICATION SERVER, to serve ORACLE FORMS AND REPORTS by example, also with information store in that . taking information from the instances of database working in the RAC&#347; Computer?
    By Example Can I have 5 computers , every one with a diferent tool, 3 with htmldb and 2 with aplication server, taking information from one computer of RAC, that have a instances of this database working?
    Regards everybody

    2º) I also understand that a RAC are various computers that keep instances of a ORACLE database, and this database can be store on a CLUSTER.
    Not quite ...
    Each part in a RAC IS AN INSTANCE, and each instance controls the same database as all the other instances.
    Therefore, HTMLDB, which is simply kept in a database, can be delivererd to the users from any instance, or from all, in the RAC.
    FORMS and REPORTS can connect to any instance in the RAC and get exactly the same data from exactly the same database as when connecting to any other instance in the RAC.
    Therefore, in a RAC, you do not have different instances 'with different tools'. An external-to-database tool, such as forms, points to one olf the instances. An internal-to-database tool, such as htmldb, is available through all of the instances.

  • Where we can know about the stuck threads without taking thread dump.

    Hi Everyone,
    Where we can View/know about the stuck threads without taking thread dump.
    Thank You

    Hi!
    WebLogic Server diagnoses a thread as stuck if it is continually working (not idle) for a set period of time. You can tune stuck threads in the Weblogic Server.
    You can tune a server’s thread detection behavior by changing the length of time before a thread is diagnosed as stuck, and by changing the frequency with which the server checks for stuck threads.
    It can be configured using below mentioned 2 parameters. These can be configured from Admin console -> Servers ->Configuration > Tuning tab.
    1)Stuck Thread Max Time
    2)Stuck Thread Timer Interval
    Although you can change the criteria WebLogic Server uses to determine whether a thread is stuck, you cannot change the default behavior of setting the “warning” and “critical” health states when all threads in a particular execute queue become stuck.
    There is a parameter "Stuck Thread Count" which can be configured from Console
    (Servers -> Configuration ->Overload -> Stuck Thread count) which helps to transition the Server to FAILED state once the stuck threads reaches the value.
    You can also use "OverloadProtectionMBean" for tuning. In Weblogic Server 9.x and later, it is recommended that you use the "ServerFailureTriggerMBean" in the "OverloadProtectionMBean".The ServerFailureTriggerMBean transitions the server to a FAILED state after the specified number of stuck threads are detected.The OverloadProtectionMBean has options to suspend or shutdown a failed server.
    WebLogic Server checks for stuck threads periodically. If all application threads are stuck, a server instance marks itself failed, if configured to do so, exits. You can configure Node Manager or a third-party high-availability solution to restart the server instance for automatic failure recovery.
    You can configure these actions to occur when not all threads are stuck, but the number of stuck threads have exceeded a configured threshold:
    - Shut down the Work Manager if it has stuck threads. A Work Manager that is shut down will refuse new work and reject existing work in the queue by sending a rejection message. In a cluster, clustered clients will fail over to another cluster member.
    - Shut down the application if there are stuck threads in the application. The application is shutdown by bringing it into ADMIN mode. All Work Managers belonging to the application are shut down, and behave as described above.
    - Mark the server instance as failed and shut it down it down if there are stuck threads in the server. In a cluster, clustered clients that are connected or attempting to connect will fail over to another cluster member.
    You can configure the "ServerFailureTriggerMBean" in the "OverloadProtectionMBean".
    Below is documentation link for "ServerFailureTriggerMBean" methods.
    http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13945/weblogic/management/configuration/ServerFailureTriggerMBean.html
    You can use getStuckThreadCount() method to check the number of stuck threads and transition the server to Failed State once itreaches the limit.
    getStuckThreadCount:
    int getStuckThreadCount() - The number of stuck threads after which the server is transitioned into FAILED state. There are options inOverloadProtectionMBean to suspend and shutdown a FAILED server. By default, the server continues to run in FAILED state. If the StuckThreadCount value is set to zero then the server never transitions into FAILED server irrespective of the number of stuck threads.
    Returns:
    The StuckThreadCount value
    Default Value:
    0
    Maximum Value:
    java.lang.Integer.MAX_VALUE
    Minimum Value:
    0
    Below is documentation link for "OverloadProtectionMBean" methods.
    http://download.oracle.com/docs/cd/E11035_01/wls100/javadocs_mhome/weblogic/management/configuration/OverloadProtectionMBean.html
    In the Admin console, you can set the "FailureAction" under Servers->Configuration->Overload to force shutdown the managed server once the server is in Failed state.
    The OverloadProtectionMBean has a method getFailureAction to achieve the same.
    getFailureAction:
    String getFailureAction() - Enable automatic forceshutdown of the server on failed state. The server self-health monitoring detects fatal failures and mark the server as failed. The server can be restarted using NodeManager or a HA agent.
    Valid Values:
    OverloadProtectionMBean.NO_ACTION, OverloadProtectionMBean.FORCE_SHUTDOWN, OverloadProtectionMBean.ADMIN_STATE
    If you start the managed servers using node manager, you can enable "Auto Kill if Failed" and "Auto Restart" in the Admin console, under Servers-> configuration->Health Monitoring. Node Manager will take care of restarting the managed server if you enable "Auto Restart".
    You can also configure the "Stuck Thread Count" and "Failure Action" to "Force Immediate shutdown of the Server" from Admin console under servers-> configuration-> Overload. This will help you to shutdown the server when the stuck thread count is reached. But there is no way to release the threads once they are stuck from the configuration.
    Suppose if you set the value of the Stuck Thread Count to 20, The server will be transitioned to failed state once the count reaches 20 and if you enable the Failure Action, the server self-health monitoring detects fatal failures and mark the server as failed.
    Depending on how you are starting the servers (custom scripts or Node Manager or startup scripts,...), you can restart the servers.
    For more details on this please refer to below link:
    http://www.oracle.com/technetwork/articles/entarch/workload-management-088692.html
    Hope this helps.
    Thanks,
    Cris

  • This is about the KT6 Delta (FIS2R)

    1st, i waited a lonnnnnnnnng time for it to arrive at the shops.
    2nd, was rather boggled by the lack of accessories that came with it (missing the 1) D-Led adapter, 2) USB adapter, 3) the Red rounded cable for PATA, 4)only came with 2 sata cables, 5) no power splitter for SATA drives.
    hmmmm
    Thats all the complaints i have, now to the good stuff
    Its been running solid, I took extra time when constructing the new PC, an important attribute for any PC.
    Everything has been placed precisely, PCI cards in certain slots, HD's in grouped arrays (5 HD's installed), power cables and other cables tucked neatly and non obstructive (and SH*T theres alot of cables in this thing)
    I am unfamiliar with hardware assignments for this mobo, which is to do with windows installs on particular HD setups.
    The HD controllers in particular, just load drivers for the VIA SATA controller if windows is being installed to that drive, and vice versa for the Promise controller.
    Then load the remaining drivers after windows has finished.
    Overclocking the CPU is working fine, im using a XP2400+ with the pin in the socket trick to unlock it.
    its hit 2.3Ghz so far, but i need a better heatsink to cool it.
    Which is my next topic.
    Its been reeeeeeeeeeallllllllllllll hot here, and another one coming tomorrow.
    The CPU has been running hot, and ATM its at 2.2ghz with a 65*C temp recording ive noticed so far at max load. And the chipset is at 55*C, so it can handle the heat coz i havnt had a BSOD with it yet, except for the CPU overclock (but thats a heatsink issue)
    When using the Promise controller, configure it for RAID in bios, it will be alot more reliable i have noticed. (The other config kept getting a "Dirty" assignment by windows and would constantly load the checkdisk before windows startup)
    You can use single drives, and can keep all your data, as long as you understand the bios setup for the promise controller - when it asks if you want to delete the drive or not   etc....)
    So no complaints about the actual mobo hardware at all.
    I love it.
    Here's the hardware specs now or, the chewy gooey stuff!
    If anyone is using Hyper-X PC3500, use these settings listed below in this order;
    Fast
    2
    2
    6
    3
    Auto
    4
    8
    Enabled
    Fast
    Enabled
    RAM @ 2.80 volts
    you should beable to touch the 3GB\second mark with this setting. (i can)
    For SATA RAID, i used 2x120GB Seagates 7200.7 (Firmware 3.05)
    Its hitting 135MB's burst transfer and 90MB's+ on Read/Write Sequential transfers.
    I have 2 Seagate 7200.7 PATA drives on the promise controller, firmware 3.06, configured as single RAID array drives.
    These are getting scores of 45MB's sequential average with 90MB's burst.
    So its all nice n fast, gonna be getting another 512MB HyperX and a new heatsink for OC'ing.
    Aiming for 2.4Ghz, which should speed up everything across the board.
    Later  

    "Isn't it wonderful when a plan comes together?"

  • Question about the gray screen and wheel that keeps on spinning !

    After an update (I now have Mavericks 10.9.3) Safari froze. I tryed starting it again, nothing.
    I restarted my computer (imac early 2008) and got a gray screen,an apple logo and a spinning pin wheel!
    I could get into Disk Utility to 'verify and repair', everything was apparently OK.
    I saw a letter from a few years ago (where it was from, i can'nt remember) it suggested restarting with cammand+v
    to show where the fault was, it then scolled down a lot of witten material and stoppe at :-    'Bootcachecontrol : unable
    to open/var/db/Boot cache. Playlist :2 no such file or dirictory.     I have no idea what it means !
    Can anybody help me ? I miss my Mac !
    Best Wishes from Jonathan Sandberg.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.   
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
         a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.   
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Maybe you are looking for