I configured source and target endpoint for DMS services, The migration I need to perform is from EC2 to Oracle RDS using AWS DMS and both are 12c.
I am testing the source end point and I am getting this error
Endpoint identifier
Replication instance
Status
Failure message
ec2-172-31-6-111
test-dms-oracle
failed
Error Details: [errType=ERROR_RESPONSE, status=1022307, errMessage=ORA-12514: TNS:listener does not currently know of service requested in connect descriptor OCI error., errDetails=]
I don't feel this occurs because of Network error since, I tried testing the connection with all ports open. And I can able to access the DB within EC2
please refer the screenshot
Please help me to find the solution.
ORA-12514 could mean either of
a. The SERVICE_NAME in the TNSNAMES.ORA or Connect-String does not match the Database Service Name
b. The Listener is running on a non-default port and the database instance does not have LOCAL_LISTENER configured to the listener (thus the instance does not update the listener with its service name)
Run LSNRCTL STATUS and LSNRCTL SERVICES on the database server to verify the running services.
Hemant K Chitale
Related
While connecting to Oracle 19c database from Java 8 client code, I got error -
ORA-28040: No matching authentication protocol exception
This was resolved by adding SQLNET.ALLOWED_LOGON_VERSION=8 in sqlnet.ora file.
Now, when I connect to AWS oracle RDS instance from code running in EC2 instance (RDS and java application running in same subnet), result in same error. Is there an option to add parameter(SQLNET.ALLOWED_LOGON_VERSION=8) in AWS Oracle RDS instance? How can resolve this issue?
You can set some SQLNET parameters in Oracle RDS by modifying sqlnetora.sqlnet.allowed_logon_version_server and sqlnetora.sqlnet.allowed_logon_version_client in your parameter group. (I assume you will then have to restart the database, but I haven't tested changing those values.)
I am using following Command to connect oracle cloud instance 19c using Oracle Cloud Shell
sqlplus username/password#db
It shows following error
SQL*Plus: Release 19.0.0.0.0 - Production on *******
Version 19.5.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
ERROR:
ORA-12154: TNS:could not resolve the connect identifier specified
Depending on the type of Database you have in OCI, you can connect from Cloud Shell to that database via a Service Gateway.
https://docs.cloud.oracle.com/en-us/iaas/Content/Network/Tasks/servicegateway.htm
Both Cloud Shell and Cloud Infrastructure Databases (such as Autonomous Transaction Processing database) can be accessed via a Service Gateway without using the public internet.
https://www.oracle.com/cloud/networking/service-gateway.html
The Cloud Shell isn't connected to your VCNs - it will need to access your database through internet. For this to happen, you'll need to open your database's listener port to the internet, and this is a "VERY BAD IDEA" generally speaking.
Best is to create a VM instance in the same VCN and connect to the DB from the VM.
If you want to eliminate all the intermediate layers for your test, even the local VCN network, then you can connect directly to the DB node using ssh and emit your select from there.
Here's a quick how-to guide on how to connect your on-prem SQL Dev tool to Oracle Cloud Database. https://www.youtube.com/watch?v=3bJ3JlpGlPo&list=PLdtXkK5KBY56jDbMevAMIbZGVAGUz9aYQ&index=14 You can create a bastion session, use ssh port forwarding to connect your local DB tools to cloud database instance using DB listener port for sqlnet.
While connecting to Oracle 12c database from Java 8 client code, I got error -"ORA-28040: No matching authentication protocol exception" This was resolved by adding SQLNET.ALLOWED_LOGON_VERSION=8 in sqlnet.ora file.
Now, when I connect to AWS oracle RDS instance from code running in EC2 instance (RDS and java application running in same subnet), result in same error. Is there an option to add parameter(SQLNET.ALLOWED_LOGON_VERSION=8) in AWS Oracle RDS instance? How can resolve this issue?
The AWS docs list the params you can alter for your needs.
sqlnetora.sqlnet.allowed_logon_version_client
sqlnetora.sqlnet.allowed_logon_version_server
I suggest you to play with those.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ModifyInstance.Oracle.sqlnet.html
I can't start up the TNSListener Service.
The problem is(Google Translate):
The service on the local computer stops after startup. Some services
will automatically stop when not used by other services or programs
I searched on the internet.
Changing listener.ora and tnsnames.ora HOST parameter is not helping.
lsnrctl status says: Unable to OpenSCManager: err=5. TNS-12560 and TNS-00350.
Regedit is not helping.
When I installed Oracle 12c the first time, it's working, but after restarted, the listener can't be started.
I'm using win10x64.
By the way, sql plus can connect to the database, but PL/SQL Developer can't.
Thank you.
been trying to configure an ADO.NET connection for my Visual Studio application but I am running into issues and having no luck at all troubleshooting them. The major error that I run into is:
A network-related or instance-specific error occurred while establishing a connection to SQL server. The server was not found or not accessible. Verify the instance name is correct and that SQL server is configured to allow remote connections (Error 40: Could not open connection to the SQL server)
The steps I undertook to troubleshoot this are:
1. Open up Sql server configuration manager and under the SQL Server Network Configuration, Protocols for MSSQLSERVER,SQLExpress, SQL server 2008 connection string data source I enable each of the protocol names (Shared memory, Named pipes,TCP/IP,VIA)
As instructed I stop the SQL server services first under the SQL server services nodes.
Now I click start, MSSQL server service starts but both SQL Server 2008 and SQLEXPRESS agents do not. Stating the following:
The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details
This might just be the problem as when I attempt to create the connection string , the server name specified is MYWORLD/SQL SERVER 2008. Since the SQL server 2008 agent service refuses to start, the connection fails, leading to the first error message.
Does anybody have any leads on this and can let me know the necessary steps to mitigate this.
The SQL Browser service must be running to connect to a named instance.
Use SQL Servr Configuration Manager under Configuration Tools under Microsot SQL Server 2008 to assign the logon accounts for each service you want to run. Do NOT use any other method to assign user accounts because the correct rights will not be enabled.