Alert log internal error exeception caught in pfrrun() while running pl/sql

Hi ,
For the past two days these error messages appears in the alert log.
ACTION NAME(PAGE 1)
MODULE NAME:(APPLICATION xxx)
*** got internal error exception caught in pfrrun() while running pl/sql***
*** Got ora-3113 while running plsql***
Function FLOWS_030000.V (or) PACKAGE BODY FLOWS_030000.WWV_FLOW:
can anyone assist me on this.
Thanks

user589320,
As Scott mentioned, have a look at
http://www.inside-oracle-apex.com/2008/03/attention-are-you-using-drop-in.html
That might solve your problem.
Patrick
*** New *** Oracle APEX Essentials *** http://essentials.oracleapex.info/
My Blog, APEX Builder Plugin, ApexLib Framework: http://www.oracleapex.info/

Similar Messages

Got internal error Exception caught in pfrrun() while running PLSQL in apex

Hi,
The apex 3.1 is running on the windows 2003 box with 10.2.0.3 database.For almost 3 weeks,there are error messages on the alert log that
ORA-00603: ORACLE server session terminated by fatal error
ORA-03135: connection lost contact
When the trace file is observed,the following messages is displayed
*** 2008-07-29 07:25:42.715
*** ACTION NAME:(PAGE 26) 2008-07-29 07:25:42.684
*** MODULE NAME:(APEX:XXX) 2008-07-29 07:25:42.684
*** SERVICE NAME:(test) 2008-07-29 07:25:42.684
*** CLIENT ID:() 2008-07-29 07:25:42.684
*** SESSION ID:() 2008-07-29 07:25:42.684
*********START PLSQL RUNTIME DUMP************
***Got internal error Exception caught in pfrrun() while running PLSQL***
***Got ORA-3113 while running PLSQL***
PACKAGE BODY FLOWS_030100.WWV_RENDER_REPORT3:
Did somebody encountered this error?What is the problem here?please advice on this.

This was upgraded to 3.1 from a month back and there
are no messages on the development box where the
envirnoment is the sameI'm not sure (at the moment I have not instance with APEX here) but FLOWS_030000 should be APEX 3.0 package...
So to say it's a corpse of previous APEX installation...
But there is an Oracle Application Express (APEX) where you can ask further questions about APEX structure.
Message was edited by:
Faust
Edit:
alert log internal error exeception caught in pfrrun() while running pl/sql

ORA-600 [17069] error while running catrelod.sql to downgrade 11g database

Hi,
We are downgrading our 11.2.0.2 database to 10.2.0.4. We have successfullly run catdwgrd.sql without any errors in 11g env. While running catrelod.sql in 10g env we are facing the following error:
SQL> @?/rdbms/admin/catrelod.sql
TIMESTAMP
COMP_TIMESTAMP RELOD__BGN 2013-04-24 20:15:39 2456407 72939
DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database server version is not 10.0.0.
DOC> Shutdown ABORT and use a different script or a different server.
DOC>#######################################################################
DOC>#######################################################################
DOC>#
no rows selected
DOC>#######################################################################
DOC>#######################################################################
DOC> The following statement will cause an "ORA-01722: invalid number"
DOC> error if the database has not been opened for MIGRATE.
DOC>
DOC> Perform a "SHUTDOWN ABORT" and
DOC> restart using MIGRATE.
DOC>#######################################################################
DOC>#######################################################################
DOC>#
no rows selected
Session altered.
Session altered.
no rows selected
DECLARE
ERROR at line 1:
ORA-00600: internal error code, arguments: [17069], [0x170FB8CA8], [], [], [],
[], [], []I have checked the trace file in udump but it dint give any readable information.
Please find below environment details.
OS : RHEL 5 64 bit
11g Database : 11.2.0.2
10g Database : 10.2.0.4
Kindly assist.

