728x90

/tmp/installFixPack.log.1503312


Backing up installed components.


Back up the file "/work/IBM/db2/V9.7/lib32/C/icc/ReadMe.txt" failed since it

does not exist.


Some error occurred while move file,

"/work/IBM/db2/V9.7/lib32/C/icc/ReadMe.txt", to directory,

"/work/IBM/db2/V9.7/.backup/lib32/C/icc".


ERROR: Some error occurred while moving file(s) during backup or restore to

directory, "/work/IBM/db2/V9.7/.backup". The return code is "4294967295".


Back up the file "/work/IBM/db2/V9.7/.backup/lib32/C/icc/ReadMe.txt" failed

since it does not exist.


Some error occurred while move file,

"/work/IBM/db2/V9.7/.backup/lib32/C/icc/ReadMe.txt", to directory,

"/work/IBM/db2/V9.7/lib32/C/icc".


ERROR: Some error occurred while moving file(s) during backup or restore to

directory, "/work/IBM/db2/V9.7/.backup". The return code is "4294967295".


ERROR: Some error occurred while moving file(s) during backup or restore to

directory, "/work/IBM/db2/V9.7/.backup". The return code is "4294967295".


The specified file, "/work/IBM/db2/V9.7/.backup/.metadata/BASE_CLIENT_R/files",

was not found.


Updating DB2 file sets :.......Failure



 ./installFixPack -f db2lib -f nobackup


http://www-01.ibm.com/support/docview.wss?uid=swg1IC77614

http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.admin.cmd.doc/doc/r0023700.html

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

DB2 異常終了時の対処方法と、原因調査に必要な最低限の資料収集方法  (0) 2012.07.30
FAQ of db2fmp messages in the db2diag.log  (0) 2012.07.21
Error [IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed trying to connect using unixODBC driver manager  (0) 2012.05.06
System-maintenance MQT created based on nicknames takes a long time to referesh  (0) 2012.04.26
SQL 복제 구성에서 캡쳐 프로세스 오류  (0) 2012.04.06
728x90

Question

On DB2 UDB Version 8 FixPak 11 or later, after following the steps to set up the unixODBC driver manager as stated in the documentation section "Setting up the unixODBC Driver Manager", you receive the following error when you test the connection:

$ isql -v testdb username mypassword 
[IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on 
SQL_HANDLE_DBC failed 
[ISQL]ERROR: Could not SQLConnect

Cause

Documentation incorrectly states to use

Answer

The following step in the documentation is NOT necessary for DB2 UDB Version 8 FixPak 11 or above.

For AIX only: Extract the shared library from the ODBC driver for DB2 to yield
shr.o on 32-bit platforms and shr_64.o on 64-bit platforms: 

  • For 32-bit:
cd /u/db2inst1/sqllib/lib
ar -x libdb2.a 
  • For 64-bit:
cd /u/db2inst1/sqllib/lib
ar -x -X 64 libdb2o.a

The library db2o.o is already bundled with DB2 UDB. You just need to edit your odbc.ini file to use the correct library.

Example:

[TESTDB] 

Description=TEST database 
Driver=/home/username/sqllib/lib/db2o.o



728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

FAQ of db2fmp messages in the db2diag.log  (0) 2012.07.21
db2 9.7 FixPack6 설치 오류 (AIX 5.3)  (0) 2012.07.04
System-maintenance MQT created based on nicknames takes a long time to referesh  (0) 2012.04.26
SQL 복제 구성에서 캡쳐 프로세스 오류  (0) 2012.04.06
no resources to create process or thread 오류  (0) 2012.01.05
728x90


Question

You configured system-maintained MQT based on nicknames, when trying to retrieve latest data from remote data source, you found the elapsed time was very long. Why does it take so long when refreshing system-maintained MQT which is created on nicknames?

Cause

System-maintained MQT which is created on nicknames uses full refreshment.

Answer

From refreshing scale, there are 2 ways for system-maintained MQT. one is full refreshment, the other is incremental refreshment.

1) MQT defined with REFRESH IMMEDIATE option only uses incremental refreshment. REFRESH TABLE command actually doesn't do any operation on MQT. 
2) MQT defined with REFRESH DEFERRED option normally uses full refreshment, but not always, there is an exception. If you defined staging table for MQT, incremental refreshment will be used.

Only REFRESH DEFERRED MQT can be created on nickname, but staging table doesn't support nickname, that's why this kind of MQT uses full refreshment. If you want to use incremental refreshment, cache table is a choice.


