Hi Friends,
Am trying to install IBM Infosphere Information Server v8.1 in windows env. But am getting the following issues. Kindly let me know how to proceed further. Thank You!
My Hardware:
Windows XP 2002 SP3/ 1gb ram / 75 gb harddisk
Error:
This is the error am getting at 5% of installation. I have supplied all the username and password of db2/iauser/isadmin/wasadmin and all.
In the error log i could also see this...
SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 CREATE TEMPORARY TABLESPACE XMETATEMP IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 2 BUFFERPOOL XMETA FILE SYSTEM CACHING
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 COMMENT ON TABLESPACE XMETATEMP IS '32 page swap'
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command.
Detailed error LOG:(error code = 601; message="ERepositoryInstaller65514: An error occurred creating the metadata repository database. For details, see the log file: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ibm_is_logs\ISInstall2011.06.17.17.40.54.log.")
Jun 17, 2011 6:13:02 PM , INFO: com.ibm.is.install.core.WindowsFileService deleteFile: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\configure_db2.log
Jun 17, 2011 6:13:02 PM , INFO: com.ascential.acs.installer.asb.InstallRepositoryAction command = db2 -tvf C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\configure_db2_95.sql -l C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\configure_db2.log, Jun 17, DB20000I The CREATE DATABASE command completed successfully.
UPDATE DBM CFG USING QUERY_HEAP_SZ 4096 IMMEDIATE
DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
were not changed dynamically. Client changes will not be effective until the
next time the application is started or the TERMINATE command has been issued.
Server changes will not be effective until the next DB2START command.
successfully.
SQL1362W One or more of the parameters submitted for immediate modification were not changed dynamically. Client changes will not be effective until thenext time the application is started or the TERMINATE command has been issued.
Server changes will not be effective until the next DB2START command.
UPDATE DBM CFG USING agent_stack_sz 256 IMMEDIATE
DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
successfully.
SQL1362W One or more of the parameters submitted for immediate modification
were not changed dynamically. Client changes will not be effective until the
next time the application is started or the TERMINATE command has been issued.
Server changes will not be effective until the next DB2START command.
UPDATE DATABASE CONFIGURATION FOR xmeta USING AVG_APPLS 5 IMMEDIATE
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DB CFG FOR xmeta USING DATABASE_MEMORY 250000
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DB CFG FOR xmeta USING LOCKLIST 20000
SQL5146W "MAXLOCKS" must be set to "MANUAL" when "LOCKLIST" is "MANUAL".
"MAXLOCKS" has been set to "MANUAL".
UPDATE DB CFG FOR xmeta USING MAXLOCKS 60
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DATABASE CONFIGURATION FOR xmeta USING SHEAPTHRES_SHR AUTOMATIC
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGBUFSZ 2048 IMMEDIATE
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGFILSIZ 5000
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGPRIMARY 50
CONNECT TO xmeta
SQL1084C Shared memory segments cannot be allocated. SQLSTATE=57019
GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON DATABASE TO USER xmeta
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
COMMIT WORK
SQL1024N A database connection does not exist. SQLSTATE=08003
CREATE BUFFERPOOL XMETA IMMEDIATE SIZE 8000 AUTOMATIC PAGESIZE 32 K
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
CREATE REGULAR TABLESPACE XMETA IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 500 M INCREASESIZE 10 PERCENT MAXSIZE NONE EXTENTSIZE 2 BUFFERPOOL XMETA FILE SYSTEM CACHING DROPPED TABLE RECOVERY ON
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
COMMIT WORK
SQL1024N A database connection does not exist. SQLSTATE=08003
CREATE TEMPORARY TABLESPACE XMETATEMP IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 2 BUFFERPOOL XMETA FILE SYSTEM CACHING
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
COMMENT ON TABLESPACE XMETATEMP IS '32 page swap'
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL1024N A database connection does not exist. SQLSTATE=08003
COMMIT WORK
SQL1024N A database connection does not exist. SQLSTATE=08003
CONNECT RESET
SQL1024N A database connection does not exist. SQLSTATE=08003
TERMINATE
DB20000I The TERMINATE command completed successfully.
Jun 17, 2011 6:13:36 PM , INFO: com.ascential.acs.installer.asb.InstallRepositoryAction IRepositoryInstaller65641: Return Value: 6
Jun 17, 2011 6:13:36 PM , INFO: com.ascential.acs.installer.asb.InstallRepositoryAction #################### Start of configure_db2.log ####################
06/17/2011 18:13:04 CREATE DATABASE xmeta ON 'C:\' ALIAS xmeta USING CODESET UTF-8 TERRITORY US COLLATE USING IDENTITY DFT_EXTENT_SZ 2 USER TABLESPACE MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 500 M INCREASESIZE 10 PERCENT MAXSIZE NONE
06/17/2011 18:13:35 DB20000I The CREATE DATABASE command completed successfully.
06/17/2011 18:13:35 UPDATE DBM CFG USING QUERY_HEAP_SZ 4096 IMMEDIATE
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
06/17/2011 18:13:35 SQL1362W One or more of the parameters submitted for immediate modification were not changed dynamically. Client changes will not be effective until the next time the application is started or the TERMINATE command has been issued. Server changes will not be effective until the next DB2START command.
06/17/2011 18:13:35 UPDATE DBM CFG USING ASLHEAPSZ 1024 IMMEDIATE
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
06/17/2011 18:13:35 SQL1362W One or more of the parameters submitted for immediate modification were not changed dynamically. Client changes will not be effective until the next time the application is started or the TERMINATE command has been issued. Server changes will not be effective until the next DB2START command.
06/17/2011 18:13:35 UPDATE DBM CFG USING agent_stack_sz 256 IMMEDIATE
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
06/17/2011 18:13:35 SQL1362W One or more of the parameters submitted for immediate modification were not changed dynamically. Client changes will not be effective until the next time the application is started or the TERMINATE command has been issued. Server changes will not be effective until the next DB2START command.
06/17/2011 18:13:35 UPDATE DBM CFG USING DFT_MON_TIMESTAMP OFF IMMEDIATE
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed successfully.
06/17/2011 18:13:35 UPDATE DATABASE CONFIGURATION FOR xmeta USING AVG_APPLS 5 IMMEDIATE
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:35 UPDATE DB CFG FOR xmeta USING DATABASE_MEMORY 250000
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:35 UPDATE DB CFG FOR xmeta USING LOCKLIST 20000
06/17/2011 18:13:35 SQL5146W "MAXLOCKS" must be set to "MANUAL" when "LOCKLIST" is "MANUAL". "MAXLOCKS" has been set to "MANUAL".
06/17/2011 18:13:35 UPDATE DB CFG FOR xmeta USING MAXLOCKS 60
06/17/2011 18:13:35 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:35 UPDATE DATABASE CONFIGURATION FOR xmeta USING SHEAPTHRES_SHR AUTOMATIC
06/17/2011 18:13:36 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:36 UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGBUFSZ 2048 IMMEDIATE
06/17/2011 18:13:36 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:36 UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGFILSIZ 5000
06/17/2011 18:13:36 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:36 UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGPRIMARY 50
06/17/2011 18:13:36 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:36 UPDATE DATABASE CONFIGURATION FOR xmeta USING LOGSECOND 200
06/17/2011 18:13:36 DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
06/17/2011 18:13:36 CONNECT TO xmeta
06/17/2011 18:13:36 SQL1084C Shared memory segments cannot be allocated. SQLSTATE=57019
06/17/2011 18:13:36 GRANT DBADM,CREATETAB,BINDADD,CONNECT,CREATE_NOT_FENCED_ROUTINE,IMPLICIT_SCHEMA,LOAD,CREATE_EXTERNAL_ROUTINE,QUIESCE_CONNECT ON DATABASE TO USER xmeta
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 COMMIT WORK
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 CREATE BUFFERPOOL XMETA IMMEDIATE SIZE 8000 AUTOMATIC PAGESIZE 32 K
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 CREATE REGULAR TABLESPACE XMETA IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE AUTORESIZE YES INITIALSIZE 500 M INCREASESIZE 10 PERCENT MAXSIZE NONE EXTENTSIZE 2 BUFFERPOOL XMETA FILE SYSTEM CACHING DROPPED TABLE RECOVERY ON
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 COMMIT WORK
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 CREATE TEMPORARY TABLESPACE XMETATEMP IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32768 MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 2 BUFFERPOOL XMETA FILE SYSTEM CACHING
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 COMMENT ON TABLESPACE XMETATEMP IS '32 page swap'
06/17/2011 18:13:36 DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned:
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 COMMIT WORK
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 CONNECT RESET
06/17/2011 18:13:36 SQL1024N A database connection does not exist. SQLSTATE=08003
06/17/2011 18:13:36 TERMINATE
06/17/2011 18:13:36 DB20000I The TERMINATE command completed successfully.
Jun 17, 2011 6:13:36 PM , INFO: com.ascential.acs.installer.asb.InstallRepositoryAction #################### End of configure_db2.log ####################
Jun 17, 2011 6:15:12 PM , SEVERE: com.ascential.acs.installer.utils.ProductActionUtil
ProductException: (error code = 601; message="ERepositoryInstaller65514: An error occurred creating the metadata repository database. For details, see the log file: C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\ibm_is_logs\ISInstall2011.06.17.17.40.54.log.")
at com.ascential.acs.installer.utils.ProductActionUtil.showUserMessage(ProductActionUtil.java:48)
Installation Issues in V8.1
Moderators: chulett, rschirm, roy
