2 Replies Latest reply on May 2, 2018 1:45 PM by ryan nicosia

    Connecting to Read only DB

    ryan nicosia

      Trying to connect to a read-only DB using the steps at Setting database options - Documentation for BMC Remedy Action Request System 9.1 - BMC Documentation and when we follow those steps using the Java API Driver we are getting The session identifier in the control record is invalid.

       

      Any ideas what we could be doing wrong?  The steps outlined here Runtime configuration - Documentation for BMC Remedy Action Request System 9.1 - BMC Documentation are not that intuitive.

        • 1. Re: Connecting to Read only DB
          ryan nicosia

          LJ LongWing, any ideas?  I think we might be having trouble with the syntax of the Java Driver.

          • 2. Re: Connecting to Read only DB
            ryan nicosia

            For anybody else that runs into this, here are our lessons learned.   If you have Smart Reporting and want to limit your impacts to production, have your DB team setup a read-only copy with async clustering.

             

            1. The AR Server you setup as your data source in Smart Reporting must be version 9.1.02 or newer.  Anything older will not connect to the read-only db

             

            2.  When you run the steps in the BMC documentation via the Java driver, realize there are 3 steps before the "ssi".  You first have to run "init" to initialize it.  You then run "log" to login to the arsystem.  And then "ssp" to set the server port for arserver

             

            3.  Step 2 cannot be done unless your ARSystem is up and running but you don't have to do it until after you connect to the read-only DB

             

            We haven't tested Smart Reporting just  yet but ARSystem is connected without issue and an update made to production is immediately sync'd to the read-only DB so it is real time or near real time.