OracleLog

Empty sql_id and other columns in v$session for jobs - 10.2.0.3

gato — Sun, 06 Jul 2008 08:36:38 +0000

10.2.0.3 has a nasty bug, where one is not able to see what SQL is job actually executing, the following fix will resolve that partially. For parallel slaves the relevant v$session columns are still going to be empty.

5928612 SQL ADDRESS COLUMN IN V$SESSION VIEW FOR JOB IS ZERO

This might be resolved completely in 10.2.0.4, anyone?

Oracle Identity Management(OIM) How to reset OID cn=orcladmin password

gato — Fri, 04 Apr 2008 14:43:43 +0000

If you wonder what is the password for Oracle Internet Directory(OID) user cn=orcladmin after OIM installation, well, it is exactly the same as ias_admin password specified during installation of OIM. If you really want to reset the password, use included utility resetiASpasswd.sh in $ORACLE_HOME\bin as follows:

First make sure your environment is setup properly for OIM home. (ORACLE_HOME param.)
$ORACLE_HOME/bin/resetiASpasswd.sh cn=orcladmin your_new_pass $ORACLE_HOME

To reset OID password use oidpasswd utility as Robbert pointed out.

Oracle patchset 10.2.0.4

gato — Wed, 02 Apr 2008 21:05:58 +0000

Oracle patchset 10.2.0.4 is now available via metalink for Windows(32bit) and Linux x86(32bit) platforms.

Update 22.05.2008: Now available also for some 64 bit platforms like AIX5L 64.

ALTER SYSTEM SET GO_FASTER

olegar — Fri, 21 Dec 2007 00:40:07 +0000

ALTER SYSTEM SET GO_FASTER=TRUE;

PLS-00630 unsupported collection return types / 10G upgrade

gato — Fri, 21 Dec 2007 00:29:53 +0000

If you’ve just upgraded from 9i to 10g, and you are using unsupported collection return types in pipelined functions you are no longer able to compile the code due to a more restrictive 10g compiler. Your pipelined functions compiled just fine on 9i. You are unable to compile the functions with the following error message PLS-00630: pipelined functions must have a supported collection return type. If rewriting huge amounts of code is not an option for you, this event will allow you to compile the code:

ALTER session SET events= '10946 trace name context level 4';

Oracle 11g now available for Windows and 64bit Linux

gato — Wed, 24 Oct 2007 22:01:05 +0000

Microsoft Windows (1.7 GB)
Linux x86 (1.7 GB)
Linux x86-64 (1.8 GB)

Oracle 11g RAC na Oracle Enterprise Linux 4(Update 5) a VMware Server 1.0.3

olegar — Tue, 02 Oct 2007 13:44:22 +0000

I’ve recently came across excelent article/how-to for Oracle 11g RAC na Oracle Enterprise Linux 4(Update 5) a VMware Server 1.0.3. Thank you Frikkie.

Determining Log Switch Frequency

olegar — Tue, 17 Jul 2007 14:36:51 +0000

Too much log switching is no good for database, you should see numbers not bigger than 6 per hour. Increasing the size of redo log groups is one way to lower log switch frequency, please refer to Oracle documentation on how to lower log switch frequency.

You can use the following query to determine your log switch frequency past 7 days (by hour):

