More issues with dbunload (ASA11)

[DJS]

7/7/09

Well, that was interesting (not useful, but most interesting). When I
finally got dbunload working, it gave the messages for unloading table
defs, unloading index defs, unloading triggers, then creating new
database.

Then it went ahead and made all of the tablespaces and seemed to
allocate space for about 60% of the size of each of t4he tablespaces
(even the ones I did not indicate any talbes to be copied, since I
indicated all tables individually).

Well, after it allocated all of the 6 table spaces, then I get the
error "***** SQL error: User ID 'sai' does not exist, and then ends.

When using the ASA9 dbunload I used the exact same tables, but in the
case of ASA11 dbunload it did not seem to work the same.

Is the new (ASA11) version of dbunload expecting EVERY table that is
to be copied (EVEN SYSTEM TABLES) to be specified? I did not see
anything in the docs I read that covered this particular scenario.
Any ideas out there would be appreciated and helpful.

Thanks again for the assistance.

Douglas J. Switzer
Longitude System Architect
DVTel

[DJS]

As a follow up... I just tried adding ALL of the system tables and
still get the exact same error: "User ID 'sai' does not exist" and
then it ends...

We have a user SAI in the original database, why does it appear it is
NOT getting copied over (since it is in the original)...

Is there some special option needed to copy users (I see one NOT to
copy users for replicated DBs but I am not using this option at all).

Again, any ideas would be appreciated (or where to look for further
information). One of the problems, is that anything I try takes a
long time to get there since it seems to allocate the whole DB first
then start copying. Maybe I will try it on a very little DB (liek one
almost empty) and see if I can get it to work right first, then try
this gain with the bigger one...

[Ray Ruvinskiy [Sybase iAnywhere]]

Hello,

dbunload's -t (or -e) switch cannot be used for a complete database
reload, since the switch restricts the unload to table definitions only
(see the documentation for these switches at
http://dcx.sybase.com/index.php#http%3A%2F%2Fdcx.sybase.com%2F1100en%2Fdbadmin_en11%2Fdbunload.html).

There does not appear to be a one-step way to accomplish what you're
trying to do. Bruce Hay has suggested the following alternatives:

- make a copy of the database
- using the copy, drop the tables he wants to exclude
- do the rebuild using the copy

Or

- use dbunload -nl to create a reload.sql script including the LOAD
TABLE statements
- use dbunload -d to generate the data files, excluding a subset of
tables if needed
- modify the reload script if necessary
- run the reload.sql script using a new database

Ray

[DJS]

On Jul 8, 10:29 am, "Ray Ruvinskiy [Sybase iAnywhere]"

<first.l...@sybase.com> wrote:
> Hello,
>
> dbunload's -t (or -e) switch cannot be used for a complete database
> reload, since the switch restricts the unload to table definitions only

> (see the documentation for these switches athttp://dcx.sybase.com/index.php#http%3A%2F%2Fdcx.sybase.com%2F1100en%...).

> > this gain with the bigger one...- Hide quoted text -
>
> - Show quoted text -

Thanks for the suggestions, but each of them has problems from my
perspective, including the time it takes when unloading the tables,
dropping certian items and editing files, and the like. I am looking
for an easier alternative, so am trying to do it another way. I will
see if it works and post a follow up if possible.

I am dissapointed that dbunload was not written with a little more
forethought to allow upgrading from older databases where a
significant amount of the data is not desired, but still reducing the
amount of work required.

I will let you know how my experimentation goes...

Thanks anyway for the help so far...

DJS