SQL2038N A database system error "-5130" occurred during processing.

[Jurgen Haan]

Hi hi, I'm trying to perform a redirected restore, but I get a nice
error returned. Does anyone have an idea of what the -5130 errorcode means?
db2inst@ELMO:~> db2 restore db efproddb into testprod redirect
SQL1277N Restore has detected that one or more table space containers are
inaccessible, or has set their state to 'storage must be defined'.
DB20000I The RESTORE DATABASE command completed successfully.

db2inst@ELMO:~> db2 set tablespace containers for 11 using \(PATH
\'/data/efproddb/tablespaces/c0001/t0001_04/\'\)
DB20000I The SET TABLESPACE CONTAINERS command completed successfully.

db2inst@ELMO:~> db2 restore db efproddb continue
SQL2038N A database system error "-5130" occurred during processing.
Thanks.

-R-

[Kiran Nair]

I feel the error due to which the resore failed is SQL5130N.
Do you feel there is lots of environment diffrence
SQL5130N The value specified for the configuration parameter
"<parameter>" is not in the valid range of
"<start-of-range>" to "<end-of-range>".

Explanation:

The request is not done because the value of "<parameter>" is not
within the valid range.

User Response:

Ensure that the value specified for "<parameter>" is within the
valid range, then try the request again.

[Jurgen Haan]

Well, no shocking differences.
Both 64bit platforms with 64bit instances. (the platform where the
backup was taken and the platform where the backup is to be restored).

SQL5130N, that's something about messed up parameters? Not a clue where
to look.
Can the error have something to do with the tablespaces that are being
set for the restore?

-R-

Kiran Nair wrote:

I feel the error due to which the resore failed is SQL5130N.
Do you feel there is lots of environment diffrence
SQL5130N The value specified for the configuration parameter
"<parameter>" is not in the valid range of
"<start-of-range>" to "<end-of-range>".

Explanation:

The request is not done because the value of "<parameter>" is not
within the valid range.

User Response:

Ensure that the value specified for "<parameter>" is within the
valid range, then try the request again.

[Kiran Nair]

Jurgen,
Do you find any clues in db2diag.log ?
Jurgen Haan wrote:

Well, no shocking differences.
Both 64bit platforms with 64bit instances. (the platform where the
backup was taken and the platform where the backup is to be restored).

SQL5130N, that's something about messed up parameters? Not a clue where
to look.
Can the error have something to do with the tablespaces that are being
set for the restore?

-R-

Kiran Nair wrote:

I feel the error due to which the resore failed is SQL5130N.
Do you feel there is lots of environment diffrence
SQL5130N The value specified for the configuration parameter
"<parameter>" is not in the valid range of
"<start-of-range>" to "<end-of-range>".

Explanation:

The request is not done because the value of "<parameter>" is not
within the valid range.

User Response:

Ensure that the value specified for "<parameter>" is within the
valid range, then try the request again.

[Jurgen Haan]

Ah... ofcourse.

2006-05-02-09.47.04.134361+120 I21158097G500 LEVEL: Error
PID : 2387 TID : 332215680 PROC : db2agent (TESTPROD)
INSTANCE: db2inst NODE : 000 DB : TESTPROD
APPHDL : 0-758 APPID: *LOCAL.db2inst.060502074346
FUNCTION: DB2 UDB, database utilities, sqludsfp, probe:556
MESSAGE : Failed to set database configuration parameter HDR_DB_ROLE to
standard
DATA #1 : Hexdump, 4 bytes
0xFFFEF6C0 : F6EB FFFF ....

Kiran Nair wrote:

Jurgen,
Do you find any clues in db2diag.log ?
Jurgen Haan wrote:

Well, no shocking differences.
Both 64bit platforms with 64bit instances. (the platform where the
backup was taken and the platform where the backup is to be restored).

SQL5130N, that's something about messed up parameters? Not a clue where
to look.
Can the error have something to do with the tablespaces that are being
set for the restore?

-R-

Kiran Nair wrote:

I feel the error due to which the resore failed is SQL5130N.
Do you feel there is lots of environment diffrence
SQL5130N The value specified for the configuration parameter
"<parameter>" is not in the valid range of
"<start-of-range>" to "<end-of-range>".

Explanation:

The request is not done because the value of "<parameter>" is not
within the valid range.

User Response:

Ensure that the value specified for "<parameter>" is within the
valid range, then try the request again.

[Kiran Nair]

Not sure why its showing HDR_DB_ROLE
As per documentation it should have been HADR_DB_ROLE, which is a
informational parameter showing current role of the database, that is
STANDARD, PRIMARY, or STANDBY...What is its value in datbase at time of
taking backup any idea ?

http://publib.boulder.ibm.com/infoce...n/r0011439.htm

Regards,
Kiran Nair
Jurgen Haan wrote:

Ah... ofcourse.

2006-05-02-09.47.04.134361+120 I21158097G500 LEVEL: Error
PID : 2387 TID : 332215680 PROC : db2agent (TESTPROD)
INSTANCE: db2inst NODE : 000 DB : TESTPROD
APPHDL : 0-758 APPID: *LOCAL.db2inst.060502074346
FUNCTION: DB2 UDB, database utilities, sqludsfp, probe:556
MESSAGE : Failed to set database configuration parameter HDR_DB_ROLE to
standard
DATA #1 : Hexdump, 4 bytes
0xFFFEF6C0 : F6EB FFFF ....

Kiran Nair wrote:

Jurgen,
Do you find any clues in db2diag.log ?
Jurgen Haan wrote:

Well, no shocking differences.
Both 64bit platforms with 64bit instances. (the platform where the
backup was taken and the platform where the backup is to be restored).

SQL5130N, that's something about messed up parameters? Not a clue where
to look.
Can the error have something to do with the tablespaces that are being
set for the restore?

-R-

Kiran Nair wrote:

I feel the error due to which the resore failed is SQL5130N.
Do you feel there is lots of environment diffrence
SQL5130N The value specified for the configuration parameter
"<parameter>" is not in the valid range of
"<start-of-range>" to "<end-of-range>".

Explanation:

The request is not done because the value of "<parameter>" is not
within the valid range.

User Response:

Ensure that the value specified for "<parameter>" is within the
valid range, then try the request again.

[Jurgen Haan]

Stupid old me...

The restore was done in a newly created instances especially for that
restore, instead of the regular one.
This instance was not created with the -w64 parameter.
In short, I was trying to restore a 64bit backup into a 32bit environment.

D'oh!

-R-