Hi
Am getting following erro while executing craete database command


SQL0104N An unexpected token "/home/vcminst/vcmdata/syscatalog" was found
following "(". Expected tokens may include: "<character-string>".
SQLSTATE=42601


here is the Command i have given ( from os prompt)

db2 create database vcmdb on '/home/vcminst' using codeset IBM-1252 \
> territory US collate using system catalog tablespace managed by \
> system using \('/home/vcminst/vcmdata/syscatalog'\) user tablespace \
> managed by database using \( file '/home/vcminst/vcmdata/userdata_02' 128000, file '/home/vcminst/vcmdata/userdata_02' 128000 \) \
> temporary tablespace managed by system \
> using \('home/vcminst/vcmdata/temp'\) with 'DB for test

any help is appreciated.

Why don't you generate the script using the Control Center. You can submit the script or save the script and submit it through the command line.

Escape single quote characters

Put the command is double quote

Mujeeb

Thx for the replies.

I got another error while trying to start the Admin server

i have given the follwoing command
$db2admin start

and got the following error

SQL4401C The DB2 Administration Server encountered an error during startup.

checked the db2dasdiag.log , here is the log contents


2005-02-01-14.14.37.145340 pid:24572 tid:1 level:2
DB2 tools - DB2 administration server - createDasRrmQueues() probe:20
called OSSHIPCQueue::attach()
return code 0x9000005C The specified message queue ID already exists for the key parameter

2005-02-01-14.17.56.110936 pid:25098 tid:1 level:2
DB2 tools - DB2 administration server - createDasRrmQueues() probe:20
called OSSHIPCQueue::attach()
return code 0x9000005C The specified message queue ID already exists for the key parameter

2005-02-01-14.54.37.071139 pid:1519 tid:1 level:2
DB2 tools - DB2 administration server - readRrmSqlca() probe:20
called OSSHIPCQueue::get()
return code 0x90000013 Time out

-- this is repeated several times.


Quick response is appreciated

Thx

Check your shared structure , using

ipcs -l

first try to stop the admin process, If it is not already stopped.
The clean the keys that belong to admin user, using

ipcrm /// check the man page.

You can drop the admin instance and create a new one.


regards

Mujeeb