Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2004
    Posts
    4

    Exclamation Unanswered: [db2diag.log] "Both paths seem to be bad, try path1.0000 6e58"

    hi! please help me...

    1. disk error
    2005-01-26-16.58.19.102633 start: Disk already marked bad, not inserting to array.

    2. userexit error
    2005-01-26-17.11.09.578828 Instance:db2spb Node:000
    PID:14412(db2cart) Appid:none
    data_protection sqlpgart Probe:490

    User Exit returned error when archiving log file S0028244.LOG from /UDB2/ACLOG2/ for database DBSPB, error code 28


    2005-01-26-17.11.09.582852 Instance:db2spb Node:000
    PID:14412(db2cart) Appid:none
    data_protection sqlpgart Probe:490

    Error received from userexit program.
    DB2 will not call userexit program for this database for 5 minutes.

    2005-01-26-19.06.15.121919 Instance:db2spb Node:000
    PID:37928(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgspr Probe:2022

    Error 1288 when searching message queue for archived logs. Ignore this error.


    2005-01-26-19.06.15.578423 Instance:db2spb Node:000
    PID:37928(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgmar Probe:55

    At least 5 minutes has passed since the last time an error was received when
    archiving a log file. Give it another try on log file S0028245.LOG

    2005-01-26-19.06.15.599413 Instance:db2spb Node:000
    PID:14412(db2cart) Appid:none
    data_protection sqlpgart Probe:490

    User Exit returned error when archiving log file S0028245.LOG from /UDB2/ACLOG2/ for database DBSPB, error code 28

    2005-01-26-19.06.15.602162 Instance:db2spb Node:000
    PID:14412(db2cart) Appid:none
    data_protection sqlpgart Probe:490

    Error received from userexit program.
    DB2 will not call userexit program for this database for 5 minutes.

    2005-01-26-19.06.20.582431 Instance:db2spb Node:000
    PID:37928(db2loggr (DBSPB)) Appid:none
    data_protection sqlpghck Probe:160

    DB2 was unable to confirm log S0028245.LOG was archived. rc 1288


    2005-01-26-19.06.20.582431 Instance:db2spb Node:000
    PID:37928(db2loggr (DBSPB)) Appid:none
    data_protection sqlpghck Probe:160

    DB2 was unable to confirm log S0028245.LOG was archived. rc 1288


    2005-01-26-19.07.23.757493 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgolf Probe:30
    DIA3806C 예기치 않게 파일의 끝(EOF)에 도달했습니다

    ZRC=0xFFFFF609

    2005-01-26-19.07.24.175708 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgilt Probe:552

    DB2 will try to archive log extent 28244 to 28245


    2005-01-26-19.07.27.187453 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgilt Probe:2090

    Error -6653 when renaming old log extent 28244 on path 2.
    Ignore this error, and will try to delete the file.

    2005-01-26-19.07.27.201297 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    oper_system_services sqlodelete Probe:110

    errno: 0000 0005 ....


    2005-01-26-19.07.27.205134 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgolf Probe:30
    DIA3806C 예기치 않게 파일의 끝(EOF)에 도달했습니다

    ZRC=0xFFFFF609

    3. disk error (again)
    2005-01-26-19.07.27.601240 Instance:db2spb Node:000
    PID:37930(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgifl Probe:20
    DIA3702C 디스크 오류가 발생했습니다.

    ZRC=0xFFFFE603




    4. System check and reboot
    5. Recovery

    2005-01-26-20.51.03.777984 Instance:db2spb Node:000
    PID:107972(db2agent (DBSPB)) Appid:AC1E0165.8207.050126114145
    base_sys_utilities sqledint Probe:0 DatabaseBSPB

    Crash Recovery is needed.

    2005-01-26-20.51.05.028904 Instance:db2spb Node:000
    PID:99408(db2agent (SESSDB)) Appid:AC1E0165.81EA.050126114109
    recovery_manager sqlprecm Probe:400 DatabaseESSDB
    DIA3916W 응급 복구의 전방향 단계가 완료되었습니다. 다음 LSN은
    "00066603FAEE"입니다.

    2005-01-26-20.51.06.159865 Instance:db2spb Node:000
    PID:99408(db2agent (SESSDB)) Appid:AC1E0165.81EA.050126114109
    recovery_manager sqlpresr Probe:170 DatabaseESSDB
    DIA3909W 응급 복구(crash recovery)가 완료되었습니다. 다음 LSN은
    "00066603FAEE"입니다.

    2005-01-26-20.51.10.052280 Instance:db2spb Node:000
    PID:107972(db2agent (DBSPB)) Appid:AC1E0165.8207.050126114145
    recovery_manager sqlpresr Probe:1 DatabaseBSPB
    DIA3908W 응급 복구(crash recovery)가 시작되었습니다. Lowtran LSN은
    "0072F59D000C"이고, Minbuff LSN은 "0072F59D000C"입니다.

    2005-01-26-20.51.10.056851 Instance:db2spb Node:000
    PID:107972(db2agent (DBSPB)) Appid:AC1E0165.8207.050126114145
    recovery_manager sqlprecm Probe:125 DatabaseBSPB

    Using parallel recovery with 7 agents 18 QSets 126 queues and 32 chunks


    2005-01-26-20.51.10.067997 Instance:db2spb Node:000
    PID:125250(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgarl Probe:897

    Both paths seem to be bad, try path1.0000 6e56 ..nV


    2005-01-26-20.51.10.102752 Instance:db2spb Node:000
    PID:125250(db2loggr (DBSPB)) Appid:none
    data_protection sqlpgarl Probe:897

    Both paths seem to be bad, try path1.0000 6e56 ..nV


    6. continue display
    Both paths seem to be bad, try path1.0000 6e56 ..nV


    7. System Reboot
    Both paths seem to be bad, try path1.0000 6e58
    Both paths seem to be bad, try path1.0000 6e58
    Both paths seem to be bad, try path1.0000 6e58
    Both paths seem to be bad, try path1.0000 6e58

    What does the last sentence(Both paths seem to be bad, try path1.0000 6e58) mean ?
    and
    How do I work to remove the error(Both paths seem to be bad, try path1.0000 6e58)?


    plz. help me!!!!!!


    thanks


    OS : AIX 4.3.3.11
    DB2 : UDB7.2 EE , FP12

  2. #2
    Join Date
    Aug 2004
    Location
    London, UK
    Posts
    31

    AIX problem

    It's clear that somethings happened to your disk. You'll need to ask an AIX expert.
    jdey@macehill.co.uk
    http://www.macehill.co.uk

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •