Sybase Forums,Unix Forums-Sybase Adaptive server|Replication Server|Sun Solaris Unix|Perl|Technical Videos - All Forums

ASE Migration from 12.5 to 15.0.X - SQL Code Changes

niceboykunal123 — Tue, 09 Mar 2010 00:18:46 -0800

While ASE Migration from 12.5 to 15.0.X, Can anyone please help me to identify the blocks of SQL which also need to cosider while migrating. Or which need to change hence the migaration will be successful.

'rlogin' command

srama2 — Mon, 08 Mar 2010 22:39:13 -0800

The rlogin command allows remote login access to another host in the local network. rlogin passes information about the local environment, including the value of the TERM environment variable, to the remote host.

Syntax

rlogin [-468DEKLdx] [-e char] [-i localname] [-k realm] [-l username] host

Options:

-4 Use IPv4 addresses only.

-6 Use IPv6 addresses only.

-8 The -8 option allows an eight-bit input data path at all times;
otherwise parity bits are stripped except when the remote side's
stop and start characters are other than ^S/^Q.

-D The -D option sets the TCP_NODELAY socket option which can improve
interactive response at the expense of increased network load.

-E The -E option stops any character from being recognized as an
escape character. When used with the -8 option, this provides a
completely transparent connection.

-K The -K option turns off all Kerberos authentication.

-L The -L option allows the rlogin session to be run in ``litout''
(see tty(4)) mode.

-d The -d option turns on socket debugging (see setsockopt(2)) on the
TCP sockets used for communication with the remote host.

-e The -e option allows user specification of the escape character,
which is ``~'' by default. This specification may be as a literal
character, or as an octal value in the form \nnn.

-i The -i option allows the caller to specify a different local name
to be used for authentication. This option is restricted to pro-
cesses with uid 0.

-k The -k option requests rlogin to obtain tickets for the remote host
in realm realm instead of the remote host's realm as determined by
krb_realmofhost(3).

-l The -l option specifies a different username for the remote login.
If this option is not specified, your local username will be used.

-x The -x option turns on DES encryption for all data passed via the
rlogin session. This may impact response time and CPU utilization,
but provides increased security.
Ex:

[prodaip@tahiti] /usr/appl/aip $ rlogin -l ftpaip iota
ftpaip's Password:
*******************************************************************************
* *
* Welcome to the **new** iota! *
* *
*******************************************************************************

This system is for authorized users only.
For help getting started, see http://zen.ntrs.com/unix/user/

Last unsuccessful login: Tue Feb 9 13:22:58 CST 2010 on /dev/pts/15 from ilch-m
Last login: Tue Mar 9 00:23:42 CST 2010 on /dev/pts/6 from tahiti.ntrs.com

[ftpaip@iota] /usr/appl/aip/home/aipprod $

'compress' command

srama2 — Sun, 07 Mar 2010 22:16:54 -0800

'compress' command is used to compress a given file. The compress utility will attempt to reduce the size of the named files by using adaptive Lempel-Ziv coding. Except when the output is to the standard output, each file will be replaced by one with the extension .Z, while keeping the same ownership modes, change times and modification times. If appending the .Z to the file pathname would make the pathname exceed 1023 bytes, the command will fail. If no files are specified, the standard input will be compressed to the standard output.

syntax:
compress [ file ]

If no file is specified input is taken from stdin.

Options:

