redo log size

Wed Dec 24 16:51:37 2008
Thread 1 advanced to log sequence 5323
Current log# 1 seq# 5323 mem# 0: /OMS/oms1/OMS/redo01.log
Wed Dec 24 16:51:52 2008
Thread 1 cannot allocate new log, sequence 5324
Checkpoint not complete
Current log# 1 seq# 5323 mem# 0: /OMS/oms1/OMS/redo01.log
Thread 1 advanced to log sequence 5324
Current log# 2 seq# 5324 mem# 0: /OMS/oms1/OMS/redo02.log
Wed Dec 24 18:45:54 2008
WARNING: inbound connection timed out (ORA-3136)
Wed Dec 24 18:56:01 2008
Thread 1 advanced to log sequence 5325
Current log# 3 seq# 5325 mem# 0: /OMS/oms1/OMS/redo03.log
It has something to do the the size of redo log.

Any one can help on this. thanks.

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.

nothing to do with redo log size

vijiII,

The default settings of sqlnet parameters are fine for most situations. You will have to change it only to handle special scenario's. This might be caused by either a user or application which initiated a connection but did not complete it etc., Unless this happens frequently, you dont have to do anything OR if users start complaining.

Regards,