Compressor 4.1 distributed job - "waiting" status

In a 3 computer cluster...Why are these 3 not processing simultaneously? The other 2 computers are sitting there, with no other programs running, etc.
It just seems to me like they should all be transcoding simultaneously.
Compressor 4.1 seems really slow to do any transcoding in general. I don't know what's going on...sigh.

Same here.
Really poor performance (more than 4x slower, I guess), interrupted jobs and unstable behavior in cluster setup.
That disappoints me really deeply, as Compressor 4.0 was so bad regarding reliability in cluster environment.
Seems we have to switch to a Mac Pro as other models are outdated by update.
So Apple should give us a generous discount on the Mac Pro. But wait - we would have to wait till February anyway... No solution.

Similar Messages

Closed/Wait status for WebLogic v. 3.0.4

Hello,
Has anyone ever heard of an issue with WebLogic ver 3.0.4 having a
threshold for the number of transactions that can remain in a Closed/Wait
status, before causing the application instance to hang up? If so, please
provide any information you have.
Thank you,
Greg Kupetz

First of all, when you publish to a folder, iWeb's job is done.
Now it's your responsibilty to upload the files and folders.
Hint : feed.xml

DatabaseError: ORA-02049: timeout: distributed transaction waiting for lock

Hi all
There is script running in my database 'A' that will select some data from tables in other database through DBLINK and update some tables too. The script which 6 I am running for the past 6 monts succesfully. Yesterday I got error saying that,
DatabaseError: ORA-02049: timeout: distributed transaction waiting for lock
ORA-02063: preceding line from test
I have tested the Link and its active no issues in DBLINk
I understand the objects which I am accessing the table in locked mode,
SQL> select OBJECT_ID,SESSION_ID,PROCESS,LOCKED_MODE from v$locked_object where
SESSION_ID=121;
OBJECT_ID SESSION_ID PROCESS LOCKED_MODE
77391 121 21394 3
i
I killed the session 121 and in v$session status is Killed, but I am getting the same error repeating while running the script. And the session_id is still in locked_mode.
Could please add some light on this?
-Thanks
Antony

Hi,
I have killed the session which caused blocking and the status is KILLED for the past two days. But still the object is in locked mode
SQL> select OBJECT_ID,SESSION_ID,PROCESS,LOCKED_MODE from v$locked_object where
SESSION_ID=121;
OBJECT_ID SESSION_ID PROCESS LOCKED_MODE
77391 121 21394 3
How would I resolve this any idea
-Thanks & Cheers
Antony

ERM background jobs "waiting"

Dear all,
Any jobs I create in ERM - apart from those I schedule manually with "immediate" start - remain in status "waiting" forever and do not get processed.
This applies to periodic updates of transaction/object/activity data etc, as well as to automatically scheduled jobs with type "immediate", such as "Role Approver Update" after I have changed the workflow - approval criteria.
Deactivating/Activating the jobs doesn't help, either.
Am I missing something? Jobs in other capabilities are working fine, so surely it is not a problem with the background daemon itself?
Thanks and regards
Patrick

Thanks for the hint to the note, Sunny.
The note describes the problem, however the resolution is a bit funny. It really justs says that this is by design - surely, however, jobs hovering in "waiting" status without ever being executed cannot be "by deign"?
I not sure if I understand the note correctly.
Regards
Patrick

T code to check the job run status

Hi Gurus,
I am filling the setup tables for inventory, but i didn't run in background. I clicked on execute button, but suddenly i got disconnected from net and my server also.
Now i have to check the job run status whether it is running or not.
Request you to provide the suggessions.
Thanks & Regards,
Saketh

Hi,
if you ran job in background you can see at SM37.use proper time ,date and use id to get your job.
if you ran on frond end then you won't see job.if your job was completed then you can see data at SE11 by using setup table name or you can see at t code NPRT by using name of the run.
if you won't find your job then just delete your setup tables again and fill it.
No issues.
Thanks

How to re-start the workflow for Shopping carts in WAITING status

