How to diagnose a hanging process/session?
Hello,
I've got a user that has a stored procedure that (I'm still waiting to get the code from him) he says basically drops a table, then recreates it by a select on another table. He says this only involves tables of about 600 rows.
He has run this numerous times with no problems and it usually completes immediately.
However, since yesterday, he fires this off, and it seems to just sit there hung forever. Even killing it takes a good bit of time.
Strangely enough, this seems to have started happening on all 3 instances on the same box (3 different test environments, all approximately the same) at the same time.
Can someone give me some good steps and suggestions to try to help troubleshoot this?
Thank you,
cayenne
Oracle prevents modification of a procedure under certain conditions.
1) Procedure does DML
2) No COMMIT has been issued.
No session is allowed to change procedure until either COMMIT or ROLLBACK is issued by session that did DML.
In other words, user is blocking himself by invoking multiple sessions & never issuing COMMIT or ROLLBACK.
Edited by: sb92075 on Sep 1, 2009 7:11 AM
Similar Messages
-
Lion 10.7.2 On both mac book pro and iMac, both with Lion 10.7.2, obtain repeated iCal event notifications from calendar or address book. Cannot turn these off. They repeat several times per session and every time computer is used. How to diagnose this?
First, uninstall "SuperTV" (whatever that is) according to the developer's instructions. It isn't working and it's filling the log with noise.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Post the messages logged before the boot, while the system was unresponsive or was failing to shut down. Please include the BOOT_TIME message at the end of the log extract.
Post the log text, please, not a screenshot. If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message. When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
PLEASE DO NOT INDISCRIMINATELY DUMP THOUSANDS OF LINES FROM THE LOG INTO A MESSAGE. If you do that, I will not respond.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful. -
How to reduce buffer busy waits, session hanging due to buffer busy waits
Hi,
How to reduce buffer busy waits, session hanging due to buffer busy waits.
Thanks,
Sathis.When I see through enterprise manager I see lot of
tables with buffer busy waits.
Is there any way by table name we can check the
blocks info.
The simple way is to look at the SQL statement and corresponding table name?
P1=file#, P2=block#. You can extract segment name(table or index) using this info.
Query v$bh like following:
SQL> select file#, block#, class#, objd from v$bh where file# = P1 and block# = P2;
SQL> select object_name from all_objects where object_id = <objd>;See following doc:
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14237/dynviews_1051.htm
Or you can dump block:
SQL> alter system dump datafie <P1> block <P2>;Some excerpts from block dump:
scn: 0x07df.17e70782 seq: 0x01 flg: 0x04 tail: 0x07822301
frmt: 0x02 chkval: 0x61d0 type: 0x23=PAGETABLE SEGMENT HEADER
Map Header:: next 0x00000000 #extents: 1 obj#: 55881 flag: 0x10000000>
Can we do something at table level that will reduce
the waits.
Yes, some methods are known. But before thinking of that, you must verify which block class and which access are involved.
Typo... always. :(
Message was edited by:
Dion_Cho -
How can we correct and process errorrecords in session and call transaction
hai all
how ca we correct and process error records in session and call transaction method . tell me with coding.
Edited by: swamy katta on May 14, 2008 10:25 AM
Edited by: swamy katta on May 14, 2008 10:26 AM
Edited by: swamy katta on May 14, 2008 10:27 AMhi,
Check out the below sample code ...Here are the records are getting posting with call transaction method and a session is getting created with erroreneous records....
REPORT ztest_report
NO STANDARD PAGE HEADING
LINE-SIZE 255
MESSAGE-ID ZRASH.
* Internal Table Declarations *
*--Internal Table for Data Uploading.
DATA : BEGIN OF IT_FFCUST OCCURS 0,
KUNNR(10),
BUKRS(4),
KTOKD(4),
ANRED(15),
NAME1(35),
SORTL(10),
STRAS(35),
ORT01(35),
PSTLZ(10),
LAND1(3),
SPRAS(2),
AKONT(10),
END OF IT_FFCUST.
*--Internal Table to Store Error Records.
DATA : BEGIN OF IT_ERRCUST OCCURS 0,
KUNNR(10),
EMSG(255),
END OF IT_ERRCUST.
*--Internal Table to Store Successful Records.
DATA : BEGIN OF IT_SUCCUST OCCURS 0,
KUNNR(10),
SMSG(255),
END OF IT_SUCCUST.
*--Internal Table for Storing the BDC data.
DATA : IT_CUSTBDC LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*--Internal Table for storing the messages.
DATA : IT_CUSTMSG LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
DATA : V_FLAG1(1) VALUE ' ',
"Flag used for opening session.
V_TLINES LIKE SY-TABIX,
"For storing total records processed.
V_ELINES LIKE SY-TABIX,
"For storing the no of error records.
V_SLINES LIKE SY-TABIX.
"For storing the no of success records.
* Selection screen *
SELECTION-SCREEN BEGIN OF BLOCK B1.
PARAMETERS : V_FNAME LIKE RLGRAP-FILENAME,
V_SESNAM LIKE RLGRAP-FILENAME.
SELECTION-SCREEN END OF BLOCK B1.
* Start-of-selection *
START-OF-SELECTION.
*-- Form to upload flatfile data into the internal table.
PERFORM FORM_UPLOADFF.
* TOP-OF-PAGE *
TOP-OF-PAGE.
WRITE:/ 'Details of the error and success records for the transaction'
ULINE.
SKIP.
* End of Selection *
END-OF-SELECTION.
*-- Form to Generate a BDC from the Uploaded Internal table
PERFORM FORM_BDCGENERATE.
*--To write the totals and the session name.
PERFORM FORM_WRITEOP.
*& Form form_uploadff
* Form to upload flatfile data into the internal table.
FORM FORM_UPLOADFF .
*--Variable to change the type of the parameter file name.
DATA : LV_FILE TYPE STRING.
LV_FILE = V_FNAME.
*--Function to upload the flat file to the internal table.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = LV_FILE
* FILETYPE = 'ASC'
HAS_FIELD_SEPARATOR = 'X'
* HEADER_LENGTH = 0
* READ_BY_LINE = 'X'
* DAT_MODE = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
DATA_TAB = IT_FFCUST
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
NO_AUTHORITY = 6
UNKNOWN_ERROR = 7
BAD_DATA_FORMAT = 8
HEADER_NOT_ALLOWED = 9
SEPARATOR_NOT_ALLOWED = 10
HEADER_TOO_LONG = 11
UNKNOWN_DP_ERROR = 12
ACCESS_DENIED = 13
DP_OUT_OF_MEMORY = 14
DISK_FULL = 15
DP_TIMEOUT = 16
OTHERS = 17
IF SY-SUBRC = 0.
*--Deleting the headings from the internal table.
DELETE IT_FFCUST INDEX 1.
*--Getting the total number of records uploaded.
DESCRIBE TABLE IT_FFCUST LINES V_TLINES.
ENDIF.
ENDFORM. " form_uploadff
*& Form Form_bdcgenerate
* Form to Generate a BDC from the Uploaded Internal table
FORM FORM_BDCGENERATE .
*--Generating the BDC table for the fields of the internal table.
LOOP AT IT_FFCUST.
PERFORM POPULATEBDC USING :
'X' 'SAPMF02D' '0105',
' ' 'BDC_OKCODE' '/00' ,
' ' 'RF02D-KUNNR' IT_FFCUST-KUNNR,
' ' 'RF02D-BUKRS' IT_FFCUST-BUKRS,
' ' 'RF02D-KTOKD' IT_FFCUST-KTOKD,
'X' 'SAPMF02D' '0110' ,
' ' 'BDC_OKCODE' '/00',
' ' 'KNA1-ANRED' IT_FFCUST-ANRED,
' ' 'KNA1-NAME1' IT_FFCUST-NAME1,
' ' 'KNA1-SORTL' IT_FFCUST-SORTL,
' ' 'KNA1-STRAS' IT_FFCUST-STRAS,
' ' 'KNA1-ORT01' IT_FFCUST-ORT01,
' ' 'KNA1-PSTLZ' IT_FFCUST-PSTLZ,
' ' 'KNA1-LAND1' IT_FFCUST-LAND1,
' ' 'KNA1-SPRAS' IT_FFCUST-SPRAS,
'X' 'SAPMFO2D' '0120',
' ' 'BDC_OKCODE' '/00',
'X' 'SAPMF02D' '0125',
' ' 'BDC_OKCODE' '/00',
'X' 'SAPMF02D' '0130',
' ' 'BDC_OKCODE' '=ENTR',
'X' 'SAPMF02D' '0340',
' ' 'BDC_OKCODE' '=ENTR',
'X' 'SAPMF02D' '0360',
' ' 'BDC_OKCODE' '=ENTR',
'X' 'SAPMF02D' '0210',
' ' 'KNB1-AKONT' IT_FFCUST-AKONT,
' ' 'BDC_OKCODE' '/00',
'X' 'SAPMF02D' '0215',
' ' 'BDC_OKCODE' '/00',
'X' 'SAPMF02D' '0220',
' ' 'BDC_OKCODE' '/00',
'X' 'SAPMF02D' '0230',
' ' 'BDC_OKCODE' '=UPDA'.
*--Calling the transaction 'fd01'.
CALL TRANSACTION 'FD01' USING IT_CUSTBDC MODE 'N' UPDATE 'S'
MESSAGES INTO IT_CUSTMSG.
IF SY-SUBRC <> 0.
*--Populating the error records internal table.
IT_ERRCUST-KUNNR = IT_FFCUST-KUNNR.
APPEND IT_ERRCUST.
CLEAR IT_ERRCUST.
*--Opening a session if there is an error record.
IF V_FLAG1 = ' '.
PERFORM FORM_OPENSESSION.
V_FLAG1 = 'X'.
ENDIF.
*--Inserting the error records into already open session.
IF V_FLAG1 = 'X'.
PERFORM FORM_INSERT.
ENDIF.
*--Populating the Success records internal table.
ELSE.
IT_SUCCUST-KUNNR = IT_FFCUST-KUNNR.
APPEND IT_SUCCUST.
CLEAR IT_SUCCUST.
ENDIF.
*--Displaying the messages.
IF NOT IT_CUSTMSG[] IS INITIAL.
PERFORM FORM_FORMATMSG.
ENDIF.
*--Clearing the message and bdc tables.
CLEAR : IT_CUSTBDC[],IT_CUSTMSG[].
ENDLOOP.
*--Getting the total no of error records.
DESCRIBE TABLE IT_ERRCUST LINES V_ELINES.
*--Getting the total no of successful records.
DESCRIBE TABLE IT_SUCCUST LINES V_SLINES.
*--Closing the session only if it is open.
IF V_FLAG1 = 'X'.
PERFORM FORM_CLOSESESS.
ENDIF.
ENDFORM. " Form_bdcgenerate
*& Form populatebdc
* FOrm to Populate the BDC table.
FORM POPULATEBDC USING VALUE(P_0178)
VALUE(P_0179)
VALUE(P_0180).
IF P_0178 = 'X'.
IT_CUSTBDC-PROGRAM = P_0179.
IT_CUSTBDC-DYNPRO = P_0180.
IT_CUSTBDC-DYNBEGIN = 'X'.
ELSE.
IT_CUSTBDC-FNAM = P_0179.
IT_CUSTBDC-FVAL = P_0180.
ENDIF.
APPEND IT_CUSTBDC.
CLEAR IT_CUSTBDC.
ENDFORM. " populatebdc
*& Form FORM_OPENSESSION
* Form to Open a session.
FORM FORM_OPENSESSION .
*--Variable to convert the given session name into reqd type.
DATA : LV_SESNAM(12).
LV_SESNAM = V_SESNAM.
*--Opening a session.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
CLIENT = SY-MANDT
GROUP = LV_SESNAM
HOLDDATE = '20040805'
KEEP = 'X'
USER = SY-UNAME
PROG = SY-CPROG
* IMPORTING
* QID =
EXCEPTIONS
CLIENT_INVALID = 1
DESTINATION_INVALID = 2
GROUP_INVALID = 3
GROUP_IS_LOCKED = 4
HOLDDATE_INVALID = 5
INTERNAL_ERROR = 6
QUEUE_ERROR = 7
RUNNING = 8
SYSTEM_LOCK_ERROR = 9
USER_INVALID = 10
OTHERS = 11
IF SY-SUBRC <> 0.
WRITE :/ 'Session not open'.
ENDIF.
ENDFORM. " FORM_OPENSESSION
*& Form FORM_INSERT
* fORM TO INSERT ERROR RECOED INTO A SESSION.
FORM FORM_INSERT .
*--Inserting the record into session.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
TCODE = 'FD01'
* POST_LOCAL = NOVBLOCAL
* PRINTING = NOPRINT
* SIMUBATCH = ' '
* CTUPARAMS = ' '
TABLES
DYNPROTAB = IT_CUSTBDC
EXCEPTIONS
INTERNAL_ERROR = 1
NOT_OPEN = 2
QUEUE_ERROR = 3
TCODE_INVALID = 4
PRINTING_INVALID = 5
POSTING_INVALID = 6
OTHERS = 7
IF SY-SUBRC <> 0.
WRITE :/ 'Unable to insert the record'.
ENDIF.
ENDFORM. " FORM_INSERT
*& Form FORM_CLOSESESS
* Form to Close the Open Session.
FORM FORM_CLOSESESS .
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN = 1
QUEUE_ERROR = 2
OTHERS = 3.
IF SY-SUBRC <> 0.
ENDIF.
ENDFORM. " FORM_CLOSESESS
*& Form FORM_FORMATMSG
* Form to format messages.
FORM FORM_FORMATMSG .
*--Var to store the formatted msg.
DATA : LV_MSG(255).
CALL FUNCTION 'FORMAT_MESSAGE'
EXPORTING
ID = SY-MSGID
LANG = SY-LANGU
NO = SY-MSGNO
V1 = SY-MSGV1
V2 = SY-MSGV2
V3 = SY-MSGV3
V4 = SY-MSGV4
IMPORTING
MSG = LV_MSG
EXCEPTIONS
NOT_FOUND = 1
OTHERS = 2.
IF SY-SUBRC = 0.
WRITE :/ LV_MSG.
ENDIF.
ULINE.
ENDFORM. " FORM_FORMATMSG
*& Form form_writeop
* To write the totals and the session name.
FORM FORM_WRITEOP .
WRITE :/ 'Total Records Uploaded :',V_TLINES,
/ 'No of Error Records :',V_ELINES,
/ 'No of Success Records :',V_SLINES,
/ 'Name of the Session :',V_SESNAM.
ULINE.
ENDFORM. " form_writeop
* if routeindicator is initial.
* LOOP AT IT_YMMEE00090.
* LV_LENGTH = STRLEN( IT_YMMEE00090-CHANGETYPE ).
* IF SY-TABIX = '1'.
* IF IT_YMMEE00090-CHANGETYPE = 'B' AND LV_LENGTH = 1.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE = 'R' AND LV_LENGTH = 1.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE = 'S' AND LV_LENGTH = 1.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE CA 'BRSCD' AND LV_LENGTH GT 1
* AND LV_LENGTH LE 5.
* ROUTEINDICATOR = 'S'.
* ENDIF.
* ELSE.
* IF IT_YMMEE00090-CHANGETYPE = 'B' AND LV_LENGTH = 1 AND
* ROUTEINDICATOR = 'S'.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE = 'R' AND LV_LENGTH = 1 AND
* ROUTEINDICATOR = 'S'.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE = 'S' AND LV_LENGTH = 1 AND
* ROUTEINDICATOR = 'S'.
* ROUTEINDICATOR = 'S'.
* ELSEIF IT_YMMEE00090-CHANGETYPE CA 'BRSCD' AND LV_LENGTH GT 1
* AND LV_LENGTH LE 5 AND ROUTEINDICATOR = 'S'.
* ROUTEINDICATOR = 'S'.
* ENDIF.
* ENDIF.
* ENDLOOP.
* endif. -
Hi,
I Would like to know how to process sessions.
Regards,
PrasadRefer to these links
<b>Managing Batch Input Sessions</b>
http://help.sap.com/saphelp_46c/helpdata/en/69/c2501a4ba111d189750000e8322d00/frameset.htm
<b>Processing Sessions Automatically</b>
http://help.sap.com/saphelp_46c/helpdata/en/69/c250414ba111d189750000e8322d00/frameset.htm
Regds
Manohar -
How to check hanged process in solaris
Hi every one ...
I have a 10 processes running in my server .. suddenly on process got hanged ..
How can i check the hanged process...is there any specific command or ehat does the notation it shows in prstat command
Thanks in AdvanceFirst, if the process is not showing 0% CPU utilization in prstat, it's not hung, although it may be stuck in an infinite loop. That's actually a significant difference, as an infinite loop is a logic error, whereas getting stuck could be a failure of some type.
To see if it's really hung, you can use the "truss" or "pstack" commands:
truss -p PID &or
pstack PID &where PID is the process ID of the process you want to check. Note the ampersand to background the process. That's because if the process is indeed stuck in an unkillable wait for a kernel lock, your truss or pstack process will also be stuck and unkillable.
The pstack call should just run and return. It will show the current call stack for all threads in the process. Run it several times and see if it changes. The truss call will run as long as the target process is running, and it will show all system calls made by the process. If it doesn't output anything at all the process is running in user space and should still be getting CPU time, or it's stuck. -
How to stop the internal batch session
Hi ,
How to stop the internal batch session, which is triggered from the program.
When I execute the program, there is an batch session, which starts processing in parallel with the program, and causes an error message for the program, so the further process is affected.
I tried finding the session through the Transactions - SM35, SM37. However, I could find any session in my name.
However, when I try thro SM04, I could find an session with the same error message. But I am not able to end the session.
Pleas advise.
Thanks,
cartesian.Go through transaction SM50. In case you have more than one application server (transaction SM51 will show) you can also use SM66 which will show all running processes on all application servers.
With SM50 you will only see the process running if it is running on the same application server you are logged on to.
Mark the process and use menu 'Program/Session - End Session' or 'Process - End with or without Core'
Hope that helps,
Michael -
How to run the Batch input session(SM35) in background thru Report program
Hi Experts,
I am working in one modification report requirement ,the report is Mass upload will update and run the file via batch input session. The client requirement is to implement the report execution in background mode , the batch input session will process automatically (ie. the job runs the batch input session in background and process the session ends).
Currently, the report calls SM35 to write a batch input session and the user manually selects the session and record the transactions.
Once the Transaction enters and the selection-screen inputs are given, then the transaction executed in background mode and all the above batch input process to be implemented.
Please advise and guide me, how to proceed.
I need your guidance to proceed via Call transaction using bdcdata statement, if it can be achieved the requirement.
Thanks & Regards
San.Hi Arabind Prasad,
Thanks for your inputs.
I know the process of the report Execution in background and job steps.
I want the inputs for how to upload thru Batch input session in background job and the session should also processed automatically
Currently the report logic declared like call transaction 'SM35' and skip first screen.Once the report (tcode) executed (not in background) It writes one session in SM35. The user should select the session and process the transaction manually.
The new requirement is, if the report (tcode) executes in background mode...what and how the batch input session should be declared and how it process automatically (like you said mode 'N').
Hope I am clear in my query.
Please advise.
Regards
San.
Edited by: San Learner on Mar 1, 2011 7:16 PM -
How to continue the running process behind the model dialogue box options ?
How to continue the running process behind the model dialogue box options like this
In Updation of K7 user press the Cancel Button
New dialogue box appear with Yes/No options.
But the backend updation is going on... not Pause the updation.
Like this how to do ?
Please provide me code.I don't know, if you mean you have done your form or you have solved the problem.
It's visible your code is only partly reflecting your screenshot, and that's okay to demonstrate the problem you have given a fine example.
As you marked my suggestion as solution this may not be needed anymore, but here's how I modified your code and used a self made QuestionBox instead of messagebox.
The essential part is defining a callback method and letting the QuestionBox call back there. It's not essential I used RAISEEVENT, but it's fine as it has all the behaviour and parameters needed to call back.
Public oTestFrm
oTestFrm=Createobject("MyForm_Model_to_NonModel")
oTestFrm.Show
Define Class MyForm_Model_to_NonModel As Form
onxx = 0
Add Object lbl_DispValue As Label With Top=90, Left = 120, Width = 50, Height=30, Caption=''
Add Object cmd_Start As CommandButton With Top=120, Left = 120, Width = 50, Height=30, Caption='Start'
Add Object cmd_Stop As CommandButton With Top=120, Left = 190, Width = 50, Height=30, Caption='Stop', Enabled =.F.
Procedure cmd_Start.Click
This.Enabled =.F.
Thisform.cmd_Stop.Enabled =.T.
Thisform.onxx = 0
Do While Thisform.onxx < 90000000
DoEvents
Thisform.onxx = Thisform.onxx +1
Thisform.lbl_DispValue.Caption = Transform(Thisform.onxx)
Enddo
This.Enabled =.T.
Thisform.cmd_Stop.Enabled =.F.
Thisform.lbl_DispValue.Caption = ''
Procedure cmd_Stop.Click
* Here, I want NO PAUSE -- (Show running numbers continuously...)
* how to control Model to NonModel in Messagebox.
QuestionBox('Really stop the process', Thisform, 'handleanswer')
Endproc
Procedure handleanswer
Lparameters tlYes
If tlYes && means Stop
Thisform.onxx = 99999999999999999
Endif
Endproc
Enddefine
Procedure QuestionBox()
Lparameters tcMessage, toCaller, tcCallback
If Not Pemstatus(_Screen,"oForms",5)
_Screen.AddObject("oForms","Collection")
Endif
oMsgBox = Createobject("QuestionBoxForm", tcMessage, toCaller, tcCallback)
_Screen.oForms.Add(oMsgBox)
oMsgBox.Show(2)
Endproc
Define Class QuestionBoxForm As Form
Autocenter = .T.
AlwaysonTop = .T.
Minwidth = 200
Add Object label1 As Label With AutoSize=.T., WordWrap =.T.
Add Object cmdYes As CommandButton With Caption = "Yes", Width=40
Add Object cmdNo As CommandButton With Caption = "No", Width=40
Procedure Init()
Lparameters tcQuestion, toCaller, tcCallback
Thisform.label1.Caption = tcQuestion+" ?"
This.AddProperty("oCaller",toCaller)
This.AddProperty("cCallback",tcCallback)
This.Width = Max(This.Minwidth, Thisform.label1.Width)
Thisform.label1.Left = (This.Width-Thisform.label1.Width)/2
This.Height = Thisform.label1.Height+48
This.cmdYes.Left = This.Width/2 - 10 - This.cmdYes.Width
This.cmdNo.Left = This.Width/2 + 10
This.cmdYes.top = Thisform.label1.Height+24
This.cmdNo.top = This.cmdYes.top
Endproc
Procedure cmdYes.Click
#Define clYes .T.
Raiseevent(Thisform.oCaller,Thisform.cCallback,clYes)
Thisform.Release()
Endproc
Procedure cmdNo.Click
#Define clNo .F.
Raiseevent(Thisform.oCaller,Thisform.cCallback,clNo)
Thisform.Release()
Endproc
Enddefine
I didn't yet introduced a timer for counter display updates. As you see the counter hangs a bit, if you mouse over your form, but it is a way of multithreading without using a separate thread and instead keep the rest of the application active by DOEVENTS
in the long running loop code.
Bye, Olaf.
Olaf Doschke - TMN Systemberatung GmbH http://www.tmn-systemberatung.de -
How can we execute the BDC session in error mode through se38 programme
Dear Experts,
How can we execute the BDC session in error mode through se38 programme....
we can execute the session in the below 2 ways
1) Through SM35 we can process the session manually in foreground/Error mode or Background also.
2) through RSBDCSUB (standared Program) we can process the session in back ground.
But i want to process the session in foreground or Error mode..Do we have any standared program for process the session in foreground or error mode.
Please suggest.
Regards,
Bussa.Hi,
SAP was smart enough to provide this little program: RSBDCCTU
Sandra
Edited by: Sandra Rossi, 15 minutes later
Maybe the answer to your question is just to use CALL TRANSACTION ... USING ... (see the example in RSBDCCTU). You can also generate such a program using transaction SHDB -
Lion slow performance due to hanging TCP sessions
After upgrading to 10.7.2 I experienced that Safari and Mail hangs.
After a reboot the problem was gone but occured again after a while.
I found out that a lot of TCP sessions were in the CLOSE_WAIT state.
The affekted deamon was ocspd.
I killed the deamon and it restarted automatically. The problem related to hanging https sessions Safari an Mail was gone.
The problem occurs again and again.
Does someboda have an idea how to solve this issue.
Bellow I listed some output:
Hinkelstein:~ mav$ sudo lsof -i -P | grep CLOSE_WAIT
applepush 372 root 13u IPv4 0xffffff801434e320 0t0 TCP 192.168.10.52:53317->nk11p01st-courier018-bz.push.apple.com:443 (CLOSE_WAIT)
WebProces 3720 mav 16u IPv4 0xffffff802e9ce880 0t0 TCP 192.168.66.154:54481->tls_server.uslendernetwork.com:80 (CLOSE_WAIT)
WebProces 3720 mav 17u IPv4 0xffffff80330fac20 0t0 TCP 172.20.1.73:58913->172.20.5.7:443 (CLOSE_WAIT)
PubSubAge 7794 mav 19u IPv4 0xffffff80344426c0 0t0 TCP 172.20.1.73:59003->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 3u IPv4 0xffffff802f6b84e0 0t0 TCP 172.20.1.73:58847->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 7u IPv4 0xffffff803310d6c0 0t0 TCP 172.20.1.73:59014->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 8u IPv4 0xffffff802e03ba40 0t0 TCP 172.20.1.73:58849->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 9u IPv4 0xffffff802e952c00 0t0 TCP 172.20.1.73:58845->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 10u IPv4 0xffffff8033150fa0 0t0 TCP 172.20.1.73:58850->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 11u IPv4 0xffffff80330f6c00 0t0 TCP 172.20.1.73:58878->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 12u IPv4 0xffffff8034443c20 0t0 TCP 172.20.1.73:58843->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 13u IPv4 0xffffff802e8b0160 0t0 TCP 172.20.1.73:58844->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 14u IPv4 0xffffff80331404e0 0t0 TCP 172.20.1.73:58856->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 15u IPv4 0xffffff802e9b54e0 0t0 TCP 172.20.1.73:58892->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 18u IPv4 0xffffff802e8afa40 0t0 TCP 172.20.1.73:58867->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 19u IPv4 0xffffff802f6bafa0 0t0 TCP 172.20.1.73:58863->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 20u IPv4 0xffffff803317dc20 0t0 TCP 172.20.1.73:58885->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 21u IPv4 0xffffff8033164c20 0t0 TCP 172.20.1.73:58884->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 22u IPv4 0xffffff8033141320 0t0 TCP 172.20.1.73:58871->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 23u IPv4 0xffffff80331396c0 0t0 TCP 172.20.1.73:58874->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 24u IPv4 0xffffff802e9b7160 0t0 TCP 172.20.1.73:58881->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 25u IPv4 0xffffff8033171c00 0t0 TCP 172.20.1.73:58897->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 26u IPv4 0xffffff801434f880 0t0 TCP 172.20.1.73:58918->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 27u IPv4 0xffffff80330f7320 0t0 TCP 172.20.1.73:58877->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 28u IPv4 0xffffff802f6c4880 0t0 TCP 172.20.1.73:58899->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 29u IPv4 0xffffff802e8bac00 0t0 TCP 172.20.1.73:58917->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 30u IPv4 0xffffff803316afa0 0t0 TCP 172.20.1.73:58964->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 31u IPv4 0xffffff8034441160 0t0 TCP 172.20.1.73:58906->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 32u IPv4 0xffffff802e956500 0t0 TCP 172.20.1.73:58985->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 33u IPv4 0xffffff8033172a40 0t0 TCP 172.20.1.73:58905->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 34u IPv4 0xffffff8033106c20 0t0 TCP 172.20.1.73:58935->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 35u IPv4 0xffffff802e9b6a40 0t0 TCP 172.20.1.73:58904->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 36u IPv4 0xffffff8033136c00 0t0 TCP 172.20.1.73:58965->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 37u IPv4 0xffffff8033138880 0t0 TCP 172.20.1.73:58980->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 38u IPv4 0xffffff8033147c00 0t0 TCP 172.20.1.73:58915->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 39u IPv4 0xffffff802e954160 0t0 TCP 172.20.1.73:58966->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 40u IPv4 0xffffff8033138fa0 0t0 TCP 172.20.1.73:58938->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 41u IPv4 0xffffff8033149160 0t0 TCP 172.20.1.73:58933->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 42u IPv4 0xffffff8033103a40 0t0 TCP 172.20.1.73:58939->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 43u IPv4 0xffffff8033142880 0t0 TCP 172.20.1.73:58930->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 44u IPv4 0xffffff80331056c0 0t0 TCP 172.20.1.73:58940->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 45u IPv4 0xffffff8033173fa0 0t0 TCP 172.20.1.73:58937->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 46u IPv4 0xffffff801434dc00 0t0 TCP 172.20.1.73:58941->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 47u IPv4 0xffffff803314fa40 0t0 TCP 172.20.1.73:58992->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 48u IPv4 0xffffff803312ffa0 0t0 TCP 172.20.1.73:58975->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 49u IPv4 0xffffff803314b500 0t0 TCP 172.20.1.73:58981->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 50u IPv4 0xffffff8033104880 0t0 TCP 172.20.1.73:58967->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 51u IPv4 0xffffff80330fa500 0t0 TCP 172.20.1.73:58982->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 52u IPv4 0xffffff802e9cf6c0 0t0 TCP 172.20.1.73:59033->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 53u IPv4 0xffffff8033142160 0t0 TCP 172.20.1.73:58969->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 54u IPv4 0xffffff802e9ccc00 0t0 TCP 172.20.1.73:58989->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 55u IPv4 0xffffff8033149880 0t0 TCP 172.20.1.73:58970->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 56u IPv4 0xffffff802e9b8de0 0t0 TCP 172.20.1.73:59004->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 57u IPv4 0xffffff80331516c0 0t0 TCP 172.20.1.73:58971->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 58u IPv4 0xffffff803317cde0 0t0 TCP 172.20.1.73:58972->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 59u IPv4 0xffffff8034623500 0t0 TCP 172.20.1.73:59023->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 60u IPv4 0xffffff802e03a4e0 0t0 TCP 172.20.1.73:59081->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 61u IPv4 0xffffff803461fc00 0t0 TCP 172.20.1.73:59034->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 62u IPv4 0xffffff803314a6c0 0t0 TCP 172.20.1.73:59042->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 63u IPv4 0xffffff802e9944e0 0t0 TCP 172.20.1.73:59075->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 64u IPv4 0xffffff802e9cda40 0t0 TCP 172.20.1.73:59016->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 65u IPv4 0xffffff803312ea40 0t0 TCP 172.20.1.73:59026->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 66u IPv4 0xffffff8033161a40 0t0 TCP 172.20.1.73:59036->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 67u IPv4 0xffffff80331364e0 0t0 TCP 172.20.1.73:59018->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 68u IPv4 0xffffff80331684e0 0t0 TCP 172.20.1.73:59056->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 69u IPv4 0xffffff8034621fa0 0t0 TCP 172.20.1.73:59019->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 70u IPv4 0xffffff8033173880 0t0 TCP 172.20.1.73:59020->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 71u IPv4 0xffffff802e8b0880 0t0 TCP 172.20.1.73:59035->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 72u IPv4 0xffffff803310cfa0 0t0 TCP 172.20.1.73:59021->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 73u IPv4 0xffffff8033175500 0t0 TCP 172.20.1.73:59067->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 74u IPv4 0xffffff80331794e0 0t0 TCP 172.20.1.73:59022->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 75u IPv4 0xffffff803314e4e0 0t0 TCP 172.20.1.73:59148->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 76u IPv4 0xffffff8033172320 0t0 TCP 172.20.1.73:59052->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 77u IPv4 0xffffff802f6c5de0 0t0 TCP 172.20.1.73:59095->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 78u IPv4 0xffffff803443f4e0 0t0 TCP 172.20.1.73:59064->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 79u IPv4 0xffffff8034443500 0t0 TCP 172.20.1.73:59082->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 80u IPv4 0xffffff8033169320 0t0 TCP 172.20.1.73:59068->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 81u IPv4 0xffffff8034622de0 0t0 TCP 172.20.1.73:59130->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 82u IPv4 0xffffff8034629de0 0t0 TCP 172.20.1.73:59119->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 83u IPv4 0xffffff802e8bba40 0t0 TCP 172.20.1.73:59054->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 84u IPv4 0xffffff8033131500 0t0 TCP 172.20.1.73:59061->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 85u IPv4 0xffffff8033139de0 0t0 TCP 172.20.1.73:59071->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 86u IPv4 0xffffff8033163de0 0t0 TCP 172.20.1.73:59058->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 87u IPv4 0xffffff802e9cd320 0t0 TCP 172.20.1.73:59096->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 88u IPv4 0xffffff8034628fa0 0t0 TCP 172.20.1.73:59084->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 89u IPv4 0xffffff803310a4e0 0t0 TCP 172.20.1.73:59080->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 90u IPv4 0xffffff802e8ba4e0 0t0 TCP 172.20.1.73:59115->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 91u IPv4 0xffffff802e8bec20 0t0 TCP 172.20.1.73:59085->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 92u IPv4 0xffffff802e8bd6c0 0t0 TCP 172.20.1.73:59094->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 93u IPv4 0xffffff802f6bb6c0 0t0 TCP 172.20.1.73:59138->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 94u IPv4 0xffffff802e8b16c0 0t0 TCP 172.20.1.73:59117->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 95u IPv4 0xffffff8033130de0 0t0 TCP 172.20.1.73:59103->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 96u IPv4 0xffffff8033104160 0t0 TCP 172.20.1.73:59134->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 97u IPv4 0xffffff802e954fa0 0t0 TCP 172.20.1.73:59104->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 98u IPv4 0xffffff8033149fa0 0t0 TCP 172.20.1.73:59135->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 99u IPv4 0xffffff803312f880 0t0 TCP 172.20.1.73:59114->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 100u IPv4 0xffffff802e9cc4e0 0t0 TCP 172.20.1.73:59140->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 101u IPv4 0xffffff8034620320 0t0 TCP 172.20.1.73:59150->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 102u IPv4 0xffffff803310ec20 0t0 TCP 172.20.1.73:59120->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 103u IPv4 0xffffff802e9b6320 0t0 TCP 172.20.1.73:59116->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 104u IPv4 0xffffff802e9cfde0 0t0 TCP 172.20.1.73:59126->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 105u IPv4 0xffffff8033131c20 0t0 TCP 172.20.1.73:59127->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 106u IPv4 0xffffff803317aa40 0t0 TCP 172.20.1.73:59183->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 107u IPv4 0xffffff802f6bcc20 0t0 TCP 172.20.1.73:59129->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 109u IPv4 0xffffff8033162fa0 0t0 TCP 172.20.1.73:59144->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 110u IPv4 0xffffff8033144500 0t0 TCP 172.20.1.73:59156->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 111u IPv4 0xffffff802e998500 0t0 TCP 172.20.1.73:59158->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 112u IPv4 0xffffff803312f160 0t0 TCP 172.20.1.73:59154->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 113u IPv4 0xffffff80330f8160 0t0 TCP 172.20.1.73:59185->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 115u IPv4 0xffffff8033174de0 0t0 TCP 172.20.1.73:59177->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 116u IPv4 0xffffff802f6c2c00 0t0 TCP 172.20.1.73:59187->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 117u IPv4 0xffffff803314ade0 0t0 TCP 172.20.1.73:59172->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 118u IPv4 0xffffff8034441880 0t0 TCP 172.20.1.73:59164->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 119u IPv4 0xffffff803317d500 0t0 TCP 172.20.1.73:59179->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 120u IPv4 0xffffff803316a160 0t0 TCP 172.20.1.73:59173->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 121u IPv4 0xffffff80346226c0 0t0 TCP 172.20.1.73:59196->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 122u IPv4 0xffffff802f6c6c20 0t0 TCP 172.20.1.73:59170->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 123u IPv4 0xffffff803310ac00 0t0 TCP 172.20.1.73:59206->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 124u IPv4 0xffffff80331636c0 0t0 TCP 172.20.1.73:59239->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 125u IPv4 0xffffff80331306c0 0t0 TCP 172.20.1.73:59242->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 126u IPv4 0xffffff801434f160 0t0 TCP 172.20.1.73:59215->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 128u IPv4 0xffffff8033144c20 0t0 TCP 172.20.1.73:59208->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 129u IPv4 0xffffff8033102c00 0t0 TCP 172.20.1.73:59209->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 130u IPv4 0xffffff80331604e0 0t0 TCP 172.20.1.73:59233->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 131u IPv4 0xffffff803461f4e0 0t0 TCP 172.20.1.73:59210->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 132u IPv4 0xffffff803313a500 0t0 TCP 172.20.1.73:59211->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 133u IPv4 0xffffff8033150160 0t0 TCP 172.20.1.73:59218->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 135u IPv4 0xffffff802e03e500 0t0 TCP 172.20.1.73:59213->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 136u IPv4 0xffffff80330f8880 0t0 TCP 172.20.1.73:59214->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 137u IPv4 0xffffff8033104fa0 0t0 TCP 172.20.1.73:59241->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 138u IPv4 0xffffff802e8be500 0t0 TCP 172.20.1.73:59234->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 140u IPv4 0xffffff802e9524e0 0t0 TCP 172.20.1.73:59235->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 143u IPv4 0xffffff803314f320 0t0 TCP 172.20.1.73:59237->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 144u IPv4 0xffffff803316bde0 0t0 TCP 172.20.1.73:59225->172.20.5.7:443 (CLOSE_WAIT)
ocspd 7823 root 145u IPv4 0xffffff802e03dde0 0t0 TCP 172.20.1.73:59232->172.20.5.7:443 (CLOSE_WAIT)Hi
Is ther anybody having the same problem?
I still didn't got rid of it. -
How can I implement parallel processing feature in Oracle 9i?
I need to load (and transform) millions of data from Table1 to Table2. How can I speed the process using parallel processing. The server has 4 processors (running on Win2k Advanced server).
Can anyone guide me what are the exact steps required to enable parallel loading. I've already partitioned Table1 into 4 parts.insert /*+ PARALLEL(8) */ into table A select * from table B ;
or alter table A parallel 8 ;
or alter session enable parallel dml ;
Look for PARALLEL on http://tahiti.oracle.com for more infos.
Fred -
How to prolong the bluetooth timeout session on ipad and iphone
how to prolong the bluetooth timeout session on ipad and iphone?
I understannd that the standard timeout setting is 3 mins. what if I want to prolong the connection duration, how should I do?
thanksTo my knowledge, there is no "time out" on a device. A mouse, KB, etc will go into a low power mode after a short period of non-use.
Barry -
I just bought a iTunes card and its not accepting it. It already sent it to the support team and they said they were going to get back to my within 24 hours and i am trying to buy a program in the app store for work. How can I expedite this process?
Has it been 24 hours?
I take it this was a gift card. iTunes Store: Invalid, Inactive, or Illegible codes http://support.apple.com/kb/TS1292 - gift cards
I don't know if this provides an alternative means: https://expresslane.apple.com ; select 'iTunes' in the first column; 'iTunes Store' in the second column
If you are really desperate you could buy the app yourself, then request reimbursement. -
Report to show me how many invoices are being processed by users
Hi,
I am currently working as a Accounts Payable Supervisor and I would like to run a report to show me how many invoices are being processed by users in my team.
Currently I am using Transaction F.98 (Posted Docs by user report), but this report includes posting from intercompany so all users will have duplicate invoices showing on this report.
Is there any other report I could run to get the result I am after?
Many thanks
AlexHello Alex,
You can also use the GL line item report (FBL3N) with the offsetting accounts (for example GR/IR A/c) which would be posted while posting the invoice. You can display the results with User Name and also can create a layout of your own which can be used time and again.
Kind Regards // Shaubhik
Edited by: Shaubhikg on Nov 10, 2010 6:02 AM
Maybe you are looking for
-
Non-central adapter engine not visable in integration builder
ls, I have a pi system and a separate non-central adapter engine. After installing i did all the post actions including the following part: 5.13 Clearing the SLD Data Cache after Installing a Non-central Advanced Adapter Engine When you have installe
-
Search itunes library by account name
i have gathered many songs over the years. often i will get a message saying i can not play a song because i am not authorized. i woud like to clean the library once and for all. how can i search or sort by account name or purchased by?
-
ESS 50.4 supported in nw2004s EP w. 4.7 backend?
On the download page for the ESS business package 50.4, it indicates the portal requirements as follows: 5.0 (SP5 and higher), EP 6.0 (SP0 and higher). We're running EP 7.0 SP 10 - is this a supported platform? Are there detailed instructions on con
-
I am unable to download and print. Can you tell if I have most current download?
I have Adobe but for some reason I have lately been unable to download and print. Can you help ensure I have most current downloads? E mail address: [email address removed by host]. I am registered as a member. Thank You Tom Ryan
-
[LDAP: error code 11 - Administrative Limit Exceeded]
Hi, I am trying to search LDAP and retrieve a attribute (checksecurity) based on the uid (hardcoded the uid), below is the code : <invoke name='getResourceObjects' class='com.waveset.ui.FormUtil'> <invoke name='getLighthouseContext'> <ref>WF_CONTEXT<