This content has been marked as final. Show 13 replies
ORA-01219: database not open: queries allowed on fixed tables/views only
alter database open;
and try again.
Please read my message: sometimes it works.
SQL> select open_mode from v$database;
SQL> select logins from v$instance;
SQL> alter database open;
alter database open
ERROR at line 1:
ORA-01531: a database already open by the instance
can you tnsping? can you post tnsnames.ora? check for traces for more info of the error
Here is more info.
TNS Ping Utility for 32-bit Windows: Version 188.8.131.52.0 - Production on 08-JUN-2
Copyright (c) 1997, 2010, Oracle. All rights reserved.
Used parameter files:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS_LIST= (ADDRESS = (protocol=ipc)(ke
y=IPC_bla)) (ADDRESS = (COMMUNITY = tcp.world) (PROTOCOL = TCP) (Host = bla
) (Port = 1521))) (CONNECT_DATA = (SERVICE_NAME = TST.WORLD))
OK (80 msec)
(ADDRESS = (protocol=ipc)(key=IPC_bla))
(COMMUNITY = tcp.world)
(PROTOCOL = TCP)
(Host = bla.ee.intern)
(Port = 1521)
(SERVICE_NAME = TST.WORLD)
Fri Jun 08 09:04:39 2012
08-JUN-2012 09:04:39 * (CONNECT_DATA=(SERVICE_NAME=TST.WORLD)(CID=(PROGRAM=C:\ORACLE\client112_32\bin\sqlplus.exe)(HOST=LAPTOP)(USER=pven
))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.128.128.16)(PORT=57359)) * establish * TST.WORLD * 0
I just had a succesfull connection and a failed connection, both show up in listener-logging exactly the same, only the timestamp differs.
Looks like my local SQLplus is able to reach the database, which is confirmed by tnsping.
Edited by: pvenpven on Jun 8, 2012 9:08 AM
I read you all posts on this thread. I see you are using Windows OS.
I think this help you : you can try delete listener, and add new listener with other port (create duration if you get this port is using choose other port)
And clear tansnames.ora file content.
Add TST.WORLD description to tnsnames with NETCA.
Mahir M. Quluzade
My client is on Windows, my db is on Sunsolaris. :)
We have more databases on this server, none of them have this problem, just my tst-db.
sometimes i had problems with the host, try to change the "bla.ee.intern" by the IP address and check if the error continues.
I changed the host to the IP-address: the first connection was succesfull, second connection failed.
I have the feeling my connecton is succesfull if I wait for some seconds, if I connect too fast it fails.
check listener.log and emoms.log to get more information about errors, and please post it if you find something. Anyway try to check if you are having any error with your network
can you check after removing "(PRESPAWN_MAX = 10)" set in listener? Do you still face the issue?
I removed "(PRESPAWN_MAX = 10)" (and restarted the listener), after this I was able to login about twenty times before the old errors occured again.
Edited by: pvenpven on Jun 8, 2012 11:25 AM
Is this condition specific to a particular user connection or any any user? Does connection with sys or system also errors out? Wild guess, but any difference in profile set for the user or any setting in sqlnet.ora on the database server?
It occurs for different users in the database, from several different clients we encounter the same problem. There are no errors in listener.log or alert.log.