닉네임에 대해서는 MQT(materialized query table)작성은 가능하지만 MQT에 대한스테이징 테이블(변경된 데이터만 저장한 테이블)은 작성할 수 없음. 대안인 캐시 테이블도 테이블 복제나 매한가지임, Capture and Apply. OTL


https://www-304.ibm.com/support/docview.wss?uid=swg21514881

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.iis.fed.tuning.doc/topics/iiyvfed_tuning_cachetbls.html

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

db2 9.7 FixPack6 설치 오류 (AIX 5.3)  (0) 2012.07.04
Error [IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed trying to connect using unixODBC driver manager  (0) 2012.05.06
SQL 복제 구성에서 캡쳐 프로세스 오류  (0) 2012.04.06
no resources to create process or thread 오류  (0) 2012.01.05
db2icrt/db2idrop hangs when executing db2isrv  (0) 2011.12.28
728x90

2012-04-06-00.30.38.007919+540 I28096582A537      LEVEL: Error

PID     : 9699554              TID  : 64097       PROC : db2sysc 0

INSTANCE: inst01               NODE : 000         DB   : ?????

APPHDL  : 0-13196              APPID: *LOCAL.inst01.120405153039

AUTHID  : INST01

EDUID   : 64097                EDUNAME: db2agent (?????) 0

FUNCTION: DB2 UDB, data protection services, sqlpALR_ReadPagesDisk, probe:1170

MESSAGE : Received error

DATA #1 : Hexdump, 4 bytes

0x0700000258FEACA8 : 0000 0004                                  ....


2012-04-06-00.30.38.008149+540 I28097120A165      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_ALRCB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.008894+540 I28097286A164      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_LFPB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.010873+540 I28097451A164      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_LFPB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.012019+540 I28097616A164      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_DBCB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.012258+540 I28097781A164      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_LECB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.012410+540 I28097946A463      LEVEL: Error

PID     : 9699554              TID  : 64097       PROC : db2sysc 0

INSTANCE: inst01               NODE : 000         DB   : ?????

APPHDL  : 0-13196              APPID: *LOCAL.inst01.120405153039

AUTHID  : INST01

EDUID   : 64097                EDUNAME: db2agent (?????) 0

FUNCTION: DB2 UDB, data protection services, sqlpALR_ReadPagesDisk, probe:1170

MESSAGE : Need to examine log S0002529.LOG rc 4


2012-04-06-00.30.38.012597+540 I28098410A165      LEVEL: Error

PID:9699554 TID:64097 NODE:000 Title: SQLP_ALRCB

Dump File: /?????/db2dump/9699554.64097.000.dump.bin


2012-04-06-00.30.38.012753+540 I28098576A569      LEVEL: Error

PID     : 9699554              TID  : 64097       PROC : db2sysc 0

INSTANCE: inst01               NODE : 000         DB   : ?????

APPHDL  : 0-13196              APPID: *LOCAL.inst01.120405153039

AUTHID  : INST01

EDUID   : 64097                EDUNAME: db2agent (?????) 0

FUNCTION: DB2 UDB, data protection services, sqlp_AsyncLogReadAPI, probe:210

DATA #1 : String, 127 bytes

Error: sqlcode -2650, rc 4, hflag2LsnReuse 0

action 1, startLSN 0000003946048010, endLSN 0000003985CC9B81, logBufferSize 262144



Capture fails with ASN0005E/SQL2656N messages

http://www-01.ibm.com/support/docview.wss?uid=swg21269863


Manage DB2 log files in an SQL replication environment

http://www.ibm.com/developerworks/data/library/techarticle/dm-0701casey/


Understanding APAR LI 70320 - SQL2650 RC=5

http://www-01.ibm.com/support/docview.wss?uid=swg21173900


Can Capture be sent backwards to re-process log records?

http://www-01.ibm.com/support/docview.wss?uid=swg21233858

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

Error [IM005][unixODBC][Driver Manager]Driver's SQLAllocHandle on SQL_HANDLE_DBC failed trying to connect using unixODBC driver manager  (0) 2012.05.06
System-maintenance MQT created based on nicknames takes a long time to referesh  (0) 2012.04.26
no resources to create process or thread 오류  (0) 2012.01.05
db2icrt/db2idrop hangs when executing db2isrv  (0) 2011.12.28
Why is db2top screen output not being shown in colors?  (0) 2011.11.17
728x90
물리 메모리 혹은 ipc limit 와 관련된 이슈.
AIX의 경우 커널 매개변수 설정이 필요없지만, HP-UX, Solaris, linux는 권장 매개변수 값을 참조하여 설정하는 것이 좋겠다.


IZ47611: DB2 INSTANCE CRASH AFTER SEVERE OS RESOURCE ALLOCATION FAILURE (FAILURE TO FORK OR ALLOCATE IPC RESOURCES)

https://www-304.ibm.com/support/docview.wss?uid=swg1IZ47611


DB2: Severe system error occurs with SQLO_NORES, DIA8336C and DIA8532C messages in db2diag.log

http://www-01.ibm.com/support/docview.wss?uid=swg21406633


Redirect restore failed with SQL2043N on DB2 9.X

http://www-01.ibm.com/support/docview.wss?uid=swg21425464

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

System-maintenance MQT created based on nicknames takes a long time to referesh  (0) 2012.04.26
SQL 복제 구성에서 캡쳐 프로세스 오류  (0) 2012.04.06
db2icrt/db2idrop hangs when executing db2isrv  (0) 2011.12.28
Why is db2top screen output not being shown in colors?  (0) 2011.11.17
DB2START Fails with SQL10007N Message "-1390" could not be retrieved.  (0) 2011.10.18
728x90


Problem(Abstract)

When using IBM DB2 for Linux, UNIX and Windows, running db2icrt/db2idrop against an DB2 instance name results in db2icrt/db2idrop process hangs when it is executing db2isrv in child process.

Symptom

db2icrt/db2idrop hangs when executing db2isrv

Cause

DB2 port entries in /etc/services file are missing or in wrong order etc.

Example 1:
DB2_db2instance1 entry is missing:


    DB2_db2instance1_1 60045/tcp 
    DB2_db2instance1_2 60046/tcp 
    DB2_db2instance1_END 60047/tcp

Example 2:
DB2_instance2 related port entries are in wrong order:
    DB2_db2instance2_1 60001/tcp 
    DB2_db2instance2_2 60002/tcp 
    DB2_db2instance2_END 60003/tcp 
    DB2_db2instance2 5914/tcp

Resolving the problem

1. Remove DB2 port entries related to the instance name in /etc/services file

2. Run db2icrt/db2idrop command again.



http://www-01.ibm.com/support/docview.wss?uid=swg21441874

http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.qb.server.doc/doc/t0008487.html

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

SQL 복제 구성에서 캡쳐 프로세스 오류  (0) 2012.04.06
no resources to create process or thread 오류  (0) 2012.01.05
Why is db2top screen output not being shown in colors?  (0) 2011.11.17
DB2START Fails with SQL10007N Message "-1390" could not be retrieved.  (0) 2011.10.18
Install fails with "FILE keyword is not valid" error  (0) 2011.10.13
728x90

Question

Why is db2top screen output not being shown in colors?

Cause

db2top is a monitoring tool included in DB2 for LUW on AIX, Linux, and Solaris platforms. Sometimes this utility is not shown in colors, Even though the monochromatic view of db2top is very useful, db2top can use colors when using the interactive screen mode to highlight some outputs and that can be more useful and attractive to some users.

Answer

The most common reasons to see db2top without colors are the following:

Your term emulator and/or your TERM environment setting cannot manage colors. In this case using xterm or dtterm at your TERM environment setting and use a term emulator capable to emulate either xterm or dtterm would be enough to show db2top in colors.

Your db2top configuration is not configured to show the output in colors, In order to check if db2top is configured to manage colors just execute the utility "db2top -d <database>" (where database is any database active on your instance), and once you are seeing the db2top main screen, just press "w" key, this writes the db2top configuration file and shows its current values:


Ensure the parameter "colors" is set to "ON". If it is configured to "OFF" you can edit directly the configuration file indicated by the first line of the above screen ("/home/db2inst1/.db2toprc" in this case) in order to set this parameter to "ON".



http://www-01.ibm.com/support/docview.wss?uid=swg21458782

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

no resources to create process or thread 오류  (0) 2012.01.05
db2icrt/db2idrop hangs when executing db2isrv  (0) 2011.12.28
DB2START Fails with SQL10007N Message "-1390" could not be retrieved.  (0) 2011.10.18
Install fails with "FILE keyword is not valid" error  (0) 2011.10.13
IY73035: "FORCE APPLICATION" ON GATEWAY CAN CAUSE GATEWAY INSTANCE CRASH IF MONITOR IS TURNED ON GATEWAY  (0) 2011.10.11
728x90

Problem(Abstract)

DB2START can fail, reporting SQL1390C, for various reasons.

Symptom

The db2start command will fail with the following error message:

SQL10007N Message "-1390" could not be retrieved.  Reason code: "3"



Cause

The problem can be due to several reasons. The common culprits are:

  1. Incorrect DB2INSTANCE environment variable setting.
  2. The db2profile has not be sourced properly.
  3. IZ36615
  4. Inconsistencies in /etc/group or /etc/passwd

Resolving the problem

First, it is a good idea to run db2iupdt as the root user if you're receiving this error message. Ifdb2start continues to fail you should check the following:

  1. The "DB2INSTANCE" environment variable should be set to the instance name of the instance you wish to start. You can check this value by running "env".
     
  2. On UNIX and Linux the db2profile should be sourced properly (db2cshrc for C shell). This may mean the user's profile contains a command similar to:

    . sqllib/db2profile
     
  3. If you're on AIX and receiving this message you should check the password algorithm being used for the user. The sha256 algorithm, for example, is not supported in DB2 V9.1 (at V9.5 Fix Pack 4 it is). You can check the password rules for each DB2 version in the respective Information Center.
     
  4. Check the "id" output of the user running db2start. Then, check to make the user and user's group exist in the /etc/passwd and /etc/group files respectively. Make sure permissions correctly set (at least 644).

https://www-304.ibm.com/support/docview.wss?uid=swg21474604

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

db2icrt/db2idrop hangs when executing db2isrv  (0) 2011.12.28
Why is db2top screen output not being shown in colors?  (0) 2011.11.17
Install fails with "FILE keyword is not valid" error  (0) 2011.10.13
IY73035: "FORCE APPLICATION" ON GATEWAY CAN CAUSE GATEWAY INSTANCE CRASH IF MONITOR IS TURNED ON GATEWAY  (0) 2011.10.11
WRONG XA RC VALUE XA_RMERR (-3) IS RETURNED IN THE XA FUNCTION CALL DURING THE CONNECTION TIMEOUT CONDITION  (0) 2011.10.11
728x90

DB2 Setup log file started at: Thu Oct 13 16:53:26 2011 CDT

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


Operating system information: AIX 6.1

ERROR:The value provided for the FILE keyword is not valid. The location specified

"/opt/IBM/db2/V9.1" exists and is not empty. Specify a new or empty location.



DB2 Setup log file finished at: Thu Oct 13 16:53:26 2011 CDT

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



Problem(Abstract)

Installing DB2 in a non-default directory results in a "FILE keyword is not valid" error.

Symptom

Error as seen in the installation.log file:

DB2 Setup log file started at: Tue Jun 16 08:13:26 2010 EDT              
============================================================                                                                 
Operating system information: AIX 5.3                                    
ERROR:The value provided for the FILE keyword is not valid. The location 
specified "/opt/db2V91" exists and is not empty. Specify a new or empty location.                                                                  
DB2 Setup log file finished at: Tue Jun 16 08:13:27 2010 EDT             
============================================================             

In this scenario the non-default installation directory being used is /opt/db2V91.

Cause

The specified directory is not empty. There may be files or possibly another directory within it.

Resolving the problem

Change directories (cd) to the non-default directory you want to install in. Verify that the directory is empty.

Example:
root@nuat01 /opt/db2V91> ls -latr 
total 8 
drwxrwxrwx 2 root system 256 Feb 1 07:40 lost+found 
drwxr-xr-x 6 bin bin 256 Feb 1 15:54 .. 
drwxrwxrwx 3 root system 4096 Feb 5 18:59 . 

In this example the directory is not actually empty. The lost+found directory is present. 

Resolution:

  1. Remove lost+found directory
  2. Install DB2
  3. Recreate lost+found directory



http://www-01.ibm.com/support/docview.wss?uid=swg21437910

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

Why is db2top screen output not being shown in colors?  (0) 2011.11.17
DB2START Fails with SQL10007N Message "-1390" could not be retrieved.  (0) 2011.10.18
IY73035: "FORCE APPLICATION" ON GATEWAY CAN CAUSE GATEWAY INSTANCE CRASH IF MONITOR IS TURNED ON GATEWAY  (0) 2011.10.11
WRONG XA RC VALUE XA_RMERR (-3) IS RETURNED IN THE XA FUNCTION CALL DURING THE CONNECTION TIMEOUT CONDITION  (0) 2011.10.11
SQL30081N TCPIP communication errors  (0) 2011.10.11
728x90

Error description


User affected: Users who use V8 client ->V8 Gateway ->DB2 server configuration.

Problem description:
In V8 client -> V8 GW -> server configuration, if the request from the client is big(greater than communication buffer size) and MONITOR is turned on on gateway, running "force application" command on gateway may cause gateway instance crash.
You can see similar messages in db2diag.log:
2005-06-08-17.01.05.054919   Instance:XXXXXX   Node:000
PID:76504(db2agentg (XXXXX ) 0)   TID:1
Appid:O212DF2D.GF2E.01045B2D1685
DRDA Application Server  sqljsTermAgentReply Probe:10
DIA5000C A DRDA AS token "AGENT TERMINATING" was detected.  The
diagnostic data
returned is (SRVDGN): "SQLERRP:SQLJCMN  SQLCODE:-30081".
ALERT :26
PID:76504 TID:1 Node:000 Title: SQLCA
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -30081   sqlerrml:
37
 sqlerrmc: 32 * 0 TCP/IP SOCKETS 127.0.0.1 send
 sqlerrp : SQLJCMN ?
 sqlerrd : (1) 0x81360012      (2) 0x00000012      (3)
0x00000000
           (4) 0x00000000      (5) 0x00000000      (6)
0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
          (7)      (8)      (9)      (10)        (11)
 sqlstate:
2005-06-08-17.01.05.762408   Instance:XXXXXX   Node:000
PID:76504(db2agentg (XXXXX ) 0)   TID:1
Appid:O212DF2D.GF2E.01045B2D1685
base sys utilities  sqleagnt_sigsegvh Probe:1
Error in agent servicing application with coor_node:
0x2FF19ECC : 0x0000                                     ..
Trap file looks like that:
0xD1F0E0A0 sqljcCompleteDss__FP10sqljCmnMgrl + 0x11C
0xD2CABCA0 sqljrDrdaArDisconnect__FP7UCintfc + 0x244
0xD2510640 sqleuUCagentDrdaArTermConnect__FP7UCintfc + 0x88
0xD250EB68 sqleUCagentConnectReset + 0x148
0xD1CC7DC0 sqljsCleanup__FP13sqle_agent_cbP11UCconHandle + 0x244
0xD1CC7608 sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0x2A0
0xD1CC7440 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 0x134


Local fix

Connect directly to server.


Problem summary

User Affected:
Users who using DB2 gateway and monitor is turned on Problem Description:
If you run DB2 as a gateway, and monitor is turned on in the gateway, you may encounter DB2 crash if you issue "force applicaiton all" command in gateway server.
Problem Summary:
In V8 client -> V8 gateway -> server configuration, and monitor is turned on on the gateway. You may encounter DB2 instance cras h if you running "FORCE APPLICATION" command on the DB2 gateway server. The trap file looks like that:
0xD1F0E0A0 sqljcCompleteDss__FP10sqljCmnMgrl + 0x11C
0xD2CABCA0 sqljrDrdaArDisconnect__FP7UCintfc + 0x244
0xD2510640 sqleuUCagentDrdaArTermConnect__FP7UCintfc + 0x88
0xD250EB68 sqleUCagentConnectReset + 0x148
0xD1CC7DC0 sqljsCleanup__FP13sqle_agent_cbP11UCconHandle + 0x244
0xD1CC7608 sqljsDrdaAsInnerDriver__FP17sqlcc_init_structb + 0x2A0
0xD1CC7440 sqljsDrdaAsDriver__FP17sqlcc_init_struct + 0x134


Problem conclusion

Problem was first fixed in Version 8.1 FixPak 11(also known as Version 8.2 FixPak 4)(s060120)


Temporary fix

Connect to DB2 server directly, don't use DB2 gateway.

APAR Information

  • APAR number

    IY73035

  • Reported component name

    DB2 UDB ESE AIX

  • Reported component ID

    5765F4100

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2005-06-23

  • Closed date

    2006-02-05

  • Last modified date

    2006-02-05




http://www-01.ibm.com/support/docview.wss?uid=swg1IY73035

728x90
저작자표시 비영리 변경금지

'Db2 > Db2 troubleshooting' 카테고리의 다른 글

DB2START Fails with SQL10007N Message "-1390" could not be retrieved.  (0) 2011.10.18
Install fails with "FILE keyword is not valid" error  (0) 2011.10.13
WRONG XA RC VALUE XA_RMERR (-3) IS RETURNED IN THE XA FUNCTION CALL DURING THE CONNECTION TIMEOUT CONDITION  (0) 2011.10.11
SQL30081N TCPIP communication errors  (0) 2011.10.11
테이블 스페이스 컨테이너 추가 개수에 대한 이슈  (0) 2011.10.06

+ Recent posts

티스토리툴바