TNS Listener stopping frequently.

Hi Team,
From few days i m facing below issue. As i m not aware of Database stuffs finding difficult to trace the error and the root cause for this issue.
Problem: TNS Listener stops even though the service seems to be running. Due to this my application stops and we are not able to access the application.
When i tried connecting to oracle Enterprise management console i get TNS Listener error, so i restarted the TNS listener service and my application services . Then everything worked fine.
I could see few errors in event viewer:
error: Faulting application TNSLSNR.EXE, version 0.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000.
Please let me for further details. Immediate response will be appreciated.
Regards,
Salma

Sada wrote:
Hi All,
Thanks for the reply,
Actually i m usinf export command to take backup. But even my system admin is using Symantec backup procedure to take backup of server.ie all folders prepsent in that server.
Please let me know which is the best solution to take backup.
Regards,
SalmaExport is not a backup of the physical database. It's output cannot be used to recover lost or corrupted database files. It knows nothing about checkpoints, control files, redo sequences etc. It's use is one part of a backup plan, but it is not sufficient on its own.
As a DBA it is your job to be able to recover the db, not your SA's. His backup plan is obviously no good for Oracle databases.

Similar Messages

TNS Listener goes off frequently

I have installed oracle9i on my laptop having operating system Windows XP Home. I have successfully created database, TNS Listener both. I can start TNS Listener as the windows service. But when i try to connect to database using SQL Plus or any other client, TNS Listner goes off. If I start it again, it will be on until next time i will try to connect to database.
This is a strange behaviour of listner i am seeing first time.
If any of you Database GURUs have any idea, why its happening ?
Appreciate your help.
Regards,
Nilesh

Hi 120116
Oracle9i is not certified for XP Home Edition. I have seen a lot of people with that same problem. Regarding that you can not do anything apart from change your OS to XP Professional.
Joel PÃ©rez
http://www.oracle.com/technology/experts

Oracle SID 102TNSListener stops frequently

Hi All,
Recently we installed Oracle 10.2.0.2.0.
Now we observe that Oracle<SID>102TNSListener service is stopping frequently.
We read below application error in event log:
Faulting application TNSLSNR.EXE, version 0.0.0.0, faulting module oranl10.dll, version 10.2.0.1, fault address 0x000232ba.
Can anyone tell us how we can resolve this problem.
Thank you.
Prashanth.R.G.

If you have Metalink support read article "TNS LISTENER (10GR2 WIN32) CRASHES DUE TO MEMORY FAULT IN MODULE ORANL10.DLL" document number 5214373 and see if that applies.
I would suggest upgrading to 10.2.0.3 or higher as the fix is listed in 11.1 and the bug reports lists only one customer as hitting the bug but the report is from Jan. 2007.
Restarting the listener seems to be the suggested action.
HTH -- Mark D Powell --

Listener stop automatically when my application installation is done....

Hi All,
I come across one incidence in my environment that when my application installation is finished , listener at oracle database goes down.
I am using Oracle Enterprise Linxu 5.3 and database is 10.2.0.4.
when looking to listener.log file for more details
18-JUN-2009 03:54:03 * service_update * orcl * 0
18-JUN-2009 03:54:03 * (CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.20.0.120)(PORT=2446)) * establish * ORCL * 12518
TNS-12518: TNS:listener could not hand off client connection
TNS-12571: TNS:packet writer failure
TNS-12560: TNS:protocol adapter error
TNS-00530: Protocol adapter error
Linux Error: 104: Connection reset by peer
I particulary know that there isnot any script calling or linked between my application installation and Database or listener part. then what are the possible cause to put stop the listener automatically? Is there any connection limit reach by listener or something?
please sugget me...

OS has limitations on the processes per user. DB has limitations on resources. You can find a guide in Metalink: 550859.1
According to the error message, it appears to be related to network TCP/IP shortage. At least, that is a place to start. Maybe look at network log or OS system log for possible cause.

TNS Listener Problem in 8.1.6

Hi,
While trying to connect to Oracle 8.1.6 , installed on local machine (OS Windows NT 4.0), using Oracle's thin JDBC drivers I get the following error :
TNS-12500: TNS:listener failed to start a dedicated server process
TNS-12537: TNS:connection closed
My database is running in dedicated mode on the same PC where I am executing this JAVA program.
Any pointer. Any Help will be highly appreciated.
Thanks.
King.

