SQL Anywhere for Linux - ASA 9.0.0 and RHEL 3.4

Author

ASA 9.0.0 and RHEL 3.4

Oliver Schulze L.

2005-05-17, 3:23 am

Hi,
I'm writing regarding running ASA 9.0.0 on RedHat Linux
Enterprise 3.4

The problem I have is that the server does not start to listen
on the network.

The last message I got is:
Starting database "example" (/example.db) at Sat May 14 2005 15:40

So, no network information is printed, also, no port is
listed while listing all listen port of the server:
$ netstat -tunl

What could be the problem?

Many thanks
Oliver

Mauro Bertapelle

2005-05-17, 7:23 am

Oliver Schulze L. ha scritto:
> Hi,
> I'm writing regarding running ASA 9.0.0 on RedHat Linux
> Enterprise 3.4
>
> The problem I have is that the server does not start to listen
> on the network.
>
> The last message I got is:
> Starting database "example" (/example.db) at Sat May 14 2005 15:40
>
> So, no network information is printed, also, no port is
> listed while listing all listen port of the server:
> $ netstat -tunl
>
> What could be the problem?
>
> Many thanks
> Oliver
news://forums.sybase.com:119/3fe0401b@forums-2-dub

Greg Fenton

2005-05-17, 9:23 am

Oliver Schulze L. wrote:
>
> The last message I got is:
> Starting database "example" (/example.db) at Sat May 14 2005 15:40
>

As I asked in the general newsgroup:

Can you show us the exact command line you are using to start the engine?

Is the process running? (use the command "ps -ef | grep db")

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Mark Culp

2005-05-17, 8:23 pm

Note that ASA 9.0.0 was release before RH ES 3, and has not been
tested on this platform...

in fact, I believe I remember that we had to make changes in order to
get ASA to run / startup on this distro (since Linux keeps changing things
and is particular not very good at making things upward compatible).

You will need to get the 9.0.2 maintenance patch to be able to run
ASA on RH ES 3.

Go to http://downloads.sybase.com, click on SQLAnywhere and choose the
Linux x86 maintenance 9.0.x to 9.0.2 patch
--
Mark Culp
SQLAnywhere Research and Development
-------------------------------------------------------------------------
** Whitepapers, TechDocs, bug fixes are all available through the **
** iAnywhere Developer Community at http://www.ianywhere.com/developer **
-------------------------------------------------------------------------

"Oliver Schulze L." wrote:
>
> Hi,
> I'm writing regarding running ASA 9.0.0 on RedHat Linux
> Enterprise 3.4
>
> The problem I have is that the server does not start to listen
> on the network.
>
> The last message I got is:
> Starting database "example" (/example.db) at Sat May 14 2005 15:40
>
> So, no network information is printed, also, no port is
> listed while listing all listen port of the server:
> $ netstat -tunl
>
> What could be the problem?
>
> Many thanks
> Oliver

Oliver Schulze L.

2005-05-17, 8:23 pm

Hi Greg,
sorry for the delay. Here is the command:

dbsrv9 -ud -c 16M -x " tcpip(ServerPort=264
0)" -n Example
/DATABASES/example.db &

This command is executed as rood and after all Sybase
environment variables has been set.

Thanks
Oliver

Greg Fenton wrote:
> Oliver Schulze L. wrote:
>
>
> As I asked in the general newsgroup:
>
> Can you show us the exact command line you are using to start the engine?
>
> Is the process running? (use the command "ps -ef | grep db")
>
> greg.fenton

Oliver Schulze L.

2005-05-17, 8:23 pm

Hi Mark,
I will download the patch and start the tests.

The problem is that this developer does not like to
upgrade. Don't know why people don't want to upgrade.

I always upgrade to latest maintenance patchs from
Sybase.

With this info, I can tell the developer to upgrade
and to please certify his product to run in ASA 9.0.2

Thanks,
Oliver

Mark Culp wrote:[color=darkred
]
> Note that ASA 9.0.0 was release before RH ES 3, and has not been
> tested on this platform...
>
> in fact, I believe I remember that we had to make changes in order to
> get ASA to run / startup on this distro (since Linux keeps changing things
> and is particular not very good at making things upward compatible).
>
> You will need to get the 9.0.2 maintenance patch to be able to run
> ASA on RH ES 3.
>
> Go to http://downloads.sybase.com, click on SQLAnywhere and choose the
> Linux x86 maintenance 9.0.x to 9.0.2 patch
> --
> Mark Culp
> SQLAnywhere Research and Development
> -------------------------------------------------------------------------
> ** Whitepapers, TechDocs, bug fixes are all available through the **
> ** iAnywhere Developer Community at http://www.ianywhere.com/developer **
> -------------------------------------------------------------------------
>
> "Oliver Schulze L." wrote:
>

Mauro Bertapelle

2005-05-18, 3:23 am

Olivier,

this has been discussed some months ago in this newsgroup:
[color=darkred]
> Thanks to the two people that sent me strace output - it appears that there
> is a problem in the call to io_getevents() that is causing the problem.
> We are investigating the issue further.
>
> In the meantime, you can tell the engine to disable asynchronous I/O (i.e.
> the calls to io_getevents) by adding the -ua switch to your engine start line.
>
> - Mark
>
> Mark Culp wrote:
>

Mark Culp

2005-05-18, 9:23 am

