DB cannot be opened

[kube]

Hello,
I've got a problem with oracle11, I can't resolve - database can be mounted - but cannot be opened.
All trials to resolve the problem where not useful till now.

Thanks for ideas helping me!

[gandolf989]

You can start by posting the last 200 lines of your alert log. In sqlplus "show parameter diag", go to that directory then cd into the diag/rdbms///trace directory and do a tail -100 alert*. Post that and someone can help you. It would also help to post any error message that you are getting. The above might or might not be in upper case.

[viren12]

what is the error message when you try to open database, please post the last 50 lines of ur alert log file

[gandolf989]

what is the error message when you try to open database, please post the last 50 lines of ur alert log file

It has been 5 weeks sine my reply went unanswered. Could it be that the original poster either already solved his issue or just gave up?

[kube]

I'm really sorry - I had to do a lot of things ...

SQL-developer error message: ORA-12514 TNS listener does not currently know of
service requested in connect descriptor

SQLPLUS - startup mount is successfull - database mounted
alter database open; is not successfull
communication is interrupted.

Thank you for your help!

[kube]

Perhaps you need the following informations:

My tnsnames.ora:
LISTENER_ORCL =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))


ORCL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
)
(CONNECT_DATA =
(SID = ORCL)
(SERVER = DEDICATED)
(SERVICE_NAME = ORCL)
)
)

ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ORCL)
)
)

EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_ORCL))
)
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
)
)
listener.ora:

SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = CLRExtProc)
(ORACLE_HOME = E:\app\Claudia\product\11.2.0\dbhome_1)
(PROGRAM = extproc)
(ENVS = "EXTPROC_DLLS=ONLY:E:\app\Claudia\product\11.2.0\dbhome_1\bin\oraclr11.dll")
)
)

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
)
)

ADR_BASE_LISTENER = E:\app\Claudia

[PAVB]

If the database does not open listener is irrelevant, don't you think so?

Where are the last 50 lines of you alert log people has being begging you to post?

[kube]

If the database does not open listener is irrelevant, don't you think so?

Where are the last 50 lines of you alert log people has being begging you to post?

I'm sorry - is that the right tail
of file?
Fri Nov 29 19:42:08 2013
ARC2 started with pid=22, OS id=2992
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
sksasmowrt WriteConsole error 6
Fri Nov 29 19:42:08 2013
ARC3 started with pid=23, OS id=2408
ARC2: Archival started
ARC2: Becoming the heartbeat ARCH
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Fri Nov 29 19:42:10 2013
Errors in file e:\app\claudia\diag\rdbms\orcl\orcl\trace\orcl_ora_700.trc:
ORA-19815: WARNUNG: db_recovery_file_dest_size von 4039114752 Byte werden benutzt, 100.00%, 0 verbleibende Byte sind noch verfugbar.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Errors in file e:\app\claudia\diag\rdbms\orcl\orcl\trace\orcl_ora_700.trc:
ORA-19809: Grenzwert fur Recovery-Dateien uberschritten
ORA-19804: 43587584 Byte Datentragerspeicher konnen nicht aus Grenzwert 4039114752 zuruckgefordert werden
ARCH: Error 19809 Creating archive log file to 'E:\APP\CLAUDIA\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_11_29\O1_MF_1_335_%U_.ARC'
Errors in file e:\app\claudia\diag\rdbms\orcl\orcl\trace\orcl_ora_700.trc:
ORA-16038: Log 2 Sequenz-Nr. 335 kann nicht archiviert werden
ORA-19809: Grenzwert fur Recovery-Dateien uberschritten
ORA-00312: Online-Log 2, Thread 1: 'E:\APP\CLAUDIA\ORADATA\ORCL\REDO02.LOG'
USER (ospid: 700): terminating the instance due to error 16038
Errors in file e:\app\claudia\diag\rdbms\orcl\orcl\trace\orcl_arc1_2888.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 4039114752 bytes is 100.00% used, and has 0 remaining bytes available.
************************************************************************
You have following choices to free up space from recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
Instance terminated by USER, pid = 700

[PAVB]

Errors in file e:\app\claudia\diag\rdbms\orcl\orcl\trace\orcl_ora_700.trc:
ORA-19815: WARNUNG: db_recovery_file_dest_size von 4039114752 Byte werden benutzt, 100.00%, 0 verbleibende Byte sind noch verfugbar.

USER (ospid: 700): terminating the instance due to error 16038

either resize/add space to db_recovery_file_dest or delete expired archive log files.

[gandolf989]

either resize/add space to db_recovery_file_dest or delete expired archive log files.

... und fertig!