By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,756 Members | 1,760 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,756 IT Pros & Developers. It's quick & easy.

Problem with redirected restore

P: n/a
GL
I am running DB2 8.1.1 on AIX 5.1

Having a problem with a redirected restore.

Once into the restore continue phase, I immediately get the following

“SQL2059W A device full warning was encountered on device "TBS_IDX".
Do you want to continue(c), terminate this device only(d), abort the
utility(t)
? (c/d/t) t

I'm not allowed to continue as if I try I just get the 'warning' again.

This is the first DMS tablespace in the script.

Space does not seem to be the issue. The path in question is showing
49610752 in 1024 blocks allocated and only 17% used.

The tablespace in question was defined as 1000000 4k pages.

The permissions down the entire path are good.

I have checked and tried the following.

Checked ulimit and ulimit -a. Showing unlimited on ulimit.

Ulimit -a yields

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 245760
stack(kbytes) 16384
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

Went into smitty and made sure both the soft and hard file size limit
were set to -1 for the user (instance owner).

Tried breaking up the containers into separate directories for each
container. Tried using various size combinations from 100000 4k pages
each container to 200000 4k pages.

Tried defining the containers to total 1200000 4k pages, larger than
originally defined.

Tried defining one container at 100000 4k pages, 1/10th the original
sizing.

I get the same SQL error whatever I try.

In etc/security/limits the values for the instance owner show the
following

fsize = -1
core = -1
data = 491519
rss = -1
stack = 32767

I
fsize_hard = -1

So the size of the file I am defining does not seem to get rid of the
error.

As I've mentioned, the file permissions seem to be ok.

Would appreciate any comments or thoughts.

Many Thanks
Gerry
Nov 12 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a
Do you have another error messages in the db2diag.log ?
the answer of the ulimit command : are you using the userid of the instance
owner ?

do you have a db2 list tablespace containers for x before the restore ?
do you have a db2 list tablespaces show detail before the restore ?

"GL" <gl@nospam.net> a écrit dans le message de
news:Xn*************************@216.196.97.131...
I am running DB2 8.1.1 on AIX 5.1

Having a problem with a redirected restore.

Once into the restore continue phase, I immediately get the following

"SQL2059W A device full warning was encountered on device "TBS_IDX".
Do you want to continue(c), terminate this device only(d), abort the
utility(t)
? (c/d/t) t

I'm not allowed to continue as if I try I just get the 'warning' again.

This is the first DMS tablespace in the script.

Space does not seem to be the issue. The path in question is showing
49610752 in 1024 blocks allocated and only 17% used.

The tablespace in question was defined as 1000000 4k pages.

The permissions down the entire path are good.

I have checked and tried the following.

Checked ulimit and ulimit -a. Showing unlimited on ulimit.

Ulimit -a yields

time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 245760
stack(kbytes) 16384
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

Went into smitty and made sure both the soft and hard file size limit
were set to -1 for the user (instance owner).

Tried breaking up the containers into separate directories for each
container. Tried using various size combinations from 100000 4k pages
each container to 200000 4k pages.

Tried defining the containers to total 1200000 4k pages, larger than
originally defined.

Tried defining one container at 100000 4k pages, 1/10th the original
sizing.

I get the same SQL error whatever I try.

In etc/security/limits the values for the instance owner show the
following

fsize = -1
core = -1
data = 491519
rss = -1
stack = 32767

I
fsize_hard = -1

So the size of the file I am defining does not seem to get rid of the
error.

As I've mentioned, the file permissions seem to be ok.

Would appreciate any comments or thoughts.

Many Thanks
Gerry

Nov 12 '05 #2

P: n/a
GL
"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:
First, thanks...I really appreciate any thoughts you might have.

Do you have another error messages in the db2diag.log ?
Yes, please see below
the answer of the ulimit command : are you using the userid of the
instance owner ?
Yes

? do you have a db2 list tablespaces show detail before the restore ?
Yes, this is the tablespace in question of the database being restored

Tablespace ID = 5
Name = TBS_IDX
Type = Database managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal
Total pages = 1000000
Useable pages = 999808
Used pages = 604864
Free pages = 394944
High water mark (pages) = 910720
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 128
Number of containers = 4
Minimum recovery time = 2004-09-10-12.49.31.000000

