Unix Technical Forum

What is db restore waiting for ?

This is a discussion on What is db restore waiting for ? within the DB2 forums, part of the Database Server Software category; --> I am copying a DB2 UDB (7.2.4) on UNIX (4.3.3) production system to a temporary system. I think I ...


Go Back   Unix Technical Forum > Database Server Software > DB2

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-26-2008, 09:57 AM
James
 
Posts: n/a
Default What is db restore waiting for ?

I am copying a DB2 UDB (7.2.4) on UNIX (4.3.3) production system to a
temporary system.

I think I created the same instance, built the same filesystem, set
the same authorization on temporary system, but after I issue "db2
restore db XXX from /sapbackup", after about 2 hours, all the
containers are restored to the filesystem, but this command does not
exist! Not any I/O activity. CPU is 50% idel and 50% I/O wait.

How can I know what is it waiting for? What else can I check except
for database filesystem and log filesystem?

I've created directories log_archive, log_dir, log_retrieve under
/db2/SP1.


Thanks for your comment in advance.
jamesyang@163.net


# df -k
Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 327680 301248 9% 1397 1% /
/dev/hd2 1343488 461444 66% 19490 6% /usr
/dev/hd9var 16384 14000 15% 189 5% /var
/dev/hd3 32768 29660 10% 132 2% /tmp
/dev/hd1 16384 15728 5% 40 1% /home
/dev/localSID 524288 505552 4% 125 1% /usr/sap/SP1
/dev/sapmntSID 524288 391820 26% 145 1% /sapmnt/SP1
/dev/saptrans 786432 761652 4% 29 1%
/usr/sap/trans
/dev/sapdb2 5242880 5041884 4% 647 1% /db2
/dev/sapdata1 11534336 1019552 92% 61 1%
/db2/SP1/sapdata1
/dev/sapdata2 4194304 1635960 61% 36 1%
/db2/SP1/sapdata2
/dev/sapdata3 10485760 2255400 79% 31 1%
/db2/SP1/sapdata3
/dev/sapdata4 6291456 1442784 78% 29 1%
/db2/SP1/sapdata4
/dev/sapdata5 10485760 2255156 79% 30 1%
/db2/SP1/sapdata5
/dev/sapdata6 5242880 2077788 61% 24 1%
/db2/SP1/sapdata6
/dev/sapdata7 10485760 2305012 79% 36 1%
/db2/SP1/sapdata7
/dev/sapdata8 10485760 3103628 71% 47 1%
/db2/SP1/sapdata8
/dev/sapdata9 10485760 4865552 54% 29 1%
/db2/SP1/sapdata9
/dev/lv00 4063232 279624 94% 5006 1% /sapinst
h70sp1:/db2/sapbck/dbback 81428480 34165212 59% 22 1%
/sapbackup


# ps aux |head
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 48.6 1.0 12 15592 - A 21:06:42 1050:01 kproc
root 774 48.5 1.0 12 15592 - A 21:06:42 1047:55 kproc
db2sp1 17650 0.8 0.0 600 356 - A 11:48:45 3:01 db2pfchr
db2sp1 19144 0.7 0.0 608 356 - A 11:48:45 2:57 db2pfchr
root 1032 0.7 1.0 12 15592 - A 21:06:42 14:15 kproc
db2sp1 14384 0.6 0.0 616 356 - A 11:48:45 2:26 db2pfchr
root 3146 0.2 0.0 164 188 - A 21:08:13 3:53
/usr/sbin/syncd 6
root 2678 0.1 0.0 1300 1468 - A 21:08:59 2:04 dtgreet
db2sp1 25418 0.0 0.0 4832 4744 - A 14:15:45 0:01 db2agent
(idle)

