Home   |   Register   |   Rules   |   Calendar   |   Get Daily   |     |  
 


If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Problem restoring DB

Reply
Page 1 of 2 1 2
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-20-08, 14:22
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
Problem restoring DB
We have our production system which is DB2 9.5 ESE FP 2a on RedHat linux 5.1 64 bit. We backup the database using Veritas Netbackup. We have a requirement that we test the backup images periodically. So we set up a server with 32 bit RedHat linux and installed DB2 Express-C v 9.5 on it. I was able to issue the restore command (redirected) and it processed through the entire image and gave this error:

Code:
SQL5130N  The value specified for the configuration parameter "maxfilop" is 
not in the valid range of "64" to "30720".
Here are the relevant entries in the db2diag.log file:

Code:
2008-11-20-10.33.45.207355-300 E81321G461         LEVEL: Warning
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludValidatePlatform, probe:620
MESSAGE : Performing a Cross Platform Restore.

2008-11-20-10.33.45.207763-300 E81783G489         LEVEL: Info
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludPrintStartingMsg, probe:1292
DATA #1 : <preformatted>
Starting a full database restore.
Agent EDU ID: 674

2008-11-20-10.33.46.328836-300 I82273G445         LEVEL: Warning
PID     : 3492                 TID  : 2034232208  PROC : db2sysc
INSTANCE: db2inst1             NODE : 000
EDUID   : 934                  EDUNAME: db2bm.674.0 (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludProcessHistoryFile, probe:2871
DATA #1 : String, 107 bytes
An empty database history has been detected.
The database history will be overwritten by the backup image.

2008-11-20-10.33.46.992140-300 E82719G545         LEVEL: Warning
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludBMResponse, probe:307
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
1277
DATA #2 : Hexdump, 4 bytes
0x7E4BEB1C : FD04 0000                                  ....

2008-11-20-10.33.46.992682-300 E83265G1055        LEVEL: Warning
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludBMResponse, probe:307
MESSAGE : SQL1277W  A redirected restore operation is being performed.  Table 
          space configuration can now be viewed and table spaces that do not 
          use automatic storage can have their containers reconfigured.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: 1277   sqlerrml: 0
 sqlerrmc: 
 sqlerrp : sqludBMR
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 0x00000000
           (4) 0x00000000      (5) 0x00000000      (6) 0x00000000
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)    
           (7)      (8)      (9)      (10)        (11)     
 sqlstate:      

2008-11-20-13.19.14.054873-300 E84321G458         LEVEL: Info
PID     : 3492                 TID  : 947907472   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000
EDUID   : 936                  EDUNAME: db2med.674.0 (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqluReadFromVendorDevice, probe:218
DATA #1 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
Vendor RC=0x00000017=23 -- see DB2 API Guide for meaning.
DATA #2 : signed integer, 4 bytes
16384

2008-11-20-13.19.35.998521-300 I84780G584         LEVEL: Error
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, High Availability Disaster Recovery, hdrSetDbRole, probe:10020
MESSAGE : Failed to update database configuration parameter HADR_DB_ROLE.
DATA #1 : Hexdump, 4 bytes
0x36BF2100 : F6EB FFFF                                  ....

2008-11-20-13.19.36.021041-300 E85365G632         LEVEL: Error
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludProcessDBCfg, probe:539
MESSAGE : SQL5130N  The value specified for the configuration parameter "" is 
          not in the valid range of "" to "".
DATA #1 : String, 71 bytes
Failed to set database configuration parameter HADR_DB_ROLE to standard

2008-11-20-13.19.36.081476-300 E85998G430         LEVEL: Severe
PID     : 3492                 TID  : 918547344   PROC : db2sysc
INSTANCE: db2inst1             NODE : 000         DB   : TEST_ATL
APPHDL  : 0-251                APPID: *LOCAL.db2inst1.081120145708
AUTHID  : DB2INST1
EDUID   : 674                  EDUNAME: db2agent (TEST_ATL)
FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:781
MESSAGE : Restore Terminated.
I thought that restoring from 64 bit to 32 bit was supported.

Any ideas?

Andy
Reply With Quote
  #2 (permalink)  
Old 11-20-08, 14:31
Marcus_A Marcus_A is offline
Registered User
  
Join Date: May 2003
Location: USA
Posts: 5,196
Try to restore the database without rolling forward (and without the "without rolling forward command"). After the restore, lower the db cfg parm mentioned to a value that is supported by a 32-bit database (db2 update db cfg for <db-name> using maxfilop n", and then complete the rollforward operation, and see if that works.
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390
Reply With Quote
  #3 (permalink)  
Old 11-20-08, 15:15
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
It is an online backup and I am not using the "WITHOUT ROLLING FORWARD" clause.

Andy
Reply With Quote
  #4 (permalink)  
Old 11-20-08, 15:54
n_i n_i is offline
:-)
  
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
The maxfilop parameter value ranges are different on 64- and 32-bit systems. If you don't have a valid reason to set it so high on the production system you might as well keep it within the range that's allowed on the test system.

I'm also wondering if you could trick DB2 by doing a redirected restore, but instead of redefining containers update the database configuration while the restore pauses...
Reply With Quote
  #5 (permalink)  
Old 11-20-08, 16:16
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
Quote:
Originally Posted by n_i
The maxfilop parameter value ranges are different on 64- and 32-bit systems. If you don't have a valid reason to set it so high on the production system you might as well keep it within the range that's allowed on the test system.

I'm also wondering if you could trick DB2 by doing a redirected restore, but instead of redefining containers update the database configuration while the restore pauses...
You mean like:

Restore DB mydb ... Redirect ...
SET tablespace containers for ...
SET tablespace containers for ...
SET tablespace containers for ...
...
update db cfg for mydb using maxfilop 64
restore db mydb continue

Andy
Reply With Quote
  #6 (permalink)  
Old 11-20-08, 16:18
n_i n_i is offline
:-)
  