BTW: On a somewhat different topic (from the one in this thread...)
I noticed that you are adding a '&' to the end of your command line.
Note that this is not recommended, generally will not work, and is not the
correct way to put the server into the background.
BUT you happen to also be adding -ud to your list of switches, which is the
correct way to start a daemon server process, and therefore you are getting
away with the '&' at the end.

The problem with just using '&' is that it does let the server know that
it should be a daemon and therefore (without the -ud) it will attempt to read
from stdin (i.e. to get the response for "Press Q to quit") and therefore
will halt the server process as soon as it issues the read() call.

The -ud switch is the proper way to start a daemon process because with this
switch the server will not attempt to read from stdin. This switch also
causes the server to close stdin, stdout, stderr as well as 'chdir /'
so that it properly acks as a daemon.

An added advantage to using -ud is that the dbsrv9 command will not complete
(i.e. exit) until the database server is up and running. If for any reason
the database server could not be started, dbsrv9 -ud will return with an
exit code that will indicate an error. You can therefore use the exit code
as a means of ensuring that the process started correctly.

You can also use dbspawn to start a daemon process.

Just a FYI: :-)

- Mark

"Oliver Schulze L." wrote:[color=darkred
]
>
> Hi Greg,
> sorry for the delay. Here is the command:
>
> dbsrv9 -ud -c 16M -x " tcpip(ServerPort=264
0)" -n Example
> /DATABASES/example.db &
>
> This command is executed as rood and after all Sybase
> environment variables has been set.
>
> Thanks
> Oliver
>
> Greg Fenton wrote:

Greg Fenton

2005-05-18, 9:23 am

Mark Culp wrote:
>
> The problem with just using '&' is that it does let the server know that
> it should be a daemon and therefore (without the -ud) it will attempt to read
> from stdin

That should be "... it does _not_ let the server know..."

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Oliver Schulze L.

2005-05-18, 11:23 am

Hi Mark,
will do! Many thanks for the FYI
Oliver

Mark Culp wrote:
> BTW: On a somewhat different topic (from the one in this thread...)
> I noticed that you are adding a '&' to the end of your command line.
> Note that this is not recommended, generally will not work, and is not the
> correct way to put the server into the background.
> BUT you happen to also be adding -ud to your list of switches, which is the
> correct way to start a daemon server process, and therefore you are getting
> away with the '&' at the end.
>
> The problem with just using '&' is that it does let the server know that
> it should be a daemon and therefore (without the -ud) it will attempt to read
> from stdin (i.e. to get the response for "Press Q to quit") and therefore
> will halt the server process as soon as it issues the read() call.
>
> The -ud switch is the proper way to start a daemon process because with this
> switch the server will not attempt to read from stdin. This switch also
> causes the server to close stdin, stdout, stderr as well as 'chdir /'
> so that it properly acks as a daemon.
>
> An added advantage to using -ud is that the dbsrv9 command will not complete
> (i.e. exit) until the database server is up and running. If for any reason
> the database server could not be started, dbsrv9 -ud will return with an
> exit code that will indicate an error. You can therefore use the exit code
> as a means of ensuring that the process started correctly.
>
> You can also use dbspawn to start a daemon process.
>
> Just a FYI: :-)
>
> - Mark
>

Oliver Schulze L.

2005-05-18, 1:23 pm

Hi Mauro,
thanks! The switch -ua solved the problem, now it is working!
The network part of ASA is now running. :)

But I think we need to upgrade to 9.0.1 to be offcially supported
by Sybase.

Cheers
Oliver

Mauro Bertapelle wrote:[color=darkred
]
> Olivier,
>
> this has been discussed some months ago in this newsgroup:
>

Mark Culp

2005-05-18, 1:23 pm

Greg: Thanks for noticing the critical "not" !

Greg Fenton wrote:
>
> Mark Culp wrote:
>
> That should be "... it does _not_ let the server know..."
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Andre Schild

2005-05-18, 8:23 pm

Oliver Schulze L. schrieb:
> Hi Mauro,
> thanks! The switch -ua solved the problem, now it is working!
> The network part of ASA is now running. :)
>
> But I think we need to upgrade to 9.0.1 to be offcially supported
> by Sybase.

I would strongly urge you to do the 9.0.1 upgrade.
We had a lot of troubles with 9.0.0.x under linux, especialy under high
load conditions.
With 9.0.1.x it works very smooth, even under heavy stress.

André
[color=darkred]
>
> Cheers
> Oliver
>
> Mauro Bertapelle wrote:
>

Greg Fenton

2005-05-19, 9:23 am

Andre Schild wrote:
>
> I would strongly urge you to do the 9.0.1 upgrade.

FYI, 9.0.2 is now available for Unix/Linux/MacOSX, as well as an newer EBF.

greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Steve Burbrink

2005-05-27, 8:23 pm

Has the issue been resolved in the latest version (9.0.2.2552) that causes
the recommendation of the "-ua" switch ?

Steve

"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:428ca219$1@foru
ms-1-dub...
> Andre Schild wrote:
>
> FYI, 9.0.2 is now available for Unix/Linux/MacOSX, as well as an newer
> EBF.
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Oliver Schulze L.

2005-06-10, 11:23 am

Steve Burbrink wrote:
> Has the issue been resolved in the latest version (9.0.2.2552) that causes
> the recommendation of the "-ua" switch ?
>
> Steve

I think it is:
http://www.sybase.com/detail? id=10...ibut
ions

Haven't try it yet.
Oliver

Sponsored Links