Unable to install datastage

iskapalli · Post by **iskapalli** » Wed Dec 21, 2011 6:30 am

HI,

We are installing datastage paralle edition 8.5 on redhat linux.There is no DB2 in the target system.so we have given "true" option for metadata repository tier. It should create DB2 dabtase as it is built in.
we are getting below error.
com.ibm.is.install.exception.InstallException: CDIIN3234E: Could not connect to Database.jdbc:db2://localhost:50000/xmeta
ther

qt_ky · Post by **qt_ky** » Thu Dec 22, 2011 11:26 am

Yes, it should install DB2 and create xmeta for you during the setup/install process.

Can your server resolve localhost OK?

Do you see DB2 installed files on the server?

Have you tried connecting to xmeta yourself?

I suggest that you:
1. Gather above information and contact support
2. Consider installing 8.7 instead of 8.5. If it's a new install then this is a good time to go with the newest release availble.

iskapalli · Post by **iskapalli** » Fri Dec 23, 2011 12:32 am

Thanks for your reply.
This is the first timeing I am installing datastage server on redhat linux.
could you pleas explain me what is "Can your server resolve localhost OK?" and how to check this. DB2 is not instaled. I do not know why it is trying to connect with xmeta.

-rw-r--r-- 1 root root 10478 Dec 23 07:07 ISInstall2011.12.23.06.53.38Error.log
-rw-r--r-- 1 root root 1331824 Dec 23 07:07 ISInstall2011.12.23.06.49.54.log
-rw-r--r-- 1 root root 10478 Dec 23 07:26 ISInstall2011.12.23.07.25.32Error.log
-rw-r--r-- 1 root root 1331677 Dec 23 07:26 ISInstall2011.12.23.07.21.33.log
-rw-r--r-- 1 root root 10478 Dec 23 07:54 ISInstall2011.12.23.07.52.36Error.log
-rw-r--r-- 1 root root 1331744 Dec 23 07:55 ISInstall2011.12.23.07.49.21.log
-rw-r--r-- 1 root root 10478 Dec 23 08:22 ISInstall2011.12.23.07.58.24Error.log
-rw-r--r-- 1 root root 1331834 Dec 23 08:22 ISInstall2011.12.23.07.55.11.log
-rw-r--r-- 1 root root 10478 Dec 23 09:31 ISInstall2011.12.23.09.01.28Error.log
-rw-r--r-- 1 root root 1331766 Dec 23 09:31 ISInstall2011.12.23.08.58.20.log
-rw-r--r-- 1 root root 10482 Dec 23 10:50 ISInstall2011.12.23.10.48.13Error.log
-rw-r--r-- 1 root root 1331845 Dec 23 10:50 ISInstall2011.12.23.10.44.54.log
[root@localhost ibm_is_logs]# vi ISInstall2011.12.23.10.48.13Error.log