Join Date: Jun 2003
Location: Toronto, Canada
Posts: 4,449
I don't think you even need to set containers. Unless you are actually redirecting, of course.

I haven't tried that, just a guess. The big questions are: 1) whether it pauses before the error and 2) whether it will allow you to change db cfg...
Reply With Quote
  #7 (permalink)  
Old 11-20-08, 16:44
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
I am redirecting. My thoughts are that the DB does not exist before the restore command, so will it exist just before the "restore continue" command?

I will try it tomorrow.

Andy
Reply With Quote
  #8 (permalink)  
Old 11-21-08, 08:45
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
OK, I changed the script to update the db cfg maxfilop parameter before the restore continue command and I got this error:

Code:
SQL1350N The application is not in the correct state to process
          this request.  Reason code="3".
The restore is continuing and will take about 3 hours to complete.

Andy
Reply With Quote
  #9 (permalink)  
Old 09-24-09, 02:55
mahesh_h mahesh_h is offline
Registered User
  
Join Date: Sep 2009
Posts: 5
"SQL5130N The value specified for the configuration parameter "maxfilop" is not in t
I'm getting same problem.
I have taken backup on (64 bit) Linux RHEL 5 with DB2 9.5 version.
I'm trying to restore it on another Linux RHEL (32 bit) with DB2 9.5 version.

The error is - "SQL5130N The value specified for the configuration parameter "maxfilop" is not in the valid range of "64" to "30720"."

I also tried to set the maxfilop to 61440 (compatible to 64 bit machine) using db2 "update database config for <db name> using maxfilop 61440"
Still it does not work.

Is there any solution to this problem?
Reply With Quote
  #10 (permalink)  
Old 09-24-09, 08:19
ARWinner ARWinner is offline
Registered User
  
Join Date: Jan 2003
Posts: 3,575
We solved it by restoring to a 64 bit server. We never could get the 32 bit one to work.

Andy
Reply With Quote
  #11 (permalink)  
Old 09-24-09, 08:21
mahesh_h mahesh_h is offline
Registered User
  
Join Date: Sep 2009
Posts: 5
Backup and restore operations between different operating systems and h/w platforms
This is one of the important link that I found which says - you can not restore data from 64 bit machine into 32 bit machine. Other hardware & endianness configurations are also mentioned there.

IBM DB2 9.5 Information Center for Linux, UNIX, and Windows


Regards,
Mahesh
Reply With Quote
  #12 (permalink)  
Old 09-24-09, 08:21
db2girl db2girl is offline
∞∞∞∞∞∞
  
Join Date: Aug 2008
Location: Toronto, Canada
Posts: 1,816
What is the maxfilop value on source db (64-bit)? If it's higher than 30720, lower it so that it's in range for 32-bit, take a new backup and then try to restore the new image to 64-bit env.

This error can also be due to the following:
IBM JR28336: RESTORE USING A DB2 64BIT BACKUP IMAGE TO A DB2 32BIT ENVIRONMENT FAILS WITH SQL2038 - SQL5130 (HADR_DB_ROLE). - United States

Check if you have messages about failing to update HADR_DB_ROLE in the db2diag.log.
Reply With Quote
  #13 (permalink)  
Old 09-24-09, 08:34
db2girl db2girl is offline
∞∞∞∞∞∞
  
Join Date: Aug 2008
Location: Toronto, Canada
Posts: 1,816
Correction:
...take a new backup and then try to restore the new image to 32-bit env
Reply With Quote
  #14 (permalink)  
Old 09-25-09, 05:34
mahesh_h mahesh_h is offline
Registered User
  
Join Date: Sep 2009
Posts: 5
thanks Bella, your suggestion worked....
Reply With Quote
  #15 (permalink)  
Old 10-27-09, 02:54
mahesh_h mahesh_h is offline
Registered User
  
Join Date: Sep 2009
Posts: 5
Tables are not listed in database, after restoration of the backup data-image
Hi,

I'm trying to restore db2 database on 32-bit machine, for which backup was taken on 64-bit machine.

While taking backup on 64-bit Linux machine, I modified maxfilop to 65 & took backup.

After that, I tried to restore it on 32-bit Linux machine using command - db2 restore db <db_name> from <dir_name> taken at <time_stamp> into <target_db_name> comprlib libdb2compr.so.

Database was restored successfully with message - DB20000I The RESTORE DATABASE command completed successfully.

But, when I connected to restored database & tried to fetch table details using db2 list tables command, it gives me error - SQL0727N An error occurred during implicit system action type "1".Information returned for the error includes SQLCODE "-440", SQLSTATE "42884" and message tokens "REPLACE|FUNCTION". SQLSTATE=56098 .

Can anyone tell me whether restoration of the database is successful or not?
Is there any step, that I forgot while restoring database?

Till now what I found is - you can not restore data on 32-bit machine for which backup is taken on 64-bit machine, while reverse it possible. Which is mentioned at https://publib.boulder.ibm.com/infoc.../c0006237.html

Please help me...
Reply With Quote
Reply
Page 1 of 2 1 2

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 
 
 
Home  |   Register  |   Get New  |   FAQ's  |   Sitemap

Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.