| Thread | Last Post | Replies |
|
| db2stop taking time | 27 Oct 2008 09:54 GMT | 5 |
When i am trying to take offline backup of my production db .. it is taking more time in db2stop command (around 15 min.) while earlier max was 2 mins. what might be the reason for this delay. To stop the db I am using following sequence of commands:-
|
| dynamic sql - prepare statement | 27 Oct 2008 08:39 GMT | 1 |
Hy, I am trying to understand how the prepare statement works. I am using Qt C++ library to access db2: {
|
| DB2 Database Administrator | 26 Oct 2008 20:08 GMT | 3 |
I'm sorry if it sounds off topic but please help m, because your replies will really effect on my decision: I have been in touch with DB2 and its administrations tasks, and i want to extend my abilities on administration part. meanwhile I have a
|
| Possible to manually mark routine packages as inoperative in DB2LUW? | 26 Oct 2008 15:02 GMT | 8 |
Is there a mechanism for manually marking routine packages as inoperative in DB2LUW? The problem I'm trying to solve is one of recreating interdependent functions. My application creates a number of functions during its
|
| DATABASECAPACITY and SMS tablespaces | 25 Oct 2008 20:12 GMT | 2 |
So I have a good-sized db (~500GB) that's on only SMS tablespaces(ugh, I know). I'm tight on space and keeping an eye using the get_dbsize_info function - but the DATABASECAPACITY value keeps changing. I know on DMS tablespaces, DATABASECAPACITY is tied to the
|
| DB2 federation problem when reconnecting to a remote federated AS/400 | 24 Oct 2008 18:35 GMT | 1 |
My Windows DB2 Server 9.x is connected, via federation, to a remote AS/ 400 system: I created several nicknames to remote tables and I can query them. Problem is, during the night, my remote AS/400 is rebooted and DB2
|
| 9.5 LUW, pointers on running 32 bit client against 64 bit server? | 23 Oct 2008 17:41 GMT | 6 |
I'm trying to read up on the possibility to migrate a db2 V9.5 server to 64 bit, and continue running 32 bit application servers (via db2 runtime client, or otherwise). Does anyone have links to this kind of information? I've google around a bit, and searched the db2 docs
|
| issue on | 23 Oct 2008 11:06 GMT | 3 |
The problem over here is when i am runing these query in test region it is working fine. but when i run in the production region it fails and giving error like : 434: An ON clause associated with a JOIN operator or in a MERGE
|
| PHP5 and DB2 9.5 | 22 Oct 2008 16:52 GMT | 2 |
We have an older Suse linux server with DB2 v8.2 and PHP 4.4.2. The PHP was configured --with-ibm_db2 and uses odbc_connect(), odbc_exec(), odbc_fetch_row(), odbc_result(). We have a new Redhat (RHEL5) server with DB2 Workgroup Edition v9.5
|
| Yielding timeslice | 22 Oct 2008 14:35 GMT | 1 |
I'm getting a large number of paragraphs like this in a db2diag.log: 2008-10-22-09.31.50.339542+120 I277626395A468 LEVEL: Warning PID : 1576968 TID : 1 PROC : db2agntp (SST) 0 INSTANCE: db2inst2 NODE : 000 DB : SST
|
| Sigh, Undocumented error - SQL30082N, RC=22 | 21 Oct 2008 21:32 GMT | 1 |
I'm installing DB2 9.1 on z/OS 1.9 and am trying to test DRDA. Can anyone tell me where to find documentation on SQL30082N, RC=22? Thank you, kk
|
| How to determine the isolation level of incoming queries. | 21 Oct 2008 19:48 GMT | 3 |
Is there any way of tracking the isolation level of incoming queries from the server; not the client? The client app is a third party black box application. Can't find anything in the snapshots or activity monitor.
|
| confusion about cardinality in explain plan node on compressed table | 21 Oct 2008 19:38 GMT | 2 |
I have compressed table 442992 rows and when i run explain plan on this table for some SQL using this table, i see table scan and cardinality on top of table node as 18458. I am new to compression and do not understand why cardinality is not the actual number of rows but
|
| backup with multiple targets | 21 Oct 2008 11:41 GMT | 2 |
I was trying to make backup faster so After studying I used this cmd for backup:- db2 backup db <dbname> to /bkup/dir1, /bkup/dir2 compress without prompting;
|
| SQL30082N Attempt to establish connection failed with security reason "24" ("USERNAME AND/OR PASSWORD INVALID"). | 21 Oct 2008 10:02 GMT | 2 |
I encounted this error when i restored database. but the usename and password is right.
|