Oracle SQL Developer Shortcuts
Thursday, October 29, 2020
Saturday, October 17, 2020
Friday, October 16, 2020
Administering the DDL Log Files in 12c
Administering the DDL Log Files in 12c
The DDL log is created only if the ENABLE_DDL_LOGGING initialization parameter is set to TRUE. When this parameter is set to FALSE, DDL statements are not included in any log. A subset of executed DDL statements is written to the DDL log.
How to administer the DDL Log?
--> Enable the capture of certain DDL statements to a DDL log file by setting ENABLE_DDL_LOGGING to TRUE.
--> DDL log contains one log record for each DDL statement.
--> Two DDL logs containing the same information:
--> XML DDL log: named log.xml
--> Text DDL: named ddl_<sid>.log
When ENABLE_DDL_LOGGING is set to true, the following DDL statements are written to the log:
ALTER/CREATE/DROP/TRUNCATE CLUSTER
ALTER/CREATE/DROP FUNCTION
ALTER/CREATE/DROP INDEX
ALTER/CREATE/DROP OUTLINE
ALTER/CREATE/DROP PACKAGE
ALTER/CREATE/DROP PACKAGE BODY
ALTER/CREATE/DROP PROCEDURE
ALTER/CREATE/DROP PROFILE
ALTER/CREATE/DROP SEQUENCE
CREATE/DROP SYNONYM
ALTER/CREATE/DROP/RENAME/TRUNCATE TABLE
ALTER/CREATE/DROP TRIGGER
ALTER/CREATE/DROP TYPE
ALTER/CREATE/DROP TYPE BODY
DROP USER
ALTER/CREATE/DROP VIEW
Example
$ more ddl_orcl.log
Thu Nov 15 08:35:47 2012
diag_adl:drop user app_user
Locate the DDL Log File
$ pwd
/u01/app/oracle/diag/rdbms/orcl/orcl/log
$ ls
ddl ddl_orcl.log debug test
$ cd ddl
$ ls
log.xml
Notes:
- Setting the ENABLE_DDL_LOGGING parameter to TRUE requires licensing the Database Lifecycle Management Pack.
- This parameter is dynamic and you can turn it on/off on the go.
- alter system set ENABLE_DDL_LOGGING=true/false;
How to set oracle path in Linux
How to set oracle path in Linux
[oracle@test04 ~]$vi MQTEST.env
export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH:.
export ORACLE_SID=MQTEST
ALERT=/u01/app/oracle/diag/rdbms/mqprod/MQTEST/trace
:wq!
Different types of Shared Memory available in Solaris
Different types of Shared Memory available in Solaris
1) Shared Memory (SHM)
-basic anonymous shared memory
-also called Pageable Shared Memory
-pages can be swapped out during memory shortages which affects the application performance
2) Intimate Shared Memory (ISM)
-is used by default in Solaris
-cannot be dynamically resized
-if you want to modify (e.g. resize) a segment you must restart the processes
-does not need swap space
-segments are automatically locked by the Solaris kernel
3) Dynamic Intimate Shared Memory (DISM)
-allows shared memory segments to be adjusted dynamically (resized or relocated) (e.g. SGA can be resized) - no restart of the processes necessary
-shared memory segments can be locked by the applications by using mlock(3C)
-kernel virtual-to-physical memory address translation structures are shared between processes that attach to the DISM segment, saving kernel memory and CPU time
-needs swap space as it makes reservations on it
4) Optimized Shared Memory (OSM)
-the most recommended shared memory
-provides similar benefits as DISM but without some of the requirements of DISM
Reference metalink Doc ID 1010818.1
ggsci fails with error 'symbol lookup error' on new installation
ggsci fails with error 'symbol lookup error' on new installation
Symptoms:
Installing OGG12.3.0.2 , while invoking ggsci gets below error...
./ggsci: symbol lookup error: /optware/software/gg12_3/libggparam.so: undefined symbol:_ZZ11ggGetConfigE4pcfg
Cause:
OGG version 12.3 is not compatible with linux 5
++ Certification matrix link
https://mosemp.us.oracle.com/epmos/faces/CertifyResults?searchCtx=st%5EANY%7Cpa%5Epi%5E922_Oracle+GoldenGate%7Evi%5E435776%7Epln%5EAny%7E%7C&_afrLoop=246908612827636
Solution:
OGG 12.3 is not compatible with Linux 5.
To confirm, check OS version
> uname -a
You may use OGG 12.2 versions which supports Linux 5
Reference metalink Doc ID 2352254.1
Subscribe to:
Comments (Atom)