Dec 23, 2011 10:48:13 AM, SEVERE: com.ibm.is.install.engine.runtime.InstallEngine^M
com.ibm.is.install.exception.InstallException: CDIIN3234E: Could not connect to Database.jdbc:db2://localhost:50000/xmeta
at com.ibm.is.install.core.SQLHelper.createConnection(SQLHelper.java:47)
at com.ibm.is.install.core.SQLHelper.executeFile(SQLHelper.java:167)
at com.ibm.is.install.engine.action.builtin.ExecuteSQLAction.execute(ExecuteSQLAction.java:132)
at com.ibm.is.install.engine.runtime.InstallEngine.executeAction(InstallEngine.java:1318)
at com.ibm.is.install.engine.runtime.InstallEngine.processInstallActionStep(InstallEngine.java:1258)
at com.ibm.is.install.engine.runtime.InstallEngine.processActionStep(InstallEngine.java:1142)
at com.ibm.is.install.engine.runtime.InstallEngine.processInstallStep(InstallEngine.java:333)
at com.ibm.is.install.engine.runtime.InstallEngine.processAllSteps(InstallEngine.java:313)
at com.ibm.is.install.engine.runtime.InstallEngine.run(InstallEngine.java:235)
at com.ibm.is.install.engine.runtime.InstallEngine.execute(InstallEngine.java:626)
at com.ibm.is.install.Installer.execute(Installer.java:195)
at com.ibm.is.install.AbstractInstaller.recoverAndExecutePlan(AbstractInstaller.java:650)
at com.ibm.is.install.AbstractInstaller.execute(AbstractInstaller.java:395)
at com.ibm.is.install.Installer.main(Installer.java:107)
Caused by: com.ibm.db2.jcc.c.DisconnectException: [ibm][db2][jcc][t4][2043][11550] Exception java.net.ConnectException: Error opening socket to server localhost/127.0.0.1 on port 50,000 with message: Connection refused.
at com.ibm.db2.jcc.b.yb.a(yb.java:375)
at com.ibm.db2.jcc.b.yb.<init>(yb.java:76)
at com.ibm.db2.jcc.b.a.v(a.java:254)
at com.ibm.db2.jcc.b.b.a(b.java:1669)
at com.ibm.db2.jcc.c.p.a(p.java:350)
at com.ibm.db2.jcc.c.p.<init>(p.java:404)
at com.ibm.db2.jcc.b.b.<init>(b.java:256)
at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:163)
at com.ibm.is.install.core.SQLHelper.createConnection(SQLHelper.java:43)
... 13 more
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:389)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:250)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:237)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)
at java.net.Socket.connect(Socket.java:543)
at com.ibm.db2.jcc.b.bb.run(bb.java:34)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.ibm.db2.jcc.b.yb.a(yb.java:369)
... 21 more

Dec 23, 2011 10:50:02 AM, SEVERE: com.ibm.is.install.engine.runtime.InstallEngine^M
"ISInstall2011.12.23.10.48.13Error.log" 160L, 10482C

qt_ky · Post by **qt_ky** » Fri Dec 23, 2011 7:24 pm

If you ping localhost from on the server, it should ping to 127.0.0.1. Did you run the install as the root user? My questions are a shot in the dark. The answer to why DB2 failed to install could be in one of the earlier install log files. You've revealed some symptoms from a log file but not the cause. I would suggest you open a new support case send them the log files.

iskapalli · Post by **iskapalli** » Mon Dec 26, 2011 5:34 am

HI, I ping localhost from on the server. it is pinging to 127.0.0.1. yes I am useing root user.

as you said DB2 failed to install could be in one of the earlier install log files. so I want to remove log files and unstall the software.

could you please let me know what are the steps I should do to unstall the software and remove the log files.

Kirtikumar · Post by **Kirtikumar** » Mon Dec 26, 2011 11:03 pm

Did you check if DB2 install is successful or not? From the message it looks like it is failing when connecting to DB2.

iskapalli · Post by **iskapalli** » Tue Dec 27, 2011 3:03 am

DB2 did not install.

Kirtikumar · Post by **Kirtikumar** » Tue Dec 27, 2011 3:09 am

May be it gets installed and then reaches this point where it is trying to connect to DB2. When the connection to DB2 is refused, it roll back the install.

So once install is unsuccessful, you dont see DB2. Did you check other log files to see if DB2 was done or not.

iskapalli · Post by **iskapalli** » Tue Dec 27, 2011 8:07 pm

I am looking into log file.

between from line no.570 to line no.574 in logfile:

Begin: [actionId = update.information.server.port, installUnitId = ISFServer]

End: [actionId = update.information.server.port, installUnitId = ISFServer]

between from line no.575 to line no.2661 in logfile:

Begin: [actionId = copy.isf.server.files, installUnitId = ISFServer]
End: [actionId = copy.isf.server.files, installUnitId = ISFServer]

between from line no.2662 to line no.2670in logfile:

Begin: [actionId = set.isf.server.file.permissions.for.executables, installUnitId = ISFServer]
End: [actionId = set.isf.server.file.permissions.for.executables, installUnitId = ISFServer]

