Parallels update

I have installed parallels and xp and it worked.
I updated Parallels and now get this message-
"Parallels Desktop is unable to operate properly since it cannot communicate with one of its drivers. Seems that drivers are inconsistent with the currently installed version of Parallels Desktop. To overcome this issue, reinstall Parallels Desktop and start it by selecting Finder->Applications->Parallels->Parallels Desktop."
I have installed unistalled and keep geting the same message -
Oh - I now remember why I have a Mac!!!!
Please can some one help?
Thanks

You can buy an apple time capsule to do it wirelessly with apple time machine
You can buy any third party external hard drive, and do it automatically with time machine
You can buy any third party external hard drive, and do it manually.
I have a time capsule and external hard drives for safety.
May be the best external hard drives are the newer smaller portable ones that take power from the USB. e.g. iomega eGo or the rugged laCie unless you need huge external storage in the terrabyte range.

Similar Messages

Parallel updates on a user

Hello,
I'm facing a problem that some already faced (in the forum on sun.com, in 2006, http://forums.sun.com/thread.jspa?threadID=5061281) but no definitive solution was provided...
A use case I have is to request roles for a user and for each requested role, I have potential approvals to gather.
If I allow to request multiple roles at the same time (which is the standard if using the default user form in the admin GUI):
- I have approvals sent to the different approvers (ie. adminA & adminB for role1, adminA & adminC for role2) : that's OK, that's what I want, adminA receives two workitems to approve
- I one of the approval is rejected, no matter which one (let's say adminB rejects assignment of role1), the whole request is rejected (even the assignment of role2!) and a new request is needed to assign role2 : that's not OK. role1 may be rejected and role2 approved
If I decide to modify the form to only allow one role to be requested at a time:
- I have approval sent to the approvers for the requested role
- Until the approval phase is over, I cannot launch a new request for the user. If I need to assign multiple roles, I have to wait between each role request. This would mean a user may have to wait for days before being able to have the needed access to resources!
How would you workaround this Sun IDM (sorry, Oracle Waveset!) design:
- Renaming the update task is not sufficient since the userview is checked out before the approval process is launched. Isn't it? Therefore, I cannot check out the view until it is checked-in after the approval is done
- modify the update user standard workflow (or another standard process somewhere) to differ the view checkout only once the approval is done. But I'm not sure I can replace it with a getView to compute updates and approvals so easily... I fear side-effects...
Do you have any (good) idea regarding this issue? I'm sure I'm not the only one facing this currently...
Thanks for your help!
Edit: I made a wrong statement about why renaming is not OK:
If I try to rename the task adding a timestamp for instance to make the name uniqueif I launch a new request for the user, things will not be OK:
-- say the first request is approved first => user is updated according to first request. When second request is approved, the role assigned during the first reqeust will be un-assigned (the user view generated at the time of the second reqeust did not include the first role assignement yet...
-- say the second request is arrpoved first => same kind of effect .
second
Edited by: bcarlier on Nov 4, 2010 2:47 PM

Hello,
no this does not solve directly my problem. I cannot use standard "update user" with "standard approvals" because "update user" takes a view as an entry (and if you provide only updates, it calculates a view at the beginning). If you need several parallel role requests, the standard "update user" prevents you from that (by saying an aupdate task already exists and if you rename the first one, the latest one being approved will overwrite previous updates.
What I need is:
- ask the requester for the changes he wants
- forward this information to my custom approvers
- upon approval, and only then, checkout the current view (so not the one at the time of the request), apply the requested change, launch the standard "update user" process without further approval.
This way, I can launch several requests in parallel having independant approval processes and having only approved changes applied to the user without the fear of discarding previous assignments.
@madhatter: I may use the split join mecanism to do parallel approval on single requests (I have two type of approvals for a single role). I'm also thinking building a custom approval object to pass to the Approval Evaluator process.

How To Perform Parallel UPDATE When Trigger is ENABLE On Table.

select *from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
PL/SQL Release 11.1.0.7.0 - Production
CORE    11.1.0.7.0      Production
TNS for Linux: Version 11.1.0.7.0 - Production
NLSRTL Version 11.1.0.7.0 - ProductionIs there any way to perform PARALLEL UPATE on a table which has a trigger?
One of my ETL performs a large UPDATE (14 Million update) everyday on a production hot table. Eventhough PDML is enable at session level (also TABLE.DEGREE=8), Oracle is doing serialized UPDATE.
As per Oracle documents, it is documented behavior.
Here is my Execution plan when i put the trigger ENABLE
| Id | Operation              | Name                | Rows | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |    TQ |IN-OUT| PQ Distrib |
|   0 | UPDATE STATEMENT       |                     |       |       | 6443 (100)|          |       |       |        |      |            |
|   1 | UPDATE                | ACCOUNT             |       |       |            |          |       |       |        |      |            |
|* 2 |   PX COORDINATOR       |                     |       |       |            |          |       |       |        |      |            |
|   3 |    PX SEND QC (RANDOM) | :TQ10000            | 72487 | 3610K| 6443   (3)| 00:01:18 |       |       | Q1,00 | P->S | QC (RAND) |
|* 4 |     FILTER             |                     |       |       |            |          |       |       | Q1,00 | PCWC |            |
|   5 |      PX BLOCK ITERATOR |                     | 72487 | 3610K| 6443   (3)| 00:01:18 |   KEY |   KEY | Q1,00 | PCWC |            |
|* 6 |       TABLE ACCESS FULL| ACCOUNT             | 72487 | 3610K| 6443   (3)| 00:01:18 |   KEY |   KEY | Q1,00 | PCWP |            |
Predicate Information (identified by operation id):
     8 - filter("SET_OF_BOOKS"='1' AND "GL_BATCH_ID">(-10) AND ("JOURNAL_ENTRY_TYPE_ID"<2400 OR
              "JOURNAL_ENTRY_TYPE_ID">=3000) AND "ACCOUNTING_DATE">=TO_DATE(' 2010-08-11 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss') AND "ACCOUNTING_DATE"<TO_DATE(' 2010-08-12 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))When i disable trigger
| Id | Operation                | Name     | Rows | Bytes | Cost (%CPU)| Time     |    TQ |IN-OUT| PQ Distrib |
|   0 | UPDATE STATEMENT         |          |   726 | 27588 | 11899   (2)| 00:02:23 |        |      |            |
|   1 | PX COORDINATOR          |          |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM)    | :TQ10001 |   726 | 27588 | 11899   (2)| 00:02:23 | Q1,01 | P->S | QC (RAND) |
|   3 |    INDEX MAINTENANCE     | ACCOUNT |       |       |            |          | Q1,01 | PCWP |            |
|   4 |     PX RECEIVE           |          |   726 | 27588 | 11899   (2)| 00:02:23 | Q1,01 | PCWP |            |
|   5 |      PX SEND RANGE       | :TQ10000 |   726 | 27588 | 11899   (2)| 00:02:23 | Q1,00 | P->P | RANGE      |
|   6 |       UPDATE             | ACCOUNT |       |       |            |          | Q1,00 | PCWP |            |
|   7 |        PX BLOCK ITERATOR |          |   726 | 27588 | 11899   (2)| 00:02:23 | Q1,00 | PCWC |            |
|* 8 |         TABLE ACCESS FULL| ACCOUNT |   726 | 27588 | 11899   (2)| 00:02:23 | Q1,00 | PCWP |            |
Predicate Information (identified by operation id):
   8 - filter("SET_OF_BOOKS"='1' AND "GL_BATCH_ID">(-10) AND ("JOURNAL_ENTRY_TYPE_ID"<2400 OR
              "JOURNAL_ENTRY_TYPE_ID">=3000) AND "ACCOUNTING_DATE">=TO_DATE(' 2010-08-11 00:00:00', 'syyyy-mm-dd
              hh24:mi:ss') AND "ACCOUNTING_DATE"<TO_DATE(' 2010-08-12 00:00:00', 'syyyy-mm-dd hh24:mi:ss'))I cannot disable trigger due to some business reasons.
Is there any way to speed up UPDATE ?

No, you cannot perform parallel dml with a trigger present.
If you are updating the bulk of the rows and can take an outage, you can
disable the trigger, perform the update, enable the trigger
OR
copy to another table, performing the update in the select, rename the tables and add the trigger on the new table
Hemant K Chitale

Oracle 8i hash parallel update question

Hello All,
Fairly new to Oracle (old Sybase guy). Using Oracle 8i. Trying to
get an update to run in parallel against a table. Partitioned the
table 4 ways using hash partitioining. Please see the following
query/plan. I am trying to determine if this query is actually running
in parallel or not from the plan? If it is not, what might be
preventing it from running in parallel? I would expect Oracle would
kick off one thread to update each of the four partitions of the
sales_tran_detail table.
Appreciated,
Jeff
UPDATE /*+ PARALLEL(sd, 4) */ SALES_TRAN_DETAIL_HASH SD
SET PRI_PUBLISHER_CALC_STATUS_CD = DECODE(9, 1,
PUBLISHER_CALC_STATUS_CD, 4, PUBLISHER_CALC_STATUS_CD, 7,
PUBLISHER_CALC_STATUS_CD, 10, PUBLISHER_CALC_STATUS_CD,
PRI_PUBLISHER_CALC_STATUS_CD),
PUBLISHER_CALC_STATUS_CD = '10', --If Monthly/Quarterly, then
'DROPOUT'
PUBLISHER_CALC_STAT_CHANGE_DT = '30-SEP-2006',
PUBLISHER_PROCESS_PERIOD_DT = '30-SEP-2006'
WHERE PUBLISHER_CALC_STATUS_CD IN ('09', '10', '30', '50')
AND EXISTS (SELECT 1
FROM SALES_TRAN_HEADER SH,
MCEF_INPUT_RPUPSALE MCEF
WHERE SH.SALES_PERIOD_DT <= '30-SEP-2006'
AND SD.SALES_PERIOD_DT = SH.SALES_PERIOD_DT
AND SD.BATCH_ID = SH.BATCH_ID
AND SD.AFFILIATE_ID = SH.AFFILIATE_ID
AND MCEF.DATAFILE_CD = 'D' -- Records in Error
AND MCEF.BATCH_ID IN (' ', SH.BATCH_ID)
AND MCEF.ALT_COPYRIGHT_IN = 'N'
AND SH.DISTRIBUTION_METHOD_CD =
MCEF.DISTRIBUTION_METHOD_CD
AND SH.AFFILIATE_ID = MCEF.AFFILIATE_ID
AND SD.AFFILIATE_ID = MCEF.AFFILIATE_ID
AND SD.CATLG_CORE_ID = MCEF.CATLG_CORE_ID
AND SD.CATLG_PFIX_ID = MCEF.CATLG_PFIX_ID)
EXPLAIN PLAN from QUEST:
1 Every row in the table Partitions accessed #1 - #4 is read.
2 All partitions of steps 1 were accessed..
3 Rows were retrieved using the unique index PRD1.SALES_TRAN_HEADER_P.
4 Rows from table PRD1.SALES_TRAN_HEADER were accessed using rowid got
from an index.
5 One or more rows were retrieved using index
PRD1.MCEF_INPUT_RPUPSALE_N1. The index was scanned in ascending order.
6 For each row retrieved by step 4, the operation in step 5 was
performed to find a matching row.
7 For the rows returned by step 6, filter out rows depending on filter
criteria.
8 For the rows returned by step 2, filter out rows depending on filter
criteria.
9 Rows were updated.
10 Rows were updated.

Thanks everyone for the responses on this. I have tried everything suggested thus far and still do not get what I can recognize as an explain plan that shows parallel execution or multiple threads when running. I would have thought the hint would have forced it to happen!
My parallel_max_servers is set to 6.
I copied in the header as stated in goodwithalls email.
I enabled parallel dml for the session and played with "..adaptive_multiuser_tuning".
I still get exactly the same plan as posted and still 1 thread. I wonder if Oracle just doesn't like doing updates vs. hash paritioned tables in 8i? It claims it does it vs. paritioned tables but maybe hash doesn't count.. or it wants me to create paritioned indexes too or something wierd..
Still lost on this one,
Any other thoughts anyone?
Thanks,
Jeff

Parallels Update Build 3224

I am having difficulties installing Windows XP Professional onto my fully purchased copy of Parallels (build 1848.2) I emailed the support crew at Parallels and they gave me the following steps:
The thing is that 1940 build is too old and it is not compatible with
Leopard OS. That is why you should upgrade your Parallels Desktop up to
3224 build. Please follow my instructions:
1. Start Parallels Desktop.
2. When you'll see the window that says Windows is suspended or stopped
you should press the stop button from the right side once again.
3. Then from the top of your screen you can find Help. Click on it and
choose Check for Updates...
4. In appeared window click on Check Now button.
5. Download the dmg package on your desktop.
6. When it's finished you should close Parallels Desktop and open the
package.
7. Click on installation icon andfollow the instructions to update your
Parallels Desktop.
Step 4 is where I hit the wall. The 'searching for updates' window pops up but that's it, even after waiting for a considerable amount of time, nothing appears. I just want to get this program working, can anyone please help ? ? ?
Peace
mat

Since Parallels is not an Apple product, you'll probably want to post your question on Parallels own discussion forums, as they're obviously geared more toward your issues than an Apple forum:
http://forums.parallels.com

ORA-08177 Parallel updates

Hello,
some days ago I got a problem where I get a ORA-08177 error.
I have 2 process running in parallel and each update one row in a particular table, but not the same row.
They ran every nigth for 3 months or so and I never had a problem with that, but one time they stoped with a ORA-08177 and when I restarted them I got the same error again, had to run them in sequence to solve the problem.
I'm using Oracle 11g and the table that those processes are updating has inittrans=1 and PCTUSED = null.
I'm guessing that on that particular day both rows where on the same block and that block must have been full and did not have space to expand the transaction header, so I must increase inittrans to 2 or put some limit in PCTUSED so that I always have some free space in the blocks.
I want to know if this makes any sense or I'm trying to solve the problem in the wrong way.
Thanks

$ oerr ora 8177
08177, 00000, "can't serialize access for this transaction"
// *Cause:   Encountered data changed by an operation that occurred after
//           the start of this serializable transaction.
// *Action: In read/write transactions, retry the intended operation or
//           transaction.I'm not sure that has something do to with INITRANS setting but it is more likely this has something to do with transaction isolation level that seems to be set to serializable. Are you using serializable transactions ? If yes are you sure that it is really needed by your application ?
Edited by: P. Forstmann on 17 janv. 2011 17:27
Edited by: P. Forstmann on 17 janv. 2011 17:37

Parallel Update

( I want to update all tables parallely using this procedure) How to rewrite the query for speed operation
CREATE OR REPLACE PROCEDURE fast_direct_sk1 (cust_id in varchar2,cust_name in varchar2,old_customername in varchar2,error_id in varchar2 )
IS
v_ErrorCode NUMBER;
v_ErrorMessage VARCHAR2(255);
BEGIN
update EXP__CFG__Search_sk set CUSTOMERNAME=cust_name where CUSTOMERNAME= old_customername;
update POM__CRF__OutputData_sk set customer_name=cust_name where CUSTOMER_NAME= old_customername;
commit;
update EXP__PRT__Generic_Print_sk set R_CUSTOMERNAME= cust_name where R_CUSTOMERNAME=old_customername;
update POM__GSR_sk set d_CUSTOMERNAME= cust_name where d_CUSTOMERNAME=old_customername;
commit;
update EXP_Main_Console_Searches_sk set T_VIEWCUSTOMERNAME=cust_name where T_VIEWCUSTOMERNAME=old_customername;
update EXP_Main_Console_Searches_sk set OM_VIEWCUSTOMERNAME=cust_name where OM_VIEWCUSTOMERNAME=old_customername;
commit;
Update EXP__CFG__Customer_Contract_sk set CUSTOMER_NAME=cust_name where BFG_CUSTOMER_ID=cust_id;
Update EXP__CFG__Contract_Access_sk set CUSTOMERNAME= cust_name where BFG_CUSTOMERID=cust_id;
Update EXP__CFG__Contract_Settings_sk set CUSTOMERNAME= cust_name where BFG_CUSTOMERID=cust_id;
commit;
Update EXP__CFG__Customer_Settings_sk set CUSTOMERNAME= cust_name where BFG_CUSTOMERID=cust_id;
Update EXP__CFG__MSA_New_sk set CUSTOMER_NAME=cust_name where CUSTOMER_ID=cust_id;
Update EXP__CFG__MSA_Settings_sk set CUSTOMER_NAME=cust_name where BFG_CUSTOMER_ID = cust_id;
commit;
Update EXP__I_F__Create_Request_sk set CUSTOMERNAME= cust_name where BFG_CUSTOMERID = cust_id;
Update EXP__Inventory__Audit_Trail_sk set CUSTOMERNAME= cust_name where CUSTOMERNAME= old_customername;
commit;
Update EXP__MC__Search_Criteria_sk set CUSTOMERNAME= cust_name where CUSTOMERNAME= old_customername;
Update EXP__Notification_sk set CUSTOMER_NAME=cust_name where customer_name=old_customername;
commit;
Update EXP__Request_sk set R_CUSTOMERNAME = cust_name where BFG_CUSTOMERID=cust_id;
commit;
Update Product__InstanceHeader_sk set R_CUSTOMERNAME= cust_name where D_BFG_CUSTOMERID= cust_id;
commit;
exception
WHEN OTHERS THEN
v_errorcode := SQLCODE;
v_ErrorMessage := SUBSTR(SQLERRM, 0, 255);
INSERT INTO REMEDY_SYSLOG
(logtime, errorcode, errormsg, FUNCTION)
VALUES
(SYSDATE, v_ErrorCode, v_ErrorMessage, error_id);
COMMIT;
END fast_direct_sk1;

The above query update one by one, The update is consuming more time, How to rewrite the query for fast update

Parallel query for UPDATE

Hi,
In the documentation of Oracle 10.2 -> Data Warehousing guide -> Ch.25 Using Parallel execution, search for section labeled "Rules for UPDATE, MERGE and DELETE", it is mentioned that,
"UPDATE, MERGE, and DELETE operations are parallelized by partition or subpartition. Update, merge, and delete parallelism are not possible within a partition, nor on a nonpartitioned table"
I am on 10.2 Enterprise edition, Solaris. I can see that, I can parallelize an UPDATE command (commands pasted below).
Please can somebody explain me, what am I missing ??
SQL> drop table r1 ;
Table dropped.
SQL> create table r1 as select * from user_objects where 1=2 ;
Table created.
SQL> exec dbms_stats.set_table_stats( ownname=>'solarp', tabname=>'R1', numrows=> 100000000, numblks=>251342 ) ;
PL/SQL procedure successfully completed.
SQL> alter table r1 parallel 5 ;
Table altered.
SQL> set autotrace traceonly explain
SQL> update r1 set status='XX' where created > ( sysdate - 7) ;
0 rows updated.
Execution Plan
Plan hash value: 1840129185
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time | TQ |IN-OUT| PQ Distrib |
| 0 | UPDATE STATEMENT | | 5000K| 66M| 14083 (14)| 00:02:49 | | | |
| 1 | UPDATE | R1 | | | | | | | |
| 2 | PX COORDINATOR | | | | | | | | |
| 3 | PX SEND QC (RANDOM)| :TQ10000 | 5000K| 66M| 14083 (14)| 00:02:49 | Q1,00 | P->S | QC (RAND) |
| 4 | PX BLOCK ITERATOR | | 5000K| 66M| 14083 (14)| 00:02:49 | Q1,00 | PCWC | |
|* 5 | TABLE ACCESS FULL| R1 | 5000K| 66M| 14083 (14)| 00:02:49 | Q1,00 | PCWP | |
Predicate Information (identified by operation id):
5 - filter("CREATED">SYSDATE@!-7)
Thanks in advance

The manuals get out of date and out of synch. Somewhere in the 9i manuals it says that there is "limited" support for all parallel DML. Your plan, as David said, is a parallel select with serial update - if you want to perform the update in parallel then you need an explicit:
alter session enable parallel dml;Here's a plan (pulled from v$sql_plan in 10.2.0.3) for a similar update to yours. This plan is the parallel update version:
update t1 set n1 = 0 where mod(id,100) = 0
| Id | Operation             | Name     | Rows | Bytes | Cost (%CPU)| Time     |    TQ |IN-OUT| PQ Distrib |
|   0 | UPDATE STATEMENT      |          |       |       |   753 (100)|          |        |      |            |
|   1 | PX COORDINATOR       |          |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM) | :TQ10000 |   100 |   800 |   753   (0)| 00:00:10 | Q1,00 | P->S | QC (RAND) |
|   3 |    UPDATE             | T1       |       |       |            |          | Q1,00 | PCWP |            |
|   4 |     PX BLOCK ITERATOR |          |   100 |   800 |   753   (0)| 00:00:10 | Q1,00 | PCWC |            |
|* 5 |      TABLE ACCESS FULL| T1       |   100 |   800 |   753   (0)| 00:00:10 | Q1,00 | PCWP |            |
Predicate Information (identified by operation id):
   5 - access(:Z>=:Z AND :Z<=:Z)
       filter(MOD("ID",100)=0)Note, particularly, that the UPDATE operation is the child of the PX SEND to coordinator. i.e. we update in the PX slaves, then tell the co-ordinator what we updated.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

Synchronizing Updates on a Staging Table

Please help me out with the resolving the following issue:
A load script is running for moving records from a data file to a staging table.
After this script completes, there is a code to update two fields of the staging table.
To do this the shell script runs a script (generate_ranges.sql). It takes a parameter of 5000000. It creates ranges based on this passed in number upto the total number of rows in the staging table. So say the staging table has 65,000,000 rows.
This script will create a file that looks like the following (when 5000000 is passed in):
1 | 5000000
5000001 | 10000000
10000001 | 15000000
15000001 | 20000000
20000001 | 25000000
25000001 | 30000000
30000001 | 35000000
35000001 | 40000000
40000001 | 45000000
45000001 | 50000000
50000001 | 55000000
55000001 | 60000000
60000001 | 65000000
The script goes on to read the data file for each row and it calls a shell script and passes in each range. So in this case there are 13 ranges. What is happening is there are 13 seperate updates on the staging table happening in the background.
The first update rows 1 - 5000000, the second rows 5000001 - 10000000 etc.
So there are 13 updates happenng behind the scenes.
The problem is that there is no way for the script to know that all updates are completed successfully before proceeding automatically. Right now I manually check to see that that all updates completed and then I restart the script at the next step. However we want to code to ensure that all the updates are done automatically and then move on in the script. So we need a way to count the number of candidate updates ( right now 13 but could be 14 or more in future) and know that all "x" updates completed, it may be the case that update (1-5000000) is taking 30 mins and the next update ( 5000001 - 10000000) is taking 35 mins, all updates iare running parallely, and only when after the 13 parallel updates are complete, the script can proceed with subsequent steps.
So please help me out with fixing this problem programmatically.
Thanks for your cooperation in advance.
Regards,
Ayan.

Ayan,
Are you really sure you want to update 65 million rows ?
Alternative: create table as select <columns with 2 columns updated> from staging table;
While using this approach, you probably don't need to split the update.
Regards,
Rob.

Issue in Delivery document Status update

Hi ,
We are facing serious issue in delivery document delta extraction via Delivery item Datasource (2LIS_12_VCITM). This leads to incorrect Pending logistic figures in stock and dispatch report. Details for the issue are as follows.
Datasource used : 2LIS_12_VCITM
Issue Description :
The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
Steps taken to rectify the issue
-     We have removed the commit work statement and applied in parallel update task in ECC. Include : ZSD_INCL_DEL_SAVE_FINS
-     Setup tables for Delivery were filled in ECC.
-     Historic data was deleted from the Delivery cube in BW
-     Data was pulled into PSA (Info package u2013 Full Update) from where it was loaded to DSO in overwrite mode (Historic data was not deleted from DSO)
-     Data from DSO to delivery cube was loaded with DTP setting as Full Update.
-     After complete data was updated in Cube the DTP setting were changed to Delta.
-     Delta info package was scheduled for the capturing the document changes from next load.
-     Goods Movement status for all the documents created till this point was exactly similar to the status in ECC.
-     The goods movement status flag (WBSTA) field from the ECC table VBUP is not correctly extracted by the standard deliveries item datasource (2LIS_12_VCITM) during delta loads.
Example              :
                                Delivery document no: 2131260470 is pulled with goods movement status u201CAu201D in firstly load (here BW Delivery status matches
                                    With ECC )
                               Before next delta load status in ECC (WBSTA) changes to u201CCu201D (PGI Complete) along with updated u201CGoods Issue Dateu201D
                               Extractor fails to capture the change in document ,thus status in BW remains as u201CAu201D with no date updated in u201CGoods Issue Dateu201D
                                   field.
Steps for Reconstruction :
1)     Check the value of Goods movement status and actual goods issue date fields in the PSA for the datasource
2LIS_12_VCITM in BW for the sample delivery mentioned in the attached file
2)     Compare these values with the ones in the ECC table VBUP.
Kindly help at the earliest.
Regards,

Hi,
   Could anyone please reply as its quite critical.
many thanks in advance,
regards
pramod.

Finder corrupted after 10.6.8 update

Updated to 10.6.8 and had problems with rolling beach ball and dock not loading at all. Discovvfered incompatibility with having Parallels in the dock and took it out. But in the process of discovery and several hard boots into and out of safe mode, the Finder changed permanently so that the sidebar no longer shoes devices and places etc.. I trashed the Finder .plist file and rebooted, to no avail. even tried replacing the .plist file with a backed up file from before the change, to no avail.
How do I get a functional Finder back?

Ronald,
First I'd download the Parallels update that fixes the problem. (If Parallels is still installed).
Then if the issue persists, trash ~/Library/Preferences/com.apple.sidebarlists.plist
Logoff and Login (or restart the finder). You will probably need to set the options again in Finder > Preferences > Sidebar.
Regards,
Captfred

2011 MBP 13" i7, 10.6.8 update, no issues

So, I bit the bullet and decided to run the 10.6.8 update on
my MBP. All went without a hitch. Reboot after install was
only somewhat longer than usual (typically what I have seen
with past OSX updates). Installed the new Parallels update,
and all is good. My Sony 19". DVI monitor works without
any problems at all.
My procedure was as follows:
1. Booted my system from my clone on a Firewire drive.
2. I used Disk Warrior to do a file scan on the internal drive
    to check for corrupt files.
3. Then used Disk Warrior to scan/repair/rebuild directories
      on the internal drive.
4. Then used Disk Utility to repair permissions on the internal
      drive.
5. Then, rebooted to the internal drive and updated my clone.
      (Wanted to make sure I had a nice clean backup, just in case)
6. Ran the 10.6.8 Combo updater.
At this point, all seems to work well. No issues with external
display, no issues plugging in peripherals.
Also, no printing issues. However, since my HP Laserjet 1022
is plugged into my Airport Extreme, not sure if it that means anything
for those who have had problems.

Next time an Apple employee tells me, "People don't post when they don't have a problem.", I'll be able to say "LIAAAAARRRR!!! LOOK HERE!!!!"

Hint in Update or Select Statement in an inline query ??

Hi ,
I had an update statement that will get the data from the inline select statement,now where can i can keep the hint ,either in update statement or in Select statement...
Please let me know if my sample script is wrong or any better way to approach...Please assume that Salary table had millions of employee's salary records.
update emp
set salary = salary + (select /*+ full(a) parallel(a,4) */ salary from Salary
where experience > 5 and empno = 55 )
where empno = 85Thanks
Rede

You would put the hint in the select statement as you have it, but it won't work until you alias your table name to "a" since that is how you are referencing it in the hint:
update emp
set salary = salary + (select /*+ full(a) parallel(a,4) */ salary from Salary a
where experience > 5 and empno = 55 )
where empno = 85
NOTE I added the "a" right after the Salary table name AND you can only do parallel updates on partitioned table, but the select will run in parallel to at least get the data for you quickly.
To answer your other question about syntax, it is incorrect and there are a lot of ways to write it but a straight forward way would be to use the merge statement
merge into emp e
using (select /*+ full(s) parallel(s,4) */ s.salary from salary s where s.experience > 5) s
on (e.empno = s.empno)
when matched then update
set salary = s.salary;

Parallel query

hi all
I wanted to parallel update a nonpartitioned table . I thought this is in Oracle 11g possible, however the statement runs sequential:
ALTER SESSION ENABLE PARALLEL DML;
UPDATE /*+ PARALLEL (B, 8) */ test b
SET
b.address_1 = NULL,
b.address_2 = NULL
WHERE address_1 IS NOT NULL
OR address_2 IS NOT NULL
UPDATE STATEMENT Cost = 1418 16 MRows 397 MB--ALL_ROWS
UPDATE of 'test'
PX COORDINATOR
PX SEND (QC (RANDOM)) of 'SYS.:TQ10000' 16 MRows 397 MB [P->S]
PX BLOCK (ITERATOR) 16 MRows 397 MB [PCWC]
TABLE ACCESS (FULL) of 'test' (TABLE) 16 MRows 397 MB [PCWP]{B@UPD$1}--ANALYZED
1.
Is this because of the following:
For tables that do not have the parallel DML itl invariant property (tables created before Oracle Database release 9.2 or tables that were created with the COMPATIBLE initialization parameter set to less than 9.2), the degree of parallelism (DOP) equals the number of partitions or subpartitions. That means that, if the table is not partitioned, the query runs in serial. To see what tables do not have this property, issue the following statement:
SELECT u.name, o.name FROM obj$ o, tab$ t, user$ u
WHERE o.obj# = t.obj# AND o.owner# = u.user#
AND bitand(t.property,536870912) != 536870912;
2.
will recreating the table really help this and does the PCTFREE and INITRANS play a part
3.
If my DOP is 6 does it help to recreate my table with initrans set to a value of 6 and above?
Thanks in advance

Hello guru sb92075
your statement is not clear enough for me, but never mind I understand you cannot be bothered to anwser such trival questions clearly.
Any according to a statement from the Oracle documentation it does not clearly state that this is not possible.
For tables that do not have the parallel DML itl invariant property (tables created before Oracle Database release 9.2 or tables that were created with the COMPATIBLE initialization parameter
COMPATIBLE initialization parameter set to less than 9.2), the degree of parallelism (DOP) equals the number of partitions or subpartitions. That means that, if the table is not partitioned, the query runs in serial. To see what tables do not have this property, issue the following statement:
My question is how can I set this itl invariant property?
Thx

Invalid COMMIT WORK in an update function module.

Hi,Experts,
Currently We got a problem for posting PO's GR with t-code MIGO. Our requirement is that can create Delivery by automaitcly after PO's GR is saving. Then I have tailored a program for creating delivery.The program will be triggered in an output type when saving action is done.
Error info is as below
"Calling a COMMIT WORK in an update process is not allowed
because the function modules triggered in a Logical Unit
of Work cannot then be processed correctly."
Any help will be appreciated
Thanks in advance
Richard Zhou

Hi Richard,
First create an implementation for the BADI in se19,
then in any of the methods put break point and run MIGO
You can clearly see in the debugger what all values come
Please note that u have 2 methods
one works in update task and another as normal function module..to view the documentation of the BADI->go to se18 -> enter the name of the BADI -> Display -> click on documentation to View the purpose and use of the BADI you have mentioned,Please note that all BADIs may not have documentations.............
Also if u feel that the replies are helping you out please reward points....this way the SDN members will be willing to do a bit more homework for you and help you out...
To proceed with the BADI
Please check the documentation below
Business add-ins when creating a material document
The enhancement MB_DOCUMENT_BADI has two methods that are called up by the same interface, though at different times. All material document data from the following tables is transferred to this business add-in:
MKPF (material document header)
MSEG (material document items)
VM07M (update data)
This data can be used in other programs, but cannot be changed.
The methods differ according to the time at which they are called up:
The method MB_DOCUMENT_BEFORE_UPDATE is called up before the FI document is created. This means that it is called up even if the program is terminated by an error during the subsequent processing. The update of data in separate tables should always be contained in function modules that are called up with the addition 'in update task'. This ensures that all the data is updated consistently.
The method MB_DOCUMENT_UPDATE is not carried out until update. This means that all updates are carried out immediately in their own tables and do not have to be contained in 'update task' in function modules. For performance reasons, you should not re-read the tables or carry out any time-consuming routines at this point.
You should always call up MB_DOCUMENT_BEFORE_UPDATE before MB_DOCUMENT_UPDATE, particularly if time is a critical factor when posting the material documents. The method MB_DOCUMENT_UPDATE is processed after the FI document numbers are called. As a result, no other FI documents can be posted until this document is completely updated.
Even if the two methods are in the same class, you cannot access the same global fields, as the methods are called up at different times and are therefore carried out in another roll area.
From the business add-in display, you can go to coding examples for both methods by choosing Goto -> Example coding -> Display
Note
The enhancement does not transfer any data to the material document, that is, you cannot change material document data before it is updated.
If this business add-in is not set up properly, it may result in an inconsistency between the documents and the stocks and between the material documents and the accounting documents. Inconsistencies like these may be caused by the following elements in the business add-in:
COMMIT WORK
Remote function call (CALL FUNCTION ... DESTINATION)
Own updates in document tables or stock tables (for example, update in tables MBEW, MARD, MSEG)
The unlocking of data (for example, via DEQUEUE_ALL)
Before the two business add-ins are called up, data is already flagged for the UPDATE. If a COMMIT WORK or a Remote Function Call is transmitted in the enhancement, these are written in the database. If another error occurs after the business add-ins are processed, you cannot carry out a complete ROLL BACK, as the data up to the COMMIT or Remote Function Call has already been written in the database. This can result in an inconsistent status (for example, material document without accounting document), which can only be repaired with considerable cost and effort.
The business add-ins are not suitable for customer-specific updates in the stock tables, as updates like these destroy the standard stock update.
Unlocking the data (for example, via DEQUEUE_ALL) is also critical, as the data that is to be updated is no longer protected from updates from external systems, and inconsistencies can result from parallel updates.
Before you activate an enhancement, check carefully that the business add-in does not contain any critical coding places.
If data inconsistencies have already occurred in your system as a result of the business add-in, remove the critical coding so that it does not cause any further inconsistencies.
Regards
Byju

Parallels update

Similar Messages

Maybe you are looking for