cancel
Showing results for 
Search instead for 
Did you mean: 

how to start and login to utility_db on windows?

Former Member
0 Kudos

I have started the utility_db from command line using this statement:

C:\ProgramData\SybaseIQ\demo\> start_iq -n utility_db -gu utility_db -iqmt 256


I can see on the popup window, that the process gets started.

I can see that it listens to the default port: 2638

And I am able to see that in the task manager.


But if I try to connect to the database; it fails.


C:\ProgramData\SybaseIQ\demo>@echo|dbisql -nogui -c "UID=dba;pwd=sql;dbn=utility_db;eng=utility_db" "restore database 'iqdemo' from 'C:\iq.bkp';"

Could not connect to the database.

Data source name not found and no default driver specified

SQLCODE=0, ODBC 3 State="IM002"

Could not connect to the database.

Data source name not found and no default driver specified

SQLCODE=0, ODBC 3 State="IM002"

You are not connected to a database.

C:\ProgramData\SybaseIQ\demo>

Can anyone guide me what I am doing wrong?

Regards Tomas

Accepted Solutions (0)

Answers (3)

Answers (3)

c_baker
Employee
Employee
0 Kudos

Tomas,

The correct group for this post is the SAP IQ group:

http://scn.sap.com/community/iq

For now, check your that you have a util_db.ini defined with the correct password:

Defining the Utility Database Password

or try changing -gu to 'DBA'

As you are in Windows, you can also run dbisql as a gui and connect to the utility_db to run your restore command interactively to see if there is an error.  By default, the restored database and dbspace files will be placed exactly where they were backed up from.

Chris

Laszlo_B
Active Contributor
0 Kudos

Dear Tomas,

based on the problem description the Space could help more quickly.

Alternatively, Space could also be useful (if such a Sybase version is used).

Regards,

Laszlo

Former Member
0 Kudos

Is this forum alive?it must be easy for you expert to help me just get connection to utility_db

Former Member
0 Kudos

Thanks for all replies.


The problem was a conflict with SQL Anywhere and IQ Server installed on same labb server.

I uninstalled SQL Anywhere; and reinstalled IQ Server, after that it worked.

Regards Tomas