Cannot create logical unit in VMM2012R2, starwind v8

i want to create a logic unit on vmm 2012 r2. i am using starwind v8. the vmm can see the storage pool but when i want to create the logical unit, it appears for 2 sec in the overview and then disappears. when i check the job log's i found this
Error (26135)
Creating storage logical unit VMStorage1 on storage pool ConcretePool_Storage_Flat failed with error code 4 [SM_RC_GENERIC_FAILURE]. Failed: Operation Failed
Recommended Action
Specify valid parameters for creating logical unit.

Ok, Here are some info
I have 2 nodes hyper-v (Win se 2012 r2) with
1- Management interface 192.168.1.0
2- Cluster interface 192.168.2.0
3- Storage Interface 192.168.3.0
4- VM interface
i have SAN ( Starwind v8 ) with
1- Management interface 192.168.1.0
2- Storage interface 192.168.3.0
I have VMM 2012 R2
1- Management Interface 192.168.1.0
I am using physical computers for each node, SAN on real PC with Server 2012 R2.
all nodes are connected to physical Switch (tp link).
when i try to create cluster on VMM for the two nodes, I get the error message above which is mostly about The
Windows Storage Management API. so what should I do.
Here is the last error message I just got
Error (20400)
1 parallel subtasks failed during execution.
Error (26260)
The Windows Storage Management API returned an error code for the requested operation.
Error code: 41006 [SM_RC_DISK_STYLE_MISMATCH]
Recommended Action
For more information about this error code, see the Windows Storage Management API documentation.
Warning (26266)
Virtual Machine Manager will not convert disk to MasterBootRecord as the disk contains one or more partitions. This is done to prevent data loss.
Recommended Action
Either remove existing partitions from disk or change the partition style and retry the operation.
Warning (26266)
Virtual Machine Manager will not convert disk to MasterBootRecord as the disk contains one or more partitions. This is done to prevent data loss.
Recommended Action
Either remove existing partitions from disk or change the partition style and retry the operation.
Warning (26266)
Virtual Machine Manager will not convert disk to MasterBootRecord as the disk contains one or more partitions. This is done to prevent data loss.
Recommended Action
Either remove existing partitions from disk or change the partition style and retry the operation.
Warning (26165)
The volume STARWIND STARWIND Multi-Path Disk Device on host host01.uist.edu is already formatted as NTFS. In order to prevent data loss, the volume has not been formatted.
Recommended Action
To format this volume, use the -ForceFormat parameter, or format the volume manually.
Warning (26165)
The volume STARWIND STARWIND Multi-Path Disk Device on host host01.uist.edu is already formatted as NTFS. In order to prevent data loss, the volume has not been formatted.
Recommended Action
To format this volume, use the -ForceFormat parameter, or format the volume manually.

Similar Messages

VMM error when trying to create logical unit (disk space) as part of the Fabric

