3 Replies Latest reply: Feb 16, 2013 7:40 AM by EdStevens RSS

    does cloning of database stop dbconsole working

    user4790344
      Hi

      Recently cloned "live" to "test" database but DBID has not been changed on "test" after cloning.

      The "test" version of dbconsole will now not load although the "live" one still does.

      Is this because of the dbid changing?

      regards

      Paul
        • 1. Re: does cloning of database stop dbconsole working
          EricvdS
          Hi Paul,
          You did not give much info to help thinking about a solution.
          Did you clone the db using the same home/ different home/home on an other server, OS, db version, errors?

          You wrote " DBID has not been changed" and you ask if the dbid changing is the reason for not being able to start (=load?) dbconsole.
          If you change the home,server ip adress, SID etc normally you have to recreate the repository.

          Eric
          • 2. Re: does cloning of database stop dbconsole working
            user4790344
            Hi

            No the clone from "live" to "test" was just overwriting the previious "test" data
            but the dbid has been overwritten with the dbid of the "live" db so now live and test have the same dbid.
            This all took place in the same oracle home and on the same server,

            regards

            Paul
            • 3. Re: does cloning of database stop dbconsole working
              EdStevens
              user4790344 wrote:
              Hi

              No the clone from "live" to "test" was just overwriting the previious "test" data
              but the dbid has been overwritten with the dbid of the "live" db so now live and test have the same dbid.
              This all took place in the same oracle home and on the same server,

              regards

              Paul
              Then your 'test' database still has the repository of the 'live' database. The repository is just a bunch of tables under the SYSMAN schema, nothing inherent that would trigger any special action in any type of clone operation. Really, as far as oracle is concerned they are just more application data.

              Also, the dbcontrol configuration is in a directory under ORACLE_HOME that is named after the host.

              Best bet after such a cloning operation is to use emca to drop and recreate the config and repository.