- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Speed up Oracle log application
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-31-2008 10:58 PM
тАО07-31-2008 10:58 PM
Both systems (Primary & DR) run on PA RISC Superdome (16 CPU with 32 GB RAM). Archive logs are transferred from PR to DR on real time basis. Log file size is 200 MB each. On an average more than 200 archive files are generated.
Log application at DR is done using Shell script and cron. During log application, some archive files are applied within 2 minutes whereas some files take more than 10 minutes. I would like to know:
1. Why such difference in timing?
2. What can be done at Oracle/HP-UX level to speed up log application.
3. Any tuning at storage level (XP1024) that can help?
Thanks.
sks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-01-2008 08:45 AM
тАО08-01-2008 08:45 AM
Solutionapplying redo to a small table results in the table being quickly completly inside the db-cache. So recovery requires mostly read of data and only a few writes to disk.
Applying redo to big tables results in some blocks may have need to be flushed back to disk, to regain space inside the dbcache for other objects that need recovery. This might require more writes during recovery and is more expensive.
I assume you have a central SAP instance on the same host, which is usually not active :-) during standby application, so you can give the RAM from the SAP CI to the DB cache while you do the recovery.
This will require to dynamicly reduce the db-cache after the database has been opened (or restart with diffrent init.ora if this feels better) to give the RAM back to the central instance.
In addition you could check, if you can utilize parallel recovery.
alter database recover parallel ....
More cache on the storage sides helps as well.
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2008 01:19 AM
тАО08-04-2008 01:19 AM
Re: Speed up Oracle log application
recover automatic standby database parallel 32;
significantly reduced the recovery time.
Oracle MAA site also provided great white papers.
http://www.oracle.com/technology/deploy/availability/htdocs/maa.htm
sks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2008 06:08 AM
тАО08-05-2008 06:08 AM
Re: Speed up Oracle log application
check if parameter
parallel_min_servers = 32
helps you to reduce the overhead to start 32 slaves all the time again when a log comes in.
If they stay alive all the time it might be even better.
Volker
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-05-2008 08:57 PM
тАО08-05-2008 08:57 PM
Re: Speed up Oracle log application
As we start Oracle periodically and apply logs in bulk, this parameter may not be required.
However we have set the parameter parallel_max_servers to a value higher than int set in "RECOVER int" statement.
sks