Unfortunately in Oracle you can’t create or drop database link in another schema. It’s very frustrating. Simple solution is to create anonymous block which will first create dummy function in another schema and then reuse it to create or drop an object(in our case database link).
Of course it can be reused to do other types of object as well.
If you want try to select CLOB column via database link then you get error ORA-22992
select * from <TABLE_NAME>@<DATABASE LINK>;
ORA-22992: cannot use LOB locators selected from remote tables
22992. 00000 - "cannot use LOB locators selected from remote tables"
*Cause: A remote LOB column cannot be referenced.
*Action: Remove references to LOBs in remote tables.
This article shows how to avoid this error
This article presents simple method how you can estimate index size for CREATE REBUILD operation
This article presents how-to dump SQL as CSV files using PL/SQL
The most popular method to clone a schema in Oracle is impdp tool. It allows to clone one or many schema between databases or inside the same database.
Impdp tool is based on PL/SQL package DBMS_DATAPUMP. This article shows how to use the package and clone a schema using pure PL/SQL.
This article presents methods to check storage performance IOPS and MBPS in Oracle:
- ORION tool
Oracle internal table SYS.USER$ has got many interesting columns for DBAs. This article describes some of them.
This article presents simple methods to write or read CLOB to/from file using following packages:
This article presents solution for “KUP-04026: field too long for datatype” for external tables. Usually it happens when you want to read data for CLOB columns.
Typical problem that you can encounter during tuning is how to change explain plan inside complex view or inside a subquery for your sql statements. QB_NAME hints helps to do it. It can define a name for a query block. This name can then be used in another query block to hint tables appearing in the named query block.