今天生产库一直在报以下错误,查看trace文件后发现是physical standby的LOG_ARCHIVE_DEST_1有问题,可奇怪的是physical standby的LOG_ARCHIVE_DEST_1连的是本机
最后发现是FAL_SERVER、FAL_CLIENT设置有问题,在physical standby找不到fal_client为billdb2的tnsnames,把他改为racdg后正常(在tnsnames.ora中有racdg,指向本机)
生产库报错:
Sun Nov 7 11:28:56 2010
Errors in file /u01/app/admin/billdb/bdump/billdb2_arc3_2215.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
FAL[server, ARC3]: Error 12154 creating remote archivelog file 'billdb2'
FAL[server, ARC3]: FAL archive failed, see trace file.
trace文件信息:
*** 2010-11-07 11:28:56.089
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
'
*** 2010-11-07 11:28:56.090 60639 kcrr.c
Error 12154 received
最后发现是FAL_SERVER、FAL_CLIENT设置有问题,在physical standby找不到fal_client为billdb2的tnsnames,把他改为racdg后正常(在tnsnames.ora中有racdg,指向本机)
生产库报错:
Sun Nov 7 11:28:56 2010
Errors in file /u01/app/admin/billdb/bdump/billdb2_arc3_2215.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
FAL[server, ARC3]: Error 12154 creating remote archivelog file 'billdb2'
FAL[server, ARC3]: FAL archive failed, see trace file.
trace文件信息:
*** 2010-11-07 11:28:56.089
Redo shipping client performing standby login
OCIServerAttach failed -1
.. Detailed OCI error val is 12154 and errmsg is 'ORA-12154: TNS:could not resolve the connect identifier specified
'
*** 2010-11-07 11:28:56.090 60639 kcrr.c
Error 12154 received