Archive

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

Sybase, Inc. Sybase reported record results for the quarter and full year ended Dec. 31, 2009. Among the company’s records were Q4 revenue of $331.7 million, annual revenue of $1.17 billion, and record operating margins and cash flow from operations. The company’s strong Q4 performance completes the best year in Sybase’s 25-year history.

Sybase Delivers Best Quarter in Company History, Resulting in Third Consecutive Year of Record Revenue!!

Sybase ASE 15.5 features the addition of two new options: ASE In-memory Databases (IMDB) and Advanced Backup Services. With these enhancements, ASE 15.5 continues to deliver unparalleled performance and manageability for data intensive environments that require very low response times and high throughput.

The IMDB option in Sybase ASE 15.5 enables data virtualization and scaling critical to meeting the needs of high data volume and high concurrent user organizations, whether deployed in public cloud or private data center environments. Unlike other in-memory products, the ASE 15.5 IMDB is fully integrated within ASE, eliminating the need for application changes and providing the flexibility that allows in-memory databases to be configured to meet application requirements.

“In-memory DBMS is an important dimension of the DBMS landscape, and will become more so in the coming years,” said Carl Olofson, Vice President of Research at IDC. “The Sybase developments that provide transparent in-memory database management show clear leadership in the DBMS field.”

ASE 15.5 also increases efficiency in the data center with the integration of the ASE Backup Server with Tivoli® Storage Manager (TSM) from IBM. With this support, ASE databases can be backed up on any TSM supported media, providing faster backups and restores with less network and storage resources required. This new integration provides a cost effective solution for storage management.

“The database management features offered by Sybase ASE 15.5 coupled with the storage management features offered by IBM® TSM provide a powerful solution to overcome the challenges of data protection faced in today’s business environment.” said Richard Vining, Product Marketing Manager, IBM Tivoli Storage. “We are pleased to provide Sybase ASE with the Ready for Tivoli software designation, which shows customers that the solution meets or exceeds IBM compatibility criteria and successfully integrates with one or more IBM Tivoli Software products.”

“In data centers, the IT challenge is to increase efficiency and availability while lowering data center costs. At the same time, application deployments in grid and cloud computing environments are increasing the requirements of transaction processing systems to support large volumes of concurrent users with high transaction rates,” said Brian Vink, vice-president, data management products, Sybase. “ASE 15.5 addresses these extreme requirements by delivering increased data throughput and greater concurrent activity while elevating productivity and uptime.”

Hi Folks,
For the checking latency between Primary and Replicated DBs , we have several methods.

Here, I am posting the manual method for checking the replication latency. If you have any more thoughts, please comment it out.

Rite Now I am travelling to Delhi, my train got late, so I am spending my time with my fav, with new posting in blog.

For calculating the latency, we can make two tables in PDB and RDB with column as defaut datetime, and setup replication between these two tables.

Before excuting the batch of your’s queries, insert the id (only for reference for the point, where we executed the insert statement) and it will update the primary_datetime by default current system date.

After the completing the batch, insert the the next id, automaticaly it will get the finish date in default column.

Now go to RDS and check the diff between primary_datetime and replicate_datetime.

Sybase Software (India) Pvt. Ltd, the Indian subsidiary of Sybase, Inc., a provider of enterprise infrastructure and mobile software, today announced that it entered into a master reseller agreement with Inflow Technologies Pvt. Ltd in India.

The agreement will enable Inflow Technologies to extend the benefits of Sybase’s offerings, particularly analytics and enterprise mobility, to the growing market in India, said a press release.

Inflow Technologies, part of the US$ 5 billion Datatec Group, has presence in more than 12 locations across India and Sri Lanka.
Sources : news, www.

Subscribe Us

Leave Blank:Do Not Change:

Your email:

Worldwide Visitors

Contributors

Anurag has more than 6+ years of experience in Sybase Database Development .His Area of expertise includes Performance, Query Optimization, Cost Optimization, TSQL Development. He is also involved in Consultancy to Financial Firms for Database Implementation and Maintenance. He has supported many Global Financial firms and recently started a new portal -Mati Rang. AnVa (Founder) has more than 6+ years Exp in Sybase ASE/REP Database Administration. His area of interest is ASE Implemenation and maintenance , Performace Tunning , Sybase HA ,Shared Cluster and Replication. Also exploring the In-Memory Databases (HANA) , Big Data, Hadoop and Java. He is also supporting the Forum Sybase Team and started this sybaseblog.com in late 2009.Andrew is Guest Blogger on sybaseblog.com. Andrew have been working with Sybase for more than a decade: ASE & RS mostly.
He has written lot of tools that help to manage/monitor the system for ASE and Replication and some tools are on the way..
He is also poet and love to be creative all the way.

Admin

Disclaimer

This Blog is neither sponsored by nor in any way affiliated with SAP & Sybase,Inc. In any case, neither any authors nor SAP & Sybase Inc assumes any responsibility for errors in the blog postings, nor do they have any liblilties for damages resulting from the use of blog postings.If you are using any Supported & Unsupported commands/features listed in blog, this is completely on your(user) risk, sybaseblog.com not having any libilitiy.

This blog is only for sharing purpose. The opinions expressed here represent bloggers own and not those of their any past and present employer.