dump databases on machine with secured databases

edwinvb

New Member
We have 2 machines, a production unit and a backup unit.
Both have identical hardware & OS (RS/6000, AIX) and Progress V9.1c database.
The database on the production machine has been locked down (access to the Progress database administration tool has been removed), but we do have access to the Progress database administration tool on the other machine.

Is it possible to dump the databases from the production machine and to "load" this data
into the database on the backup machine although we do not have access to the "donor" machine's administration tool?

Both machines are property of the same company, the data on both machines is basically the same and property of same company.

Thanks in advance!
 
Do you mean by "locked" down that you don't have a development license and therefore are not able to access the data administration tool?

Anyway, you can always dump and load a database outside the data administration tool. Basically you have two options ( the data definition can only be dumped in ASCII format :cool: ):

  1. Binary - using proutil <database-name> -C dump / load.
  2. ASCII running the procedures which are started from the data administration tool from you procedure ( see KB article "How to perform a batch ASCII dump" ).
The only thing you need is a user account that is not restricted with schema security settings.

HTH, RealHeavyDude.
 
First of all 9.1C is incredibly ancient, obsolete and unsupported. One would hope that you are contemplating a dump and load in order to accomplish a long overdue upgrade.

Presumably by "administration tool" you mean the data dictionary's "data administration"?

If you can run "proutil" then you can perform a binary dump & load (which is also generally faster and less error prone than a dictionary dump & load). (By "error prone" I refer to human error.)

proutil dbname -C dump tableName

There are a few things, like the user table and sequences that proutil cannot dump. You could remotely connect to the target db with the dictionary tools and dump those manually. They are small and easy to handle.
 
Back
Top