Home » RDBMS Server » Server Administration » ORA-16038, ORA-00312, ORA-16014 (Oracle 12c (12.1.0.1.0)- Solaris)
ORA-16038, ORA-00312, ORA-16014 [message #668392] Wed, 21 February 2018 00:54 Go to next message
daulat01
Messages: 55
Registered: May 2011
Location: Delhi
Member
Hi Experts,

can anyone please help me on this issue. I have a dataguard environment and its reported on primary.

Errors in file /mnt/cn/oracle/diag/rdbms/kbcn1/kbcn/trace/kbcn_tt00_21417.trc:
ORA-16038: log 1 sequence# 104373 cannot be archived

20-FEB-18 08.32.06.760 PM -08:00
ORA-16038: log 1 sequence# 104376 cannot be archived
ORA-16038: log sequence# cannot be archived
ORA-00312: online log 1 thread 1: '/mnt/cn/oracle/oradata/kbcn/redo01.log'

20-FEB-18 08.32.07.064 PM -08:00
ORA-16014: log 1 sequence# 104376 not archived, no available destinations
ORA-00312: online log 1 thread 1: '/mnt/cn/oracle/oradata/kbcn/redo01.log'

20-FEB-18 08.40.28.567 PM -08:00
WARNING: inbound connection timed out (ORA-3136)

My Actions:

SQL> select * from v$flash_recovery_area_usage;

FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES CON_ID
----------------------- ------------------ ------------------------- --------------- ----------
CONTROL FILE 0 0 0 0
REDO LOG 0 0 0 0
ARCHIVED LOG 0 0 0 0
BACKUP PIECE 0 0 0 0
IMAGE COPY 0 0 0 0
FLASHBACK LOG 0 0 0 0
FOREIGN ARCHIVED LOG 0 0 0 0
AUXILIARY DATAFILE COPY 0 0 0 0


Thanks


Re: ORA-16038, ORA-00312, ORA-16014 [message #668395 is a reply to message #668392] Wed, 21 February 2018 02:11 Go to previous messageGo to next message
Michel Cadot
Messages: 65759
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator

ORA-03136: inbound connection timed out
 *Cause:  Inbound connection was timed out by the server because
          user authentication was not completed within the given time
          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
 *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
          2) Configure SQL*NET with a proper inbound connect timeout value
             if necessary.
Check your network between primary and standby.
Check v$archive_dest_status, v$archive_gap and messages in v$dataguard_status.

Please read and apply How to use [code] tags and make your code easier to read.

Re: ORA-16038, ORA-00312, ORA-16014 [message #668396 is a reply to message #668392] Wed, 21 February 2018 03:07 Go to previous messageGo to next message
John Watson
Messages: 7551
Registered: January 2010
Location: Global Village
Senior Member
select inst_id,status,dest_name from gv$archive_dest;
Re: ORA-16038, ORA-00312, ORA-16014 [message #668526 is a reply to message #668392] Wed, 28 February 2018 01:41 Go to previous messageGo to next message
daulat01
Messages: 55
Registered: May 2011
Location: Delhi
Member
Hi,
I have raised this concern to Oracle support.

I will update the status once I will received any update.

Regards,
Daulat
Re: ORA-16038, ORA-00312, ORA-16014 [message #668527 is a reply to message #668395] Wed, 28 February 2018 01:45 Go to previous message
daulat01
Messages: 55
Registered: May 2011
Location: Delhi
Member
Hi Michel,

Thanks for your support. There was some network issue. Resolved by our Network administrator.
Regards,
Daulat
Previous Topic: Global Temp Table and UNDO Generation
Next Topic: Changing Noninterval to Interval Partitions
Goto Forum:
  


Current Time: Thu Sep 20 00:16:26 CDT 2018