MongoDB BI Connector Uninstallation and Installation

-
This is a quick guide to uninstall and install any version of mongodb bi connector:


First Identify the mongosqld is indeed present on this box.

[root@msdlva-dsnavl04 ~]# mongosqld --version
mongosqld version v2.2.0-rc0
git version: eface8f89d6b65fba09d831d6471b527ab508ab0


Identify where the mongosqld is installed

[root@msdlva-dsnavl04 apps]# which mongosqld
/usr/local/bin/mongosqld


Mongosqld is usally installed with mongodrdl, therefore, we can just identify them by running

[root@msdlva-dsnavl04 ~]# ls /usr/local/bin | grep mongo
mongodrdl
mongosqld

or we can simply do 
which mongodrdl, and we can find where the mongodrdl is installed


Remove binaries

[root@msdlva-dsnavl04 ~]# rm -r /usr/local/bin/mongo*
rm: remove regular file ‘/usr/local/bin/mongodrdl’? y
rm: remove regular file ‘/usr/local/bin/mongosqld’? y


Download the versions you desire and copy onto the server. 

I want to work with version 2.0, 


tar -xvf mongodb-bi-linux-x86_64-rhel70-v2.0.1.tgz
mongodb-bi-linux-x86_64-rhel70-v2.0.1/LICENSE
mongodb-bi-linux-x86_64-rhel70-v2.0.1/README
mongodb-bi-linux-x86_64-rhel70-v2.0.1/THIRD-PARTY-NOTICES
mongodb-bi-linux-x86_64-rhel70-v2.0.1/bin/mongosqld
mongodb-bi-linux-x86_64-rhel70-v2.0.1/bin/mongodrdl

then 

install -m755 mongodb-bi-linux-x86_64-rhel70-v2.0.1/bin/mongo* /usr/local/bin

Verify:

[root@msdlva-dsnavl04 apps]# which mongosqld
/usr/local/bin/mongosqld
[root@msdlva-dsnavl04 apps]# mongosqld --version
mongosqld version v2.0.1


Start mongosqld:

mongosqld --addr=10.155.208.169:3307 --schema=/apps/personnel_status.drdl --mongo-uri mongodb://xxx/?replicaSet=yyy --logPath /apps/biLog/mongoBI.log --sslPEMKeyFile=/apps/certs/mongodb.pem --sslAllowInvalidCertificates --auth --verbose=5 &


[root@msdlva-dsnavl04 apps]# ps -ef | grep mongosqld
root     16226 14799  0 12:49 pts/1    00:00:00
mongosqld --addr=10.155.208.169:3307 --schema=/apps/personnel_status.drdl --mongo-uri mongodb://xxx/?replicaSet=yyy --logPath /apps/biLog/mongoBI.log --sslPEMKeyFile=/apps/certs/mongodb.pem --sslAllowInvalidCertificates --auth --verbose=5


Note: I have done everything in root for convenience sake, mongodb recommend to do this as dedicated mongodb user.

Comments

  1. Azure DevOpsSeptember 15, 2018 at 12:12 AM

    Thanks for posting such a great article.you done a great job.
    MEAN Stack Training in Hyderabad

    ReplyDelete
  2. kavyasriDecember 19, 2019 at 1:37 AM


    Thank you for sharing this information and Very good looking blog...

    Mean stack online training
    Mean stack training in hyderabad

    ReplyDelete
  3. Sowmiya RJuly 25, 2020 at 2:08 AM

    Nice article I was impressed by seeing this blog, it was very interesting and it is Thanks for sharing all the information with us all.very useful for me.wonderful article. Very interesting to read this article.I would like to thank you for the efforts you had made for writing this awesome article.

    oracle training in chennai

    oracle training institute in chennai

    oracle training in bangalore

    oracle training in hyderabad

    oracle training

    oracle online training

    hadoop training in chennai

    hadoop training in bangalore

    ReplyDelete
  4. UnknownFebruary 11, 2021 at 1:56 AM

    hanks for sharing amazing information.Gain the knowledge and hands-on experience

    Mongodb Training in Bangalore

    ReplyDelete

Post a Comment

Popular posts from this blog

MongoDB tip: 4 ways to modify replica set configuration

-
This is just a quick guide on how to modify your replica set settings in 4 different ways. This guide is assuming you have a functional replica set ready, it doesn't matter if it's a single node or multi-node replica set. In each of the four method, I am looking to modify the priority of the _id=0 node Method 1: Via Mongo Shell Login to your Mongo shell,  simply type in mongo , assuming default port is being used and authentication is not enabled [in Mongo shell] cfg = rs.conf() cfg.members[0].priority=99 rs.reconfig(cfg) # "ok":1 indicates the new configuration has been set  MongoDB Enterprise minvera:PRIMARY> rs.reconfig(cfg) {         "ok" : 1,         "operationTime" : Timestamp(1528464949, 1),         "$clusterTime" : {                 "clusterTime" : Timestamp(1528464949, 1),                 "signature" : {                         "hash" : BinData(0
Read more

MongoDB Quick Note: BI Connector Issue

-
This is just a quick note of what can stop mongosqld from working properly that I wasn't aware of. Background: My work runs everything mongodb inside of docker containers, so sometimes it's not as straight forward to see immediately of what's preventing your container from working properly What happened: I ran into issue that my container does not stay up after I updated my drdl to reflect new fields introduced to the underlying collection. How to debug: Go to the host server, copy out entrypoint.sh and add sleep 100000000 to before mongosqld is executed. This force the container to stay up for us to look into issue. Cause of the issue: When I updated the drdl, I used tab instead of space, which is causing the mongsqld to error out Fix: Just replace tab with space and everything is back to normal
Read more

MongoDB Tips: Kill long running processes

-
This is just a quick and simple script to find all active opid that has been running over 10 seconds and they are running against the databases and collections you can specify in the "ns" filter. It's best to first run db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["equipment.detachment","personnel.detail","personnel.unavailability","personnel.detachment"]}    } ).inprog.forEach(function (doc) { print(doc.opid); }) and verify your output before you execute the kill command in my experience to make sure you are killing the processes that are meant to be killed. Once verifed, simply run: db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["<db1>.<col1>","<db2>.<col2>","<dbn>.<coln>
Read more