Topic: DB hangup
There was the strange piece.
At DB start there was an error:
After that the DB was launched, all norms.
After time there was an error:
[spoiler] Fatal NI connect error 12514, connecting to:
(DESCRIPTION = (ADDRESS = (PROTOCOL=TCP) (HOST=10.0.0.21) (PORT=1521)) (CONNECT_DATA = (SERVER=DEDICATED) (SERVICE_NAME=test) (CID = (PROGRAM=oracle) (HOST=dboracle.dom) (USER=o
TNS for Linux: Version 22.214.171.124.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 126.96.36.199.0 - Production
Time: 07-AUG-2018 4:45:24 AM
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0 [/spoiler]
In result of the given error possibility to be connected to a DB of everything, except sysdba disappeared. As the DB hung up at any reversal to it, for example at show parameter name.
Serviceability of a DB recovered correction pfile, namely repeating parameters of type: "*." And "sid.", different values had the majority of these parameters. For an example:
[spoiler] sid.log_archive_dest_1 ="
*.log_archive_dest_1 ='location=USE_DB_RECOVERY_FILE_DEST ', ' valid_for = (ALL_LOGFILES, ALL_ROLES) ' [/spoiler]
Question: what was from a DB and where to dig?