SELECT * FROM (
SELECT * FROM (
SELECT   TO_CHAR(FIRST_TIME, 'DD/MM') AS "DAY"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '00', 1, 0)), '99') "00:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '01', 1, 0)), '99') "01:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '02', 1, 0)), '99') "02:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '03', 1, 0)), '99') "03:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '04', 1, 0)), '99') "04:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '05', 1, 0)), '99') "05:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '06', 1, 0)), '99') "06:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '07', 1, 0)), '99') "07:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '08', 1, 0)), '99') "08:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '09', 1, 0)), '99') "09:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '10', 1, 0)), '99') "10:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '11', 1, 0)), '99') "11:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '12', 1, 0)), '99') "12:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '13', 1, 0)), '99') "13:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '14', 1, 0)), '99') "14:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '15', 1, 0)), '99') "15:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '16', 1, 0)), '99') "16:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '17', 1, 0)), '99') "17:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '18', 1, 0)), '99') "18:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '19', 1, 0)), '99') "19:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '20', 1, 0)), '99') "20:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '21', 1, 0)), '99') "21:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '22', 1, 0)), '99') "22:00"
       , TO_NUMBER(SUM(DECODE(TO_CHAR(FIRST_TIME, 'HH24'), '23', 1, 0)), '99') "23:00"
    FROM V$LOG_HISTORY
    WHERE extract(year FROM FIRST_TIME) = extract(year FROM sysdate)
GROUP BY TO_CHAR(FIRST_TIME, 'DD/MM')
) ORDER BY TO_DATE(extract(year FROM sysdate) || DAY, 'YYYY DD/MM') DESC
) WHERE ROWNUM < 8
/

How to determine users idle time

olegar — Tue, 17 Jul 2007 14:23:28 +0000

You can determine users idle time using the following query:

SELECT SID, SERIAL#, USERNAME,
(CASE   WHEN EXTRACT (DAY FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) > 0
        THEN
        EXTRACT (DAY FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) || 'd '
        ELSE NULL
 END || CASE
        WHEN EXTRACT (HOUR FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) > 0
        THEN
        EXTRACT (HOUR FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) || 'h '
        ELSE NULL
  END  || CASE
        WHEN EXTRACT (MINUTE FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) > 0
        THEN
        EXTRACT (MINUTE FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) || 'm '
        ELSE NULL
  END  || CASE
        WHEN EXTRACT (SECOND FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) > 0
        THEN
        EXTRACT (SECOND FROM (NUMTODSINTERVAL (SYSDATE - (SYSDATE - LAST_CALL_ET), 'SECOND'))) || 's '
        ELSE NULL
  END) AS  "IDLE_TIME"
FROM V$SESSION
WHERE USERNAME IS NOT NULL
ORDER BY LAST_CALL_ET DESC
/

Oracle Application Server on Linux with Eastern European Characters How To

olegar — Tue, 17 Jul 2007 12:36:08 +0000

Our Linux OAS should be started using the same NLS_LANG as client is using, in our case NLS_LANG=SLOVAK_SLOVAKIA.EE8MSWIN1250

export NLS_LANG=SLOVAK_SLOVAKIA.EE8MSWIN1250

cd $ORACLE_HOME/opmn/bin

# restart OAS
./opmnctl stopall
opmnctl: stopping opmn and all managed processes...

./opmnctl startall
opmnctl: starting opmn and all managed processes...

Assuming that there are eastern european characters used in your FMB files in labels, etc..
You need to recompile all the PLL(libraries), MMB(menus), FMB(forms) files using the following:

# this is required
export ORACLE_TERM=vt220

# For PLL files we need to use
# NLS_LANG=AMERICAN_SLOVAKIA.EE8MSWIN1250
# otherwise you get nasty compile messages.

export NLS_LANG=AMERICAN_SLOVAKIA.EE8MSWIN1250

for x in *.pll
do
$ORACLE_HOME/bin/frmcmp_batch.sh module=$x \
userid=user/pass@TNS_NAME batch=yes module_type=library
done

# For MMB and FMB files we need to
# use NLS_LANG=SLOVAK_SLOVAKIA.EE8MSWIN1250

export NLS_LANG=SLOVAK_SLOVAKIA.EE8MSWIN1250

for x in *.mmb
do
$ORACLE_HOME/bin/frmcmp_batch.sh module=$x \
userid=user/pass@TNS_NAME batch=yes module_type=menu
done

for x in *.fmb
do
$ORACLE_HOME/bin/frmcmp_batch.sh module=$x \
userid=user/pass@TNS_NAME batch=yes module_type=form
done

Note: Using this example above, you DON’T need to set DISPLAY variable.