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

Oracle Goldengate Extract, Pump, and Replicat

-
This is just a quick demonstration of setting up extract, pump, and replicate. I prefer to edit the prm files at OS level, but we can also do GGSCI> edit param esource to enter the vi mode to create the prm file. Here are the sample prm files used in the demonstration: prm files: -------------------------------- Source: (2 processes) ~~~~~~~~~~~~~~~~ esource.prm ~~~~~~~~~ EXTRACT ESOURCE SETENV (ORACLE_SID=source) SETENV (ORACLE_HOME="/source/app/oracle/product/11.2.0.3") userid ggg, password ggg EXTTRAIL /ggSource/app/goldengate/product/12.1.0/dirdat/es --Resolves the TABLES to be replicated when they first encounter a dml operation WILDCARDRESOLVE DYNAMIC --Reduce the system I/O overhead of redolog reads EOFDELAY 5 TABLE mine.table; psource.prm ~~~~~~~~~ EXTRACT PDWDSPRD SETENV (ORACLE_SID=source) SETENV (ORACLE_HOME="/source/app/oracle/product/11.2.0.3") userid ggg, password ggg RMTHOST targetServer.example.net, MGRPO...
Read more

MongoDB Ops Manager Basic Installation and Configuration

-
Image
This post is just a quick guide of MongoDB Ops Manager basic installation and configuration. The bare minimum of getting an instance of MongoDB Ops Manager up and running. We will be working with the latest version of the OpsManager, release version 3.4.7. Prerequisite: To start fresh, we remove any mongodb related RPM. I had Mongod installed as well, therefore, I have extras to be removed. [root@msdlva-dsnops01 ~]# yum autoremove $(rpm -qva | grep mongo) Loaded plugins: langpacks, product-id, rhnplugin, search-disabled-repos, subscription-manager This system is receiving updates from RHN Classic or Red Hat Satellite. Resolving Dependencies --> Running transaction check ---> Package mongodb-enterprise.x86_64 0:3.4.6-1.el7 will be erased ---> Package mongodb-enterprise-mongos.x86_64 0:3.4.6-1.el7 will be erased ---> Package mongodb-enterprise-server.x86_64 0:3.4.6-1.el7 will be erased ---> Package mongodb-enterprise-shell.x86_64 0:3.4.6-1.el7 will be erased...
Read more