ASA Unix版本常见问题解答

Q8. Where is the on-line help?
A8. An html version of the on-line help files can be found on the CD. The install program gives you the option of installing a copy to your hard disk. The help files on the CD are located in the directory 'help'. If, for example, your CD is mounted at /mnt/cdrom, then point your browser to: file:/mnt/cdrom/help/contents.htm. The gui-based tools dbconsole and dbisqlc do not have context-sensitive help. If you press F1, you will see the message "Warning at line 1, Help file not found". Use the html-based help instead.

Using the Database Engine

Q9. What are the system resources needed by ASA?
A9. ASA uses the following resources:

• Semaphores: the Solaris version uses native semaphores, but the Linux, HP-UX and AIX versions use System V semaphores, so it is possible to run out on these platforms. The server uses 1, each non-threaded client uses 1, and each threaded client uses 1 plus 1 per connection. If you do run out, then either the server will not be able to start, or clients will not be able to connect to a running server. If this happens, see your system documentation for how to increase your number of semaphores.
• Memory: the server manages its own cache. The size of the cache can be set by the -c option. ASA 7.0.0 and up also features dynamic cache sizing and allow you to specify the minimum and maximum sizes of the cache. The dynamic cache will grow or shrink depending on need.
• Temporary file space: the server creates a number of temporary files in the directory specified by SATMP or ASTMP (default: /tmp/.SQLAnywhere). These files must not be changed or deleted while the server is running. To prevent the temp files of a long-running server from becoming stale enough to be deleted by an automatic temp file cleaner, use the -ut option. It is possible to run out of file descriptors if your O/S limits their number. Use the 'ulimit' command to examine and increase the maximum allowed number of open files. If this number is too low, then the server may hang or crash.
• Threads: all platforms use posix threads.
• Signals: ASA uses a SIGALRM and a SIGIO handler in non-threaded clients, and a SIGIO handler in threaded clients. If you also wish to handle these signals, please read the file 'readme.txt' in your ASA install.

Q10. Which engine switches are supported only on Unix?
A10. The following engine command-line switches are supported only on Unix:

• -ud - run the server in the background as a daemon. This allows the server to keep running after the current user logs out.
• -s id - sets the ID that is used in messages to the syslog facility. The default is: user. Other values are: none, daemon, and local0, local1 ? local7.
• -ut min - causes the server to touch temporary files every min minutes (default: 30). This keeps them from being deleted by automatic temp file cleaner programs.

Q11. Which engine switches are not supported on Unix?
A11. The following engine command-line switches are not supported on Unix:

• -d - disable asynchronous I/O
• -df - use direct, asynchronous I/O
• -di - use direct I/O if possible
• -gb - set database priority class
• -gx - set number of execution threads (use 杇n instead)
• -sc - use C2 communication links
• -tmt - set reenlistment timeout for distributed transactions
• -tmf - for recovery from distributed transactions
• -y - run as a Windows 95/98 service

Q12. Which ASA features are not supported on Unix?
A12. The following ASA features are not supported on Unix:

• any communication protocol other than TCP/IP and local shared memory, including named pipes, NETBIOS, IPX and SPX.
• OLE DB
• the FileDSN connection parameter is not currently available, but will be in a version ASA after, but not including, 7.0.2.
• integrated logins

Q13. Which ASA features are only supported on some Unix versions?
A13a. The following ASA features are only supported on some Unix versions:

• dynamic cache sizing is not available on Linux kernels earlier than 2.4 and also not on Linux for ASA versions 7.0.2 or earlier
• remote data access (proxy tables) are only available on Solaris and Linux, and only for ASA 7.0.2 and later
• SMP support is only available in ASA 6.0.0 and later; earlier versions will run on SMP machines, but will only use one processor
• the new external stored procedure APIs are only available in ASA 7.0.0 and later

A13b. The following SQL Anywhere Studio features are only supported on some Unix versions:

