This is a discussion on Database backup in V8 within the DB2 forums, part of the Database Server Software category; --> Hello, When I run the following command under a directory different from $INSTHOME: 'db2 backup db <mydb> to . ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, When I run the following command under a directory different from $INSTHOME: 'db2 backup db <mydb> to . with 2 buffers buffer 2048' the generated file is in the $INSTHOME directory. My operating system is an AIX. Why do we see this behaviour? Why should we write the full path directory with the 'to' option? The problem doesn't appear in V7. Thanks in advance for your help. Best regards, The DB2 user. |
| ||||
| The DB2 user <dsd@fd.net> wrote: > When I run the following command under a directory different from $INSTHOME: > 'db2 backup db <mydb> to . with 2 buffers buffer 2048' > > the generated file is in the $INSTHOME directory. If you specify a relative path name as the backup target, it will be used in the context of the DB2 *server*, not the client. There are too many weird special cases to deal with when the client and server aren't on the same system (or even the same operating system) that we decided it's best to just do everything in the context of the server. (The one special case is when you don't specify any backup target, in which case the client figures out what its current directory is and passes that to the server.) Your choices are: 1. Back up to a fully-qualified path; or 2. Don't specify a backup target and let DB2 figure it out for you. dave |