Posts

Automatic Standby PDB Instantiation and Standby Redo Log Creation in Oracle AI Database 26ai(23.26.2)

By -
  Oracle AI Database Release Update 23.26.2 introduces an important enhancement for Data Guard per Pluggable Database (PDB) environments. When a protected PDB is added through Data Guard Broker, Oracle automatically performs several tasks that previously required manual intervention. Prior to Release Update 23.26.2 , creating a standby PDB typically involved multiple manual steps, such as: Copying datafiles to the standby CDB Creating Standby Redo Logs (SRLs) Verifying the standby configuration Starting with 23.26.2 , Data Guard Broker automates these operations, simplifying the deployment process and reducing the risk of configuration errors. To demonstrate this enhancement, I created a standby PDB named AMOL on the standby database CDB2 using the following Broker command: DGMGRL> ADD PLUGGABLE DATABASE 'amol' AT cdb2 SOURCE is 'amol' AT cdb1 PDBFileNameConvert is "'/CDB1/','/CDB2/'" ; Pluggable Database "AMOL" added N...
Post a Comment
Read more

Oracle 26ai(23.26.2): WAIT and NOWAIT Support for DELETE, UPDATE, INSERT, and MERGE Statements

By -
  Rows modified by DML statements are locked and, if another session attempts to modify the same row, that session must wait until the row becomes available. In previous Oracle Database releases, the WAIT clause was supported only by the SELECT FOR UPDATE statement, enabling users to specify how long to wait for a row lock before the statement is rolled back. For example: Connected to Oracle Database 19 c Enterprise Edition Release 19.0 .0 .0 .0 SQL > select * from tbl for update wait 10 ; ORA -30006 : resource busy; acquire with WAIT timeout expired Similarly, the NOWAIT clause can be used to instruct the database to return immediately if the requested row is locked by another transaction: SQL > select * from tbl for update nowait; ORA -00054 : resource busy and acquire with NOWAIT specified or timeout expired If neither WAIT nor NOWAIT is specified, Oracle retains its default behavior and waits indefinitely for the row lock to become available: SQL > s...
Post a Comment
Read more