OracleLog » Administration

ORA-01436: CONNECT BY loop in user data

gato — Wed, 07 Apr 2010 19:45:17 +0000

If you are trying to debug error ORA-01436: CONNECT BY loop in user data in

the CONNECT BY sql statements, the following might help you:

ALTER SESSION
   SET "_dump_connect_by_loop_data"=TRUE;

-- execute the CONNECT BY here

Now look in the UDUMP destination for the trace file,
it will contain the problematic IDs which are causing the
infinite loop in the hierarchy.

-OR-

Simply if you want to ignore it, use ‘nocycle’ keyword:

select
   ...
from
  ...
start with
  somecol = 12345
connect by nocycle
  prior nodeto_col = nodefrom_col;

Oracle Database 11g Release 2 (11.2.0.1.0) for Linux x86, Linux x86-64

gato — Wed, 02 Sep 2009 17:56:04 +0000

Oracle releases Oracle Database 11g Release 2 (11.2.0.1.0) for Linux x86 and Linux x86-64 platforms.

ORA-39125, ORA-01801: date format is too long for internal buffer

gato — Mon, 20 Jul 2009 18:12:04 +0000

If your are getting:

ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TAB
LE:"UNIUS"."SBA_E_SYSTEM_H"]
ORA-01801: date format is too long for internal buffer

during expdp or dbms_metadata exports, it’s because there are stored incorrect date values in the dictionary.

The following plsql should _not_ report any tables, if yes you may need to correct the values, see below.


declare
   n number;
begin
   for x in(
      select * from dba_tab_columns
         where column_name = 'ANALYZETIME'
            and owner='SYS'
            and table_name like '%$'
   )
   loop
      N := 0;
      EXECUTE IMMEDIATE 'SELECT COUNT(1) FROM '
         || X.TABLE_NAME || '
         WHERE to_char(analyzetime,''DD-MON-YY'') = ''00-000-00'''
         INTO N;

      IF N > 0 THEN
         dbms_output.put_line('Problem: ' || X.TABLE_NAME);
      END IF;

   end loop;
end;
/

Problem: TABSUBPART$

To fix the table TABSUBPART$ run the following update: (!!! FIRST CONSULT ORACLE SUPPORT !!!)

-- !!! Be sure that you have a valid bakup. !!!
connect / as sysdba
SQL>shutdown immediate
SQL>startup restrict
SQL>update tabsubpart$ set analyzetime = sysdate where to_char(analyzetime,'DD-MON-YY') = '00-000-00';
SQL>commit;
SQL>shutdown immediate
SQL>startup

Please use this at your own risk, you should always consult Oracle support before doing anything to your database.

Compiling objects with utlrp.sql

gato — Fri, 16 Jan 2009 16:08:43 +0000

From my previous expriences with script utlrp.sql provided by Oracle, for mass-compilation of invalid objects, I recommend running this script only in STARTUP UPGRADE / MIGRATE mode. Otherwise you may end up with dictionary and or schema incosistencies especially if you use alot of schema objects (45 000+) .

$ORACLE_HOME/rdbms/admin/utlrp.sql

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.

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)

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
/