Max Gadget, GPG Dragon Latest Version, Install Android, Sony Xperia, Xiaomi Mi Robot Vacuum, Verizon, Android Marshmallow, Network, stock firmware

Jumat, 13 Juni 2008

WebSphere Portal Server migration Issues - Part I

WebSphere Portal Server migration Issues - Part I - this blog we have built a few years ago and already very many blog visitors Max Gadget who are satisfied with the information we convey and we say thanks for that, we will then improve the quality of information we convey to you, well according to what you are looking for we will now discuss first about WebSphere Portal Server migration Issues - Part I this information we framework from various trusted sources, please see:

Articles : WebSphere Portal Server migration Issues - Part I
full Link : WebSphere Portal Server migration Issues - Part I

You can also see our article on:


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.




so much information WebSphere Portal Server migration Issues - Part I

hopefully the information WebSphere Portal Server migration Issues - Part I that we convey can make you satisfied because it can be useful to determine the gadget according to your needs.

you just read the article titled WebSphere Portal Server migration Issues - Part I if you feel this information is useful and want to bookmark or share please use the link https://maxyaquos.blogspot.com/2008/06/websphere-portal-server-migration.html do not forget to go back to this blog to get more information about gadgets.

Tag :
Share on Facebook
Share on Twitter
Share on Google+
Tags :

Related : WebSphere Portal Server migration Issues - Part I

0 komentar:

Posting Komentar