database.sarang.net
UserID
Passwd
Database
DBMS
MySQL
PostgreSQL
Firebird
Oracle
Informix
ㆍSybase
MS-SQL
DB2
Cache
CUBRID
LDAP
ALTIBASE
Tibero
DB 문서들
스터디
Community
공지사항
자유게시판
구인|구직
DSN 갤러리
도움주신분들
Admin
운영게시판
최근게시물
Sybase Q&A 4400 게시물 읽기
No. 4400
sybase 구동시 에러
작성자
동주(초보관리자)
작성일
2014-09-12 09:24
조회수
5,069

안녕하세요 

회사에서 sybase 디비를 사용하는데

구동시 아래와 같이 에러가 나면서 구동이 되지 안습니다..

무엇이 원인이고 해결은 어떻게 해야할지 알려주시면

감사하겠습니다..  부탁드립니다.ㅠ.ㅠ

00:00000:00001:2014/09/11 19:42:35.47 server  Opening Master Database ...
00:00000:00001:2014/09/11 19:42:35.48 server  Loading SQL Server's default sort
order and character set
00:00000:00001:2014/09/11 19:42:35.48 server  Loaded default Unilib conversion h
andle.
00:00000:00002:2014/09/11 19:42:35.48 kernel  network name tm01, type ether, por
t 6100
00:00000:00001:2014/09/11 19:42:35.48 server  Timestamp in page 620 of text obje
ct 45 is out of sync. Please run DBCC REBUILD_TEXT(45) to fix this.
00:00000:00001:2014/09/11 19:42:35.48 server  Timestamp in page 618 of text obje
ct 45 is out of sync. Please run DBCC REBUILD_TEXT(45) to fix this.
00:00000:00001:2014/09/11 19:42:35.49 server  Recovering database 'master'
00:00000:00001:2014/09/11 19:42:35.73 server  Checking external objects.
00:00000:00001:2014/09/11 19:42:35.74 server  Database 'master' is now online.
00:00000:00001:2014/09/11 19:42:35.74 server  The transaction log in the databas
e 'master' will use I/O size of 2 Kb.
00:00000:00001:2014/09/11 19:42:35.93 server  This installation was created usin
g a 12.0 or later version of buildmaster.
00:00000:00001:2014/09/11 19:42:35.93 server  0 dump conditions detected at boot
 time
00:00000:00001:2014/09/11 19:42:35.93 server  server name is 'SYBASE'
00:00000:00001:2014/09/11 19:42:35.93 server  Activating disk 'elog'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Initializing virtual device 9, '/b
ackup/tmlog_back.log' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Virtual device 9 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.93 server  Activating disk 'sysprocsdev'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Initializing virtual device 1, '/s
ybase/dev/sybprocs.dat' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Virtual device 1 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.93 server  Activating disk 'temp_dev'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Initializing virtual device 5, '/D
B/db_dev1/tempdev1.dat' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Virtual device 5 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.93 server  Activating disk 'tmcenter_dev01'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Initializing virtual device 3, '/D
B/db_dev1/tmcenter_dev01.dat' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Virtual device 3 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.93 server  Activating disk 'tmcenter_dev02'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Initializing virtual device 6, '/D
B/db_dev1/tmcenter_dev02.dat' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.93 kernel  Virtual device 6 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.94 server  Activating disk 'tmcenter_log01'.
00:00000:00001:2014/09/11 19:42:35.94 kernel  Initializing virtual device 4, '/D
B/log_dev1/tmcenter_log01.dat' with dsync 'on'.
00:00000:00001:2014/09/11 19:42:35.94 kernel  Virtual device 4 started using asy
nchronous i/o.
00:00000:00001:2014/09/11 19:42:35.94 server  Activating disk 'tmp_01'.
00:00000:00001:2014/09/11 19:42:35.94 kernel  Initializing virtual device 10, '/
DB/db_dev2/tmp_01.dat' with dsync 'on'.
0:00000:00001:2014/09/11 19:42:35.94 kernel  Virtual device 10 started using as
nchronous i/o.
0:00000:00001:2014/09/11 19:42:35.94 server  Activating disk 'tmp_02'.
0:00000:00001:2014/09/11 19:42:35.94 kernel  Initializing virtual device 11, '/
B/db_dev2/tmp_02.dat' with dsync 'on'.
0:00000:00001:2014/09/11 19:42:35.94 kernel  Virtual device 11 started using as
nchronous i/o.
0:00000:00001:2014/09/11 19:42:35.94 server  Activating disk 'tmp_log'.
0:00000:00001:2014/09/11 19:42:35.94 kernel  Initializing virtual device 12, '/
B/db_dev2/tmp_log.dat' with dsync 'on'.
0:00000:00001:2014/09/11 19:42:35.94 kernel  Virtual device 12 started using as
nchronous i/o.
0:00000:00001:2014/09/11 19:42:35.97 server  Recovering database 'sybsystemdb'.
0:00000:00001:2014/09/11 19:42:36.20 server  Boot Count: 158
0:00000:00001:2014/09/11 19:42:36.21 server  Checking external objects.
0:00000:00001:2014/09/11 19:42:36.21 server  The transaction log in the databas
 'sybsystemdb' will use I/O size of 2 Kb.
