Wednesday, November 22, 2006

Export Portal schema and move to another db

OK, so I admit this is very esoteric, but if you ever need to move a Portal schema by using export/import (e.g., you are changing database operating system), you may run into this problem... (I'll try to put up a more comprehensive "how to" later, but thought this little issue deserved its own spot.) In the meantime, we have done a bunch of these moves. If you need some help, click on the C2 Consulting link to the right.

The solution is right in the documentation
but if you miss it, the errors are not too helpful.

You get a servlet error

Servlet Error

An unexpected servlet error was encountered.

Please check the log file for more details.

In the log file
you will see the following:

06/11/22 09:43:41 portal: [module=PortalServlet, ecid=92635952220,1] ERROR: oracle.webdb.repository.service.RepositoryServiceException: Unable to obtain Portal Repository version.

Search all through metalink and on the web and it will likely tell you that your PORTAL schema password is wrong. Well, that might be true, but once you find it isn't wrong, log in as either PORTAL, sys or system and run the following command:


Bounce everything. I'm interested in finding out if this helps anyone. If it does, leave a comment.




Ivan said...

No, it didnt work. Schema wasnt exported/imported. Only it survived two portal/oiddas expirations. Nevertheless i could log on with portal to run this command.

Anton Nielsen said...

Give me a little more info and maybe I can help. I'm not sure what you mean by "Schema wasnt exported/imported. Only it survived two portal/oiddas expirations."

If you did not do an export/import, what did you do to cause it to stop working?

Anonymous said...

yep...sure helps cause we're doing just that
thanks a lot

Tom Fite said...

Thanks so much for putting this up! I ran into the exact same issue after changing the portal schema password and I was completely stumped. Wouldn't have thought about your solution!

Anonymous said...

I tried this but didn't work. So I checked ldap.ora on the midtier and there was a mistake (wrong hostname) so I changed it to the correct one and restarted the midtier. All working now. :-)

There's not a lot of information about this on MetaLink

Thomas Isaksen