cancel
Showing results for 
Search instead for 
Did you mean: 

OPSCenter 7.7.1 - dbisqlc - "Database server not found"

mrmadej
Level 4
Partner Accredited

Hi,

I have recently upgraded my OPSC from 7.6.0.3 to 7.7.1.

I've tried to connect to database via 'dbisqlc' and recieved popup with "Database server not found" message.
I think that I gave proper user/pass and database name:

user: DBA
pass: SQL
database name: opscenter_<hostname>

if anyone had such a problem?
Any advice how I can debug the issue?

Regards

Madej

1 ACCEPTED SOLUTION

Accepted Solutions

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

figured it out, you must put opscenter_opscenter in the servername field, not the database field. leave that blank

View solution in original post

11 REPLIES 11

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Is the database server online?

run

opsadmin -monitor

mrmadej
Level 4
Partner Accredited

Yes, I can login to webgui. OPSC is runnig properly.

Command returns (Windows :) :(

c:\Program Files\Symantec\OpsCenter\server\bin>opsadmin.bat -monitor
Invalid arguments
"HELP:opsadmin.bat [ start | stop ]"

Database server service is running:

 

c:\Program Files\Symantec\OpsCenter\server\bin>sc query SQLANYs_VERITAS_OPSCENTE
R

SERVICE_NAME: SQLANYs_VERITAS_OPSCENTER
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

 

Regards

Madej

 

 

areznik
Level 5

If you're trying to connect remotely, check your database's server.conf file (C:\Program Files\Symantec\OpsCenter\server\db\CONF\server.conf) and see if it still has the LocalOnly=NO

If I remember correctly, when I did this upgrade my conf file got reset and I had to recover it. 

If thats not the case, run C:\Program Files\Symantec\OpsCenter\server\db\WIN64\dblocate.exe and make sure it lists your DB. Also, tell us where are you running dbisqlc from?

 

mrmadej
Level 4
Partner Accredited

server.conf file contains:

  -n OPSCENTER_OPSCENTER -x tcpip(LocalOnly=YES;ServerPort=13786) -gd DBA -gk DBA -gl DBA -gp 4096 -ti 0 -c 256M -ch 1024M -cl 256M -zl -os 1M -m  -o "C:\Program Files\Symantec\OpsCenter\server\db\log\server.log" -m

This is default.

But I run dbisqlc localy, so this shouldn't matter.

And dblocate found my database as I expected:

c:\Program Files\Symantec\OpsCenter\server\db\WIN64>dblocate.exe
SQL Anywhere Server Enumeration Utility Version 16.0.0.2095
Server Name           Address
-----------           -------
opscenter_opscenter   opscenter:13786

1 server found

It is strange.

 

Regards

Madej

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Post exactly what you're entering, screenshot please.

mrmadej
Level 4
Partner Accredited

Two screenshots attached.

Regards

Madej

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Put the server name in there too

mrmadej
Level 4
Partner Accredited

c:\Program Files\Symantec\OpsCenter\server\db\WIN64>hostname
opscenter

 

Port 13786 is opened, I can telnet on it.

Before upgrade I could connect without problems in the same way.

Maybe the problem is that I have tested the backup/restore of database using dbbackup command. But I don't think so. Few times I was doing this and always was ok after that.

 

Regards

Madej

 

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

figured it out, you must put opscenter_opscenter in the servername field, not the database field. leave that blank

mrmadej
Level 4
Partner Accredited

:-))))

You're wright. I feel so stupid.

But I am pretty sure I have tested this way.

Thanks and sorry for wasted time.

 

Regards

Madej

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

No problem :)