# ps aux |grep -v wait |head
USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 48.6 1.0 12 15592 - A 21:06:42 1050:13 kproc
root 774 48.5 1.0 12 15592 - A 21:06:42 1048:06 kproc
db2sp1 17650 0.8 0.0 600 356 - A 11:48:45 3:01 db2pfchr
db2sp1 19144 0.7 0.0 608 356 - A 11:48:45 2:57 db2pfchr
root 1032 0.7 1.0 12 15592 - A 21:06:42 14:15 kproc
db2sp1 14384 0.6 0.0 616 356 - A 11:48:45 2:26 db2pfchr
root 3146 0.2 0.0 164 188 - A 21:08:13 3:53
/usr/sbin/syncd 6
root 2678 0.1 0.0 1300 1468 - A 21:08:59 2:04 dtgreet
db2sp1 25418 0.0 0.0 4832 4744 - A 14:15:45 0:01 db2agent
(idle)


db2 => connect to SP1
SQL1119N A connection to or activation of database "SP1" cannot be
made
because a previous restore is incomplete. SQLSTATE=57019



db2 => get dbm cfg

Database Manager Configuration

Node type = Database Server with local and remote clients

Database manager configuration release level = 0x0900

CPU speed (millisec/instruction) (CPUSPEED) =
1.621715e-06

Max number of concurrently active databases (NUMDB) = 8
Data Links support (DATALINKS) = NO
Federated Database System Support (FEDERATED) = YES
Transaction processor monitor name (TP_MON_NAME) =

Default charge-back account (DFT_ACCOUNT_STR) =

Java Development Kit 1.1 installation path (JDK11_PATH) =

Diagnostic error capture level (DIAGLEVEL) = 3
Diagnostic data directory path (DIAGPATH) =
/db2/SP1/sqllib/db2du
mp

Default database monitor switches
Buffer pool (DFT_MON_BUFPOOL) = OFF
Lock (DFT_MON_LOCK) = OFF
Sort (DFT_MON_SORT) = OFF
Statement (DFT_MON_STMT) = OFF
Table (DFT_MON_TABLE) = OFF
Unit of work (DFT_MON_UOW) = OFF

SYSADM group name (SYSADM_GROUP) = SYSADM
SYSCTRL group name (SYSCTRL_GROUP) = SYSCTRL
SYSMAINT group name (SYSMAINT_GROUP) =

Database manager authentication (AUTHENTICATION) = SERVER
Cataloging allowed without authority (CATALOG_NOAUTH) = NO
Trust all clients (TRUST_ALLCLNTS) = YES
Trusted client authentication (TRUST_CLNTAUTH) = CLIENT

Default database path (DFTDBPATH) = /db2/SP1

Database monitor heap size (4KB) (MON_HEAP_SZ) = 56
UDF shared memory set size (4KB) (UDF_MEM_SZ) = 256
Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0

Backup buffer default size (4KB) (BACKBUFSZ) = 1024
Restore buffer default size (4KB) (RESTBUFSZ) = 1024

Sort heap threshold (4KB) (SHEAPTHRES) = 20000

Directory cache support (DIR_CACHE) = YES

Application support layer heap size (4KB) (ASLHEAPSZ) = 15
Max requester I/O block size (bytes) (RQRIOBLK) = 32767
Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128

Priority of agents (AGENTPRI) = SYSTEM
Max number of existing agents (MAXAGENTS) = 200
Agent pool size (NUM_POOLAGENTS) = 8
(calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0
Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS
- NUM_INIT
AGENTS)
Max no. of concurrent coordinating agents (MAXCAGENTS) =
MAX_COORDAGENTS
Max number of logical agents (MAX_LOGICAGENTS) =
MAX_COORDAGENTS

Keep DARI process (KEEPDARI) = YES
Max number of DARI processes (MAXDARI) =
MAX_COORDAGENTS
Initialize DARI process with JVM (INITDARI_JVM) = NO
Initial number of fenced DARI process (NUM_INITDARIS) = 0

Index re-creation time (INDEXREC) = RESTART

Transaction manager database name (TM_DATABASE) = 1ST_CONN
Transaction resync interval (sec) (RESYNC_INTERVAL) = 180

SPM name (SPM_NAME) = h70ent
SPM log size (SPM_LOG_FILE_SZ) = 256
SPM resync agent limit (SPM_MAX_RESYNC) = 20
SPM log path (SPM_LOG_PATH) =

