Abstract: Disclosed is an improved approach to implement a mechanism to provide customer control over access to cloud infrastructure by the cloud provider's operator employees. This mechanism allow customer controlled access to any cloud infrastructure that belongs to or is otherwise allocated to the customer.

Abstract: Disclosed is an improved approach to implement a cloud access control mechanism. The mechanism provides customer control over access to cloud infrastructure by the cloud provider's operator employees, where the approach provides an override mechanisms for allowing operator access without additional customer approval based upon configured policies/rules.

Abstract: Disclosed is an improved approach to implement a mechanism to provide customer control over access to cloud infrastructure by the cloud provider's operator employees. This mechanism allow customer controlled access to any cloud infrastructure that belongs to or is otherwise allocated to the customer.

Abstract: Techniques for detecting an anomaly in queries of a relational database are disclosed. The techniques include identifying a set of attribute values from a query for accessing data within a database. Based on previously received queries, at least one of a joint probability for the set of attribute values or individual probabilities for the set of attribute values is determined. When at least one of the joint probability for the set of attribute values or an individual probability for one or more attribute values in the set of attribute values does not satisfy a probability cutoff, an indication that the query is anomalous is outputted.

Abstract: Techniques for detecting an anomaly in queries of a relational database are disclosed. The techniques include obtaining a set of semantic attributes for a query of a relational database. The semantic attributes are then used to calculate a set of similarities between the query and a set of non-anomalous queries of the relational database. When a highest similarity in the set of similarities does not meet a similarity threshold, an indication that the query is anomalous is outputted.

Abstract: Systems for high-performance, low-latency database log mining applications. A method commences upon receiving a log mining query. The query specifies desired results that correspond to a prior logical state of the database system. A first type of processing entity is invoked to process contents of the redo stream by loading metadata into a data dictionary, and a second type of processing entity is invoked to construct metadata from the redo stream, wherein the constructed metadata pertains only database objects referenced in the query. During the time that the first type of processing entity is processing contents of the redo stream by loading metadata into a data dictionary, a process of a second type serves incoming queries using a subset of entries in the redo stream. When the data dictionary is completed, a switchover point is reached and thenceforth, incoming queries are served using the first type of processing entity.

Abstract: Techniques for detecting an anomaly in queries of a relational database are disclosed. The techniques include identifying a set of attribute values from a query for accessing data within a database. Based on previously received queries, at least one of a joint probability for the set of attribute values or individual probabilities for the set of attribute values is determined. When at least one of the joint probability for the set of attribute values or an individual probability for one or more attribute values in the set of attribute values does not satisfy a probability cutoff, an indication that the query is anomalous is outputted.

Abstract: Techniques for detecting an anomaly in queries of a relational database are disclosed. The techniques include obtaining a set of semantic attributes for a query of a relational database. The semantic attributes are then used to calculate a set of similarities between the query and a set of non-anomalous queries of the relational database. When a highest similarity in the set of similarities does not meet a similarity threshold, an indication that the query is anomalous is outputted.

Abstract: Systems for high-performance, low-latency database log mining applications. A method commences upon receiving a log mining query. The query specifies desired results that correspond to a prior logical state of the database system. A first type of processing entity is invoked to process contents of the redo stream by loading metadata into a data dictionary, and a second type of processing entity is invoked to construct metadata from the redo stream, wherein the constructed metadata pertains only database objects referenced in the query. During the time that the first type of processing entity is processing contents of the redo stream by loading metadata into a data dictionary, a process of a second type serves incoming queries using a subset of entries in the redo stream. When the data dictionary is completed, a switchover point is reached and thenceforth, incoming queries are served using the first type of processing entity.

Abstract: A method, system, and computer program product for upgrading high-availability database systems. The method commences by specifying a subject database configuration state (e.g., an initial state) as well as an upgraded database configuration state (e.g., an upgraded state). Then, the method performs operations for compiling the specifications and validating the upgraded database configuration state with respect to the specified subject database configuration state. Compile errors are reported and a user can change the specifications. Once the compiler determines that the upgraded configuration state can be reached from the subject database configuration state, then the method generates an upgrade plan. The upgrade plan is executed by a computer-implemented controller. During execution of the plan, the controller pauses for accepting user intervention at key execution points. The controller monitors state changes to establish checkpoints.

Abstract: The present technology relates to compositions and methods useful for preventing and treating degenerative eye diseases or disorders. The compositions and methods include ocular biomaterials. In some embodiments, the ocular biomaterial compositions include retinal biomaterial, interphotoreceptor matrix biomaterial or a combination thereof. In some embodiments, the ocular biomaterial compositions are formed into films, gels, scaffolds and matrices for cell delivery.

Abstract: A database rollback processor allows rollback, or rewind, of the data and metadata to a point at which a failover or other metadata change occurred, therefore “rewinding” the metadata to a previous consistent point. The rollback processor identifies transaction entries in a redo log resulting in changes to the metadata. The changes are identified backward to a target recovery time. Transactions affecting the metadata are stored in a stack. The transactions are then backed out of the metadata according to the stack to restore the metadata to the state at the target recovery time. Data changes from the redo log may then be applied to the corresponding metadata as it existed at the target recovery time. Since the target recovery time is not bound by the timing of the snapshots, but rather may be at an arbitrary point chosen as the target recovery time, a failover, replication or recovery operation need not rely on the snapshot time.