Hi
We are using 1-step approval work flow, and we get some strange issue. We can add approver in the workflow, but after we click order button and back to check status again, sometimes there will be "Ad-hoc agent not found" issue. Do you know how to solve?
And one workaround for user is to re-add the approval, and sometimes the shopping cart back to normal. But sometimes, after we add the approver, the shopping cart are in waiting status:
Workflow Item:
Workitem-ID 000000714642
Task WS10000276
Text One-Step Approval: Value limit: Shopping Cart
1000114698
Status WAITING
Statustext Waiting
Date 13.06.2008
Time 10:41:22
So may I ask how to re-trigger the workflow?

Hi,
Thx for that. I need to trigger the Approval workflow to go the the approval manager.
Can u give me the document on this? thx, kerry.liu [at] ap.effem.com.
Thx very much
Kerry

Work flow in waiting status

Hi,
we are using N step PO work flow for chagning the purchase orders.
when the PO is changed and ordered workflow is going into WAITING status.
It is not triggering the next steps at all.
Could any one suggest how to proceed further?
Thanks,
Naresh

Hi Daniel,
It's wokring fine for all the PO'S.
For only one specific PO we are facing this problem.
Even If I try to change the same PO again it gives an error
'Document being processed in background; try again later'
Please suggest.
Thanks,
Naresh

HT1688 I'm trying to download a audiobook I got this morning with iTunes. However, the book is frozen on "waiting" status, what is the audiobook "waiting" for?

I'm trying to download a audiobook I got this morning with iTunes. However, the book is frozen on "waiting" status, what is the audiobook "waiting" for?

Hello Jose,
I would be concerned too if the audiobook I purchased from iTunes was not downloading on my iPhone. I have a few suggestions to get it downloaded to your iPhone.
First, I recommend checking to see if the download was interrupted:
If your download was interrupted using your iPhone, iPad, or iPod touch
From the Home screen, tap the iTunes app.
For iPhone or iPod touch, tap More > Downloads. For iPad, tap Downloads.
Enter your account name and password if prompted.
Tap the blue download arrow to resume.
iTunes: How to resume interrupted iTunes Store downloads
http://support.apple.com/kb/ht1725
If the audiobook still does not download, I recommend signing out and back into the iTunes Store on your iPhone:
Changing your Apple ID account
Tap Settings > iTunes & App Stores, then tap the Apple ID signed in.
Sign out of the current Apple ID account and then sign in with another account or create a new Apple ID.
The last step states to sign in with another account, but for the situation you described, I recommend just signing in with your same Apple ID.
You can find the full article here:
iOS: Changing the signed-in iTunes Store Apple ID account
http://support.apple.com/kb/HT1311
If you are still not able to download the audiobook, you can report an issue with this purchase using the steps in this article:
How to report an issue with your iTunes Store, App Store, Mac App Store, or iBookstore purchase
http://support.apple.com/kb/ht1933
Best,
Sheila M.

BPM with waiting status in MONI

hi forum ...
in a fille to file scenario...with BPM.....
there are two receivers and 1 send step....
its like receiver1-->receiver2----->send1
when the scenario runs.......it receives a particular message for "receive2".....which i cant provide right now.......so the sxmb_moni shows a waiting status .....means a clock like signal......
how can i stop the BPM instance in waiting loop
is there any time out after which the BPM instance ll stop automatically

<<you have configured a terminating event>>
but i cant provide that condition due to some reasons......
<<SWIA to complete the workflow manually>>
how to do that...can u elaborate

There songs in the wait status and not any more on my mac

I have songs in the cloud which are still on wait status but I have them not any more on my computer.

Then they will never be available to play on your iOS status. You'll either need to find a way to restore the files, or just delete the tracks from the iTunes library.

JDBC receiver in "waiting" status