TCP/IP Service name (SVCENAME) = sapdb2SP1
APPC Transaction program name (TPNAME) =
IPX/SPX File server name (FILESERVER) =
IPX/SPX DB2 server object name (OBJECTNAME) =
IPX/SPX Socket number (IPX_SOCKET) = 879E

Discovery mode (DISCOVER) = SEARCH
Discovery communication protocols (DISCOVER_COMM) = TCPIP
Discover server instance (DISCOVER_INST) = ENABLE

Directory services type (DIR_TYPE) = NONE
Directory path name (DIR_PATH_NAME) =
/.:/subsys/database/
Directory object name (DIR_OBJ_NAME) =
Routing information object name (ROUTE_OBJ_NAME) =
Default client comm. protocols (DFT_CLIENT_COMM) =

Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
Enable intra-partition parallelism (INTRA_PARALLEL) = YES

No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 1024
Number of FCM request blocks (FCM_NUM_RQB) = 512
Number of FCM connection entries (FCM_NUM_CONNECT) =
(FCM_NUM_RQB * 0.75)
Number of FCM message anchors (FCM_NUM_ANCHORS) =
(FCM_NUM_RQB * 0.75)



Error message in /db2/SP1/sqllib/db2dump/db2diag.log



2003-07-15-11.44.02.094246 Instance:db2sp1 Node:000
PID:21830(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.44.03.537094 Instance:db2sp1 Node:000
PID:21830(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.44.03.614787 Instance:db2sp1 Node:000
PID:21830(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.44.12.679641 Instance:db2sp1 Node:000
PID:15770(db2stop2) Appid:none
base_sys_utilities stopdbm Probe:911

Database manager is stopped.

2003-07-15-11.44.46.813356 Instance:db2sp1 Node:000
PID:19132(db2star2) Appid:none
base_sys_utilities LicCheckProcessors Probe:11

SQL8017W The number of processors on this machine exceeds the defined
entitlement of "1" for the product "DB2 Enterprise Edition". The
number of
processors on this machine is "2". You should purchase additional
processor
entitlements from your IBM representative or authorized dealer and
update your
license using the License Center or the db2licm command line utility.
For more
information on updating processor licenses, refer to the Quick
Beginnings
manual for your platform. For more information on the db2licm
utility, refer
to the DB2 Command Reference.


2003-07-15-11.44.48.055209 Instance:db2sp1 Node:000
PID:18538(db2spmrm) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 0011 ....


2003-07-15-11.44.48.158622 Instance:db2sp1 Node:000
PID:19132(db2star2) Appid:none
base_sys_utilities startdbm Probe:911

Database manager is started.

2003-07-15-11.45.04.501943 Instance:db2sp1 Node:000
PID:19134(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
database_utilities sqludPrintStartingMsg Probe:1 Database:TESTDB

Starting a full database restore.

2003-07-15-11.45.04.664720 Instance:db2sp1 Node:000
PID:16074(db2bm.19134.0) Appid:none
database_utilities sqluhOpen Probe:769

DB History: Error reading header. rc = ffff f609
....


2003-07-15-11.45.04.728552 Instance:db2sp1 Node:000
PID:16074(db2bm.19134.0) Appid:none
database_utilities sqluhOpen Probe:893

DB History: Nonrecoverable error - existing history deleted, backup
made.

2003-07-15-11.45.04.820215 Instance:db2sp1 Node:000
PID:16074(db2bm.19134.0) Appid:none
database_utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by
the backup image.


2003-07-15-11.46.18.801619 Instance:db2sp1 Node:000
PID:19134(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
database_utilities sqludrsa Probe:0 Database:TESTDB

Restore Complete.

2003-07-15-11.46.33.408916 Instance:db2sp1 Node:000
PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
PSM - SQL Procedure psm_recover_all_procs Probe:8 Database:TESTDB

SQL procedure executables recovery has been initiated.

2003-07-15-11.46.33.470870 Instance:db2sp1 Node:000
PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
PSM - SQL Procedure psm_recover_all_procs Probe:36
Database:TESTDB

SQL procedure executables recovery ended. RC: 0000 0000
....


2003-07-15-11.46.55.319896 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.46.56.799915 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.46.56.877674 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.47.08.396911 Instance:db2sp1 Node:000
PID:24884(db2bp) Appid:*LOCAL.db2sp1.030715164505
database_utilities sqludProcessInitialCall Probe:60

DiagData
ffff fbe9 


2003-07-15-11.47.33.632242 Instance:db2sp1 Node:000
PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164735
database_utilities sqludPrintStartingMsg Probe:1 Database:TESTDB

Starting a full database restore.

2003-07-15-11.47.33.783685 Instance:db2sp1 Node:000
PID:16080(db2bm.20454.0) Appid:none
database_utilities sqluhOpen Probe:769

DB History: Error reading header. rc = ffff f609
....


2003-07-15-11.47.33.861044 Instance:db2sp1 Node:000
PID:16080(db2bm.20454.0) Appid:none
database_utilities sqluhOpen Probe:893

DB History: Nonrecoverable error - existing history deleted, backup
made.

2003-07-15-11.47.33.942953 Instance:db2sp1 Node:000
PID:16080(db2bm.20454.0) Appid:none
database_utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by
the backup image.


2003-07-15-11.47.44.673008 Instance:db2sp1 Node:000
PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164735
database_utilities sqludrsa Probe:0 Database:TESTDB

Restore Complete.

2003-07-15-11.48.08.163943 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.48.09.586461 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.48.09.646274 Instance:db2sp1 Node:000
PID:25320(db2agent (instance)) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....


2003-07-15-11.48.45.352704 Instance:db2sp1 Node:000
PID:18134(db2agent (SP1)) Appid:*LOCAL.db2sp1.030715164846
database_utilities sqludPrintStartingMsg Probe:1 Database:SP1

Starting a full database restore.

2003-07-15-11.50.57.612194 Instance:db2sp1 Node:000
PID:16082(db2bm.18134.0) Appid:none
database_utilities sqluhOpen Probe:769

DB History: Error reading header. rc = ffff f609
....


2003-07-15-11.50.57.675838 Instance:db2sp1 Node:000
PID:16082(db2bm.18134.0) Appid:none
database_utilities sqluhOpen Probe:893

DB History: Nonrecoverable error - existing history deleted, backup
made.

2003-07-15-11.50.57.778066 Instance:db2sp1 Node:000
PID:16082(db2bm.18134.0) Appid:none
database_utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by
the backup image.


2003-07-15-12.50.35.060629 Instance:db2sp1 Node:000
PID:16082(db2bm.18134.0) Appid:none
oper_system_services sqloopenp Probe:36

errno: 0000 001a ....
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-26-2008, 09:58 AM
James
 
Posts: n/a
Default Re: What is db restore waiting for ?

P.S.

create db & drop db can exit successfully.

I've tested a small testdb restore, it works sometimes but dows not
work sometimes, and I do not know the difference.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-26-2008, 09:58 AM
Vikrant
 
Posts: n/a
Default Re: What is db restore waiting for ?

Hi James,

It seems you are using DB2/UDB with SAP R/3, I would suggest you also
put this problem on DB2forSAP forum www.sap-db2.de
or put an OSS message under BC-DB-DB6-ADM

Thanks,
VKG
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-26-2008, 09:59 AM
Fan Ruo Xin
 
Posts: n/a
Default Re: What is db restore waiting for ?

James,
(1) Can you post the all the db2 processes when there is no io activity ?
ps -ef|grep <InstName>
(2) Can you turn of the the dbm cfg - keepdari = NO, then do the restore
to see if the restore can exit this time?

Regards,
FRX



James wrote:

> I am copying a DB2 UDB (7.2.4) on UNIX (4.3.3) production system to a
> temporary system.
>
> I think I created the same instance, built the same filesystem, set
> the same authorization on temporary system, but after I issue "db2
> restore db XXX from /sapbackup", after about 2 hours, all the
> containers are restored to the filesystem, but this command does not
> exist! Not any I/O activity. CPU is 50% idel and 50% I/O wait.
>
> How can I know what is it waiting for? What else can I check except
> for database filesystem and log filesystem?
>
> I've created directories log_archive, log_dir, log_retrieve under
> /db2/SP1.
>
> Thanks for your comment in advance.
> jamesyang@163.net
>
> # df -k
> Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
> /dev/hd4 327680 301248 9% 1397 1% /
> /dev/hd2 1343488 461444 66% 19490 6% /usr
> /dev/hd9var 16384 14000 15% 189 5% /var
> /dev/hd3 32768 29660 10% 132 2% /tmp
> /dev/hd1 16384 15728 5% 40 1% /home
> /dev/localSID 524288 505552 4% 125 1% /usr/sap/SP1
> /dev/sapmntSID 524288 391820 26% 145 1% /sapmnt/SP1
> /dev/saptrans 786432 761652 4% 29 1%
> /usr/sap/trans
> /dev/sapdb2 5242880 5041884 4% 647 1% /db2
> /dev/sapdata1 11534336 1019552 92% 61 1%
> /db2/SP1/sapdata1
> /dev/sapdata2 4194304 1635960 61% 36 1%
> /db2/SP1/sapdata2
> /dev/sapdata3 10485760 2255400 79% 31 1%
> /db2/SP1/sapdata3
> /dev/sapdata4 6291456 1442784 78% 29 1%
> /db2/SP1/sapdata4
> /dev/sapdata5 10485760 2255156 79% 30 1%
> /db2/SP1/sapdata5
> /dev/sapdata6 5242880 2077788 61% 24 1%
> /db2/SP1/sapdata6
> /dev/sapdata7 10485760 2305012 79% 36 1%
> /db2/SP1/sapdata7
> /dev/sapdata8 10485760 3103628 71% 47 1%
> /db2/SP1/sapdata8
> /dev/sapdata9 10485760 4865552 54% 29 1%
> /db2/SP1/sapdata9
> /dev/lv00 4063232 279624 94% 5006 1% /sapinst
> h70sp1:/db2/sapbck/dbback 81428480 34165212 59% 22 1%
> /sapbackup
>
> # ps aux |head
> USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
> root 516 48.6 1.0 12 15592 - A 21:06:42 1050:01 kproc
> root 774 48.5 1.0 12 15592 - A 21:06:42 1047:55 kproc
> db2sp1 17650 0.8 0.0 600 356 - A 11:48:45 3:01 db2pfchr
> db2sp1 19144 0.7 0.0 608 356 - A 11:48:45 2:57 db2pfchr
> root 1032 0.7 1.0 12 15592 - A 21:06:42 14:15 kproc
> db2sp1 14384 0.6 0.0 616 356 - A 11:48:45 2:26 db2pfchr
> root 3146 0.2 0.0 164 188 - A 21:08:13 3:53
> /usr/sbin/syncd 6
> root 2678 0.1 0.0 1300 1468 - A 21:08:59 2:04 dtgreet
> db2sp1 25418 0.0 0.0 4832 4744 - A 14:15:45 0:01 db2agent
> (idle)
>
> # ps aux |grep -v wait |head
> USER PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
> root 516 48.6 1.0 12 15592 - A 21:06:42 1050:13 kproc
> root 774 48.5 1.0 12 15592 - A 21:06:42 1048:06 kproc
> db2sp1 17650 0.8 0.0 600 356 - A 11:48:45 3:01 db2pfchr
> db2sp1 19144 0.7 0.0 608 356 - A 11:48:45 2:57 db2pfchr
> root 1032 0.7 1.0 12 15592 - A 21:06:42 14:15 kproc
> db2sp1 14384 0.6 0.0 616 356 - A 11:48:45 2:26 db2pfchr
> root 3146 0.2 0.0 164 188 - A 21:08:13 3:53
> /usr/sbin/syncd 6
> root 2678 0.1 0.0 1300 1468 - A 21:08:59 2:04 dtgreet
> db2sp1 25418 0.0 0.0 4832 4744 - A 14:15:45 0:01 db2agent
> (idle)
>
> db2 => connect to SP1
> SQL1119N A connection to or activation of database "SP1" cannot be
> made
> because a previous restore is incomplete. SQLSTATE=57019
>
> db2 => get dbm cfg
>
> Database Manager Configuration
>
> Node type = Database Server with local and remote clients
>
> Database manager configuration release level = 0x0900
>
> CPU speed (millisec/instruction) (CPUSPEED) =
> 1.621715e-06
>
> Max number of concurrently active databases (NUMDB) = 8
> Data Links support (DATALINKS) = NO
> Federated Database System Support (FEDERATED) = YES
> Transaction processor monitor name (TP_MON_NAME) =
>
> Default charge-back account (DFT_ACCOUNT_STR) =
>
> Java Development Kit 1.1 installation path (JDK11_PATH) =
>
> Diagnostic error capture level (DIAGLEVEL) = 3
> Diagnostic data directory path (DIAGPATH) =
> /db2/SP1/sqllib/db2du
> mp
>
> Default database monitor switches
> Buffer pool (DFT_MON_BUFPOOL) = OFF
> Lock (DFT_MON_LOCK) = OFF
> Sort (DFT_MON_SORT) = OFF
> Statement (DFT_MON_STMT) = OFF
> Table (DFT_MON_TABLE) = OFF
> Unit of work (DFT_MON_UOW) = OFF
>
> SYSADM group name (SYSADM_GROUP) = SYSADM
> SYSCTRL group name (SYSCTRL_GROUP) = SYSCTRL
> SYSMAINT group name (SYSMAINT_GROUP) =
>
> Database manager authentication (AUTHENTICATION) = SERVER
> Cataloging allowed without authority (CATALOG_NOAUTH) = NO
> Trust all clients (TRUST_ALLCLNTS) = YES
> Trusted client authentication (TRUST_CLNTAUTH) = CLIENT
>
> Default database path (DFTDBPATH) = /db2/SP1
>
> Database monitor heap size (4KB) (MON_HEAP_SZ) = 56
> UDF shared memory set size (4KB) (UDF_MEM_SZ) = 256
> Java Virtual Machine heap size (4KB) (JAVA_HEAP_SZ) = 2048
> Audit buffer size (4KB) (AUDIT_BUF_SZ) = 0
>
> Backup buffer default size (4KB) (BACKBUFSZ) = 1024
> Restore buffer default size (4KB) (RESTBUFSZ) = 1024
>
> Sort heap threshold (4KB) (SHEAPTHRES) = 20000
>
> Directory cache support (DIR_CACHE) = YES
>
> Application support layer heap size (4KB) (ASLHEAPSZ) = 15
> Max requester I/O block size (bytes) (RQRIOBLK) = 32767
> Query heap size (4KB) (QUERY_HEAP_SZ) = 1000
> DRDA services heap size (4KB) (DRDA_HEAP_SZ) = 128
>
> Priority of agents (AGENTPRI) = SYSTEM
> Max number of existing agents (MAXAGENTS) = 200
> Agent pool size (NUM_POOLAGENTS) = 8
> (calculated)
> Initial number of agents in pool (NUM_INITAGENTS) = 0
> Max number of coordinating agents (MAX_COORDAGENTS) = (MAXAGENTS
> - NUM_INIT
> AGENTS)
> Max no. of concurrent coordinating agents (MAXCAGENTS) =
> MAX_COORDAGENTS
> Max number of logical agents (MAX_LOGICAGENTS) =
> MAX_COORDAGENTS
>
> Keep DARI process (KEEPDARI) = YES
> Max number of DARI processes (MAXDARI) =
> MAX_COORDAGENTS
> Initialize DARI process with JVM (INITDARI_JVM) = NO
> Initial number of fenced DARI process (NUM_INITDARIS) = 0
>
> Index re-creation time (INDEXREC) = RESTART
>
> Transaction manager database name (TM_DATABASE) = 1ST_CONN
> Transaction resync interval (sec) (RESYNC_INTERVAL) = 180
>
> SPM name (SPM_NAME) = h70ent
> SPM log size (SPM_LOG_FILE_SZ) = 256
> SPM resync agent limit (SPM_MAX_RESYNC) = 20
> SPM log path (SPM_LOG_PATH) =
>
> TCP/IP Service name (SVCENAME) = sapdb2SP1
> APPC Transaction program name (TPNAME) =
> IPX/SPX File server name (FILESERVER) =
> IPX/SPX DB2 server object name (OBJECTNAME) =
> IPX/SPX Socket number (IPX_SOCKET) = 879E
>
> Discovery mode (DISCOVER) = SEARCH
> Discovery communication protocols (DISCOVER_COMM) = TCPIP
> Discover server instance (DISCOVER_INST) = ENABLE
>
> Directory services type (DIR_TYPE) = NONE
> Directory path name (DIR_PATH_NAME) =
> /.:/subsys/database/
> Directory object name (DIR_OBJ_NAME) =
> Routing information object name (ROUTE_OBJ_NAME) =
> Default client comm. protocols (DFT_CLIENT_COMM) =
>
> Maximum query degree of parallelism (MAX_QUERYDEGREE) = ANY
> Enable intra-partition parallelism (INTRA_PARALLEL) = YES
>
> No. of int. communication buffers(4KB)(FCM_NUM_BUFFERS) = 1024
> Number of FCM request blocks (FCM_NUM_RQB) = 512
> Number of FCM connection entries (FCM_NUM_CONNECT) =
> (FCM_NUM_RQB * 0.75)
> Number of FCM message anchors (FCM_NUM_ANCHORS) =
> (FCM_NUM_RQB * 0.75)
>
> Error message in /db2/SP1/sqllib/db2dump/db2diag.log
>
> 2003-07-15-11.44.02.094246 Instance:db2sp1 Node:000
> PID:21830(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.44.03.537094 Instance:db2sp1 Node:000
> PID:21830(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.44.03.614787 Instance:db2sp1 Node:000
> PID:21830(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.44.12.679641 Instance:db2sp1 Node:000
> PID:15770(db2stop2) Appid:none
> base_sys_utilities stopdbm Probe:911
>
> Database manager is stopped.
>
> 2003-07-15-11.44.46.813356 Instance:db2sp1 Node:000
> PID:19132(db2star2) Appid:none
> base_sys_utilities LicCheckProcessors Probe:11
>
> SQL8017W The number of processors on this machine exceeds the defined
> entitlement of "1" for the product "DB2 Enterprise Edition". The
> number of
> processors on this machine is "2". You should purchase additional
> processor
> entitlements from your IBM representative or authorized dealer and
> update your
> license using the License Center or the db2licm command line utility.
> For more
> information on updating processor licenses, refer to the Quick
> Beginnings
> manual for your platform. For more information on the db2licm
> utility, refer
> to the DB2 Command Reference.
>
> 2003-07-15-11.44.48.055209 Instance:db2sp1 Node:000
> PID:18538(db2spmrm) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 0011 ....
>
> 2003-07-15-11.44.48.158622 Instance:db2sp1 Node:000
> PID:19132(db2star2) Appid:none
> base_sys_utilities startdbm Probe:911
>
> Database manager is started.
>
> 2003-07-15-11.45.04.501943 Instance:db2sp1 Node:000
> PID:19134(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
> database_utilities sqludPrintStartingMsg Probe:1 Database:TESTDB
>
> Starting a full database restore.
>
> 2003-07-15-11.45.04.664720 Instance:db2sp1 Node:000
> PID:16074(db2bm.19134.0) Appid:none
> database_utilities sqluhOpen Probe:769
>
> DB History: Error reading header. rc = ffff f609
> ....
>
> 2003-07-15-11.45.04.728552 Instance:db2sp1 Node:000
> PID:16074(db2bm.19134.0) Appid:none
> database_utilities sqluhOpen Probe:893
>
> DB History: Nonrecoverable error - existing history deleted, backup
> made.
>
> 2003-07-15-11.45.04.820215 Instance:db2sp1 Node:000
> PID:16074(db2bm.19134.0) Appid:none
> database_utilities sqludProcessHistoryFile Probe:3
>
> An empty database history has been detected.
> The database history will be overwritten by
> the backup image.
>
> 2003-07-15-11.46.18.801619 Instance:db2sp1 Node:000
> PID:19134(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
> database_utilities sqludrsa Probe:0 Database:TESTDB
>
> Restore Complete.
>
> 2003-07-15-11.46.33.408916 Instance:db2sp1 Node:000
> PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
> PSM - SQL Procedure psm_recover_all_procs Probe:8 Database:TESTDB
>
> SQL procedure executables recovery has been initiated.
>
> 2003-07-15-11.46.33.470870 Instance:db2sp1 Node:000
> PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164505
> PSM - SQL Procedure psm_recover_all_procs Probe:36
> Database:TESTDB
>
> SQL procedure executables recovery ended. RC: 0000 0000
> ....
>
> 2003-07-15-11.46.55.319896 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.46.56.799915 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.46.56.877674 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.47.08.396911 Instance:db2sp1 Node:000
> PID:24884(db2bp) Appid:*LOCAL.db2sp1.030715164505
> database_utilities sqludProcessInitialCall Probe:60
>
> DiagData
> ffff fbe9 
>
> 2003-07-15-11.47.33.632242 Instance:db2sp1 Node:000
> PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164735
> database_utilities sqludPrintStartingMsg Probe:1 Database:TESTDB
>
> Starting a full database restore.
>
> 2003-07-15-11.47.33.783685 Instance:db2sp1 Node:000
> PID:16080(db2bm.20454.0) Appid:none
> database_utilities sqluhOpen Probe:769
>
> DB History: Error reading header. rc = ffff f609
> ....
>
> 2003-07-15-11.47.33.861044 Instance:db2sp1 Node:000
> PID:16080(db2bm.20454.0) Appid:none
> database_utilities sqluhOpen Probe:893
>
> DB History: Nonrecoverable error - existing history deleted, backup
> made.
>
> 2003-07-15-11.47.33.942953 Instance:db2sp1 Node:000
> PID:16080(db2bm.20454.0) Appid:none
> database_utilities sqludProcessHistoryFile Probe:3
>
> An empty database history has been detected.
> The database history will be overwritten by
> the backup image.
>
> 2003-07-15-11.47.44.673008 Instance:db2sp1 Node:000
> PID:20454(db2agent (TESTDB)) Appid:*LOCAL.db2sp1.030715164735
> database_utilities sqludrsa Probe:0 Database:TESTDB
>
> Restore Complete.
>
> 2003-07-15-11.48.08.163943 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.48.09.586461 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.48.09.646274 Instance:db2sp1 Node:000
> PID:25320(db2agent (instance)) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....
>
> 2003-07-15-11.48.45.352704 Instance:db2sp1 Node:000
> PID:18134(db2agent (SP1)) Appid:*LOCAL.db2sp1.030715164846
> database_utilities sqludPrintStartingMsg Probe:1 Database:SP1
>
> Starting a full database restore.
>
> 2003-07-15-11.50.57.612194 Instance:db2sp1 Node:000
> PID:16082(db2bm.18134.0) Appid:none
> database_utilities sqluhOpen Probe:769
>
> DB History: Error reading header. rc = ffff f609
> ....
>
> 2003-07-15-11.50.57.675838 Instance:db2sp1 Node:000
> PID:16082(db2bm.18134.0) Appid:none
> database_utilities sqluhOpen Probe:893
>
> DB History: Nonrecoverable error - existing history deleted, backup
> made.
>
> 2003-07-15-11.50.57.778066 Instance:db2sp1 Node:000
> PID:16082(db2bm.18134.0) Appid:none
> database_utilities sqludProcessHistoryFile Probe:3
>
> An empty database history has been detected.
> The database history will be overwritten by
> the backup image.
>
> 2003-07-15-12.50.35.060629 Instance:db2sp1 Node:000
> PID:16082(db2bm.18134.0) Appid:none
> oper_system_services sqloopenp Probe:36
>
> errno: 0000 001a ....


Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-26-2008, 10:00 AM
James
 
Posts: n/a
Default Re: What is db restore waiting for ?

That is a stupid error.

I think NFS is supported but we did not config the network card very
well. The first 1.5 hours is to create the containers and then the
restore is waiting for reading the data blocks from the image!

I copyied the backup image to local and it spent another 4 hours to
restore the data.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 09:35 PM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
www.UnixAdminTalk.com