Connect to database instance PRD Failed

Hi,
We had refreshed our SCM quality system last month with production data, since then we are facing problem in BR connect operations like CheckDB, Verif DB, cleanup logs and update stats . When we schedule these operation using DB13 then we get an error  "Connect to database instance PRD failed", but when try to run this manually by clicking excute immediately button then these operations complete succesfully.
Can you please help on this ?
Our version details are as below.
SCM 5.0
Oracle Release 10.2.0.2.0
Thanks,
Chetan

Problems with the OPS$ mechanism? Check SAPNotes 400241 and 50088...
Also check the output of
> R3trans -d
use <sid>adm on os level...
GreetZ, AH

Similar Messages

  • EM Alert: Critical:PROD.test.edu.au - Failed to connect to database instanc

    HI Experts,
    Today i got this alert from oem grid during RMAN bakcup of the PROD database.when i try to connect the database i am able to get into to the DB successfully with out any issues.
    But i am not sure why this error has come and resone behind that.Please advise.
    From: Oracle OEM [mailto:[email protected]]
    Sent: Tuesday, February 22, 2011 11:21 PM
    To: DBA_GROUP
    Subject: EM Alert: Critical:PROD.test.edu.au - Failed to connect to database instance: ORA-00257: archiver error. Connect internal only, until freed. (DBD ERROR: OCISessionBegin).
    Target Name=PROD.test.edu.au
    Target type=Database Instance
    Host=delhi.win.test.edu.au
    Occurred At=Feb 22, 2011 11:20:33 PM EST
    Message=Failed to connect to database instance: ORA-00257: archiver error. Connect internal only, until freed. (DBD ERROR: OCISessionBegin).
    Severity=Critical
    Acknowledged=No
    Notification Rule Name=Database Availability and Critical States
    Notification Rule Owner=SYSMAN
    when i check the alertlog file i could see the following
    Tue Feb 22 23:01:36 2011
    Starting control autobackup
    Control autobackup written to DISK device
    handle '/oracledb/rman_backup/PROD/control_c-197342269-20110222-01'
    Tue Feb 22 23:22:42 2011
    Errors in file /oracle/admin/PROD/udump/hubprd_ora_27069.trc:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-01438: value larger than specified precision allowed for this column
    ORA-06512: at line 2
    PLease let me know the cause of the issues and solution to overcome this issues.
    Regards,
    Salai

    It would appear that your archive location is full. If it is full, then try to get some more free space there by either deleting the old archives or specifying a different location.
    I don't see any mention of a flash recovery area in the log message, but you may also want to confirm that you have reached your space allocated to the FRA.

  • OEM Grid "Failed to connect to database instance: ORA-03135

    Hello all,
    Did anyone know why we get the error in the OEM grid:
    Failed to connect to database instance: ORA-03135: connection lost contact (DBD ERROR: OCISessionBegin).
    We checked the listener and it is running fine. Can someone advice where to look? Thanks.

    Hello,
    1. I tried to ping to the grid control server, and it was successful. However when reviewing the emagent.trc trace file, I noticed the following error:
    SQL = "/* OracleOEM */ BEGIN :succ_sub := 0; dbms_aqadm.enabl"...
    LOGIN = dbsnmp/<PW>@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=mddbbanner8-vip)(PORT=1521))(CONNECT_DATA=(SID=PROD4)))
    2009-01-13 10:44:31 Thread-4113849248 ERROR recvlets.aq: Error enabling user dbsnmp for aq agent mddbbanner8_3872_PROD4 on PROD.loe.corp_PROD4: ORA-06550: line 1, column 65:
    PLS-00201: identifier 'DBMS_AQADM' must be declared
    ORA-06550: line 1, column 65:
    PL/SQL: Statement ignored
    2009-01-13 10:44:31 Thread-4113849248 ERROR recvlets.aq: unable to create subscription on oracle_database PROD.loe.corp_PROD4
    2. In the emdctl.trc trace file, I see these errors:
    2009-01-09 15:54:26 Thread-4136655072 WARN http: snmehl_connect: connect failed to (mddbbanner8:3872): Connection refused (error = 111)
    2009-01-09 15:54:26 Thread-4136655072 ERROR main: nmectla_agentctl: Error connecting to https://mddbbanner8:3872/emd/main. Returning status code 1
    3. Anyone experienced the same errors from 1 and 2 above? Any solution to this issue?
    Thanks.

  • Failed to connect to database instance: ORA-12541: TNS:no listener

    Hello -
    This is the error in grid alert:
    Failed to connect to database instance: ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach).
    But the test of connection string in database configure screen is successful. tnsping works too.
    Grid version: 11.2.0.1.0, no patches.
    Target database version: 10.2.0.2
    Connect string: (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = s08) (PORT = 1528))) (CONNECT_DATA = (SID = S08) (GLOBAL_NAME = S08.WORLD)))
    Any ideas?

    OK.. Are you testing the connectivity from "Preferred Credentials " setting page?
    Try to configure target from
    Targets-->databases--> then select your database and click on "configure" button.
    Enter all the details and press "Test Connection" button once it shows that connection is successful go to next page and finally save the setting.
    Let me know how it goes....

  • ORCL Failed to connect to database instance: Closed Connection.

    Hi all,
    i am getting ORCL Failed to connect to database instance: Closed Connection, on my work environment but when i look into the database it is ok more over this ticket is generated from GridControl , i checked in trace-file but i haven't got any clue what to do in this case please any one help me on this why it is giving this kind of error
    (ORCL Failed to connect to database instance: Closed Connection.)
    Thanks
    venkat
    Edited by: madala03 on Apr 10, 2013 3:32 AM

    Hi ,
    thanks for the reply i checked in listener log , havent got any connection errors but in sqlnet.log
    i got this
    VERSION INFORMATION:
    TNS for Linux: Version 10.2.0.4.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
    Time: 10-JAN-2011 12:08:29
    Tracing not turned on.
    Tns error struct:
    ns main err code: 12564
    TNS-12564: TNS:connection refused
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0

  • Enterprise manager is not able to connect to database instance

    Hi
    I am having a problem with Oracle EM. I would appreciate very much if anyone can help me.
    I installed Oracle on XP which runs on virtual pc on XP as well. Everything is fine, I can connect to database with sqlplus, and there were no errors during installation.
    But the problem is that, when I try to connect to database with EM, it says:
    Enterprise manager is not able to connect to database instance . The state of the components are listed below.
    Can anoyone help me?

    user10637311 wrote:
    When you want OEM DB , your existing DB should be created by DBCA or if suppose manually creaed DB then you have to configure that DB to EM by
    "emca -config dbcontrol db -repos create". for these two cases istener should be running.
    emctl start dbconsole -> to start dbconsole service
    emctl status dbconsole-> status of servicesI am sorry, I was looking at $ORACLE_HOME\admin . And in the proper path, both listener.ora and tnsnames.ora do exist.
    emca -config dbcontrol db -repos create :
    <last part>:
    INFO: This operation is being logged at C:\oracle\product\10.2.0\db_1\cfgtoollog
    s\emca\orcl\emca_2010-02-18_02-01-40-AM.log.
    Feb 18, 2010 2:02:46 AM oracle.sysman.emcp.util.DBControlUtil stopOMS
    INFO: Stopping Database Control (this may take a while) ...
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig createRepository
    INFO: Creating the EM repository (this may take a while) ...
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig invoke
    SEVERE: Error creating the repository
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMReposConfig invoke
    INFO: Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\or
    cl\emca_repos_create_<date>.log for more details.
    Feb 18, 2010 2:03:19 AM oracle.sysman.emcp.EMConfig perform
    SEVERE: Error creating the repository
    Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\orcl\emc
    a_2010-02-18_02-01-40-AM.log for more details.
    Could not complete the configuration. Refer to the log file at C:\oracle\product
    \10.2.0\db_1\cfgtoollogs\emca\orcl\emca_2010-02-18_02-01-40-AM.log for more deta
    ils.
    C:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\or
    cl\emca_repos_create_<date>.log:
    Check if repos user already exists.
    old 6: WHERE username=UPPER('&EM_REPOS_USER');
    new 6: WHERE username=UPPER('SYSMAN');
    old 8: IF ( '&EM_CHECK_TYPE' = 'EXISTS') THEN
    new 8: IF ( 'NOT_EXISTS' = 'EXISTS') THEN
    old 11: raise_application_error(-20000, '&EM_REPOS_USER does not exists..');
    new 11: raise_application_error(-20000, 'SYSMAN does not exists..');
    old 14: ELSIF ( '&EM_CHECK_TYPE' = 'NOT_EXISTS' ) THEN
    new 14: ELSIF ( 'NOT_EXISTS' = 'NOT_EXISTS' ) THEN
    old 17: raise_application_error(-20001, '&EM_REPOS_USER already exists..');
    new 17: raise_application_error(-20001, 'SYSMAN already exists..');
    old 21: raise_application_error(-20002, 'Invalid Check type &EM_CHECK_TYPE');
    new 21: raise_application_error(-20002, 'Invalid Check type NOT_EXISTS');
    DECLARE
    ERROR at line 1:
    ORA-20001: SYSMAN already exists..
    ORA-06512: at line 17

  • Database instance installation failed

    Hi to All,
    I am using Solution Manager 3.2 to install database instance (MaxDB). Central instance has been installed successfuly. Durring installation I got the error:
    CJS-00030 Assertion failed:
    Connection failed to node sapserver:dbmsrv not found
    Please any help on it.
    Aleksandar

    Hi Alexander,
    Check whether dbmsrv instance exists in Max DB or it may be down as well.
    Regards,
    Mike

  • Not able to connect linux database instance in another machine

    Hi,
    I have installed oracle 10g database server in Linux, and i created one database instance. and i have added tns entry and listener entry.
    I am to connect the database on that machine. but not in different machine. i am able to access/ping linux machine in another machine also.
    while creating tns entry for linux database instance in another machine using "netca" i am getting this error.
    Connecting...ORA-12560: TNS:protocol adapter error
    The test did not succeed.
    Some of the information you provided may be incorrect.
    Click Back to review the information provided for net service name, or Change Login to change username.
    I verified listener and tns entry ( i think for this listener configuration is enough) also. and database is up.
    If anybody knows why i am not able to connect linux database in another machine. is there any network configurations other than listener configuration.
    Thanks in advance.

    yes i tried to connect with ORACLE_SID, its successful. and using tnsname like you said.
    Instead of using netca to create the tnsnames.ora entry on the second server, copy the tnsnames.ora entry from the DB server. Then use tnsping to test connection :-i done above but not able to ping the tns name, i am getting this error.
    TNS-12560: TNS:protocol adapter error
    ------------------------------------------------

  • Prerequisite check of database instance installation failed on Solaris

    Dear All,
    Please provide your valuable suggestions in resolving the below issue
    We are installing the SAP NW 7.4 EP as distributed installation
    Application server on RHEL 6 and Oracle database on Solaris 11(SPARC).
    We have installed the SCS instance on RHEL  with out any issues.
    While running prerequisite check of database installation on solaris we are getting below errors.
    "Atleast 500MB of free disk space are required for an diagnostic agent installation"
                     and
    "could not evaluate condition obsolete kernel parameters"
    In the sapinstdev_log file we are getting below lines.
    TRACE     
    Found 0 MB of free space on /dev
    TRACE     
    Prerequisite Checker performing checks: Condition hardware::disk_space from package ::j2ee_smd_inst evaluated to PRCCondEvalResult.FALSE. Message: 'At least 500 MB of free disk space are required for an Diagnostics Agent installation. Found 0 GB.'.
    We have tried to increase space for /dev which is not possible in Solaris (As per the OS team).please find the below reference link.
    /dev and the /devices Namespace (System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle S…
    The/dev file system is loopback-mounted into the zone using a read-only mount.
    Please find the file system created for database instance installation.
    Filesystem             Size   Used  Available Capacity  Mounted on
    rpool/ROOT/solaris      29G   973M        28G     4%    /
    /dev                     0K     0K         0K     0%    /dev
    rpool/ROOT/solaris/var
                            29G    49M        28G     1%    /var
    proc                     0K     0K         0K     0%    /proc
    ctfs                     0K     0K         0K     0%    /system/contract
    mnttab                   0K     0K         0K     0%    /etc/mnttab
    objfs                    0K     0K         0K     0%    /system/object
    swap                    30G   1.5G        29G     5%    /system/volatile
    sharefs                  0K     0K         0K     0%    /etc/dfs/sharetab
    fd                       0K     0K         0K     0%    /dev/fd
    swap                    30G   1.5G        29G     5%    /tmp
    rpool/VARSHARE          29G    40K        28G     1%    /var/share
    h2hpool1/Dump           40G   9.2G        31G    23%    /Dump
    rpool/export            29G    32K        28G     1%    /export
    rpool/export/home       29G    32K        28G     1%    /export/home
    rpool/export/home/admin
                            29G    34K        28G     1%    /export/home/admin
    h2hpool1               244G    31K       235G     1%    /h2hpool1
    h2hpool1/oracle        180G    36K       180G     1%    /oracle
    h2hpool1/oracle/EPD    180G    44K       180G     1%    /oracle/EPD
    h2hpool1/oracle/EPD/112_64
                            10G    31K        10G     1%    /oracle/EPD/112_64
    h2hpool1/oracle/EPD/mirrlogA
                           1.0G    31K       1.0G     1%    /oracle/EPD/mirrlogA
    h2hpool1/oracle/EPD/mirrlogB
                           1.0G    31K       1.0G     1%    /oracle/EPD/mirrlogB
    h2hpool1/oracle/EPD/oraarch
                            20G    31K        20G     1%    /oracle/EPD/oraarch
    h2hpool1/oracle/EPD/origlogA
                           1.0G    31K       1.0G     1%    /oracle/EPD/origlogA
    h2hpool1/oracle/EPD/origlogB
                           1.0G    31K       1.0G     1%    /oracle/EPD/origlogB
    h2hpool1/oracle/EPD/sapdata1
                            30G    31K        30G     1%    /oracle/EPD/sapdata1
    h2hpool1/oracle/EPD/sapdata2
                            30G    31K        30G     1%    /oracle/EPD/sapdata2
    h2hpool1/oracle/EPD/sapdata3
                            30G    31K        30G     1%    /oracle/EPD/sapdata3
    h2hpool1/oracle/EPD/sapdata4
                            30G    31K        30G     1%    /oracle/EPD/sapdata4
    h2hpool1/oracle/EPD/sapreorg
                           2.0G    31K       2.0G     1%    /oracle/EPD/sapreorg
    h2hpool1/oracle/client
                           1.0G    31K       1.0G     1%    /oracle/client
    h2hpool1/oracle/stage
                           5.0G    31K       5.0G     1%    /oracle/stage/112_64
    rpool                   29G    31K        28G     1%    /rpool
    h2hpool1/sapmnt         20G    31K        20G     1%    /sapmnt
    h2hpool1/usr            20G    31K        20G     1%    /usr/sap

    Hi Praveen,
    It looks to be more permission issue rather than space issue. Ensure the file system where you copied the DVD has full permission.
    Check the installation logs for more details on which other file system needs full permission and work accordingly.
    Regards,
    Deepak Kori

  • Test connection in Database component is failed

    In JDeveloper 2.0 when I try test connection in Database
    component I get message:
    borland.jbcl.dataset.DataSetException: End of TNS data channel
    at
    borland.jbcl.dataset.DataSetException.throwException(Compiled
    Code)
    at
    borland.jbcl.dataset.DataSetException.throwException(Compiled
    Code)
    at
    borland.jbcl.dataset.DataSetException.SQLException(Compiled Code)
    at borland.sql.dataset.Database.openConnection(Compiled
    Code)
    java.sql.SQLException: End of TNS data channel
    at
    oracle.jdbc.dbaccess.DBError.check_error(DBError.java:363)
    at
    oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:
    125)
    at
    oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:155)
    at
    java.sql.DriverManager.getConnection(DriverManager.java:91)
    at
    java.sql.DriverManager.getConnection(DriverManager.java:134)
    at borland.sql.dataset.Database.openConnection(Compiled
    Code)
    I try use JDBC Thin 8.0.5 and 8.1.4
    My Applet work is fine. In JDeveloper 1.0 (AppBuider) I not get
    this message.
    It's bug?
    null

    Hi Eugeny,
    If you are using the JDBC 8.0.5 driver to connect to an 8.1.4
    database, you need to make sure of the following:
    * within the JDeveloper IDE, open Project->Project Properties
    from the menu
    * in the libraries list, make sure that Oracle 8.0.5 JDBC appears
    in the list of libraries before BOTH Oracle 8.1.4 JDBC AND
    'Enterprise Java Beans'
    If the Oracle 8.0.5 JDBC library appears after either of the
    above two libraries, select it in the list, and drag it up so
    that it appears first. Save your project and retry the compile.
    I think this may be what is causing the errors. Please reply if
    this does not fix your problem, or if I misunderstood.
    - Laura
    Eugeny Orlov (guest) wrote:
    : In JDeveloper 2.0 when I try test connection in Database
    : component I get message:
    : borland.jbcl.dataset.DataSetException: End of TNS data channel
    : at
    : borland.jbcl.dataset.DataSetException.throwException(Compiled
    : Code)
    : at
    : borland.jbcl.dataset.DataSetException.throwException(Compiled
    : Code)
    : at
    : borland.jbcl.dataset.DataSetException.SQLException(Compiled
    Code)
    : at borland.sql.dataset.Database.openConnection(Compiled
    : Code)
    : java.sql.SQLException: End of TNS data channel
    : at
    : oracle.jdbc.dbaccess.DBError.check_error(DBError.java:363)
    : at
    oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:
    : 125)
    : at
    : oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:155)
    : at
    : java.sql.DriverManager.getConnection(DriverManager.java:91)
    : at
    : java.sql.DriverManager.getConnection(DriverManager.java:134)
    : at borland.sql.dataset.Database.openConnection(Compiled
    : Code)
    : I try use JDBC Thin 8.0.5 and 8.1.4
    : My Applet work is fine. In JDeveloper 1.0 (AppBuider) I not get
    : this message.
    : It's bug?
    null

  • Failed to connect to database instance: ORA-02002: error writing to audit_t

    I have a 4 node cluster and getting this alert very ferquently...
    checking audit_trail gives this error
    SQL> select count(*) from dba_audit_trail
    2 ;
    select count(*) from dba_audit_trail
    ERROR at line 1:
    ORA-01115: IO error reading block from file 1 (block # 108673)
    ORA-01110: data file 1: '+DG_PROD/ngprod/datafile/system.258.665846277'
    ORA-15081: failed to submit an I/O operation to a disk
    Documentation on error says.........
    ORA-02002: error while writing to audit trail
    Cause: The auditing facility is unable to write to the AUDIT_TRAIL table. If this error occurs, SQL statements that are currently being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space.
    Action: Add space to the SYSTEM tablespace or delete rows from the AUDIT_TRAIL table. If these operations fail or do not eliminate the problem, shut down and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE.
    How should I check the system tablespaces ...I'm getting the error....and moreover they are autoextendible....Any idea about the issue

    You can check the space available in any tablespace with a query from dba_free_space;
    Give serious consideration to moving AUD$ out of the system tablespace. Theoretically you can not do this prior to database 11.1.0.7 (where you can use the built-in package DBMS_AUDIT_MGMT.MOVE_DBAUDIT_TABLES). But if you open an SR at metalink they will instruct you to do it manually which keeps everything legal and supported.
    http://www.morganslibrary.org/reference/dbms_audit_mgmt.html
    Also look into using resumable transactions (DBMS_RESUMABLE) to keep these things from happening in the future.
    http://www.morganslibrary.org/reference/dbms_resumable.html

  • Invalid or unknown NLS parameter value specifiedBR0310E Connect to database

    Dear all ,
    While installing Db instance (4.7 e,HPIA64-oracle), in database update stati.
      got error like
    "WARNING 2008-03-19 01:36:25
    Execution of the command "/sapmnt/C2P/exe/brconnect -u / -c -f crsyn -o SAPC2P" finished with return code 3. Output: BR0801I BRCONNECT 6.40 (11)BR0280I BRCONNECT time stamp: 2008-03-19 01.36.25BR0301E SQL error -12705 at location db_connect-2ORA-12705: invalid or unknown NLS parameter value specifiedBR0310E Connect to database instance C2P failed
    ERROR 2008-03-19 01:36:25
    CJS-00288  Could not update database statistics.<br>DIAGNOSIS: Command brconnect -u / -c -f crsyn -o SAPC2P returned 3.<br>SOLUTION: See brconnect.log for details.
    Brconnect.log shows like
    R0801I BRCONNECT 6.40 (11)
    BR0280I BRCONNECT time stamp: 2008-03-19 01.36.25
    BR0301E SQL error -12705 at location db_connect-2
    ORA-12705: invalid or unknown NLS parameter value specified
    BR0310E Connect to database instance C2P failed
    BR0280I BRCONNECT time stamp: 2008-03-19 01.36.25
    BR0804I BRCONNECT terminated with errors
    How resolve this issue.
    Regards,
    satish kumar

    Hi Sergo,
    those notes are a bit outdated, that is the reason I indicate to read the FAQ.
    If you read it carefully you will realize of several things:
    1) the oracle client to be used depends on the SAP kernel version
    2) the way the oracle client is "linked" with the kernel depends also on the version.
    You can take a look at the powerpoint attached to the note.
    For the sake of simplification I'll go from kernel 4.6D (and forgot the exceptions)
    Kernel 4.6D was linked against oracle client 8.0
    The ORA_NLS33 has to point to the NLS files of that version. But oracle made something easier.
    Oracle NLS files for version 8.1 are also compatible with 8.0.
    This means that, even when the client was 8.0, you could use NLS files of 8.1.7 without any error (the one is refered in this thread)
    Another thing is that the oracle client library was included on the SAP kernel, it was statically linked, SAP only needed the NLS files.
    This changed a little with newer kernels.
    What happens with Kernel 6.20?
    SAP does not includes the client inside the KERNEL, now the oracle library is dinamically linked. By default the kernel looks for it on the /oracle/client/81x_64/lib (assumming here 64 bit)
    ORA_NLS33 can point to the oracle client or the oracle home, again we have compatibility.
    But, then oracle start doing "funny" things with oracle 9i.
    SAP kernel 6.40 is dynamically linked against this oracle client version. Now the search directory is /oracle/client/92x_64. But NLS files are not backwards compatible (later on Oracle provided information about a couple of environment variables to be able to use 9i nls files with 8x client)
    it is more, nls files are not even compatible between oracle 9i versions.
    For that reason, it could be that you have installed in your oracle home, lets say 9.2.0.7 and your ORA_NLS33 pointing to the oacle home.
    But SAP kernel is using (if your environmet variables are OK) the library on the /oracle/client/92x_64 and you get the error ORA-12705 even when you think everything is OK.
    Again, my recommendation is to follow the proper note.
    If you are using a kernel that uses the client 9.2 then you have to configure the environment variables as the correspondent note for that client (539922 Installing the ORACLE client software 9.2.X for UNIX t) or other note that could complement it (like installing several clients on one server)
    Hope the explanation is clear.
    Note. This is only valid for UNIX, in windows it is a different history.

  • Ent. Manager is not able to connect to the database instance. ORA-12541

    Hi
    I have installed and configured Oracle 10.2.0.1 on a Microsoft Cluster with Windows 2003 Server.
    Database instance and listener are running OK on both cluster nodes.
    On one of the nodes (pwmssrv1) I configured Enterprise Manager to monitor and control the database.
    At the beginning it worked fine, but after making a reboot on this server the Enterprise Manager cannot see the database instance and listener anymore.
    I already recreated/reinstalled EM and the problem persists.
    When I try to access the Oracle EM I get the errors (it do not show the login page):
    Database Instance
    (it shows the red down arrow)
    Host pwmssrv1
    Port 1521
    SID WMS10
    Oracle Home C:\oracle\product\10.2.0\db_1
    Listener
    (it shows the red down arrow)
    Status Down
    Host pwmssrv1
    Port 1521
    Name FSLEFA_BOCWMS_ORA
    Oracle Home C:\oracle\product\10.2.0\db_1
    Location C:\oracle\product\10.2.0\db_1\network\admin
    Details TNS-12541: TNS:no listener
    Agent Connection to Instance
    (it shows the red down arrow)
    Status Failed
    Details ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach)
    If I do the "emctl status dbconsole" it shows:
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    http://pwmssrv1.BOCWMS.COM:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory C:\oracle\product\10.2.0\db_1/pwmssrv1.BOCWMS.CO
    M_wms10/sysman/log
    I also look into the logs and it shows a few errors (emoms.log):
    2010-02-22 17:09:49,000 [HttpRequestHandler-9300338] ERROR conn.ConnectionService verifyRepositoryEx.433 - Invalid Connection Pool. ERROR = Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:56,000 [HttpRequestHandler-22569956] WARN jdbc.ConnectionCache _getConnection.303 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
    2010-02-22 17:09:56,000 [HttpRequestHandler-22569956] WARN jdbc.ConnectionCache _getConnection.306 - Io exception: The Network Adapter could not establish the connection
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:57,000 [HttpRequestHandler-22569956] ERROR conn.ConnectionService verifyRepositoryEx.433 - Invalid Connection Pool. ERROR = Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:57,000 [EMUI_17_09_57_/console/aboutApplication] ERROR em.console doGet.311 - java.lang.IllegalStateException: Response has already been committed
    java.lang.IllegalStateException: Response has already been committed
    Can someone help me on this problem.
    Thanks in advance.
    Jose

    You need to do some troubleshooting to find exact issue...
    Here are some metalink notes,
    How to Verify Agent Connectivity to 'OMS and Repository' Target using emrepresp.pl [ID 472292.1]
    --Database Status Shows Down Getting Error "Failed to Connect to Database Instance: ORA-12541: TNS:no listener " [ID 402227.1]
    --Error While Configuring the Database from the Grid Control Console [ID 750621.1]
    Hope this helps,
    http://www.oracleracexpert.com/
    Oracle RAC Load balancing and failover
    http://www.oracleracexpert.com/2010/01/oracle-rac-load-balancing-and-failover.html
    Download Oracle Grid Control and ASMLib and Install
    http://www.oracleracexpert.com/2009/08/download-oracle-grid-control-and-asmlib.html

  • 10g RAC database: instances fail after a few days...

    Im afraid I'm new to Oracle, so assume total ignorance when replying!
    We have two servers, db1 and db2 running Oracle under Windows 2K3 web edition [SP1].
    Both have a shared Direct Attached Storage disk, over a Scsi fibre connection.
    The database is set up using instructions found online for RAC.
    Either instance will stop, and the other will take over, after a few days. The problem is, we aren't using the database yet. [There isn't a problem with it, the development people have checked that they can use the database.]
    The two errors [found using the EM console] which seem to be relevant are:
    'Metrics "Database Time Spent Waiting (%)" is at 100 for event class "other"'
    and 'Failed to connect to database instance ... TNS no listener'.
    [Which is obvioulsly the failure]
    I have scoured the web, and the rather dense reference books for Oracle I have access to, and to no avail.
    Another contributing factor is the 'WMI Performance Adaptor' stops and starts on both machines every thirty seconds.
    Any response/guidlines/advise would be greatly appreciated.
    Apologies if I have started this thread in the wrong place!
    James
    Spelling errors - Message was edited by: jmorse

    Tada, it failed at 4am last night.
    Below is the bottom half of the log file.
    2005-09-05 15:27:57.796: Attempting to start `ora.gandlake-db2.ASM2.asm` on member `gandlake-db2`
    2005-09-05 15:28:04.703: Start of `ora.gandlake-db2.ASM2.asm` on member `gandlake-db2` succeeded.
    2005-09-05 15:28:04.921: Attempting to start `ora.x200.x2002.inst` on member `gandlake-db2`
    2005-09-05 15:28:33.359: Start of `ora.x200.x2002.inst` on member `gandlake-db2` succeeded.
    2005-09-05 15:28:40.578: Start of `ora.x200.x2001.inst` on member `gandlake-db1` succeeded.
    2005-09-05 15:28:40.609: CRS Daemon Started.
    2005-09-05 15:28:41.140: Attempting to start >`ora.gandlake-db1.LISTENER_GANDLAKE-DB1.lsnr` on member `gandlake-db1`
    2005-09-05 15:30:06.078: Start of `ora.gandlake-db1.LISTENER_GANDLAKE-DB1.lsnr` on member `gandlake-db1` succeeded.
    `ora.gandlake-db1.vip` on `gandlake-db1` went OFFLINE unexpectedly
    2005-09-06 19:48:35.703: Attempting to stop `ora.gandlake-db1.vip` on member `gandlake-db1`
    2005-09-06 19:48:36.250: Stop of `ora.gandlake-db1.vip` on member `gandlake-db1` succeeded.
    Restarting `ora.gandlake-db1.vip` on `gandlake-db1`
    2005-09-06 19:48:36.312: Attempting to start `ora.gandlake-db1.vip` on member `gandlake-db1`
    2005-09-06 19:48:38.843: Start of `ora.gandlake-db1.vip` on member `gandlake-db1` succeeded.
    Successfully restarted `ora.gandlake-db1.vip` on `gandlake-db1`
    `ora.gandlake-db1.ons` on `gandlake-db1` went OFFLINE unexpectedly
    2005-09-06 22:59:36.875: Attempting to stop `ora.gandlake-db1.ons` on member `gandlake-db1`
    2005-09-06 22:59:38.218: Stop of `ora.gandlake-db1.ons` on member `gandlake-db1` succeeded.
    Restarting `ora.gandlake-db1.ons` on `gandlake-db1`
    2005-09-06 22:59:38.296: Attempting to start `ora.gandlake-db1.ons` on member `gandlake-db1`
    2005-09-06 22:59:40.109: Start of `ora.gandlake-db1.ons` on member `gandlake-db1` succeeded.
    Successfully restarted `ora.gandlake-db1.ons` on `gandlake-db1`
    `ora.gandlake-db1.vip` on `gandlake-db1` went OFFLINE unexpectedly
    2005-09-08 04:47:35.078: Attempting to stop `ora.gandlake-db1.vip` on member `gandlake-db1`
    2005-09-08 04:47:35.734: Stop of `ora.gandlake-db1.vip` on member `gandlake-db1` succeeded.
    `ora.gandlake-db1.vip` ran out of restarts on `gandlake-db1`
    `ora.gandlake-db1.vip` failed on `gandlake-db1`, relocating.
    2005-09-08 04:47:35.875: Attempting to stop `ora.gandlake-db1.LISTENER_GANDLAKE-DB1.lsnr` on member `gandlake-db1`
    2005-09-08 04:47:36.718: Stop of `ora.gandlake-db1.LISTENER_GANDLAKE-DB1.lsnr` on member `gandlake-db1` succeeded.
    2005-09-08 04:47:36.765: Attempting to stop `ora.gandlake-db1.ASM1.asm` on member `gandlake-db1`
    2005-09-08 04:47:37.390: [RUNNABLELISTENER:4648] state change aborted (locked): ora.x200.x2001.inst
    2005-09-08 04:47:44.578: Stop of `ora.gandlake-db1.ASM1.asm` on member `gandlake-db1` succeeded.
    2005-09-08 04:47:44.625: Attempting to stop `ora.x200.x2001.inst` on member `gandlake-db1`
    2005-09-08 04:47:46.531: Stop of `ora.x200.x2001.inst` on member `gandlake-db1` succeeded.
    2005-09-08 04:47:46.625: Attempting to start `ora.gandlake-db1.vip` on member `gandlake-db2`
    2005-09-08 04:47:50.203: Start of `ora.gandlake-db1.vip` on member `gandlake-db2` succeeded.x200 is the name of the database, there are two instances in total, db1 and db2. The company name is 'gandlake', and the machines are called 'gandlake-db1' and 'gandlake-db2'.
    Thanks again.

  • Listener (and database instance) does not starts up automatically: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

    Hi at all.... I'm a newbie with database oracle.,
    I have the follow problem:
    I installed Oracle Database 11g R2 XE on my guest operating system CentOS 6.5.
    I have changed  the hostname in my SO CentOS (where is installed oracle 11g R2 XE) after installation was completed successfully.
    -) Before and during installation the hostname was localhost.
    -) After installation I changed the hostname in VMCentOS
    From the moment I changed the hostname, nothing starts up automatically. In particular, the listener and the database instance does not starts up automatically.
    When I starts up the listener manually and I try to connect to database instance with SQLPLUS i get this error:
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    I think that the problem is due to the changed hostname because I, for testing and debugging purpose, re-installed a new OS CentOS virtual machine, re-installed oracle database 11g and  I have not got that problem. The database instance and the listener starts up automatically!
    Can any one tell me if maybe the problem is related to the hostname changed? ... and Why?
    P.S.: After changed the hostname I have also modified the listener.ora and the tnsnames.ora by modifying the HOST with the correct hostname.

    -) Output of command chkconfig (there isn't any line oracle-xe 0:off   1:off  2:on  3:on  4:on  5:on  6:off):
    [oracle@VMCentOS /]$ chkconfig
    NetworkManager     0:off    1:off    2:on    3:on    4:on    5:on    6:off
    abrt-ccpp          0:off    1:off    2:off    3:on    4:off    5:on    6:off
    abrtd              0:off    1:off    2:off    3:on    4:off    5:on    6:off
    acpid              0:off    1:off    2:on    3:on    4:on    5:on    6:off
    atd                0:off    1:off    2:off    3:on    4:on    5:on    6:off
    auditd             0:off    1:off    2:on    3:on    4:on    5:on    6:off
    blk-availability    0:off    1:on    2:on    3:on    4:on    5:on    6:off
    bluetooth          0:off    1:off    2:off    3:on    4:on    5:on    6:off
    cpuspeed           0:off    1:on    2:on    3:on    4:on    5:on    6:off
    crond              0:off    1:off    2:on    3:on    4:on    5:on    6:off
    cups               0:off    1:off    2:on    3:on    4:on    5:on    6:off
    dnsmasq            0:off    1:off    2:off    3:off    4:off    5:off    6:off
    firstboot          0:off    1:off    2:off    3:on    4:off    5:on    6:off
    haldaemon          0:off    1:off    2:off    3:on    4:on    5:on    6:off
    htcacheclean       0:off    1:off    2:off    3:off    4:off    5:off    6:off
    httpd              0:off    1:off    2:off    3:off    4:off    5:off    6:off
    ip6tables          0:off    1:off    2:on    3:on    4:on    5:on    6:off
    iptables           0:off    1:off    2:on    3:on    4:on    5:on    6:off
    irqbalance         0:off    1:off    2:off    3:on    4:on    5:on    6:off
    jexec              0:off    1:on    2:on    3:on    4:on    5:on    6:off
    kdump              0:off    1:off    2:off    3:on    4:on    5:on    6:off
    lvm2-monitor       0:off    1:on    2:on    3:on    4:on    5:on    6:off
    mdmonitor          0:off    1:off    2:on    3:on    4:on    5:on    6:off
    messagebus         0:off    1:off    2:on    3:on    4:on    5:on    6:off
    netconsole         0:off    1:off    2:off    3:off    4:off    5:off    6:off
    netfs              0:off    1:off    2:off    3:on    4:on    5:on    6:off
    network            0:off    1:off    2:on    3:on    4:on    5:on    6:off
    ntpd               0:off    1:off    2:off    3:off    4:off    5:off    6:off
    ntpdate            0:off    1:off    2:off    3:off    4:off    5:off    6:off
    portreserve        0:off    1:off    2:on    3:on    4:on    5:on    6:off
    postfix            0:off    1:off    2:on    3:on    4:on    5:on    6:off
    psacct             0:off    1:off    2:off    3:off    4:off    5:off    6:off
    quota_nld          0:off    1:off    2:off    3:off    4:off    5:off    6:off
    rdisc              0:off    1:off    2:off    3:off    4:off    5:off    6:off
    restorecond        0:off    1:off    2:off    3:off    4:off    5:off    6:off
    rngd               0:off    1:off    2:off    3:off    4:off    5:off    6:off
    rsyslog            0:off    1:off    2:on    3:on    4:on    5:on    6:off
    saslauthd          0:off    1:off    2:off    3:off    4:off    5:off    6:off
    smartd             0:off    1:off    2:off    3:off    4:off    5:off    6:off
    snmpd              0:off    1:off    2:off    3:off    4:off    5:off    6:off
    snmptrapd          0:off    1:off    2:off    3:off    4:off    5:off    6:off
    spice-vdagentd     0:off    1:off    2:off    3:off    4:off    5:on    6:off
    sshd               0:off    1:off    2:on    3:on    4:on    5:on    6:off
    sysstat            0:off    1:on    2:on    3:on    4:on    5:on    6:off
    udev-post          0:off    1:on    2:on    3:on    4:on    5:on    6:off
    vmware-tools       0:off    1:off    2:on    3:on    4:on    5:on    6:off
    vmware-tools-thinprint    0:off    1:off    2:on    3:on    4:on    5:on    6:off
    wdaemon            0:off    1:off    2:off    3:off    4:off    5:off    6:off
    winbind            0:off    1:off    2:off    3:off    4:off    5:off    6:off
    wpa_supplicant     0:off    1:off    2:off    3:off    4:off    5:off    6:off
    [oracle@VMCentOS /]$
    Moreover in /etc/sysconfig there isn't any file oracle-xe!!!
    At this point, I suspect that something in the installation I mistook.

Maybe you are looking for