TNS:listener could not find available handler with matching protocol stack

Hi,
I am getting the following stack trace in b2b.log file:
2009.01.06 at 14:34:35:869: Thread-108: BusinessLogicLayer - (ERROR) caught error: Error -: AIP-13002: SQL error getting the DataSource
2009.01.06 at 14:34:35:870: Thread-108: IP - (ERROR) java.sql.SQLException: Listener refused the connection with the following error:
ORA-12516, TNS:listener could not find available handler with matching protocol stack
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521)))(LOAD_BALANCE=yes)(CONNECT_DATA=(SERVICE_NAME=test)))
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:292)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:327)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:429)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:150)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:113)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:58)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getNewPoolOrXAConnection(OracleConnectionCacheImpl.java:493)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getPooledConnection(OracleConnectionCacheImpl.java:368)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:306)
     at oracle.jdbc.pool.OracleConnectionCacheImpl.getConnection(OracleConnectionCacheImpl.java:285)
     at oracle.tip.buslogic.common.DBConnectivity.getConnection(DBConnectivity.java:151)
     at oracle.tip.buslogic.common.ExecutionContextImpl.getService(ExecutionContextImpl.java:379)
     at oracle.tip.buslogic.common.ExecutionContextImpl.setRuntimeActiveandQuiescing(ExecutionContextImpl.java:799)
     at oracle.tip.adapter.b2b.data.B2BExecutionContext.setRuntimeActiveAndQuiescing(B2BExecutionContext.java:130)
     at oracle.tip.adapter.b2b.data.B2BExecutionContext.activate(B2BExecutionContext.java:98)
     at oracle.tip.adapter.b2b.data.DBContext.initialize(DBContext.java:90)
     at oracle.tip.adapter.b2b.data.DataContext.getNewDBContext(DataContext.java:365)
     at oracle.tip.adapter.b2b.data.DataContext.getDBContext(DataContext.java:346)
     at oracle.tip.adapter.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:232)
     at oracle.tip.transport.basic.FileSourceMonitor.processMessages(FileSourceMonitor.java:858)
     at oracle.tip.transport.basic.FileSourceMonitor.run(FileSourceMonitor.java:302)
When I ran the enquire script. I am getting the following exception:
IPEnqueue start...
Action Name = null
oracle.jms.AQjmsException: ORA-00600: internal error code, arguments: [kwqbgqc: bad state], [1], [1], [], [], [], [], []
ORA-06512: at "SYS.DBMS_AQIN", line 454
ORA-06512: at line 1
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1180)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1512)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:201)
[Linked-exception]
java.sql.SQLException: ORA-00600: internal error code, arguments: [kwqbgqc: bad state], [1], [1], [], [], [], [], []
ORA-06512: at "SYS.DBMS_AQIN", line 454
ORA-06512: at line 1
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:315)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:281)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:638)
at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:183)
at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:872)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1085)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2983)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3025)
at oracle.jms.AQjmsProducer.enqueue(AQjmsProducer.java:1110)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1407)
at oracle.jms.AQjmsProducer.publish(AQjmsProducer.java:1512)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:201)
Error -: AIP-13121: Connection-related error. Please verify that the database server is running.: java.sql.SQLException: Closed Connection
at oracle.tip.buslogic.common.SessionDownException.isSessionDown(SessionDownException.java:96)
at oracle.tip.common.IPException.initIPException(IPException.java:179)
at oracle.tip.common.IPException.<init>(IPException.java:114)
at oracle.tip.repos.core.persistency.DCException.<init>(DCException.java:68)
at oracle.tip.repos.core.driver.CatalogDriver.disconnect(CatalogDriver.java:1666)
at oracle.tip.repos.core.persistency.PersistencyService.disconnect(PersistencyService.java:578)
at oracle.tip.buslogic.common.ExecutionContextImpl.disconnectService(ExecutionContextImpl.java:602)
at oracle.tip.buslogic.common.ExecutionContextManager.cleanContextResources(ExecutionContextManager.java:629)
at oracle.tip.buslogic.common.ExecutionContextManager.leaveContext(ExecutionContextManager.java:581)
at oracle.tip.buslogic.common.ExecutionContextManager.leaveContext(ExecutionContextManager.java:720)
at oracle.tip.adapter.b2b.data.IPEnqueue.main(IPEnqueue.java:245)
Caused by: java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:226)
at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:1041)
at oracle.jdbc.OracleConnectionWrapper.rollback(OracleConnectionWrapper.java:90)
at oracle.tip.repos.core.driver.CatalogDriver.disconnect(CatalogDriver.java:1662)
... 6 more
I tested the database and it was up. Any help is appreciated.

You may be interested in http://www.tek-tips.com/viewthread.cfm?qid=1368266&page=10

Similar Messages

ORA-12516, TNS:listener could not find available handler Weblogic error

Hello,
I have a wierd issue while setting up a datasource in weblogic.
The database am trying to connect to is an Oracle DB and am using a LDAP based URL as the datasource URL in weblogic.
Service name : PSG03900_PEWTER_APPL.WORLD
The LDAP url given was jdbc:oracle:thin:@ldap://oid_ldap_server_ln.csfp.co.uk:1522/PSG03900_PEWTER_APPL.WORLD,cn=OracleContext,dc=uk,dc=csfb,dc=com
driver oracle.jdbc.xa.client.OracleXADataSource
When am trying to setup the datasource and test the connection configuration the test is successful. However when I try to activate the changes I get the following error:
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
Listener refused the connection with the following error: ORA-12516, TNS:listener could not find available handler with matching protocol stack The Connection descriptor used by the client was: (DESCRIPTION = (SDU = 8192) (TDU = 8192) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = PSGLOD2008-SCAN.AP.HEDANI.NET)(PORT = 1522)) (LOAD_BALANCE = ON) (FAILOVER = ON ) ) (CONNECT_DATA = (SERVICE_NAME = PSG03900_PEWTER_APPL.WORLD) (FAILOVER_MODE = (TYPE = SESSION) (METHOD = BASIC) (RETRIES = 20) (DELAY = 5))))
The DBAs have confirmed to me that the database setup on their side is correct as they are able to do a tnsping and sqlplus connectivity succeeds.
I have also tried accessing the database through PL/SQL developer and am able to login however the weblogic activation fails for some wierd reason.
Could I request someone to enlighten me what I am missing here? I have been at it for days now.
Many thanks.
Best Regards,
Vinod
Edited by: 984452 on Jan 27, 2013 11:16 PM

Hi Kishore,
Thank you for the response.
The number of processes has been set to 500 and number of sessions set to 792 and currently the utilization has just reached 15% of the limit set.
We are using Weblogic 9.2 and trying to connect to Oracle 11g database, could the Oracle thin client being used in Weblogic have any issues connecting?
Many thanks.
Vinod