between from line no.2671 to line no.2676 in logfile:

Begin: [actionId = create.was.profile.classes.directory, installUnitId = ISFServer]
End: [actionId = create.was.profile.classes.directory, installUnitId = ISFServer]

between from line no.2677 to line no.3905 in logfile:

Begin: [actionId = copy.xmeta.server.install, installUnitId = ISFServer]
END: [actionId = copy.xmeta.server.install, installUnitId = ISFServer]

between from line no.3906 to line no.3908 in logfile:

Begin: [actionId = create.xmeta.server.zos.install.properties.file, installUnitId = ISFServer]

End: [actionId = create.xmeta.server.zos.install.properties.file, installUnitId = ISFServer]

between from line no.3909 to line no.3911 in logfile:

Begin: [actionId = comment.out.zOS.entries, installUnitId = ISFServer]
End: [actionId = comment.out.zOS.entries, installUnitId = ISFServer]

between from line no.3912 to line no.4009 in logfile:

Begin: [actionId = install.xmeta.server, installUnitId = ISFServer]

2011-12-27T20:57:12.466, INFO: CDIIN4482I: End: [actionId = install.xmeta.server, installUnitId = ISFServer]

between from line no.4010 to line no.4014 in logfile:

Begin: [actionId = delete.xmeta.server.install, installUnitId = ISFServer]

End: [actionId = delete.xmeta.server.install, installUnitId = ISFServer]

rm -rf /tmp/ibm_is_temp.2011.12.27.20.54.00/xmeta, env = null, workingDir =null
20

from line no.4010

Begin: [actionId = create.xmeta.tables, installUnitId = ISFServer]

Here I am getting below error

2011-12-27T21:00:15.415, SEVERE: com.ibm.is.install.engine.runtime.InstallEngine
com.ibm.is.install.exception.InstallException: CDIIN3234E: Could not connect to Database.jdbc:db2://localhost:50000/xmeta

My understanding is xmeta database has been created. Final it is deleteing.I think becuase of this it is unable to connect.

is it correct? if yes what could be reason?

iskapalli · Post by **iskapalli** » Tue Dec 27, 2011 8:16 pm

Hi,

Here I am attaching the response file as well. I am useing only IBMDB2(plugin). not useing any database apart from DB2.

#################################################################################################################
# suite.installLocation is the absolute directory path to where InfoSphere Information Server is to be installed
#################################################################################################################
suite.installLocation=/opt/IBM/InformationServer

#################################################################################################################
# LIC_AGREEMENT is for license agreement. Use ACCEPT to accept the license agreement.
#################################################################################################################
LIC_AGREEMENT=ACCEPT

#################################################################################################################
#Tier selection
#################################################################################################################
# suite.tier[database.tier].selected=[true|false]
# Set to true if the Repository tier is to be installed.
suite.tier[database.tier].selected=true

# suite.tier[app.server.tier].selected=[true|false]
# Set to true if the Services tier is to be installed.
suite.tier[app.server.tier].selected=true

# suite.tier[enginee.tier].selected=[true|false]
# Set to true if the Engine tier is to be installed.
suite.tier[engine.tier].selected=true

#################################################################################################################
#Product selection
#################################################################################################################
# product[metadata.server].selected=[true|false]
# Set to true if the InfoSphere Metadata Server is to be installed.
product[metadata.server].selected=true

# product[datastage].selected=[true|false]
# Set to true if InfoSphere DataStage is to be installed.
product[datastage].selected=true

# product[qualitystage].selected=[true|false]
# Set to true if InfoSphere QualityStage is to be installed.
product[qualitystage].selected=true

# product[InformationAnalyzer].selected=[true|false]
# Set to true if InfoSphere Information Analyzer is to be installed.
product[InformationAnalyzer].selected=false

# product[BusinessGlossary].selected=[true|false]
# Set to true if InfoSphere Business Glossary is to be installed.
product[BusinessGlossary].selected=false