• MobiLink for ASA is available for Solaris and Linux in ASA 7.0.0 and later
• MobiLink transport-layer security (TLS) for the MobiLink server/client connection is available for Solaris and Linux in ASA 7.0.0 and later
• the Java versions of Sybase Central and Interactive SQL are available in ASA 7.0.0 and later
• the stored procedure and Java debugger is available in ASA 6.0.3 and later

Q14. How should I shut down the server?
A14. There are several ways to shut down the server cleanly:

• From a shell prompt, use the command 'dbstop'. Note: stopping the network server requires adding a connection string with a user ID that has permission to stop the server (by default: DBA authority). For example: dbstop -c"uid=DBA;pwd=SQL".
• While connected to the server (for example, from within dbisql), issue the STOP ENGINE statement.
• (SA network server) in the server console, select the menu item File (or use ALT-F), and choose Quit.
• (SA personal server, ASA server) hit 'q' on the server console.
• From a shell prompt, use the kill -1 command to stop the server's process. Do not to use kill -s KILL, kill -9, or kill -s STOP as the server cannot catch these signals and is forced to exit without cleaning up its resources. If it is absolutely necessary to use kill -9, then you must clean up any un-freed semaphores and undeleted server temporary files, and kill any zombie processes before restarting the server. Using kill -9 may cause data to be lost from the database.

Q15. How do I port my database from Windows to Unix?
A15. The database files are binary compatible between Windows and Unix. You can copy the files between platforms. Ensure that you use a binary copy when moving files between machines. Be aware of case-sensitivity on Unix. You may need to run dblog if you have absolute file names in the database.

Q16. How do I connect to my server through the firewall?
A16. If your firewall blocks UDP packets, then you will need to specify UDP=NO in your connection string. Also, you may need to specify DoBroadcast=NO and Host=x.x.x.x. Here is an example of how to set up a dsn:

dbdsn -w mydsn -c "eng=myengine;links=tcpip{udp=no;dobroadcast=no;host=1.2.3.4}"

Here is an example of a connection string:
dbisqlc -c "uid=dba;pwd=sql;links=tcpip{udp=no;dobroadcast=no;host=1.2.3.4};eng=asademo"

Q17. Which ODBC driver manager should I use on Unix?
A17. ASA can be accessed through ODBC either with or without a driver manager. If you use a driver manager, then you must set up a section for the ASA ODBC driver inside of the file .odbcinst.ini. Two versions of the ASA driver are available: the non-threaded dbodbc7.so, and the threaded dbodbc7_r.so. See the documentation for your driver manager for details on how to set up .odbcinst.ini. Also, make sure that the ASA driver is inside a directory in your library path. If you use asa_config.sh (see above), this will be set automatically. On the other hand, if you wish to run ASA without a driver manager, .odbcinst.ini is not required. In both cases, you must place your DSN definitions in .odbc.ini, which is located by default in your home directory, or in the locations specified by ODBCINI and ODBCHOME (see above). The dbdsn utility can help you create a dsn. Please refer to the html help for dbdsn for more information about this.

Q18. How do I use ASA with one or more of: Apache, PHP, perl, DBD and UnixODBC?
A18. We are currently preparing a white paper outlining the steps needed to set up an ASA-based web site. It will appear soon on my.sybase.com.

Common Problems and Error Messages

Q19. When trying to install ASA on Linux, I get "dbinstall: error in loading shared libraries: libstdc++.so: cannot open shared object file: No such file or directory.
A19. You must first install libstdc++ from your Linux distribution in order to install and run ASA.

Q20. When trying to start a server, I get: Error in command near "x" followed by the usage screen.
A20. Braces ( '{' and '}') must be escaped or quoted if used in the csh or tcsh shells. Braces are special characters which need to be proceeded by a \ (backslash) in order to be taken literally. For example:
dbsrv7 -x tcpip\{host=portal\} asademo.db

Q21

上一页  [1] [2] [3] [4]  下一页

Copyright ＠ 2007-2012 敏韬网(敏而好学，文韬武略--MinTao.Net)（学习笔记） Inc All Rights Reserved.
闵涛 E_mail:admin@mintao.net(欢迎提供学习资源)

鄂公网安备 42011102001154号

站长：MinTao ICP备案号：鄂ICP备11006601号-18