According to Oracle Error Message, action for TNS-12500 is that Check the Listener.ORA is properly been set with the Oracle Environment if not make it and stop and start the Oracle and Listener too. If we faced and we did the above and it was working perfect.

Perculiar ORA-12514 TNS:listener does not currently know of service request

Hi all
I'm not sure if this is the correct place to ask this but I was wondering whether Anyone has ran into a similar problem or know how to solve this seeing as this involes SOA.
I am running Oracle 10g 10.2.0.4 and Oracle SOA 10.1.3.3. I've also written a piece of code that connects to the database using the database's jndi name from a connection pool. I can start the DB and the SOA with no problems however, if I try and connect to the database using one of the connection objects from the connection pool , i.e.
db = connection.getConnection("jdbc/LocalASDBDataSource");
the listener stops working and I get the error message
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
I know that prior to trying to get the connection from the connection pool, the listener works because if i run lsnrctl services, it reports that the listener is up and running but after the point where I try to get the connection i.e.
db = connection.getConnection("jdbc/LocalASDBDataSource");
the listener stops working. If run lsnrctl services, it then reports that the listener supports no services. The only way I can get the service and the listener to start working is to delete the listener and the Service using Net Manager and then recreating it again but then every time that I run the code again, I get back to the error
the funny thiing is that this only started when I increased the processes because I was gettig ORA-12518: TNS:listener could not hand off client connection
The jndi properties file that I use to create my initial context is
java.naming.factory.initial=com.evermind.server.ApplicationClientInitialContextFactory
java.naming.provider.url=opmn:ormi://localhost:6003:oc4j_soa
java.naming.security.principal=oc4jadmin
java.naming.security.credentials=password1
My Listener.ora is
# listener.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\network\admin\listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\oracle\product\10.2.0\db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = DEVPSTEXP)(PORT = 1521))
My TNS Names.ora is
# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
ASDB =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ASDB)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Any help will be greatly appreciated
Thanks!

The tnsname.ora is not used in this situation as the datasource / connection pool connects via jdbc.
What happens if you bounce the database, instead of deleting the service.
It sounds like you are hitting bug 6017068.
Have a look at that patch
cheers
James

TNS Listener unstable.

Hi,
I am experiencing problems with TNS listener with my Oracle8 in my NT machine.
In the services, it shows that it is started but it refused to connect. But when I try to stop it, it prompts me that it was not started. I believe that there is a synch problem with NT and oracle. please help and advice. Thanks!

Since restarting the server solves the problem. I think it is related to 2gb memory restriction in windows. Please use /3g switch or reduce the sga size if possible.
Thanks and Regards,
Satheesh Babu.S
Bangalore.

Error ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