- c Writes to stdout. no files are changed and no .Z files are created. The behavior of zcat is identical to that of `uncompress -c'.

-f When compressing, forces compression of file, even if it does not actually reduce the size of the file, or if the corresponding
file.Z file already exists.

-v Verbose. Writes to standard error messages concerning the percentage reduction or expansion of each
file.

-b bits Sets the upper limit (in bits) for common substring codes. bits must be between 9 and 16 (16 is the default). Lowering
the number of bits will result in larger, less compressed files.

uncompress
The uncompress utility will restore files to their original
state after they have been compressed using the compress
utility. If no files are specified, the standard input will
be uncompressed to the standard output.

This utility supports the uncompressing of any files pro-
duced by compress. For files produced by compress on other
systems, uncompress supports 9- to 16-bit compression (see
-b).

zcat
The zcat utility will write to standard output the
uncompressed form of files that have been compressed using
compress. It is the equivalent of uncompress -c. Input files
are not affected.

[prodaip@tahiti] /usr/appl/aip/saritha_test$ ls -l ex.sh
-rwxr----- 1 prodaip aip 75 Mar 4 05:39 ex.sh

[prodaip@tahiti] /usr/appl/aip/saritha_test$ compress ex.sh

[prodaip@tahiti] /usr/appl/aip/saritha_test $ ls -l ex.sh.Z
-rwxr----- 1 prodaip aip 73 Mar 4 05:39 ex.sh.Z
[prodaip@tahiti] /usr/appl/aip/saritha_test

[prodaip@tahiti] /usr/appl/aip/saritha_test $ zcat ex.sh.Z
#!/usr/bin/ksh

column=$1

echo $column

nawk '{print $'$column'}'

exit 0
[prodaip@tahiti] /usr/appl/aip/saritha_test $ uncompress ex.sh
[prodaip@tahiti] /usr/appl/aip/saritha_test $ ls -l ex.sh
-rwxr----- 1 prodaip aip 75 Mar 4 05:39 ex.sh
[prodaip@tahiti] /usr/appl/aip/saritha_test $

Shell Programming Control Structures - SH,BASH,KSH,CSH,TCSH quick reference

Joshi — Fri, 05 Mar 2010 06:01:50 -0800

Please download the card (image) below containing Shell Programming Control Structures - SH,BASH,KSH,CSH,TCSH quick reference

Sybase DBA Interview Question - How do you determine the current ASE edition running

Joshi — Fri, 05 Mar 2010 05:45:58 -0800

Determining the Current Sybase ASE Edition using isql
Learn how to find out which edition you are currently running.

Enter:

sp_lmconfig 'edition'

Adaptive Server returns a value of EE, SE, or DE based on the edition that is currently running.

$ isql -Uxxxx -Pxxxx -c
Password:
1> sp_lmconfig 'edition'
2>

Parameter Name Config Value
----------------- ------------
edition EE

(return status = 0)
1> exit

Determining the Current Sybase ASE Edition from errorlog file

00:00000:00000:2010/02/28 09:29:50.08 kernel Checked out license ASE_CORE
00:00000:00000:2010/02/28 09:29:50.08 kernel Adaptive Server Enterprise (Enterprise Edition)

'ln' command

srama2 — Thu, 04 Mar 2010 23:18:34 -0800

'ln' command is used to link files and directories. It is used to create new files with the names speciifed and links them to existing files or directories.

syntax:
ln source_file target_file
options:

-s to create soft links.

There are two types of links. Hard links and soft links. 'ln' without any options creates a hard link to the file. Hard link is a pointer to physical data. Effectively, all standard files are hard links, because they ultimately create an association between a file name and a physical data which corresponds to each file.

Ex:
[prodaip@tahiti] /usr/appl/aip/saritha_test $ cat file1
echo "Hello !! Welcome to the world of unix !!!!"
[prodaip@tahiti] /usr/appl/aip/saritha_test $
creating a hard link to file1

[prodaip@tahiti] /usr/appl/aip/saritha_test $ ln file1 file2

file2 is a hard link to file1 which contains same data as file. Both file1 & file2 share same inode.

[prodaip@tahiti] /usr/appl/aip/saritha_test $ ls -l file2
-rw-r----- 2 prodaip aip 50 Mar 5 00:51 file2
[prodaip@tahiti] /usr/appl/aip/saritha_test $ cat file2
echo "Hello !! Welcome to the world of unix !!!!"
[prodaip@tahiti] /usr/appl/aip/saritha_test $ ls -i file1 file2
1783 file1 1783 file2
[prodaip@tahiti] /usr/appl/aip/saritha_test $

Soft link (also referred to as symlink - short for symbolic link) is a special type of file in Unix, which references another file or directory. Symlink contains the name for another file and contains no actual data. To most commands, symlinks look like a regular file, but all the operations (like reading from a file) are referred to the file the symlink points to.

When you remove a soft link, you simply remove one of the pointers to the real file. When you remove the original file a soft link points to, your data is lost. Even though your soft link will still exist, it will be pointing to the non-existent file and will therefore be useless (it will probably have to be removed as well).

Ex:

[prodaip@tahiti] /usr/appl/aip/saritha_test $ ln -s file1 file3
[prodaip@tahiti] /usr/appl/aip/saritha_test $ ls -l file3
lrwxrwxrwx 1 prodaip aip 5 Mar 5 01:10 file3 -> file1
[prodaip@tahiti] /usr/appl/aip/saritha_test $ cat file3
echo "Hello !! Welcome to the world of unix !!!!"
[prodaip@tahiti] /usr/appl/aip/saritha_test $

BENEFITS OF SYBASE DEVELOPERS NETWORK

crazYoga — Thu, 04 Mar 2010 09:06:07 -0800

* Access a large online library of technical documents
* Download software and code samples for developers
* Research options and solutions
* Learn about events and announcements for developers
* Pursue educational and training opportunities

Tuning SYBASE Transact-SQL Queries

crazYoga — Thu, 04 Mar 2010 08:05:03 -0800

* Learn the Strengths and Weaknesses of the Optimizer

* One of the largest factors determining performance is TSQL! Test not only for efficient plans but also semantic correctness.

* Optimizer will cost every permutation of accesses for queries involving 4 tables or less. Joins of more than 4 tables are "planned" 4-tables at a time (as listed in the FROM clause) so not all permutations are evaluated. You can influence the plans for these large joins by the order of tables in the FROM clause.

* Avoid the following, if possible:
o What are SARGS?

This is short for search arguments. A search argument is essentially a constant value such as:
+ "My company name"
+ 3448

but not:
+ 344 + 88
+ like "%what you want%"
o Mathematical Manipulation of SARGs

SELECT name FROM employee WHERE salary * 12 > 100000

o Use of Incompatible Datatypes Between Column and its SARG

Float & Int, Char & Varchar, Binary & Varbinary are Incompatible;

Int & Intn (allow nulls) OK

o Use of multiple "OR" Statements - especially on different columns in same table. If any portion of the OR clause requires a table scan, it will! OR Strategy requires additional cost of creating and sorting a work table.
o Not using the leading portion of the index (unless the query is completely covered)
o Substituting "OR" with "IN (value1, value2, ... valueN) Optimizer automatically converts this to an "OR"
o Use of Non-Equal Expressions (!=) in WHERE Clause.

* Use Tools to Evaluate and Tune Important/Problem Queries
o Use the "set showplan on" command to see the plan chosen as "most efficient" by optimizer. Run all queries through during development and testing to ensure accurate access model and known performance. Information comes through the Error Handler of a DB-Library application.
o Use the "dbcc traceon(3604, 302, 310)" command to see each alternative plan evaluated by the optimizer. Generally, this is only necessary to understand why the optimizer won't give you the plan you want or need (or think you need)!
o Use the "set statistics io on" command to see the number of logical and physical i/o's for a query. Scrutinize those queries with high logical i/o's.
o Use the "set statistics time on" command to see the amount of time (elapsed, execution, parse and compile) a query takes to run.
o If the optimizer turns out to be a "pessimizer", use the "set forceplan on" command to change join order to be the order of the tables in the FROM clause.
o If the optimizer refuses to select the proper index for a table, you can force it by adding the index id in parentheses after the table name in the FROM clause.

SELECT * FROM orders(2), order_detail(1) WHERE ...

This may cause portability issues should index id's vary/change by site !

Why should I use stored procedures in Sybase ASE

crazYoga — Thu, 04 Mar 2010 08:03:43 -0800

There are many advantages to using stored procedures (unfortunately they do not handle the text/image types):

* Security - you can revoke access to the base tables and only allow users to access and manipulate the data via the stored procedures.
* Performance - stored procedures are parsed and a query plan is compiled. This information is stored in the system tables and it only has to be done once.
* Network - if you have users who are on a WAN (slow connection) having stored procedures will improve throughput because less bytes need to flow down the wire from the client to ASE.
* Tuning - if you have all your SQL code housed in the database, then it's easy to tune the stored procedure without affecting the clients (unless of course the parameter change).
* Modularity - during application development, the application designer can concentrate on the front-end and the DB designer can concentrate on the ASE.
* Network latency - a client on a LAN may seem slower if it is sending large numbers of separate requests to a database server, bundling them into one procedure call may improve responsiveness. Also, servers handling large numbers of small requests can spend a surprising amount of CPU time performing network IO.
* Minimise blocks and deadlocks - it is a lot easier to handle a deadlock if the entire transaction is performed in one database request, also locks will be held for a shorter time, improving concurrency and potentially reducing the number of deadlocks. Further, it is easier to ensure that all tables are accessed in a consistent order if code is stored centrally rather than dispersed among a number of apps.

How to View MRU-LRU procedure cache chain in Sybase ASE

crazYoga — Thu, 04 Mar 2010 07:58:44 -0800

dbcc procbuf gives a listing of the current contents of the procedure cache. By repeating the process at intervals it is possible to watch procedures moving down the MRU-LRU chain, and so to see how long procedures remain in cache. The neat thing about this approach is that you can size your cache according to what is actually happening, rather than relying on estimates based on assumptions that may not hold on your site.

To run it:

dbcc traceon(3604)
go
dbcc procbuf
go

Improving Text/Image Type Performance in Sybase ASE

crazYoga — Thu, 04 Mar 2010 07:57:07 -0800

If you know that you are going to be using a text/insert column immediately, insert the row setting the column to a non-null value.

There's a noticeable performance gain.

Unfortunately, text and image datatypes cannot be passed as parameters to stored procedures. The address of the text or image location must be created and returned where it is then manipulated by the calling code. This means that transactions involving both text and image fields and stored procedures are not atomic. However, the datatypes can still be declared as not null in the table definition.

Given this example -

Code:

create table key_n_text

    (

        key     int    not null,

        notes    text    not null

    )

This stored procedure can be used -

Code:

create procedure sp_insert_key_n_text

        @key    int,

        @textptr    varbinary(16)    output

    as

    /*

    ** Generate a valid text pointer for WRITETEXT by inserting an

    ** empty string in the text field.

    */

    insert key_n_text

    (

        key,

        notes

    )

    values

    (

        @key,

        ""

    )

    select  @textptr = textptr(notes)

    from    key_n_text

    where   key     = @key

    return 0

    go

The return parameter is then used by the calling code to update the text field, via the dbwritetext() function if using DB-Library for example.

Essential and Optional DBA Tasks

crazYoga — Thu, 04 Mar 2010 07:48:35 -0800

Essential DBA Tasks (courtesy of the Complete Sybase ASE Quick Reference Guide)

* Perform database and transaction log dumps (daily/hourly)
* Run dbcc checkstorage for all database and follow up on any problems found (weekly)
* Run update index statistics on user tables (weekly/as needed)
* Regular preventative stop and restart of ASE server
(they suggest monthly but in my experience, other than applying EBFs you don’t ever need to take down the server)
* Monitor server errorlog for anomalies (daily)
* Troubleshoot unforeseen emergences (ad-hoc read daily )
* Attend to (end) user / developer needs (whenever)

Additional/Optional DBA Tasks (also courtesy of the Complete Sybase ASE Quick Reference Guide)

Monitor growth of data volume and log space usage (daily/weekly)
Defragment tables (reorg or (re)build clustered index) (monthly/quarterly)
Monitor/tune server resource usage with sp_sysmon (when possible)
Report problems to Sybase Technical Support(when necessary)
Install EBFs or upgrades for ASE (when necessary)
Set up the dbccdb database for dbcc checkstorage (once)
Set up the sybsyntax database (once)

Sybase triggers protects our data - Very useful

crazYoga — Thu, 04 Mar 2010 07:34:21 -0800

Takeaway: Triggers are used to preserve data integrity by checking on or changing data in a consistent manner. Sybase provides various mechanisms for utilizing the power of triggers.

Automating routine tasks is the hallmark of a great application. This automation allows the developer to tackle more important issues. Triggers provide automation to database developers. This article introduces the concepts associated with using triggers in Sybase.

Sybase triggers are your data enforcers
A database trigger is a set of SQL statements that automatically "fires off" an action simultaneously with a specific operation, such as changing data in a table. A trigger consists of an event (an INSERT, DELETE, or UPDATE statement issued against an associated table) and an action (the related procedure). Triggers are used to preserve data integrity by checking on or changing data in a consistent manner.

Triggers are most often used to implement referential integrity or complex rules, or for keeping duplicate, summarized, or aggregated values in sync with detail records. While defaults bound to a column may contain only one value, a trigger can enforce a multitude of default values conditionally based on other data in the same or another table.

Triggers can enforce complex referential integrity (RI) where a lookup is required in another table, or even another column in the same table. They can prevent the modification of primary/foreign keys or even cascade the modifications to other tables. Many also consider storing summary values (or most other derivative values) in another table in real-time a justifiable use of triggers. Triggers can enforce complex business rules or quality assurance where you want to ensure that an updated value doesn’t deviate too far from the original value. Triggers are preferred over integrity constraints for another important reason: integrity constraints don’t facilitate conditional transaction management.

One trigger can have many uses
A trigger may be fired for any given data modification language (DML) SQL statement. These statements include INSERT, UPDATE, and DELETE, and each event may have its own trigger. It’s also possible to use the same trigger for more than one DML event by specifying what actions you wish the trigger to fire on in the CREATE statement.

Many developers believe the statement fires once for every affected row. Actually, a trigger fires only once for the DML statement that fired it. It’s a common misconception that a trigger is not fired if no rows are affected. Actually, the trigger fires even if no rows are affected. This can occur if the “where” clause is unsatisfied. The only situation in which a trigger will not fire is when a table constraint (defined as part of the CREATE statement which created the table) disallows the modification. Also, Delete triggers will not fire on a truncate table statement, and Insert triggers will not fire as a result of the Writetext command.

Trigger creation is simple and flexible
The syntax for creating a Sybase trigger is as follows:
create trigger [owner.]trigger_name
on [owner.]table_name
{for {insert , update , delete}
as SQL_statements

Or, using the if update clause:
create trigger [owner.]trigger_name
on [owner.]table_name
for {insert , update}
as
[if update (column_name )
[{and | or} update (column_name )]...]
SQL_statements
[if update (column_name )
[{and | or} update (column_name )]...
SQL_statements ]...

To drop a trigger, the syntax is as follows:
drop trigger

You can temporarily disable a trigger if you are loading a table from a previous dump and need to speed up the process. This capability was introduced in Sybase Adaptive Server 12.0. To disable or re-enable a trigger, the syntax is as follows:
alter table [database_name.[owner_name].]table_name
{enable | disable} trigger [trigger_name]

To keep things simple, we’ll create a trigger whose only purpose is to prevent deletions and insertions in a table. The syntax is as follows:
create trigger publishers_IDtg
on publishers
for insert, delete
as
begin
print "You cannot insert or delete any records!"
rollback transaction
return
end

This trigger will fire whenever a DELETE or INSERT statement executes on the publishers table. This also includes situations where another trigger may have inserted or deleted records into this table. Rollback Transaction reverts any modifications made to the database from either the explicit or implied transaction that contained the SQL DELETE statement that caused the trigger to fire.

Now, let’s create a trigger that uses if update and whose job it is simply to disallow modifications to a primary key.
create trigger publishers_Utg
on publishers
for update
as
if update( pub_id )
begin
print "You cannot Update the primary key!"
rollback transaction
return
end

Triggers access the inserted and deleted tables
During its execution, a trigger has access to two special tables. These tables are exactly the same in structure as the trigger table. They are always referred to as “inserted” and “deleted.” A trigger can access these tables to determine what modifications have occurred, but the trigger can’t modify these tables. Note that updates to table rows result in deletions followed by insertions. So, if records appear in both the deleted and inserted tables, the trigger knows an update was performed.

Rollback Transaction and Rollback Trigger prevent unwanted modifications
There are two commands that will explicitly roll back all modifications made by the SQL statement that fired a trigger: Rollback Transaction and Rollback Trigger.

Rollback Transaction
Use Rollback Transaction to prevent the modifications that fired the trigger, to roll back all changes back to the outermost begin transaction and to abort the rest. This is the method used most often; it ensures that all modifications associated with the outermost transaction, or batch are rolled back.

Rollback Trigger [with raiserror]
Rollback Trigger is used to prevent the modifications that fired the trigger. It does allow any other transaction modifications or batch to be committed at the end. This method of rolling back is trickier to use and should be debugged thoroughly, as it may allow partial modifications and result in a loss of data integrity.

Let’s consider an example of this approach:
begin tran
insert into table_a (column_a) values (“11111”)
insert into table_a (column_a) values (“22222”)
insert into table_a (column_a) values (“33333”)
commit trans
end trans

If the Insert trigger on table_a issued a Rollback trigger on any firing of the Insert triggers in the above example, the other Inserts would not be affected and would subsequently be committed.

If the Insert trigger on table_a issued a rollback transaction on any firing of the Insert triggers in the above example, the already executed Inserts would be rolled back, and any remaining Inserts would never execute at all.

Generate lists to identify and view trigger source text
You can generate a list of triggers currently defined in the database using the following SELECT statement:
select *
from sysobjects
where type = "TR"

You can view the source code of the trigger as follows:
sp_helptext

As long as sp_hidetext hasn’t been used to encrypt the trigger text and the DBA has not disabled the ability to view the syscomments.text column, you should see the text used to create the specified trigger.

If you wish to know what tables and views a trigger references, there is always the sp_depends stored procedure.
sp_depends

Trigger rules and limitations prevent unauthorized changes
Here is a list of trigger rules and limitations.

Only the owner of a table can create or drop a trigger on that table.
Unlike views and stored procedures, permissions apply the same way inside a trigger as they do in a normal SELECT statement. Thus, if a user doesn’t have permission to update table_b and he updates table_a and fires trigger_a, which tries to update table_b, the trigger will fail and the modifications will fail.
In a trigger you may reference up to 192 other database objects like tables, views, etc.

What isn't allowed in a trigger?
Here is a list of rules for what is not allowed in a trigger:

Create and Drop commands are not allowed in any form. However, temp tables may be called in a stored procedure that is called by the trigger.
Alter table/database is not allowed.
Grant and Revoke are both disallowed.
Select Into isn’t allowed.
Truncate Table is prohibited.
Update Statistics isn’t allowed.
Reconfigure is not allowed.
Load Database/Transaction isn't allowed.
Disk Init/Mirror/Reinit/Refit/Remirror/Unmirror are all disallowed.

Trigger naming conventions are important
Any good programmer knows the importance of naming conventions. Triggers are no exception. Trigger names are limited to 30 characters. My personal preference is to use the full table name with the suffixes in Table A.
Table A

Trigger Type	Table Name & Suffix
Insert	employee_Itg
Update	employee_Utg
Delete	employee_Dtg
Update & Delete	employee_UDtg
Update & Delete & Insert	employee_UDItg
* Assuming the table name is employee

Trigger naming

Using triggers is easier than you think
This is by no means a definitive “end-all” to triggers. You’d need further discussion of these topics and others not mentioned here to even begin to master the art of trigger design and implementation. The Sybase documentation and a plethora of third-party manuals available at your local bookstore are valuable resources for understanding the power of triggers as part of your database design, and the finesse you need to use them. This overview should help you to begin to utilize them and understand what they can to do.

Microsoft Excel 2007 with Sybase IQ 15.0 and SQL Anywhere 11.0, Report 318

crazYoga — Thu, 04 Mar 2010 07:23:31 -0800

Microsoft Excel 2007 with Sybase IQ 15.0 and SQL Anywhere 11.0, Report 318

This section describes each of the products tested and how they were used during testing. For more information about any of the products, please refer to the product literature. This report documents only the platforms and products tested for certification. Other possible combinations of these products and platforms are not certified by Sybase. For more information about Sybase IQ or SQL Anywhere, including known issues not encountered during this certification or those occurring on other platforms, see the Sybase Release Bulletin for the relevant product and platform.

* Microsoft Office Excel 2007 (hereafter called "Excel"), which is part of Microsoft Office Enterprise 2007 suite of products, served as the reporting tool, querying the Sybase IQ and SQL Anywhere databases. Excel includes a feature called MS Query. MS Query and its wizard were used to select tables in Sybase IQ and SQL Anywhere and build queries. The Excel version tested was a 32-bit application installed and run on a 64-bit Windows XP Professional machine.
* Sybase® IQ version 15.0 (hereafter called "IQ") served as a data source. Two 64-bit IQ server instances running on the same Sun SPARC Solaris 10 workstation were tested.
* 32-bit Sybase IQ 15.0 ODBC Driver for Windows version 11 (hereafter called the "IQ ODBC driver") enabled ODBC connectivity between Excel and the IQ servers. The driver was installed with the Sybase IQ 15.0 Network Database Client for Windows, which includes the driver in both 32-bit and 64-bit word sizes. Note that version 11 of the driver is the appropriate version to work with the 15.0 version of IQ. The 32-bit version of the driver was used because the version of Excel tested was a 32-bit application and the word-size of the driver must match that of the client application, not the target server.
* Sybase SQL Anywhere Network Server version 11.0 (hereafter called "SA") served as a data source. Two 64-bit SA instances run on the same Windows XP machine were tested.
* 32-bit Sybase SQL Anywhere 11 ODBC Driver (hereafter called the "SA ODBC driver") enabled connectivity between Excel and the SA servers. The SA ODBC driver was also installed with the Sybase IQ 15.0 Network Database Client for Windows, which includes both the SA and IQ drivers in both 32-bit and 64-bit word sizes.

for more: http://www.sybase.in/detail?id=1064156

Sybase partners with Wipro, SAPAG to offer integrated SAP business solutions

crazYoga — Thu, 04 Mar 2010 07:03:57 -0800

Sybase partners with Wipro, SAPAG to offer integrated SAP business solutions
With organizations increasingly switching over to MEAP, latest SAP offerings on Sybase Unwired Platform(SUP) come as a welcome move

In yet another move aiding organizations towards MEAP platforms, Sybase Software, India and Wipro Infotech have partnered to extend SAP applications to a variety of mobile devices, allowing SAP customers to access their enterprise applications in a secured way while on the move.

Accordingly, Sybase and SAP will deliver co-developed solutions for extending SAP CRM and SAP Business Suite to mobile devices. Using these solutions, SAP customers will be able to leverage Wipro's SAP offerings to customize these Sybase mobile solutions for SAP, in addition to developing custom mobile applications for other SAP modules such as SRM SCM, and PLM, directed towards areas like mobile services, mobile sales, time and travel approvals, workflows, warehouse management, asset management, and more.

Commenting on the tie-up, Sairaman Jagannathan, VP, business solutions division, Wipro remarked, "Building on our SAP partnership, this partnership with Sybase demonstrates a strong synergy between our companies, as we share a common goal of providing businesses easy access to valuable information contained within enterprise applications. As Sybase's implementation partner, we will bring in tight integration with a wide range of mobile environments to ensure secure and real-time access to information."

Wipro's solutions will be based on Sybase Unwired Platform (SUP), enabling enterprises to implement, manage and expand their mobile computing initiatives in a coherent, streamlined and cost-effective manner. As part of this joint initiative, Wipro will set-up a Center of Excellence at its research center in Sangam, Bengaluru, where customers will be able to view various mobile applications developed by Wipro to mobilize SAP. The Center of Excellence will also be used to develop new industry frameworks that can be used across different customer verticals.

Elaborating on the workability of these new solutions, Sunil Jose, MD, India & subcontinent, Sybase Software said, "SUP supports a wide variety of popular mobile platforms. This enables true mobility for a large section of employees and not just top or middle management. Through this, SAP's customers will be able to create an information edge by optimizing and enhancing the infrastructure they already own, linking valuable data resources in place, and securely delivering information anytime, anywhere."

According to a recent Gartner report on Mobile Enterprise Application Platforms (MEAP), over 95% of the organizations will be choosing MEAP or packaged mobile application vendors as their primary mobile development platforms till 2012, and from 2010 to 2013, the number of enterprises choosing multichannel MEAP vendors is estimated to rise by 10% annually.

In this light, Sybase has also tied up with SAPAG to offer two new solutions for mobile users to carry out key business and CRM processes via iPhone and Windows Mobile. Built on SUP, the mobile solution extends the capabilities of SAP Business Suite applications, including SAP CRM, and also can be customized to tap into a variety of back-end data sources, including databases, web services, files and any enterprise application that leverages SOA.

ref: http://voicendata.ciol.com

'ps' command

srama2 — Thu, 04 Mar 2010 01:23:05 -0800

'ps' command is used to display information about the processes running on the system.

Syntax: ps [ options ]

The output of the command will contain the following

PID - process id
TTY - Terminal
TIME - CPU time the process used
CMD - command

Options:
-a Displays all processes on a terminal, with the exception of group leaders.
-c Displays scheduler data.
-d Displays all processes with the exception of session leaders.
-e Displays all processes.
-f Displays a full listing.
-glist Displays data for the list of group leader IDs.
-j Displays the process group ID and session ID.
-l Displays a long listing
-plist Displays data for the list of process IDs.
-slist Displays data for the list of session leader IDs.
-tlist Displays data for the list of terminals.
-ulist Displays data for the list of usernames.

Examples:

To see every process on the system using standard syntax:
ps -e
ps -ef

UID PID PPID C STIME TTY TIME CMD
root 0 0 0 Mar 25 ? 4:29 sched
root 1 0 0 Mar 25 ? 724:48 /etc/init -s
root 2 0 0 Mar 25 ? 2:34 pageout
root 3 0 1 Mar 25 ? 41038:16 fsflush
root 5464 1 0 Mar 25 ? 0:00 /usr/lib/saf/sac -t 300
root 65 1 0 Mar 25 ? 1:55 /sbin/in.mpathd

Difference between normal Shutdown and Shutdown with nowait in Sybase ASE

Joshi — Wed, 03 Mar 2010 06:46:50 -0800

The default for the shutdown command is with wait. The with wait option allows Adaptive Server to finish executing SQL statements or procedures, perform a checkpoint in each database, disable new logins, and perform other shutdown tasks.

Issuing the shutdown command prints a message like this to the sterr file:

Server SHUTDOWN by request.The SQL Server is terminating this process.
CT-LIBRARY error:

This is normal behavior.

If the message indicates that Adaptive Server is waiting for processes to complete, and you need to stop Adaptive Server immediately, you can use the shutdown with nowait command. shutdown with nowait does not wait for currently executing statements to finish, nor does it perform checkpoints in every database. Use the shutdown with nowait command only when necessary.

Sybase ASE Shutdown and Shared memory files

Joshi — Wed, 03 Mar 2010 06:45:09 -0800

Sybase ASE Shutdown and Shared memory files

When Adaptive Server starts, it creates SERVER_NAME.krg file in $SYBASE/$SYBASE_ASE directory to store information about shared memory segments that it uses.

If Adaptive Server is configured with a memory size that is greater than the MAXSHMSEGSIZE parameter in the operating system then Adaptive Server may create additional shared memory segments and for every additional shared memory segment that it creates, an additional file with SERVER_NAME.srg[N] (where N ranges from 0 – N), is created under $SYBASE/$SYBASE_ASE.

When Adaptive Server is shut down in a normal manner, the shared memory files are automatically removed. If Adaptive Server crashes or is stopped with the kill -9 command, these files are not deleted. You need read and write permissions on these files to restart Adaptive Server after a crash or a kill -9 command, because Adaptive Server must be able to overwrite the previously created shared memory files.

If Adaptive Server or Backup Server is killed abnormally it also leaves shared memory segments.Sometimes the server may not come up until these shared memory segments are removed. Use the ipcs and ipcrm commands to identify and remove these shared memory segments that have “NATTACH” count as “0”.

ASE 15.5 product manuals

shashikandi — Wed, 03 Mar 2010 03:05:59 -0800

Here is the link to ASE 15.5 manuals.

http://infocenter.sybase.com/help/index..../title.htm

Thanks,
Shashirekha

'nohup' command

srama2 — Tue, 02 Mar 2010 23:34:39 -0800

'nohup' command is used to run commands immune to hangups.

syntax:
nohup command [ argument... ]

'nohup' utility runs the command with the given arguments.

'nohup' causes the command to ignore the SIGHUP signals which will cause them to be killed.

'nohup' utility can be used when it is known that the command will take a long time to run and the user wants to logout of the terminal. When the shell exits the system sends its children SIGHUP signals, which by default cause them to be killed. All stopped, running and background jobs will ignore SIGHUP and continue to run if their invocation is preceeded by 'nohup'.

A nohup.out output file is created when the 'nohup' command runs.

Ex: nohup ./XYZ.sh &

The '&' will cause XYZ.sh to run in background.

If an error occus in 'nohup' execution a value of 127 is returned.