I have installed Oracle xe 18 with apex and ORDS successfully on Centos 7, every thing runs fine but after certain inactivity on database like 6/8 hours later Oracle stopped and ORDS throws 503 error code.
Once I start the database up, all are normal then.
Can you please suggest me how to keep Oracle up all time/ unless manually shutdown VPS or the like?
Thanks
After your database is restarted, connect with an ADMIN level user, and use SQL Developer to inspect the Alert Log - you'll find this as one of the standard reports we ship in the Database Administration section.
Look for things like 'fatal' 'ora-600' 'abort' - this should clue you in as to what is happening.
We'll assume you don't have a job scheduled on Centos that shuts down the database.
Related
I installed Oracle Database 19c and was able to connect to the database using sqlplus in command line. However when I try to use SQL developer I'm unable to connect. I noticed I don't have any listener service like I did when I had Oracle Database 21c installed on another computer. Is this why I can't access it on SQL developer? And if so how do I create that listener?
Access the database through SQL Developer.
(I don't have the reputation to comment, so I'm posting this here.)
Just wanted to say that I just encountered the same issue.
I installed Oracle 19c on Windows as "Software Only".
I used dbca.bat to create a database with a single pluggable database through the "basic" configuration. In the past I've gone through the "advanced" configuration, and I'm wondering if that's what lead to this.
So now I'm dropping the database and will try re-creating it to see if using the advanced DB installation provides a listener.
Edit
After deleting the database, then going back through the DB installation in dbca.bat via the "advanced" installation option, I noticed that the listener configuration was actually disabled by default, and I had to choose to add a listener.
I'm getting reacquainted with Oracle after several years and Oracle 18 XE is causing some problems. I use SQLDeveloper to connect as the SYSTEM user. Then when I create a new user cpp it says that is an invalid user name. I have to prefix new users with c##, so I created the user c##cpp. The c##cpp user is there under Other Users.
But when I try to create a new connection as the c##cpp user the connection fails. I've also tried creating the connection as just cpp, but that fails too.
What's up with creating users in Oracle 18 XE?
-------Update showing my connection parameters-------
I get the same error if I try to connect with SID XE.
Welcome back to Oracle.
Since you've been away, we added a Multitenant architecture. There is a Container Database - it has common users, with names like C##user.
What you're looking for is the actual database where your data is going to live, that's called a pluggable database. There you would go back to creating users, just like you did back before you left.
Make sure you connect to the pluggable database service. The default would be 'XEPDB1' - connect to THAT as sys or system, and then create your users.
It looks like the problem is that Oracle doesn't like lower case user names. When I put the username in double quotes the connection succeeds:
This is on Oracle 11. I gave up on Oracle 18 XE and installed Oracle 11. What a ridiculous waste of time.
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 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
Im having some trouble with an oracle database. Every time i try to connect, i get this message.
ORA-01033: ORACLE initialization or
shutdown in progress
I searched the web, and found that the solution is to execute an alter database open command, but what I dont understand is where should i execute if, since I cant connect to the database.
Am I missing something?
Thanks in advance
You should connect AS SYSDBA:
sqlplus "sys/pwd AS SYSDBA"
An ORA-01033 would also be thrown if the connection attempt were made against a mounted standby database (Oracle Data Guard environment) by a non-sysdba user. Maybe a database role change (switchover or failover) has occurred since your last connection attempt.
Which OS are you using? The database is still shutting down - check the alert log as to the status of where it is at. Sometimes there are sessions hanging around that need to manually be killed off, there should be an indication of this in the alert log. It also depends how the database was shutdown, NORMAL, TRANSACTIONAL, IMMEDIATE. Even with a SHUTDOWN IMMEDIATE the sessions hanging around may still happen. To find the sessions on UNIX use the 'ps' to list all processes on the server ('ps -eaf' on Solaris) command and 'grep' for the ORACLE_SID name.