Have been using SQL Server 2008 R2 Express for years, and my db engine somehow got corrupt.
Installed/reinstalled, da da da...
I've got 2 days in now trying to fix known nagging error without success:
Database Engine recovery handle failed
I am ready to pay for remote technical support now...
I've read and tried most of the support forum solutions on this, trying to change the server logon and am at a standstill...
Any idea whom I might call for support?
Thanks
jlm86
Related
The company's server encountered a virus, and the server administrator reset the server. Luckily, they kept the oracle instance folder, but I didn't know how to extract the data from it.
This is the legacy oracle instance folder
I tried to move system01.dbf directly to my oracle, but failed
My English is not very good, this writing is written in Google translation, I hope I can express accurately,thanks.
I'm trying use Microsoft SSMA for Oracle to migrate a database onto Azure SQL, but I can't get it going. I've double checked the server name, server port, Oracle SID, password... everything. No matter the type of entry screen I use, I can't get it to connect to the on-premise Oracle instance.
I'm pretty sure the login information is all correct, and I should have a working connector to Oracle since I connect to it from TOAD on a daily basis. I tried installing Oracle libraries per previous posts but not sure if I did it successfully because the issues still remains.
What are the troubleshooting steps I should take in order to make this work?
Log in screen:
Error 1:
Unable to find specified provider.
Compatible Oracle Data Access Connectivity libraries were not found on the machine. You can install them from Oracle product media or download it from Oracle web site.
Error 2:
Connection to Oracle failed.
ORA-01017: invalid username/password; logon denied
Error 3:
Connection to Oracle failed.
Network Naming: No LDAP server detected or configured
After a few more days of debugging, I was finally able to get SSMA to work. This answer helps to document my solution for personal use, as well as hopefully answer anyone else's question in the future.
After looking at the list of prerequisites to have SSMA running, I saw that I needed to have a correct Oracle client running. After some internal discussion, it was likely that the Oracle client SSMA needed was different than the one my computer already had for TOAD. The .Net provider for the TOAD connectors was probably not useful for SSMA.
We run Oracle 11g but I had to install Oracle 12c because 11g did not support Windows 10 apparently. Not too much of a roadblock here.
I found this guide to install Oracle client 12c pretty helpful. Shoutout to my alma mater.
Unfortunately the installer kept freezer, but using this former post, I was able to bypass it with the windows command:
setup.exe -ignoreprereq -J"-Doracle.install.client.validate.clientSupportedOSCheck=false"
After that, I saw different error messages when trying to connect SSMA. I kept trying different options with my logins until it worked. Provider: OLEDB Provider, Mode: Standard.
After being granted the appropriate permissions, I was finally able to access our internal tables and objects.
It was a pretty annoying question with a lot of rabbit holes along the way, but it was definitely worth it, being able to translate all our Oracle schemas to Azure SQL with a few clicks. Hope this helps!
Make sure to validate all steps mentioned below before going to install Microsoft SQL Server Migration Assistant for Oracle.
Make sure you have already installed SQL Server instance that will host the migrated database. Also keep in mind that you are not installing SQL Server Express edition to host the migrated database.
You must have sysadmin account to install SQL Server Migration Assistant for Oracle.
Make sure to install SSMA for Oracle on the server that will host newly migrated database on SQL Server.
It is recommended to install Oracle client software on your target system where SQL Server Instance is running.
Make sure your windows server has Microsoft Windows Installer 3.1 or a later version. Port 1434 should be open.
For more details, You can reference: How to Install SSMA for Oracle to Migrate Oracle Database to SQL Server.
Here's the Azure Database Migration Guide: Migrate Oracle to Azure SQL Database. As you prepare for migrating to the cloud, verify that your source environment is supported and that you have addressed any prerequisites. This will help to ensure an efficient and successful migration.
Connect to Oracle with Oracle Client Provider.
Azure also has other way can help you migrate Oracle database to Azure SQL database, such as with Azure Data Factory. If you still has the connect error. I think you can try to use it. Please reference this tutorial: Copy data from and to Oracle by using Azure Data Factory.
Hope this helps.
I am connecting to oracle 12 in Oracle cloud, from PowerBI Desktop windows server 2016.
Oracle client is installed and TNS file configured.
Oracle is hosted by a vendor so my only access is to directly query the database.
In powerBI, when using an oracle connection, i get ORA-03113 errors about 50% of the time when refreshing data. There is no discernible pattern to the appearance of the error.
If i connect via a System ODBC connection set up in windows, I dont get any issues or errors, although the data load is a bit slower.
I would appreciate ideas on what may be causing this issue or what to check to help get more information.
I'm afraid your issue needs some deeper analysis as ORA-03113 might have various reasons, but typically it means that the 'oracle' executable has terminated unexpectedly once there was an existing connection. You should try to isolate the SQL command that is executing when the error occurs. It can be done either by checking the trace files on the server or by using SQL*Net trace if you don't have access to the server. If a statement can be isolated which consistently raises the ORA-3113 error, then it can be further analysed (like execution plan, triggers, etc), or maybe the best to raise an SR so Oracle Support can work on the issue. If you have access to Oracle Support you can find more information about ORA-03113 troubleshooting in MOS Doc ID 1506805.1. Let me know if I can help you any further.
i have an error which is driving me crazy and i dont know how to deal with it. In a PC with windows 10 64-bit , i got an oracle database server 11g. Everytime the pc restarts or shuts down and then restarts i get the following error when i try to connect to the database :
ORA-01033: ORACLE initialization or shutdown in progress
Process ID: 0
Session ID: 0 Serial number: 0
the only way to get my database running is the following one:
open a cmd and type :
rman target /
recover database;
shutdown immediate;
startup mount;
alter database open resetlogs;
after that everything is fine , but if i restart the PC i get the same error again.
Has anyone dealted with anything like this before?
I have checked the hard disk and is ok, have defragmented it, have run test diagnostics, it is driving me crazy. Any idea would be welcome!
Thanx in advance!
That is a pretty general error. Your database can have issues with either starting up or maybe shuting down cleanly.
I would recommend you looking at the end of the alert.log file right after the server is started, before performing rman recovery.
You can find hints there as why the database did not started up to open state, where and why it is hanging, etc.
EDIT: So the error is ORA-00600 [dbkif_find_next_record_1]
Whenever an ORA-00600, or ORA-00700 or ORA-07445 occurs, this is an internal error within Oracle core. For this cases there is this neat tool at http://support.oracle.com which can search the knowledge base of Oracle MySupport network and try to find existing articles and/or patches, hotfixes for respective arguments of these internal errors.
The tool can be found as Oracle Support Doc ID 153788.1.
Unfortunatelly, the lookup tool did not found anything for argument ORA-00600 [dbkif_find_next_record_1]. In that case please make sure that your OS is updated and supported. Also if you are running on VM, that the VM has all parameters set according to Oracle's recommendations and if there is nothing suspicious there, you will have to open "Service request" at http://support.oracle.com
I am using DevArt's dotConnect Universal to connect to Oracle database.
It works very well in test enviroment and also on my local machine, but when I deployed it to production, it keeps giving errors intermittently. These errrors are like ORA 12571: TNS Packet Failure and ORA -03114 :not connected to Oracle. You can see these errors at: http://screencast.com/t/1XreLL0fq and http://screencast.com/t/mpbTkf3t4.
However, when I change the provider from Devart dotConnect Universal to Microsoft's System.Data.OracleClient, everything works without any errors. My code is exactly the same when using DevArt OR Micrsoft's Oracle provider, since I use the DBProvider style of coding in ADO.Net.
Why is DevArt's provider sometimes succeeding and sometimes failing in production ( it was perfect in test environment)? May be someone else has had a similar experience.
We consider that both these errors (ora-12571 and ora-03114) are caused by the Oracle server. And System.Data.OracleClient would produce the same error in a similar situation. Does the problem go away after you started using System.Data.OracleClient?
Try switching to the Direct mode when using dotConnect Universal: http://www.devart.com/dotconnect/oracle/docs/?directmode.html (add the "Provider=Oracle;" connection string parameter to get a valid connection string for dotConnect Universal).