Ошибка ora 12500

Problem

Error ossucrs when attempting to login to an Impromptu catalog accessing an Oracle datasource via SQL*Net, or when attempting to test a data source in Framework Manager or accessing a Query Subject in Framework Manager.

Symptom

QE-DEF-0285 Logon Failure
QE-DEF-0325 The cause of the logon failure is:
QE-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 databases in: PMS Retentions

UDA-SQL-0031 Unable to access the PMS Retentions database.
UDA-SQL-0446 Oracle returned an error message.
ORA-12500: TNS: Listener failed to start a dedicated server process.
UDA-SQL-0107 A general exception has occured during the operation «Attach».

This happens even if you are able to test datasource connection in Cognos Connection which is on the different machine.

Error:

ORA-12500 Listener failed to start a dedicated server process

Resolving The Problem

This is an Oracle error message being returned from the Oracle database
layer.

First, confirm that a successful connection can be made
outside of Impromptu or Framework Manager, in SQL*Plus, using the same login.
If this is successful confirm that the following is not true.

For Impromptu: If the Oracle instance that the Impromptu
catalog accesses has been changed, (under the Catalog Tables
dialog), then the catalog was redistributed to Users, the logical Database Name
in the Database Definition will remain the same. However, unless the same
changes are made on the users’ machines, the above error may occur. This is due
to the old instance still being referenced in the cognos.ini file. Remark out
the the database definition in the cognos.ini, and reopen the catalog to
reenter the connection information in the ini file, or
copy the cognos.ini file from the administrator’s machine to replace the users’
cognos.ini files.

Note: Confirm the paths are
correct in the ini if copying over this file. Always back up ini files before
making any changes.

For Framework Manager: Ensure
that you have the Oracle client installed and that tnsnames.ora is configured
correctly, as it will utilize the Oracle client to access to the
database.

If a successful connection cannot be made in SQL*Plus
please contact your DBA or Oracle vendor.

Related Information

[{«Product»:{«code»:»SSTQPQ»,»label»:»IBM Cognos Series 7 PowerPlay»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w\/o TPS»},»Component»:»Impromptu»,»Platform»:[{«code»:»PF016″,»label»:»Linux»},{«code»:»PF025″,»label»:»Platform Independent»},{«code»:»PF033″,»label»:»Windows»}],»Version»:»Cognos 8 BI Cognos Connection 8.1;Cognos 8 BI Framework Manager 8.1;Cognos 8 Software Dev. Kit 8.1;Cognos ReportNet 1.1MR2;Cognos ReportNet 1.1MR3;Impromptu 3.5″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}},{«Product»:{«code»:»SSEP7J»,»label»:»Cognos Business Intelligence»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud \u0026 Data Platform»},»Component»:»Cognos Connection»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}},{«Product»:{«code»:»SSEP7J»,»label»:»Cognos Business Intelligence»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud \u0026 Data Platform»},»Component»:»Framework Manager»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}},{«Product»:{«code»:»SSEP7J»,»label»:»Cognos Business Intelligence»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud \u0026 Data Platform»},»Component»:»Software Development Kit»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}},{«Product»:{«code»:»SUNSET»,»label»:»PRODUCT REMOVED»},»Business Unit»:{«code»:»BU053″,»label»:»Cloud \u0026 Data Platform»},»Component»:»ReportNet»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»»,»label»:»»}},{«Product»:{«code»:»SSTQPQ»,»label»:»IBM Cognos Series 7 PowerPlay»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w\/o TPS»},»Component»:»Impromptu»,»Platform»:[{«code»:»»,»label»:»»}],»Version»:»»,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]

This error appears when the process of starting up a dedicated server process failed and it could be either because the executable could not be found or the environment isn’t set up correctly.

Turn on tracing at the ADMIN level and re-execute the operation. Tracing can be set by adding following clause in listener.ora file and restarting the listener:-

TRACE_LEVEL_listener=admin

Verify that the ORACLE Server executable ($ORACLE_HOME/bin/oracle) is present and has execute (6751) permissions enabled. Ensure that the ORACLE environment is specified correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being called may not be installed on the local hard drive. Please check that the correct Protocol Adapter are successfully linked.