How to trap ORA-12520: TNS:listener could not find available handler in OEM

Hi,
We are using 11G in Linux. We are often receiving "ORA-12520: TNS:listener could not find available handler for requested type of server" error though listener is working properly. My client would like to trap this error through OEM. Can any one please advise me how to implement this one.
We are using 11GR1 OEM in our system.
Thanks in-advance.
Regards
DBA.

Hello,
You may see system parameters used to start the database via the interface:
home->administration->about database->parameters
you may want to modify the PROCESSES parameter to a higher value.
This parameter also modifies the derived SESSIONS parameter, who specifies the maximum number of sessions possible.
These parameters are static, so you need to restart the db after changing.
You can as well see the limit reached by some values querying
select * from v$resource_limit;
These parameters are described in detail in the Reference manual.
HTH,
Andrea

ORA-12516: TNS:listener could not find ... on Windows Server 2003

We are getting "ORA-12516: TNS:listener could not find available handler" while testing asp.net web application.
We have following configuration:
- A 10g database server on Windows Server 2000
- A Web Server running IIS6 on Windows Server 2003
- ODP.Net for 10g client installed on Web Server
we are testing our web app with 75 concurrent users, as far as I can tell we are closing connections in our app and open connection only while retrieving and saving records.
I saw this error very first time when we upgraded our web server to use 10g client. Before that we were using Oracle 9 client and have tested this app with 100 concurrent users without any error.
Does anyone can help or point a resource that can help to resolve this error?
Thanks.

Hi,
You'll likely want to take that up with the networking folks as the error seems to be coming from the Listener.
How many connections does each instance of your app make? If you make the same number of connections via sqlplus for example rather than ODP, do you see the same results? I know creating 60 or sqlplus sessions may not be fun, but it will help determine if this issue is truly somehow related to ODP. It doesnt seem likely it would be, and if ODP can be removed from the picture, it will be that much easier to troubleshoot.
One thing I'd suggest though, is to make sure your app is cleaning up after itself properly to as to use resources efficiently. If you have access to My Oracle Support, see the following note:
Note 730678.1 Oracle Data Provider for .Net Best Practices
Hope it helps,
Greg

Could not find a Handler associated with the following type

i keep randomly getting this error in some of my managed devices.
Could not find a Handler associated with the following type: printer policy.
Does anyone have any clue about this?
Thanks in advance.
Here are the log messages:
[DEBUG] [01/10/2012 11:27:46.218] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Begining to register policy handlers.] [] []
[DEBUG] [01/10/2012 11:27:46.437] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Registering handlers for Policy Handler Registration Module] [] []
[DEBUG] [01/10/2012 11:27:46.437] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Configuration file C:\Program Files\Novell\ZENworks\conf\PolicyHandlersRegistrat ion.xml] [] []
[DEBUG] [01/10/2012 11:27:47.062] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Deserialized 5 handlers] [] []
[DEBUG] [01/10/2012 11:27:47.062] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Got 5 valid handlers to register.] [] []
[DEBUG] [01/10/2012 11:27:47.078] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Loading handler assembly: C:\Program Files\Novell\ZENworks\bin\handlers\launcherconfig. dll] [] []
[DEBUG] [01/10/2012 11:27:47.171] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Registering launcher configuration policy with ActionManager.] [] []
[DEBUG] [01/10/2012 11:27:47.171] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [register handler for launcher configuration policy returning True] [] []
[DEBUG] [01/10/2012 11:27:47.171] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Loading handler assembly: C:\Program Files\Novell\ZENworks\bin\handlers\WindowsGroupPol icyPlural.dll] [] []
[DEBUG] [01/10/2012 11:27:47.296] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Registering grouppolicy with ActionManager.] [] []
[DEBUG] [01/10/2012 11:27:47.296] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [register handler for grouppolicy returning True] [] []
[DEBUG] [01/10/2012 11:27:47.296] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Loading handler assembly: C:\Program Files\Novell\ZENworks\bin\handlers\Printerenf.dll] [] []
[DEBUG] [01/10/2012 11:27:47.390] [1736] [ZenworksWindowsService] [5] [] [printer policy] [] [Creating wrapper] [] []
[DEBUG] [01/10/2012 11:27:47.500] [1736] [ZenworksWindowsService] [5] [] [printer policy] [] [Exception while creating Providers
Exception Details: The type initializer for 'Novell.Zenworks.PolicyHandlers.PrinterPolicy.Zenw orksPrinterProviderPINVOKE' threw an exception.
at Novell.Zenworks.PolicyHandlers.PrinterPolicy.Zenwo rksPrinterProviderPINVOKE.new_PrinterProvider()
at Novell.Zenworks.PolicyHandlers.PrinterPolicy.Print erProviderWrapper.GetProvider(ILoggerWrapper logger)] [] []
[DEBUG] [01/10/2012 11:27:47.515] [1736] [ZenworksWindowsService] [5] [] [printer policy] [] [Exception in Handler constructor
Exception Details: The type initializer for 'Novell.Zenworks.PolicyHandlers.PrinterPolicy.Zenw orksPrinterProviderPINVOKE' threw an exception.
at Novell.Zenworks.PolicyHandlers.PrinterPolicy.Print erProviderWrapper.GetProvider(ILoggerWrapper logger)
at Novell.Zenworks.PolicyHandlers.PrinterPolicy.Print erPolicyHandler..ctor()] [] []
[DEBUG] [01/10/2012 11:27:47.515] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Exception occurred while registering handler printer policy. Exception details: Exception has been thrown by the target of an invocation.] [] []
[DEBUG] [01/10/2012 11:27:47.515] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Inner Exception details: The type initializer for 'Novell.Zenworks.PolicyHandlers.PrinterPolicy.Zenw orksPrinterProviderPINVOKE' threw an exception.] [] []
[DEBUG] [01/10/2012 11:27:47.515] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [register handler for printer policy returning False] [] []
[DEBUG] [01/10/2012 11:27:47.515] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Loading handler assembly: C:\Program Files\Novell\ZENworks\bin\handlers\browserbookmark senf.dll] [] []
[DEBUG] [01/10/2012 11:27:47.531] [1736] [ZenworksWindowsService] [5] [] [browserbookmarkspolicy] [] [Entered the constructor] [] []
[DEBUG] [01/10/2012 11:27:47.531] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Registering browserbookmarkspolicy with ActionManager.] [] []
[DEBUG] [01/10/2012 11:27:47.531] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [register handler for browserbookmarkspolicy returning True] [] []
[DEBUG] [01/10/2012 11:27:47.531] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Loading handler assembly: C:\Program Files\Novell\ZENworks\bin\handlers\dluenf.dll] [] []
[DEBUG] [01/10/2012 11:27:47.671] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Registering dlu policy with ActionManager.] [] []
[DEBUG] [01/10/2012 11:27:47.671] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [register handler for dlu policy returning True] [] []
[DEBUG] [01/10/2012 11:27:47.984] [1736] [ZenworksWindowsService] [5] [] [MessageLogger] [] [Unable to write to event log (Application) using source (Novell.Zenworks.Logger) Exception: System.ComponentModel.Win32Exception: The event log file is full
at System.Diagnostics.EventLog.InternalWriteEvent(UIn t32 eventID, UInt16 category, EventLogEntryType type, String() strings, Byte() rawData, String currentMachineName)
at System.Diagnostics.EventLog.WriteEntry(String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte() rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID, Int16 category, Byte() rawData)
at System.Diagnostics.EventLog.WriteEntry(String source, String message, EventLogEntryType type, Int32 eventID)
at log4net.Appender.EventLogAppender.Append(LoggingEv ent loggingEvent)] [] []
[ERROR] [01/10/2012 11:27:47.671] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [EXTENSIONUTILS.RegistrationModule.FailedRegistrati onMessage] [The following modules could not be registered: printer policy. The configurations of these types would not be applied on this device.] [] []
[DEBUG] [01/10/2012 11:27:47.984] [1736] [ZenworksWindowsService] [5] [] [Policy Handler Registration Module] [] [Completed registration of policy handlers.] [] []
[DEBUG] [01/10/2012 11:27:47.984] [1736] [ZenworksWindowsService] [5] [] [ModuleLoader] [] [Start() for module com.novell.zenworks.module.policyhandlerregistrati onmodule returned successfully] [] []
[DEBUG] [01/10/2012 11:27:47.984] [1736] [ZenworksWindowsService] [5] [] [ModuleLoader] [] [Before calling Initialize() for module com.novell.zenworks.module.remotemanagement at path C:\Program Files\Novell\ZENworks\bin\modules\Novell.Zenworks. RMModule.dll] [] []
[DEBUG] [01/10/2012 11:27:48.046] [1736] [ZenworksWindowsService] [5] [] [ModuleLoader] [] [Initialize() for module com.novell.zenworks.module.remotemanagement returned successfully] [] []
[DEBUG] [01/10/2012 11:27:48.046] [1736] [ZenworksWindowsService] [5] [] [ModuleLoader] [] [Before calling Start() for module com.novell.zenworks.module.remotemanagement at path C:\Program Files\Novell\ZENworks\bin\modules\Novell.Zenworks. RMModule.dll] [] []
[DEBUG] [01/10/2012 11:27:48.046] [1736] [ZenworksWindowsService] [5] [] [Remote Management Module] [] [(RMMODULE_DEBUG)Initialized(RMMODULE_DEBUG)] [] []
[DEBUG] [01/10/2012 11:27:48.078] [1736] [ZenworksWindowsService] [5] [] [Remote Management Module] [] [(RMMODULE_DEBUG) Adding Property Pages (RMMODULE_DEBUG)] [] []
[DEBUG] [01/10/2012 11:27:48.078] [1736] [ZenworksWindowsService] [5] [] [PolicyManager] [] [Entered PolicyManager.RegisterComponent] [] []
[DEBUG] [01/10/2012 11:27:48.078] [1736] [ZenworksWindowsService] [5] [] [PolicyManager] [] [Registered the component remotemgmt] [] []
[DEBUG] [01/10/2012 11:27:48.109] [1736] [ZenworksWindowsService] [5] [] [Remote Management Module] [] [(RMMODULE_DEBUG)Trying to START service in Start Method (RMMODULE_DEBUG)] [] []

