Skip to main content

Connect Amazon Redshift using DBeaver

Connect Redshift Database Sever using DBeaver: This is an example of the Mac OS, but it will works on Windows also. the input value and filed name are same for the Mac OS and Windows for DBeaver. In the following connection configuration you don't require to configure Putty tunnel and tunnel configuration as we are opening tunnel using SSH configuration.

Main Tab:

Host/Instance: global-consumer-np-rs.subdomain.domain.com. This is the host name of the database server in AWS cloud. Pay attention to the global, consumer as it is going to consume the data and data is getting ingested using software such as HVR, Talend etc. , np for non production, domain and subdomain can be analytics.exapmple.com 

Port:5439. This is default port for the Amazon Redshift. 

Authentication: Database Native

Username: SSO_ID

Password Database Password: _______  Check the check box to save password locally.

Following is an example of the Main Tab:


 Select  Connection details (name, type button which will enable - Edit Driver Setting button.

Edit Driver Setting screen:

Leave all values on the tab Settings, it is select by default.


Select Driver properties:

If you have downloaded the driver locally on your laptop or desktop in a user defined location, please select it here, by choosing Add File, and then select OK.

Following is an example of Redshift Tab: 

Check the check box for - Show all databases as follows.


Select SSH tab:

Here we are going to configure SSH tunnel. 

Host/ IP: global-consumer-np-bastion.subdomain.domain.com

Port - 22

User Name : Your Linux ID / LDAP ID you got it form the organization. 

Authentication Method : Password

Password : ___________________

Select Test tunnel configuration. This test has to be successful, if it fail, check all the values you have provided.

Select tab SSL:

Check the box - Use SSL. Select Finish.

 


Comments

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...

MySQL slave Error_code: 1032 | MySQL slave drift | HA_ERR_KEY_NOT_FOUND

MySQL slave Error_code: 1032 | MySQL slave drift: With several MySQL, instance with master slave replication, I have one analytics MySQL, environment which is larger in terabytes, compared to other MySQL instances in the environment. Other MySQL instances with terabytes of data are running fine master, slave replication. But this analytics environment get started generating slave Error_code :1032. mysql> show slave status; Near relay log: Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_log_pos 5255306 Near master section: Could not execute Update_rows event on table <db_name>.<table_name>; Can't find record in '<table_name>', Error_code: 1032; Can't find record in '<table_name>', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log <name>-bin.000047, end_l...

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...