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...

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(...

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...