matos02,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Oracle error: The listener could not find any available service handlers...?

I'm running Coldfusion 8 and Oracle XE 10, both on IIS 7.
Every so often, I get this message:
[Macromedia][Oracle JDBC Driver][Oracle]ORA-12519 The
listener could not find any available service handlers that are
appropriate for the client connection. One possible cause for this
error is that the server was not configured for the specified
server type (shared/dedicated).
I can restart the OracleServiceXE service and it works fine.
However, I have no clue what is causing this. I believe it all
began once I started using CFSCRIPTS and running queries using that
instead of CFML. Would anyone know what COULD cause this error to
happen and what I should look out for? I am new to Oracle and CF
btw.
Also, I can access it fine through the oracle homepage, but
when I attempt to connect to it from the coldfusion administrator,
it cannot establish a connection to that data source. It is only
after I restart the service that things go back to normal. Thanks.
Ryan

Hello,
Can you provide output of the following? Any other errors along with this error in alert.log file? Also your listener.ora and tnsnames.ora?
lsnrctl>set displaymode verbose
lsnrctl>services your_listener_name
lsnrctl>status
$> sqlplus '/as sysdba'
sql> select * from v$resource_limit;Regards
Edited by: OrionNet on Jan 14, 2009 10:17 PM
Edited by: OrionNet on Jan 14, 2009 10:22 PM

Could not find prepared statement with handle %.

Greetings. I've seen several posts for this error on the web, but no clear cut answers. I captured the code below in profiler, with the intention of replaying in mgmt studio.
However, the attempt end in the following error: "Could not find prepared statement with handle 612."
declare @p1 int
set @p1=612
declare @p2 int
set @p2=0
declare @p7 int
set @p7=0
exec sp_cursorprepexec @p1 output,@p2 output,N'@P0 int,@P1 int,@P2 int,@P3 int,@P4 bit',N'EXEC dbo.mySproc @P0,@P1,@P2,@P3,@P4 ',4112,8193,@p7 output,219717,95,NULL,1,0
select @p1, @p2, @p7
Something noteworthy is that my sproc only has 5 input parameters, but this makes it look like it has many more.
How do I manipulate the code enough to make it work in mgmt studio? Thanks!
TIA, ChrisRDBA

In profiler you would normally see RPC:Starting and RPC:Completed. The statement shown in RPC staring is what you need to pick because as Erland explained, completed would show "funky" behavior.
Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Could not find prepared statement with handle 13

Hi,
I'm having a terrible problem: When I try to execute a SQL Query the following exception is thrown:
* "java.sql.SQLException: [Macromedia][SQLServer JDBC Driver][SQLServer]Could not find prepared statement with handle 13."
This exception is thrown is this line:
boolean returnResultSet = ((PreparedStatement)sqlStatement).execute();
The sqlStatement object is a java.sql.PreparedStatement that was received as a Statement in the method definition.
The following query is being executed in this PreparedStatement:
SELECT id_promocao, ds_nome, id_tipo, ds_sinopse, dt_lancamento, pt_site, pt_caminho_relativo, fl_ativo FROM TAB_CINE_GM ORDER BY ds_nome
I'm using Macromedia JRun 4 build 61650 and I'm using MS-SQL Server 2000 as a database server.
If anyone can help, I'll thanks a lot.
Helcio Chaves
S�o Paulo - SP - Brazil
[email protected]

