DBlink 생성하기

----------------------------------------------------------------
Link 상대 Server 정보
IP Address : 156.147.95.42
SID NAME : ERP_DEV1
Port : 1534
Oracle USER ID : intf / intf

Link 요청 Server
IP Address : 156.147.95.21(MIS Server)
SID NAME : PRODDB(1605),TESTDB(1523)


*현재 ERP가 개발중이므로 IP Address는 자주 바뀔것 같고요
다른 자세한 정보는 강동우D(4234)로 연락 하시면 됩니다.
---------------------------------------------------------------

1. su - oraprod 접속

tnsnames.ora 에 아래를 등록

ERP_DEV1=
(DESCRIPTION=
(ADDRESS= (PROTOCOL=tcp)(HOST=156.147.95.42)(PORT=1534))
(CONNECT_DATA = (SID=ERP_DEV1))
)

2. system user 로 들어가서.....

create public database link dl_erpdev
connect to intf identified by intf
using 'ERP_DEV1';

로 등록.

3. 확인.
sqlplus intf/intf@ERP_DEV1
or
그냥 들어가서...
select * from user_tables@dl_erpdev;



select * from dba_db_links;


===================================================================

우리 쪽 서버를 예로 들면 pc0unf1 에서 CINSA DB로 붙고 싶다 할땐
pc0unf1 쪽에 tnsnames.ora 파일에 CINSA tns를 추가하고
tnsping을 날린다. seos가 설치되어 있으면 핑이 안 날아간다.
담당자와 협의 후 우리 pc0unf1 IP allow 할 것.

tnsping 확인하고
dblink 생성한다.

생성전에 먼저 public인지 아닌지 확인하고

create public database link dl_cinsa
connect to intf identified by XXXXXX
using 'CINSA';


dbqhwk는 패스워드를 그대로 입력
using 뒤에는 사용할 tns 입력

생성되면 성공적으로 생성되었다는 메세지가 뜸


* 테스트
sqlplus intf/XXXXXX@CINSA
접속 후 select 문 하나 날려본다.

read funix message on syslog

Subject: read funix message on syslog
Franklin Merida

May 27, 2003 23:29:14 GMT
Hi All,

I'm having repeatedly this message on syslog
syslogd: read funix: Resource temporarily unavailable
And the syslog daemon was down. Has anyone face this before.

Thank you and best regards,

Franklin
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click here

=====================Answer========================

Hi,
This error is usually caused by having multiple syslogd daemons running;
$ ps -ef | grep syslog*
When multiple processes are running, confusion occurs as to which daemon needs to be writing
to the syslog file and the error occurs. To resolve this issue, stop the syslogd daemons running and restart the one daemon necessary to write output to the syslog file. Follow these steps:

$ /sbin/init.d/syslogd stop #kill all syslogd
$ ps -ef | grep syslog* #Verify no daemons running.
$ /sbin/init.d/syslogd start #Restart syslogd
$ ps -ef | grep syslog* #Verify only one syslogd running.

Then monitor the /var/adm/syslog/syslog.log file for these errors again. This should resolve the issue. Hopes this helps.

rgds,
janerik