KR10822864 wrote:
Whenever an ORA-600 error is raised a trace file is generated and an entry written to the alert.log with details of the trace file location. Starting with Oracle Database 11g Release 1, the diagnosability infrastructure was introduced which places the trace and core files into a location controlled by the DIAGNOSTIC_DEST initialization parameter when an incident, such as an ORA-600 is created. For earlier versions, the trace file will be written to either USER_DUMP_DEST (if the error was caught in a user process) or BACKGROUND_DUMP_DEST (if the error was caught in a background process like PMON or SMON). The trace file contains vital information about what led to the error condition
please post 40 lines of alert log info .
MOS Note:ORA-600 [17069] "Failed to pin a library cache object after 50 attempts" [ID 39616.1]
"Look in the trace file for the text 'LIBRARY OBJECT HANDLE: handle=170fb8ca8'"
if not found any massages like above please raise [email protected].
Hi KR,
Thanks for your help. As suggested I have checked the trace file to search and found the below info. I suppose it is some kind of lock but not sure about it. Please let me know if the following makes sense:
    SO: 0x21158a6e0, type: 3, owner: 0x211006f28, flag: INIT/-/-/0x00
    (call) sess: cur 211572570, rec 211572570, usr 211572570; depth: 0
      SO: 0x21158a9b8, type: 3, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      (call) sess: cur 211572570, rec 0, usr 211572570; depth: 1
        SO: 0x1727a2618, type: 54, owner: 0x21158a9b8, flag: INIT/-/-/0x00
        LIBRARY OBJECT PIN: pin=1727a2618 handle=170fb8ca8 mode=S lock=171243e98
        user=211572570 session=211572570 count=1 mask=001d savepoint=0x43 flags=[00]
        SO: 0x171243e98, type: 53, owner: 0x21158a9b8, flag: INIT/-/-/0x00
        LIBRARY OBJECT LOCK: lock=171243e98 handle=170fb8ca8 mode=S
        call pin=0x1727a2618 session pin=(nil) hpc=0000 hlc=0000
        htl=0x171243f18[0x17278a310,0x17278a310] htb=0x17278a310 ssga=0x172789928
        user=211572570 session=211572570 count=1 flags=PNC/[0400] savepoint=0x43
        LIBRARY OBJECT HANDLE: handle=170fb8ca8 mtx=0x170fb8dd8(0) cdp=0
        name=SYS.STANDARD
        hash=51570e225ed8a9a803b7318f191e0a8d timestamp=04-18-2006 00:00:00
        namespace=TABL flags=KGHP/TIM/SML/[02000000]
        kkkk-dddd-llll=0000-001d-001d lock=S pin=S latch#=3 hpc=0004 hlc=0004
        lwt=0x170fb8d50[0x170fb8d50,0x170fb8d50] ltm=0x170fb8d60[0x170fb8d60,0x170fb8d60]
        pwt=0x170fb8d18[0x170fb8d18,0x170fb8d18] ptm=0x170fb8d28[0x170fb8d28,0x170fb8d28]
        ref=0x170fb8d80[0x170fb8d80,0x170fb8d80] lnd=0x170fb8d98[0x170f05b50,0x170fa6858]
          LIBRARY OBJECT: object=170e82de8
          type=PCKG flags=EXS/LOC[0005] pflags=NST/IVR[0201] status=VALD load=0
          DATA BLOCKS:
          data#     heap pointer    status pins change whr
              0 170e831f8 170e82fc0 I/P/A/-/-    0 NONE   00
      SO: 0x21158e470, type: 5, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      (enqueue) CU-70E88BC0-00000001    DID: 0001-001F-00000004
      lv: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 res_flag: 0x2
      res: 0x17677adc8, mode: X, lock_flag: 0x0
      own: 0x211572570, sess: 0x211572570, proc: 0x211006f28, prv: 0x17677add8
      SO: 0x177f82c28, type: 59, owner: 0x21158a6e0, flag: INIT/-/-/0x00
      cursor enqueue
      child: 170e89348, flag: 53, number: 0
      parent: 170e89738

Error while running catmetx.sql

