Delphix Products

  • 1.  Problems adding dSource for XEXE demo database - "In use"

    Posted 01-22-2015 03:20:00 PM
    Hi,
    I'm trying to add a dSource to the demo database XEXE (Employee XE DB) but I get 'In use' on the 'Add dSource' dialog of the Delphix management  web GUI.  I tried to shut down the database via telnet/SQLPlus using delphixdb user Id but get "ORA-12547: TNS:lost contact" when trying to connect within SQLPlus.  Any ideas?
    Thanks...
    #DemoEnvironment


  • 2.  RE: Problems adding dSource for XEXE demo database - "In use"

    Posted 01-22-2015 03:45:00 PM
    Hi Adrian,

    It sounds like you might be trying to make another dsource from the same source database but just so I can confirm what is happening can you please provide a screen shot of the GUI showing the "in use" error. 

    Thanks Paul.


  • 3.  RE: Problems adding dSource for XEXE demo database - "In use"

    Posted 01-22-2015 03:54:00 PM



  • 4.  RE: Problems adding dSource for XEXE demo database - "In use"

    Posted 01-22-2015 03:54:00 PM
    Sorry - maybe this is a complete noob error ...


  • 5.  RE: Problems adding dSource for XEXE demo database - "In use"
    Best Answer

    Posted 01-22-2015 04:22:00 PM
    Hi Adrian,

    Thanks for the screen shot, this confirms that you are doing as I suspected. You can only have a single dsource of a source database per Delphix Engine. In the GUI it shows that you have selected to make a dsource from a dsource called XEXE. You can only provision a VDB from a dsource so please have an attempt at this. There are some good videos that show the LandShark(XEXE) installation and how to make you first Vdb. 

    Videos: 
    http://vimeo.com/108463991
    http://vimeo.com/68332834

    I hope these help.

    Regards Paul.


  • 6.  RE: Problems adding dSource for XEXE demo database - "In use"

    Posted 01-22-2015 04:42:00 PM
    Hi - that's great thanks.  Slight oddness - provisioning a VDB leaves the GUI with something wrong - wrong user? So I can't provision a second VDB immediately - refreshing the GUI & going through the steps again seems to work fine though.  Solved! Thanks.