I migrated a SQL Server database to Oracle 11 Express and have trouble to connect to the converted database in Oracle SQL Developer. I followed the instruction here: Oracle Migration the only difference is I am using an on-line migration.
I have successfully converted the database, but what I am struggling with is I cannot connect to the converted database because there is no user migrated (or created). Please see image below. I wonder if anyone has the same problem before or can give me directions how to solve this.
much appreciated for any suggestions/helps.
SQL Server to Oracle Migration - connect migrated user
If your migration is completed and your repository has recorded all migration transactions.
It is confirmed that before migration you created Oracle User. you are well aware about the password.
If you have lost after migration.
Just log in as System or Sysdba user and change the particular username password. That's it.
Now connect to migrated user.
Related
Is there a proper way to move a SQL Server 2016 sharded database from self-hosted to Azure Database?
I have a SQL Server 2016 sharded database that is part of the platform (Sitecore 10) I'm working with. It has a Shard Map Manager database and two Shard databases. I want to migrate the databases from self-hosted to Azure Database.
When the database is in a SQL Server Instance, it has one login mapped to the Shard Map Manger user and both Shard users. Everything works great. Since Azure Database does not use logins the same way and the databases are partially contained, I created separate users in each database in Azure with the same name and password.
Next, I migrated the schema with Azure Data Migration Services and then the data. There are some stored procedures that Sitecore provides to setup permissions and I ran those.
Finally, I updated the ServerName and DatabaseName fields in the [__ShardManagement].[ShardsGlobal] table for the ShardMapManager DB and the [__ShardManagement].[ShardsLocal] table in both Shard databases to match the new server and database names.
When I updated the app to use the new database, it spewed errors into the log, ultimately tracking to a failed login for the user. There are 13 other databases for the app which were also migrated and work fine, only the sharded database does not work in the app. I ran a PowerShell script that tests the connection string for all of the databases. All of the connection strings were successful. Backing out only the connection strings for the sharded database fixes the errors proving that the connection to the sharded databases is the problem.
What did I do wrong and what should I do to fix it?
If the requirement is only to migrate the databases from local to Azure, the best possible way is to use SQL Server Management Studio (SSMS).
The advantage is that you can mention the new database name on Azure while migrating itself and hence no need to change later. But just make sure same named database shouldn't available already in Azure SQL Server.
You can follow the migration steps from my this answer.
Also, my suggestion is to go through the official documents Assessment rules for SQL Server to Azure SQL Database migration, Troubleshoot connecting to the SQL Server Database Engine. I'm sure you will find the useful insights there which could help to make migrated database work properly with the apps.
I'm attempting to use the Visio Reverse Engineer wizard, part of the database add-in for Visio, targeting one of our databases that's an Azure SQL Database.
I'm able to successfully connect using the same connection strings that I use for all of our other services, SSMS, SSIS, Python, etc..., however the only DB option it gives me is 'master' Master DB only Option. One connected it displays only objects in the master db which obviously I'm not trying to reverse engineer into a data model. Master DB objects available
Additionally, I've tried passing 'Catalog=' Parameter to point to the database in question but this gives me the same options.
All of our Azure SQL Databases have the connection string <databasename>.database.windows.net
I've used the Reverse Engineer wizard before for our other SQL Server (which is on an Azure VM and not a Azure SQL Database itself) with no problems.
At this point, I'm not sure if this is an issue with the Visio Reverse Engineer wizard or if there is some setting that we are missing with our Azure SQL Databases.
Any help is greatly appreciated.
Thanks!
When choosing what Visio DB Driver I wanted to use, I figured I'd try to use SQL Server Native Client 11.0 and it allowed me to select the DB I wanted to Reverse Engineer instead of just master db. Driver Selection
I'm not certain why this worked for me, bit it did.
This is the first time I'm using Splunk DB Connect for an Oracle database.
I've configured my database successfully and deployed the updated DB Connect app.
But when I try to access my connection in SQL Explorer I can't choose "Catalog" and it's greyed out. I can't get any info from the Oracle connection.
I've run into this, too. As I understand it, Oracle does not have the concept of a catalog like other SQL databases do.
Do check a few things. Make sure your database is running Oracle 11g or later. Your account may need to have dictionary access.
I cannot seem to browse the tables on my Azure SQL Server database from within Oracle SQL Developer (Version 4.1 - using jtds-1.3.1.jar plugin).
I can connect and perform all queries (inserts, selects, etc.), but when I try to expand it to view the tables, I see this error:
An error was encountered performing the requested operation:
Reference to database and/or server name in 'master..sysdatabases' is
not supported in this version of SQL Server.
Vendor code 40515
Note: I tried rolling SQL Server back to version 3, and I'm getting the same error.
Please advise. Thanks for your help!
We're not certified for Azure..there's a similar problem in SQL 2014. The way we're asking for a list of tables isn't valid in that version. Would require an enhancement request to support Azure for Oracle Database Migrations.
I am using SQL Server 2008, developer edition. I connect to my database from my asp.net mvc application using Linq2SQL. I noticed that my database went into recovery mode about 4 times in a span of a month. I am running a few complext Linq2SQL queries. When database is in recovery mode, my asp.net mvc application is going off line as it could not connect to the database. I do not know how to prevent the database from getting into recovery mode. I have seen some of the questions on SO, but could not find a way how to solve it. I am hoping some one could help me out.
Some possibilities/things to check include:
Is this database part of a Log
Shipping configuration? If so, whilst
the Secondary server is being
restored you will be unable to
establish connections to the
database.
You are certain you are using the Developer
Edition of SQL Server and not the
Express Edition?
Is the Autoclose option set to TRUE?
If so the database will shutdown when
there are no active user connections.
To check if you have any databases set to Autoclose use the following T-SQL:
SELECT * FROM sys.databases WHERE DATABASEPROPERTYEX(name, 'IsAutoClose') = 1