Database Connection Error in SQL Developer status: Failure

Error: Status: Failure  -Test failed: IO Error: Got minus one from a read call

The sqlnet.ora file is the profile configuration file. It resides on the client machines and the database server. Profiles are stored and implemented using this file. The database server can be configured with access control parameters in the sqlnet.ora file. These parameters specify whether clients are allowed or denied access based on the protocol.

The sqlnet.ora file enables you to do the following:

·         Specify the client domain to append to unqualified names

·         Prioritize naming methods

·         Enable logging and tracing features

·         Route connections through specific processes

·         Configure parameters for external naming

·         Configure Oracle Advanced Security

·         Use protocol-specific parameters to restrict access to the database

By default, the sqlnet.ora file is located in the ORACLE_HOME/network/admin directory. The sqlnet.ora file can also be stored in the directory specified by the TNS_ADMINenvironment variable.

Restore Control Files using backup tracefile

Restore Controlfile

When you lost control file and unable to start DB as shown below.

SQL> shutdown
ORA-01507: database not mounted

ORACLE instance shut down.
SQL> exit


[oravis@test dbs]$ rman target /
Recovery Manager: Release 12.1.0.2.0 - Production on Wed Sep 12 09:57:19 2018
Copyright (c) 1982, 2014, Oracle and/or its affiliates.  All rights reserved.
connected to target database: VIS (not mounted)

RMAN> startup nomount

RMAN> restore controlfile from autobackup;

Starting restore at 12-SEP-18

using channel ORA_DISK_1

recovery area destination: /u03/oravis/VIS/recovery_area/VIS

database name (or database unique name) used for search: VIS

channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area

AUTOBACKUP search with format "%F" not attempted because DBID was not set

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of restore command at 09/12/2018 09:59:06

RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece

Try to start Database with Pfile

SQL> startup pfile=/u03/oravis/VIS/12.1.0/dbs/initVIS.ora

ORA-32006: SEC_CASE_SENSITIVE_LOGON initialization parameter has been deprecated

ORACLE instance started.

Total System Global Area 2147483648 bytes

Fixed Size                  3712904 bytes

Variable Size             905971832 bytes

Database Buffers         1224736768 bytes

Redo Buffers               13062144 bytes

ORA-00205: error in identifying control file, check alert log for more info

SQL> exit

Disconnected

[oravis@test vis]$ pwd

/u03/oravis/VIS/recovery_area/vis

[oravis@test vis]$ ls

controlfile.bkp  createcontrol.sql

[oravis@test vis]$ !sq

sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Wed Sep 12 10:48:27 2018

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> @/u03/oravis/VIS/recovery_area/vis/createcontrol.sql

ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance

ORACLE instance started.

Total System Global Area 2147483648 bytes

Fixed Size                  3712904 bytes

Variable Size             905971832 bytes

Database Buffers         1224736768 bytes

Redo Buffers               13062144 bytes

Control file created.

PL/SQL procedure successfully completed.

PL/SQL procedure successfully completed.

Media recovery complete.

Database altered.

Tablespace altered.

Tablespace altered.

Tablespace altered.

SQL> select name from v$controlfile;

NAME

--------------------------------------------------------------------------------

/u03/oravis/VIS/data/cntrl01.dbf

/u03/oravis/VIS/data/cntrl02.dbf

/u03/oravis/VIS/data/cntrl03.dbf

SQL> select status from v$instance;

STATUS

------------

OPEN