We are moving from 7.2 to 9.x. So I'm trying to restore a 7.2 backup
to a 8.1 and I'm getting a sqlcode 2038N with system error of 1062. We
have to got 8.x then move 9.x.
Here is the command that I'm using from the command line.
DB2 RESTORE DATABASE DBFDS2 FROM E:\\Db2back\\Fdssrv1\\DBFDS.0\\DB2\
\NODE0000\\CATN0000\\ TAKEN AT 20080108204504 WITH 1 BUFFERS BUFFER
1024 PARALLELISM 1 WITHOUT PROMPTING;
Any help would be appreciated.
John
Jeroen van den Broek - 15 Jan 2008 17:45 GMT
On Jan 15, 4:12 pm, jfitz...@gmail.com wrote:
> We are moving from 7.2 to 9.x. So I'm trying to restore a 7.2 backup
> to a 8.1 and I'm getting a sqlcode 2038N with system error of 1062. We
[quoted text clipped - 9 lines]
>
> John
Probably something wrong with your PATH.
Is something written to the db2diag.log ?
--
Jeroen
Ian - 16 Jan 2008 18:15 GMT
> We are moving from 7.2 to 9.x. So I'm trying to restore a 7.2 backup
> to a 8.1 and I'm getting a sqlcode 2038N with system error of 1062. We
[quoted text clipped - 5 lines]
> \NODE0000\\CATN0000\\ TAKEN AT 20080108204504 WITH 1 BUFFERS BUFFER
> 1024 PARALLELISM 1 WITHOUT PROMPTING;
That's an invalid path. You would specify:
DB2 RESTORE DATABASE DBFDS2 FROM E:\\Db2back\\Fdssrv1
TAKEN AT 20080108204504
WITHOUT PROMPTING;
(I also removed the buffers/parallelism options because DB2 will
determine these automatically for you and make "optimal" choices).
jfitz261@gmail.com - 17 Jan 2008 17:12 GMT
> jfitz...@gmail.com wrote:
> > We are moving from 7.2 to 9.x. So I'm trying to restore a 7.2 backup
[quoted text clipped - 15 lines]
> (I also removed the buffers/parallelism options because DB2 will
> determine these automatically for you and make "optimal" choices).
Is there a way to change the code page from 1252 to 437 so I can
restore an backup that the machine was configured to use a codepage of
437.
Thanks,
John
Ian - 17 Jan 2008 18:51 GMT
> Is there a way to change the code page from 1252 to 437 so I can
> restore an backup that the machine was configured to use a codepage of
> 437.
No. The database codepage is selected at CREATE DATABASE, and can't be
modified. The only option is to unload all data, create a database with
the new code page and load all data back.
jfitz261@gmail.com - 24 Jan 2008 13:03 GMT
> jfitz...@gmail.com wrote:
>
[quoted text clipped - 5 lines]
> modified. The only option is to unload all data, create a database with
> the new code page and load all data back.
We thought that the codepage was gotten from the Windows environment
but it gets it from the DB2 environment using db2set.
Thanks for your help,
John
Ian - 24 Jan 2008 20:47 GMT
>> jfitz...@gmail.com wrote:
>>
[quoted text clipped - 7 lines]
> We thought that the codepage was gotten from the Windows environment
> but it gets it from the DB2 environment using db2set.
There is a difference between the *database* code page (i.e. how DB2
stores your data internally) and the *client* code page (i.e. the code
page of the client application).
The DB2CODEPAGE variable controls the client code page only. As I said
before, the database code page is determined when the database is
created.
FYI, DB2 performs code page conversion between the client and the
server code page. This may result in garbage, if the code points
don't match properly.