# product[BusinessGlossaryAnywhere].selected=[true|false]
# Set to true if InfoSphere Business Glossary Anywhere is to be installed.
product[BusinessGlossaryAnywhere].selected=false

# product[MetadataWorkbench].selected=[true|false]
# Set to true if InfoSphere Metadata Workbench is to be installed.
product[MetadataWorkbench].selected=false

# product[ISTools].selected=[true|false]
# Set to true if InfoSphere Information Server Manager is to be installed. Installed by default in the GUI.
product[ISTools].selected=true

# product[FastTrack].selected=[true|false]
# Set to true if InfoSphere FastTrack is to be installed.
product[FastTrack].selected=false

# product[WISD].selected=[true|false]
# Set to true if WebSphere Information Services Director is to be installed.
product[WISD].selected=false

#################################################################################################################
#Variable setting
#################################################################################################################
## DataStage Features
# DataStage=[true|false]
# Set to true if the IBM InfoSphere DataStage feature is to be installed. Note that the core DataStage feature is needed to support Information Analyzer.
DataStage=true

# DataStage.BalOp=[true|false]
# Set to true if the IBM InfoSphere DataStage Balance Optimization feature is to be installed.
DataStage.BalOp=false

# DataStage.MVS=[true|false]
# Set to true if the IBM InfoSphere DataStage MVS Edition feature is to be installed.
DataStage.MVS=false

# DataStage.SAS=[true|false]
# Set to true if the IBM InfoSphere DataStage Pack for SAS feature is to be installed.
DataStage.SAS=false

# DataStage.Server=[true|false]
# Set to true if the IBM InfoSphere DataStage Server Edition feature is to be installed.
DataStage.Server=true

## Application Server options
# allow.customize.was.profile.ports=[true|false]
# Set to true if you specifying the WebSphere ports instead of installing with the defaults
allow.customize.was.profile.ports=false

# app.server.password=
# Set to the password for the Application Server administrator
app.server.password=iiswas123

# app.server.type=[was|cos|weblogic]
# Set to the type of application server that is being configured:
# was = WebSphere Application Server
# cos = Cosminexus Application Server
# weblogic = WebLogic Application Server
app.server.type=was

# app.server.user=
# Set to the user ID for the webserver adminstrator ID. This ID will be created in the local repository for authentication.
app.server.user=wasadmin

## Database options
#db2.admin.group.name=
# Set to DB2 administrator group name
db2.admin.group.name=dasadm

#db2.admin.home.directory=
# Set to DB2 administraor home dirictory
db2.admin.home.directory=/home/dasusr

# db2.admin.user.name=
# Set to the operating system ID to be used as the DB2 administrator ID
db2.admin.user.name=db2admin

# db2.admin.user.password
# Set to the password for the DB2 administrator ID
db2.admin.user.password=iisdb2123

#db2.fenced.group.name=
# Set to the db2 fenced group name
db2.fenced.group.name=db2fadm

#db2.fenced.home.directory=
# Set to the db2 fenced home directory
db2.fenced.home.directory=/home/db2fenc1

#db2.fenced.user.name=
# Set to the db2 fenced user name
db2.fenced.user.name=db2fenc5

#db2.fenced.user.password=
# Set to the db2 fenced user password
db2.fenced.user.password=iisdbfn5

# db2.install.location={absolute path}
# Set to the absolute path where DB2 is to be installed
db2.install.location=/opt/IBM/db2

#db2.instance.group=
# Set to the groupname of the instance
db2.instance.group=db2iadm

#db2.instance.home.directory=
# Set to directory of the instance
db2.instance.home.directory=/home/db2inst5

# db2.instance.name={ unique DB2 instance name }
# Set to a string that will identify the DB2 instance. The DB2INSTANCE environment variable will be set to this by default.
db2.instance.name=DB2

#db2.instance.user.name=
# Set to the username of the instance
db2.instance.user.name=db2inst5

