After the ASE 15.5 release and Sybase Q4 result, one more good news for all Sybase Guys...
4th Feb 2010, Sybase, Inc. (NYSE: SY), an industry leader in enterprise and mobile software, today announced that it has finalized an Asset Purchase Agreement with Aleri Inc. Aleri is a leading provider of enterprise-class complex event processing (CEP) technology and CEP-based solutions.
"With this transaction Sybase positions itself as a clear market leader in CEP. We have strengthened our real-time analytics platform, by adding Liquidity Risk Management and the industry leading Liquidity Management Suite," said Dr. Raj Nathan, Senior Vice President and CMO of Sybase. "Our customers increasingly expect Sybase to provide a broad analytics portfolio to meet their growing needs and we are committed to continue to deliver on this vision."
Keep Rocking sybase!!!
Source : http://www.sybase.com/detail?id=1067153 & http://www.aleri.com/developers/blogs/sy...leri-staff
About Aleri
According to Forrester Research, "The Aleri platform is a strong product backed by a strong strategy." Aleri is recognized as a standout leader in CEP in the Forrester Research, Inc., independent report published August 4, 2009 --"The Forrester Wave™: Complex Event Processing (CEP) Platforms," Q3 2009. The full report can be found at http://www.forrester.com.
Aleri is focused on providing tools and solutions that deliver Continuous Intelligence ™ - allowing businesses to make better decisions through more timely insight and respond quickly to changing conditions. The centerpiece of this effort is Aleri's Complex Event Processing (CEP) technologies, designed for high speed real-time analysis of data streams, with tools for rapid application development and deployment. Aleri offers a range of solutions to common business problems, with CEP at the core of all solutions. In March of 2008, Aleri merged with Coral8, another leading provider of CEP technology enabling the company to offer a complete suite of tools and solutions focused on continuous intelligence and business agility in a fast paced business environment. Founded in 1999 and headquartered in Chicago, Aleri was privately held at the time of the transaction.
Friday, February 5, 2010
Saturday, January 30, 2010
Cleaning Shared Memory Segment and semaphore, for the ASE startup..
Panic dataserver, stopping it manually, and on restart showing issues with memory , meanwhile business people wants updates in every 5 mins...The situation is really worst for a DBA.
This posting is related to shared memory problem, for cleaning the shared memory:
When we shutdown the Sybase dataserver abruptly, by using the kill -9 or kill -12(or due to any reason automatically).
During the restart, sometime it gives the problem unable to create shared memory region, as below:
os_create_region: shmget (0x%x): %s
os_create_region: Shared memory segment %d is in the way
os_create_region: uninitialized shared memory descriptor
os_create_region: shmat (%d): %
Killing Process may left behind the System V semaphore or shared memory left behind instead of being cleaned up automatically. To eliminate unneeded semaphores or shared memory segments, we need to release semaphore or shared memory segment manually.
For the Semaphores:
Run the command ipcs -sa, it will give all semaphores active in the UNIX box, look for the value "0" in the column NSEMS. 0 values indicate that unused semaphore, find all semaphore for the Sybase user and remove them using command ipcrm -s
testinghostname:(/sybase)=>ipcs -sa
IPC status from as of Thu Sep 17 08:50:11 EST 2007
T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME
Semaphores:
s 201326671 0xc103d804 --ra-ra-ra- patrol dba patrol dba 2 8:45:15 0:00:08
s 201326668 0xc103d80e --ra-ra-ra- sybase dba sybase dba 0 8:50:08 0:00:00
testinghostname:(/sybase)=>ipcrm -s 201326668
For the Shared Memory:
To cleanup the Shared memory segment, which are assigned at OS level but not in use, run ipcs -ma command.
testinghostname:(/sybase)=>ipcs -ma
IPC status from as of Thu Sep 17 08:50:24 EST 2007
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME
Shared Memory:
m 654311446 0x4103d80e --rw-rw-rw- patrol dba patrol dba 0 2304 1766 1766 8:50:18 8:50:18 0:00:08
m 671088657 0x4103d80d --rw-rw-rw- sybase dba sybase dba 0 1792 1766 1762 8:45:15 8:45:15 0:00:08
m 671088650 0x4103d80b --rw-rw-rw- root root root root 0 768 1766 1766 8:50:18 8:50:18 0:00:08
m 671088648 0x4103d80a --rw-rw-rw- sybase dba sybase dba 1 1280 1766 1766 8:50:18 8:50:18 0:00:08
m 654311548 0x4103d809 --rw-rw-rw- sybase dba sybase dba 0 256 1766 1766 8:50:08 8:50:08 0:00:08
Now look in the NATTCH field for 0, if it 0 zero for Sybase user , it is unneeded, but still assigned at OS level. Remove it ipcrm -m by providing the id.
testinghostname:(/sybase)=>ipcrm -m 671088657 -m 654311548
Now Start the dataserver....
Same case with backup server, if u get any error with shared memory..!
Thanks.
Source : Sybooks and UNIX Manuals on wwww.
Same Thread @ http://www.sybaseteam.com/cleaning-shared-memory-segment-semaphore-for-ase-startup-t-715.html
This posting is related to shared memory problem, for cleaning the shared memory:
When we shutdown the Sybase dataserver abruptly, by using the kill -9 or kill -12(or due to any reason automatically).
During the restart, sometime it gives the problem unable to create shared memory region, as below:
os_create_region: shmget (0x%x): %s
os_create_region: Shared memory segment %d is in the way
os_create_region: uninitialized shared memory descriptor
os_create_region: shmat (%d): %
Killing Process may left behind the System V semaphore or shared memory left behind instead of being cleaned up automatically. To eliminate unneeded semaphores or shared memory segments, we need to release semaphore or shared memory segment manually.
For the Semaphores:
Run the command ipcs -sa, it will give all semaphores active in the UNIX box, look for the value "0" in the column NSEMS. 0 values indicate that unused semaphore, find all semaphore for the Sybase user and remove them using command ipcrm -s
testinghostname:(/sybase)=>ipcs -sa
IPC status from as of Thu Sep 17 08:50:11 EST 2007
T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME
Semaphores:
s 201326671 0xc103d804 --ra-ra-ra- patrol dba patrol dba 2 8:45:15 0:00:08
s 201326668 0xc103d80e --ra-ra-ra- sybase dba sybase dba 0 8:50:08 0:00:00
testinghostname:(/sybase)=>ipcrm -s 201326668
For the Shared Memory:
To cleanup the Shared memory segment, which are assigned at OS level but not in use, run ipcs -ma command.
testinghostname:(/sybase)=>ipcs -ma
IPC status from as of Thu Sep 17 08:50:24 EST 2007
T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME
Shared Memory:
m 654311446 0x4103d80e --rw-rw-rw- patrol dba patrol dba 0 2304 1766 1766 8:50:18 8:50:18 0:00:08
m 671088657 0x4103d80d --rw-rw-rw- sybase dba sybase dba 0 1792 1766 1762 8:45:15 8:45:15 0:00:08
m 671088650 0x4103d80b --rw-rw-rw- root root root root 0 768 1766 1766 8:50:18 8:50:18 0:00:08
m 671088648 0x4103d80a --rw-rw-rw- sybase dba sybase dba 1 1280 1766 1766 8:50:18 8:50:18 0:00:08
m 654311548 0x4103d809 --rw-rw-rw- sybase dba sybase dba 0 256 1766 1766 8:50:08 8:50:08 0:00:08
Now look in the NATTCH field for 0, if it 0 zero for Sybase user , it is unneeded, but still assigned at OS level. Remove it ipcrm -m by providing the id.
testinghostname:(/sybase)=>ipcrm -m 671088657 -m 654311548
Now Start the dataserver....
Same case with backup server, if u get any error with shared memory..!
Thanks.
Source : Sybooks and UNIX Manuals on wwww.
Same Thread @ http://www.sybaseteam.com/cleaning-shared-memory-segment-semaphore-for-ase-startup-t-715.html
Subscribe to:
Posts (Atom)