Patent application number | Description | Published |
20090070558 | MULTIPLEXING PER-PROBEPOINT INSTRUCTION SLOTS FOR OUT-OF-LINE EXECUTION - The present invention provides a probe system and method for multithreaded user-space programs. The system includes an instrumentation module that enables single stepping out of line processing for multithreaded programs, an establish probepoint module that divides up an area of the probed program's memory into a plurality of instruction slots, an ensure slot assigned module that ensures that an instruction slot is assigned to a probepoint, a slot acquisition module that acquires the instruction slot for the probepoint, stealing a slot from another probepoint as needed, and a free slot module that relinquishes the instruction slot owned by the probepoint when the probepoint is being unregistered. | 03-12-2009 |
20090070867 | METHOD FOR SECURELY ENABLING DYNAMIC INSTRUMENTATION - A method is provided for securely enabling dynamic instrumentation. The method includes categorizing probes, upon creation, into one or more classes, providing lists of permissions for activating the probes and associating users with the permissions for activating the probes, such that certain users have permissions for activating certain probes. Users are associated with permissions by mapping classes of probes to permissions and mapping users to permissions, mapping classes of users to probes, or mapping users to at least one of classes of probes and classes of capabilities. | 03-12-2009 |
20110320404 | STANDBY INDEX IN PHYSICAL DATA REPLICATION - Generating a standby index on a standby database server in a physical log-shipping data replication environment. Embodiments of the invention include providing a primary database server and a standby database server, replicating a primary database and a primary database index from the primary database server to the standby database server, generating a standby index on the standby database server, and cataloging the standby index on the standby database server. | 12-29-2011 |
20130006932 | Physical Replication of Database Subset to Improve Availability and Reduce Resource Cost in a Cloud Environment - An approach is provided in which a standby component receives a database log record that corresponds to a modification to one of a primary database's corresponding physical storage spaces. The standby component determines whether a modified object associated with the database log record corresponds to a standby database, which includes a replication of a subset of the primary database's corresponding physical storage spaces. When the standby component determines that the modified object corresponds to the standby database, the standby component invokes a physical replay that replicates the modification on the standby database. | 01-03-2013 |
20130198134 | ONLINE VERIFICATION OF A STANDBY DATABASE IN LOG SHIPPING PHYSICAL REPLICATION ENVIRONMENTS - Techniques are disclosed for performing an operation for determining whether a standby database is synchronized with a primary database in a log shipping physical database replication environment. In one embodiment, the operation may include receiving a transaction log at the standby database from the primary database. The transaction log may specify a first one or more checksum values for a first set of pages on the primary database. The operation may also include calculating a second one or more checksum values for a second set of pages on the standby database. The operation may also include determining whether the standby database is synchronized with the primary database by comparing the first one or more checksum values with the second one or more checksum values. | 08-01-2013 |
20130246358 | ONLINE VERIFICATION OF A STANDBY DATABASE IN LOG SHIPPING PHYSICAL REPLICATION ENVIRONMENTS - Techniques are disclosed for performing an operation for determining whether a standby database is synchronized with a primary database in a log shipping physical database replication environment. In one embodiment, the operation may include receiving a transaction log at the standby database from the primary database. The transaction log may specify a first one or more checksum values for a first set of pages on the primary database. The operation may also include calculating a second one or more checksum values for a second set of pages on the standby database. The operation may also include determining whether the standby database is synchronized with the primary database by comparing the first one or more checksum values with the second one or more checksum values. | 09-19-2013 |
20150081639 | OPTIMIZING THE NUMBER AND TYPE OF DATABASE BACKUPS TO ACHIEVE A GIVEN RECOVERY TIME OBJECTIVE (RTO) - A method of optimizing the number and type of database backups to achieve a given RTO is provided and may include receiving a RTO and receiving a heuristic for determining an amount of unencumbered processing time. A type of next backup, (i.e., a next backup), is determined wherein the type of next backup is an incremental backup when the sum of the heuristic, and the times to: restore the latest full backup, restore zero or more incremental backups, complete a current incremental backup, and perform a full backup is less than the received RTO, else the type of the next backup is a full backup. A time to schedule the next backup is scheduled based on the received RTO being a total of an amount of time to: complete the type of next backup; rollforward zero or more transaction log records; and to restore at least one backup. | 03-19-2015 |
20150081643 | CLASSIFYING AND MONITORING DATABASE OPERATIONS BASED ON A COST OF RECOVERY - A method of classifying and monitoring database operations based on a recovery cost may include receiving an indication of a recoverable operation. A count in a persistent storage, such as a catalog, corresponding to an occurrence of the recoverable operation is incremented. | 03-19-2015 |
20150081646 | CLASSIFYING AND MONITORING DATABASE OPERATIONS BASED ON A COST OF RECOVERY - A method of classifying and monitoring database operations based on a recovery cost may include receiving an indication of a recoverable operation. A count in a persistent storage, such as a catalog, corresponding to an occurrence of the recoverable operation is incremented. | 03-19-2015 |