The Platform and Software versions I am using are as follows :
Red Hat Enterprise Linux Server release 7.4 (Maipo)
Microsoft SQL Server 2017 (RTM-CU3-GDR) (KB4052987) - 14.0.3015.40 (X64)
Dec 22 2017 16:13:22
Copyright (C) 2017 Microsoft Corporation Express Edition (64-bit) on
Windows Server 2012 R2 Standard 6.3 <X64> (Build 9600:) (Hypervisor)
I have searched a lot for answers on Google but haven't found any solution yet. I can't connect to RDS instance having MS SQL instance via Linux.
It shows following errors If I try to :
[ec2-user#ip-~]$ sqlcmd -H mssqldb.xxxxxxxxxxxxxx.com -P 1433
-U userXXXXX -P aXXXXXX
-Q 'SELECT TOP 1 [n] FROM [dbbase2].[dbo].[table_people]'
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server :
Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server :
TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 17 for SQL Server :
A network-related or instance-specific error has occurred while
establishing a connection to SQL Server. The server is not found
or not accessible. Check if instance name is correct and if SQL
Server is configured to allow remote connections. For more
information see SQL Server Books Online.
[ec2-user#ip- ~]$ Check if instance name is correct and if SQL Server is
configured to allow remote connections.
Could anyone please tell the issue and resolution ?
Thanks.
Related
I have a linux server OEL 5.8 in which 8 oracle DB instances are running. 4 Db instances are running on Oracle 10.2.0.4 and other 4 on 11.2.0.3. Initially, all the DB instances were running on 10.2.0.4. I upgraded 4 of them to 11.2.0.3. Now the existing linux server is going to be migrated on new location. Server was cloned to the new server location and I got the exact replica of my old server at new location. I was able to start the Oracle 10g DB instances perfectly fine just changing the hostname in tnsnames.ora and listener.ora. However I am unable to start ORacle 11g instances. sqlplus is unable to find the Db instance. $ORACLE_SID, $ORACLE_HOME and $PATH are set to oracle 11g location in environment variables. Pfile exists in $ORACLE_HOME/dbs. But when I try to connect like 'sqlplus / as sysdba' I am unable to find any idle instnace to start.
flow81 > echo $ORACLE_HOME
/dboracle/orabase/product/11.2.0.3
flow81 > echo $PATH
/dboracle/orabase/product/11.2.0.3/bin
flow81 > echo $ORACLE_SID
flow81
flow81 > sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Tue Sep 19 05:58:01 2017
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected.
SQL>
For DB instances in 10g,
fltr81 > sqlplus / as sysdba
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Sep 19 06:00:10 2017
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
SQL> STARTUP
ORACLE instance started.
Total System Global Area 159383552 bytes
Fixed Size 2082464 bytes
Variable Size 113248608 bytes
Database Buffers 37748736 bytes
Redo Buffers 6303744 bytes
Database mounted.
Database Opened.
My question is why sqlplus is unable to find idle instance in oracle 11g to start them?
There was some configuration issue in /etc/hosts. IP was mapped against some different hostname, hence the issue. After mapping IP to correct Hostname issue got resolved.
Its very simply if your Database is already started up, sqlplus will connect to the instance. If instance is not started up, sqlplus will connect to an idle instance by default. Moreover if you want to connect with a specific instance you have to specify #SID_NAME as follows in the sqlplus command
sqlplus / as sysdba#SID
I'm from Linux server background and very new to JBOSS. I'm trying to setup a IoT application server which requires JBOSS service to provide
a web interface for the application server.
But when i check the JBOSS server state it is showing 'starting', i need this to be 'running'.
# /opt/cgms/bin/jboss-cli.sh --connect controller=127.0.0.1 ":read- attribute(name=server-state)"
{
"outcome" => "success",
"result" => "starting"
}
I can see that the deployment is getting failed when i start JBOSS using the script standalone.sh. I've increased the deployment-timeout
up to 6000 seconds in standalone.xml, still the deployment is failing with the following message in /opt/cgms/standalone/deployments/cgms.ear.failed,
""JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [6000 seconds].
Check the server configuration file and the server logs to find more about the status of the deployment."
Here is my JBOSS setup details,
[root#app-server ~]# /opt/cgms/bin/jboss-cli.sh --connect
[standalone#localhost:9999 /] version
JBoss Admin Command-line Interface
JBOSS_HOME: /opt/cgms
JBoss AS release: 7.3.0.Final-redhat-14 "Janus"
JBoss AS product: EAP 6.2.0.GA
JAVA_HOME: null
java.version: 1.8.0_65
java.vm.vendor: Oracle Corporation
java.vm.version: 25.65-b01
os.name: Linux
os.version: 3.10.0-229.el7.x86_64
When i check the server.log, it is stuck at,
# tailf /opt/cgms/server/cgms/log/server.log
624: app-server: Aug 12 2017 05:45:01.506 +0000: %IOTFND-6-UNSPECIFIED: %[ch=StdSchedulerFactory][sev=INFO][tid=MSC service thread 1-1]: Quartz scheduler 'CgnmsQuartz' initialized from an externally provided properties instance.
625: app-server: Aug 12 2017 05:45:01.506 +0000: %IOTFND-6-UNSPECIFIED: %[ch=StdSchedulerFactory][sev=INFO][tid=MSC service thread 1-1]: Quartz scheduler version: 2.2.1
It will not go further from here.
I've tried with java 1.7, but the script standalone.sh failed with a java error,
java.lang.UnsupportedClassVersionError: com/cisco/cgms/loglayout/LogHandler : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:345)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:423)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:261)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:76)
Here are my server details,
OS - Red Hat Enterprise Linux Server release 7.1 (Maipo) - runs on Oracle VM VirtualBox
kernel - app-server 3.10.0-229.el7.x86_64 #1 SMP Thu Jan 29 18:37:38 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
When i check netstat, port 80 and 443 are listening.
Please help to fix this problem.
My DBeaver Enterprise Edition is unable to connect to a remote Cassandra store (2.1.2) on a Unix machine in the same network.It's throwing a NoHostAvailableException- All host(s) tried for query failed. The firewall is down on the Unix machine,the tcp port in cassandra.yaml is 9042 & I am using the same port in the DBeaver Connection configuration. I am also using SSH tunnel in the configuration to connect to the Unix machine.
I could use some help on fixing this problem.
OS: Red Hat 4.1.2-54
Linux 2.6.18-92.el5 #1 SMP Tue Jun 10 18:49:47 EDT 2008 i686 i686 i386 GNU/Linux
Progress OpenEdge Database Release 10.2B on Linux 32 bit
ODBC Driver: pgoe1023.so (which was available with the database package)
export LD_LIBRARY_PATH=/usr/dlc/odbc/lib:/usr/dlc/lib
export ODBCINI=/etc/odbc.ini
isql -v Progress
I am receiving "Segmentation fault" error when trying to use ODBC connection to progress database using isql command.
I have followed the required steps mentioned in this article and installed missing library libstdc++-libc6.2-2.so.3 (with yum install compat-libstdc++-296.i386).
How can I fix it?
I do not see any indication in the kbase article, nor in your post, that a db is running and accepting SQL connections. The kbase is assuming "testdb", port 5555 and a user named "sysprogress" (password "sysprogress" too).
Assuming that you have a "testdb" and that you setup the user you also need to start a server to accept SQL connections. For instance:
proserve testdb -m3 -Ma 5 -Mpb 5 -S 5555 -ServerType SQL -minport 9000 -maxport 9100
Before you try to use it with your isql stuff you can test that this is working with Progress' "sqlexp" command:
sqlexp -user sysprogress -password sysprogress -db testdb -S 5555
If that doesn't work then you have not correctly configured the db to accept SQL connections and downstream utilities, like isql, will not work.
I've configured Oracle wallet successfully in my Linux server(Linux 2.6.32-642.4.2.el6.x86_64 GNU/Linux).
When I try to execute the below command using Database connection string, it works perfect.
$/sqlplus /#TESTDB
SQL*Plus: Release 11.2.0.3.0 Production on Tue Oct 18 07:12:49 2016
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning option
SQL>
But, when I run the same command using sqlplus Instant Client, it's throwing the below error. Please help me to resolve this.
$ oracle/instantclient/11.1.0.6.0-ml01/.exec/x86-64.linux.2.6/bin/sqlplus /#TESTDB
SQL*Plus: Release 11.1.0.6.0 - Production on Tue Oct 18 07:14:38 2016
Copyright (c) 1982, 2007, Oracle. All rights reserved.
ERROR:
ORA-12534: TNS:operation not supported
Note:
Any way, When I use the Instant sqlplus client to connect using username and password, it works fine.
/oracle/instantclient/11.1.0.6.0-ml01/.exec/x86-64.linux.2.6/bin/sqlplus USERNAME/PASSWORD#TESTDB
SQL*Plus: Release 11.1.0.6.0 - Production on Tue Oct 18 07:16:46 2016
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning option
SQL>
You may have to recreate the wallet using the specific environment. For example, my oracle-11 client wallet doesn't work when I have an oracle-12 environment defined ... and vice versa. Neither of my client configs are instant clients, but I think the 'secure external password' (aka wallet) store is specific to the client.