ASA and ASE woes

ASA and ASE woes

Post by Adrian Mui » Fri, 01 Sep 2000 23:15:18



Hi All:
        Hope someone can help with my situation.  I'm eval'ing
Allaire Spectra on Solaris. It sits on top of Coldfusion and
comes bundled with sqlAnywhere to manage its cfaobjects.db

$SQLANY/dbsrv6 -x tcpip -n db1_cfaobjects $DBDIR/cfaobjects.db

But the application omits any of the db tools that come with anywhere:
./               dbeng7*          dbping*          dbvalid*
../              dberase*         dbprdbg*         dbversion*
RionReadme.txt   dbexpand*        dbremote*        dbwrite*
asa_config.csh*  dbinfo*          dbshrink*        dbxtract*
asa_config.sh*   dbinit*          dbspawn*         rebuild*
dbbackup*        dbisql*          dbstop*          run_isqlc*
dbcollat*        dbisqlc*         dbtran*          util_db.ini*
dbconsole*       dblocate*        dbunload*
dbdsn*           dblog*           dbupgrad*

I need to get into cfaobjects and see what's there, so I d/l'd
eval copy of SYBSsa7 to try and use the above tools to peek inside.
Well, dbisql is a java appy that reports font.property errors and wont
display properly; dbisqlc connects to the db fine using the odbc.ini
file that comes with Spectra (copied to my ~) but I have yet to find
a way to display user tables. I tried:
select c.colid, c.name, t.type as type, c.length
from syscolums c, systypes t
where c.usertype = t.usertype
and c.id = ( select id from sysobjects where name = '<tablename>')
order by c.colid

But that didn't work.  Since that machine is a backup db server running
ASE, I went over to my vmware window, installed ASE on it and config'd
dsedit to include the ASA server.  It pinged it OK, but when I tried to
connect to it thru Central, or Adavantage, it failed.
My dbAdmin thinks that because the dbserver is listed under:
+Sybase Central
  +Sybase Adaptive Server Enterprise
        -->Utilities
        +db1

That SybCentral is using Enterprise drivers to try to access an  Anywhere
server, and that i need a plugin for SybCentral. You know, my first hurdle
with Anywhere is that, unlike Enterprise and the Interfaces file, there is
no way to determine the port that the server is listening to.  It may
default to 2638, but if another port is used there is no command
(ping -v is terse) to establish what the port is.  I'm now going to try
and install Anywhere Eval on my linux box and hope that the dbisql java
app works and is more informative than dbisqlc.

Any tips would be greatly appreciated. Please use email replies
TIA
Rion D'Luz

 
 
 

ASA and ASE woes

Post by Anthony Mandi » Sun, 03 Sep 2000 19:28:43


**** Post for FREE via your newsreader at post.usenet.com ****


>         Hope someone can help with my situation.  I'm eval'ing
> Allaire Spectra on Solaris. It sits on top of Coldfusion and
> comes bundled with sqlAnywhere to manage its cfaobjects.db

        I'm surprised that they are using ASA on Solaris rather
        than ASE. Not that there's anything wrong with ASA, but I
        found it a strange beast when compared to ASE. (I once
        downloaded the eval version for Solaris but gave up trying
        to work out how to use it.)

Quote:> But the application omits any of the db tools that come with anywhere:

        Hmmm ... you really ought to take this us with them.

Quote:> My dbAdmin thinks that because the dbserver is listed under:
> +Sybase Central
>   +Sybase Adaptive Server Enterprise

        Yes, you'd want SC to point to an ASA server.

Quote:> That SybCentral is using Enterprise drivers to try to access an  Anywhere
> server, and that i need a plugin for SybCentral. You know, my first hurdle
> with Anywhere is that, unlike Enterprise and the Interfaces file, there is
> no way to determine the port that the server is listening to.  It may
> default to 2638, but if another port is used there is no command
> (ping -v is terse) to establish what the port is.  I'm now going to try
> and install Anywhere Eval on my linux box and hope that the dbisql java
> app works and is more informative than dbisqlc.

        You can most likely work out the port its using on Solaris by
        using "netstat -a". Shut down ASA, run the netstat command, start
        ASA up again and the rerun netstat and check if there is a new
        port being listened on.

-am

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=