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.
SQL2038N A database system error "-5130" occurred during processing
We are restoring one db to another db and we get:
SQL2038N A database system error "-5130" occurred during processing.
I found a SQL2038N which says "Examine the error code in the message for more information" but can not find description of system error code -5130 anywhere (neither in pdf docs, nor in v8.2 Information Center on-line).
Please advise
Happy New Year everyone!
__________________
DB2 v9.5 ESE on AIX v6.1/ v9./10 on z/OS
the error is sql5130n
can not reset a db cfg parameter
have seen other posts with same message and one indicated
..In short, I was trying to restore a 64bit backup into a 32bit environment.
maybe also for your case...
have a look at diag log to see the error
__________________
Best Regards, Guy Przytula
Database Software Consultant
DB2 UDB LUW Certified V7-V8-V9-V9.7 DB Admin - Dprop..
Information Server Datastage Certified http://www.infocura.be
the error is sql5130n
can not reset a db cfg parameter
have seen other posts with same message and one indicated
..In short, I was trying to restore a 64bit backup into a 32bit environment.
maybe also for your case...
have a look at diag log to see the error
You are right - this is our case (restoring a 64bit backup into a 32bit). Nothing would say that this is where the problem is.
Another thing - documentation says that we CAN do this: You can restore databases created on DB2 Version 8 AIX, HP-UX, or the Solaris Operating Environment 9 platforms, in 32-bit or 64-bit, to DB2 Version 8 AIX, HP-UX, or Solaris Operating Environment platforms 9 (32-bit or 64-bit).
__________________
DB2 v9.5 ESE on AIX v6.1/ v9./10 on z/OS
Acceptable value ranges of some DBM and DB parameters in 64-bit instances differ from those in 32-bit instances. For example, maximum PKGCASHESIZE is 128000 pages in a 32-bit database and 512K pages in a 64-bit database.
The restore attempts to set those DB parameters in the target database to the source values and fails. I believe MarcusA on this board had a similar issue a while back; not sure if he was able to resolve it.
I'm thinking that may be if you create an empty target database first and perform individual tablespace restore it will not attempt to overwrite the database configuration parameters.
I believe that I updated the db cfg after the restore command, but before the rollforward, and then the rollforward worked. My problem had something to do with one of the path statements (log, archive, etc).
__________________
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390