There is a common way to check runtime type:
if (sqlStatement instanceof PreparedStatement)
returnResultSet = ((PreparedStatement)sqlStatement).execute();
else
returnResultSet = sqlStatement.execute();
}By the way - I can't understand why you're trying to cast sqlStatement to PreparedStatement? It doesn't matter at all due to so-called polymorphism of all Java methods (except static ones). Anyway execute() will run for PreparedStatement but bot for Statement
Enjoy,
Pavel

CF error: The listener could not find any available service handlers...?

I'm running Coldfusion 8 and Oracle XE 10, both on IIS 7. Every so often, I get this message:
[Macromedia][Oracle JDBC Driver][Oracle]ORA-12519 The listener could not find any available service handlers that are appropriate for the client connection. One possible cause for this error is that the server was not configured for the specified server type (shared/dedicated).
I can restart the OracleServiceXE service and it works fine. However, I have no clue what is causing this. I believe it all began once I started using CFSCRIPTS and running queries using that instead of CFML. I know this isn't a coldfusion forum, but would anyone know what COULD cause this error to happen and what I should look out for? I am new to Oracle and CF btw. Thanks.
Ryan

Hi rpeters83 and 396167,
Did you find a solution for this?
We have ColdFusion 7.0.2 connecting to an Oracle Database 10 R2 and we just got this error when executing a ColdFusion component.
This is the first time we see this error and this CF/Oracle setup has been working fine for a long time.
Thanks.

FindByPrimaryKey: Could not find prepared statement with handle 3

I've inherited a WL61 application and been asked to make it work under WL81. We're using SQL Server 2000. We only access two tables. The XML got auto-converted during the upgrade, but I had to correct the RDBMS column names in the weblogic-cmp-jar.xml
The application mostly works except the findByPrimaryKey fails with:
ERROR ExecuteThread: '14' for queue: 'weblogic.kernel.Default' Administrator : TargetSessionBean - Error finding promotion with ID <2>
javax.ejb.FinderException: Problem in findByPrimaryKey while preparing or executing statement: 'weblogic.jdbc.wrapper.PreparedStatement_weblogic_jdbc_base_BasePreparedStatement@95':
java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]Could not find prepared statement with handle 3.
java.sql.SQLException: [BEA][SQLServer JDBC Driver][SQLServer]Could not find prepared statement with handle 3.
at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
I've checked the database table and the row exisits with the appropriate PK (in this case a promotion with ID <2>).
In the WL61 version the findByPrimaryKey was explicitly defined in the weblogic-cmp-rdbms-jar.xml as follows:
<finder>
<method-name>findByPrimaryKey</method-name>
<method-params>
<method-param>com.fujitsu.ftxs.corema.server.PromotionPK</method-param>
</method-params>
<finder-query><![CDATA[ (= $0 promotionId) ]]></finder-query>
<finder-expression>
<expression-number>0</expression-number>
<expression-text><![CDATA[@0.promotionId]]></expression-text>
<expression-type>int</expression-type>
</finder-expression>
</finder
But I understand that with WL81 I should no longer define this - it's done implicitly - so I've removed this finder definition.
Any help appreciated. Thanks,
- Andy Abel

I fixed it by switching from the using the BEA driver:-
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
URL="jdbc:bea:sqlserver://host:1433"
And using the Microsoft Driver instead:-
DriverName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
url=jdbc:microsoft:sqlserver://host:1433
If anyone can explain why the Microsoft Driver works and the BEA driver does not I'd like to know.
Thanks,
- Andy Abel

Could not find prepared statement with handle 1.

[Macromedia][SQLServer JDBC Driver][SQLServer]Could not find prepared statement with handle 1.
I'm getting this error message in what appear to be random ways. The first time I look at a page I might not get it, but the second time I might. I discovered that removing a cfqueryparam tag worked, but that is not really a safe solution. I checked that the cf_sql_type matched the database field, and in one case changed a cf_sql_varchar to a cf_sql_char so it would match a SQL Server nchar(10) field. But still these errors. Any ideas? I've not had any luck Googling this.
I should add that I'm running Coldfusion 9 as a Tomcat webapp on a Linux server. The database is SQL Server 2005, I think.

Here's the one that is breaking now:
<cfquery name="CheckCredentials" datasource="#application.crossreg_dsn#">
                                        SELECT [name_first]+' '+[name_last] as name
                                                    ,p.[uni]
                                                    ,p.email
                                                    ,p.role_id
                                                     ,r.role_name
                                                  ,p.external_program_id
                                          FROM [CrossReg].[dbo].[People] p
                                           INNER JOIN dbo.Roles r on r.role_id = p.role_id
                                          WHERE uni = <cfqueryparam cfsqltype="cf_sql_char" value="#Session.username#">
</cfquery>
Session.username is being returned from a CAS authentication system. I've never had troubles with it before.

ORA-12518: TNS:listener could not hand off client connection