Have anybody received an error while running CATMETX.SQL in attempt to fix a known problem in 10gR2 - inconsistent datatype: expected BLOB, CLOB got CHAR?
Any and all ideas appreciated.
Greg
Here is what I've got:
SQL> @catmetx
Package altered.
Index altered.
create or replace force view sys.ku$_xmlschema_view of sys.ku$_xmlschema_t
ERROR at line 1:
ORA-22973: size of object identifier exceeds maximum size allowed
Grant succeeded.
View created.
etc.

Before I'm willing to hazard a guess as to what is wrong some more information is required.
1. What version are you on exactly (to 3 or 4 decimal places)
2. What problem led you to decide to run catmex.sql?
3. What metalink doc did you read that indicated you should?
4. What are the results of the following queries?
SELECT comp_name, version, status
FROM dba_registry;
SELECT owner, object_name, object_type
FROM dba_objects
WHERE status = 'INVALID';The alternative is an SR at metalink.

Oracle Apps Forms errors out with FRM-40735 while running from Oracle D2K

Hi
Will anybody please provide me a solution on Oracle Apps Forms which errors out with FRM-40735 while running from Oracle D2K
Regards
Nakul Venkataraman

Hello,
certain trigger in your form is throwing an exception and its not being catched by the exception part for your block. check the code of your trigger and pur exception handling into your trigger code

An error occurred while running adsetmmd.sql

I'm trying to disable the maintenance and getting this error
An error occurred while running adsetmmd.sql.
Continue as if it were successful [No] : No
Could not disable Maintenance Mode.
Can anybody let me know what could be wrong!!!
Regards
-Mahesh

Hussein,
Please apply 11i.ATG_PF.H.RUP5 without enabling maintenance mode (use adpatch options=hotpatch). I've started with this. I started the adpatch session with two workers. Initially it went on very well but after sometime, it got struct up at
APPL_TOP is set to /d01/oracle/visappl
FAILED: file jtfpfrepgrants.sql on worker 2 for product jtf username JTF.
ATTENTION: All workers either have failed or are waiting;
FAILED: file jtfpfrepgrants.sql on worker 2.
ATTENTION: Please fix above failed worker(s) so the manager can continue.
Worker status on the instance
Control
worker Code Context Filename Status
1 Run AutoPatch 115 Wait
2 Run AutoPatch 115 tfpfrepgrants.sql FAILED
Then to fix this issue I tried
- Kill the adworker process from the OS "use ps -ef | grep -i adworker"
- Use adctrl to "Tell Manager that worker has failed its job"
- Use adctrl to "Tell worker to restart failed job"
But I don't know what next? whether I've to restart the adpatch? If so, how to do it?
-Mahesh

The database alert log has errors. Please help me

Hi all
I have an Oracle 8i Database that seams to be functioning well but when I
Checked the Database alert Log I realized that something is not fine
Part of the alert log content is here under. What can be problem and how can I
Resolve it. Please I need you assistance...
Thu Feb 07 08:50:37 2008
Thread 1 advanced to log sequence 266
Thu Feb 07 08:50:37 2008
Current log# 11 seq# 266 mem# 0: E:\ORACLE\ORADATA\MUKREC\LOGS\REDO11.LOG
Thu Feb 07 08:50:38 2008
ARC0: Beginning to archive log# 10 seq# 265
Thu Feb 07 08:51:07 2008
ARC0: Completed archiving log# 10 seq# 265
Thu Feb 07 09:23:22 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA03976.TRC:
Thu Feb 07 09:23:23 2008
Errors in file E:\Oracle\admin\MUKREC\udump\ORA04092.TRC:
................................................................................................................