I have a java code that tries to connect to my oracle database.Below given the code snippet.
I am getting error when I ran this code.
Java code.
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.SQLException;
public class jdbc {
   public static void main(String[] args) {
     try {
         Class.forName("oracle.jdbc.OracleDriver");
     } catch (ClassNotFoundException e) {
         e.printStackTrace();
         return;
     Connection connection = null;
     try {
         connection = DriverManager.getConnection(
                 "jdbc:oracle:thin:@localhost:1521:XE", "SCOTT",
                 "password");
     } catch (SQLException e) {
         e.printStackTrace();
         return;
Error I am getting is
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
Can Someone explain me what is wrong here?

Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ip
(DESCRIPTION=(ADDRESS=(PROTOCOL=tc
Services Summary...
Service "CLRExtProc" has 1 instance(
Instance "CLRExtProc", status UNKN
Service "PLSExtProc" has 1 instance(
Instance "PLSExtProc", status UNKN
The command completed successfully
Obviously there is no handler for XE service.
Maybe you changed hostname(this should be "Owner-PC") ?
Try to manually start/stop db and see if there are some errors:
sqlplus / as sysdba
startup
shutdown immediate
If after that you still can't find cause, try to ask on oracle db forum.
Dario

OEM 10g - ORA-12505: TNS:listener does not currently know of SID...

Hello,
In OEM (version 10.1.0.5 on Red Hat linux 4), on the page Database Instance: dbexemple.domain.be
It says:
- Database Instance > up
- Listener > up
- Agent connection to database > Status: Failed
Details: Failed to connect to database instance: ORA-12505: TNS:listener does not currently know of SID given in connect descriptor (DBD ERROR: OCIServerAttach).
And my OEM database is always in Blackout state.
I can connect on the database and if I select from global_name it gives me the good name.
If I do lsnrctl status
Service "dbexemple.domain.be" has 1 instance(s).
Instance "emrep", status READY, has 1 handler(s) for this service...
If I do lsnrctl services
Service "dbexemple.domain.be" has 1 instance(s).
Instance "dbexemple", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:44 refused:0 state:ready
LOCAL SERVER
So all looks normal. But my DB is still in blackout state.
I did stop and start the agent > no change
I did shutdown and start the database > no change
I did stop the agent delete the $oracle_home/sysmen/emd/... files and start the agent and emctl upload... > no change
In the targets.xml file from the agent I have:
<Target TYPE="oracle_database" NAME="dbexemple.domain.be">
<Property NAME="OracleHome" VALUE="/oracle/product/db10g"/>
<Property NAME="UserName" VALUE="###" ENCRYPTED="TRUE"/>
<Property NAME="MachineName" VALUE="machine.domain.be"/>
<Property NAME="Port" VALUE="1521"/>
<Property NAME="SID" VALUE="dbexemple"/>
<Property NAME="ServiceName" VALUE="dbexemple.domain.be"/>
<Property NAME="password" VALUE="###" ENCRYPTED="TRUE"/>
</Target>
Seems good also
My tnsnames.ora
DBEXEMPLE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = machine.domain.be)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = dbexemple.domain.be)
tnsping dbexemple is also good:
Used LDAP adapter to resolve the alias
Attempting to contact (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=machine)(PORT=1521)))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=dbexemple.domain.be)))
OK (10 msec)
The DB is not in the listener.ora but anyway at the startup of the database the database register in the listener (can take some seconds).
In OEM if I look at blackout, it says no blackout exists
So after all these verifications my OEM database is still in blackout status and remain in blackout.
I would like to find the reason why it stays like this and the agent finally stop giving me an error.
thank you for your help,
Loïc

The fact is that I did not set any blackout for the emrep database. (no blackout are set at the moment in fact)
So, we did change the HDD of the computer were was OEM to another HDD.
The update to 10.1.0.5 was made before all this (2 weeks) and no problem appears after that.
There's no blackout in OEM Blackouts:
No Blackouts found.
and no blackout with emctl:
[oracle@computeroem bin]$ ./emctl status blackout
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
No Blackout registered.
[oracle@computeroem bin]$ ./emctl status blackout emrep
Oracle Enterprise Manager 10g Release 10.2.0.1.0.
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
No Blackout registered.
At the link:
http://computeroem.domain.be:4889/em/console/health/healthSystemError
I get these:
Loader
https://computeroem.domain.be:3872/emd/main/
14-Jan-2007 10:32:32 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target up received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts = 2007-01-14 22:32:27) (violation_level =CLEAR) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 959 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 277, File name:Severity
Loader
https://computeroem.domain.be:3872/emd/main/
14-Jan-2007 10:32:32 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000003.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000003.xml
Blackouts
n/a
14-Jan-2007 6:19:26 PM
Error
Duplicate start blackout record for 39EDA0C7E44C422698958F9463393C52 for target E9A00D9D6447DF4BE1CF43F7A94BF402
Loader
https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 3:07:22 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target up received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts = 2007-01-12 15:07:05) (violation_level =CLEAR) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 959 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 14, File name:Severity
Loader
https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 3:07:22 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000002.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000002.xml
Loader
https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 3:04:44 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target down received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts= 2007-01-12 14:56:52) (violation_level =CRITICAL) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 818 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 14, File name:Severity
Loader
https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 3:04:44 PM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000001.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000001.xml
Blackouts
n/a
12-Jan-2007 10:10:23 AM
Error
end_blackout: unexpected current state 10
Blackouts
n/a
12-Jan-2007
10:05:28 AM
Error
Duplicate start blackout record for FD1380AAEB69BAE53339F58EA0C83ADC for target E9A00D9D6447DF4BE1CF43F7A94BF402
Loader
https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 9:57:16 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000001.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000001.xml
Loader https://computeroem.domain.be:3872/emd/main/
12-Jan-2007 9:57:15 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target up received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts = 2007-01-12 09:56:53) (violation_level =CLEAR) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 959 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 270, File name:Severity
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 9:07:17 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target up received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts = 2007-01-08 09:07:02) (violation_level =CLEAR) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 959 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 25, File name:Severity
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 9:07:17 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000003.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000003.xml
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 9:04:10 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000002.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000002.xml
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 9:04:09 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target up received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts = 2007-01-08 09:01:54) (violation_level =CLEAR) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 959 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 151, File name:Severity
Blackouts
n/a
8-Jan-2007 8:57:47 AM
Error
Duplicate start blackout record for 39EDA0C7E44C422698958F9463393C52 for target E9A00D9D6447DF4BE1CF43F7A94BF402
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 8:56:00 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ Loaded B0000000001.xml with errors; moving to errors directory, File name:/oracle2/product/oms10g/sysman/recv/B0000000001.xml
Loader
https://computeroem.domain.be:3872/emd/main/
8-Jan-2007 8:56:00 AM
Error
Thread: SeverityLoad https://computeroem.domain.be:3872/emd/main/ java.sql.SQLException: ORA-20615: Severity received during blackout for : Target down received during blackout for : (target_guid = E9A00D9D6447DF4BE1CF43F7A94BF402) (policy_guid=3BF84446B273FE1F5743FD6293C7E192) (key_value= ) (collection_ts= 2007-01-06 01:25:35) (violation_level =CRITICAL) ORA-06512: at "SYSMAN.EM_VIOLATION_CHECKS", line 818 ORA-04088: error during execution of trigger 'SYSMAN.EM_VIOLATION_CHECKS' Error occured at line : 14, File name:Severity
For the note, mostly I cannot do anything because I have no blackout name for the script. Still reading the note to see if some sql can help.
Message was edited by:
Loic

