Migrate vCenter Server Database

Hi,
I have vCenter database on SQL Server 2008 R2 SP1 CU1. Now I have installed SQL Server 2012 on new server. I need to migrate the Database to this new server SQL Server 2012.
Please give KB note.
Regards
Bilal

Hello,
Please refer to the following VMWare support article?
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=7960893
We used that article to migrate VMWare databases to SQL Server 2012 SP1.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Similar Messages

Migrating SQL Server database to Oracle 8i - any known issues

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose.
When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting
SQL Server database? Would the users be able to use SQL Server database as usual?? Are
there any known issues in this regard?
Please reply.
Thanks.
Ramesh Hi Ramesh!
The Migration Workbench does not make any modifications to the SQL Server database. It only reads information from it. Your users should be able to use the SQL Server database as usual.
Please note however that if you migrate the data over to Oracle using the Migration Workbench and your users continue to enter/update data in the exiting SQL Server database then you may need to move all that data over again in order to have the most up to date data in the Oracle database.
thanks
- Garry

Quick Migrate: SQL Server database to Oracle

When I try Quick Migrate: SQL Server database to Oracle, I get the following error messages:
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
Error #1 I do not understand.
Error #2: I created the user as follows:
DROP USER GRAINTEST CASCADE
CREATE USER GRAINTEST
IDENTIFIED BY SQL
DEFAULT TABLESPACE SMARTSOFT_DATA
TEMPORARY TABLESPACE TEMP
QUOTA UNLIMITED ON SMARTSOFT_DATA
QUOTA UNLIMITED ON SMARTSOFT_INDEX
GRANT CONNECT,
RESOURCE,
CREATE ROLE,
CREATE VIEW,
CREATE SESSION,
ALTER ANY TRIGGER TO GRAINTEST
DROP ROLE R_GRAINTST
CREATE ROLE R_GRAINTST NOT IDENTIFIED
GRANT R_GRAINTST TO GRAINTEST
WITH ADMIN OPTION
Thanks
Murray

Murray,
Apologies for referring to the 1.5 documentation but the 2.1 documentation still has the same information about creating a user to hold the repository.
You initially reported 2 problems -
1. Locating source plugin...failed
2. Checking multi-schema privileges...Privilege 'CREATE ROLE" is not granted with admin option.
For the first error have you installed the necessary JDBC driver ? I have just installed SQL*Developer 2.1 on a new laptop and could successfully connect following the documentation steps -
Oracle® SQL Developer
User’s Guide
Release 2.1
2.5.2 Before Migrating From Microsoft SQL Server or Sybase Adaptive Server
To configure a Microsoft SQL Server or Sybase Adaptive Server database for
migration:
1. Ensure that the source database is accessible by the Microsoft SQL Server or
Sybase Adaptive Server user that is used by SQL Developer for the source
connection. This user must be able to see any objects to be captured in the
Microsoft SQL Server or Sybase Adaptive Server database; objects that the user
cannot see are not captured. For example, if the user can execute a stored
procedure but does not have sufficient privileges to see the source code, the stored
procedure cannot be captured.
2. Ensure that you can connect to the Microsoft SQL Server or Sybase Adaptive
Server database from the system where you have installed SQL Developer.
3. Ensure that you have downloaded the JTDS JDBC driver from
http://jtds.sourceforge.net/.
4. In SQL Developer, if you have not already installed the JTDS driver using Check
for Updates (on the Help menu), do the following:
a. Click Tools, then Preferences, then Database, then Third Party JDBC Drivers.
b. Click Add Entry.
c. Select the jar file for the JTDS driver you downloaded from
http://jtds.sourceforge.net/.
d. Click OK.
========
The second error is again documented in the 2.1 documentation -
5.99 Privilege Warning for Migration
This dialog box is displayed if you click Verify in the Quick Migrate box and the
database user for the connection does not have all privileges necessary for a
multischema migration. For multischema migrations, this user must granted the
RESOURCE role with the ADMIN option; and this user must also be granted the
CREATE ROLE, CREATE USER, and ALTER ANY TRIGGER privileges, all with the
ADMIN option.
If you are performing a single-schema migration, you can ignore this warning.
=====
Which errors are you now seeing and which user was used to hold the repository ?
If you are using GRAINTEST for the repository then create it using this syntax -
CREATE USER GRAINTEST IDENTIFIED BY password <=== change password as necessary
DEFAULT TABLESPACE users TEMPORARY TABLESPACE temp; <=== change tablespaces as necessary
GRANT CONNECT, RESOURCE, CREATE VIEW, CREATE PUBLIC SYNONYM TO
GRAINTEST WITH ADMIN OPTION;
GRANT ALTER ANY ROLE, ALTER ANY SEQUENCE, ALTER ANY TABLE, ALTER TABLESPACE,
ALTER ANY TRIGGER, COMMENT ANY TABLE, CREATE ANY SEQUENCE, CREATE ANY TABLE,
CREATE ANY TRIGGER, CREATE ROLE, CREATE TABLESPACE, CREATE USER, DROP ANY
SEQUENCE, DROP ANY TABLE, DROP ANY TRIGGER, DROP TABLESPACE, DROP USER, DROP ANY
ROLE, GRANT ANY ROLE, INSERT ANY TABLE, SELECT ANY TABLE, UPDATE ANY TABLE TO
GRAINTEST with admin option ;
then when making the migration make sure the Oracle connection is to this user.
Please update the thread with the errors you get after following these steps.
Regards,
Mike