I'll just throw a shameless copy-paste from Metalink note : 164839.1 , hope you can use it to get further ? :
Subject: FATAL ERROR IN TWO-TASK SERVER: error = 12571 Found in Alert File
Doc ID: Note:164839.1 Type: PROBLEM
Last Revision Date: 17-DEC-2007 Status: PUBLISHED
fact: Oracle Server - Enterprise Edition
symptom: Errors appear in alert file
symptom: FATAL ERROR IN TWO-TASK SERVER:
symptom: ERROR = 12571
symptom: trace file generated
symptom: Database operations continue successfully
cause: The most common cause for the above error is an ungraceful
disconnection of a session from the oracle db while the db is currently running
a dml statement issued by that session. The error is recorded when oracle
attempts to reply back to the session with the results of the dml and cannot
access the session. Overall database operations are usually not affected.
An ungraceful disconnection could cause by but is not limited to any of the
following:
- the client machine crashed
- the network connection crashed
- the user exited the session improperly (not issuing the 'exit' command)
- the user application allows the user to exit the application without properly
terminating the session.
The above can cause problems with corrupted rollback segments if occurring on a
regular basis and is not addressed. This would require db recovery and
possibly a db rebuild (not a light matter)
PMON will usually rollback most transactions in the rollback segments for a
session if it finds that the session has been ungracefully disconnected, but
there is always a chance that it cannot and this will lead to rollback segment
corruption.
fix:
The dml and the user that issued the dml can be determined from the trace file.
The current dml is in the tracefile header section. The user can be found in
the process state dump of the trace. The process state shows the machine,
o/suser, and user for the session.
The DBA can use this information to determine what the user was doing at the
time and if there was an ungraceful exit from the session the user was
utilizing.
The DBA should then address the cause of the ungraceful exit to reduce the
possibility of recurrence.

Most Recent Alert Log Entries - Error processing Alert Log

Hi..
Can someone help me?
When I want to check the log of alerts the following thing goes out for me:
"This shows the last 100,000 bytes of the alert log. The log is constantly growing, so select the browser's Refresh button to see the most recent log entries.
Number of Lines Displayed Error processing Alert Log"
Since I can solve it?

Number of Lines Displayed Error processing Alert Log"
check ur alert.log file content any data.
bcoz if ur alert.log file entries is null then above error is show. ( happen with me when i am purge alert.log file and try to view content of alert.log then above error received so may be problem is null contents ( empty alert.log file)).
HTH

12c Cloud Control Alert Log Purge Error

I'm trying to purge old alert log events in EM 12c, but i'm getting error - The alert(s) could not be purged. Please ensure you have Edit privileges on this target while purging.
What's i'm doing wrong? Cant find anything close to this in EM documentation.
Thank you.

Hi,
What privileges do you have on the target? You'll need at least Manage Target Events (a subprivilege of Operator) in order to clear events on the target.
regards,
Ana

Msg 8631 Internal error: Server stack limit has been reached on SQL Server 2012 from T-SQL script that runs on SQL Server 2008 R2

