Re: Exporting WebDB to a new Server

Hi!

[Quoted] WebDB hold it's components data in WebDB shema.

To export my own components I used the component export script (Reports - then click on component name - Manage - Export - Save as sql file). Then it's possible to make some changes in script and run it as Webdb with SQLPlus.

This metod is useful when you have fiew reports/charts etc. (but I read that there are some bug's with menus).

The other solution is export some WebDB shema data, but I haven't tried it.

UrRa

Mark Hills wrote:
>
> Hi Jacquie,
>
> Did you ever make any progress on this issue?? I now find myself in a
> similar situation.
>
> Many TIA,
> Mark Hills.
>
> Jacquie Armstrong <jacquieNOSPAM_at_softtracks.com> wrote in message
> news:38c44b71_at_rsl2.rslnet.net...
> >
> > Hello all,
> >
> > I am experiencing a problem moving a webdb application to a new server.
> >
> > I have a schema for the website (MYSITE) which I imported over to the new
> > server using the sbimport and sbexport described on the webdb CD. I also
> have
> > a schema in which all of my reports were created (DEVELOPER) and yet
> another
> > schema for all of the tables and data (TESTDATA). I exported/imported the
> > DEVELOPER schema using the Oracle Enterprise manager Data Manager, but
> when I
> > try to edit the components on the new server using WebDB, they are not
> listed
> > in the available components. Is there any special order that these
> Schemas
> > need to be exported? I'm assuming that the only schema that can be
> exported
> > using the sbimport and spexport is the MYSITE schema. Am I correct in
> assuming
> > this? Does anybody know how I can successfully port the whole application
> to
> > the new server???
> >
> > Any help would be greatly appreciated,
> > Jacquie.
> >
Received on Wed Mar 22 2000 - 12:06:59 CET