物理DG的FAL_CLIENT設定錯誤引起的主庫報錯

jasonwang328發表於2010-11-09
client
今天生產庫一直在報以下錯誤，檢視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 logging on to the standby
Error 12154 connecting to destination LOG_ARCHIVE_DEST_1 standby host 'billdb2'
kcrrwupirfs KCRROCIS Handle 0x0x7fbfffcbe0 has NULL OCI servicehandle - Returning success
Error 12154 attaching to destination LOG_ARCHIVE_DEST_1 standby host 'billdb2'
ORA-12154: TNS:could not resolve the connect identifier specified
*** 2010-11-07 11:28:56.090 58901 kcrr.c
kcrrfail: dest:1 err:12154 force:0 blast:1
kcrrwupirfs KCRROCIS Handle 0x0x7fbfffcbe0 has NULL OCI servicehandle - Returning success
kcrrwkx: unknown error:12154
ORA-16055: FAL request rejected
ARCH: Connecting to console port...
ARCH: Connecting to console port...
kcrrwkx: nothing to do (end)


physical standby的資訊:
log_archive_dest_1 string LOCATION=/u02/archive/billdb/
VALID_FOR=(ONLINE_LOGFILES,ALL
_ROLES) DB_UNIQUE_NAME=racdg

fal_client string billdb2
fal_server string rac [@more@]物理DG的FAL_CLIENT設定錯誤引起的主庫報錯.

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/23250928/viewspace-1041196/，如需轉載，請註明出處，否則將追究法律責任。

相關文章