I have an Script mostly that is generated by SSMS which works with-out issue on SQL Server 2008, but when I attempt to run it on a new fresh install of SQL Server 2012 I get an Msg 8631. Internal error: Server stack limit has been reached. Please look for
potentially deep nesting in your query, and try to simplify it.
The script itself doesn't seem to be all that deep or nested. The script is large 2600 lines and when I remove the bulk of the 2600 lines, it does run on SQL Server 2012. I'm just really baffled why something that SQL Server generated with very
few additions/changes AND that WORKS without issue in SQL Server 2008 R2 would suddenly be invalid in SQL Server 2012
I need to know why my script which is working great on our current SQL Server 2008 R2 servers suddenly fails and won't run on an new SQL Server 2012 server. This script is used to create 'bulk' Replications on a large number of DBs saving a tremendous
amount of our time doing it the manual way.
Below is an 'condensed' version of the script which fails. I have removed around 2550 lines of specific sp_addarticle statements which are mostly just copy and pasted from what SQL Management Studio 'scripted' for me went I when through the Replication
Wizard and told it to save to script.
declare @dbname varchar(MAX), @SQL nvarchar(MAX)
declare c_dblist cursor for
select name from sys.databases WHERE name like 'dbone[_]%' order by name;
open c_dblist
fetch next from c_dblist into @dbname
while @@fetch_status = 0
begin
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 2400 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script =
null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509F, @identityrangemanagementoption = N''manual'', @destination_table = N''TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false'', @ins_cmd = N''CALL sp_MSins_dboTABLE_ONE'',
@del_cmd = N''CALL sp_MSdel_dboTABLE_ONE'', @upd_cmd = N''SCALL sp_MSupd_dboTABLE_ONE''
EXEC sp_executesql @SQL
SET @dbname = REPLACE(@dbname, 'dbone_', 'dbtwo_');
print @dbname
SET @SQL = 'DECLARE @dbname NVARCHAR(MAX); SET @dbname = ''' + @dbname + ''';
use ['+@dbname+']
exec sp_replicationdboption @dbname = N'''+@dbname+''', @optname = N''publish'', @value = N''true''
use ['+@dbname+']
exec ['+@dbname+'].sys.sp_addlogreader_agent @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1, @job_name = null
-- Adding the transactional publication
use ['+@dbname+']
exec sp_addpublication @publication = N'''+@dbname+' Replication'', @description = N''Transactional publication of database
'''''+@dbname+''''' from Publisher ''''MSSQLSRV\INSTANCE''''.'', @sync_method = N''concurrent'', @retention = 0, @allow_push = N''true'', @allow_pull = N''true'', @allow_anonymous = N''false'', @enabled_for_internet
= N''false'', @snapshot_in_defaultfolder = N''true'', @compress_snapshot = N''false'', @ftp_port = 21, @allow_subscription_copy = N''false'', @add_to_active_directory = N''false'', @repl_freq = N''continuous'', @status = N''active'', @independent_agent = N''true'',
@immediate_sync = N''true'', @allow_sync_tran = N''false'', @allow_queued_tran = N''false'', @allow_dts = N''false'', @replicate_ddl = 1, @allow_initialize_from_backup = N''true'', @enabled_for_p2p = N''false'', @enabled_for_het_sub = N''false''
exec sp_addpublication_snapshot @publication = N'''+@dbname+' Replication'', @frequency_type = 1, @frequency_interval = 1, @frequency_relative_interval = 1, @frequency_recurrence_factor = 0, @frequency_subday = 8,
@frequency_subday_interval = 1, @active_start_time_of_day = 0, @active_end_time_of_day = 235959, @active_start_date = 0, @active_end_date = 0, @job_login = N''DOMAIN\DBServiceAccount'', @job_password = N''secret'', @publisher_security_mode = 1
-- There are around 140 lines roughly the same as this only difference is the tablename repeated below this one
use ['+@dbname+']
exec sp_addarticle @publication = N'''+@dbname+' Replication'', @article = N''DB_TWO_TABLE_ONE'', @source_owner = N''dbo'', @source_object = N''DB_TWO_TABLE_ONE'', @type = N''logbased'', @description = null, @creation_script
= null, @pre_creation_cmd = N''drop'', @schema_option = 0x000000000803509D, @identityrangemanagementoption = N''manual'', @destination_table = N''DB_TWO_TABLE_ONE'', @destination_owner = N''dbo'', @vertical_partition = N''false''
EXEC sp_executesql @SQL
fetch next from c_dblist into @dbname
end
close c_dblist
deallocate c_dblist
George P Botuwell, Programmer

Hi George,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
If you have any feedback on our support, please click
here.
Allen Li
TechNet Community Support

Error "Internal error occurred checking the external " while creating a job

Hi All,
        I am getting an error while trying to schedule a job, Im not very shure abt what the job does, the user tried it and she got an error and asked me to do it.
        A similer kind of job has been created in an other system and it works fine there. This job should run monthly and belowis the job step
        The job runs on an external command and following are the paramerters
         Name           SAA_TP_CHECK
         Parameters     /usr/sap/transTCluster/bin/TP_DOMAIN_TD1.PFL
         Operating sys. UNIX
         Target server saptp1
        This gives an error "Internal error occurred checking the external "
A similer kind of job that runs in a different system has the parameters as follows
        Name           SAA_TP_CHECK
        Parameters     /usr/sap/trans/bin/TP_DOMAIN_YD4.PFL
        Operating sys. UNIX
        Target server sapyp4