Related posts

my spring-hibernate application run without problem for the past 1 week, but suddenly i get below error. will this caused by configuration error in applicationContext.xml? there is no error on my oracle10g log files (i get below errror every 1-2weeks once)

28 Jul 2010 14:20:19,177 INFO [http-2020-19] - Loading XML bean definitions from class path resource [org/springframework/jdbc/support/sql-error-codes.xml]
28 Jul 2010 14:20:19,224 INFO [http-2020-19] - SQLErrorCodes loaded: [DB2, Derby, H2, HSQL, Informix, MS-SQL, MySQL, Oracle, PostgreSQL, Sybase]
28 Jul 2010 14:20:19,240 WARN [http-2020-19] - Error while extracting database product name - falling back to empty error codes
org.springframework.jdbc.support.MetaDataAccessException: Could not get Connection for extracting meta data; nested exception is org.springframework.jdbc.CannotGetJdbcConnectionException: Could not get JDBC Connection; nested exception is java.sql.SQLException: Listener refused the connection with the following error:
ORA-12500, TNS:listener failed to start a dedicated server process
The Connection descriptor used by the client was:
10.1.0.23:1521:myserver

 at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:293)
 at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:320)
 at org.springframework.jdbc.support.SQLErrorCodesFactory.getErrorCodes(SQLErrorCodesFactory.java:216)
 at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.setDataSource(SQLErrorCodeSQLExceptionTranslator.java:140)
 at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.<init>(SQLErrorCodeSQLExceptionTranslator.java:103)
 at org.springframework.orm.hibernate3.SessionFactoryUtils.newJdbcExceptionTranslator(SessionFactoryUtils.java:145)
 at org.springframework.orm.hibernate3.HibernateAccessor.getDefaultJdbcExceptionTranslator(HibernateAccessor.java:453)
 at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:410)
 at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:424)
 at org.springframework.orm.hibernate3.HibernateTemplate.executeWithNativeSession(HibernateTemplate.java:374)
 at org.springframework.orm.hibernate3.HibernateTemplate.findByCriteria(HibernateTemplate.java:1055)
 at com

my applicationcontext.xml hibernate config

<property name="hibernateProperties">
    <props>



        <prop key="hibernate.dialect">org.hibernate.dialect.Oracle10gDialect</prop>
        <prop key="hibernate.show_sql">false</prop>
        <prop key="hibernate.format_sql">false</prop>
        <prop key="hibernate.use_sql_comments">false</prop>
        <prop key="hibernate.cglib.use_reflection_optimizer">true</prop>  


                      <prop key="hibernate.c3p0.min_size">10</prop>
                        <prop key="hibernate.c3p0.max_size">100</prop>
                        <prop key="hibernate.c3p0.timeout">10</prop>
                        <prop key="hibernate.c3p0.acquireRetryAttempts">30</prop>

                        <prop key="hibernate.c3p0.acquireIncrement">5</prop>

                        <prop key="hibernate.c3p0.idleConnectionTestPeriod">100</prop>

                        <prop key="hibernate.c3p0.initialPoolSize">20</prop>
                        <prop key="hibernate.c3p0.maxPoolSize">100</prop>
                        <prop key="hibernate.c3p0.maxIdleTime">300</prop>
                        <prop key="hibernate.c3p0.maxStatements">50</prop>
                        <prop key="hibernate.c3p0.minPoolSize">10</prop>
                        <prop key="hibernate.c3p0.preferredTestQuery">SELECT 1 FROM DUAL</prop>
                        <prop key="hibernate.c3p0.testConnectionOnCheckout">true</prop>



      <prop key="hibernate.cache.provider_class">

                                                    org.hibernate.cache.EhCacheProvider
        </prop>
        <prop key="hibernate.cache.use_second_level_cache">true</prop>
        <prop key="hibernate.cache.use_query_cache">true</prop>




    </props>
</property>

Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.

sqlplus usr/pwd@orcl
ORA-12500: TNS:listener failed to start a dedicated server process

This error can be seen on Windows platforms when the file LISTENER.ORA located in the directory %ORACLE_HOME%\network\admin contains an explicit database service declaration (see below in green) and the database has not been started:

...
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.1.0\Db_1)
(PROGRAM = extproc)
)
(SID_DESC =
(GLOBAL_DBNAME = orcl)
(ORACLE_HOME = C:\oracle\product\10.1.0\Db_1)
(SID_NAME = orcl)
)
)
...

This means that you should contact the DBA and ask why the database service is down.

A misconfiguration of the TNSNAMES.ora file would lead to different errors, like ORA-12541 (when TCP PORT numbers mismatch for instance).
Note that you can remove the explicit declaration of the database service from the LISTENER.ora file in case you are using a standard listener configuration (on port 1521) because the database should be able to register itself after starting up. If something goes wrong in this case, you may get ORA-12514 or ORA-12505, most likely.

See message translations for ORA-12500 and search additional resources

Solution

Dear Friend, 2nd Sep 2001 17:04 hrs chennai

Welcome to dbasupport.com .I kindly request you to mention O/S and DB version in future.

I persume it should ne windows NT.Its where lot of Problem like this Occurs.With win2000 its still more.

Look at the folowing solution i traced from a simillar problem.

A. TNS-12500 on Microsoft Windows NT
B. Intermittent TNS-12500 Errors on Microsoft Windows NT

A. TNS-12500 on Microsoft Windows NT
——————————————
1. Please make sure that the userid that installed/started
oracle, and started the listener is administrator.

2. Go to the Control Panel by clicking on [START]—>
[Settings]—> [Control Panel] and then double click
on «Services». A window is displayed which
looks similar to this:

+———————————————————+
| |
| Service Status Startup |
+———————————————————+
|OracleNamesService80 Manual |
|OracleServiceORCL Started Auto |
|OracleStartORCL Started Auto |
|OracleTNSListener Started Auto |
|OracleTNSListener80 Manual |
|OracleWebAssistant Manual |
|pcANYWHERE Service Started Manual |
+———————————————————+

Look at «OracleService» and «OracleStart». These two
services are followed by your SID name (in this case ORCL).
These services should be started. If they are not click
on the [START] button on the right side of the dialog box.

3. Verify the SID names shown with «OracleService» and
«OracleStart» in the Control Panel:Services are the same
SID names in the client’s TNSNAMES.ORA and the server’s
LISTENER.ORA files.

4. Make sure that the listener is logged on as the System
Account. You can check this by going into Control
Panel/Services highlight the OracleTNSListener then
click on Startup. The listener should be logged on as
the System Account. Once you make this change make
sure that you stop and start the listener.

5. Make sure that the tnsnames.ora file doesn’t specify the
ORACLE_HOME parameter in the connect_data section. If it
does, remove it.

6. You may want to simply try restarting your instance.

B. Intermittent TNS-12500 Errors on Microsoft Windows NT
———————————————————

1. Increase the amount of memory available to the system
either by removing unnecessary processes or increasing
the amount of physical memory.

2. Increasing the amount of swap space will also
temporarily help relieve the symptoms.

3. Disable OTRACE. OTRACE is a tracing feature that can
cause many problems. OTRACE is enabled by default.
To disable OTRACE:

a. Stop the Oracle database.
b. Go to the orant/otrace/admin directory.
c. Delete all files with a �.dat� extension.
d. Restart the Oracle database.

4. The TNS-12500 can be a result of the ‘processes’
parameter in the init.ora file being too low.

Cheers

Padmam

Attitude:Attack every problem with enthusiasam …as if your survival depends upon it


Re: Solution on Unix platform

Hi, 2nd sep 2001 17:25 hrs chennai

On unix platform look at this link.

http://technet.oracle.com/support/bb…ontent/508.htm

I am sorry the problem is not only with win ,not even with unix ,even not with oracle but with all softwares.

Cheers

Padmam

Attitude:Attack every problem with enthusiasam …as if your survival depends upon it


Понравилась статья? Поделить с друзьями:
  • Ошибка oracle недопустимый идентификатор
  • Ошибка err 4 carrier рефрижератор
  • Ошибка owners manual e34
  • Ошибка orange emu nfs heat
  • Ошибка err 30 canon 60d