0:00000:00001:2014/09/11 19:42:36.42 server  Recovering database 'model'.
0:00000:00001:2014/09/11 19:42:36.64 server  Checking external objects.
0:00000:00001:2014/09/11 19:42:36.64 server  The transaction log in the databas
 'model' will use I/O size of 2 Kb.
0:00000:00001:2014/09/11 19:42:36.85 server  Database 'model' is now online.
0:00000:00001:2014/09/11 19:42:36.85 server  Resident Node id: fca2cb834a4f
0:00000:00001:2014/09/11 19:42:36.85 server  Transaction coordinator initialize
.
0:00000:00001:2014/09/11 19:42:36.85 server  Clearing temp db
0:00000:00000:2014/09/11 19:42:41.15 kernel  sddone: write error on virtual dis
 5 block 46594:
0:00000:00000:2014/09/11 19:42:41.15 kernel  sddone: I/O error
0:00000:00001:2014/09/11 19:42:41.15 server  Error: 823, Severity: 24, State: 2
0:00000:00001:2014/09/11 19:42:41.15 server  I/O error detected during wait for
BUF pointer = '0x19d0110e0', MASS pointer = '0x19d0110e0', (Buf#: '0'), page pt
 = '0x19a985000', dbid = '2', Mass virtpage = '83932674', Buffer page = '0', Ma
s status = '0x80908', Buffer status = '0x1', size = '2048', cache (id: 0) = 'de
ault data cache', Pinning Xdes = '0x0', spid = '0'.
00:00000:00001:2014/09/11 19:42:41.15 server  SQL Server's default sort order is
:
00:00000:00001:2014/09/11 19:42:41.15 server    'bin_iso_1' (ID = 50)
00:00000:00001:2014/09/11 19:42:41.15 server  on top of default character set:
00:00000:00001:2014/09/11 19:42:41.15 server    'iso_1' (ID = 1).
01:00000:00000:2014/09/11 19:42:41.28 kernel  engine 1, os pid 30332  online
01:00000:00000:2014/09/11 19:42:41.28 server  HA Config: High Availability Basis
 Services loaded: version 'Adaptive Server Enterprise/12.0.0.7/P/EBF 11094 ESD 1
/RS6000/AIX 4.3.2/2008/64bit/FBO/Wed May  7 06:33:51 2003'.
02:00000:00000:2014/09/11 19:42:41.42 kernel  engine 2, os pid 32914  online
02:00000:00000:2014/09/11 19:42:41.42 server  HA Config: High Availability Basis
 Services loaded: version 'Adaptive Server Enterprise/12.0.0.7/P/EBF 11094 ESD 1
/RS6000/AIX 4.3.2/2008/64bit/FBO/Wed May  7 06:33:51 2003'.
00:00000:00000:2014/09/11 19:42:41.43 kernel  ncheck: Network 60032f80 online
00:00000:00001:2014/09/11 19:42:41.46 kernel  nconnect: connect, Connection refu
sed
00:00000:00001:2014/09/11 19:42:41.46 server  WARNING: Pss found with open sdes.
 pspid 1, psuid 0, pcurdb 1, system table entry 0, sdesp 0x00000001764e3a68, obj
id 1
02:00000:00000:2014/09/11 19:42:41.42 kernel  engine 2, os pid 32914  online
02:00000:00000:2014/09/11 19:42:41.42 server  HA Config: High Availability Basis
 Services loaded: version 'Adaptive Server Enterprise/12.0.0.7/P/EBF 11094 ESD 1
/RS6000/AIX 4.3.2/2008/64bit/FBO/Wed May  7 06:33:51 2003'.
00:00000:00000:2014/09/11 19:42:41.43 kernel  ncheck: Network 60032f80 online
00:00000:00001:2014/09/11 19:42:41.46 kernel  nconnect: connect, Connection refu
sed
00:00000:00001:2014/09/11 19:42:41.46 server  WARNING: Pss found with open sdes.
 pspid 1, psuid 0, pcurdb 1, system table entry 0, sdesp 0x00000001764e3a68, obj
id 1
00:00000:00001:2014/09/11 19:42:41.46 server  Error: 6103, Severity: 17, State:
1
00:00000:00001:2014/09/11 19:42:41.46 server  Unable to do cleanup for the kille
d process; received Msg 823.
이 글에 대한 댓글이 총 1건 있습니다.

1. recycle시 823 에러가 tempdb (dbid=2) 에서 발생했네요.
823 에러는 보통 Sybase 액세스 권한이 없는 경우 발생하는 경우가 많습니다. 
tempdb 위치는 로그 상으로 보면 /DB/db_dev1/tempdev1.dat 네요.
해당 device에 rw 권한이 있는지, 해당 directory까지 x 권한이 있는지 확인해보셔야 할 것 같습니다.
sybase 계정으로 해당 디렉토리까지 이동해서 임의 파일을 만들어 보면 되겠죠.
(예: cd /DB/db_dev1;touch tmp.txt)

 

2. 권한 문제가 없다면, device의 특정 블럭이 논리적으로 문제가 생긴 경우가 있을 수도 있습니다.
다행히 tempdb 영역은 DB 재기동시 새로 device를 format 하기 때문에, 파일만 존재하면 됩니다.
단 작업은 SYBASE engine이 내려가 있는 상태에서 해주셔야 합니다.
(showserver 결과가 없는 상태)
cd /DB/db_dev1
mv tempdev1.dat tempdev1.dat.old      #mv 대신 삭제도 가능합니다만...
touch tempdev1.dat
cd $SYBASE/ASE-*/install
startserver -f RUN_SYBASE

 

3. 그래도 823 에러가 나온다면....
master device에 있는 tempdb 영역이 문제가 된 것일 수도 있습니다.
이경우 SYBASE 유지보수 엔지니어를 콜하는게 좋을 듯 싶습니다.
(작업시 master DB 가 깨질 수 도 있기 때문에....)
굳이 직접하시겠다면....
DB 서버가 내려간 상태에서 master.dat 파일 하나 copy 해두고...
$SYBASE/ASE-*/SYBASE.cfg 파일에서 allow updates to system tables = 1 바꾸고,
서버 기동시 startserver -f RUN_SYBASE -m 으로 single user mode 로 올리고,
DB 접속 후 update sysusages set segmap=0 where dbid=2 and lstart=0
SYBASE 재기동시 -m 없이 재기동 후 문제 clear 되었는지 확인.

 

4. 3번 으로 문제가 클리어 안된다면. 3.번에서 백업해뒀던, master.dat 로 원복하고,
싱글유저모드(-m) 으로 올리고,
bcp 로 sysdatabases, sysdevices, sysusages, syslogins, sysloginroles 받아놓고,
새로 mater 빌드후에 sysdatabases, sysdevices, sysusages 에서 dbid=2인것들 삭제 편집하고,
새로 만든 mater에 부어 놓고 tempdb에 tempdev1.dat 를 추가하는 방법도 생각해볼 만함.

 

5. 6103 에러는 아마도 tempdb 가 문제가 되서 발생된 에러로 추측... 패스 ....
재기동시 tempdb 문제가 clear 되었다면, 안생길 듯...

 

잘 복구 되시길 바랍니다.   콜베이스로 처리시 50~100만원쯤 하니 복구가 잘되었다면 돈 번거라고 하시길....호호호

소이화님이 2014-09-12 11:48에 작성한 댓글입니다.
이 댓글은 2014-09-12 11:57에 마지막으로 수정되었습니다. Edit Ｘ
[Top]
No.
제목
작성자
작성일
조회
4403Interactive Sql 에서 한글 깨짐 여쭤봅니다. [12]
JAAN
2014-11-11
9450
4402sybase odbc 관련되어 질문 드립니다. [3]
초보개발자
2014-10-15
6520
4401sybase 구동에러 [1]
동주
2014-09-12
4941
4400sybase 구동시 에러 [1]
동주
2014-09-12
5069
4399전자정부프레임워크 + Sybase 쓰는데 JDBC이용해서 DB 접속이 안됩니다 ㅠㅠ [1]
최세원
2014-09-11
7067
4398반복 쿼리 [1]
김한상
2014-09-01
5312
4396서버 복구시 Data(dat)파일 과 master(dat) 을 어찌 올려야하나요? [2]
천영수
2014-07-29
3803
Valid XHTML 1.0!
All about the DATABASE... Copyleft 1999-2023 DSN, All rights reserved.
작업시간: 0.051초, 이곳 서비스는 PostgreSQL v16.1로 자료를 관리합니다