What might be causing the error, and how can this be solved. Please help!!!!

Hi,
I think the issue is with the server .
Please check whether the Server name you are giving has the all the RFC connections.
I mean Remote Connection with the Server is establised or not.
Regards
Arbind

Receive "Fatal Internal Error: Linker.cpp, line 1926 when run executable.

Hi, I use invoke node to call multiple subvi.vit, it work fine under .vi but when run under an executable I receive this error:
Fatal Internal Error: 'linker.cpp", line 1926
LabVIEW Version 7.0 You will lose any unsaved work. For more assistance in resolving this problem, please relaunch LabVIEW, or contact National Instruments.
Any suggestion will be very appreciated

Hi David,
What you are seeing is a known issue when calling LabVIEW 7.0 VITs from
an executable or DLL if the VITs include any Express VIs. It can happen if you
try to load
multiple instances of that template VI using VI Server.
There are a couple of workarounds for this issue:
Take
all the express VIs that are inside the template VI and turn them into
static subVIs. You can do this by right-clicking on the express VI and
selecting "Open Front Panel"; then save the express VI as a normal
subVI.
Build the entire application into a single executable, which will force all of the express VIs to get compiled as static subVIs.
Don't use the runtime engine at all and always run your application in development mode.
Let me know if the workarounds fix your issue, thanks.
Good luck!
- Philip Courtois, Thinkbot Solutions

Internal Error: 8004, 4867936, 4920984, 4921436 while attempting to save as XML

Hi,
I get the following error while trying to save fm files as XML.
=== Header Begin ===
Internal Error: 8004, 4867936, 4920984, 4921436
FrameMaker 8.0.0 for Intel
Build: 8.0p266
Window System: MSWindows
Operating System: Windows NT 6.1 (major.minor.build: 6.1.7600 )
Generated on: Tuesday, November 26, 2013 2:01:40 PM
To file: c:\program files\adobe\framemaker8\FrameLog_13.11.26_14.01.40.txt
=== Header End ===
-ramesh

Yes .. definitely get the latest FM8 patch, that may solve the problem.
http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows
However, if this is a structured document, you should also be sure to validate (Element > Validate) the file before saving. Also check for graphics that are referenced from a reference page, and you may want to delete any cross-refs that aren't resolved (or resolve them). FM can crash for a variety of reasons when saving to XML, anything that's slightly amiss is likely to cause a problem.
Cheers,
...scott

Error while running the sql queries in unix as cron job..

Hi,
I've configured some sql queries to run as cronjob from unix,i'm able to excute all the sql queries with out any error,after all the queries are executed,I'm getting the following error message.
ORA-00600: internal error code, arguments: [4080], [1], [131], [], [], [], [],
Could any one advise me why this error is being thrown?
How to avoid this error?
Thanks,
Anil

Are you running these queries through TopLink?
If so, the error seems to be occurring on the database, when the query is being executed.
I have never seen that error before. Performing some websearches it seems to be a general database error, potentially something to do with synchronization. Sorry I can't be of more help, perhaps the database forum can provide more insight...

Java VM: Java HotSpot(TM) Error in weblogic 8.1 while running crystal rep

I am trying to call crystal reports 9 RAS through weblogic 8.1.
I am running a jsp.
weblogic has jdk141_03.
But, I am getting error at the below line in the jsp.
ReportClientDocument clientDoc = new ReportClientDocument();
The weblogic server crashes out giving below error.
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
# Java VM: Java HotSpot(TM) Client VM (1.4.1_03-b02 mixed mode)
# Error ID: 43113F32554E54494D45110E4350500305
# Problematic Thread: prio=5 tid=0x008E12C8 nid=0x6ec runnable
Does anyone know the solution.
thanks..

i got the sam problem have you fix it yet ?
please let me know what should i do.

Alert log internal error exeception caught in pfrrun() while running pl/sql

Similar Messages

Maybe you are looking for