" /> I cannot access my Brio reports - Genesys CTI User Forum

Author Topic: I cannot access my Brio reports  (Read 4327 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Koki

  • Guest
I cannot access my Brio reports
« on: October 25, 2006, 11:50:20 AM »
Advertisement
Dear Genesys professionals,



I cannot access my Brio reports. It was working just few hours ago and now it is not. I have tried in vain to check if my Oracle connectionis good by doing: sqlplus genesys/genesys@GENESYS_DM but Oracle tells me: ORA-00257 - can only login internally.

What can this be? Please help me in resolving this great mystery.



[hr]
Koki ::)

Offline Alexander

  • Newbie
  • *
  • Posts: 15
  • Karma: 0
Re: I cannot access my Brio reports
« Reply #1 on: October 25, 2006, 12:23:01 PM »
Did you check http://ora-00257.ora-code.com/ ?

ORA-00257: archiver error. Connect internal only, until freed.
Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.
Action: Check archiver trace file for a detailed description of the problem. Also verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

Maybe your Hard Drive is full?

Offline Haldane

  • Jr. Member
  • **
  • Posts: 72
  • Karma: 1
Re: I cannot access my Brio reports
« Reply #2 on: October 25, 2006, 12:24:38 PM »
Koki,
  This is purely a DB issue. You may have run out of space or need to clear down some archive logs. Just contact your DBA and they will sort it out quickly for you.

Regards

Marked as best answer by on Today at 11:17:46 PM

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
Re: I cannot access my Brio reports
« Reply #3 on: October 26, 2006, 04:14:29 AM »
  • Undo Best Answer
  • Koki,

    ok, here is the thing - 99.999 % it is your hard drive is full,
    and it will be full until you do something about it.

    There are several things that you should do, but the first thing is probably making sure that Oracle is responsive.
    So, here are some fo the assumptions that I make:

    - your disk is full because of archive logs.
    - you do not have enough space to move data somewhere else
    - you do not care about archive logs
    - your number priority is to make sure that CCA is working
    - your ODS is on a different Oracle (as Genesys strongly suggests)
    - you do not have time to make a backup
    - you ar eusing UNIX (as any normal person would ;) )


    Since ODS is on a  different Oracle, all your reporting data is not lost and is safely stored in ODS, so we are fine.

    1. Let's check disk space first: df -k  -- does it say Capacity 100% somewhere?
    2. Let's check where your archive logs are:

            sqlplus sys/... as sysdba  (make sure you are doing it from the machine where ORACLE is running!)
          select destination from v$archive_dest;
         
    is the directory where archive logs are the same as where capacity is 100%? If so, proceed, if not, STOP and tell us.

    (ONLY IF ARCHIVE LOGS FILLED YOUR SPACE)
    3. we want to make sure that ORacle is up and running again, so what we want to do is turn Archiving off
        alter system archive log stop;

    4. let's delete archive files!
      cd to directory shown in step#2
      rm * (<-- careful - make sure that only archive files are there. Usually it is in "archive" folder. If it is under archive folder, chance are you are fine, so don't sweat. If you are not, STOP and reply to us

    5. deleting will be instanteneous but df -k will not show it for a few minutes, because probably we are talking about gigs of files, so just wait.
    6. let's see if you can enter oracle: sqlplus yourlogin/yourpassword@yourinstance (sqlplus genesys/genesys@GENESYS_DM judging by your post)
    7. you should then check if your ETL-trans logs : on its next run it should move the data just fine.

    Tell us how it went!






    PK

    • Guest
    Re: I cannot access my Brio reports
    « Reply #4 on: December 05, 2006, 12:27:46 PM »
    Koki - did it work for you? If so, what was it?

    PK