guys,
i have a problem here with the connection between a client host and a server database, using a new non-default listener LISTENER_BKP_1. The error showed is:
ORA-12518: TNS:listener could not hand off client connection
i had learned about this error here before, and i toke some notes as follows:
h2. listener.log
TNSLSNR for 32-bit Windows: Version 10.2.0.1.0 - Production on 25-SEP-2009 01:23:49
Copyright (c) 1991, 2005, Oracle. All rights reserved.
System parameter file is C:\oracle\product\10.2.0\db_2\network\admin\listener.ora
Log messages written to C:\oracle\product\10.2.0\db_2\network\log\listener_bkp_1.log
Trace information written to C:\oracle\product\10.2.0\db_2\network\trace\listener_bkp_1.trc
Trace level is currently 0
Started with pid=2212
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=WINXP)(PORT=1523)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
25-SEP-2009 01:24:39 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=PAULO))(COMMAND=services)(ARGUMENTS=64)(SERVICE=listener_bkp_1)(VERSION=169869568)) * services * 0
25-SEP-2009 01:24:49 * (CONNECT_DATA=(SERVICE_NAME=financeira.winxp)(CID=(PROGRAM=C:\ORACLE?instantclient_10_2\sqlplus.exe)(HOST=PAULO_NOTEBOOK)(USER=ORACLE_DBA))) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.100)(PORT=51649)) * establish * financeira.winxp * 12518
TNS-12518: TNS:listener could not hand off client connection
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
32-bit Windows Error: 2: No such file or directory
25-SEP-2009 01:24:53 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=PAULO))(COMMAND=services)(ARGUMENTS=64)(SERVICE=listener_bkp_1)(VERSION=169869568)) * services * 0
h2. lsnrctl services
C:\>lsnrctl services listener_bkp_1
LSNRCTL for 32-bit Windows: Version 10.2.0.1.0 - Production on 25-SEP-2009 01:33:40
Copyright (c) 1991, 2005, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=WINXP)(PORT=1523)))
Services Summary...
Service "FINANCEIRA.WINXP" has 1 instance(s).
Instance "FINANCEI", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:1
LOCAL SERVER
The command completed successfully
h2. listener.ora file
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = FINANCEIRA.WINXP)
(SID_NAME = FINANCEI)
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = WINXP)(PORT = 1521))
SID_LIST_LISTENER_BKP_1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = FINANCEIRA.WINXP)
(SID_NAME = FINANCEI)
LISTENER_BKP_1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = WINXP)(PORT = 1523))
h2. v$resource_limit
RESOURCE_NAME ; CURRENT_UTILIZATION ; MAX_UTILIZATION ; INITIAL_ALLOCATION ; LIMIT_VALUE
processes ; 26 ; 30 ; 150; 150
sessions ; 30 ; 35 ; 170 ; 170
2 rows selected
this means that it didn't reach the resource limites yet. What i can do to solve the problem ???
another important information is that connecting by the default listener LISTENER instead of the LISTENER_BKP_1 listener, the connection is completed successfully. There's enough SGA memory space too.
Tks,

Paulo_BR wrote:
i have a problem here with the connection between a client host and a server database, using a new non-default listener LISTENER_BKP_1. The error showed is:
ORA-12518: TNS:listener could not hand off client connectionDon't do Oracle on Windows, so I'm not sure how the following relates to the Listener dealing with a dedicated server connection request on Linux/Unix.
On Linux/Unix, a dedicated server request means just that - a dedicated process has to be started to service that client. The Listener does it by using the parameters of the configured listener.ora service to execute +$ORACLE_HOME/bin/oracle+. This process then starts up, and the Listener hands off the client connection for this process for servicing.
If there is a failure somewhere on this series of steps fail, the Listener throws the ORA-12518 exception. For example, the +$ORACLE_HOME+ has been incorrectly configured in listener.ora and it fails to execute and startup a dedicated server process.
And this relates to the underlying error you are seeing:
TNS-12518: TNS:listener could not hand off client connection
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
32-bit Windows Error: 2: No such file or directoryI think that the Listener on Windows uses the CreateRemoteThread() Win32 call to start up the server process thread. However, it needs a valid process identifier (of the existing Oracle instance) for this call - and thus needs to first identify the Oracle instance process. Could be that this step uses a ORACLE_HOME reference. And if that directory path is not valid, it is unable to identify the process id of the Oracle instance and thus unable to spawn a dedicated thread to service that client.

ORA-12518: TNS:listener could not hand off

Hi
we are having oracle11i (11.5.10.2) on windows 2000 Server (service pack 4) database version 10.2.0.3.
we are getting frequently(Once In a week) Error 'ORA-12518: TNS:listener could not hand off' .What could be the reason for that?
Thanks
With Regards
Umair

