New WebSphere Portal Server migration Issues - Part I By Patricbensen - is the information you are looking for, and in the blog All Specs Gadget we have provided her, all right in this article titled New WebSphere Portal Server migration Issues - Part I By Patricbensen we will discuss it in full, in addition to the information we have also provided a lot of info about the latest gadgets and a wide range of tips and tricks that according to the gadget you are using, well please continue reading:

Articles: New WebSphere Portal Server migration Issues - Part I By Patricbensen
Full Link : New WebSphere Portal Server migration Issues - Part I By Patricbensen
Artikel IBM, Artikel tips and tricks,

New WebSphere Portal Server migration Issues - Part I By Patricbensen

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.

Information New WebSphere Portal Server migration Issues - Part I By Patricbensen has finished we discussed

says the article New WebSphere Portal Server migration Issues - Part I By Patricbensen, we beharap be useful to you in finding repensi about the latest gadgets and long.

Information on New WebSphere Portal Server migration Issues - Part I By Patricbensen has finished you read this article and have the link https://patricbensen.blogspot.com/2008/06/new-websphere-portal-server-migration.html Hopefully the info we deliver is able to address the information needs of the present.