Hello,
in our project (.NET4 Application with EF), we plan to change the DBMS, moving from MS SQL Server 2008 to Oracle 11gR2. Thus, I am a kind of newbie in the "Oracle world"!
I am trying to migrate a database withing SQL Developer 3.1: the conversion from MS-SQL to my own Oracle repository worked fine, but all objects name are in the migrated database with UPPER CASE: how can I get that fixed?
Here are the steps I did until that point:
0. Install Oracle Express on my local machine, create a connection for SYSTEM user in SQL Developer
1. Create a new user 'oracleUser' with some rights in the sql editor with the following commands:
CREATE USER oracleUser IDENTIFIED BY userPwd DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP;
GRANT CONNECT, RESOURCE, CREATE SESSION, CREATE VIEW, UNLIMITED TABLESPACE TO oracleUser;
2. Create a new connection named "OracleMigration" for this new user: username = oracleUser and password = userPwd
3. Get a JDBC Driver for MS SQL Server from http://sourceforge.net/projects/jtds/ and add it in SQL Developer into Tools\Preferences then under Database\Third Party JDBC Drivers,
4. Create new connection named "MS SQL Server", tab SQLServer using Windows Authentication to my running MS SQL Server
5. Open the connection and select a database, right clic "Migrate to Oracle". Follow the migration wizard with the default values (online migration), using OracleMigration (created in step2) as repository, and SYSTEM as target database.
6. Create a new connection in SQL Developer with userName = name of the migrated database. It works and the data are here! But why are all table and fields in UPPER CASE?
Is there any possibility to keep the case of the objects names during the migration?
--------------------
-- Previous issue: the target database. --
Initially, I put my OracleMigration as target database as well, but go the log full of messages like "oracle.dbtools.migration.workbench.core.MigrationLogResourceBundle : Failed to disable constraints: Data Move"
It appeared it was an issue with the privileges, as the .out file showed up.
-->
Bug in SQL Developer: it said the migration was successful while it was NOT!
I tried also the migration adding some further rights:
grant CREATE User, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM to oracleUser
but still had the following log:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation
Error report:
SQL Error: ORA-01031: insufficient privileges
Which rights is needed here?
As read in a
2189819 , I then migrated with Target Database = SYSTEM, and everything went fine, until this UPPER CASE issue.
--------------------