TNS Listener Service won't start after upgrading server from NT to 2000

I am new to Oracle and have worked my way through downloading and installing Oracle Enterprise Edition on an NT 4.0 SP6a server and I believe the installation was successful--I was able to run the Oracle Enterprise Manager successfully and I browsed the Oracle services in NT and they all appeared to be working.
I upgraded NT to Windows 2000 Server and Service Pack 2 yesterday and after that I am unable to run Oracle Enterprise Manager and have noticed that the TNS Listener will not start. Actually it starts and immediately stops. It does not cause any messages in the Event Viewer.
Any help on how to proceed would be very gratefully received.
I am a database administrator with a school district and are evaluating/comparing Oracle vs. SQL Server 2000 for creating a data warehouse.
Thanks!

Srinivasa and Allen,
Thank you very much for your replies. I tried the lsnrctl show connect_timeout command and got a message that connect_timeout was an invalid parameter. Is that true of 9i? However, I used the help show command and tried some of the other parameters and the error messages said something about not being able to locate the host. At that point I recalled that at the same time I was upgrading the server to Windows 2000 I also changed the name of the server from MISNT to just MIS.
At that point I renamed the server back to MISNT and after rebooting, the TNS listener works fine. I do want to change the server name back to MIS. It appears there is a configuration file somewhere that has the host name in it that I will need to change. It makes me wonder if there are any other places where I am going to need to change this before I'm done. Will I be better off to just completely uninstall Oracle, change the server name and then reinstall?
Thanks!
Rick

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-12528: TNS:listener:

Hi,
i have a database for learning purpose. i got this error when i connected to database.
may i know what could cause this to happen?
Enter user-name: sys@baba as sysdba
Enter password:
ERROR:
ORA-12528: TNS:listener: all appropriate instances are blocking new connections
Regards
Ravikumar.A

Hi,
1. Stop the listener.
2. Login to idle instance.
3. Start the database and see what is the error you are getting.it has been stopped, and now it is begin started .
i tried to connect a database, i got this error.
Enter user-name: sys@baba as sysdba
Enter password:
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