#db2.instance.user.password=
# Set to the password of instance user
db2.instance.user.password=iisdb2ins

# db2.port.number= #####
# Set to the TCPIP port for this DB2 instance. Default is 50000.
db2.port.number=50000

#ds.admin.uid=
# Set to the datastage admin username
ds.admin.uid=dsadmin

# ds.client.language.acronym={language code}
# Set to language code for DB2 clients. English is always included. The two letter upper case country code is used for non-English.
ds.client.language.acronym=ENU

## DataStage Project settings
# ds.project.#.name={project name}
# Replace the # with the incrementing number starting with 1 of the project to be created for DataStage. Set the value to the project name desired.
ds.project.1.name=EFBIDEV

# ds.project.#.path={absolute path to project files}
# Replace the # with the incrementing number starting with 1 of the project to be created for DataStage. Set the value to the path to the project files.
ds.project.1.path=/opt/IBM/InformationServer/Server/Projects/EFBIDEV

# ds.project.#.version=[New]
# Replace the # with the incrementing number starting with 1 of the project to be created for DataStage. Set the value to New for this release.
ds.project.1.version=New

#ds.rpc.instance.tag=
# Set to the datastage rpc instance tag
ds.rpc.instance.tag=ade

#dsrpc.port=#####
# Set to the datastage dsrpc port. Default port is 31538
dsrpc.port=31538

## Information Analyzer database settings - repository installation version
# ia.db.hostname={hostname of target installation system}
# Set to the Information Analyzer database server name
ia.db.hostname=localhost

# ia.db.location=/opt/IBM/InformationServer/Repos/iadb
# Set to path where the database will be stored
ia.db.location=/opt/IBM/InformationServer/Repos/iadb

# ia.db.name=iadb
# Set to name of the Information Analyzer database to be created
ia.db.name=iadb

# ia.db.password=
# Set to the password for the Information Analyzer database owner
ia.db.password=iadb123

# ia.db.port=#####
# Set to the port for the DB2 instance where the database is to be created. Note that this must equal db2.port.number if this is a repository install and the Information Analyzer database is to be created in the local DB2 instance.
ia.db.port=50000

# ia.db.type=[db2|db2zos|oracle|sqlserver]
# Set to database type for the Information Analyzer database
# db2=IBM DB2 Database for Linux, UNIX, and Windows
# db2zos=DB2 for z/OS
# oracle=Oracle
# sqlserver=Microsoft SQL Server
ia.db.type=db2

# ia.db.username
# Set to the operating system ID to be used as the Information Analyzer database owner ID
ia.db.username=iauser

# install.path=[1|2|3|4|5|6]
# Set to 1 = Fresh Install
# 2 = Add Product
# 3 = Add Tier
# 4 = Remove Product
# 5 = Remove Tier
# 6 = Uninstall
install.path=1

# is.admin.password=
# Set to the password for the Information Server Adminstrator ID.
is.admin.password=<CHANGE_TO_YOUR_PASSWORD>

# is.admin.user
# Set to the user name that you want for the Information Server Administrator ID. This ID will be created in the local repository.
is.admin.user=admin

# is.ha.selected=[true|false]
# Set to true if this is an active-passive server cluster configuration installation. Default is false.
is.ha.selected=false

# is.sas.selected=[true|false]
is.sas.selected=false

# is.was.cluster=[true|false]
# Set to true if you are installing into a WebSphere Application Server cluster configuration
is.was.cluster=false

# isf.agent.port=#####
# Set to the port number for the Information Server Agent. Default is 31531.
isf.agent.port=31531

# jobmon.port.1=#####
# Set to the port number for the first job monitor port. Default is 13400.
jobmon.port.1=13400

# jobmon.port.2=#####
# Set to the port number for the second job monitor port. Default is 13401.
jobmon.port.2=13401

# logging.agent.port=#####
# Set to the port number for the Logging Agent. Default is 31533
logging.agent.port=31533

