Ensure you quickstart docker vm is running ( you can check by using below command) https://hub.docker.com/r/cloudera/quickstart/ Launch VM container ( Go to terminal and run ) docker run –hostname=quickstart.cloudera –privileged=true -t -i -v /Users/navnit/Documents/cloudera:/src –publish-all=true -p 8888 cloudera/quickstart /usr/bin/docker-quickstart 2. Run docker ps command to validate if cloudera/quickstart is running… Read More How to copy file from cloudera quickstart docker to local file system ( mac or windows )
Step 1 – Connect to your ec2 instance ( follow below article ) https://learnsqlteam.com/2018/11/30/how-to-connect-aws-ec2-instance-through-terminal/ step 2 – go to /etc – ( cd /etc ) step 3 – edit crontab ( nano crontab ) step 4 – define schedule and command e.g. in this example I am sysning file b/w ec2 instance and s3 bucket… Read More How to enable cron schedule in AWS EC2 instance
Step 1 – Ensure your EC2 instance is running Step 2 – Get EC2 instance name or public ip . Step 3 – Locate your Key Pair ( you must need keypair to connect to AWS services programmatically ) Step 4 – grant sufficient access chmod 400 myKeypair.pem Step 4 – ssh to your ec2… Read More How to connect AWS EC2 instance through terminal
input [a,b,c,d] [b,c] [f,g,h] output a b c d b c f g h with NS AS ( select 1 as n union all select 2 union all select 3 union all select 4 union all select 5 union all select 6 union all select 7 union all select 8 union all select 9… Read More Redshift – How to flatten JSON data in redshift
Issue – Where Replication Agents job Locate Resolution – While troubleshooting replication issue; it’s always good to know which server have which job. In transnational replication scenario. Snapshot agent Log Reader agent Distribution agent If Publisher and Distribution Server is same and you have configured Push subscription; all the job reside Publisher\Distributor server. If Publisher and… Read More Replication – Agents Job Location
Issue – Replication Monitor could not open the Detail Window. Cause – When you have SQL 2012 as a Publisher and distribution as SQL 2014 and when you try to launch replication monitor through SQL 2014; you will get this error message. Resolution – Launch replication monitor through SQL 2012 i.e. Publisher
Issue – Replication Log Reader agent was failing with below error messages. 2018-04-24 19:33:07.854 Status: 32768, code: 53044, text: ‘Validating publisher’. 2018-04-24 19:33:07.873 Status: 4096, code: 20024, text: ‘Initializing’. 2018-04-24 19:33:07.873 The agent is running. Use Replication Monitor to view the details of this agent session. 2018-04-24 19:33:07.879 Status: 0, code: 20011, text: ‘The process… Read More Replication Issue – Cannot execute as the database principal because the principal “dbo” does not exist, this type of principal cannot be impersonated, or you do not have permission.