do you have a db2 list tablespace containers for x before the restore


Yes
Tablespace Containers for Tablespace 5

Container ID = 0
Name = /db2idx/scioltpt/baseidx/sieb01
_idx.dat
Type = File

Container ID = 1
Name = /db2idx/scioltpt/baseidx/sieb02
_idx.dat
Type = File

Container ID = 2
Name = /db2idx/scioltpt/baseidx/sieb03
_idx.dat
Type = File

Container ID = 3
Name = /db2idx/scioltpt/baseidx/sieb04
_idx.dat
Type = File

This is the way the containers are defined in the restore script

set tablespace containers for 5 using
(File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
DB20000I The SET TABLESPACE CONTAINERS command completed successfully.

here are the entries from the db2diag.log when the redirected restore
script is started. I don't know if the unexpected end of file is typical
of entries for a redirected restore.

2004-09-12-10.07.59.075466 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbReadBufferPoolTable Probe:905

DIA8506C Unexpected end of file was reached.
ZRC=0x870F0009

Immediately after that entry, I get many, many repeated entries of
ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is most
definitely terminated before the restore..to the point where I have been
restarting db2 between runs, so I don't understand this message.

SQL1119N A connection to or activation of database "<name>" cannot be
made because a previous restore is incomplete.

Explanation: The database is in an inconsistent state because a system
error occurred during a restore function.

No connection was made.

Federated system users: this situation can be detected by the data
source.

User Response: Issue the RESTORE command and then try the command again.

2004-09-12-10.07.59.298834 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbinit Probe:620

Database will come up with hidden buffer pools.
totalBufferPoolPages: 0000 0000 0000 0040
........@
2004-09-12-10.07.59.366280 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL

Starting a full database restore.
Agent PID: 58916
2004-09-12-10.07.59.823955 Instance:siebdev Node:000
PID:78808(db2bm.58916.0 0) TID:1 Appid:none
database utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by the backup image.
2004-09-12-10.11.41.039258 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqleCheckForBackupRestore Probe:10

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBA1".

2004-09-12-10.11.41.081622 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqlePrepareForSerialization Probe:20

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBA1".

Could these be referring to the image copy of the database?
Also, I am wondering if large file enabling is set on the target system.
Nov 12 '05 #3

P: n/a

Have you made a db2ckbkp on the backup files to check them ?

perhaps ,the SQL1119 error comes during the different restore after the
first restore KO.
I usualy stop and restart the instance before try to restore the database.
Sometimes, then the restore stop before the end (on a problem), I drop the
database before trying a new restore (If you don't have the comand
"replace exisiting" in your script)

I see different path before and after the restore
(/db2idx/scioltpt/baseidx/ ->
'/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' ). Have you created
the new entire path before the restore ? Are you restoring with the userid
of the instance ?
"GL" <gl@nospam.net> a écrit dans le message de
news:Xn*************************@216.196.97.131...
"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:
First, thanks...I really appreciate any thoughts you might have.

Do you have another error messages in the db2diag.log ?


Yes, please see below
the answer of the ulimit command : are you using the userid of the
instance owner ?


Yes

? do you have a db2 list tablespaces show detail before the restore ?
Yes, this is the tablespace in question of the database being restored

Tablespace ID = 5
Name = TBS_IDX
Type = Database managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal
Total pages = 1000000
Useable pages = 999808
Used pages = 604864
Free pages = 394944
High water mark (pages) = 910720
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 128
Number of containers = 4
Minimum recovery time = 2004-09-10-12.49.31.000000

do you have a db2 list tablespace containers for x before the restore


Yes
Tablespace Containers for Tablespace 5

Container ID = 0
Name = /db2idx/scioltpt/baseidx/sieb01
_idx.dat
Type = File

Container ID = 1
Name = /db2idx/scioltpt/baseidx/sieb02
_idx.dat
Type = File

Container ID = 2
Name = /db2idx/scioltpt/baseidx/sieb03
_idx.dat
Type = File

Container ID = 3
Name = /db2idx/scioltpt/baseidx/sieb04
_idx.dat
Type = File

This is the way the containers are defined in the restore script

set tablespace containers for 5 using
(File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
DB20000I The SET TABLESPACE CONTAINERS command completed successfully.

here are the entries from the db2diag.log when the redirected restore
script is started. I don't know if the unexpected end of file is typical
of entries for a redirected restore.

2004-09-12-10.07.59.075466 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbReadBufferPoolTable Probe:905

DIA8506C Unexpected end of file was reached.
ZRC=0x870F0009

Immediately after that entry, I get many, many repeated entries of
ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is most
definitely terminated before the restore..to the point where I have been
restarting db2 between runs, so I don't understand this message.

SQL1119N A connection to or activation of database "<name>" cannot be
made because a previous restore is incomplete.

Explanation: The database is in an inconsistent state because a system
error occurred during a restore function.

No connection was made.

Federated system users: this situation can be detected by the data
source.

User Response: Issue the RESTORE command and then try the command again.

2004-09-12-10.07.59.298834 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbinit Probe:620

Database will come up with hidden buffer pools.
totalBufferPoolPages: 0000 0000 0000 0040
.......@
2004-09-12-10.07.59.366280 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL

Starting a full database restore.
Agent PID: 58916
2004-09-12-10.07.59.823955 Instance:siebdev Node:000
PID:78808(db2bm.58916.0 0) TID:1 Appid:none
database utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by the backup image.
2004-09-12-10.11.41.039258 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqleCheckForBackupRestore Probe:10

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBA1".

2004-09-12-10.11.41.081622 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqlePrepareForSerialization Probe:20

DIA0001E An internal error occurred. Report the following error code :
"ZRC=0xFFFFFBA1".

Could these be referring to the image copy of the database?
Also, I am wondering if large file enabling is set on the target system.

Nov 12 '05 #4

P: n/a
GL
Yes the target system has a different file structure but the paths and
permissions have all been validated.

I am restoring with the user id of the target (into) instance owner.

I did drop the db as there is no replace existing in the script.

I will check the backup files in the AM

Thanks again
Gerry

"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:

Have you made a db2ckbkp on the backup files to check them ?

perhaps ,the SQL1119 error comes during the different restore after
the first restore KO.
I usualy stop and restart the instance before try to restore the
database. Sometimes, then the restore stop before the end (on a
problem), I drop the database before trying a new restore (If you
don't have the comand "replace exisiting" in your script)

I see different path before and after the restore
(/db2idx/scioltpt/baseidx/ ->
'/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' ). Have you
created the new entire path before the restore ? Are you restoring
with the userid of the instance ?
"GL" <gl@nospam.net> a écrit dans le message de
news:Xn*************************@216.196.97.131...
"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:
First, thanks...I really appreciate any thoughts you might have.

> Do you have another error messages in the db2diag.log ?


Yes, please see below
> the answer of the ulimit command : are you using the userid of the
> instance owner ?


Yes

? do you have a db2 list tablespaces show detail before the restore ?
Yes, this is the tablespace in question of the database being
restored

Tablespace ID = 5
Name = TBS_IDX
Type = Database managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal
Total pages = 1000000
Useable pages = 999808
Used pages = 604864
Free pages = 394944
High water mark (pages) = 910720
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 128
Number of containers = 4
Minimum recovery time = 2004-09-10-12.49.31.000000

> do you have a db2 list tablespace containers for x before the
> restore


Yes
Tablespace Containers for Tablespace 5

Container ID = 0
Name =
/db2idx/scioltpt/baseidx/sieb01
_idx.dat
Type = File

Container ID = 1
Name =
/db2idx/scioltpt/baseidx/sieb02
_idx.dat
Type = File

Container ID = 2
Name =
/db2idx/scioltpt/baseidx/sieb03
_idx.dat
Type = File

Container ID = 3
Name =
/db2idx/scioltpt/baseidx/sieb04
_idx.dat
Type = File

This is the way the containers are defined in the restore script

set tablespace containers for 5 using
(File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
DB20000I The SET TABLESPACE CONTAINERS command completed
successfully.

here are the entries from the db2diag.log when the redirected restore
script is started. I don't know if the unexpected end of file is
typical of entries for a redirected restore.

2004-09-12-10.07.59.075466 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbReadBufferPoolTable Probe:905

DIA8506C Unexpected end of file was reached.
ZRC=0x870F0009

Immediately after that entry, I get many, many repeated entries of
ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
most definitely terminated before the restore..to the point where I
have been restarting db2 between runs, so I don't understand this
message.

SQL1119N A connection to or activation of database "<name>" cannot be
made because a previous restore is incomplete.

Explanation: The database is in an inconsistent state because a
system error occurred during a restore function.

No connection was made.

Federated system users: this situation can be detected by the data
source.

User Response: Issue the RESTORE command and then try the command
again.

2004-09-12-10.07.59.298834 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbinit Probe:620

Database will come up with hidden buffer pools.
totalBufferPoolPages: 0000 0000 0000 0040
.......@
2004-09-12-10.07.59.366280 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL

Starting a full database restore.
Agent PID: 58916
2004-09-12-10.07.59.823955 Instance:siebdev Node:000
PID:78808(db2bm.58916.0 0) TID:1 Appid:none
database utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by the backup image.
2004-09-12-10.11.41.039258 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqleCheckForBackupRestore Probe:10

DIA0001E An internal error occurred. Report the following error code
: "ZRC=0xFFFFFBA1".

2004-09-12-10.11.41.081622 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqlePrepareForSerialization Probe:20

DIA0001E An internal error occurred. Report the following error code
: "ZRC=0xFFFFFBA1".

Could these be referring to the image copy of the database?
Also, I am wondering if large file enabling is set on the target
system.



Nov 12 '05 #5

P: n/a
GL
Problem is solved. Turns out that deep within the bowels of the diaglog
there were actually a few error messages that were useful. Sizing was based
on an inacurate list tablespaces.
Thanks


Nov 12 '05 #6

P: n/a
Hey GL, What's going on with your redirect restore problem? I am
meeting the same problem and my tablespaces is 64GB 4k page size and I
can't even extend this tablespace.

GL <gl@nospam.net> wrote in message news:<Xn*************************@216.196.97.131>. ..
Yes the target system has a different file structure but the paths and
permissions have all been validated.

I am restoring with the user id of the target (into) instance owner.

I did drop the db as there is no replace existing in the script.

I will check the backup files in the AM

Thanks again
Gerry

"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:

Have you made a db2ckbkp on the backup files to check them ?

perhaps ,the SQL1119 error comes during the different restore after
the first restore KO.
I usualy stop and restart the instance before try to restore the
database. Sometimes, then the restore stop before the end (on a
problem), I drop the database before trying a new restore (If you
don't have the comand "replace exisiting" in your script)

I see different path before and after the restore
(/db2idx/scioltpt/baseidx/ ->
'/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' ). Have you
created the new entire path before the restore ? Are you restoring
with the userid of the instance ?
"GL" <gl@nospam.net> a écrit dans le message de
news:Xn*************************@216.196.97.131...
"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:
First, thanks...I really appreciate any thoughts you might have.
> Do you have another error messages in the db2diag.log ?

Yes, please see below

> the answer of the ulimit command : are you using the userid of the
> instance owner ?

Yes

? do you have a db2 list tablespaces show detail before the restore ?
Yes, this is the tablespace in question of the database being
restored

Tablespace ID = 5
Name = TBS_IDX
Type = Database managed space
Contents = Any data
State = 0x0000
Detailed explanation:
Normal
Total pages = 1000000
Useable pages = 999808
Used pages = 604864
Free pages = 394944
High water mark (pages) = 910720
Page size (bytes) = 4096
Extent size (pages) = 32
Prefetch size (pages) = 128
Number of containers = 4
Minimum recovery time = 2004-09-10-12.49.31.000000
> do you have a db2 list tablespace containers for x before the
> restore

Yes
Tablespace Containers for Tablespace 5

Container ID = 0
Name =
/db2idx/scioltpt/baseidx/sieb01
_idx.dat
Type = File

Container ID = 1
Name =
/db2idx/scioltpt/baseidx/sieb02
_idx.dat
Type = File

Container ID = 2
Name =
/db2idx/scioltpt/baseidx/sieb03
_idx.dat
Type = File

Container ID = 3
Name =
/db2idx/scioltpt/baseidx/sieb04
_idx.dat
Type = File

This is the way the containers are defined in the restore script

set tablespace containers for 5 using
(File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
DB20000I The SET TABLESPACE CONTAINERS command completed
successfully.

here are the entries from the db2diag.log when the redirected restore
script is started. I don't know if the unexpected end of file is
typical of entries for a redirected restore.

2004-09-12-10.07.59.075466 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbReadBufferPoolTable Probe:905

DIA8506C Unexpected end of file was reached.
ZRC=0x870F0009

Immediately after that entry, I get many, many repeated entries of
ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
most definitely terminated before the restore..to the point where I
have been restarting db2 between runs, so I don't understand this
message.

SQL1119N A connection to or activation of database "<name>" cannot be
made because a previous restore is incomplete.

Explanation: The database is in an inconsistent state because a
system error occurred during a restore function.

No connection was made.

Federated system users: this situation can be detected by the data
source.

User Response: Issue the RESTORE command and then try the command
again.

2004-09-12-10.07.59.298834 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
buffer pool services sqlbinit Probe:620

Database will come up with hidden buffer pools.
totalBufferPoolPages: 0000 0000 0000 0040
.......@
2004-09-12-10.07.59.366280 Instance:siebdev Node:000
PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.00EB32140759
database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL

Starting a full database restore.
Agent PID: 58916
2004-09-12-10.07.59.823955 Instance:siebdev Node:000
PID:78808(db2bm.58916.0 0) TID:1 Appid:none
database utilities sqludProcessHistoryFile Probe:3

An empty database history has been detected.
The database history will be overwritten by the backup image.
2004-09-12-10.11.41.039258 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqleCheckForBackupRestore Probe:10

DIA0001E An internal error occurred. Report the following error code
: "ZRC=0xFFFFFBA1".

2004-09-12-10.11.41.081622 Instance:siebdev Node:000
PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
*LOCAL.siebdev.040912141141
base sys utilities sqlePrepareForSerialization Probe:20

DIA0001E An internal error occurred. Report the following error code
: "ZRC=0xFFFFFBA1".

Could these be referring to the image copy of the database?
Also, I am wondering if large file enabling is set on the target
system.


Nov 12 '05 #7

P: n/a
good for you. I also solved my problem because of sizing. 16
containers with 64GB, it is just 100 usable pages less than original.
change back to 8 containers, everything is okay.
GL <gl@nospam.net> wrote in message news:<Xn*************************@216.196.97.131>. ..
Problem is solved. Turns out that deep within the bowels of the diaglog
there were actually a few error messages that were useful. Sizing was based
on an inacurate list tablespaces.
Thanks

Nov 12 '05 #8

P: n/a

If I am not mistaken the limit filesize for 4k pages is 64GB. To solve this
you could use an 8k page tablespace witch could grow to 128 GB (you would
also need to create an 8k page buffer pool and temporary tablespace).

If you go with 8k pages tablespace make sure that the operating system /file
system is supporting file greater than 64GB ... if not build a tablespace
with more smaller file.
"duoduo" <du*********@gmail.com> wrote in message
news:d3**************************@posting.google.c om...
Hey GL, What's going on with your redirect restore problem? I am
meeting the same problem and my tablespaces is 64GB 4k page size and I
can't even extend this tablespace.

GL <gl@nospam.net> wrote in message
news:<Xn*************************@216.196.97.131>. ..
Yes the target system has a different file structure but the paths and
permissions have all been validated.

I am restoring with the user id of the target (into) instance owner.

I did drop the db as there is no replace existing in the script.

I will check the backup files in the AM

Thanks again
Gerry

"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:
>
> Have you made a db2ckbkp on the backup files to check them ?
>
> perhaps ,the SQL1119 error comes during the different restore after
> the first restore KO.
> I usualy stop and restart the instance before try to restore the
> database. Sometimes, then the restore stop before the end (on a
> problem), I drop the database before trying a new restore (If you
> don't have the comand "replace exisiting" in your script)
>
> I see different path before and after the restore
> (/db2idx/scioltpt/baseidx/ ->
> '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' ). Have you
> created the new entire path before the restore ? Are you restoring
> with the userid of the instance ?
>
>
> "GL" <gl@nospam.net> a écrit dans le message de
> news:Xn*************************@216.196.97.131...
>> "zeb nest" <ka******@tiscali.fr> wrote in
>> news:ci**********@news.tiscali.fr:
>>
>>
>> First, thanks...I really appreciate any thoughts you might have.
>>
>>
>> > Do you have another error messages in the db2diag.log ?
>>
>> Yes, please see below
>>
>> > the answer of the ulimit command : are you using the userid of the
>> > instance owner ?
>>
>> Yes
>>
>>
>>
>> ? do you have a db2 list tablespaces show detail before the restore ?
>>
>>
>> Yes, this is the tablespace in question of the database being
>> restored
>>
>> Tablespace ID = 5
>> Name = TBS_IDX
>> Type = Database managed space
>> Contents = Any data
>> State = 0x0000
>> Detailed explanation:
>> Normal
>> Total pages = 1000000
>> Useable pages = 999808
>> Used pages = 604864
>> Free pages = 394944
>> High water mark (pages) = 910720
>> Page size (bytes) = 4096
>> Extent size (pages) = 32
>> Prefetch size (pages) = 128
>> Number of containers = 4
>> Minimum recovery time = 2004-09-10-12.49.31.000000
>>
>>
>> > do you have a db2 list tablespace containers for x before the
>> > restore
>>
>> Yes
>> Tablespace Containers for Tablespace 5
>>
>> Container ID = 0
>> Name =
>> /db2idx/scioltpt/baseidx/sieb01
>> _idx.dat
>> Type = File
>>
>> Container ID = 1
>> Name =
>> /db2idx/scioltpt/baseidx/sieb02
>> _idx.dat
>> Type = File
>>
>> Container ID = 2
>> Name =
>> /db2idx/scioltpt/baseidx/sieb03
>> _idx.dat
>> Type = File
>>
>> Container ID = 3
>> Name =
>> /db2idx/scioltpt/baseidx/sieb04
>> _idx.dat
>> Type = File
>>
>> This is the way the containers are defined in the restore script
>>
>> set tablespace containers for 5 using
>> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
>> DB20000I The SET TABLESPACE CONTAINERS command completed
>> successfully.
>>
>> here are the entries from the db2diag.log when the redirected restore
>> script is started. I don't know if the unexpected end of file is
>> typical of entries for a redirected restore.
>>
>> 2004-09-12-10.07.59.075466 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> buffer pool services sqlbReadBufferPoolTable Probe:905
>>
>> DIA8506C Unexpected end of file was reached.
>> ZRC=0x870F0009
>>
>> Immediately after that entry, I get many, many repeated entries of
>> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
>> most definitely terminated before the restore..to the point where I
>> have been restarting db2 between runs, so I don't understand this
>> message.
>>
>> SQL1119N A connection to or activation of database "<name>" cannot be
>> made because a previous restore is incomplete.
>>
>> Explanation: The database is in an inconsistent state because a
>> system error occurred during a restore function.
>>
>> No connection was made.
>>
>> Federated system users: this situation can be detected by the data
>> source.
>>
>> User Response: Issue the RESTORE command and then try the command
>> again.
>>
>> 2004-09-12-10.07.59.298834 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> buffer pool services sqlbinit Probe:620
>>
>> Database will come up with hidden buffer pools.
>> totalBufferPoolPages: 0000 0000 0000 0040
>> .......@
>>
>>
>> 2004-09-12-10.07.59.366280 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL
>>
>> Starting a full database restore.
>> Agent PID: 58916
>>
>>
>> 2004-09-12-10.07.59.823955 Instance:siebdev Node:000
>> PID:78808(db2bm.58916.0 0) TID:1 Appid:none
>> database utilities sqludProcessHistoryFile Probe:3
>>
>> An empty database history has been detected.
>> The database history will be overwritten by the backup image.
>>
>>
>> 2004-09-12-10.11.41.039258 Instance:siebdev Node:000
>> PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.040912141141
>> base sys utilities sqleCheckForBackupRestore Probe:10
>>
>> DIA0001E An internal error occurred. Report the following error code
>> : "ZRC=0xFFFFFBA1".
>>
>> 2004-09-12-10.11.41.081622 Instance:siebdev Node:000
>> PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.040912141141
>> base sys utilities sqlePrepareForSerialization Probe:20
>>
>> DIA0001E An internal error occurred. Report the following error code
>> : "ZRC=0xFFFFFBA1".
>>
>> Could these be referring to the image copy of the database?
>> Also, I am wondering if large file enabling is set on the target
>> system.
>
>

Nov 12 '05 #9

P: n/a
Dany, in my case, I did the redirect restore and changed the 64GB
tablespace containers from 8 * 8GB to 16 * 4GB. Unfortunately, the
original tablespace had the 16383872 pages "High Water Mark" same as
"Usable Pages", once I changed the number of containers, my "Usable
Pages" had droped to 16383744, just 128 pages short. I was so sad that
the "set container" did not tell me the message until 11 hours later I
ran "restore continue". IBM should fix this and doesn't waste our
time.
"Dany" <da******@videotron.ca> wrote in message news:<ci*********@news1.stadia.fi>...
If I am not mistaken the limit filesize for 4k pages is 64GB. To solve this
you could use an 8k page tablespace witch could grow to 128 GB (you would
also need to create an 8k page buffer pool and temporary tablespace).

If you go with 8k pages tablespace make sure that the operating system /file
system is supporting file greater than 64GB ... if not build a tablespace
with more smaller file.
"duoduo" <du*********@gmail.com> wrote in message
news:d3**************************@posting.google.c om...
Hey GL, What's going on with your redirect restore problem? I am
meeting the same problem and my tablespaces is 64GB 4k page size and I
can't even extend this tablespace.

GL <gl@nospam.net> wrote in message
news:<Xn*************************@216.196.97.131>. ..
Yes the target system has a different file structure but the paths and
permissions have all been validated.

I am restoring with the user id of the target (into) instance owner.

I did drop the db as there is no replace existing in the script.

I will check the backup files in the AM

Thanks again
Gerry

"zeb nest" <ka******@tiscali.fr> wrote in
news:ci**********@news.tiscali.fr:

>
> Have you made a db2ckbkp on the backup files to check them ?
>
> perhaps ,the SQL1119 error comes during the different restore after
> the first restore KO.
> I usualy stop and restart the instance before try to restore the
> database. Sometimes, then the restore stop before the end (on a
> problem), I drop the database before trying a new restore (If you
> don't have the comand "replace exisiting" in your script)
>
> I see different path before and after the restore
> (/db2idx/scioltpt/baseidx/ ->
> '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' ). Have you
> created the new entire path before the restore ? Are you restoring
> with the userid of the instance ?
>
>
> "GL" <gl@nospam.net> a écrit dans le message de
> news:Xn*************************@216.196.97.131...
>> "zeb nest" <ka******@tiscali.fr> wrote in
>> news:ci**********@news.tiscali.fr:
>>
>>
>> First, thanks...I really appreciate any thoughts you might have.
>>
>>
>> > Do you have another error messages in the db2diag.log ?
>>
>> Yes, please see below
>>
>> > the answer of the ulimit command : are you using the userid of the
>> > instance owner ?
>>
>> Yes
>>
>>
>>
>> ? do you have a db2 list tablespaces show detail before the restore ?
>>
>>
>> Yes, this is the tablespace in question of the database being
>> restored
>>
>> Tablespace ID = 5
>> Name = TBS_IDX
>> Type = Database managed space
>> Contents = Any data
>> State = 0x0000
>> Detailed explanation:
>> Normal
>> Total pages = 1000000
>> Useable pages = 999808
>> Used pages = 604864
>> Free pages = 394944
>> High water mark (pages) = 910720
>> Page size (bytes) = 4096
>> Extent size (pages) = 32
>> Prefetch size (pages) = 128
>> Number of containers = 4
>> Minimum recovery time = 2004-09-10-12.49.31.000000
>>
>>
>> > do you have a db2 list tablespace containers for x before the
>> > restore
>>
>> Yes
>> Tablespace Containers for Tablespace 5
>>
>> Container ID = 0
>> Name =
>> /db2idx/scioltpt/baseidx/sieb01
>> _idx.dat
>> Type = File
>>
>> Container ID = 1
>> Name =
>> /db2idx/scioltpt/baseidx/sieb02
>> _idx.dat
>> Type = File
>>
>> Container ID = 2
>> Name =
>> /db2idx/scioltpt/baseidx/sieb03
>> _idx.dat
>> Type = File
>>
>> Container ID = 3
>> Name =
>> /db2idx/scioltpt/baseidx/sieb04
>> _idx.dat
>> Type = File
>>
>> This is the way the containers are defined in the restore script
>>
>> set tablespace containers for 5 using
>> (File '/siebel/db2/instance/siebdev/idx/siebts01_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts02_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts03_idx4k.dat' 250000,
>> File '/siebel/db2/instance/siebdev/idx/siebts04_idx4k.dat' 250000)
>> DB20000I The SET TABLESPACE CONTAINERS command completed
>> successfully.
>>
>> here are the entries from the db2diag.log when the redirected restore
>> script is started. I don't know if the unexpected end of file is
>> typical of entries for a redirected restore.
>>
>> 2004-09-12-10.07.59.075466 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> buffer pool services sqlbReadBufferPoolTable Probe:905
>>
>> DIA8506C Unexpected end of file was reached.
>> ZRC=0x870F0009
>>
>> Immediately after that entry, I get many, many repeated entries of
>> ZRC=0xFFFFFBA1 This translates to SQL1119 The restore utility is
>> most definitely terminated before the restore..to the point where I
>> have been restarting db2 between runs, so I don't understand this
>> message.
>>
>> SQL1119N A connection to or activation of database "<name>" cannot be
>> made because a previous restore is incomplete.
>>
>> Explanation: The database is in an inconsistent state because a
>> system error occurred during a restore function.
>>
>> No connection was made.
>>
>> Federated system users: this situation can be detected by the data
>> source.
>>
>> User Response: Issue the RESTORE command and then try the command
>> again.
>>
>> 2004-09-12-10.07.59.298834 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> buffer pool services sqlbinit Probe:620
>>
>> Database will come up with hidden buffer pools.
>> totalBufferPoolPages: 0000 0000 0000 0040
>> .......@
>>
>>
>> 2004-09-12-10.07.59.366280 Instance:siebdev Node:000
>> PID:58916(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.00EB32140759
>> database utilities sqludPrintStartingMsg Probe:1 Database:SIEBEL
>>
>> Starting a full database restore.
>> Agent PID: 58916
>>
>>
>> 2004-09-12-10.07.59.823955 Instance:siebdev Node:000
>> PID:78808(db2bm.58916.0 0) TID:1 Appid:none
>> database utilities sqludProcessHistoryFile Probe:3
>>
>> An empty database history has been detected.
>> The database history will be overwritten by the backup image.
>>
>>
>> 2004-09-12-10.11.41.039258 Instance:siebdev Node:000
>> PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.040912141141
>> base sys utilities sqleCheckForBackupRestore Probe:10
>>
>> DIA0001E An internal error occurred. Report the following error code
>> : "ZRC=0xFFFFFBA1".
>>
>> 2004-09-12-10.11.41.081622 Instance:siebdev Node:000
>> PID:21150(db2agent (SIEBEL) 0) TID:1 Appid:
>> *LOCAL.siebdev.040912141141
>> base sys utilities sqlePrepareForSerialization Probe:20
>>
>> DIA0001E An internal error occurred. Report the following error code
>> : "ZRC=0xFFFFFBA1".
>>
>> Could these be referring to the image copy of the database?
>> Also, I am wondering if large file enabling is set on the target
>> system.
>
>

Nov 12 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.