This is the screen to manage connections between target and source databases.
There is a possibility to manage more than one connection and to create Accelario schema in source/target databases.
To setup new database press the “New” button in destination or source database list.
The following details are required:
IP – address of the host on which database resides. This may be the IP address of hostname resolvable by the server.
Port – listener port of the database. Usually 1521.
SID/Service – service name with which the listener serves the database.
User – main username of Accelario, use for connection and to store repository.
Password – password for the above user.
TNS name – valid TNS name that resolves to the database and recognized by the source and destination database.
Install button – use to make a new installation. In this case, the main user will be created, granted with all the needed permissions and created repository objects. To run this SYSDBA user and password are needed, usually it is user SYS.
The user always created with default tablespace USERS and temporary tablespace TEMP.
Save button – use to connect to the already installed database. There is a check that valid repository exists in the database.
For security reasons, the application does not save any password. Not the password of the main user or the password of SYSDBA user. The passwords are used only during connection.
After completion of Accelario database installation, the databases should be attached. Accelario supports managing multiple destination databases from one application server and multiple sources for every destination. To attach Source to Destination use option Attach in the Actions submenu. The following screen will appear:
This screen allows to attach any source database to current destination database or to detach them.
Attach – connects the source to destination by creating corresponding dblinks between the databases and updating the repository. Later, every source may have its own parallelism level.
It is highly recommended that all the sources will be the same according to their contents. It may be snapshots, dataguard, or any other form of copying database. The reason for this recommendation is the fact that during migration every source is treated the same and expected to retrieve the same results as any other source. Nevertheless, the servers’ capacity may be different.
Detach – disconnect source from the destination by dropping dblinks and updating repository. When the destination database left with no sources, it is impossible to work with it.