TNS Listener Security

Hi all,
Our E-Business Suite support is fully outsourced. We have 3 Administrators at the outsourced company who are the ONLY ones with root access,ORACLE_HOME owners and these 3 are the only ones in the DBA group. Because of this limited number admins (the 3 of them) they claim they dont need a TNS Listener password, tns listener admin restrictions switched on or tns listener logging enabled. Does this sound reasonable.

If a password is not set on the listener, anyone who knows hostname and port number has full control over the listener. Hence, the Listener files can be compromised or corrupted or even a Denial of Service Attack can be launched against the system. In this type of attack, the attacker is able to stop the listener, set a listener password so that the listener cannot be started without a password, although the DBA simply has to edit the file and remove the password line.
My personal recommendation is, Continue to have adequate password controls for access to LISTNER. The DBA should ensure that the password is encrypted.

TNS Listener error while opening a Form !

Hi all,
I have installed Form/Reports 11gr2 with Weblogic 10.3.6 64-bit & database 11gr2.
All installations and configures are successful.
But when I give URL address (servername:portno/forms/frmservlet?form=main) to open a form, it gives me following error;
ora-12514: TNS:listener does not currently know of service requested in connect descriptor.
I searched on google, but didn't clear my error. I also checked Oracle services, all are started.
So please guide me !
Thanks/Regards.
Dass

I never changed settings in tnsnames.ora, it is always as per default settings. If required now then let me know.
Please note that when I connect my form builder with databases, it is connected. But when I run my form it again show same error and open a dialog box for
username,password & databases connection string.
I copied this file into "E:\Oracle\Middleware\asinst_1\config" of form.
Below is my tnsnames.ora file;
# tnsnames.ora Network Configuration File: E:\app\admin\product\11.2.0\dbhome_1\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
    (CONNECT_DATA =
      (SID = CLRExtProc)
      (PRESENTATION = RO)
ORCL =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = orcl)
Thanks.

ORA-12514: TNS:listener does not currently know of service requested