My Experiences re: Migrating SQL Server Database to Oracle

I am using SQL Developer EA4 for thsi conversion, best attempt yet.
I had numerous problems with this conversion.
1. The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database. I also noticed a file name "Migration.out" was produced; it contained errors such as:
Error starting at line 3 in command:
CREATE USER Emulation IDENTIFIED BY Emulation DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:3 Column:36
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 4 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM,CREATE PUBLIC SYNONYM TO Emulation
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 7 in command:
CREATE USER dbo_COREv13 IDENTIFIED BY dbo_COREv13 DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP
Error at Command Line:7 Column:38
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges" and
Error starting at line 8 in command:
GRANT CREATE SESSION, RESOURCE, CREATE VIEW, CREATE MATERIALIZED VIEW, CREATE SYNONYM TO dbo_COREv13
Error report:
SQL Error: ORA-01031: insufficient privileges
01031. 00000 - "insufficient privileges".
I followed all of the steps listed in the "Help" section re: Migrations but still ended up with these errors.
2. My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
3. While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
4. Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
5. A log of all activities should be produced for review and completeness.
6. I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
7. I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
I dont want to appear negative on this Migration; I have used SQL Developer since it inception; in my opinion this is the best attempt to date.
Murray Sobol

Hi Murray,
Thanks for this feedback.
There is a lot of questions here, I think some of it boils down to misunderstandings, which we should clarify in the doc.
Hopefully Ill get a video of a migration online soon as well.
But here is a brief break down.
*1.*
"The wizard asked me to specify the new Oracle database; instead it just ignored this information and created an Oracle database similarly named as the SQL Server database."
So this relates to Step 7 of the Migration Wizard. Where you can select the target connection.
SQL Developer doesn't ignore the Target Connection you selected, It just uses it to connect to the target database , not the target schema.
SQL Developer generates a new target schema for the migrated objects. It standard approach is not to generate objects directly into an existing Schema.
The Target Connection is used to create all the migrated objects (including new Oracle Schemas) in your target oracle database. So you should choose an Oracle Target Connection which has enough privileges to create new Schemas and Objects.
But as you have found, it doesn't generate the migrate objects , like tables, ... , directly into your chosen Target Connection.
From the errors you encountered it doesn't sound like the Target Connection (and the underling Oracle Schema) doesn't have the privileges to create other Schemas.
If you use something like a connection to the SYSTEM schema on your target database, it should run OK.
It wont create any objects in SYSTEM, rather it will use SYSTEM privileges to create a new schema (ex: dbo_Northwind) and populate it.
You don't have to use SYSTEM, but you do need a schema with enough privileges to create other schemas.
That is the straight forward way. But if you really need to generate into an existing schema the following steps can be taken.
a)rename the schema under the Converted Database Objects
b)Right click "Converted Databases Objects" and choose generate. it will kick off the Migration Wizard in the correct place
*2.*
My schema consists of 1000+ tables; approximately 10 tables were NOT created. When I copied the SQL from Migration.sql making NO changes and pasted it into the new Oracle database it created without issues.
When you say Migration.sql , is the entire generation file , which can be found in your <outputspecified>/generated/<projectname.modelname>.sql ?
When your say "pasted it into the new Oracle database" , are you running it in SQL Developers SQL Worksheet using the Target Connection.
Basically your migration is all out of shape once the target Schemas are not created. So the above issues (insufficient privileges) has to be resolved first.
Please post back if it is still an issue.
*3.*
While the conversion is taking place, different objects (constraints, indexes, foreign keys, etc) are shown to be copied; their appears to be ordering of these items. Shouln't a dependancy tree be established, and object converted based on this?
Objects are converted in a particular order and their dependencies are persisted so that they can be generated in the correct order.
Are you seeing an issue?
*4.*
Several tables, in my case about 250 tables did NOT get any data copied across. No reasons given.
I'm surprised any tables were populated with data due to the target schema not being created.
The online data move is pretty simple and it does not report or recover very well from issues.
If you are having difficulties once item 1. is resolved, please post an example of the source table and I will give it a go.
For better control of the data move with much more powerful tweaking, error handling, reporting and performance try the offline data move.
SQL Developer can created a suite of scripts which use SQL Servers BCP tool to dump out the data to dat files, and Oracle SQL*Loader tool to insert the data in the dat file into Oracle.
*5.*
A log of all activities should be produced for review and completeness.
The output/generated/<projectname.modelname>.out provides the output of running the generation script.
The migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html outline what happens during the migration.
Apart from online data move issues, is there any other data missing?
*6.*
I tried to use the "Migrate select tables" option but met with no success. Apparently, it makes an assumption that both the "source" and "target" databases wil be of the same type (ie both SQL Server or both Oracle); this does not make any sense to me since the point of the exercise is to migrate data from one database vendor to another. Obviously, different database vendors use differing datatypes for similar data (ie dates).
Do you mean "Copy To Oracle" ? This option is intended to migrate tables from non Oracle databases like SQL Server to Oracle.
Can you give more details on what issue you are seeing.
*7.*
I noticed in the "Migration" sql that the "Connect" statements are not correct; they were missing the "instance name" portion.
The generation script is meant to be run using SQL Developers SQL Worksheet. I think you only get this "instance name" issue if running from SQL*Plus.
Can you confirm
8. Also, when I looked in the "MIGRATION" sql, I could not find any entries for the last step of the conversion - the movement of data from SQL Server to Oracle. Is this intentional or an oversight.
The online data move is performed separately from creating the objects. It is not script based, it uses JDBC to pump the data from the source database to the target database.
In summary , I would
a) Create a connection to your Target database using your SYSTEM schema
b) Right click on your "Converted Database Objects" and choose "Generate Target"
c) Choose your new "System" connection as the Target Connection
d) Follow the Migration Wizard to the end.
You will end up with a new target Schema and the migrated objects in it.
Check the .out file to see the errors
and the migration reports http://dermotoneill.blogspot.com/2010/11/migration-reports-30.html
Regards,
Dermot
SQL Developer Team.