I have a scenario where Idocs pass records through XI to 10 JDBC receivers (SQL to be specific).
The records are being inserted into all 10 database tables successfully, but in Runtime Workbench, the first receiver has a successful message, but the other 9 receivers go into "Waiting" status. After 3 retries, they go into "System Error" status (but for each retry, the records are inserted again into the tables, ie: I end up with 4 of the same records in the tables).
Runtime Workbench gives me the following error:
MP: Exception caught with cause com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback.
Exception caught by adapter framework: Exception thrown in method process. The transaction is marked for rollback
The message status set to WAIT.
Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Exception thrown in method process. The transaction is marked for rollback.: com.sap.engine.services.ejb.exceptions.BaseTransactionRolledbackLocalException: Exception thrown in method process. The transaction is marked for rollback..
Can anyone help?

HI,
Did you check the Retry option set for these Adapters? if not check it in the Visual admin for the JDBC Adapter
If feasible try re-look the Design. Instead of using 10 different Adapters accessing same database, you can try with one Stored Procedure so that Database hit will be minimized and hence the queue problems.
Rgds, Moorthy

Work item is in WAITING status

Hi All,
from the past 2 months we are getting so many work items in waiting status in our system. We are able to see different work flow work items in 'WAITING' status.
What would be reason to be in waiting status.
All this work items are having message as ' Work item submitted for execution' in log but it is not reaching agents inbox for approval.
Is SAP Note 962488 will help me in this issue.
Regards,
Kusuma K.

Hi ,
There can be some event which is either inactive or incomplete, check for them in the Log and do the needul.
Hope it shd help.
DP

ORA-02049: timeout: distributed transaction waiting for lock

Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet Sahai
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

guneet sahai wrote:
Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet SahaiHi Guneet. If you want to debug the JTA issue, I suggest opening an official
support case. They will lead you through producing the JTA debug information.
However, I believe you are correct that the transaction you describe is
completely doable with a simple local transaction, so if you were to alter
your pool to use the non-XA driver, it would probably be faster, simpler,
and just work.
Let me know...
Joe
>
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

Java Proxy message in waiting status

Hi,
   Let me explain my case, In our Integration Scenario we have configured an Inbound Java Proxy as the How to guide (HOW TO WORK WITH JAVA PROXIES) expain, but the proxy doesn't hava code, that is, it have the code by default when its created, and when we register it and the scenario runs, in the message monitoring the status of the message to the JP Business Service is in WAITING status, and in the details it says sometimes that an old reference to another JNDI name of bean is doesn't locate or the message "MessageSpecifier could not be reset".
   Remember, the Imp. class has only the default code and the scenario is JDBC --> XI --> JavaProxy
   Any ideas?

Hi Hector,
Status: WAITING
          The message had been sent and it is failed and is currently waiting for another attempt.
Solution :
When the fist attempt to deliver the message has failed (a recoverable exception arose), the message is usually rescheduled and the status is updated to WAITING. As long as the message is in this status, the Messaging System retries to deliver the message according to the configured retry settings (default 3 tries).
Regards
Agasthuri Doss

Works in sql not in apex: ORA-02049 distributed transaction waiting lock

