Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Help with Error 1

Status
Not open for further replies.

ptheriault

IS-IT--Management
Aug 28, 2006
2,699
US
I am new to Oracle. I have found this error on our reports server. I tried to google it but I didn't get any hits.
Can anyone tell me what this means.
Thanks


Metric Generic Alert Log Error
Time/Line Number Fri Sep 15 03:06:46 2006/221780
Severity [Warning]
Warning
Timestamp Sep 15, 2006 3:13:32 AM
Username <SYSTEM>
Message ORA-error stack (12012, 04063, 06508, 06512) logged in D:\ORACLE\PRODUCT\10.2.0\ADMIN\RSPROD\BDUMP\alert_rsprod.log.
 
Code:
+ oerr ora 12012
12012, 00000, "error on auto execute of job %s"
// *Cause:  An error was caught while doing an automatic execution of a job.
// *Action: Look at the accompanying errors for details on why the execute
//          failed.
+ oerr ora 04063
04063, 00000, "%s has errors"
// *Cause:  Attempt to execute a stored procedure or use a view that has
//          errors.  For stored procedures, the problem could be syntax errors
//          or references to other, non-existent procedures.  For views,
//          the problem could be a reference in the view's defining query to
//          a non-existent table.
//          Can also be a table which has references to non-existent or
//          inaccessible types.
// *Action: Fix the errors and/or create referenced objects as necessary.
+ oerr ora 06508
06508, 00000, "PL/SQL: could not find program unit being called"
// *Cause:
// *Action:
+ oerr ora 06512
06512, 00000, "at %sline %s"
// *Cause:   Backtrace message as the stack is unwound by unhandled
//           exceptions.
// *Action:  Fix the problem causing the exception or write an exception
//           handler for this condition. Or you may need to contact your
//           application administrator or DBA.
 
Thanks...I took a look at the alert.log file and found a few other things.
I've got a lot to learn here... But I'm slowly making progress.
Thanks for your help.

In the init.ora the db_recovery_file_dest_size is set to 2 GB. I have plenty of disk space so I was thinking of increasing that file size to 10GB. Do you think that would be a good idea?


Errors in file d:\oracle\product\10.2.0\admin\rsprod\bdump\rsprod_mmon_4376.trc:
ORA-19815: WARNING: db_recovery_file_dest_size of 2147483648 bytes is 100.00% used, and has 0 remaining bytes available.

Tue Sep 26 08:33:48 2006
************************************************************************
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************
 
I don't think the error you were getting has anything to do with that. The errors imply a problem with a stored procedure which your application is calling. Try to find out what procedures the application is calling. Also, query dba_objects to see if anything has a status which is not 'VALID'.
 
Dagon,
thanks..
I found the view that is being called. The status is INVALID. Does that mean I sould recreate the view? What would make the status invalid?
 
Maybe an upgrade? You could try recompiling it perhaps.

I don't mind people who aren't what they seem. I just wish they'd make their mind up.

Alan Bennett.
 
The status would be invalid if it gives an error on compilation. Either re-run the script to create the view and see if it gives an error or recompile the existing view using "alter view xxxx compile".

If you get an error, you can create the sys.dba_errors table to find it.

select * from sys.dba_errors where name = <view name>
 
That should say "read the sys.dba_errors table". The table already exists.
 
Thanks again...
I spend 99.9% of my time with MS SQL so when I have to dive into our Oracle system I need to enlist a lot of help. We had a vendor upgrade our Oracle to 10G too. so maybe that is what caused the error with the view.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top