Posts

26ai- Using Tags in Oracle Data Guard Broker

By -
  Oracle AI Database 26ai adds tagging support to Oracle Data Guard Broker, allowing administrators to attach custom metadata to configuration members. With tags, you can attach your own information to Data Guard members. Think of it as adding labels to databases so they become easier to identify later. For example, you may want to store: * Deployment location * Environment type * Build date * Owner team * Compliance information Before using tags, the feature must be enabled. DGMGRL> EDIT CONFIGURATION SET PROPERTY TagMode= 1 ; Property "tagmode" updated In this demo, I added two tags to the member dg1. The first tag stores the location of the database: DGMGRL > EDIT MEMBER dg1 SET TAG location = 'BABOL' ; Tag "location" updated in "dg1". The second tag stores a configuration date: DGMGRL > EDIT MEMBER dg1 SET TAG configuation_date = '2026-02-25' ; Tag "configuation_date" updated in "dg1". Now we c...
Post a Comment
Read more

Automatic temp file creation on the standby - Oracle AI Database 26ai

By -
Image
  In Oracle Database 19c, when a tempfile is added on the primary database, it is   not automatically created   on the physical standby database. This is because Oracle does not generate redo for tempfile-related DDL operations (such as creating, adding, resizing, or dropping tempfiles). Behavior in Oracle Database 19c For example, when creating a temporary tablespace on the primary database(19c): — Primary SQL > create temporary tablespace TEMP1404; Tablespace created. SQL > select ts# from v$tablespace where NAME = 'TEMP1404' ; TS# ---------- 15 SQL > select name from v$tempfile where ts# = 15 ; NAME -------------------------------------------------------------------------------- + DATA / HUME / B3AE49A3735D8867E053088A210A341D / TEMPFILE / temp1404 .807 .1225812657 On the standby database, although the tablespace metadata exists, the tempfile itself is not created: — Data Guard SQL > select ts# from v$tablespace where NAME = 'TE...
Post a Comment
Read more

Managing Alert Log Size in Oracle AI Database 26ai

By -
Image
  Starting with   Oracle AI Database 26ai (Release Update 23.9) , it is possible to control the maximum size of the alert log using the   ALERT_LOG_MAX_SIZE   parameter. The default value for this parameter is 1000 MB, which means the XML alert log can grow up to a maximum of 20 segments, each 50 MB in size. In my test, I configured the alert log maximum size to 100 MB: SQL > ALTER SYSTEM SET alert_log_max_size = 100 M; System altered. ***This parameter is modifiable using  ALTER SYSTEM , but it is not modifiable at the PDB level. To increase the size of the alert log and force file generation, I executed the following PL/SQL block to continuously write messages into the alert log: begin for i in 1 .. 1000000 loop begin sys.dbms_system.ksdwrt( 2 , 'Vahid Yousefzadeh' ); end ; end loop; end ; / After running this block, there are several XML files in the alert directory and each file size is approximately 50MB. [root @OEL9 - DB2 al...
Post a Comment
Read more