As already said, the recommended procedure is not to install Orcas in the same schema which is to be adjusted. Therefore, we will change our project to the use of a separate Orcas schema.
First of all, we should newly set up our existing schema to get rid of the Orcas database objects (In principle we can make use of the Ocras resources, but we don’t “know” them yet).
The important change is that as “user_orcas” we no longer use “myschema”. Instead we set “myschema_orcas”.
To create this user we will use the ant task “orcas_install”. For this we have created an ant target called “setup”. To call “orcas_install” we need to specify a user (including password) with the permission to create other users. After our “myschema” user has not these rights, we use the “system” user.
To the problem that the password (exactly like the others) should not be placed in the build.xml, we take care of later.
It is also possible to manually create this user (without “orcas_install”) or let create by a DBA.
To use our project now, we need to call once our setup target:
Then we can normally start the adjustment:
The result is now that in myproject only our “mytable” exists, the two ORCAS_ tables are now in the scheme “myschema_orcas”.