This is the error message we get (underneath), has worked fine before, so not sure what has changed.
An internal error has occurred trying to contact the MBSSCVMM.MBS.local server: :a:DestinationUnreachable: :MI RESULT 6:The requested object could not be found..
WinRM: URL: [http://mbsscvmm.mbs.local:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/microsoft/windows/storage/MSFT_StorageSubSystem?ObjectId={1}\\MBSSCVMM\root/Microsoft/Windows/Storage/Providers\EQL_StorageSubSystem.ObjectId="6090A0A8B05C103293E2A4"]
Check that WS-Management service is installed and running on server MBSSCVMM.MBS.local. For more information use the command "winrm helpmsg hresult". If MBSSCVMM.MBS.local is a host/library/update server or a PXE server role then ensure that VMM agent
is installed and running.
ID: 2912
Details: The handle is invalid (0x80070006)

Can you verify that the storage provider is alive and healthy from VMM? A refresh should tell you the details.
Also, please tell a bit more about which storage provider you are using.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Cannot create new virtual network adapter on logical switch team

I am currently moving from Hyper-V 2012 to Hyper-V 2012 R2 and in turn I have just installed SCVMM 2012 R2. I am using SCVMM 2012 R2 to create some NIC teams which I have done no problem in the past with SCVMM 2012 SP1. Now we have everything set up just
like we did in the past and it seems to create the NIC team just fine. The problem is when I try to create a New Virtual Network Adapter, when I click the button, it immediately says:
VMM cannot create the virtual network adapter. Either there are no VM networks associated with the network sites that the uplink port profile "Logical Network Name" Connects to, or the VM networks associated with those network sites all use Hyper-V
network virtualization.
Now I've checked and the VM Network is assigned to the logical network that is associated with the Network Site that contains the host I'm working with. I've also tried disabling Hyper-V network virtualization but that didn't change anything and I thought
that it's always enabled on 2012 R2 anyway.
I would like to gain network connectivity to this team at least for testing purposes and we also are planning on building a Hyper-V cluster. Were some new restrictions added in 2012 R2 to prevent creating virtual network adapters in this scenario or am I
doing something wrong?
Any information would be helpful. Thank you in advance for your time!

Hi Sir,
Glad to hear that the problem has been solved , thanks for your sharing .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Help with Jsp: logic:iterate Cannot create iterator for this collection

Hello,
I am developing a jsp with struts. This is the snap of the code:
        <logic:iterate id="prod" collection="productList" >
          <tr align="center">
               <td><html:text property="prodDesc" size="50" indexed="true"/></td>
               <td>
                    <html:select property="prodUnit" indexed="true">
                         <option selected>-</option>
                        <OPTION VALUE='NMB'>NMB
                         <OPTION VALUE='TEN'>TEN
                         <OPTION VALUE='TPR'>TPR
                         <OPTION VALUE='GWH'>GWH
                    </html:select>
               </td>
               <td><html:text property="prodQty" size="20" indexed="true"/></td>
               <td><html:text property="prodVal" size="20" indexed="true"/></td>
          </tr>
        </logic:iterate>"productList" is defined as an array of Product[], "prod" is defined as a single Product object in the form. But when i run the page, it gives me this errors:
"javax.servlet.jsp.JspException: Cannot create iterator for this collection".
I also tried to make "productList" an ArrayList type, but it game me this same error.
We are using Websphere 4.0 with Struts 1.1.
Anyone can help?
Thanks a lot.
All the best,
warren

Hi , I have similar problem. wonder anyone can help me. I have a datastructure. ArrayList contains list of Hashtable; each Hashtable has two key-value sets ; for each key-value set , value is a ValueObject.
My jsp works ok. but when I click on the radio butten for one radio group, it sets not only the porperty on that row, but the rows belows ,which suppose to be another radio group , because I am using indexed="true". each row should be a individual group seperated by the name poDisplayVO[i] , as show in the html generated .

<logic:iterate id="poDisplayVO"
name="testForm"
property="poDisplayVOList"
type="java.util.Hashtable">
<tr>
<td>
<bean:write name="poDisplayVO" property="name"/>
</td>
<td>
<% String val = ((java.util.Hashtable)poDisplayVO).get("subjAreaName").toString();%>
<html:radio indexed="true" name="poDisplayVO" property="fosVO.select" value="<%=val %>" />
<bean:write name="poDisplayVO" property="subjAreaName"/>
</td>
<td>
<html:radio indexed="true" name="poDisplayVO" property="fosVO.select" value="no" /> NO
</td>
<td>
<html:radio indexed="true" name="poDisplayVO" property="fosVO.select" value="yes" /> YES
</td>
</tr>
</logic:iterate>
<! ------------------------ html genterated ------------------------------------------------>
the HTML generated as folllows:
<tr>
<td>
          Accounting Studies
</td>
<td>
     <input type="radio" name="poDisplayVO[0].fosVO.select" value="Accounting">
          Accounting
</td>
<td>
     <input type="radio" name="poDisplayVO[0].fosVO.select" value="no"> NO
</td>
<td>
     <input type="radio" name="poDisplayVO[0].fosVO.select" value="yes"> YES
</td>
</tr>
<tr>
<td>
          Accounting Studies
</td>
<td>
     <input type="radio" name="poDisplayVO[1].fosVO.select" value="Bookkeeping">
          Bookkeeping
</td>
<td>
     <input type="radio" name="poDisplayVO[1].fosVO.select" value="no"> NO
</td>
<td>
     <input type="radio" name="poDisplayVO[1].fosVO.select" value="yes"> YES
</td>
</tr>
<tr>
<td>
          Accounting Studies
</td>
<td>
     <input type="radio" name="poDisplayVO[2].fosVO.select" value="Computerized Accounting(Duplicate)">
          Computerized Accounting(Duplicate)
</td>
<td>
<input type="radio" name="poDisplayVO[2].fosVO.select" value="no"> NO
</td>
<td>
<input type="radio" name="poDisplayVO[2].fosVO.select" value="yes"> YES
</td>
</tr>
<! ------------------------ action form-----------------------------------------------
public ArrayList getPoDisplayVOList() {
     return poDisplayVOList;
public void setPoDisplayVOList(ArrayList list) {
     poDisplayVOList = list;
public Hashtable getPoDisplayVO(int i) {
     Object obj = poDisplayVOList.get(i);
     if (obj == null)
          obj = new Hashtable();
          poDisplayVOList.add(obj);
     return (Hashtable)poDisplayVOList.get(i);
public void setPoDisplayVO(Hashtable programDisplayVO, int i) {
          poDisplayVOList.add(i, programDisplayVO);
     }

Can I create my own logical unit of work (LUW)?

Good day, everyone!
This is an off-shoot to a Why does the NOCOMMIT parameter not work in HR_INFOTYPE_OPERATION? yesterday in this forum.
It appears that the FM I'm calling is going to do a commit, no matter what. The only thing I can tell is that the NOCOMMIT parameter is used to do a rollback only in the event of a problem.
What I'd like to do is somehow "encapsulate" my call to this function with my own "LUW" designation so that, depending on what a user selects in a selection screen (run as test only? checkbox) I can rollback changes on my own. Unfortunately, I don't know if this is even possible and, if so, how to do it. I need to do something because the end users running this function would like to be able to do a "test run" of all the address transactions to see if there's any errors, data that still needs cleaned up, etc.
Any ideas? Points awarded for all helpful answers, as always.

Hai Dave Packard
Go through the following Link
For Logical database
Logical Unit of Work (LUW)
A Logical Unit of Work (LUW or database transaction) is an inseparable sequence of database operations which must be executed either in its entirety or not at all. For the database system, it thus constitutes a unit.
LUWs help to guarantee database integrity. When an LUW has been successfully concluded, the database is once again in a correct state. If, however, an error occurs within an LUW, all database changes made since the beginning of the LUW are canceled and the database is then in the same state as before the LUW started.
An LUW begins
each time you start a transaction
when the database changes of the previous LUW have been confirmed (database commit) or
when the database changes of the previous LUW have been cancelled (database rollback)
An LUW ends
when the database changes have been confirmed (database commit) or
when the database changes have been canceled (database rollback)
Database commit and rollback
Within an LUW, database changes are not made until after a database commit. Prior to this, any database change can be canceled by a database rollback.
In the R/3 System, a database commit is triggered either automatically or by the ABAP/4 command COMMIT WORK or the appropriate Native SQL command for the database system.
Similarly, a database rollback is triggered either automatically or by the ABAP/4 command ROLLBACK WORK or the appropriate Native SQL command for the database system.
A database commit is triggered automatically by
each screen change, and especially after the ABAP/4 commands CALL SCREEN, CALL DIALOG, CALL TRANSACTION, MESSAGE or
a Remote Function Call
A database rollback is triggered automatically by
errors which occur at runtime or
the ABAP/4 command MESSAGE with the message type 'A'
After each database commit or rollback, the database locks set in the LUW are released (see Database Locking).
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

What is luw (logical unit of work)

pls tell me what is luw (logical unit of work)
what r the types of luw .
2 what ispurpose of code inspector and extended program check
pls expalin the diffrence b/w those two
3what are the candidate keys in db tables
4 what is the difference b/w occurs 1 and occurs 2 clauses
data : begin of itab occurs 0 .
data : itab type standard table of structure type initial size 1 with header line
pls tell diffrence between theese two statements
5can u pls tell what is the client in sap
pls tell answers to questions
pls dont give any websites addresses to see answers
6 what is the transaction from database point of view
7 what is the variant in alv reports
how do we use reuse_alv_grid_variant_get fun module in alvs

hi,
this gives complete idea
SAP LUW
Since, as a rule, an application program is processed by several work processes in succession, and every change of the work process is linked with an implicit database commit , an application program is not automatically linked with a single database LUW. This applies in particular to dialog-oriented applications, in which one database LUW is assigned to one dialog step.
To ensure the data consistency of application programs that are executed across different work processes, the application statements are not directly executed in an SAP LUW, rather, are first registered and then executed by a single work process, that is, in a single database LUW.
Two techniques are available for bundling the change statements in a database LUW:
Bundling via function modules (update)
Through the statement CALL FUNCTION...IN UPDATE TASK, an update function module is registered for subsequent execution in an update work process.
Bundling via function modules (transactional RFC)
Through the statement CALL FUNCTION... IN BACKGROUND TASK DESTINATION, a remote- compatible function module is registered for subsequent asynchronous execution via the RFC interface (transactional RFC ).
Bundling via subprograms
Through the statement PERFORM ... ON COMMIT, a subprogram is registered for subsequent execution in a different work process.
Statements for SAP LUWs
A SAP LUW is controlled via the Open SQL statements COMMIT WORK, ROLLBACK WORK and SET UPDATE TASK LOCAL.
Note
A function module can be classified either as an update function module or remote-compatible, but not both at the same time. The update helps realize SAP LUWs within an SAP System, while the transactional RFC creates LUWs in distributed systems.
COMMIT WORK
Variants:
1. COMMIT WORK [AND WAIT].
2. COMMIT CONNECTION con.
Effect
Terminates an SAP LUW and stores the changes.
Variant 1
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the currenta SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
It triggers an internal event in Object Services that ensures the registration of changes in persistent objects as the last update function module, as well as the subsequent initialization of persistent object attributes.
It initiates the processing of all registered update function modules in the update work process.
This executes all high-priority update function modules registered using CALL FUNCTION ... IN UPDATE TASK in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating). If you specify the addition AND WAIT, however, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
If all high-priority update function modules are completed successfully, the statement executes the low-priority update function modules together in a common database LUW.
In parallel, it also executes the individual function modules registered using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION in a separate database LUW for each destination.
It handles all SAP locks set in the current program according to the value of the formal parameter _SCOPE of the corresponding lock function modules.
It triggers a database commit that also terminates the current database LUW.
The completion of statement COMMIT WORK triggers the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE, where the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>COMMIT_WORK.
If the statement COMMIT WORK is executed by calling special programs, be aware of the following:
In a program executed using batch input, or if you have called the program using the USING addition of the statement CALL TRANSACTION, COMMIT WORK terminates the batch input processing when using the corresponding settings.
In a program called using CALL DIALOG, COMMIT WORK initiates the processing of subroutines or updated function modules registered using PERFORM ... ON COMMIT and CALL FUNCTION ... IN UPDATE TASK. Therefore, it does not complete the current SAP LUW. The SAP LUW cannot be completed until you execute the COMMIT WORK statement in the calling program.
You cannot execute the COMMIT WORK statement during the updating procedure or during the execution of subroutines registered using PERFORM ... ON {COMMIT|ROLLBACK}.
System fields
sy-subrc Meaning
0 You have specified the AND WAIT addition, and the updating of the update function modules was successful.
4 You have specified the AND WAIT addition, and the updating of the update function modules was not successful.
The COMMIT WORK statement always sets sy-subrc to 0 if the AND WAIT addition is not specified.
Note
The COMMIT WORK statement closes all database cursors . Open SQL statements that access a database cursor later ( SELECT loop and FETCH) raise an exception that cannot be handled.
Variant 2
COMMIT CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The COMMIT command is not executed on the standard database, but only on the secondary database connection specified by con. con is the name of the database connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text) - the source_text field contains the name of the database connection. The source_text field must be of the type C or STRING.
On the specified secondary database connection, the database commit:
Closes all open database cursors (OPEN CURSOR)
Releases all database locks
Note
Note that the COMMIT CONNECTION DEFAULT statement unlike COMMIT WORK executes a pure database commit on the DEFAULT connection.
Exceptions
Non-Catchable Exceptions
Cause: COMMIT WORK is not possible in a FORM that was called using PERFORM ... ON COMMIT.
Runtime Error: COMMIT_IN_PERFORM_ON_COMMIT
Cause: COMMIT WORK is not allowed in the update.
Runtime Error: COMMIT_IN_POSTING
ROLLBACK WORK
Variants:
1. ROLLBACK WORK.
2. ROLLBACK CONNECTION con.
Effect
Terminates a SAP-LUW without storing the changes.
Variant 1
ROLLBACK WORK.
Effect
The statement ROLLBACK WORK closes the current SAP-LUW and opens a new one. In doing so, all change requests of the current SAP-LUW are canceled. To do this, ROLLBACK WORK carries out the following actions:
Executes all subprograms registered with PERFORM ON ROLLBACK.
Deletes all subprograms registered with PERFORM ON COMMIT.
Raises an internal exception in the Object Services that makes sure that the attributes of persistent objects are initialised.
Deletes all update function modules registered with CALL FUNCTION ...IN UPDATE TASK from the VBLOG and deletes all transactional remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND TASK from ARFCSSTATE and from ARFCSDATA.
Removal of all SAP locks set in the current program in which the formal parameter _SCOPE of the lock function module was set to the value 2.
Triggers a database rollback, which also ends the current database-LUW.
After completion of the statement COMMIT WORK, the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE is raised, in which the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>ROLLBACK_WORK.
Variant 2
ROLLBACK CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The ROLLBACK-statement is not executed on the standard database but only on the secondary database connection, specified through con. con is the name of the database connection as it was specified in table DBCON in column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), in which the field source_text contains the name of the database connection. The field source_text must be of the type C or STRING.
Notes
As all opened database cursors on the respective database connections are closed at ROLLBACK, the attempt to continue a SELECT-loop after a ROLLBACK, leads to a runtime error. Due to the same reason, a FETCH after a ROLLBACK to the then closed cursor, leads to a runtime error. You have to make sure that cursors that are still open, are no longer used after ROLLBACK.
After execution of the statement ROLLBACK, SY-SUBRC is always equal to 0. It is not necessary to check if SY-SUBRC is unequal to 0 after ROLLBACK.
ROLLBACK must not be used during update (CALL FUNCTION ... IN UPDATE TASK) or during the execution of FORMs, which were registered with PERFORM ... ON COMMIT resp. PERFORM ...ON ROLLBACK.
The statement ROLLBACK WORK is implicitly executed if a message of the type A is treated with the addition ERROR_MESSAGE when calling a function module with CALL FUNCTION.
Exceptions
Non-Catchable Exceptions
Cause: ROLLBACK WORK is not allowed within a FORM that is called with PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK.
Runtime Error: ROLLBACK_IN_PERFORM_ON_COMMIT
Cause: ROLLBACK WORK is not allowed within an update.
Runtime Error: ROLLBACK_IN_POSTING
SET UPDATE TASK LOCAL
Syntax
SET UPDATE TASK LOCAL.
Effect
This statement specifies that the high-priority update function modules - registered during the current SAP LUW using CALL FUNCTION ... IN UPDATE TASK - are registered in the ABAP memory instead of the VBLOG database table. In addition, it specifies that the current work process and not the update work process run these modules during the current database LUW, when the COMMIT WORK statement is executed. This statement has no effect on low-priority update function modules.
At the beginning of every SAP LUW, the local update function is deactivated. If you wish to use it, you must reactivate it again before the first update function module is registered.
System fields
sy-subrc Meaning
0 The local update function is activated.
1 The local update function has not been activated, because the program has already registered at least one update function module for the normal updating procedure in the current SAP-LUW.
Notes
The local update function performs a synchronous update according to the COMMIT WORK statement, independent of the addition AND WAIT.
The occurrence of a database rollback during the local update affects all previous change requests.

RE:logical unit of work

Hi guys,
What do u mean by logical unit of work...Can anyone explain me with an example.
Regards,
Alex.

hi,
this gives complete idea
SAP LUW
Since, as a rule, an application program is processed by several work processes in succession, and every change of the work process is linked with an implicit database commit , an application program is not automatically linked with a single database LUW. This applies in particular to dialog-oriented applications, in which one database LUW is assigned to one dialog step.
To ensure the data consistency of application programs that are executed across different work processes, the application statements are not directly executed in an SAP LUW, rather, are first registered and then executed by a single work process, that is, in a single database LUW.
Two techniques are available for bundling the change statements in a database LUW:
Bundling via function modules (update)
Through the statement CALL FUNCTION...IN UPDATE TASK, an update function module is registered for subsequent execution in an update work process.
Bundling via function modules (transactional RFC)
Through the statement CALL FUNCTION... IN BACKGROUND TASK DESTINATION, a remote- compatible function module is registered for subsequent asynchronous execution via the RFC interface (transactional RFC ).
Bundling via subprograms
Through the statement PERFORM ... ON COMMIT, a subprogram is registered for subsequent execution in a different work process.
Statements for SAP LUWs
A SAP LUW is controlled via the Open SQL statements COMMIT WORK, ROLLBACK WORK and SET UPDATE TASK LOCAL.
Note
A function module can be classified either as an update function module or remote-compatible, but not both at the same time. The update helps realize SAP LUWs within an SAP System, while the transactional RFC creates LUWs in distributed systems.
COMMIT WORK
Variants:
1. COMMIT WORK [AND WAIT].
2. COMMIT CONNECTION con.
Effect
Terminates an SAP LUW and stores the changes.
Variant 1
COMMIT WORK [AND WAIT].
Effect
The statement COMMIT WORK completes the current SAP LUW and opens a new one, storing all change requests for the currenta SAP LUW in the process. In this case, COMMIT WORK performs the following actions:
It executes all subroutines registered using PERFORM ON COMMIT.
It triggers an internal event in Object Services that ensures the registration of changes in persistent objects as the last update function module, as well as the subsequent initialization of persistent object attributes.
It initiates the processing of all registered update function modules in the update work process.
This executes all high-priority update function modules registered using CALL FUNCTION ... IN UPDATE TASK in the order of their registration and in a common database LUW. If you do not specify the addition AND WAIT, the program does not wait until the update work process has executed it (asynchronous updating). If you specify the addition AND WAIT, however, program processing after COMMIT WORK will not continue until the update work process has executed the high-priority update function modules (synchronous updating).
If all high-priority update function modules are completed successfully, the statement executes the low-priority update function modules together in a common database LUW.
In parallel, it also executes the individual function modules registered using CALL FUNCTION ... IN BACKGROUND TASK DESTINATION in a separate database LUW for each destination.
It handles all SAP locks set in the current program according to the value of the formal parameter _SCOPE of the corresponding lock function modules.
It triggers a database commit that also terminates the current database LUW.
The completion of statement COMMIT WORK triggers the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE, where the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>COMMIT_WORK.
If the statement COMMIT WORK is executed by calling special programs, be aware of the following:
In a program executed using batch input, or if you have called the program using the USING addition of the statement CALL TRANSACTION, COMMIT WORK terminates the batch input processing when using the corresponding settings.
In a program called using CALL DIALOG, COMMIT WORK initiates the processing of subroutines or updated function modules registered using PERFORM ... ON COMMIT and CALL FUNCTION ... IN UPDATE TASK. Therefore, it does not complete the current SAP LUW. The SAP LUW cannot be completed until you execute the COMMIT WORK statement in the calling program.
You cannot execute the COMMIT WORK statement during the updating procedure or during the execution of subroutines registered using PERFORM ... ON {COMMIT|ROLLBACK}.
System fields
sy-subrc Meaning
0 You have specified the AND WAIT addition, and the updating of the update function modules was successful.
4 You have specified the AND WAIT addition, and the updating of the update function modules was not successful.
The COMMIT WORK statement always sets sy-subrc to 0 if the AND WAIT addition is not specified.
Note
The COMMIT WORK statement closes all database cursors . Open SQL statements that access a database cursor later ( SELECT loop and FETCH) raise an exception that cannot be handled.
Variant 2
COMMIT CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The COMMIT command is not executed on the standard database, but only on the secondary database connection specified by con. con is the name of the database connection as it was specified in the table DBCON in the column CON_NAME. The database connection con can also be specified dynamically in the form (source_text) - the source_text field contains the name of the database connection. The source_text field must be of the type C or STRING.
On the specified secondary database connection, the database commit:
Closes all open database cursors (OPEN CURSOR)
Releases all database locks
Note
Note that the COMMIT CONNECTION DEFAULT statement unlike COMMIT WORK executes a pure database commit on the DEFAULT connection.
Exceptions
Non-Catchable Exceptions
Cause: COMMIT WORK is not possible in a FORM that was called using PERFORM ... ON COMMIT.
Runtime Error: COMMIT_IN_PERFORM_ON_COMMIT
Cause: COMMIT WORK is not allowed in the update.
Runtime Error: COMMIT_IN_POSTING
ROLLBACK WORK
Variants:
1. ROLLBACK WORK.
2. ROLLBACK CONNECTION con.
Effect
Terminates a SAP-LUW without storing the changes.
Variant 1
ROLLBACK WORK.
Effect
The statement ROLLBACK WORK closes the current SAP-LUW and opens a new one. In doing so, all change requests of the current SAP-LUW are canceled. To do this, ROLLBACK WORK carries out the following actions:
Executes all subprograms registered with PERFORM ON ROLLBACK.
Deletes all subprograms registered with PERFORM ON COMMIT.
Raises an internal exception in the Object Services that makes sure that the attributes of persistent objects are initialised.
Deletes all update function modules registered with CALL FUNCTION ...IN UPDATE TASK from the VBLOG and deletes all transactional remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND TASK from ARFCSSTATE and from ARFCSDATA.
Removal of all SAP locks set in the current program in which the formal parameter _SCOPE of the lock function module was set to the value 2.
Triggers a database rollback, which also ends the current database-LUW.
After completion of the statement COMMIT WORK, the event TRANSACTION_FINISHED of the system class CL_SYSTEM_TRANSACTION_STATE is raised, in which the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>ROLLBACK_WORK.
Variant 2
ROLLBACK CONNECTION con.
Note
This statement is for internal use only.
It cannot be used in application programs.
Effect
The ROLLBACK-statement is not executed on the standard database but only on the secondary database connection, specified through con. con is the name of the database connection as it was specified in table DBCON in column CON_NAME. The database connection con can also be specified dynamically in the form (source_text), in which the field source_text contains the name of the database connection. The field source_text must be of the type C or STRING.
Notes
As all opened database cursors on the respective database connections are closed at ROLLBACK, the attempt to continue a SELECT-loop after a ROLLBACK, leads to a runtime error. Due to the same reason, a FETCH after a ROLLBACK to the then closed cursor, leads to a runtime error. You have to make sure that cursors that are still open, are no longer used after ROLLBACK.
After execution of the statement ROLLBACK, SY-SUBRC is always equal to 0. It is not necessary to check if SY-SUBRC is unequal to 0 after ROLLBACK.
ROLLBACK must not be used during update (CALL FUNCTION ... IN UPDATE TASK) or during the execution of FORMs, which were registered with PERFORM ... ON COMMIT resp. PERFORM ...ON ROLLBACK.
The statement ROLLBACK WORK is implicitly executed if a message of the type A is treated with the addition ERROR_MESSAGE when calling a function module with CALL FUNCTION.
Exceptions
Non-Catchable Exceptions
Cause: ROLLBACK WORK is not allowed within a FORM that is called with PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK.
Runtime Error: ROLLBACK_IN_PERFORM_ON_COMMIT
Cause: ROLLBACK WORK is not allowed within an update.
Runtime Error: ROLLBACK_IN_POSTING
SET UPDATE TASK LOCAL
Syntax
SET UPDATE TASK LOCAL.
Effect
This statement specifies that the high-priority update function modules - registered during the current SAP LUW using CALL FUNCTION ... IN UPDATE TASK - are registered in the ABAP memory instead of the VBLOG database table. In addition, it specifies that the current work process and not the update work process run these modules during the current database LUW, when the COMMIT WORK statement is executed. This statement has no effect on low-priority update function modules.
At the beginning of every SAP LUW, the local update function is deactivated. If you wish to use it, you must reactivate it again before the first update function module is registered.
System fields
sy-subrc Meaning
0 The local update function is activated.
1 The local update function has not been activated, because the program has already registered at least one update function module for the normal updating procedure in the current SAP-LUW.
Notes
The local update function performs a synchronous update according to the COMMIT WORK statement, independent of the addition AND WAIT.
The occurrence of a database rollback during the local update affects all previous change requests.
Regards
vasu

ASM: cannot create asm disks - permission denied

We cannot create ASM disks using the command:
# /etc/init.d/oracleasm creatdisk ASMDISK1 /dev/mapper/mpathdp1
Marking disk "ASMDISK1" as an ASM disk: [FAILED]
The log (/var/log/oracleasm) has the following:
Clearing disk header: done
Disk "ASMDISK1" does not exist or is not instantiated
Writing disk header: done
Instantiating disk: oracleasm-instantiate-disk: Unable to create ASM disk "ASMDISK1": Permission denied
failed
Clearing disk header: done
The command is being executed by the root user. Our environment is OEL6:
[oracle@uxdbidbd1 mapper]$ uname -rm
2.6.32-100.28.11.el6.x86_64 x86_64
To install ASMLib we did the following:
Installed the three packages:
1.oracleasm-support-2.1.4-1.el5.x86_64.rpm
2.oracleasmlib-2.0.4-1.el5.x86_64.rpm
3.oracleasm-2.6.18-238.9.1.el5-debuginfo-2.0.5-1.el5.x86_64.rpm
[root@uxdbidbd1 ~]# modprobe oracleasm
[root@uxdbidbd1 ~]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: oracle
Default group to own the driver interface []: oinstall
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: [ OK ]
Scanning the system for Oracle ASMLib disks: [ OK ]
[root@uxdbidbd1 ~]#
[root@uxdbidbd1 ~]# /etc/init.d/oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
Our SA partitioned the disk using fdisk:
[root@uxdbidbd1 ~]# fdisk -l /dev/mapper/mpathd
Disk /dev/mapper/mpathd: 52.4 GB, 52428800000 bytes
255 heads, 63 sectors/track, 6374 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4849251a
Device Boot Start End Blocks Id System
/dev/mapper/mpathdp1 1 6374 51199123+ 83 Linux
Here are the owner/permissions:
[oracle@uxdbidbd1 mapper]$ ls -al /dev/mapper/
lrwxrwxrwx. 1 root root 7 Apr 22 14:58 mpathd -> ../dm-5
brw-rw-r--. 1 oracle oinstall 253, 6 Apr 25 10:56 mpathdp1
[oracle@uxdbidbd1 dev]$ ls -al /dev
brw-rw----. 1 root disk 253, 5 Apr 22 15:45 dm-5
drwxr-xr-x. 4 root root 0 Apr 22 14:58 oracleasm
[oracle@uxdbidbd1 oracleasm]$ ls -al /dev/oracleasm
total 0
drwxr-xr-x. 4 root root 0 Apr 22 14:58 .
drwxr-xr-x. 23 root root 7200 Apr 24 03:41 ..
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .check_iid
drwxr-xr-x. 1 root root 0 Apr 22 14:58 disks
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .get_iid
drwxrwx---. 1 oracle oinstall 0 Apr 22 14:58 iid
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_disk
-rw-rw----. 1 oracle oinstall 0 Apr 22 14:58 .query_version
We ran an strace on the createdisk command that is failing and I noticed this in the output file:
28830 mknod("/dev/oracleasm/disks/ASMDISK1", S_IFBLK|0600, makedev(253, 6)) = -1 EACCES (Permission denied)
28830 write(2, "oracleasm-instantiate-disk: ", 28) = 28
28830 write(2, "Unable to create ASM disk \"ASMDI"..., 56) = 56
We changed /dev/oracleasm/disks to 777 in order to test but we got the same result. Do we need to adjust the permissions to all of the parent directories in the path (/dev/oracleasm/disks)? I've been looking around for anything related to permissions on /dev/oracleasm but the docs don't mention anything. Any help would be greatly appreciated.

From what I understand, you should not set device permissions of /dev/oracleasm since oracleasm takes care of it according to /etc/init.d/oracleasm configure.
The problem in your case seems to be that ASM refuses to initialize and write metadata to your device. Was the device previously used by ASM? ASM will fail to initialize a device that contains previous ASM metadata. To erase the device you will need to use the dd command, e.g. dd if=/dev/zero of=/dev/sdb. Both ASMLib and raw devices require the candidate disks to be partitioned before they can be accessed. To create a partition on /dev/sdb, for instance, type fdisk /dev/sdb and create a standard partition using the defaults. This will create /dev/sdb1 and you can try oracleasm createdisk again.
You may try the above, but anyway, I was not sure how much you can trust your installation. The problem could also be that you installed the oracleasm kernel driver and asmlib software for OEL 5. Oracle Linux 6 includes an oracleasm kernel driver and as far as I remember you must not install another oracleasm kernel driver. Using modprob oracleasm and installing oracleasm support package using yum should do the trick. You may also need to download and install the asmlib package for the Oracle ASM grid install to see the ASM disks.

Solution Manager EWA - cannot create session in satellite system

"Hi,
I want to configure EWA self service using Solman 4.0. I succesfully did the following :
a. Maintained SMSY and create the required trusted RFC connections from SM to satellite system. All connection and authorization passed in SM59. I used SAP_ALL/SDCCN_ALL role and assigned objects S_RFC*.
b. Assigned the system to a logical system.
c. Created the a new solution and activate "Solutions Monitoring > Earlywatch Alert"
d. Activated and maintained required RFC in SDCCN in satallite system.
My problem is that the create EWA alert request (Red Flag with a specific session number ) coulnd be pass to the satelitte system even though all the trusted RFC and authorization is set. When i execute the SESSION_REFRESH in the satellite system, the session is not created.
Did I miss out any steps. Can any one share any help ?
FYI, there is no connection to SAPOSS yet, so i did not manage to run RTCCTOOL completed, but i doubt this is required for EWA self service."
I have the same problem as Solution Manager EWA - cannot create session in satellite system
tried all of solutions, but it does not help... Created the CM (high) for SAP, but get 1 response for 1 week from them:(

Dear Sapbcer,
Have you tried the following option :
Execute SMSY and from the Server entry Execute the "Read System Data Remote" option in change mode.
Save the data captured and then try using Refresh Session Task from SDCCN of the satellite system. Do select the RFC for Solution Manager while performing this task.
Hope this helps.
Regards
Amit

Creating Logical Networks and Switches via SPF

Hi,
Is it possible to create Logical switches and logical networks in VMM by calling SPF REST APIs. I can see only a GET API for logical networks and none for Logical switches. If they exist can someone point me to a link to the documentation?
Thanks,
Venky

Hi
You can only get logical network information -
http://msdn.microsoft.com/en-us/library/dn470018.aspx
The purpose of SPF is to be used as web service for Tenants. As logical networks and switches are objects that are maintained by administrators they cannot be managed by SPF. Logical networks have get operation because you might want to create VLAN-based
VM Networks depending on what is configured in Logical networks. For administrating logical switches and networks administrators will use PowerShell or the VMM console.

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So e

I have installed Adobe Lightroom CC. In the process of launching, a popup appears, that says: "AN INTERNAL ERROR HAS OCCURRED. Cannot create the required folder: /Users/(my user name)/Library/Application Support/Adobe/Lightroom/Develop Presets." So even though Lightroom CC is installed, it will not launch. What do I need to do to allow it to launch?

The problem was solved today. Here's the full story. I'm a Mac user. At first I installed Lightroom CC on my iMac (desktop). I had this problem so I called Adobe, and was referred to a "special unit" . After about an hour the tech solved it for me ... we did a screen sharing and she took control of my computer for a loooong time. Because of language difficulties, at first I wondered if she knew what she was doing but she eventually solved it. Although she couldn't explain exactly what she was doing, she summarized it by saying "it was a permissions problem." I asked if I would have the same issue later when I installed it on my laptop (Macbook Air). She said probably not.
But I did. The same internal error popup arose on launch and launch did not complete on my laptop. I tried chat but no joy so I eventually called Apple Care. I had noticed that on my laptop (and the iMac for that matter), that there was no Library folder after my user name. The Apple tech explained that the Library folder is actually there but it is hidden because it's very easy for users to do some very nasty things to their computer by going astray while in the Library folder. The folder is actually there, but they hide it. I did remember seeing that the tech helping me with my iMac had typed the work "Library" while she was controlling my computer. Basically she had activated the hidden Library folder so she could open the path that Lightroom was trying to follow to create that "Develop Presets" folder. For some reason, the inability to create that folder in the launch process was preventing launch from being completed. The Apple tech said she didn't actually have to do that and activated the Library folder by use of the Go selection on the menu bar. Anyway, once that complete path was replicated and opened, the next step was to go to the Lightroom Permissions field and add my user name to the user categories already there and enable "read and write" permissions to my user name. Once done, I shut down my laptop, and then rebooted. I launched Lightroom and then boom, voila, heavens to betsy, etc. it launched and suddenly a dismal weekend turned into a great one.
I am not a geek, so I hope this makes some sense. I also hope Lightroom launches again tomorrow and beyond!

BUILD PROGRAM ERROR - CANNOT CREATE PAYMENTS

Hi, I'm trying to run a payment batch using payments manager and encountered this error.
In my test data I used two suppliers that belongs to the same operating unit.
Payments: Version : 12.0.0
Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
IBYBUILD module: Build Payments
Current system time is 09-NOV-2009 11:26:11
**Starts**09-NOV-2009 11:26:11
**Ends**09-NOV-2009 11:26:13
BUILD PROGRAM ERROR - CANNOT CREATE PAYMENTS
Start of log messages from FND_FILE
IBY_PAYGROUP_PUB.performPostHookProcess: Fatal error - Payment count mismatch after hook operation. # payments passed to hook: 1, # payments returning from hook: 2
IBY_PAYGROUP_PUB.performPostHookProcess: Aborting program ..
End of log messages from FND_FILE
Executing request completion options...
Finished executing request completion options.
Exceptions posted by this request:
Concurrent Request for "Build Payments" has completed with error.
Concurrent request completed
Current system time is 09-NOV-2009 11:26:13
Please help
thanks,
Renz

Hi
Please review the below note from Metalink,
Bug No. 6771847
Filed 24-JAN-2008 Updated 13-MAR-2008
Product Oracle Payments Product Version 12.0.4
Platform Linux x86 Platform Version ENTERPRISE 4
Database Version 10.2.0.2 Affects Platforms Generic
Severity Severe Loss of Service Status Closed, Verified by Filer
Base Bug N/A Fixed in Product Version 12.0.4
Problem statement:
R12: AFTER APPLYING 12.0.4 BUILD PAYMENT PROGRAM ERRORS
please review the same if it resolvs your error.
Thanks
Manish Jain.

ORA-12015: cannot create a fast refresh materialized view from a complex qu

BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for Linux: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - ProductionI'm trying to create a fast refresh materialized view that uses a column of xmltype. The problem is I cannot create an MV log that accounts for the xmltype column. I tried excluding it and got the above error. Is there another way I can incrementally update a materialized view where I don't have to do a COMPLETE refresh or use FAST refresh?
CREATE TABLE "DAS_DESC"."AUTHORITY_TEST"
    "NAID"      NUMBER(20,0) NOT NULL ENABLE,
    "AUTH_TYPE" VARCHAR2(40 BYTE),
    "XML_DATA" "SYS"."XMLTYPE" ,
    "TERM_NAME" VARCHAR2(4000 BYTE)
CREATE TABLE "DAS_DESC"."AUTH_ASSC_TEST"
    "NAID"    NUMBER(20,0),
    "P_NAID" NUMBER(20,0),
    "REL_TYPE"    VARCHAR2(25 BYTE),
    "XML_DATA" "SYS"."XMLTYPE"
CREATE
MATERIALIZED VIEW person_mv
AS
SELECT p.naid
      , p.auth_type
      , INSERTCHILDXML
          p.xml_data                 -- Parent XML Column
        , '//*[contains(local-name(), ''person'')]' --XPATH to Person
        , 'nonPreferredHeadingArray'                -- Value for new child element
        (                                                       -- Sub query for injecting new variant person array
          SELECT XMLELEMENT
            "nonPreferredHeadingArray"
          , XMLAGG -- Aggregator for Variant Persons Array
              XMLELEMENT
                "variantPersonName"                    -- Wrapper for each entry in array
              , extract(a.xml_data,'*/*')
          FROM auth_assc_table -- Link table
          WHERE a.p_naid = p.naid
      ) AS XML_DATA
FROM authority p -- Parent table
WHERE p.auth_type = 'Person';The views are created fine and they work perfectly for what we need. The problem is the refresh when we edit the base tables. Ideally, it should take a couple seconds. Right now, it takes a couple minutes. XMLTYPE is one problem and the Complex Query exception is the other. If there is a work-around for fast refresh, please let me know. Greatly appreciated.

jjmdb wrote:
I'm trying to create a fast refresh materialized view that uses a column of xmltype. The problem is I cannot create an MV log that accounts for the xmltype column. I tried excluding it and got the above error. Is there another way I can incrementally update a materialized view where I don't have to do a COMPLETE refresh or use FAST refresh? Besides XMLTYPE column, your MV definition has a subquery which prevents it from being fast refreshable.
I could not find any specific reference in documentation about restriction on XMLTYPE (or CLOB) columns but it seems logical that oracle will not be able to keep track of changes to binary data. What does DBMS_MVIEW.EXPLAIN_MVIEW generate for your MV definition? That should tell you which all conditions (for FAST REFRESH) your MV violates. Since you can not create a MV LOG to include XMLTYPE column, it will not be possible to create a FAST REFRESHABLE MV that includes the XMLTYPE column.
I am afraid there is not much you can do here unless you are prepared to change the way data is stored in your base tables. If you can store data in base tables using standard data types instead of binary/XML storage, you might be able to create a FAST REFRESHABLE MV.

Cannot create billing document due to errors

Hi,
I cannot creat the billing document due to below errors in the error log of VF01.
I ran SDRQ report and cannot detect any inconsistency.
Error Log
4       0025001049 000000 ABEND due to system error
    4       0025001049 000000 Processing cancelled due to inconsistencies in billing quantity.
    4       0025001049 000010 The item has been fully invoiced already
Could you please help.
Thank you & regards,
Harshini.

Hello,
>4 0025001049 000000 ABEND due to system error
Check SAP
Note 77419 - VF076 for billing docs. w. net value unequal zero
Note 976445 - VX02N - Termination due to negative sales order value
Note 770784 - Information on locking problems during availability check
>4 0025001049 000000 Processing canceled due to inconsistencies in billing quantity.
Check SAP
Note 489676 - External billing documents cannot be cancelled due to VF 188
Note 371844 - Correction of incorrect costs
Note 819805 - Lock logic, reversal, status, posting date (5.00)
>4 0025001049 000010 The item has been fully invoiced already
Check the billing reference for Sales doc type (VOV8) for document number 0025001049
Thanks & Regards
JP

Logical unit of work

Hi all,
Can help me regarding LUW(logical unit of work) and its importance in r/3 ?
Thanks and Regards
Ravi

Hai Ravi Charan
There are 3 types of LUW's available in SAP
1)Database Transaction or DBLUW
2)SAP      Transaction or SAPLUW
2)ABAP     Transaction or ABAPLUW
1) DBLUW : when it is called it locks the rows , Update the rows & commit the rows issued by auto Commit
2) SAPLUW : collection of Business reports is called SAPLUW and Issuing the Commit
here UPDATE,INSERT,MODIFY statements are valid
Commit work is given by Developer Side.
3) ABAPLUW : What ever Transaction Code we are creating is called ABAPLUW it is belongs upon Developers
here 3 types of updates available
1) Bundled Updates
2) Un-Bundled Updates
1) Bundled Updates :
    in Bundled Updates all your updates in a single unit of work present in a PERFORM 'XYZ'
PERFORM 'XYZ' on Commit.
here PERFORM-kept in Buffer 'XYZ' this form having all your update statements
Priarities of execution.
Perform xy on comit it will execute first
perform ab on comit it will execute second
I want to change this execution Order
Perform xy on comit Level 2 it will execute second
perform ab on comit Level 1 it will execute First
because it will depends on Level command
Using in Function Modules
Call Function XYZ in Update Task.
Commit work.
In this case it stores in a buffer once encounters the commit statement this will executes from the buffer
so it is an asynchronos method
2) Un Bundled Updates
these are two types
1) Inline Updates
2) Buffered Inline Updates
1) Inline Updates : INSERT,UPDATE
when update statement found in a program then it is called inline update and you should give the 'commit work'after a update statement
inthe inline update if you not issue a commit work the system will automatically issues the commit work.
2) Buffered Inline Updates:
you will buffer all your inline updates and executes after Encounter the 'COMMIT WORK'
100
   XYZ --> we can not roll back here
200
   ABC---> if here is using commit
Thanks & Regards
Sreenivasulu P

Cannot create logical unit in VMM2012R2, starwind v8

Similar Messages

Maybe you are looking for