Hi
i have noticed Below Error in Alert log file
Wed Apr 08 01:12:03 2009
Process m000 died, see its trace file
Wed Apr 08 01:12:03 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:13:04 2009
Process m000 died, see its trace file
Wed Apr 08 01:13:04 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:14:05 2009
Process m000 died, see its trace file
Wed Apr 08 01:14:05 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:15:06 2009
Process m000 died, see its trace file
Wed Apr 08 01:15:06 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:16:07 2009
Process m000 died, see its trace file
Wed Apr 08 01:16:07 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:17:08 2009
Process m000 died, see its trace file
Wed Apr 08 01:17:08 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:18:09 2009
Process m000 died, see its trace file
Wed Apr 08 01:18:09 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:19:10 2009
Process m000 died, see its trace file
Wed Apr 08 01:19:10 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:20:11 2009
Process m000 died, see its trace file
Wed Apr 08 01:20:11 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:21:12 2009
Process m000 died, see its trace file
Wed Apr 08 01:21:12 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:22:13 2009
Process m000 died, see its trace file
Wed Apr 08 01:22:13 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:23:14 2009
Process m000 died, see its trace file
Wed Apr 08 01:23:14 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:24:15 2009
Process m000 died, see its trace file
Wed Apr 08 01:24:15 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:25:16 2009
Process m000 died, see its trace file
Wed Apr 08 01:25:16 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:26:17 2009
Process m000 died, see its trace file
Wed Apr 08 01:26:17 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:27:18 2009
Process m000 died, see its trace file
Wed Apr 08 01:27:18 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:28:19 2009
Process m000 died, see its trace file
Wed Apr 08 01:28:19 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:28:51 2009
Incremental checkpoint up to RBA [0x32.134e1.0], current log tail at RBA [0x32.1362f.0]
Wed Apr 08 01:29:20 2009
Process m000 died, see its trace file
Wed Apr 08 01:29:20 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:30:21 2009
Process m000 died, see its trace file
Wed Apr 08 01:30:21 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:31:22 2009
Process m000 died, see its trace file
Wed Apr 08 01:31:22 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:32:23 2009
Process m000 died, see its trace file
Wed Apr 08 01:32:23 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:33:24 2009
Process m000 died, see its trace file
Wed Apr 08 01:33:24 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:34:25 2009
Process m000 died, see its trace file
Wed Apr 08 01:34:25 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:35:26 2009
Process m000 died, see its trace file
Wed Apr 08 01:35:26 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:36:27 2009
Process m000 died, see its trace file
Wed Apr 08 01:36:27 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:37:28 2009
Process m000 died, see its trace file
Wed Apr 08 01:37:28 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:38:29 2009
Process m000 died, see its trace file
Wed Apr 08 01:38:29 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:39:30 2009
Process m000 died, see its trace file
Wed Apr 08 01:39:30 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:40:31 2009
Process m000 died, see its trace file
Wed Apr 08 01:40:31 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:41:32 2009
Process m000 died, see its trace file
Wed Apr 08 01:41:32 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:42:33 2009
Process m000 died, see its trace file
Wed Apr 08 01:42:33 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:43:34 2009
Process m000 died, see its trace file
Wed Apr 08 01:43:34 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:44:35 2009
Process m000 died, see its trace file
Wed Apr 08 01:44:35 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:45:36 2009
Process m000 died, see its trace file
Wed Apr 08 01:45:36 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:46:37 2009
Process m000 died, see its trace file
Wed Apr 08 01:46:37 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:47:38 2009
Process m000 died, see its trace file
Wed Apr 08 01:47:38 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:48:39 2009
Process m000 died, see its trace file
Wed Apr 08 01:48:39 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:48:51 2009
Incremental checkpoint up to RBA [0x32.137d1.0], current log tail at RBA [0x32.138e9.0]
Wed Apr 08 01:49:40 2009
Process m000 died, see its trace file
Wed Apr 08 01:49:40 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:50:41 2009
Process m000 died, see its trace file
Wed Apr 08 01:50:41 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:51:42 2009
Process m000 died, see its trace file
Wed Apr 08 01:51:42 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:52:43 2009
Process m000 died, see its trace file
Wed Apr 08 01:52:43 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:53:44 2009
Process m000 died, see its trace file
Wed Apr 08 01:53:44 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:54:45 2009
Process m000 died, see its trace file
Wed Apr 08 01:54:45 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:55:46 2009
Process m000 died, see its trace file
Wed Apr 08 01:55:46 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:56:47 2009
Process m000 died, see its trace file
Wed Apr 08 01:56:47 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:57:48 2009
Process m000 died, see its trace file
Wed Apr 08 01:57:48 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:58:25 2009
Process q003 died, see its trace file
Wed Apr 08 01:58:25 2009
ksvcreate: Process(q003) creation failed
Wed Apr 08 01:58:49 2009
Process m000 died, see its trace file
Wed Apr 08 01:58:49 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 01:59:50 2009
Process m000 died, see its trace file
Wed Apr 08 01:59:50 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:00:51 2009
Process m000 died, see its trace file
Wed Apr 08 02:00:51 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:01:52 2009
Process m000 died, see its trace file
Wed Apr 08 02:01:52 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:02:23 2009
Process m000 died, see its trace file
Wed Apr 08 02:02:23 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:02:54 2009
Process m000 died, see its trace file
Wed Apr 08 02:02:54 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:03:55 2009
Process m000 died, see its trace file
Wed Apr 08 02:03:55 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:04:56 2009
Process m000 died, see its trace file
Wed Apr 08 02:04:56 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:05:57 2009
Process m000 died, see its trace file
Wed Apr 08 02:05:57 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:06:58 2009
Process m000 died, see its trace file
Wed Apr 08 02:06:58 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:07:59 2009
Process m000 died, see its trace file
Wed Apr 08 02:07:59 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:08:51 2009
Incremental checkpoint up to RBA [0x32.13aaf.0], current log tail at RBA [0x32.13ba9.0]
Wed Apr 08 02:09:00 2009
Process m000 died, see its trace file
Wed Apr 08 02:09:00 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:10:01 2009
Process m000 died, see its trace file
Wed Apr 08 02:10:01 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:11:02 2009
Process m000 died, see its trace file
Wed Apr 08 02:11:02 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:12:03 2009
Process m000 died, see its trace file
Wed Apr 08 02:12:03 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:13:04 2009
Process m000 died, see its trace file
Wed Apr 08 02:13:04 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:14:05 2009
Process m000 died, see its trace file
Wed Apr 08 02:14:05 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:15:06 2009
Process m000 died, see its trace file
Wed Apr 08 02:15:06 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:16:07 2009
Process m000 died, see its trace file
Wed Apr 08 02:16:07 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:17:08 2009
Process m000 died, see its trace file
Wed Apr 08 02:17:08 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:18:10 2009
Process m000 died, see its trace file
Wed Apr 08 02:18:10 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:19:11 2009
Process m000 died, see its trace file
Wed Apr 08 02:19:11 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:20:12 2009
Process m000 died, see its trace file
Wed Apr 08 02:20:12 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 02:21:29 2009
Process m001 died, see its trace file
Wed Apr 08 02:21:29 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 02:28:51 2009
Incremental checkpoint up to RBA [0x32.1477d.0], current log tail at RBA [0x32.14824.0]
Wed Apr 08 02:32:39 2009
Beginning log switch checkpoint up to RBA [0x33.2.10], SCN: 8174171492544
Thread 1 advanced to log sequence 51
Current log# 2 seq# 51 mem# 0: E:\ORACLE\TESTDATA\LOG02B.DBF
Current log# 2 seq# 51 mem# 1: E:\ORACLE\TESTDATA\LOG02A.DBF
Wed Apr 08 02:37:45 2009
Completed checkpoint up to RBA [0x33.2.10], SCN: 8174171492544
Wed Apr 08 02:48:53 2009
Incremental checkpoint up to RBA [0x33.12574.0], current log tail at RBA [0x33.125ef.0]
Wed Apr 08 03:01:18 2009
Process m001 died, see its trace file
Wed Apr 08 03:01:18 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 03:08:53 2009
Incremental checkpoint up to RBA [0x33.12fd9.0], current log tail at RBA [0x33.13070.0]
Wed Apr 08 03:28:53 2009
Incremental checkpoint up to RBA [0x33.132b6.0], current log tail at RBA [0x33.13340.0]
Wed Apr 08 03:48:53 2009
Incremental checkpoint up to RBA [0x33.13580.0], current log tail at RBA [0x33.13602.0]
Wed Apr 08 04:08:53 2009
Incremental checkpoint up to RBA [0x33.13f0b.0], current log tail at RBA [0x33.13fac.0]
Wed Apr 08 04:28:53 2009
Incremental checkpoint up to RBA [0x33.14264.0], current log tail at RBA [0x33.142ee.0]
Wed Apr 08 04:48:53 2009
Incremental checkpoint up to RBA [0x33.14533.0], current log tail at RBA [0x33.145ad.0]
Wed Apr 08 05:00:45 2009
Process m001 died, see its trace file
Wed Apr 08 05:00:45 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 05:08:53 2009
Incremental checkpoint up to RBA [0x33.14ef0.0], current log tail at RBA [0x33.14f75.0]
Wed Apr 08 05:20:10 2009
Process q003 died, see its trace file
Wed Apr 08 05:20:10 2009
ksvcreate: Process(q003) creation failed
Wed Apr 08 05:25:40 2009
Process q003 died, see its trace file
Wed Apr 08 05:25:40 2009
ksvcreate: Process(q003) creation failed
Wed Apr 08 05:28:53 2009
Incremental checkpoint up to RBA [0x33.1523d.0], current log tail at RBA [0x33.152ad.0]
Wed Apr 08 05:31:10 2009
Process q003 died, see its trace file
Wed Apr 08 05:31:10 2009
ksvcreate: Process(q003) creation failed
Wed Apr 08 05:36:41 2009
Process q003 died, see its trace file
Wed Apr 08 05:36:41 2009
ksvcreate: Process(q003) creation failed
Wed Apr 08 05:47:40 2009
Process q004 died, see its trace file
Wed Apr 08 05:47:40 2009
ksvcreate: Process(q004) creation failed
Wed Apr 08 05:48:53 2009
Incremental checkpoint up to RBA [0x33.15504.0], current log tail at RBA [0x33.15571.0]
Wed Apr 08 05:51:39 2009
Beginning log switch checkpoint up to RBA [0x34.2.10], SCN: 8174171506953
Thread 1 advanced to log sequence 52
Current log# 3 seq# 52 mem# 0: E:\ORACLE\TESTDATA\LOG03B.DBF
Current log# 3 seq# 52 mem# 1: E:\ORACLE\TESTDATA\LOG03A.DBF
Wed Apr 08 05:53:10 2009
Process q004 died, see its trace file
Wed Apr 08 05:53:10 2009
ksvcreate: Process(q004) creation failed
Wed Apr 08 05:56:42 2009
Completed checkpoint up to RBA [0x34.2.10], SCN: 8174171506953
Wed Apr 08 05:58:40 2009
Process q004 died, see its trace file
Wed Apr 08 05:58:40 2009
ksvcreate: Process(q004) creation failed
Wed Apr 08 06:00:16 2009
Process m000 died, see its trace file
Wed Apr 08 06:00:16 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:01:17 2009
Process m000 died, see its trace file
Wed Apr 08 06:01:17 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:02:18 2009
Process m000 died, see its trace file
Wed Apr 08 06:02:18 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:03:19 2009
Process m000 died, see its trace file
Wed Apr 08 06:03:19 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:04:21 2009
Process m000 died, see its trace file
Wed Apr 08 06:04:21 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:05:22 2009
Process m000 died, see its trace file
Wed Apr 08 06:05:22 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:06:23 2009
Process m000 died, see its trace file
Wed Apr 08 06:06:23 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:07:24 2009
Process m000 died, see its trace file
Wed Apr 08 06:07:24 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:08:25 2009
Process m000 died, see its trace file
Wed Apr 08 06:08:25 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:08:55 2009
Incremental checkpoint up to RBA [0x34.237.0], current log tail at RBA [0x34.2aa.0]
Wed Apr 08 06:09:26 2009
Process m000 died, see its trace file
Wed Apr 08 06:09:26 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:10:27 2009
Process m000 died, see its trace file
Wed Apr 08 06:10:27 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:11:28 2009
Process m000 died, see its trace file
Wed Apr 08 06:11:28 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:12:29 2009
Process m000 died, see its trace file
Wed Apr 08 06:12:29 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:13:30 2009
Process m000 died, see its trace file
Wed Apr 08 06:13:30 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:14:31 2009
Process m000 died, see its trace file
Wed Apr 08 06:14:31 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:15:32 2009
Process m000 died, see its trace file
Wed Apr 08 06:15:32 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:16:33 2009
Process m000 died, see its trace file
Wed Apr 08 06:16:33 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:17:34 2009
Process m000 died, see its trace file
Wed Apr 08 06:17:34 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:18:35 2009
Process m000 died, see its trace file
Wed Apr 08 06:18:35 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:19:36 2009
Process m000 died, see its trace file
Wed Apr 08 06:19:36 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:20:37 2009
Process m000 died, see its trace file
Wed Apr 08 06:20:37 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:21:38 2009
Process m000 died, see its trace file
Wed Apr 08 06:21:38 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:22:39 2009
Process m000 died, see its trace file
Wed Apr 08 06:22:39 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:23:40 2009
Process m000 died, see its trace file
Wed Apr 08 06:23:40 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:24:41 2009
Process m000 died, see its trace file
Wed Apr 08 06:24:41 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:25:42 2009
Process m000 died, see its trace file
Wed Apr 08 06:25:42 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:26:43 2009
Process m000 died, see its trace file
Wed Apr 08 06:26:43 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:27:44 2009
Process m000 died, see its trace file
Wed Apr 08 06:27:44 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:28:45 2009
Process m000 died, see its trace file
Wed Apr 08 06:28:45 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:28:55 2009
Incremental checkpoint up to RBA [0x34.4ef.0], current log tail at RBA [0x34.56b.0]
Wed Apr 08 06:29:46 2009
Process m000 died, see its trace file
Wed Apr 08 06:29:46 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:30:47 2009
Process m000 died, see its trace file
Wed Apr 08 06:30:47 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:31:48 2009
Process m000 died, see its trace file
Wed Apr 08 06:31:48 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:32:49 2009
Process m000 died, see its trace file
Wed Apr 08 06:32:49 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:33:50 2009
Process m000 died, see its trace file
Wed Apr 08 06:33:50 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:34:51 2009
Process m000 died, see its trace file
Wed Apr 08 06:34:51 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:35:52 2009
Process m000 died, see its trace file
Wed Apr 08 06:35:52 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:36:53 2009
Process m000 died, see its trace file
Wed Apr 08 06:36:53 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:37:54 2009
Process m000 died, see its trace file
Wed Apr 08 06:37:54 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:38:55 2009
Process m000 died, see its trace file
Wed Apr 08 06:38:55 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:39:56 2009
Process m000 died, see its trace file
Wed Apr 08 06:39:56 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:40:57 2009
Process m000 died, see its trace file
Wed Apr 08 06:40:57 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:41:58 2009
Process m000 died, see its trace file
Wed Apr 08 06:41:58 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:42:59 2009
Process m000 died, see its trace file
Wed Apr 08 06:42:59 2009
ksvcreate: Process(m000) creation failed
Process m000 died, see its trace file
Wed Apr 08 06:43:06 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:44:01 2009
Process m000 died, see its trace file
Wed Apr 08 06:44:01 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:45:02 2009
Process m000 died, see its trace file
Wed Apr 08 06:45:02 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:46:03 2009
Process m000 died, see its trace file
Wed Apr 08 06:46:03 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:47:04 2009
Process m000 died, see its trace file
Wed Apr 08 06:47:04 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:48:05 2009
Process m000 died, see its trace file
Wed Apr 08 06:48:05 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:48:55 2009
Incremental checkpoint up to RBA [0x34.75f.0], current log tail at RBA [0x34.840.0]
Wed Apr 08 06:49:06 2009
Process m000 died, see its trace file
Wed Apr 08 06:49:06 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:50:07 2009
Process m000 died, see its trace file
Wed Apr 08 06:50:07 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:51:08 2009
Process m000 died, see its trace file
Wed Apr 08 06:51:08 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:52:09 2009
Process m000 died, see its trace file
Wed Apr 08 06:52:09 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:53:10 2009
Process m000 died, see its trace file
Wed Apr 08 06:53:10 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:54:11 2009
Process m000 died, see its trace file
Wed Apr 08 06:54:11 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:55:12 2009
Process m000 died, see its trace file
Wed Apr 08 06:55:12 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:56:13 2009
Process m000 died, see its trace file
Wed Apr 08 06:56:13 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:57:14 2009
Process m000 died, see its trace file
Wed Apr 08 06:57:14 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:58:15 2009
Process m000 died, see its trace file
Wed Apr 08 06:58:15 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 06:59:16 2009
Process m000 died, see its trace file
Wed Apr 08 06:59:16 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:00:17 2009
Process m000 died, see its trace file
Wed Apr 08 07:00:17 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:01:18 2009
Process m000 died, see its trace file
Wed Apr 08 07:01:18 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:02:19 2009
Process m000 died, see its trace file
Wed Apr 08 07:02:19 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:03:20 2009
Process m000 died, see its trace file
Wed Apr 08 07:03:20 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:04:21 2009
Process m000 died, see its trace file
Wed Apr 08 07:04:21 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:05:22 2009
Process m000 died, see its trace file
Wed Apr 08 07:05:22 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:06:23 2009
Process m000 died, see its trace file
Wed Apr 08 07:06:23 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:07:24 2009
Process m000 died, see its trace file
Wed Apr 08 07:07:24 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:08:25 2009
Process m000 died, see its trace file
Wed Apr 08 07:08:25 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:08:55 2009
Incremental checkpoint up to RBA [0x34.9dc.0], current log tail at RBA [0x34.ae6.0]
Wed Apr 08 07:09:26 2009
Process m000 died, see its trace file
Wed Apr 08 07:09:26 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:10:27 2009
Process m000 died, see its trace file
Wed Apr 08 07:10:27 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:11:28 2009
Process m000 died, see its trace file
Wed Apr 08 07:11:28 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:12:29 2009
Process m000 died, see its trace file
Wed Apr 08 07:12:29 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:13:30 2009
Process m000 died, see its trace file
Wed Apr 08 07:13:30 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:14:31 2009
Process m000 died, see its trace file
Wed Apr 08 07:14:31 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:15:32 2009
Process m000 died, see its trace file
Wed Apr 08 07:15:32 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 07:16:49 2009
Process m001 died, see its trace file
Wed Apr 08 07:16:49 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 07:28:55 2009
Incremental checkpoint up to RBA [0x34.1268.0], current log tail at RBA [0x34.1448.0]
Wed Apr 08 07:48:55 2009
Incremental checkpoint up to RBA [0x34.16a2.0], current log tail at RBA [0x34.17b8.0]
Wed Apr 08 08:00:39 2009
Process m000 died, see its trace file
Wed Apr 08 08:00:39 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:01:40 2009
Process m000 died, see its trace file
Wed Apr 08 08:01:40 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:02:41 2009
Process m000 died, see its trace file
Wed Apr 08 08:02:41 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:03:42 2009
Process m000 died, see its trace file
Wed Apr 08 08:03:42 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:04:12 2009
Process q004 died, see its trace file
Wed Apr 08 08:04:12 2009
ksvcreate: Process(q004) creation failed
Wed Apr 08 08:04:43 2009
Process m000 died, see its trace file
Wed Apr 08 08:04:43 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:05:44 2009
Process m000 died, see its trace file
Wed Apr 08 08:05:44 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:06:45 2009
Process m000 died, see its trace file
Wed Apr 08 08:06:45 2009
ksvcreate: Process(m000) creation failed
Wed Apr 08 08:08:02 2009
Process m001 died, see its trace file
Wed Apr 08 08:08:02 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 08:08:55 2009
Incremental checkpoint up to RBA [0x34.1955.0], current log tail at RBA [0x34.1fb9.0]
Wed Apr 08 08:28:55 2009
Incremental checkpoint up to RBA [0x34.2270.0], current log tail at RBA [0x34.22d1.0]
Wed Apr 08 08:48:55 2009
Incremental checkpoint up to RBA [0x34.250c.0], current log tail at RBA [0x34.2576.0]
Wed Apr 08 09:01:14 2009
Process m001 died, see its trace file
Wed Apr 08 09:01:14 2009
ksvcreate: Process(m001) creation failed
Wed Apr 08 09:08:55 2009
Incremental checkpoint up to RBA [0x34.2dd9.0], current log tail at RBA [0x34.2e5f.0]
Wed Apr 08 09:26:12 2009
Process q005 died, see its trace file
Wed Apr 08 09:26:12 2009
ksvcreate: Process(q005) creation failed
Wed Apr 08 09:28:56 2009
Incremental checkpoint up to RBA [0x34.3114.0], current log tail at RBA [0x34.3177.0]
Dump file e:\oracle\testdb\10.2.0\admin\test_dbsbkp\bdump\alert_test.log
Wed Apr 08 09:34:28 2009
ORACLE V10.2.0.3.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows 2000 Version V5.0 Service Pack 4
CPU : 4 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:959M/3199M, Ph+PgF:2803M/5085M, VA:1938M/2047M
Wed Apr 08 09:34:28 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_1 parameter default value as e:\oracle\testdb\10.2.0\RDBMS
Autotune of undo retention is turned on.
thanks
Regards
Umair

