I'm developing my small project using Oracle Database and Developer. When I create a new connection, this problem always show up:
I can not create connection.
I check services, and can't find OracleDBHome1Listener, what can I do to fix this?
run lsnrctl status shown this:
Related
A user has been configured on Oracle. Via this user, I can create an ODBC connection and an OCI connection, and these both test fine in Win10. Using Alteryx with the ODBC and OCI connection, we try to write data to a new table.
The table is created and appears in PL/SQL with the expected column names. However, the rows are never written and the connection just hangs at this point.
What could be wrong? I am not an Oracle Admin
Based on comments you were expecting oracle to commit without executing "commit" command explicitly. It's not enabled by default in oracle so you have to turn it on.
It's not possible to turn this on for the database, but on client apps only.
E.g. "set autocommit on" command in SQL Plus.
So you need to check docs for the client application you're connected with (presumably Alteryx is the one). It might have such a feature.
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 can connect to my 12c Oracle database using Oracle's Sql Developer and see my schema, but when I connect via SSMA I can't. I see a bunch of other schemas in SSMA, which I assume came with Oracle because I've only created two users on the box and I don't see either of them in SSMA. I'm connecting using the System account, so I don't think it would be a permissions issue. As you might be able to tell I don't know much about Oracle. Where could my schema be hiding?
This answer states that we should start OracleService* in order to connect to an Oracle DB.
However, there isn't a OracleService* among the list shown by services.msc.
Is there any other way to connect to an Oracle DB from command line, without using OracleService*?
I have got a workspace in apex.oracle.com , Now , I want to connect to that database through JDBC from ubuntu-14.04 machine. please explain the steps , From where should I download the drivers and what should be the arguments in
DriverManager.getConnection();
step by step please. Thank you
You will not be able to connect to the database that's supporting the APEX instance on apex.oracle.com. If you are hosting your own instance, it's no different than connecting to any other Oracle database.A quick code snippet can be found here: http://www.java2s.com/Code/Java/Database-SQL-JDBC/TestOracleJDBCDriverInstallation.htm. You will need a password for the user/schema that you wish to connect to. If you don't have one, then talk to your DBA.
BTW, please remember that no production-type application and data should be used on the public APEX instance.
Maybe your problem is (or was) that you cannot connect via JDBC using the users you administered in your APEX workspace.
It seems to me that APEX users are not regular users for DB connections via JDBC. If my assumption is right, then you need to create database user with sufficient privileges to access the workspace tables.