Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / June 2006

Tip: Looking for answers? Try searching our database.

Moving from windows to AIX

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
DMina@laiki.com - 01 Jun 2006 16:09 GMT
Hello people,

I have this requirement to move a DB2 V8 database from Windows 2000 to
AIX V5.3.
I have managed to do that for a small simple database using
export/import and db2look.
Now i have a database which has BLOB, CLOB, CHAR FOR BIT DATA, VARCHAR
FOR BIT DATA, or LONG VARCHAR FOR BIT DATA data types
and i found out that you cannot export/import these data types.

Do you know how else can i move these to the AIX server?

Thank you
m - 01 Jun 2006 16:54 GMT
> Hello people,
>
[quoted text clipped - 9 lines]
>
> Thank you

Take a look at the db2move utility
Mark A - 02 Jun 2006 00:13 GMT
> Hello people,
>
[quoted text clipped - 9 lines]
>
> Thank you

You can export and load those data types, but you have to use special
modifiers in the export and load commands. These are documented in the
manual.

But as mentioned by someone else, using the db2move command is much easier
(it uses export and load to do the work, but generates the correct syntax
automatically).
MY - 02 Jun 2006 13:43 GMT
I just went thru something similar.

During the export phase you will need to specify the paths where
db2move EXPORT will place your large data. Keep in mind that you can
put only 26000 files in each directory so you'd better add up all your
LOBs and create as many dirs as you need to store them. (num_dirs=
sum_of_blobs/26000 + 1)

Be careful if you have IDENTITY columns. In this case db2move LOAD or
db2move IMPORT might not work.

You may have to "db2 import  ... modified by IDENTITY OVERRIDE ... "
for each exported table

In order for this to work you will have to create your database on the
destination server (see db2look)

Depending on the relations some of your tables will be in CHECK PENDING
STATE (you can check with 'db2 select name,status from sysibm.systables
where creator=YOUR_INSTANCE' and look for a 'C' in the status column.
To make those tables useable you will have to "SET INTEGRITY" to either
"IMMEDIATE CHECKED" or "NORMAL"

> > Hello people,
> >
[quoted text clipped - 17 lines]
> (it uses export and load to do the work, but generates the correct syntax
> automatically).
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.