Converting Access application after migrating SQL Server database

I have used migration workbench to migrate an access database and application. I now have sql server databases with access applications that need to be migrated. How can I convert the access applications that currently use sql server as a database? I don't see that migration workbench considers this combination.

If you have and Access/SQL Server combination. then download the SQL server plugin appropriate to your version of SQL server. Go ahead and migrate the SQL Server database to Oracle. Once this is done, then update your access application so your link tables point to your newly migrated Oracle database.
Donal

Issue in Migrating Sql Server Database 2012 to Sql Azure

Hi All
I am facing following issue while Deployed MS SQL Server 2012 Database to SQL Azure.
TITLE: Microsoft SQL Server Management Studio
One or more unsupported elements were found in the schema used as part of a data package.
Error SQL71564: The element Extended Property: [dbo].[Accounts_Login].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Company_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Message_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Requests_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Twitter_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Users_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
(Microsoft.SqlServer.Dac)
Error SQL71564: The element Extended Property: xxx is not supported when used as part of a data package (bacpac).
Thanks & Regards Ravi Shankar

Hello,
Extended Properties are not supported in SQL Azure.
To work around this issue, you can use Generate Scripts Wizard to generate script which are compatible with SQL Database and can be compiled on SQL Database without any further modifications. For example, in Choose Script Options, click on the Advanced button
and, set Script Extended Properties = False.
Reference:http://social.technet.microsoft.com/wiki/contents/articles/994.develop-and-deploy-with-windows-azure-sql-database.aspx
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support

