I am trying to migrate the Portal Cloudscape database to DB2. The
environment is:

Portal 5.0.2
DB2 7.2 FP9
AIX 5.2.0.2
p670

During the cloudscape export phase I get the following warning message
during each file export:

"Cloudscape is attempting to boot the database even though Cloudscape
may still be active. Only one instance of Cloudscape should boot a
database at a time. Severe and non-recoverable corruption can result
and may have already occurred"

I have stooped all Java processes, and even rebooted but still get
these messages. Job runs to end and gives Build Successful message
with 217 files exported. Job took over 20 minutes to run. I have
successfully done this on XP without warning messages and the job ran
in 7 minutes.

The local database build script ran without error.

I then ran the script to import into DB2 with the following error:

"cannot read /usr/websphere/portalserver/config/dbtransfer/wps/wpcpdb2insert
.sql
java.io.filenotfoundexception:
/usr/websphere/portalserver/config/dbtransfer/wps/wpcpdb2insert.sql (a
file or directory in the path name does not exist)"

This is correct since that directory does not contain any sql files.

So this process works on XP but not AIX.

Any ideas?

[ Post a follow-up to this message ]

Ray,
I have seen this Cloudscape error before although not in the context of
a migration from Cloudscape to DB/2.
This seems to happen when the locks to the use of the Cloudscape
database do not get cleared up correctly. If you are sure no application
accesses the Cloudscape database (when portal server is stopped), you
can try and delete the file <PortalServer>/cloudscape/wps50/db.lck
This file keeps track of locking the database access when a application
started the database. If this file does not get cleaned up correctly,
this could result in the error message you posted.

Oliver


Ray Harrison wrote:
>
> I am trying to migrate the Portal Cloudscape database to DB2. The
> environment is:
>
> Portal 5.0.2
> DB2 7.2 FP9
> AIX 5.2.0.2
> p670
>
> During the cloudscape export phase I get the following warning message
> during each file export:
>
> "Cloudscape is attempting to boot the database even though Cloudscape
> may still be active. Only one instance of Cloudscape should boot a
> database at a time. Severe and non-recoverable corruption can result
> and may have already occurred"
>
> I have stooped all Java processes, and even rebooted but still get
> these messages. Job runs to end and gives Build Successful message
> with 217 files exported. Job took over 20 minutes to run. I have
> successfully done this on XP without warning messages and the job ran
> in 7 minutes.
>
> The local database build script ran without error.
>
> I then ran the script to import into DB2 with the following error:
>
> "cannot read /usr/websphere/portalserver/config/dbtransfer/wps/wpcpdb2inse
rt.sql
>  java.io.filenotfoundexception:
> /usr/websphere/portalserver/config/dbtransfer/wps/wpcpdb2insert.sql (a
> file or directory in the path name does not exist)"
>
> This is correct since that directory does not contain any sql files.
>
> So this process works on XP but not AIX.
>
> Any ideas?

[ Post a follow-up to this message ]

Thanks for the advice, Oliver.

It sounded logical, but unfortunately did not solve my problem.

Oliver Meyer <meyer_oliver@gmx.de> wrote in message news:<406C31E2.EA0B7B2E@gmx.de>...[colo
r=darkred]
> Ray,
> I have seen this Cloudscape error before although not in the context of
> a migration from Cloudscape to DB/2.
> This seems to happen when the locks to the use of the Cloudscape
> database do not get cleared up correctly. If you are sure no application
> accesses the Cloudscape database (when portal server is stopped), you
> can try and delete the file <PortalServer>/cloudscape/wps50/db.lck
> This file keeps track of locking the database access when a application
> started the database. If this file does not get cleaned up correctly,
> this could result in the error message you posted.
>
> Oliver
>
>
> Ray Harrison wrote: 

[ Post a follow-up to this message ]

Hi! i had the same problem but on redhat 8

I exported the database (exporting 217 files)
then when i tried to import to DB2 i had a [WCM.SCHEEMA].LOCKS (or something like that) m
issing. and then the error you said.

i solved the problem by adding this lines on wpconfig.properties file:

WpcpSchema=wpcp50
WpcpDbSchema=wpcp50
FeedbackSchema=fdbk50
FeedbackDbSchema=fdbk50

the names correspond to the names of the databases on the DB2 server.

by adding theese lines it exported 218 files and imported to DB2 just fine.

hope this works!

quote:
Originally posted by Ray Harrison 
Thanks for the advice, Oliver.

It sounded logical, but unfortunately did not solve my problem.

Oliver Meyer <meyer_oliver@gmx.de> wrote in message news:<406C31E2.EA0B7B2E@gmx.de>...[colo
r=darkred]
> Ray,
> I have seen this Cloudscape error before although not in the context of
> a migration from Cloudscape to DB/2.
> This seems to happen when the locks to the use of the Cloudscape
> database do not get cleared up correctly. If you are sure no application
> accesses the Cloudscape database (when portal server is stopped), you
> can try and delete the file <PortalServer>/cloudscape/wps50/db.lck
> This file keeps track of locking the database access when a application
> started the database. If this file does not get cleaned up correctly,
> this could result in the error message you posted.
>
> Oliver
>
>
> Ray Harrison wrote: 

[ Post a follow-up to this message ]

i remembered that i run the action wpcpconfig.
./WPSconfig.sh wpcpconfig 

and then i had the 218 items

quote:
Originally posted by pApe! 
Hi! i had the same problem but on redhat 8

I exported the database (exporting 217 files)
then when i tried to import to DB2 i had a [WCM.SCHEEMA].LOCKS (or something like that) m
issing. and then the error you said.

i solved the problem by adding this lines on wpconfig.properties file:

WpcpSchema=wpcp50
WpcpDbSchema=wpcp50
FeedbackSchema=fdbk50
FeedbackDbSchema=fdbk50

the names correspond to the names of the databases on the DB2 server.

by adding theese lines it exported 218 files and imported to DB2 just fine.

hope this works! 

[ Post a follow-up to this message ]

Hi,

I had the same challenge installing on SuSE Linux. To solve it I took my backup of the 
original wpconfig.properties file and edited like stated in the Infocenter http://
publib.boulder.ibm.c...pf/cfg_db2.html

Do not(!) change any other values than described in the table!
Then the script run without errors.

[ Post a follow-up to this message ]