Hi,
I get this error
failed to parse SQL query:
ORA-02049: timeout: distributed transaction waiting for lockwhen trying to run this query from it's page. But it works fine if I run it in the SQL console...
failed to parse SQL query:
ORA-select distinct n.notif_no,
       n.maint_work_centre,
       n.maint_work_centre_text,
       n.raised_by,
       n.notif_text,
       (select (SAP_LONG_TEXT.NOTIFICATION_TEXT_1||SAP_LONG_TEXT.NOTIFICATION_TEXT_2||SAP_LONG_TEXT.NOTIFICATION_TEXT_3||SAP_LONG_TEXT.NOTIFICATION_TEXT_4||SAP_LONG_TEXT.NOTIFICATION_TEXT_5||SAP_LONG_TEXT.NOTIFICATION_TEXT_6||SAP_LONG_TEXT.NOTIFICATION_TEXT_7||SAP_LONG_TEXT.NOTIFICATION_TEXT_8||SAP_LONG_TEXT.NOTIFICATION_TEXT_9||SAP_LONG_TEXT.NOTIFICATION_TEXT_10||SAP_LONG_TEXT.NOTIFICATION_TEXT_11||SAP_LONG_TEXT.NOTIFICATION_TEXT_12||SAP_LONG_TEXT.NOTIFICATION_TEXT_13||SAP_LONG_TEXT.NOTIFICATION_TEXT_14||SAP_LONG_TEXT.NOTIFICATION_TEXT_15||SAP_LONG_TEXT.NOTIFICATION_TEXT_16||SAP_LONG_TEXT.NOTIFICATION_TEXT_17||SAP_LONG_TEXT.NOTIFICATION_TEXT_18||SAP_LONG_TEXT.NOTIFICATION_TEXT_19||SAP_LONG_TEXT.NOTIFICATION_TEXT_20||SAP_LONG_TEXT.NOTIFICATION_TEXT_21||SAP_LONG_TEXT.NOTIFICATION_TEXT_22||SAP_LONG_TEXT.NOTIFICATION_TEXT_23||SAP_LONG_TEXT.NOTIFICATION_TEXT_24||SAP_LONG_TEXT.NOTIFICATION_TEXT_25||SAP_LONG_TEXT.NOTIFICATION_TEXT_26||SAP_LONG_TEXT.NOTIFICATION_TEXT_27||SAP_LONG_TEXT.NOTIFICATION_TEXT_28||SAP_LONG_TEXT.NOTIFICATION_TEXT_29||SAP_LONG_TEXT.NOTIFICATION_TEXT_30||SAP_LONG_TEXT.NOTIFICATION_TEXT_31||SAP_LONG_TEXT.NOTIFICATION_TEXT_32||SAP_LONG_TEXT.NOTIFICATION_TEXT_33||SAP_LONG_TEXT.NOTIFICATION_TEXT_34||SAP_LONG_TEXT.NOTIFICATION_TEXT_35||SAP_LONG_TEXT.NOTIFICATION_TEXT_36||SAP_LONG_TEXT.NOTIFICATION_TEXT_37||SAP_LONG_TEXT.NOTIFICATION_TEXT_38||SAP_LONG_TEXT.NOTIFICATION_TEXT_39||SAP_LONG_TEXT.NOTIFICATION_TEXT_40||SAP_LONG_TEXT.NOTIFICATION_TEXT_41||SAP_LONG_TEXT.NOTIFICATION_TEXT_42||SAP_LONG_TEXT.NOTIFICATION_TEXT_43||SAP_LONG_TEXT.NOTIFICATION_TEXT_44||SAP_LONG_TEXT.NOTIFICATION_TEXT_45||SAP_LONG_TEXT.NOTIFICATION_TEXT_46||SAP_LONG_TEXT.NOTIFICATION_TEXT_47||SAP_LONG_TEXT.NOTIFICATION_TEXT_48||SAP_LONG_TEXT.NOTIFICATION_TEXT_49||SAP_LONG_TEXT.NOTIFICATION_TEXT_50) from sap_long_text@genadm where sap_long_text.notification = n.notif_no) "long",
       n.notif_date,
       n.funct_loc,
       n.order_no,
       n.notif_status,
       n.room,
       n.notif_type
from   notifications@amt n, SAP_LONG_TEXT@genadm
where instr(':'||:P9_NOTIFTYPE||':',':'||n.NOTIF_TYPE||':')>0 and
       instr (':'||:P9_SITE||':',':'||n.site||':') > 0 and
       n.notif_date BETWEEN :P9_DATEFROM and :P9_DATETO and
       n.notif_status not like '%NOCO%'I've had this error before but I don't remember why/what happened. The page has been working fine, the error just randomly cropped up today.
And a secondary question, is there a better way to write the query (it's a copy/paste from an older query). That select within the select is ugly...

Hello,
Take a look at the following thread -
help ORA-02049
Is it really necessary that you always query across the DBLink? Is using local materialized views not an option for you?
John.
http://jes.blogs.shellprompt.net
http://apex-evangelists.com

Compressor 4.1 distributed job - "waiting" status

Similar Messages

Maybe you are looking for