Data Guard: net_timeout parameter causing ORA-16163
732974Dec 14 2009 — edited Dec 15 2009Hello all,
I seem to be having a problem setting up our "TEST" data guard environment.
First, this is 10.2.0.4 on AIX 5.3.
My primary and standby databases are set up (with what I thought I had it set before when it was working).
Now, however, after rebuilding the whole environment again, I seem to be having a problem with the net_timeout parameter used in my "log_archive_dest_2" string.
When I start my databases as primary/standby, I am getting errors in my primary alert log as:
Mon Dec 14 10:48:41 2009
LGWR: Error 16163 creating archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=csctestprd2)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=MERCYSTB_XPT)(INSTANCE_NAME=MERCYSTB)(SERVER=dedicated)))'
Mon Dec 14 10:48:41 2009
Errors in file /oracle/product/10.2.0/admin/MERCY/bdump/mercy_lgwr_434430.trc:
ORA-16163: LGWR network server host attach error
LGWR: Failed to archive log 3 thread 1 sequence 771 (16163)
From what I've been able to tell, the ORA-16163 is being thrown by the setting of the log_archive_dest_2 "net_timeout" value.
Even though I have it set to 180, it keeps coming up with a setting of '1' when I show my log_archive_dest_2 parameter.
What could be causing this to reset itself from 180 to 1 automatically.
I checked the DG Broker settings, and they seem correct, however, after stopping and restarting the database (and dgmgr), I'm now getting an error when I show database...
Current status for "MERCY":
Error: ORA-16797: database is not using a server parameter file