Migrate SQL Server 7.0 to Oracle 8i - Any known issues??

Hi,
I am in the process of migrating SQL Server database to Oracle 8i for testing purpose. When I do migrate SQL Server database to Oracle 8i, am I doing any harm to the exiting SQL Server database? Would the users be able to use SQL Server database as usual?? Are there any known issues in this regard?
Please reply.
Thanks.
Ramesh

The Migration Workbench copys the information it requires from the source database and stores it in the Migration Workbench Repository, which is separate from the Source database. So, to answer your question, yes, the users can continue to use the SQL Server database. The data move may cause some system performance degradation. It may also be an idea to replicate the SQL Server database, in case any complication should arise.
Hope this helps
Dan

New vcenter server but keeping database with nexus 1000v

I have been reading through all the details of migrating to new hardware for the vcenter server with the nexus 1000v. i wish to avoid doing the vswitch thing. If I am keeping the same database but just moving to new hardware and possibly new ip address I was hoping to be able to do something along the lines of.
Leave everything as is,
Reinstall vcenter on new server and point to existing database.
reconnect the esx hosts
disconnect the VSM
get the xml from the vsm
install on vcenter server
reconnect the VSM to the new server
all should be good.
From my reading it appears as tho most of the issues are around connecting to a fresh database.
Is there anything wrong with my assumptions??
Regards Justin

I have done this before but I always keep the same name an IP so that I don't have to reconnect each ESXi host and my vSphere Client users don't have to use a different name.
What I do in this scenario is build the new server with a temp name/IP.
Backup the vCenter DB and SSL certs (this is very important).
Power down the old vCenter.
Re-IP/Re-Name the new to match the old.
Copy the SSL certs to the proper location (C:\ProgramData\VMware\VMware VirtualCenter\SSL)
Create your DSN and install vCenter using the old DB. The DB will be upgraded.
Your hosts will automatically connect to the new server.

Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Hi,
I need inputs in how we would migrate our connections in Repository from Oracle database to SQL server database in Sloaris server.
Is there a complication here.
Regards,
Bhavik

Well that makes more sense, you probably have phrased your question better. Microsoft SQL Server Connectivity Components are not supported in any other operating system than Windows. So you will not be able to use the SQL Server native drivers to connect to your SQL Server. ODBC it's an option but there aren't many ODBC drivers for Unix systems. Luckily for you OBIEE includes the DataDirect ODBC drivers and supports using them to connect to a SQL Server. Check [the documentation|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10416/general_101331.htm#sthref9] on how to use them. Having said that I would say that whoever is pushing to move your DWH to SQL Server should consider also moving OBIEE to a Windows server to be able to use the SQL Server native drivers to connect to SQL Server.
PS: No needs to post 3 times. :-)

Migration of the database from Microsoft SQL 2014 Express to Microsoft SQL 2012 Server

I posted a similar thread yesterday, and I realized that there was a serious typo.
Link: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b3e201ea-6c7c-43a4-8908-842b714ea451/migration-of-the-database-from-microsoft-sql-2014-express-to-microsoft-sql-2012-server?forum=sqlservermigration
Therefore, I made a decision to post another thread right now.
I am
writing to ask if there are any known issues when migration from MS SQL 2014 Express to MS SQL 2012 Server version. Are there any step-by-step instruction on how I can go about doing this?
Looking forward to your response. Thank you for your time.
Regards,
Jeff Yoo

Hello,
SQL Server 2012 setup program won’t allow you to perform a downgrade from SQL Server 2014 Express Edition. Backup/Restore
and Detach/Attach won’t help you either.
One option you have left is using SQL Server Import/Export Wizard as explained on the following article.
http://www.mytechmantra.com/LearnSQLServer/Downgrade_SQL_Server_Database_P1.html
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Migrating a physical database server to a virtual server

we are migrating a physical database server to a virtual server what are the concerns?
the server name and IP address will stay the same

Database server on a virtual server sounds like a bad idea to me.
Databases are huge resource consumers, they require dedicated resources memory/cpu/IO/network.
In virtual settings all this is shared.
So, I predict that in virtual your performance and throughput will suffer greatly.
You can google pro's and con's of virtualized servers for more details.
However, as far as BO product is concerned - all we need is connectivity, if DB connect info doesn't change - we won't see no difference . (except above about performance)

