DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: LOG MINER

  1. #11
    Join Date
    Jul 2000
    Posts
    521
    Its kind of a BUG !!

    What you need to do is, edit the dbmslmd.sql script and change the variable declaration of 'col_desc_array' from varray(513) to varray(700). And then, execute this script to recreate the package.

    More explanation on Metalink...
    svk

  2. #12
    Join Date
    Nov 2000
    Posts
    157
    Hi Jeff & SVK

    Thanks alot for your help and time friends. As you guys adviced i changed col_desc_array from 513 to 700 and the dictionary file was created successfully.

    I am going to further explore into the log miner and will contact you for the same if i end up with any new problems.

    Thanks much once again
    Ravi
    ravi

  3. #13
    Join Date
    Nov 2000
    Posts
    157
    Hi

    I am trying to declare the log files to be monitored by DBMS_LOGMNR. I am getting an error message like:

    SQL> begin
    2 DBMS_LOGMNR.ADD_LOGFILE(
    3 logfilename => 'C:\programfiles\Ora81\oradata\test\archive\[TEST]1_496.ARC',
    4 options => dbms_logmnr.NEW);
    5 END;
    6 /
    options => dbms_logmnr.NEW);
    *
    ERROR at line 4:
    ORA-06550: line 4, column 24:
    PLS-00302: component 'NEW' must be declared
    ORA-06550: line 2, column 1:
    PL/SQL: Statement ignored


    SQL> begin
    2 DBMS_LOGMNR.ADD_LOGFILE(
    3 logfilename => 'C:\programfiles\Ora81\oradata\test\archive\[TEST]1_496.ARC',
    4 options => dbms_logmnr.ADDFILE);
    5 END;
    6 /
    options => dbms_logmnr.ADDFILE);
    *
    ERROR at line 4:
    ORA-06550: line 4, column 24:
    PLS-00302: component 'ADDFILE' must be declared
    ORA-06550: line 2, column 1:
    PL/SQL: Statement ignored

    Can you correct me please!!

    Thanks
    Ravi
    ravi

  4. #14
    Join Date
    Nov 2000
    Posts
    157
    ORA-06550: line num, column num: str
    Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.

    Action: Refer to the following PL/SQL messages for more information about the error.

    ravi

  5. #15
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,447
    can you stop repeating your post?

  6. #16
    Join Date
    Nov 2000
    Posts
    157
    Hey Pando

    Its a mistake. Sorry for the Inconvenience.
    ravi

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width