Purging tables getting stuck?
Oracle 10.1.0.3 & 10.1.0.4 (Linux AMD64).
I have an often occurring problem on several Oracle SE platforms - a data management PL/SQL job that among other things, create new tables and drop old tables. Yeah I know this is not the best of ideas, but without partitioning this is the only way to create and maintain a sliding window period - by creating individual tables instead of adding new partitions...
Regularly, such a job will spin forever on a wait even called enq: RO - fast object reuse.
Metalink and Google searches have not turned up anything much. Nor has posting about the problem here... Seems like a pretty much unknown event.
Recently doing some stuff on an Oracle EE platform and I start to butt my head into this again.. and only when using the PURGE clause for the DROP TABLE statement. And that is exactly what those SE data management jobs do too - they drop and purge tables outside the sliding window period.
Thus it would seem that the problem is related to the PURGE clause.
Anyone with similar experiences or ideas as to what the underlaying problem can be? Any special disclaimers/technical issues raised via Metalink notes regarding the PURGE clause?
Thanks.
> I believe the RO enqueue is associated with code that tries to clear the buffer
cache of clean blocks belonging to the object. You might find more about it with a
search on comp.databases.oracle.server.
Thanks Joanathan, As for comp.databases.oracle.server... I do miss the old stomping grounds but IT security here, in all their oh--so-wise and infinite wisdom, has blocked access to the whole of Usenet.
> A strategy that may help is to remove the PURGE from the drop, and dispatch a
job that does a "purge recyclebin" at some later time - with the hope that by the
time the "real" drop happens there won't be any buffered blocks for that object to
cause a problem.
Yeah.. that will well be worth a try and is simple to implement.
Similar Messages
-
I come across a problem, when some action is made and page is refreshed the table gets stucked into infinite loop (slide bar is jumping up and down until the browser crashes).
I get some data where this problem ocuurs:
x161 is null
AdfDhtmlPage.prototype.scheduleTimer= function(x157,x158,x159,x160)
AdfAssert.assertFunction(x158);
AdfAssert.assertNumber(x160);
var x161=AdfDhtmlPage._timers;
var x162=AdfDhtmlPage._nextTimerId++;
var x163={context:x157,state:x159,callback:x158,timerId:x162};
x161[x162]=x163;
x163.domTimerId=this.getDomWindow().setTimeout(
"AdfDhtmlPage.__callTimerCallback(" + x162 + ");",x160);
return x162;
too much recursion
AdfDhtmlTablePeer.prototype._getElemBySubId= function(x598,x599)
var x600=this.getDomElement();
if (x600==null)
x600=x599;
return AdfDhtmlTablePeer._getChildBySubId(x600,x598);
}On page is simple table in which in one column are go links, which commits a action (there is no problem with actions).
Thank you for your help, RokCan you check your faces-config.xml file, are navigation rules correct? Check the action property of the component which submits the page..
Regards,
Vikram -
Table /BIC/DzcubeP reading get stuck
Hi,
i'm having trouble deleting and creating indexes for an infocube ZCUBE.
I'm running some tests using transaction RSRV and it always get stuck reading (secuential reading)
table /BIC/DzcubeP on the test
What is this table ?
Why is it getting stuck on the reading ?
How can i solve this ?
thx in advance
JPHi JP,
/BIC/DzcubeP is dimension table of your CUBE
Check your CUBE dimensions once.
do the RSRV check of "Fact- and Dimension- Table of an InfoCube "
Regards,
Venkatesh
Edited by: Venky1903 on Aug 18, 2011 11:10 PM -
Creating table statement gets stuck
Hi everyone, i can use "select" statements without any problem but when i want to create a table with 100-1000 rows, it gets stuck and never returns and after i close the sql navigator and restart it, it creates my table easily but after 20-30 seconds when i want to create an another table, it stucks again. What can be the problem??(At the first times that i use sql, there was no problem)
Hi,
It's a bit difficult to answer. Members will try to help you about database problems but in this case it's impossible to know if it is a database problem. If you have the needed system privileges and some quota on a tablespace there is no reason you wouldn't be able to create tables in an Oracle database !
Ask your DBA to try directly with SQL Plus but if he confirms it's OK there is a problem with your SQL Navigator tool.
Best regards
Phil -
Mail gets stuck in apex_mail_queue table
Hi there,
I am trying to send the email using apex_mail.send package.
The email gets sent to the person I am intending to send but some time... Mind you not every time, there are some records that gets stuck in apex_mail_queue and it sends the same email 3 to 4 times.
I don't understand why this is happening!. Please help me with your suggestions..
Thanks
NayeemHi Nayeem,
Are you using an application in apex.oracle.com or a local application? In case it's local, can you tell us what the error message is for the mails that get stuck in apex_mail_queue? (you can take a look at the mail queue using the apex administration services, Manage Instance -> Mail Queue). By the way, if you try to send the same email a number of times and the sending is not successful, the messages remain in the queue as you commented, so when the next time to flush the queue and send the emails comes, if APEX can do it successfully, then it will send all the copies of the emails queued. Perhaps that is the reason why you're getting multiple copies of the same message?
Regards,
Sergio -
ICal gets "stuck" on date - can't view a different week without quitting
I haven't seen anyone else post this, but it's getting really annoying. Every now and then, iCal gets "stuck" on a particular week. If I click on a new date in the calendar, it is highlighted, but the date I am on remains highlighted as well, and the week view does not change to the new week.
When I am clicking on "To Dos" the list magically moves from the item I am clicking to another item on an earlier date - essentially the list scrolls to the top of the list, and instead of clicking on the item I want, I am clicking on whatever item is in the bottom of the window when viewed from the top of the list. When this happens, the week view changes to the week of that "To Do" item's due date, and - again - will not let me change the week that I'm viewing.
Anyone know of something I can delete or purge or cross out with a magic marker to make this stop happening?Actually, I only addressed your first complaint about the view being stuck to a specific week when a todo item in that week is selected.
It turns out I am also experiencing something that looks like your second complaint, about the wrong todo item being selected when you try to click on one. What I am seeing is the following: just like you can't show a date and its events outside of the current week if a todo item in the current week is selected, you can't show a todo item outside of the current week if an event in the current week is selected. If you scroll down and try to select the todo item, the list scrolls back up automatically, and you end up selecting a different todo item in the current week.
I also reported this to Apple in the same bug report.
So, good rules of thumb are the following:
- If you want to select/show an event or a day outside of the current week, make sure you first select an event in the current week;
- If you want to select a todo item outside of the current week, make sure you first select a todo item in the current week.
Hope this helps, while the guys at Apple are (hopefully) working on a fix. But I am rather pessimistic. My experience with bugs I reported in the past is that they are only fixed if they are critical, security-related bugs. If they are just usability bugs with workarounds like this one, they are only fixed in the next major release of OS X. But let's cross our fingers. There are so many people complaining about iCal on these forums that Apple might want to do something about it. But people who have complaints or requests about a product should send them directly to Apple, and assume by default that they are not reading this forum.
You can send your complaints on the following site:
http://www.apple.com/feedback/
The more people file complaints, the more likely they are to be fixed soon. You might want to put a link to this discussion thread so they know exactly what you are complaining about. -
Messages getting stuck in SMQ2
Messages get stuck in SMQ2 with the Error msg "SQL error on database occurred when accessing a table".
This is happening on PI system 7.11 SP04 with Max DB version 7.7.06.07.
This typically happens when sending messages from one BPM to another although it has more of a random pattern.
A corresponding dump is also seen in ST22.
The dump details are as below:
Runtime error : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
Database error text : Invalid numeric value for parameter/column (10)
Internal call code : "[RSQL/UPDT/SWFRXIHDR ]"
Any help is highly appreciated in resolving this issue.
Regards,
Murali Narayanan> The dump details are as below:
> Runtime error : DBIF_RSQL_SQL_ERROR
> Exception : CX_SY_OPEN_SQL_DB
> Database error text : Invalid numeric value for parameter/column (10)
I would update the kernel (plus the database interface library lib_dbsl) to the latest patchlevels and try again. If the error persists I'd upgrade the database to the latest patchlevel. If it still doesn't work I'd open an OSS call (BC-DB-SDB).
Markus -
Job its getting stuck on SIL_PurchaserOrderCostFact_Full
Hi Gurus,
I am running a DAC a job after rebuilding a new env but the Job takes an Hour in prodn env but now taking almost 2 hours in the new env. After investigation, the issue is the Job its getting stuck on SIL_PurchaserOrderCostFact_Full for almost an hour but in prod it complete in 2minutes or less. The job ends up completing in 2 hours.
I applied the following patches EBF189068, EBF191169 and patch 10052370
BI APPS 7.9.5
DAC 10.1.3.4.1
OBIEE 10.1.3.4.0
Below is the log detail for SIL_PurchaseOrderCostFact_Full
Thanks
Simmz
WRITER_1_*_1> WRT_8167 Start loading table [W_PURCH_COST_F] at: Thu May 26 16:29:03 2011
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:30:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 10008 Applied: 10008 Rejected: 0 Affected: 10008
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:31:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 20016 Applied: 20016 Rejected: 0 Affected: 20016
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:32:52 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 30024 Applied: 30024 Rejected: 0 Affected: 30024
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:34:20 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 40032 Applied: 40032 Rejected: 0 Affected: 40032
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:35:44 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 50040 Applied: 50040 Rejected: 0 Affected: 50040
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:37:02 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 60048 Applied: 60048 Rejected: 0 Affected: 60048
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:38:21 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 70056 Applied: 70056 Rejected: 0 Affected: 70056
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:39:49 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 80064 Applied: 80064 Rejected: 0 Affected: 80064
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:41:18 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 90072 Applied: 90072 Rejected: 0 Affected: 90072
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:42:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 100080 Applied: 100080 Rejected: 0 Affected: 100080
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:43:42 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 110088 Applied: 110088 Rejected: 0 Affected: 110088
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:44:56 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 120096 Applied: 120096 Rejected: 0 Affected: 120096
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:46:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 130104 Applied: 130104 Rejected: 0 Affected: 130104
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:47:28 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 140112 Applied: 140112 Rejected: 0 Affected: 140112
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:48:41 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 150120 Applied: 150120 Rejected: 0 Affected: 150120
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:49:56 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 160128 Applied: 160128 Rejected: 0 Affected: 160128
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:51:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 170136 Applied: 170136 Rejected: 0 Affected: 170136
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:52:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 180144 Applied: 180144 Rejected: 0 Affected: 180144
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:53:46 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 190152 Applied: 190152 Rejected: 0 Affected: 190152
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:54:46 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 200160 Applied: 200160 Rejected: 0 Affected: 200160
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:56:05 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 210168 Applied: 210168 Rejected: 0 Affected: 210168
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:57:29 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 220176 Applied: 220176 Rejected: 0 Affected: 220176
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 16:58:50 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 230184 Applied: 230184 Rejected: 0 Affected: 230184
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:00:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 240192 Applied: 240192 Rejected: 0 Affected: 240192
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:01:17 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 250200 Applied: 250200 Rejected: 0 Affected: 250200
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:02:32 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 260208 Applied: 260208 Rejected: 0 Affected: 260208
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:03:49 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 270216 Applied: 270216 Rejected: 0 Affected: 270216
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:05:04 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 280224 Applied: 280224 Rejected: 0 Affected: 280224
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:06:21 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 290232 Applied: 290232 Rejected: 0 Affected: 290232
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:07:38 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 300240 Applied: 300240 Rejected: 0 Affected: 300240
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:09:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 310248 Applied: 310248 Rejected: 0 Affected: 310248
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:10:33 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 320256 Applied: 320256 Rejected: 0 Affected: 320256
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:12:04 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 330264 Applied: 330264 Rejected: 0 Affected: 330264
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:13:31 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 340272 Applied: 340272 Rejected: 0 Affected: 340272
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:14:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 350280 Applied: 350280 Rejected: 0 Affected: 350280
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:16:14 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 360288 Applied: 360288 Rejected: 0 Affected: 360288
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:17:44 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 370296 Applied: 370296 Rejected: 0 Affected: 370296
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:19:06 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 380304 Applied: 380304 Rejected: 0 Affected: 380304
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:20:38 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 390312 Applied: 390312 Rejected: 0 Affected: 390312
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:21:55 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 400320 Applied: 400320 Rejected: 0 Affected: 400320
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:23:15 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 410328 Applied: 410328 Rejected: 0 Affected: 410328
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:24:39 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 420336 Applied: 420336 Rejected: 0 Affected: 420336
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:25:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 430344 Applied: 430344 Rejected: 0 Affected: 430344
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:27:17 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 440352 Applied: 440352 Rejected: 0 Affected: 440352
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:28:39 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 450360 Applied: 450360 Rejected: 0 Affected: 450360
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:29:57 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 460368 Applied: 460368 Rejected: 0 Affected: 460368
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:31:22 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 470376 Applied: 470376 Rejected: 0 Affected: 470376
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:32:52 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 480384 Applied: 480384 Rejected: 0 Affected: 480384
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:34:16 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 490392 Applied: 490392 Rejected: 0 Affected: 490392
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:35:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 500400 Applied: 500400 Rejected: 0 Affected: 500400
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:37:03 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 510408 Applied: 510408 Rejected: 0 Affected: 510408
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:38:22 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 520416 Applied: 520416 Rejected: 0 Affected: 520416
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:39:36 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 530424 Applied: 530424 Rejected: 0 Affected: 530424
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:40:58 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 540432 Applied: 540432 Rejected: 0 Affected: 540432
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:42:20 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 550440 Applied: 550440 Rejected: 0 Affected: 550440
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:43:37 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 560448 Applied: 560448 Rejected: 0 Affected: 560448
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:44:25 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 570456 Applied: 570456 Rejected: 0 Affected: 570456
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:45:09 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 580464 Applied: 580464 Rejected: 0 Affected: 580464
WRITER_1_*_1> WRT_8161
TARGET BASED COMMIT POINT Thu May 26 17:46:19 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 590472 Applied: 590472 Rejected: 0 Affected: 590472
READER_1_1_1> BLKR_16019 Read [597399] rows, read [0] error rows for source table [W_INT_ORG_D] instance name [W_INT_ORG_D]
READER_1_1_1> BLKR_16008 Reader run completed.
TRANSF_1_1_1> DBG_21216 Finished transformations for Source Qualifier [Sq_W_PURCH_COST_FS]. Total errors [0]
WRITER_1_*_1> WRT_8168 End loading table [W_PURCH_COST_F] at: Thu May 26 17:47:08 2011
WRITER_1_*_1> WRT_8141
Commit on end-of-data Thu May 26 17:47:08 2011
===================================================
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 597399 Applied: 597399 Rejected: 0 Affected: 597399
WRITER_1_*_1> WRT_8035 Load complete time: Thu May 26 17:47:08 2011
LOAD SUMMARY
============
WRT_8036 Target: W_PURCH_COST_F (Instance Name: [W_PURCH_COST_F])
WRT_8038 Inserted rows - Requested: 597399 Applied: 597399 Rejected: 0 Affected: 597399
WRITER_1__1> WRT_8043 ****END LOAD SESSION*****
WRITER_1_*_1> WRT_8006 Writer run completed.
MANAGER> PETL_24031
***** RUN INFO FOR TGT LOAD ORDER GROUP [1], CONCURRENT SET [1] *****
Thread [READER_1_1_1] created for [the read stage] of partition point [Sq_W_PURCH_COST_FS] has completed: Total Run Time = [4877.310545] secs, Total Idle Time = [187.907454] secs, Busy Percentage = [96.147314].
Thread [TRANSF_1_1_1] created for [the transformation stage] of partition point [Sq_W_PURCH_COST_FS] has completed: Total Run Time = [4875.388657] secs, Total Idle Time = [4867.607283] secs, Busy Percentage = [0.159605].
Thread [WRITER_1_*_1] created for [the write stage] of partition point [W_PURCH_COST_F] has completed: Total Run Time = [4817.325787] secs, Total Idle Time = [4796.966177] secs, Busy Percentage = [0.422633].
MAPPING> CMN_1793 The index cache size that would hold [411967] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid], in memory, is [107673600] bytes
MAPPING> CMN_1792 The data cache size that would hold [411967] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid], in memory, is [9912320] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_PRODUCT_D_Supplier_Prod_Wid], in memory, is [25600] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_PRODUCT_D_Supplier_Prod_Wid], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid], in memory, is [1945600] bytes
MAPPING> CMN_1792 The data cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid], in memory, is [188416] bytes
MAPPING> CMN_1793 The index cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Buyer_Wid], in memory, is [1945600] bytes
MAPPING> CMN_1792 The data cache size that would hold [7333] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Buyer_Wid], in memory, is [188416] bytes
MAPPING> CMN_1793 The index cache size that would hold [7070] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid], in memory, is [1868800] bytes
MAPPING> CMN_1792 The data cache size that would hold [7070] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid], in memory, is [180224] bytes
MAPPING> CMN_1793 The index cache size that would hold [2] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid], in memory, is [25600] bytes
MAPPING> CMN_1792 The data cache size that would hold [2] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [211199] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid], in memory, is [55219200] bytes
MAPPING> CMN_1792 The data cache size that would hold [211199] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid], in memory, is [5087232] bytes
MAPPING> CMN_1793 The index cache size that would hold [31568] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid], in memory, is [8294400] bytes
MAPPING> CMN_1792 The data cache size that would hold [31568] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid], in memory, is [14376960] bytes
MAPPING> CMN_1793 The index cache size that would hold [99] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM], in memory, is [14000] bytes
MAPPING> CMN_1792 The data cache size that would hold [99] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM], in memory, is [24576] bytes
MAPPING> CMN_1793 The index cache size that would hold [92117] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid], in memory, is [24115200] bytes
MAPPING> CMN_1792 The data cache size that would hold [92117] rows in the lookup table for [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid], in memory, is [2228224] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES], in memory, is [20480] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [0] rows in the lookup table for [Lkp_W_PURCH_COST_F], in memory, is [20480] bytes
MAPPING> CMN_1792 The data cache size that would hold [0] rows in the lookup table for [Lkp_W_PURCH_COST_F], in memory, is [16384] bytes
MAPPING> CMN_1793 The index cache size that would hold [1] rows in the lookup table for [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID], in memory, is [2800] bytes
MAPPING> CMN_1792 The data cache size that would hold [1] rows in the lookup table for [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID], in memory, is [16384] bytes
MANAGER> PETL_24005 Starting post-session tasks. : (Thu May 26 17:47:10 2011)
MANAGER> PETL_24029 Post-session task completed successfully. : (Thu May 26 17:47:10 2011)
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_25W32] for transformation [Lkp_W_PURCH_COST_F].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_524289W32] for transformation [mplt_Get_Etl_Proc_Wid.LKP_ETL_PROC_WID].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1507331W32] for transformation [mplt_Curcy_Conversion_Rates.GET_GLOBAL_CURR_CODES_AND_RATE_TYPES].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572874W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Inventory_Product_D_Inventory_Prod_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_2031617W32] for transformation [MPLT_LKP_W_SUPPLIER_PRODUCT_D.LKP_W_SUPPLIER_PRODUCT_D_Primary].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572876W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Employee_D_Requestor_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572865W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_PRODUCT_D_Product_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572867W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_GL_ACCOUNT_D_Gl_Account_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572878W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_Cost_Center_D_Cost_Center_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572866W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_PROFIT_CENTER_D_Profit_Center_Wid].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572868W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_Codes_UOM].
MAPPING> TE_7216 Deleting cache files [PMLKUP11186_1572869W32] for transformation [mplt_SIL_PurchaseCostFact.Lkp_W_SUPPLIER_D_Supplier_Wid].
MAPPING> TM_6018 Session [SIL_PurchaseCostFact_Full] run completed with [0] row transformation errors.
MANAGER> PETL_24002 Parallel Pipeline Engine finished.
DIRECTOR> PETL_24012 Session run completed successfully.
DIRECTOR> TM_6022There is another log file for Informatica that will give you detailed information on the issue. You should be looking into that log file.
-
Messages getting stuck in QRFC Queue
Hi,
Today I noticed that a message had gotten stuck with the status "Sheduled for Outbound Processing" (scenario IDOC->XI->File), XI 3.0 SP11.
This in turn had the effect that the whole QRFC queue got stuck, and all following messages got stuck with status "Sheduled".
I had to remove the first message from the queue manually so that XI could start to purge the other messages from the queue.
What could be the reason for the first messages getting stuck with this status ("Sheduled for Outbound Processing")?
The message was very small, just a couple of lines. One thing that comes into mind, is that XI received 4 IDOCS for the same interface, within one second. These 4 messages were assigned to different queues, but one of them got stuck. Could there be problems with XI when several messages arrive on the same interface within a very short time?
Is it possible to use Alerts to detect this kind of problem in the future? As I have understood, Alerts only handle XI "errors", but according to XI, this message did not have an "error status", it just had the status "Sheduled for Outbound processing"..
Thanks for any help,
HansHi,
If the message got struck in Queue, you try to activate the queues in smq2 to reprocess the data instead of deleting it. This is the final solution. But you should able to see a dump in ST22 for this problem.
thanks,
sasi -
PL anonymous block does everything, but then gets stuck
We have a PL/SQL block that loops through a cursor, and inserts data into another table. We're having a strange issue with it... Every single line of code within it appears to function correctly... It does everything we want it to. The last line on it calls a simple function that writes a record to a table we made, to indicate it has completed. It does that, and we can see the record is inserted successfully.
The problem: even though we can see it did everything, it gets "stuck". If we run it as a anonymous block, the sql plus session will just stay stuck. Same thing if we turn it into a procedure and invoke it. It just stays stuck. Viewing it from OEM... We can see the session as "active", but it doesn't show that it's currently executing anything.
How can we go about figuring out what the problem is?
We've tried it on four databases... All windows platforms.. Three were oracle 10g, one was Oracle 11g. One more interesting note: one of the 10g ones... the problem does not occur... the script finishes fine. But, we don't know what is different about this database from the others.
We also notice the problem doesn't happen if we limit the amount of records... the initial cursor we process, if we limit it using "rownum < 100" or something like that, it will also always finish fine.
This is the script:
set echo on
set serveroutput on
declare
n_notes_count number;
n_records_read number;
dt_today date;
MYDATE DATE;
dt_comment_date date;
dt_updated_date date;
t_conv_exceptions "ODB"."CONVERSION_EXCEPTIONS" %ROWTYPE;
t_conv_exceptions_default "ODB"."CONVERSION_EXCEPTIONS" %ROWTYPE;
t_note_pad "ODB"."NOTE_PAD"%ROWTYPE;
t_note_pad_clear "ODB"."NOTE_PAD"%ROWTYPE;
t_pfcomm "PMI"."PFCOMM"%ROWTYPE;
c_created_by "ODB"."NOTE_PAD"."CREATED_BY" % type ;
-- Exceptions to be raised
ex_notes_number_blank EXCEPTION;
--ex_category_not_exists EXCEPTION;
--....more to come.....
CURSOR cur_notes IS
SELECT PF."MMNUM",
PF."MMLIN",
PF."MMDES",
PF."MMUSR",
PF."MMMM",
PF."MMDD",
PF."MMYY",
PF."MMCC",
--"pfcomm"."mmchr",
--"pfcomm"."mncmn",
--"pfcomm"."mmtype",
PF."MMUSRU",
PF."MMMMU",
PF."MMDDU",
PF."MMYYU",
PF."MMCCU"
FROM PMI."PFCOMM" PF
WHERE TRIM(PF."MMDES") IS NOT NULL
ORDER BY PF."MMNUM", PF."MMLIN";
BEGIN
-- Initialize variables
dt_today := "ODB"."PKG_APPLICATION_FUNCTION"."CURRENTDATETIME";
c_created_by :='PFCOMM';
-- Setup defaults for exceptions table
t_conv_exceptions_default."SCRIPT" := 'atlas_notes';
t_conv_exceptions_default."EXECUTION_DATE" := dt_Today;
t_conv_exceptions_default."CREATED_BY" := c_created_by;
-- Set up header record for exception
t_conv_exceptions := t_conv_exceptions_default;
t_conv_exceptions.column_01 := 'NOTES';
t_conv_exceptions.header := 'Y';
ODB.PKG_CONVERSIONS_EXCEPTIONS.writeException(t_conv_exceptions, false);
-- Count records in table
SELECT COUNT(*)
INTO n_records_read
FROM PMI."PFCOMM";
-- Delete previously inserted records
DELETE FROM "ODB"."NOTE_PAD" NP
WHERE NP."CREATED_BY" = c_created_by or NP."MODIFIED_BY" = c_created_by;
DELETE FROM "ODB"."NOTE_PAD" NP
WHERE NP."CREATED_BY" = 'PFCOMM2' or NP."MODIFIED_BY" = 'PFCOMM2';
DELETE FROM "ODB"."CONVERSION_EXCEPTIONS" CV
WHERE CV."CREATED_BY" IN (c_created_by,'PFCOMM2');
COMMIT;
/* Do Fetch here */
OPEN cur_notes;
LOOP
FETCH cur_notes
INTO t_pfcomm."MMNUM",
t_pfcomm."MMLIN",
t_pfcomm."MMDES",
t_pfcomm."MMUSR",
t_pfcomm."MMMM",
t_pfcomm."MMDD",
t_pfcomm."MMYY",
t_pfcomm."MMCC",
--"t_pfcommcomm"."mmchr",
--"t_pfcommcomm"."mncmn",
--"t_pfcommcomm"."mmtype",
t_pfcomm."MMUSRU",
t_pfcomm."MMMMU",
t_pfcomm."MMDDU",
t_pfcomm."MMYYU",
t_pfcomm."MMCCU";
EXIT
WHEN cur_notes % NOTFOUND;
-- Clear Variables
t_note_pad := t_note_pad_clear;
dt_comment_date := null;
dt_updated_date := null;
-- Begin variable assignments
t_conv_exceptions."COLUMN_01" := t_note_pad."NOTES";
t_note_pad."NOTES" := t_pfcomm."MMNUM";
t_note_pad."NOTES_TEXT" := t_pfcomm."MMDES";
-- Validate required fields
If t_note_pad."NOTES" is null Then
raise ex_notes_number_blank;
End if;
-- Sequence lines correctly
SELECT NVL( MAX("ODB"."NOTE_PAD"."NOTES_LINE"), 0)
INTO t_note_pad."NOTES_LINE"
FROM "ODB"."NOTE_PAD"
WHERE "ODB"."NOTE_PAD"."NOTES" = t_note_pad."NOTES"
-- Next note line number to insert
If t_note_pad."NOTES_LINE" is null Then
t_note_pad."NOTES_LINE" := 1;
Else
t_note_pad."NOTES_LINE" := t_note_pad."NOTES_LINE" + 1;
End if;
-- MMDDCCYY - Comment Date
If t_pfcomm."MMMM" > 0 Or t_pfcomm."MMDD" > 0 Or t_pfcomm."MMCC" > 0 Or t_pfcomm."MMYY" > 0 Then
SELECT TO_DATE(LPAD(t_pfcomm."MMMM",2,'0') || LPAD(t_pfcomm."MMDD",2,'0') || LPAD(t_pfcomm."MMCC",2,'0')|| LPAD( t_pfcomm."MMYY",2,'0'),'MMDDYYYY') INTO dt_comment_date FROM DUAL;
End if;
-- MMDDCCYY - Updated Date
If t_pfcomm."MMMMU" > 0 Or t_pfcomm."MMDDU" > 0 Or t_pfcomm."MMCCU" > 0 Or t_pfcomm."MMYYU" > 0 Then
SELECT TO_DATE(LPAD(t_pfcomm."MMMMU",2,'0') || LPAD(t_pfcomm."MMDDU",2,'0') || LPAD(t_pfcomm."MMCCU",2,'0')|| LPAD( t_pfcomm."MMYYU",2,'0'),'MMDDYYYY') INTO dt_updated_date FROM DUAL;
End if;
-- Updated user information
IF dt_updated_date is not null Then
t_note_pad."CREATED_BY" := TRIM(t_pfcomm."MMUSRU");
t_note_pad."CREATED_DATE" := dt_updated_date;
Elsif dt_comment_date is not null Then
t_note_pad."CREATED_BY" := TRIM(t_pfcomm."MMUSR");
t_note_pad."CREATED_DATE" := dt_comment_date;
Else
t_note_pad."CREATED_BY" := c_created_by;
t_note_pad."CREATED_DATE" := dt_today;
END IF;
/* Validate mandatory fields of TRAX table */
IF t_note_pad.NOTES = 0 THEN
t_note_pad.NOTES :=null;
End If;
IF t_note_pad.NOTES_LINE is null THEN
t_note_pad.NOTES_LINE := 1;
End If;
IF TRIM(t_note_pad.PRINT_NOTES) is null Then
t_note_pad.PRINT_NOTES := 'YES';
END IF;
IF TRIM(t_note_pad.NOTES_CATEGORY) is null THEN
t_note_pad.NOTES_CATEGORY := 'NORMAL';
END IF;
If TRIM(t_note_pad."CREATED_BY") is null Then
t_note_pad."CREATED_BY" := c_created_by;
End if;
If TRIM(t_note_pad."MODIFIED_BY") is null Then
t_note_pad."MODIFIED_BY" := c_created_by;
End if;
If TRIM(t_note_pad."MODIFIED_DATE") is null Then
t_note_pad."MODIFIED_DATE" := dt_today;
End if;
If TRIM(t_note_pad."CREATED_DATE") is null Then
t_note_pad."CREATED_DATE" := dt_today;
End if;
-- end structure validation
/* Do Insert here here */
insert into "ODB"."NOTE_PAD"
values t_note_pad;
commit;
END LOOP;
dbms_output.put_line('After loop.');
CLOSE cur_notes;
-- Update NOTES Switch
SELECT MAX(NT."NOTES") + 100
INTO n_notes_count
FROM "ODB"."NOTE_PAD" NT
UPDATE "ODB"."SYSTEM_TRAN_CONFIG"
SET "CONFIG_NUMBER" = n_notes_count,
"MODIFIED_BY" = 'TRAXCNV',
"MODIFIED_DATE" = dt_today
WHERE ( ODB."SYSTEM_TRAN_CONFIG"."SYSTEM_TRANSACTION" = 'CONFIGURATION' ) AND
( ODB."SYSTEM_TRAN_CONFIG"."SYSTEM_CODE" ='NOTES' )
COMMIT;
dbms_output.put_line('before audit.');
/* Do Save Audit record */
"ODB"."PKG_CONVERSIONS_EXCEPTIONS".writeAudit(t_conv_exceptions."SCRIPT",c_created_by,n_records_read,dt_today);
dbms_output.put_line('After audit.');
SELECT SYSDATE INTO MYDATE FROM DUAL;
-- Begin exception handling.
exception
when ex_notes_number_blank then
t_conv_exceptions.exception_description := 'Note number is blank.';
ODB.PKG_CONVERSIONS_EXCEPTIONS.writeException(t_conv_exceptions, false);
when others then
t_conv_exceptions.exception_description := substr(SQLERRM,1,1000);
ODB.PKG_CONVERSIONS_EXCEPTIONS.writeException(t_conv_exceptions, false);
RAISE;
-- End exception handling.
dbms_output.put_line('before end.');
END ;
/Avoid row-at-a-time processing if at all possible (cursor for loops, periodic commits, etc).
Try adding some calls to dbms_application_info.set_module (or set_action) in order to find out where your code is. -
Reasons why TRFC's get stuck in SM58
Hi
Can anyone give reasons why TRFCS get stuck in SM58.
We have a problem and it isnt as simple as just releasing them manually as it is happening a lot so wondered if there was any tables or log that could be deleted etc
Cheers
AndyHi,
Please check the OSS Note 1025249 - Entries in transaction SM58 "hang"
Thanks,
Sridhar
Edited by: Sridhar Kaukuntla on Jun 30, 2009 9:40 PM -
Cursor for update get stuck while running the program
Dear
i am using below mention program but work and get stuck. please any idea how can reslove this.
declare
l_segment1 VARCHAR (100);
CURSOR req_number_cur
IS
SELECT TO_CHAR (current_max_unique_identifier + 1)
FROM po_unique_identifier_control
WHERE table_name = 'PO_REQUISITION_HEADERS'
FOR UPDATE OF current_max_unique_identifier;
BEGIN
fnd_client_info.set_org_context (101);
mo_global.set_policy_context ('S', 101);
dbms_output.put_line('testing');
begin
OPEN req_number_cur;
FETCH req_number_cur
INTO l_segment1;
IF req_number_cur%NOTFOUND
THEN
--do something
NULL;
--insert statement
UPDATE po_unique_identifier_control
SET current_max_unique_identifier = current_max_unique_identifier + 1
WHERE CURRENT OF req_number_cur;
END IF;
CLOSE req_number_cur;
end;
END;
---thanks
appreciate you help.Do you realise that this is a flawed approach?
Performance in a multi-user and multi-process database system is about the ability to do things simultaneously.
Simple analogy. You have a McDonalds. You have a 100 customers wanting to be serviced. What will be better? Having the customer all queuing in a single long queue to be serviced by a single cashier?
Or 10 cashiers, 10 queues, and the ability to service 10 customers at the same time?
It should be very obvious that the ability to service 10 customers at the same time is a lot better than only servicing a single customer at a time.
Likewise, Oracle can service 1000's of different sessions all inserting data.
Now you want to create a single queue for all insert transactions - and give each one a unique and sequential identifier. This will literally kill performance. It will turn a 32 CPU server into a 1 CPU desktop as all that extra CPU power can never be used as all the sessions need to get into a single queue and be serviced one at a time.
Also consider the functionality of your approach. Session 1 gets a 5 unique identifiers as it wants to insert 5 rows. Session 2 gets the next 3 sequence numbers. Session 1 aborts and rolls back its transaction (numerous practical reasons exist for why this can and do happen).
What is the status now in the database table? 5 numbers are now "missing".
So despite your severely flawed attempt to enforce serialisation and sequential numbering, it will fail. So why then even contemplate turning the Oracle database from being able to service multiple concurrent sessions at the same time, to a slow single-user/single-process database that can only service a single request at a time?
The CORRECT approach in Oracle is to use a sequence generator (see the CREATE SEQUENCE command in the <i>SQL Reference Guide</i>). Use it. Do not try a flawed approach that WILL fail and that WILL have a very severe performance impact. -
Email getting stuck on Deferred Workflow.
Things we tried…
1.Refresh-
Workflow Deferred Notification Agent Listener
Workflow Deferred Agent Listener
Workflow Java Deferred Agent Listener
Workflow Agent Listener Service
Workflow mailer
Workflow mailer service
And
2.Run the workflow background process for AP REMITTANCE ADVICE
After running these the WF_DEFERRED table started to release stuck records.
However the when the new PAYMENT were created. The supplier is sent e mail notification ..the lines got stuck again.
Any ideas why its getting stuck ?Closing this as I will open this in another group.
-
I have a CTAS stmt, when it get a particular table scan operation, it always get stuck. I can see the op in OEM and stuck right at 76%.
Any idea?
CarltonHi,
You can also get helpful information from v$session_wait view.
Thanks
Kuljeet Pal Singh -
Hi,
We are trying to take an export from out existing database. But somehow, everytime we give the expdp command, it created a 4KB dmp file and gets stuck there. We have tried exporting a single table as well, but still the same. It does not even throw any error and nothing is written in the log file.
The status in dba_datapump_jobs shows that this job is executing. But no progress. I have even kept this job running for more than 12 hrs but still no progress.
DB Version is : 11.2.0.1.0
OS : Windows 2003 Server (64-bit) SP2
Following is the status in the command window
C:\Documents and Settings\sysfmg>expdp system/******** full=y directory=UTF_CONVERT parallel=4 dumpfile=New_Full_Dump_%U.dmp logfile=New_Full_Dump.log
Export: Release 11.2.0.1.0 - Production on Thu Apr 26 09:36:35 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_FULL_01": system/******** full=y directory=UTF_CONVERT parallel=4 dumpfile=New_Full_Dump_%U.dmp logfile=New_Full_Dump.log
Export status is shown as below
Export> status
Job: SYS_EXPORT_FULL_01
Operation: EXPORT
Mode: FULL
State: EXECUTING
Bytes Processed: 0
Current Parallelism: 4
Job Error Count: 0
Dump File: F:\UTF_CONVERT\New_Full_Dump_01.DMP
bytes written: 4,096
Dump File: F:\UTF_Convert\New_Full_Dump_%u.dmp
Worker 1 Status:
State: UNDEFINED
Request some help regarding this issue.I followed all the points mentioned by you. it is still the same.Ok, no problem, but you are not showing / answering my question(s) i.e.
1.What happens if you start exptp with trace=y and show the contents of trace file.
2.What is output of below command (to see invalid objects in SYS schema), by SYSDBA user :
select count(*) from all_objects where status='INVALID' and owner='SYS';
3.Just try to see that there is no issue with expdp binaries by creating another test db and then run expdp for this new db. And then run catalog.sql after creation.
4.How are you checking that there is no compatibility problem between Oracle client (10.2) and server versions (11.2) ?
5.Is there anything in alert log ?
6.What is status in dba_datapump_jobs ?
7.check v$session_wait for that particular program.
8.Check for BLOCKING_SESSION_STATUS in v$session for particular SID.
9.What happens if you just try to give EXP_FULL_DATABASE role to another user and then starts expdp with another user ?
At least I will not further reply, if I don't see copy and paste answer of above questions. Please don't say that "it is not working" or "it is stuck"; these seems rude as well as frustrating, show us what and how you are doing to get the solution and what and how Oracle is responding.
Regards
Girish Sharma
Edited by: Girish Sharma on Apr 26, 2012 2:35 PM
Typo corrected.
Maybe you are looking for
-
Hi all, I wonder if you can help me here? I am getting an issue will illustrator CS3 when I send a document to print some of the text goes missing on the print out? This only seems to happen with white text? I have tried creating a new document and p
-
Date reads as December 31, 1969 on ipad.
Ipad date is 12/31/69. When I try to change it, the ipad freezes up and is inoperable for about 24 hours. During the freeze, the battery is drained. I can recharge the battery with no problem.
-
Hello Experts, The following UDV code works until I add the WHERE clause, at which time I get a syntax error near keyword WHERE: DECLARE @x INTEGER SET @x = $[$3.2.NUMBER] WHERE $[$3.1.0] = 'Mileage' SELECT CASE WHEN @x BETWEEN 1 AND 19 THEN 10 WHEN
-
I would like my app to be available for download as a Trial version, which can be validated using a serial key. Can anyone please give me an idea of how the serial key validation works or how I can implement it??.. thanks for the help.
-
I keep getting an error when im answering questions for my chacha job i dont know what it means
when i go to my dash bored on my chacha account i keep getting this error and i dont know what it means Error: "CustomXML()" don't work in Firefox/Mozilla toolbar version. Please use "setCustomXML(sName, sXMLData)" instead. that is the error i get ==