Enterprise Resource Planning or ERP is an industry term for integrated, multi-module application software packages that are designed to serve and support multiple business functions. An ERP system can include software for manufacturing, order entry, accounts receivable and payable, general ledger, purchasing, warehousing, transportation and human resources. Evolving out of the manufacturing industry, ERP implies the use of packaged software rather than proprietary software written by or for one customer.
This strategy reduces complexity and capital expenditures, provides faster backup and restore performance, eliminates tape capacity planning for backup and archive, and frees up administrative staff for higher value operations.
The company was able to replace their backup tape infrastructure with cloud-based Amazon S3 storage, eliminate backup software, and experienced a 12X performance improvement, reducing restore time from around 15 hours to 2. The Challenge As Amazon. This has caused growing pains related to backing up legacy Oracle databases to tape and led to the consideration of alternate strategies including the use of Cloud services of Amazon Web Services AWSa subsidiary of Amazon.
Some of the business challenges Amazon. Utilization and capacity planning is complex, and time and capital expense budget are at a premium. Significant capital expenditures were required over the years for tape hardware, data center space for this hardware, and enterprise licensing fees for tape software.
During that time, managing tape infrastructure required highly skilled staff to spend time with setup, certification and engineering archive planning instead of on higher value projects. And at the end of every fiscal year, projecting future capacity requirements required time consuming audits, Oracle dba case studies, and budgeting.
The cost of backup software required to support multiple tape devices sneaks up on you. The cost of this software was an ongoing budgeting pain point, but one that was difficult to address as long as backups needed to be written to tape devices.
Maintaining reliable backups and being fast and efficient when retrieving data requires a lot of time and effort with tape. When data needs to be durably stored on tape, multiple copies are required.
When everything is working correctly, and there is minimal contention for tape resources, the tape robots and backup software can easily find the required data. However, if there is a hardware failure, human intervention is necessary to restore from tape. This adds to the recovery time objective RTO and makes achieving it more challenging compared to backing up to Cloud storage.
Why Amazon Web Services Amazon. As part of that evaluation, they considered security, availability, and performance aspects of Amazon S3 backups. That cost benefit analysis included the following elements: Performance advantage and cost competitiveness.
It was important that the overall costs of the backups did not increase. At the same time, Amazon. The time and effort required for backup and for recovery operations proved to be a significant improvement over tape, with restoring from Amazon S3 running from two to twelve times faster than a similar restore from tape.
Backing up to on-premises disk based storage would have improved performance, but missed on cost competitiveness. Amazon S3 Cloud based storage met both criteria. Greater durability and availability. Amazon S3 is designed to provide Elimination of complex and time-consuming tape capacity planning.
AWS has enabled Amazon. These plans are then used to charge each organization for their tape usage, spreading the cost among many teams. With Amazon S3, teams simply pay for what they use, and are billed for their usage as they go.
There are virtually no upper limits as to how much data can be stored in Amazon S3, and so there are no worries about running out of resources. For teams adopting Amazon S3 backups, the need for formal planning has been all but eliminated.
This eliminates the burden of budgeting for capital equipment well in advance as well as the capital expense. Immediate availability of data for restoring — no need to locate or retrieve physical tapes. Whenever a DBA needs to restore data from tape, they face delays.
The tape backup software needs to read the tape catalog to find the correct files to restore, locate the correct tape, mount the tape, and read the data from it. In almost all cases the data is spread across multiple tapes, resulting in further delays.
This is especially severe during critical events such as a data center outage, when many databases must be restored simultaneously and as soon as possible. None of these problems occur with Amazon S3.Published quarterly, Profit is distributed to more than , C-level executives and provides business leaders with a road map on turning their technology investments into top and bottom line advantages.
Profit Online is the Web version of the magazine, delivering expanded, exlusive content that illuminates the business impact of technology and provides industry and line-of-business.
Apr 04, · Hang analysis - a case study-- Oracle database (RAC & stand-alone) Introduce: Any DBA they may have the production database hung issue.
At that time, the DB totally screwed the activities by all means [ Database connections were hanging, Connections on the server using SQL*Plus as sysdba was also hanging, EM grid was spinning ] Dammn totally stuck . you may encounter such trap in your DBA.
Reference: Troubleshooting the ‘Pending’ status for a Database Instance Target in Enterprise Manager 12c Cloud Control (Doc ID ) Send article as PDF This entry was posted in My Reference, Oracle Case Study, Oracle Point and tagged OEM, Oracle, Troubleshooting.
heartoftexashop.com is the world’s largest online retailer. In , heartoftexashop.com switched from tape backup to using Amazon Simple Storage Service (Amazon S3) for backing up the majority of its Oracle databases.
This strategy reduces complexity and capital expenditures, provides faster backup and restore performance, eliminates tape capacity planning for backup and archive, and frees up administrative.
Apr 16, · There will be a discussion of some specific differences in SQL to be aware of between Oracle and MySQL. My team put together a cheat sheet of . The case studies are based upon the Oracle demonstration database tables, emp and dept, owned by the user scott.
(In some case studies, additional columns have been added.)The case studies are numbered 1 through 11, starting with the simplest scenario and progressing in complexity.