WebSphere Portal Server migration Issues - Part I - welcome to our blog Techno Live, now we will discuss information about the WebSphere Portal Server migration Issues - Part I, our admins on this blog has been around to collect information you are looking for so that we usakan to display complete information for you, and in this blog, you can also search for other information, ok please continue reading may be easily understood:

This is about : WebSphere Portal Server migration Issues - Part I
And this article : WebSphere Portal Server migration Issues - Part I

WebSphere Portal Server migration Issues - Part I

You've got WebSphere Portal Server 6.x comfortably hooked up to Oracle / Oracle RAC and then someone wants you to move to another Oracle installation (on a different machine possibly).

IBM has told you that all you need to do is export your database and import it into the other installation.

You're confident. You try it. You do a full=y export and do a full=y import into the new database, change your datasources to point to the new oracle instances, check all the connections and everything is fine.... start your server .... and BOOM!

Part I - tells you about this stack trace that you receive:

Unable to locate default library category Error while calling a function retrieveItemsByCMId of PLS data manager.
Unable to locate webContent library category Error while calling a function retrieveItemsByCMId of PLS data manager.
javax.jcr.RepositoryException: Error while calling a function retrieveItemsByCMId of PLS data manager.

What do you do Jack? Don't raise a PMR for one. The answer is simple for this one.
You're DBA has forgotten to check the tablespaces that were involved with the Oracle Instance for the Portal.

You'd need to tell the DBA (should you be so unlucky to have one who couldn't figure this out) to create the following tablespaces BEFORE the import.:

# These are for Oracle RAC. For plain, standalone Oracle, you'd specify the datafile location after the 'datafile' keyword

create tablespace ICMLFQ32 datafile size 300M autoextend on
next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMLNF32 datafile size 25M autoextend on
next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMVFQ04 datafile size 25M autoextend on
next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMSFQ04 datafile size 150M autoextend on
next 10M maxsize UNLIMITED extent management local autoallocate;

create tablespace ICMLSNDX datafile size 10M autoextend on
next 10M maxsize UNLIMITED extent management local autoallocate;

Run the database import again and you'll be fine.

Articles WebSphere Portal Server migration Issues - Part I finished we discussed

A few of our information about the WebSphere Portal Server migration Issues - Part I, I hope you can exploit carefully

No've You've finished reading an article on WebSphere Portal Server migration Issues - Part I and many articles about modern home in our blog this, please read it. and url link of this article is http://liveeconcerts.blogspot.com/2008/06/websphere-portal-server-migration.html Hopefully discussion articles on provide more knowledge about the world of tech gadgets.

Tag :