These are some of the scripts that will create another script that will be executed. The idea behind these scripts is that DBA won’t have to execute these alter table or index or lob one by one, when there thousand of lines of scripts.
The first script is to move lob column from every table that is owned by a schema
This can be encountered in an environment that use two-phase commit, managed distributed transaction, and where the client is having a network problem with the database server. The setup was Oracle Weblogic 10.3.3 with Oracle’s Thin XA Driver, and Oracle 11g Database Server.
Usually the only problem when using SSL in WebLogic is hostname verification, which will make the server failed to start. However, for production it is recommended to use this, so it won’t be vulnerable with man-in-the-middle attack. This how-to will be based on Weblogic 10.3.3 and Solaris 10.
This how-to is based on Oracle Weblogic 10.3.3 on Solaris 10 (Unix/Linux), lately the release is faster ~.~, the environment will like three tier application where web-app-db reside in the different host.
Make sure to create generic JAVA_HOME, WLS_HOME, and Keystore directory the same in each host. In this case
JAVA_HOME = /opt/jdk1.6
WLS_HOME = /opt/oracle11
Keystore Dir. = /opt/oracle11/ssl
This article is not purely mine, I take this from another source, which I already forgot. However, I already used this to solve several issue regarding Oracle Jobs. To solve this issue will require Oracle SYS and Oracle OS user. Let start with listing the jobs
j.next_date - j.last_date interval,
from (select dj.LOG_USER, dj.JOB, dj.BROKEN, dj.FAILURES,
dj.LAST_DATE, dj.LAST_SEC, dj.THIS_DATE, dj.THIS_SEC,
dj.NEXT_DATE, dj.NEXT_SEC, dj.INTERVAL, dj.WHAT
from dba_jobs dj) j;