Abstract: Computer-implemented methods and computer systems for automatically managing stored checkpoint data are described. The method includes accessing a first user defined time period. The first user defined time period is related to a plurality of stored checkpoint data, and each checkpoint data of the plurality of stored checkpoint data has an associated storage time. Further, the method includes identifying a first set of checkpoint data having storage times that are within the first user defined time period. Moreover, the method includes identifying a second set of checkpoint data having storage times that are older than the first user defined time period. In addition, the method includes pruning the second set of checkpoint data according to a user specified process in proportion to storage time of each checkpoint data of the second set of checkpoint data. The older stored checkpoint data is more heavily pruned over recent stored checkpoint data.

Abstract: A method and system that annotates a redo log to provide information concerning the execution of a procedure at a primary database. The annotations include entry and exit markers that indicate the beginning and the end of the execution along with any arguments passed to the procedure, and whether the execution of the procedure was successful. At the standby database, these markers are used to create a logical transaction associated with the procedure. The operations performed by the procedure are grouped into individual transactions, and these individual transactions are grouped as belonging to the logical transaction. If the execution of the procedure was successful at the primary database, then the individual transactions are discarded, and the logical transaction is applied by executing the procedure at the standby database. If the execution of the procedure failed at the primary database, then the individual transactions and the logical transaction are discarded.

Abstract: A method, system, and computer program product for upgrading high-availability database systems. The method commences by specifying a subject database configuration state (e.g., an initial state) as well as an upgraded database configuration state (e.g., an upgraded state). Then, the method performs operations for compiling the specifications and validating the upgraded database configuration state with respect to the specified subject database configuration state. Compile errors are reported and a user can change the specifications. Once the compiler determines that the upgraded configuration state can be reached from the subject database configuration state, then the method generates an upgrade plan. The upgrade plan is executed by a computer-implemented controller. During execution of the plan, the controller pauses for accepting user intervention at key execution points. The controller monitors state changes to establish checkpoints.

Abstract: A method and system that annotates a redo log to provide information concerning the execution of a procedure at a primary database. The annotations include entry and exit markers that indicate the beginning and the end of the execution along with any arguments passed to the procedure, and whether the execution of the procedure was successful. At the standby database, these markers are used to create a logical transaction associated with the procedure. The operations performed by the procedure are grouped into individual transactions, and these individual transactions are grouped as belonging to the logical transaction. If the execution of the procedure was successful at the primary database, then the individual transactions are discarded, and the logical transaction is applied by executing the procedure at the standby database. If the execution of the procedure failed at the primary database, then the individual transactions and the logical transaction are discarded.

Abstract: Techniques for making light-weight checkpoints in logs of streams of transactions and for extending the logs from the checkpoints. The state saved in the light weight checkpoint need only include the state of all transactions that are active at a prior point in the log and are still active at the checkpoint. A log is extended from the checkpoint by processing new transactions in the transaction stream beginning at the prior point to produce the extending log. When the checkpoint is reached, the state saved at the checkpoint is used to continue to produce the extending log. Techniques are further disclosed for selecting points in the stream of transactions at which the checkpoints may be made and for determining the distance between checkpoints. As disclosed, the log in which the checkpoints are used is a logical log made from a physical log produced by a relational database system. The logical log may be used for replication and for data mining.

Abstract: A method and system that annotates a redo log to provide information concerning the execution of a procedure at a primary database. The annotations include entry and exit markers that indicate the beginning and the end of the execution along with any arguments passed to the procedure, and whether the execution of the procedure was successful. At the standby database, these markers are used to create a logical transaction associated with the procedure. The operations performed by the procedure are grouped into individual transactions, and these individual transactions are grouped as belonging to the logical transaction. If the execution of the procedure was successful at the primary database, then the individual transactions are discarded, and the logical transaction is applied by executing the procedure at the standby database. If the execution of the procedure failed at the primary database, then the individual transactions and the logical transaction are discarded.

Abstract: A method and apparatus for applying changes to a standby database in real-time. According to one aspect, a change is applied to data contained in a standby database. The standby database functions as a replica of a primary database. The primary database has a current online redo log file to which a particular redo block was written. According to one aspect, prior to the archiving of the current online redo log file, the particular redo block is received at a process associated with the standby database. A change indicated by the particular redo block is applied to the data contained in the standby database.

Abstract: Techniques for making light-weight checkpoints in logs of streams of transactions and for extending the logs from the checkpoints. The state saved in the light weight checkpoint need only include the state of all transactions that are active at a prior point in the log and are still active at the checkpoint. A log is extended from the checkpoint by processing new transactions in the transaction stream beginning at the prior point to produce the extending log. When the checkpoint is reached, the state saved at the checkpoint is used to continue to produce the extending log. Techniques are further disclosed for selecting points in the stream of transactions at which the checkpoints may be made and for determining the distance between checkpoints. As disclosed, the log in which the checkpoints are used is a logical log made from a physical log produced by a relational database system. The logical log may be used for replication and for data mining.