By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,609 Members | 2,246 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,609 IT Pros & Developers. It's quick & easy.

Moving database to a larger hard disk partition

P: n/a
Good morning,

Database PRODUCTION was created on a system mamanged tablespace on
drive c:\
Now drive c:\ is running out of space and I need to move PRODUCTION to
the larger drive d:\ on the same machine.
PRODUCTION is currently accessed by 50 clients running many
applications and by some REXX scripts running on the same server
machine on a timely basis.
I do not want to modify in any way clients configuration, applications,
nor server REXX scripts.

Please let me know if the following procedure is the correct one:

1) Disconnect both client and server applications
2) Backup PRODUCTION
3) Drop PRODUCTION
4) Restore PRODUCTION into dirve d:\
5) Leave totally untoched all CAE configurations and REXX scripts.

Moroever, what if I skip to DROP PRODUCTION before restoring it ?
Will I be forced to change database name while restoring it and
recataloging all CAEs to address the new name ?

Thank you for your help.

Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
That will work.

I don't think you can restore to another location without dropping
(uncataloguing) the database first. You definitely can't restore to the same
name, so that would hardly be transparent. The physical disk issues are not
the problem.

BTW, next time, don't use the boot drive to hold a database. Other drives
can be enlarged, but not the boot drive.

"Massimiliano Campagnoli" <ma**@paoloastori.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Good morning,

Database PRODUCTION was created on a system mamanged tablespace on
drive c:\
Now drive c:\ is running out of space and I need to move PRODUCTION to
the larger drive d:\ on the same machine.
PRODUCTION is currently accessed by 50 clients running many
applications and by some REXX scripts running on the same server
machine on a timely basis.
I do not want to modify in any way clients configuration, applications,
nor server REXX scripts.

Please let me know if the following procedure is the correct one:

1) Disconnect both client and server applications
2) Backup PRODUCTION
3) Drop PRODUCTION
4) Restore PRODUCTION into dirve d:\
5) Leave totally untoched all CAE configurations and REXX scripts.

Moroever, what if I skip to DROP PRODUCTION before restoring it ?
Will I be forced to change database name while restoring it and
recataloging all CAEs to address the new name ?

Thank you for your help.

Nov 12 '05 #2

P: n/a
Do a DB2 ? RESTORE, it shows:

RESTORE DATABASE source-database-alias { restore-options | CONTINUE |
ABORT }

restore-options:
[USER username [USING password]] [TABLESPACE [ONLINE] |
TABLESPACE (tblspace-name [ {,tblspace-name} ... ]) [ONLINE] |
HISTORY FILE [ONLINE] | LOGS [ONLINE] | COMPRESSION LIBRARY [ONLINE]]
[INCREMENTAL [AUTOMATIC | ABORT]] [USE {TSM | XBSA} [OPEN num-sess
SESSIONS]
[OPTIONS {options-string | options-filename}] |
FROM dir/dev [{,dir/dev} ... ] | LOAD shared-lib [OPEN num-sess SESSIONS]
[OPTIONS {options-string | options-filename}]] [TAKEN AT date-time]
[TO target-directory] [INTO target-database-alias] [LOGTARGET directory]
[NEWLOGPATH directory] [WITH num-buff BUFFERS] [BUFFER buffer-size]
[DLREPORT file-name] [REPLACE HISTORY FILE] [REPLACE EXISTING] [REDIRECT]
[PARALLELISM n] [COMPRLIB lib-name] [COMPROPTS options-string]
[WITHOUT ROLLING FORWARD] [WITHOUT DATALINK] [WITHOUT PROMPTING]

This shows you can specify a new path for the db: TO target-directory. Also
use REPLACE EXISTING
The db has unique seed number that will show the restore that you are
bringing back the same db but to a new location. It will build the new
path.
The current path is C:\instname\node0000\SQL0000n
The new path will be: D:\instname\node0000\SQL0000n
The db diretories (system and local) will be updated also to show the new
location.

The physical location of the db is never known to the clients. They connect
to a db name which takes them to the node/server. The server's system
database directory identifies the db as a local db and the server's local db
directory identifies the actual path to the db.

The REXX scripts will have to modofied for each of their code lines showing
C:\
There's no facility for the script to know that the db has moved to a new
drive.

HTH, Pierre.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Massimiliano Campagnoli" <ma**@paoloastori.com> a écrit dans le message de
news: 11**********************@f14g2000cwb.googlegroups. com...
Good morning,

Database PRODUCTION was created on a system mamanged tablespace on
drive c:\
Now drive c:\ is running out of space and I need to move PRODUCTION to
the larger drive d:\ on the same machine.
PRODUCTION is currently accessed by 50 clients running many
applications and by some REXX scripts running on the same server
machine on a timely basis.
I do not want to modify in any way clients configuration, applications,
nor server REXX scripts.

Please let me know if the following procedure is the correct one:

1) Disconnect both client and server applications
2) Backup PRODUCTION
3) Drop PRODUCTION
4) Restore PRODUCTION into dirve d:\
5) Leave totally untoched all CAE configurations and REXX scripts.

Moroever, what if I skip to DROP PRODUCTION before restoring it ?
Will I be forced to change database name while restoring it and
recataloging all CAEs to address the new name ?

Thank you for your help.


Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.