foalabs

UnderStanding Global Temporary Table in Oracle Database In Oracle, Global Temporary Tables (GTTs) are a special type of table designed to hold data that is session-specific or transaction-specific. Unlike permanent tables, the data in a global temporary table exists only for the duration of a session or a transaction. This makes GTTs a great option when you need to store intermediate data, temporary results, or perform operations that require temporary data storage without impacting the permanent data. This article provides an in-depth look at GTTs, how they work, their use cases, and technical details about how they are implemented in Oracle. Key Features of Global Temporary Tables Session or Transaction-Specific Data : Data inserted into a GTT is visible only to the session that inserted it. Other sessions cannot access this data. The data can either be retained for the entire duration of the session or only until the transaction ends, depending on the table definition. No Permanent...

How to reconfigure patch file system in EBS R12.2 We had a scenarios where I need to re-create or again configure the patch file system in ebs. Steps 1. Run adpreclone.pl on run file system Source run file system. $ perl adpreclone.pl appsTier   2. Detach PATCH homes: Below Oracle Homes are registered in the inventory which needs to be deregistered: /u01/app/fs2/FMW_Home/Oracle_EBS-app1 /u01/app/fs2/FMW_Home/webtier /u01/app/fs2/FMW_Home/oracle_common   cd $FMW_HOME/oracle_common/oui/bin ./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/Oracle_EBS-app1 -silent ./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/webtier -silent ./runInstaller -removeHome ORACLE_HOME=/u01/app/fs2/FMW_Home/oracle_common -silent     3. Run adcfgclone.pl on run file system.   cd $COMMON_TOP/clone/bin/ [applmgr@funebs bin]$ perl adcfgclone.pl appsTier Copyright (c) 2002, 2015 Oracle Corporation Redwood Shores, California, USA Oracle E-Business Suite Rapid Clone Ver...

Expdp of  Table Returns ORA-39166 or ORA-31655 in Oracle Database Certain system-generated schemas, such as SYS , MDSYS , and ORDSYS , cannot be exported using exp or expdp because they hold Oracle-managed data and metadata. These schemas are essential for the internal functioning of the database and are excluded from export operations. Additionally, some tables owned by users like SYS or APEX_040200 are automatically skipped during export. These tables are also not eligible for export, even if explicitly specified, as they contain Oracle's internal data. For example, certain tables owned by SYSTEM user like below cannot be exported: % expdp system/<PASSWORD> directory=<DIRECTORY_NAME> tables='<TABLE_NAME>' Export: Release 12.1.0.2.0 - Production on Thu Mar 3 20:39:27 2016 Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Parti...

ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set Error: [oracle@fundb ~]$ dgmgrl DGMGRL for Linux: Release 12.2.0.1.0 - Production on Sat Jul 19 18:03:42 2019 Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved. Welcome to DGMGRL, type "help" for information. DGMGRL> connect / Connected to "PRIM_CL" Connected as SYSDG. DGMGRL> DGMGRL> create configuration 'PRIM_CL' as primary database is 'PRIM_CL' connect identifier is PRIM_CL; Configuration "PRIM_CL" created with primary database "PRIM_CL" DGMGRL> DGMGRL> add database 'STAN_CL' as connect identifier is STAN_CL maintained as physical; Error: ORA-16698: member has a LOG_ARCHIVE_DEST_n parameter with SERVICE attribute set Failed. DGMGRL> DGMGRL> exit Solution: 1. Remove the DG Broker configuration DGMGRL> remove configuration; Removed configuration DGMGRL> 2. Disable log_archive_dest_2 On Prim...

Step-by-Step Guide to Set Up Data Guard Broker in Oracle Oracle Data Guard Broker is a distributed management framework that automates and centralizes the creation, configuration, and monitoring of a Data Guard configuration. It simplifies many of the tasks related to managing Data Guard. This guide outlines the step-by-step process for setting up the Data Guard Broker in Oracle. Pre-Requisites Before setting up Data Guard Broker, ensure that: You have an Oracle Database environment configured with a primary and standby database. Data Guard is already configured and running between the primary and standby databases. Both the primary and standby databases are using Oracle Enterprise Edition . Oracle Net Services is configured to allow connectivity between the primary and standby systems. Step 1: Enable Force Logging and Archive Log Mode on Primary First, ensure that the primary database is in archive log mode and force logging is enabled: Log in to the primary database as SYSDB...

How To Use Datapump Between Different Database Releases Using Oracle Data Pump between different database releases is a common practice for moving data, especially when upgrading from an older version to a newer version. Data Pump provides the flexibility to export from one database release and import into another, whether the target database is newer or the same version. Here’s a guide on how to use Data Pump ( expdp / impdp ) between different Oracle database releases. General Process Overview: Export the data from the source database using expdp (Data Pump Export). Import the data into the target database using impdp (Data Pump Import). Handle any compatibility issues, especially when exporting from a newer database version to an older one. Data Pump Basics Data Pump utilities: expdp : Data Pump Export utility used to export data from a database. impdp : Data Pump Import utility used to import data into a database. Both of these utilities work with dump files to transport data...