While connecting "sqlplus SYSADM/SYSADM@HCM" I am getting the below error:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Installation background:
Windows 7 l(64-bit) laptop.
Created linux virtualbox to installl peoplesoft VM templates.
so far installed: Oracle11gR2.vdi and HCMDB.vdi on the linux virtualbox.
Followed the steps exactly what it is in the link below: Got the above error in page 4 of the link at connecting to database via sqlplus.
http://bloggingaboutoracleapplications.org/running-oracle-vm-templates-oracle-enterprise-linux-guide-part-1-7/
Below provided initHCM.ora, tnsnames.ora, listerner.ora and some responses I tried. I could not figure out what causing the issue even after researching in web.
Your help would be highly appreciated.
tnsnames.ora:
=============
# tnsnames.ora Network Configuration File:
HCM =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hcmdb91)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = HCM)
Listener.ora:
=============
# listener.ora Network Configuration File:
/u01/app/oracle/product/11.2.0.x/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hcmdb91)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
initHCM.ora:
============
DB_FILES =256
OPEN_CURSORS = 1000
db_block_size = 8192
remote_login_passwordfile = NONE
undo_tablespace=PSUNDOTS
NLS_LENGTH_SEMANTICS=CHAR
# Cache and I/O
#db_block_size=
db_file_multiblock_read_count=16
# Database Identification
# db_domain=us.oracle.com
# db_name=
# Diagnostics and Statistics
#background_dump_dest=
#core_dump_dest=
#user_dump_dest=
# Job Queues
job_queue_processes=10
# Processes and Sessions
processes=150
# SGA Memory
sga_target=287309824
# Security and Auditing
#audit_file_dest=
#remote_login_passwordfile=EXCLUSIVE
# Shared Server
dispatchers="(PROTOCOL=TCP) (SERVICE=XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=95420416
# System Managed Undo and Rollback Segments
undo_management=AUTO
#undo_tablespace=
unnestsubquery=false
# Miscellaneous
compatible=11.2.0.2.0
control_files=(/u01/app/oracle/oradata/HCM/control01.ctl)
DB_NAME=HCM
[oracle@hcmdb91 ~]$ tnsping hcm
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013
07:40:37
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
hcmdb91)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME =
HCM)))
OK (20 msec)
[oracle@hcmdb91 ~]$
[oracle@hcmdb91 ~]$ tnsping hcm
TNS Ping Utility for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013
07:40:37
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
hcmdb91)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME =
HCM)))
OK (20 msec)
[oracle@hcmdb91 ~]$ lsnrctl start
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:41:32
Copyright (c) 1991, 2010, Oracle. All rights reserved.
TNS-01106: Listener using listener name LISTENER has already been started
[oracle@hcmdb91 ~]$ lsnrctl status
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:42:20
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hcmdb91)(PORT=1521)))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.2.0 - Production
Start Date 28-MAR-2013 07:29:21
Uptime 0 days 0 hr. 13 min. 1 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File
/u01/app/oracle/product/11.2.0.x/db_1/network/admin/listener.ora
Listener Log File
/u01/app/oracle/product/11.2.0.x/db_1/log/diag/tnslsnr/hcmdb91/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=hcmdb91.example.com
)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
The listener supports no services
The command completed successfully
[oracle@hcmdb91 ~]$ lsnrctl services
LSNRCTL for Linux: Version 11.2.0.2.0 - Production on 28-MAR-2013 07:42:44
Copyright (c) 1991, 2010, Oracle. All rights reserved.
Connecting to
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=hcmdb91)(PORT=1521)))
The listener supports no services
The command completed successfully
[oracle@hcmdb91 ~]$
[oracle@hcmdb91 ~]$ sqlplus SYSADM/SYSADM@HCM
SQL*Plus: Release 11.2.0.2.0 Production on Thu Mar 28 07:44:25 2013
Copyright (c) 1982, 2010, Oracle. All rights reserved.
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in
connect descriptor
My guess is that the database service "HCM" is not up and running but not sure how to make up and running. Even I could not find it listed in the linux services list.
Note: Able to login sqlplus using "sqlplus sys/sys as sysdba" but failing to access database table as "select * from PSRECDEFN;"
thanks
Espii.
Edited by: 995437 on Mar 28, 2013 6:52 AM
Edited by: 995437 on Mar 28, 2013 6:59 AM

Hi Nicolas,
I have no luck and the error still persists.
I have set the "export ORACLE_SID=HCM" from root user and oracle user too.
I guess, I have already loaded database when I ran the "cd /opt/oracle/psft/vm
./oraclevm-template.sh"
The outcome of the above script as similar as below:
Creating
ovm_configure_pre
CreateVirtualEnvironment
/u01/scripts/db-reconfig.sh: line 238: ovm_set_password: command not found
/u01/scripts/db-reconfig.sh: line 239: ovm_configure_network: command not found
INFO:
Starting Oracle database reconfiguration.
Oracle Database Configuration
This will configure on-boot properties of Oracle Database.
The following questions will determine whether the database should be
starting upon system boot, the ports it will use.
Press <Enter> to accept the defaults.
Do you want to relink binaries? (y/n) [n] y
Specify a port that will be used for the database listener [1521]:
Do you want Oracle Database to be started on boot (y/n) [y]:y
Wrote to /etc/sysconfig/oracle11g
Relinking Oracle Binaries...
Oracle Relinking Completed Successfully
Logs: /home/oracle/relink.log
Running orainstRoot.sh and root.sh...
set 2GB tmpfs
Enabling Oracle Database service
Configuration Completed Successfully.
Enter the name of the database SID [TESTDB]:HCM
ORACLE instance started.
Total System Global Area 288104448 bytes
Fixed Size 2225832 bytes
Variable Size 104859992 bytes
Database Buffers 176160768 bytes
Redo Buffers 4857856 bytes
Control file created.
Database altered.
Tablespace altered.
Tablespace altered.
Tablespace altered.
1 row updated.
160 rows updated.
Commit complete.
Kumar - I have found no sqlnet.ora file exist in the $ORACLE_HOME/NETWORK/ADMIN
Edited by: 995437 on Mar 28, 2013 9:15 AM

TNS Listener stopping frequently.

Similar Messages

Maybe you are looking for