This is a discussion on problem in Portal Server 6.0 --- migrating from Cloudscape to DB2 - Websphere ; Hi i have installed portal server 6.0 and i have DB2 8.2 installed ,i have made the changes in wpconfig.properties,wpconfig_dbdomain.properties and wpconfig_dbtype.properties and ran the command WPSconfig.bat create-local-database-db2 -DDbPassword=db2admin and its giving the following error :
5:39:27 PM: adi: Fri ...

problem in Portal Server 6.0 --- migrating from Cloudscape to DB2

Hi i have installed portal server 6.0 and i have DB2 8.2 installed ,i have made the changes in wpconfig.properties,wpconfig_dbdomain.properties and wpconfig_dbtype.properties and ran the command WPSconfig.bat create-local-database-db2 -DDbPassword=db2admin and its giving the following error :

5:39:27 PM: adi: Fri Jun 06 17:36:06 IST 2008

echo Trying to create database for dbdomain 'release' on 'db2'

sqlproc action: exist-database

sqlproc __________________________________________________ _______

sqlproc DbDomain: release

sqlproc Database does not exist and will be created for domain release

exec SQL0104N An unexpected token "PAGESIZE" was found following "UCA400

_NO".

exec Expected tokens may include: "CATALOG". SQLSTATE=42601

exec UPDATE DB CFG FOR wpsdb USING applheapsz 4096

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING app_ctl_heap_sz 1024

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING stmtheap 8192

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING dbheap 2400

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING locklist 1000

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING logfilsiz 1000

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING logprimary 12

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING logsecond 20

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING logbufsz 32

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING avg_appls 5

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

exec UPDATE DB CFG FOR wpsdb USING locktimeout 30

exec SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

BUILD FAILED

file:../config/actions/db_cfg.xml:149: exec returned: 4

Total time: 1 minute 5 seconds

Any Help???

kiran.

Re: problem in Portal Server 6.0 --- migrating from Cloudscape toDB2

Your error message....

SQL1013N The database alias name or database name "WPSDB" could not

be found.

exec SQLSTATE=42705

Is being caused by this error which is previously logged in your post....

CREATE DB wpsdb USING CODESET UTF-8 TERRITORY us COLLATE USING UCA40

0_NO PAGESIZE 8192

exec SQL0104N An unexpected token "PAGESIZE" was found following "UCA400

_NO".

exec Expected tokens may include: "CATALOG". SQLSTATE=42601

This problem is most likely because your version of DB2 does not support the PAGESIZE option in the CREATE DATABASE command. DB2 added support for this option in a later release of DB2. Please confirm with DB2 on further details.