Learning by Doing

//Redo last command as Sudo sudo !! //Create a super fast RAM disk  👍 [root@msdlvd-dsnavl02 ~]# mkdir -p /mnt/ram [root@msdlvd-dsnavl02 ~]# mount -t tmpfs tmpfs /mnt/ram -o size=1024M [root@msdlvd-dsnavl02 ~]# mkdir /data/ram [root@msdlvd-dsnavl02 ~]# cd /data/ram [root@msdlvd-dsnavl02 ram]# dd if=/dev/zero of=test.iso bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 3.00793 s, 349 MB/s [root@msdlvd-dsnavl02 ram]# rm test.iso rm: remove regular file ‘test.iso’? y [root@msdlvd-dsnavl02 ram]# cd /mnt/ram [root@msdlvd-dsnavl02 ram]# dd if=/dev/zero of=test.iso bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB) copied, 0.594687 s, 1.8 GB/s //not in history, don't add your previously ran command in history, leave a leading space before command  ls -al

I ran into some issue with goldengate where it's not taking any of the update statement, they are all sent directly to ignore when we ran view param we see this statement, basically this is handling all the issue with update and send update statement to ignore count when the process thinks it cannot handle the update statement. REPERROR (1403, IGNORE) I then commented that line and restarted the replicat process. Upon starting the process, I encountered the following 2019-08-01 12:33:45  WARNING OGG-01004  Aborted grouped transaction on AVL_RPT_FOD.ALERT_MTS_SALT, Database error 1403 (OCI Error ORA-01403: no data found, SQL <UPDATE "AVL_RPT_FOD"."ALERT_MTS_SALT" x SET x."STATUS_ID" = :a9,x."FACILITY_TYPE_ID" = :a10,x."START_DATE" = :a11,x."END_DATE" = :a12,x."WEB_MERCATOR_X" = :a13,x."WEB_MERCATOR_Y" = :a14,x."FACILITY_NAME" = :a15 WHERE x."ID" = :b0>). 2019-08-01 12...

tar with progress bar tar cf - /folder-with-big-files -P | pv -s $(du -sb /folder-with-big-files | awk '{print $1}') | gzip > big-files.tar.gz to install pv first we need to add the repo create /etc/yum.repos.d/ivarch.repo : [ivarch] name=RPMs from ivarch.com baseurl=http://www.ivarch.com/programs/rpms/$basearch/ enabled=1 gpgcheck=1 import public key rpm --import http://www.ivarch.com/personal/public-key.txt yum install pv -y trying it out

We have installed and configured multiple monitoring agent to communicate with OpsManager, however, there can only be one active Monitoring Agent at a time. It's good to have multiple monitoring agent because OpsManager is able to switch over to the remaining monitoring agent automatically when the "Active" agent fails. The lightening shape under type indicates they are monitoring agent and note how one is active and one is standby. To switch to another, we need to go to the host where the monitoring agent is running and run  sudo systemctl stop mongodb-mms-monitoring-agent.service Run the folllowing to make sure it's stopped, it will take a few second for the standby monitoring agent to now become active sudo systemctl status mongodb-mms-monitoring-agent.service ● mongodb-mms-monitoring-agent.service - MongoDB MMS Monitoring Agent    Loaded: loaded (/etc/systemd/system/mongodb-mms-monitoring-agent.service; disabled; vendor preset: disa...