# mq.install.choice=[NONE|SERVER|CLIENT]
# Set to SERVER if you want to install the MQ Series Server plug-in and CLIENT if you want to install the MQ Series Client plug-in.
# The default is NONE. The MQ Series plug-ins are only recommended for existing jobs. WebSphere MQ Connector is recommended for new jobs.
mq.install.choice=NONE

# nls.enabled=[true|false]
# Set to true if you want globalization support for InfoSphere DataStage and InfoSphere QualityStage.
# Default is true. false is only supported for systems with an nls.language set to English and a supported system code page.
nls.enabled=true

# nls.language=[English|Chinese-Simplified|Chinese-Traditional|French|German|Italian|Japanese|Korean|Portuguese-Brazilian|Spanish|Thai|Turkish]
# Set to the language that InfoSphere DataStage and QualityStage will be configured for. The install computer code page must be compatible and supported by DataStage.
# English is the default.
nls.language=English

# nls.language.code=[ENU|FRA|PTB|JPN|ITA|KOR|DEU|CHT|CHS|ESP]
# Set to three letter language code for InfoSphere DataStage and InfoSphere QualityStage support
nls.language.code=ENU

# target.country.code=[US|FR|BR|JP|IT|KR|DE|TW|CN|ES]
# Set to two letter country code for the locale for the IInfoSphere DataStage and InfoSphere QualityStage component installation.
target.country.code=US

# target.language.code=[en|fr|pt_BR|ja|it|ko|de|zh_TW|zh|es]
# Set to language code for the locale for the IInfoSphere DataStage and InfoSphere QualityStage component installation.
target.language.code=en

# use.bundled.db2=[true|false]
# Install the DB2 that is bundled in the IBM InfoSphere Information Server Suite
use.bundled.db2=true

# use.bundled.was=[true|false]
# Install the WebSphere Application Server ND that is bundled in the IBM InfoSphere Information Server Suite
use.bundled.was=true

# was.admin.host.port=####
# Set to port number for WebSphere Administrative console port. Default is 9060.
was.admin.host.port=9060

# was.bootstrap.port=####
# Set to port number for WebSphere Bootstrap port. Default is 2809.
was.bootstrap.port=12809

# was.dcs.unicast.port=####
# Set to port number for WebSphere high availability manager communication port. Default is 9353.
was.dcs.unicast.port=9353

# was.default.host.port=####
# Set to port number for the HTTP transport port. Default is 9080.
was.default.host.port=9080

# was.install.location={absolute path to install WebSphere}
# Default is /opt/IBM/WebSphere/AppServer. The directory must be empty.
was.install.location=/opt/IBM/WebSphere/AppServer

# was.mutual.auth.listener.port=####
# Set to port number for WebSphere Bootstrap port. Default is 2809.
was.mutual.auth.listener.port=9402

# was.orb.listener.port=####
# Set to port number for WebSphere ORB listening port. Default is 9100.
#was.orb.listener.port=9100
was.orb.listener.port=19100

# was.sas.ssl.port=####
# Set to port number for SAS SSL Server Authentication listener. Default is 9401.
was.sas.ssl.port=9401

# was.secure.admin.host.port=####
# Set to port number for the secure WebSphere Administrator console. Default is 9043.
was.secure.admin.host.port=9043

# was.secure.default.host.port=####
# Set to port number for the default secure HTTP transport port. Default is 9443.
was.secure.default.host.port=9443

# was.secure.mib.mq.port=####
# Set to port number for the secure service integration MQ interoperability port. Default is 5578.
was.secure.sib.mq.port=5578

# was.secure.port=####
# Set to port number for the secure service integration port. Default is 7286.
was.secure.sib.port=7286

# was.server.auth.listener.port=####
# Set to port number for the CSIV2 server authentication port. Default is 9403.
was.server.auth.listener.port=9403

# was.sib.mib.port=####
# Set to port number for the service integration MQ interoperability port. Default is 5558.
was.sib.mq.port=5558