Cannot add a Vcenter server in the MA portal -

Hi,
I have been working through the deployment instructions from the help documentation. When I get to the section where you discover the source enterprise, I am unable to add our on-premise VCenter server. Specifically - there are no "discovery
agents" available in the drop down. I have attached a screenshot of what I see when I try to do this. I have ready through and tried the recommended troubleshooting steps from item 3 in this document
http://blogs.technet.com/b/srinathv/archive/2014/10/28/troubleshooting-migration-accelerator-deployment.aspx to no avail.
So far I have confirmed that the CS can see the on-premise PS server- and is visible in the Process Server section of the agent settings (Settings-->Settings-->Agent Settings).
I have also confirmed that the CS can sync with the RX (Settings-->Advanced Configuration Settings-->RX Settings) .
I am hoping I missed something simple - any help will be much appreciated.
thanks,
Fred

Hi,
I can see your point...
From my error :Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/2 configure_server_for_cluster lun /dev/mapper/35000144f85151729 0004fb0000050000c696b251dc81a087 , Status: org.apache.xmlrpc.XmlRpcException: exceptions.OSError:[Errno 2] No such file or directory
/dev/mapper/35000144f85151729 is the path where the server pool uses for it's own...
and
0004fb0000050000c696b251dc81a087 is the Pool file System...
On storage menu, at SAN Servers - Unmanaged iSCSI Storage Array - where I see my storage wich is with iSCSI at Add/Remove Admin Servers I added this new server.
Also I went to Rescan Physical Discks for my new server.
When I go with putty on my server and run
df -h
I don't see any storage...
I belive I missed one step but I can't find wich one...
Regards
Nicolae

Need help in migrating MSSQL 2008 database to Oracle 11g

Hi everyone,
So, as stated above I want to migrate our apps database from mssql to oracle as it is what the client wants..
I have absolutely no experience working with Oracle.
My computer is running windows 7 32 bit, our DB people installed a 9i client for me to connect to the server and the my SQL Developer just came straight from the site. (So it's the latest release)
I have one "DBA" access to the database I'm trying to migrate to.
I've downloaded the Oracle SQL Developer and have been attempting to "migrate" our database using the migration tool for 3 days now, but to no avail.
So the error I'm encountering is that the migration just stops, and a popup with the message "Migration actions have failed. Check the migration reports for details. : The connection is closed." comes up.
I have no idea where the migration report can be found. As I cannot find it in the reports tab available.
I'm hoping someone here can have the patience and knowledge to get me through this?

The migration report is generally created under the "Documents and Settings" folder under application data/sqldeveloper. Key thing is at what stage the failure occurs?. Does it happen immediately after you start the data migration or after a while?.
If the data migration process fails immediately after the start then there might be an issue with permissions on the source/target databases. Probably it is having trouble with disabling constraints on the target database. Because rememeber SQL Developer will disable constraints before it moves data across. My preference is to give DBA privilege to the Oracle user to avoid just cases or you can disable the constraints yourself by using scripts. Check the source/target database date/time format masks. You can set them up in SQL Developer.
If the data migration process fails after a while and you notice that data for some tables is migrated then you may be running into network timeouts or space issues on Oracle etc.
HTH
Regards
Prakash

How to create a sql server database in SQL DEVELOPER.

I installed the SQL DEVELOPER 1.5.5, but i can't found where to create the sql server database in it. please kindly tell me if you feel free.
Thanks so much in advance.

Hi,
Take a look at the main [ SQL Developer page on OTN|http://www.oracle.com/technology/products/database/sql_developer/index.html]. There is a link you should find useful, it's the Getting Started link under the Migration section. This explains how to download and setup the drivers you need to correct to non-Oracle databases. There are also links to online demonstrations on how to create connections to these databases. See how you go with that material.
It should help.
Sue

Migrating Sql server to oracle

Hi All,
Where can i get documentation/tools about migrating microsoft sql server database to oracle database.

Where can i get documentation/tools about migrating
microsoft sql server database to oracle database.Oracle SQL Developer is very good for start.
Tool:
http://www.oracle.com/technology/software/products/sql/index.html
Doc:
http://download.oracle.com/docs/cd/E12151_01/doc.150/e12156/toc.htm
Cheers!

Migrate vCenter Server Database

Similar Messages

Maybe you are looking for