Posts

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

Excluding LOB Columns Data in Data Pump

By -
Image
  We intend to create a dump from a table in which some columns contain LOB data. However, due to the large volume of LOB data in this table — and for reasons such as higher speed, better security, or reduced space allocation — we want to prevent this data from being included in the dump file, or at least prevent it from being restored during the import process. What is the solution? Excluding LOB column data during the  export  operation in Oracle 12c can be easily controlled. This can be done by creating a view and using the  VIEWS_AS_TABLES  parameter. However, if the dump file already contains LOB data, this method cannot be used during import. In such cases, the  REMAP_DATA  parameter is the solution. Previously, we explained that the  REMAP_DATA  parameter can be used for data masking and data manipulation during export and import operations. In this article, we will see how the same parameter can be used to exclude LOB column data duri...
Post a Comment
Read more