# was.sib.port=####
# Set to port number for the service integration port. Default is 7276.
was.sib.port=7276

# was.sip.port=####
# Set to port number for the SIP port. Default is 5060.
#was.sip.port=5060
was.sip.port=15060

# was.sip.secured.port=####
# Set to port number for the secured SIP port. Default is 5061.
#was.sip.secured.port=5061
was.sip.secured.port=15061

# was.soap.connector.port=####
# Set to port number for the SOAP connector port. Default is 8880.
#was.soap.connector.port=8880
was.soap.connector.port=18880

## Metadata Repository variables
# xmeta.db.collection= {DB2 JDBC collection}
# Set to collection name for DB2 JDBC collection. Used for DB2 z/OS. Default is NULL.
xmeta.db.collection=

# xmeta.db.hostname= {hostname}
# Set to hostname for the database server.
xmeta.db.hostname=localhost

# xmeta.db.location= {path}
# Set to the path of the drive where you want the metadata repository database to be created on.
xmeta.db.location=/opt/IBM/InformationServer/Repos/xmeta

# xmeta.db.name= {database name}
# Set to the database name for the metadata repository.
xmeta.db.name=xmeta

# xmeta.db.password=
# Set to the password for the metadata repository database owner.
xmeta.db.password=iisxmeta123

# xmeta.db.port=#####
# Set to the port for the DB2 instance where the database is to be created. Note that this must equal db2.port.number if this is a repository install and the Information Analyzer database is to be created in the local DB2 instance.
xmeta.db.port=50000

# xmeta.db.tablespace={tablespace name for DB2 z/OS}
# Set to the tablespace name created on the DB2 z/OS database. This field is ignored for other databases.
xmeta.db.tablespace=

# xmeta.db.username=#####
# Set to the operating system ID to be used as the metadata repository database owner ID.
xmeta.db.username=xmeta

qt_ky · Post by **qt_ky** » Tue Dec 27, 2011 9:39 pm

I suggest you mask out passwords on forums.

According to the response file, you should find most DB2 files and directories created under this path:

db2.install.location=/opt/IBM/db2

Plus some files and directories under this path:

db2.instance.home.directory=/home/db2inst5

With default database name of xmeta.

I did not see any cause for failure on the log files you posted.

If db2inst5 is your DB2 instance owner, then you should be able to telnet and login with that ID and run DB2 commands, like the db2 command line.

I would still suggest sending all the install log files to support to find out what went wrong.

Kirtikumar · Post by **Kirtikumar** » Tue Dec 27, 2011 10:54 pm

I have done one install and that was on Oracle. My current install is done by actual DS admin group.

I was just going through the logs and what I saw was - host name mentioned was actual machine name. So rather than localhost, the name of the server (which comes from command uname -n) is used.

May be you can give it a try with this if not tried already.

iskapalli · Post by **iskapalli** » Fri Dec 30, 2011 5:29 am

for installing DB2 rpm -ivh IBM_db2cc81-8.1.0-0.i386.rpm software need to be installed. Is it corect?. why because I try to run the below command I am getting error.
db2 -stf create_xmeta_db.sql
-bash: db2: command not found.

because of this It is unable to install db2. can you please conform this?

iskapalli · Post by **iskapalli** » Fri Dec 30, 2011 6:18 am

datastage internally it is executing create_xmeta_db.sh script.
inside the script it is executing below commands.

db2set DB2_INLIST_TO_NLJN=YES
db2set DB2_USE_ALTERNATE_PAGE_CLEANING=ON
db2set DB2_REDUCED_OPTIMIZATION=YES

it is unable to run above commands. it is showing error commond not found.

in my box(redhat linux box) IBM_db2cc81-8.1.0-0.i386.rpm software is missing. how to check it whether this software exists in my box.

PaulVL · Post by **PaulVL** » Fri Dec 30, 2011 9:56 am

Did you ensure that you updated your PATH with the DB2 install path? Can you make sure that db2set command works from your shell?