ORA-12505: TNS:listener could not resolve SID given in connect descriptor

Dear experts,
I restarted server since when i am getting this error while connecting with server.
ORA-12505: TNS:listener could not resolve SID given in connect descriptor
what is that?
and how can i resolve it?

You are not the first person to ask this question.
http://forums.oracle.com/forums/search.jspa?objID=f61&q=ORA-12505
Highly likely you will find your answer in one of the posts.

10.1.3 EA1: ORA-12518, TNS:listener could not hand off client connection

Hi,
Trying to connect to a remote database which worked in 10.1.3 developer preview gives now:
Listener refused the connection with the following error:
ORA-12518, TNS:listener could not hand off client connection
The Connection descriptor used by the client was:
From sqlplus I can connect. I don't have access to the remote database server/configuration. I tried the workarounds specified here
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=139775.1
I deleted
ojdbc14dms.jar ojdbc14.jar
from jdeveloper and copied ojdbc14_g.jar from Oracle 10g release1 (renamed it to ojdbc14.jar). Then it worked.

Hi,
Can you please check the below link from the forum too.
ORA-12518 Tns: Listener could not hand off client conenction
Best regards,
Rafi.
http://rafioracledba.blogspot.com

TNS:listener could not find available handler with matching protocol stack

Similar Messages

Maybe you are looking for