PL/SQL calling giving ORA-03106: fatal two-task communication protocol erro
Hi
I am facing some issue when I am calling a Pl/SQL function from Reports Region of APEX page.
Calling of the PL/SQL code is :
declare
v_query varchar2(4000) := null;
begin
SELECT DPSS_TS_SSA_PKG.getuserid('51552','3618') INTO v_query FROM DUAL;
return v_query;
end;
ERROR MSG :
report error:
ORA-03106: fatal two-task communication protocol error
ORA-02063: preceding line from DPSS_EBUST
When I am executing any other function the same way it is working correctly.
Not able to find out why its happening.
Thanks
Deepak
Error: ORA 3106
Text: fatal two-task communication protocol error
Cause: The communication path between Oracle and the user task has stopped.
This is an internal error message not usually issued.
Action: Contact customer support.
Similar Messages
-
ORA-03106: fatal two-task communication protocol erro
Hi,
I have been writing an oracle client application for Linux and I am
getting the error ORA-03106: fatal two-task communication protocol:
fatal two-task communication protocol error".
I am trying to do a Piecewise fetch of long data using
OCIDefineDynamic() and a callback function. The callback is being called
but after setting the buffer information for the data I get an ORA-03106
error.
If I just do this as a normal fetch it works.
Any ideas?Hi,
"Two-task common errors are generally RDBMS related issues, but could be caused by a problem with SQL*Net, or an application (i.e. Pro*C).
ORA-03106
========
Possible reasons for the ORA-03106 errors include:
1) Incompatibilities between the client application and the RDBMS server. For example, version incompatibilities, or a client trying to use a feature not supported by the database kernel.
2) When using database links or gateways.
3) Network or SQL*Net problems.
4) Corruptions.
5) PL/SQL - language related."
For more information, take a look at Note:1012295.102 from Oracle Metalink.
Cheers
Legatti -
ORA-03106: fatal two-task communication protocol e
Hi Experts
I am upgrading my system to Ehp3. When i am doing the upgrade i am getting a error
SQL error 3106 accessing T100S: ORA-03106: fatal two-task communication protocol
error----
Log File:
MEL-SRV-SAP3\sapmnt\trans\log\SAPI-603DTINSAPAPPL.RID
Start import R3TRTABUT100S ...
1 entry for T100S updated (8A 014).
1 entry for T100S updated (8A 015).
1 entry for T100S updated (8B 526).
1 entry for T100S updated (AA 816).
1 entry for T100S updated (FAGL_ORG_UNITS 011).
1 entry for T100S updated (FF 785).
1 entry for T100S updated (FF 788).
1 entry for T100S updated (FIPAY_GTS 001).
1 entry for T100S updated (FIPAY_GTS 002).
1 entry for T100S updated (FIPAY_GTS 003).
1 entry for T100S updated (GA 572).
[dev trc ,00000] Sun May 10 14:34:29 2009 16918558 17.094935
[dev trc ,00000] OCI-call failed with -1=OCI_ERROR 22 17.094957
[dev trc ,00000] SQL error 3106: 'ORA-03106: fatal two-task communication protocol error'
30 17.094987
[dbsloci. ,00000] *** ERROR => Error 3106 in stmt_fetch() from oci_execute_stmt(), orpc=1
46 17.095033
[dbsloci. ,00000] *** ERROR => ORA-3106 occurred when executing SQL stmt (parse error offset=0)
32 17.095065
[dev trc ,00000] sc_p=0000000000297990,no=96,idc_p=0000000000000000,con=0,act=1,slen=137,smax=256,#vars=2,stmt=0000000006662F
43 17.095108
[dev trc ,00000] SELECT /*+ FIRST_ROWS (1) */ TABNAME , VARKEY , DATALN , VARDATA FROM ATAB WHERE TABNAME\
30 17.095138
[dev trc ,00000] = :A0 AND VARKEY = :A1 FOR UPDATE; 16 17.095154
[dev trc ,00000] SELECT /*+ FIRST_ROWS (1) */ TABNAME , VARKEY , DATALN , VARDATA FROM ATAB WHERE TABNAME\
29 17.095424
[dev trc ,00000] = :A0 AND VARKEY = :A1 FOR UPDATE; 16 17.095440
[dbtran ,07512] ***LOG BY4=>sql error 3106 performing SEL on table ATAB [dbtran#11 @ 7512]
5833 17.101273
[dbtran ,07512] ***LOG BY0=>ORA-03106: fatal two-task communication protocol error [dbtran#11 @ 7512]
33 17.101306
[dev trc ,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL' 39 17.101345
RSLT: {dbsl=99, tran=1}
FHDR: {tab='ATAB', fcode=33, mode=2, bpb=0, dbcnt=0, crsr=0,
hold=0, keep=0, xfer=0, pkg=0, upto=0, init:b=0,
init:p=0000000000000000, init:#=0, wa:p=0X00000000014CC570, wa:#=15000}
[dev trc ,00000] dbtran ERROR LOG (hdl_dbsl_error): DbSl 'SEL' 80 17.101425
STMT:
CRSR: {tab='', id=0, hold=0, prop=0x88000, max.in@0=1, fae:blk=0,
con:id=0, con:vndr=5, val=2,
key:#=2, xfer=0, xin:#=0, row:#=0, upto=1, wa:p=0X00000000014CC570}
SQL error 3106 accessing T100S: ORA-03106: fatal two-task communication protocol e
52718 9059062
0 entries from T100S (GLT0 300) deleted.
Please help to resolve the issue
Thanks in AdvanceHi,
check any log in alert log/user trace file as wll as sql net trace file.
it might be problm in shared memory,semaphores ..
Check NLS compatibility.
If u upgraded database also then first time login through single more and run u*...sql as given in read me file.
surendra jain -
File:
e:\pt849-905-R1-retail\peopletools\SRC\PSRED\psred.cppSQL error. Stmt #:
1849 Error Position: 24 Return: 3106 - ORA-03106: fatal two-task
communication protocol error
Failed SQL stmt:SELECT PROJECTNAME FROM PSPROJECTDEFN ORDER
BY PROJECTNAME
Got this error when opening the peopletools application designer 8.49. The same is working fine within the server, but not working from the client's machine.
We can still able to connect to the database & URL
Please help by throwing some lights.
Thanks,
Sarathy KLooks like a SQL error. ARe you able to connect to the database with SQL*Plus ? Probably the Oracle client is badly configured.
Nicolas. -
ORA-03106: fatal two-task communication protocol error
Hello everyone,
we have a problem with one of our table.
the problem occurs when i execute
SQL> select * from t;
select * from t
ERROR at line 1:
ORA-03106: fatal two-task communication protocol error
but i can access the data by giving the column names for the whole table.
also there is nothing wrong with the other tables in the schema.
many thanx in advancefirst of all thanx in advance
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bi
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for IBM/AIX RISC System/6000: Version 10.2.0.1.0 - Productio
NLSRTL Version 10.2.0.1.0 - Production
SQL> select comp_id, version, status from dba_registry;
COMP_ID VERSION STATUS
CATALOG 10.2.0.1.0 VALID
CATPROC 10.2.0.1.0 VALID
OWM 10.2.0.1.0 VALID
JAVAVM 10.2.0.1.0 VALID
XML 10.2.0.1.0 VALID
CATJAVA 10.2.0.1.0 VALID
EXF 10.2.0.1.0 VALID
ODM 10.2.0.1.0 VALID
CONTEXT 10.2.0.1.0 VALID
XDB 10.2.0.1.0 VALID
RUL 10.2.0.1.0 VALID
COMP_ID VERSION STATUS
ORDIM 10.2.0.1.0 VALID
APS 10.2.0.1.0 VALID
XOQ 10.2.0.1.0 VALID
AMD 10.2.0.1.0 VALID
SDO 10.2.0.1.0 VALID
EM 10.2.0.1.0 VALID
but i cannot understand why..
as far as i know, nothing changed. but maybe the other admins:)
as i said i can query all colums in table t without using a *,
also i can use * when i include rowid in the query
select m.*,rowid from t m;
i am very confused now:S -
Spam - ORA-03106: fatal two-task communication protocol
Hi gurus.
I'm having this error always I import a queue.
Before the error I continue with the "import queue" and it goes to the end, no problem.
Could any one help me how to solve this?
Above the abend details.
Runtime Error DBIF_SETG_SQL_ERROR
Database error text........: "ORA-03106: fatal two-task communication protocol
error"
Internal call code.........: "[SETG/GET /INDX_HIER ]"
"DBIF_SETG_SQL_ERROR" C
"SAPLSHI2" or "LSHI2U25"
"STREE_READ_BUFFERED_DATA_GENER"
System environment:
SAP Release.............. "640"
Application server....... "PCINTRA"
Network address.......... "192.168.200.100"
Operating system......... "Windows NT"
Release.................. "5.1"
Hardware type............ "Intel 80686 (Mo"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"
Database server.......... "PCINTRA"
Database type............ "ORACLE"
Database name............ "NWW"
Database owner........... "SAPNWW"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Mar 21 2007 23:47:09"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "175"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Thanks in advance
PauloHi Ben,
i m also getting the same error. we are using ORacle 10.2.2 on Linux.
The problem is that the Updates are not getting processed and are waiting for V2 update process which is processing one of the v2 process for much time and status is running sequential read - VBdata table.
the status of the updates are - v1 processed. Find the error log of SM21 below-
NiConnect Unsuccessful, Return Code: -0003
> Host: ACPLAPP
> Service: sapgw01
Communication error, CPIC return code 020, SAP return code 665
> CPI-C function: CMINIT(SAP)
SQL error 3106 . Work processes in reconnect status
Perform rollback
Work process has left reconnect status
Run-time error "DBIF_SETG_SQL_ERROR" occurred
> Short dump "070828 020442 SAPPRD AMTFINISHING" generated
Transaction Canceled 00 671 ( DBIF_SETG_SQL_ERROR 20070828020442SAPPRD AMTFINISHING0091 )
Perform rollback
Update terminated
> Update key: 46CE6156C66E4997E1000000C0A80107
> Update module: G_PCA_0_POSTING
SQL error 3113 . Work processes in reconnect status
Kindly suggest
Thnx
Kishore -
ORA-03106: fatal two-task communication protocol
Hi,
I am getting this error with the short dump(in ST22) DBIF_SETG_SQL_ERROR.
The details of the dump is also given.
Please help.
Runtime Error DBIF_SETG_SQL_ERROR
Occurred on 12.08.2008 at 08:30:37
SQL error occurred in the database when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
How to correct the error
Database error text........: "ORA-03106: fatal two-task communication protocol
error"
Internal call code.........: "[SETG/GET /VBDATA ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"DBIF_SETG_SQL_ERROR" C
"SAPLSEUAX" or "LSEUAXV01"
"RS_NEW_PROGRAM_INDEX"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "awnts151"
Network address.......... "192.168.10.33"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "8x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 10
Short dump setting....... "full"
Database server.......... "AWNTS151"
Database type............ "ORACLE"
Database name............ "DEE"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 23 2008 21:48:04"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "239"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 999
User................ "AIL_DEV"
Language key........ "E"
Transaction......... "SE38 "
Program............. "SAPLSEUAX"
Screen.............. "RSM13000 3000"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPLSEUAX" in
"RS_NEW_PROGRAM_INDEX".
The main program was "RSM13000 ".
The termination occurred in line 27 of the source code of the (Include)
program "LSEUAXV01"
of the source code of program "LSEUAXV01" (when calling the editor 270).
The program "SAPLSEUAX" was started in the update system.
Source code extract
000010 *******************************************************************
000020 * THIS FILE IS GENERATED BY THE FUNCTION LIBRARY. *
000030 * NEVER CHANGE IT MANUALLY, PLEASE! *
000040 *******************************************************************
000050 FORM RS_NEW_PROGRAM_INDEX USING %_KEY.
000060 * Parameter declaration
000070 DATA %_P0000000001 TYPE
000080 PROGRAM
000090 .
000100 DATA %_P0000000002 TYPE
000110 PROGRAM
000120 .
000130 DATA: %_STATE.
000140 * Assign default values
000150 * Get mode for update task
000160 CALL 'GET_SWITCH_UTASK'
000170 ID 'MODE' FIELD 'S'
000180 ID 'STATE' FIELD %_STATE.
000190 IF %_STATE EQ 'N'.
000200 * Import from memory
000210 IMPORT
000220 P_NAME TO %_P0000000001
000230 P_INCLUDE TO %_P0000000002
000240 FROM MEMORY ID %_KEY.
000250 ELSE.
000260 * Import from logfile
IMPORT
000280 P_NAME TO %_P0000000001
000290 P_INCLUDE TO %_P0000000002
000300 FROM LOGFILE ID %_KEY.
000310 ENDIF.
000320 * Call update task
000330 CALL FUNCTION 'RS_NEW_PROGRAM_INDEX'
000340 EXPORTING
000350 P_NAME = %_P0000000001
000360 P_INCLUDE = %_P0000000002
000370 .
000380 ENDFORM.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 1 SY-DBCNT 1
SY-FDPOS 0 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Update control
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
5 FORM RS_NEW_PROGRAM_INDEX
SAPLSEUAX
LSEUAXV01 27
4 FORM VB_CALL_FUNC
RSM13000
RSM13000 5441
3 FORM VB_V1_EXEC
RSM13000
RSM13000 5182
2 FORM VB_V1_NORMAL
RSM13000
RSM13000 3944
1 MODULE (PBO) VBEXEC
RSM13000
RSM13000 3793
Chosen variables
5 FORM RS_NEW_PROGRAM_INDEX
SAPLSEUAX
LSEUAXV01 27
%_DUMMY$$
2222
0000
%_STATE Y
5
9
RSJOBINFO 00000000
2222222222222222222222222222222233333333
0000000000000000000000000000000000000000
... + 40 000000
3333332222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 ####
0000
0000
%_KEY 2CF93538B4E949608CAEF68FCB839DA0####
344333334343333334444334443334430000
236935382459496083156686328394101000
SY-SUBRC 0
0000
0000
SYST-REPID SAPLSEUAX
5454545452222222222222222222222222222222
310C355180000000000000000000000000000000
%_P0000000001
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
%_P0000000002
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
%_VIASELSCR #
0
4
SY-REPID SAPLSEUAX
5454545452222222222222222222222222222222
310C355180000000000000000000000000000000
4 FORM VB_CALL_FUNC
RSM13000
RSM13000 5441
SAVE_VBPARAM #
0
3
VBPARAM 2CF93538B4E949608CAEF68FCB839DA00001RS_N
3443333343433333344443344433344333335554
23693538245949608315668632839410000123FE
... + 40 EW_PROGRAM_INDEX AIL_DEV 99
4555544544544445222222222244454452222233
57F02F721DF9E458000000000019CF4560000099
... + 80 9### ##
3000222222222222222222222222222220022222
9612000000000000000000000000000001100000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222
0000000000000000000
VBHDR-VBTCODE SE38
54332222222222222222
35380000000000000000
VBHDR-VBREPORT RS_CALL_PROGRAMM_INDEX_DELTA
5554444555445444544445544454222222222222
23F31CCF02F721DDF9E458F45C41000000000000
VBMODCNT 1
0000
1000
DLDE DLDE
4444222222222222222222222222222222222222
4C45000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VBPARAM-VBPHASE 538968577
0
1
VB_V1_TEST #
0
2
SYST-REPID RSM13000
5543333322222222222222222222222222222222
23D1300000000000000000000000000000000000
HGEN HGEN
4444222222222222222222222222222222222222
875E000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
IS_A_ARFC #
0
0
TH_TRUE #
0
1
OFFICE_TASO00 SO00
5433222222222222222222222222222222222222
3F00000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
TH_FALSE #
0
0
VBSTAT-START2_REQ
222222222222222
000000000000000
EWST EWST
4555222222222222222222222222222222222222
5734000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
BACK BAC
4442222222222222222222222222222222222222
2130000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
TFDIR RS_NEW_PROGRAM_INDEX SAPLSEUAX
5554455554454454444522222222225454545452
23FE57F02F721DF9E4580000000000310C355180
... + 40 0100000000
2222222222222222222222222222223333333333
0000000000000000000000000000000100000000
... + 80 1
22222222222223
00000000000001
TFDIR-PNAME SAPLSEUAX
5454545452222222222222222222222222222222
310C355180000000000000000000000000000000
VBFUNC RS_NEW_PROGRAM_INDEX
555445555445445444452222222222
23FE57F02F721DF9E4580000000000
%_DUMMY$$
2222
0000
VBID 2CF93538B4E949608CAEF68FCB839DA0####
344333334343333334444334443334430000
236935382459496083156686328394101000
VBDEBUG 538976258
0
2
VB_UPDATE_MODUL_PROCESSED #
1
C
3 FORM VB_V1_EXEC
RSM13000
RSM13000 5182
ROLE_SUBST_ACTIVE 3
3
3
VBMOD_TABL-VBMODE 1
3
1
VB_COLLECTOR_FB 5
3
5
SY-REPID RSM13000
5543333322222222222222222222222222222222
23D1300000000000000000000000000000000000
LISL LISL
4454222222222222222222222222222222222222
C93C000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
EXISTS_COLLECTOR #
0
0
VB_V1_FB 1
3
1
VB_V1_NO_UPD_AGAIN_FB 3
3
3
VBHDR-VBSTATE 826605823
F
F
VB_V1_PROCESSED #
0
1
VB_V1_AND_V2_PROCESSED #
0
2
SYST ########################################
0000000000000000000000000000000000000000
0000000010001000000000000000000000000000
... + 40 ####################u0161###############H###
0000000000000000000090000000000000004000
10000000100000001000A0000000000000008000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
... + 120 ########################################
0000000000000000000000000000000010009000
00000000000000000000000000000000B0000000
... + 160 ############XM## ############# E0 3
0000000000005400220000000000000222432223
0000000000008D00000020000C0000C000500003
... + 200 000 N ####__S 999
3332222222420000555222222222222222223332
0000000000E00000FF3000000000000000009990
... + 240 00
222223322222222
000000000000000
MTAS MAS
4452222222222222222222222222222222222222
D130000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VBMOD_TABL-VBKEY 2CF93538B4E949608CAEF68FCB839DA0
34433333434333333444433444333443
23693538245949608315668632839410
VBMOD_TABL-VBFUNC RS_NEW_PROGRAM_INDEX
555445555445445444452222222222
23FE57F02F721DF9E4580000000000
VBMOD_TABL-VBMODCNT 1
0000
1000
LOC_VBPARAM-VBPHASE 538968577
0
1
LOC_VBPARAM-VBDEBUG 538976258
0
2
READ READ
5444222222222222222222222222222222222222
2514000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
EXISTS_V2 #
0
0
SPACE
2
0
NEW_VBSTATE 0
0
0
OBJA OBJA
4444222222222222222222222222222222222222
F2A1000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
OFFICE_TASO18 SO18
5433222222222222222222222222222222222222
3F18000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
USER_NOT_EXIST 34
2000
2000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
SY-XFORM
222222222222222222222222222222
000000000000000000000000000000
2 FORM VB_V1_NORMAL
RSM13000
RSM13000 3944
VBHDR-VBCLIINFO #
0
0
VB_SYNC_VB #
0
1
%_ARCHIVE
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240
222222222222222
000000000000000
SY-MSGID
22222222222222222222
00000000000000000000
ROOM_TAPP30 PP30
5533222222222222222222222222222222222222
0030000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
ADMI ADM
4442222222222222222222222222222222222222
14D0000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
SY-MSGNO 000
333
000
NOTE_NOT_ADDED 11
0000
B000
SY-MSGV1
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV2
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV3
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
SY-MSGV4
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 40
2222222222
0000000000
LOGO LOG
4442222222222222222222222222222222222222
CF70000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VBHDR 2CF93538B4E949608CAEF68FCB839DA0999AIL_D
3443333343433333344443344433344333344454
2369353824594960831566863283941099919CF4
... + 40 EV RS_CALL_PROGRAMM_INDE
4522222222222222222555444455544544454444
560000000000000000023F31CCF02F721DDF9E45
... + 80 X_DELTA SE38
5544454222222222222543322222222222222222
8F45C41000000000000353800000000000000000
... + 120
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 160 ÿ###awnts151_DEE_00
22222222222222222222F0006767733354445332
00000000000000000000F00017E43151F455F000
... + 200
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 240 :E:
222222223432222
00000000A5A0000
1 MODULE (PBO) VBEXEC
RSM13000
RSM13000 3793
VB_V1_NORMAL #
0
1
%_SPACE
2
0
STOP RET
5452222222222222222222222222222222222222
2540000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
RSUP RSUP
5555222222222222222222222222222222222222
2350000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
USPR USPR
5555222222222222222222222222222222222222
5302000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VB_V2_NORMAL #
0
3
ENTER ENTR
4455222222222222222222222222222222222222
5E42000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
USAD USAD
5544222222222222222222222222222222222222
5314000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VB_MAIL #
0
4
INBO INB
4442222222222222222222222222222222222222
9E20000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
PAGP PAGP
5445222222222222222222222222222222222222
0170000000000000000000000000000000000000
... + 40
222222222222222222222222222222
000000000000000000000000000000
VB_AUTO_SYS_START #
0
5
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "expInpDb " of the SAP
Basis System, specifically in line 4364 of the module
"//bas/640_REL/src/krn/runt/abexpo.c#14".
The internal operation just processed is "IMPO".
The internal session was started at 20080812083037.
Internal call code.........: "[SETG/GET /VBDATA ]"
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=5484)
When : 8/12/2008 8:30:37.808
Threads : 2
Computer Name : AWNTS151
User Name : SAPSERVICEDEE
Number of Processors: 8
Processor Type: x86 Family 6 Model 15 Stepping 11
Windows Version : 5.2 Current Build: 3790
Stack Dump for Thread Id 1578
eax=00000201 ebx=0000040c ecx=00000210 edx=009c35fa esi=0000040c edi=00000000
eip=7c8285ec esp=0410cd10 ebp=0410cd80 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c8285ec c3 ret
7c8285ed 8da42400000000 lea esp,[esp] ss:0410cd10=7c827d0b
7c8285f4 8d642400 lea esp,[esp] ss:2571bd23=????????
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0410cd80 77e61c8d 0000040c 0001d4c0 00000000 0410cdb8 ntdll!KiFastSystemCallRet
0410cd94 00f6a44d 0000040c 0001d4c0 00000001 7c3ad8c8 kernel32!WaitForSingleObject
0410cdb8 0054011a 00540153 7c3ad8c8 7c3ad8c8 7c3ad8c8 disp+work!NTDebugProcess >
>
0410cdbc 00540153 7c3ad8c8 7c3ad8c8 7c3ad8c8 01778db4 disp+work!NTStack >
>
0410cdd8 00540187 7c3ad8c8 00000000 008224b3 7c3ad8c8 disp+work!CTrcStack2 >
>
0410cde4 008224b3 7c3ad8c8 00040000 41305f59 30303030 disp+work!CTrcStack >
>
0410ce00 008259e9 02079620 0472a370 00000000 00000000 disp+work!rabax_CStackSave >
>
0410d2a0 007a00f8 01223708 012755fc 0000110c 018ac020 disp+work!ab_rabax >
>
0410d30c 00725113 00000001 01223708 0000110c 018ac020 disp+work!ab_setgerr >
>
0410d36c 007ac556 0410d498 0410d49c 00000000 00000000 disp+work!expInpDb >
>
0410e618 007278d3 00000003 00000000 00000000 00000000 disp+work!ab_connread >
>
0410e69c 0072a3a9 00000001 00000000 00000000 00000000 disp+work!ab_expvb >
>
0410e6d4 0067334a 00000003 516c9cf0 00000000 0410e73c disp+work!expo_import >
>
018ac020 2f2f203a 2f736162 5f303436 2f4c4552 2f637273 disp+work!ab_extri >
>
64492420 00000000 00000000 00000000 00000000 00000000
0668ffb8 77e64829 04f7feb0 00000000 00000000 04f7feb0 MSVCR71!endthreadex
0668ffec 00000000 7c3621a4 04f7feb0 00000000 00000000 kernel32!GetModuleHandleA
List of ABAP programs affected
Type
Program
Gen. Date Time
Load Size
Prg
RSM13000
19.05.2007 19:22:41
242688
Prg
SAPMSSYD
05.06.2002 17:09:33
16384
Prg
SAPFSYSCALLS
14.02.2002 14:22:47
6144
Typ
VBHDR
09.11.2000 14:25:09
5120
Typ
VBMOD
08.08.1995 14:49:58
2048
Typ
TFDIR
29.07.1998 19:49:08
3072
Typ
TFDIR
29.07.1998 19:49:08
3072
Prg
SAPLSEUAX
19.05.2007 19:03:05
8192
Typ
SYST
04.12.2000 14:54:51
27648
Typ
VBPARAM
30.03.1998 09:43:02
4096
Typ
VBSTAT
07.05.1997 13:20:30
9216
Typ
VBMOD
08.08.1995 14:49:58
2048
List of internal tables
No dump information available
Directory of Application Tables
Program
Name................ Contents....1........2........3........4........5....+....
RSM13000
SYST |000000000000x01000000000000000
VBHDR |2CF93538B4E949608CAEF68FCB839DA0999AIL_DEV
VBPARAM |2CF93538B4E949608CAEF68FCB839DA00001RS_NEW_PROGRAM_INDEX
VBSTAT |0
TFDIR |RS_NEW_PROGRAM_INDEX SAPLSEUAX
SAPLSEUAX
RSJOBINFO | 00000000000000
Directory of Application Tables (Administrative Information)
Program
Name.......................... Time.......... Length...
SAPLSEUAX
SYST 00002404
VBHDR 00000432
VBPARAM 20000323224119 00000179
VBSTAT 00000736
TFDIR 00000094
SAPLSEUAX
RSJOBINFO 00000084
ABAP control blocks CONT
Include Line source code
Index Name F1 Co Par01 Par2. Par3. Par4. Tabl
LSEUAXV01 19 IF %_STATE EQ 'N'.
61 cmp1 00 42 0020
63 BRAF 02
LSEUAXV01 21 IMPORT
64 TCHK 04 15
66 CLEA 00
67 XDAT 90
69 XDAT 91 03 C000
71 XDAT 91 03 C001
LSEUAXV01 25 ELSE.
73 BRAX 00
LSEUAXV01 27 IMPORT
74 TCHK 07 15
76 IMPO 04 02 0000
80 PAR2 06 C000
82 PAR2 06 C001
>>>>> IMPO 05 0000
LSEUAXV01 33 CALL FUNCTION 'RS_NEW_PROGRAM_
88 FUNC 00
89 FUNC 00
90 PAR2 02 C001
92 PAR2 02 C000
94 FUNC 10
95 FUNC FF
LSEUAXV01 38 ENDFORM.
96 ENDF 00
End of runtime analysis
Please help.
Regards,
siddharthaHi Guys,
Thanks for the reply!!
To SriHari,
Just to get the insight of the problem am posting it in the forum.Sometimes, it need not be an oracle issue instead it may be an Kernel issue. I did not know which sort of issue as i am new to Basis. Sorry if i have done anything wrong and against the ethics of this forum. Please pardon.
To Fidel Vales,
1) I have installed 10.2.0.2 patch which is available in the service marketplace.
i have not installed the OPatch
2) My kernel version is 239 (SAP R/3 4.7)
3) The env variables are give beolow.
DBMS_TYPE=ORA
DBS_ORA_SCHEMA=SAPR3
dbs_ora_tnsname=DEE
NLS_LANG=AMERICAN_AMERICA.WE8DEC
NUMBER_OF_PROCESSORS=8
ORACLE_HOME=D:\ORACLE\DEE\102
ORACLE_SID=DEE
OS=Windows_NT
Path=C:\Perl\bin\;D:\oracle\DEE\102\jre\1.4.2\bin\client;D:\oracle\DEE\102\jre\1
.4.2\bin;C:\Program Files\EMC\PowerPath\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDO
WS\System32\Wbem;C:\Program Files\Dell\SysMgt\RAC5;C:\Program Files\Dell\SysMgt\
oma\bin;C:\Program Files\Dell\SysMgt\oma\oldiags\bin;C:\Program Files\EMC\Navisp
here CLI;C:\Program Files\Resource Kit\;D:\Oracle92\Opatch;D:\Oracle92\Opatch;d:
\oracle\DEE\102;D:\usr\sap\DEE\sys\exe\run;D:\Oracle\DEE\102\BIN;d:\oracle92;d:\
oracle92\bin;D:\usr\sap\DEE\sys\exe\run;
SAPARCH=E:\oracle\DEE\saparch
SAPBACKUP=E:\oracle\DEE\sapbackup
SAPCHECK=E:\oracle\DEE\sapcheck
SAPDATA_HOME=E:\oracle\DEE
SAPEXE=D:\usr\sap\DEE\SYS\exe\run
SAPLOCALHOST=awnts151
SAPREORG=E:\oracle\DEE\sapreorg
SAPTRACE=E:\oracle\DEE\saptrace
SAPTRANSHOST=AWNTS151
TNS_ADMIN=D:\usr\sap\DEE\sys\profile\ORACLE
USERDNSDOMAIN=AUDCO9.AILVALVES.COM
USERDOMAIN=AUDCO9
USERNAME=deeadm
USERPROFILE=C:\Documents and Settings\deeadm
USE_KIT=OFF
4) Since there is no application server i have not installed oracle client.
5) Kernel version is 640.
Please help.
Thanks and regards,
siddhartha. -
ORA-03106: fatal two-task communication protocol error USING INFORMATICA
Hi,
We are testing Oracle 10203 with linux using INFORMATICA 8.1.1
The user who run the informaica is getting the following error , after runing query against a remote database.
READER_12_1_1> RR_4035 SQL Error [
ORA-03106: fatal two-task communication protocol error
(Please note that informatica is not using db links to open a connection against a remote db).
The informatica client is installed on the same machine as the oracle database and they are using the same oracle client (e.g: 10203)
I also set a trace in the sqlnet.ora at server side and at the client side.
No error regarding ora-3106 was generated in the trace files.
I also added: alter system set events '3106 trace name errorstack level 10', but nothing writthen to the trace file.
Any suggestion ?
Thanks.Error: ORA 3106
Text: fatal two-task communication protocol error
Cause: The communication path between Oracle and the user task has stopped.
This is an internal error message not usually issued.
Action: Contact customer support.
====================================================
Unfortunately the error text doesn't lie, this error is difficult to catch. You may search metalink's knowledge base for possible reasons,but there are many. And, since this is a 3rd party application, I would ask INFORMATICA (not Oracle), do they certify against 10g? Sometimes simply the application is not ready for the used Oracle version.
Werner -
InitialLOBFetchSize causes ORA-03106: fatal two-task communication protocol
After my previous problem with setting InitialLOBFetchSize to -1 (see {thread:id=2338611}) I worked with a setting of 5 KB. This works fine on our development and testing database (11.2.0.1.0 Windows x86).
But on the database of our customer (11.2.0.1.0 Windows x64) some queries throw an "ORA-03106: fatal two-task communication protocol error" exception. This is completely reproduceable, selecting some specific rows work, but others don't work. I've also tried a value of -1 on the customers database, this seems to fail on the same rows, but with a different error: "ORA-03149: Invalid Oracle error code".
Interestingly, the first exception (ORA-03106) is only thrown if I also set a value to FetchSize (I'm currently using 1 MB for that). If I don't modify FetchSize the app just freezes (seems like the query call never returns). But setting the FetchSize doesn't change the behaviour of InitialLOBFetchSize with a value of -1 (always ORA-03149).
I'd really like to use InitialLOBFetchSize (either with a positive value of about 5 KB or with -1) because this brings a huge performance increase for queries that select many CLOBs. Why causes this setting so many problems? Are there any known solutions?
I'm using ODP.NET 11.2.0.3.0 x86 with .NET 4.0.
Edited by: user12301043 on 21.03.2012 01:32In case someone tracks this thread, here is an update:
The problem on the customer database was caused by the "DB_SECUREFILE=ALWAYS" setting. Oracle Support has now created a bug report for it (Bug 14279250). -
EJB Error: ORA-03106: fatal two-task communication protocol error
after weblogic running some time,my program often throw this Exception:
javax.ejb.EJBException: ejbLoad: ORA-03106: fatal two-task communication
protocol error
at
com.ebao.life.ejb.entity.customer.CustomerBean.ejbLoad(CustomerBean.java:206
at
weblogic.ejb.internal.EntityEJBContext.load(EntityEJBContext.java:160)
at
weblogic.ejb.internal.EntityEJBContext.afterBegin(EntityEJBContext.java:217)
at
weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
t.java:165)
at
weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at
com.ebao.life.ejb.entity.customer.CustomerBeanEOImpl.getData(CustomerBeanEOI
mpl.java:105)
at
com.ebao.life.bean.newbizgroup.entry.code.CodeBean.entry(CodeBean.java:120)
at
com.ebao.life.servlet.newbizgroup.entry.code.CodeEntryServlet.doPost(CodeEnt
ryServlet.java:39)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
I use weblogic 5.1 sp10,Redhat Linux 6.2,and JDK 1.3
and the sp9 is the same.I think there are too many bugs weblogic sp9 and later.
There are many strange jdbc error in these service pack
"Narinder" <[email protected]> wrote:
It seems like the connection to the oracle database is lost for no reason.
What is the oracle database server and the jdbc driver you are using?
Most
of the time this happens because the jdbc driver is not compatible with
the
oracle server.
-Narinder
"jason" <[email protected]> wrote in message
news:[email protected]..
after weblogic running some time,my program often throw this Exception:
javax.ejb.EJBException: ejbLoad: ORA-03106: fatal two-task communication
protocol error
at
com.ebao.life.ejb.entity.customer.CustomerBean.ejbLoad(CustomerBean.java:206
at
weblogic.ejb.internal.EntityEJBContext.load(EntityEJBContext.java:160)
at
weblogic.ejb.internal.EntityEJBContext.afterBegin(EntityEJBContext.java:217)
at
weblogic.ejb.internal.StatefulEJBObject.getContextForInvoke(StatefulEJBObjec
t.java:165)
at
weblogic.ejb.internal.BaseEJBObject.preInvoke(BaseEJBObject.java:476)
at
com.ebao.life.ejb.entity.customer.CustomerBeanEOImpl.getData(CustomerBeanEOI
mpl.java:105)
at
com.ebao.life.bean.newbizgroup.entry.code.CodeBean.entry(CodeBean.java:120)
at
com.ebao.life.servlet.newbizgroup.entry.code.CodeEntryServlet.doPost(CodeEnt
ryServlet.java:39)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:772)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at
weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:120)
I use weblogic 5.1 sp10,Redhat Linux 6.2,and JDK 1.3
and the sp9 is the same. -
Help about "ORA-03106: fatal two-task communication protocol error"
Hello.
After having changed some functions written in pro*C, I am getting "ORA-03106: fatal two-task communication protocol error", in the functions I have changed (all of them).
Can someone tell me what the problem can be ?
Tahnks in advance.The problem seems to be in pro*C code:
My pro*C function is like this:
int CSRIRDB_checkGT(char* in_CO_GT_V,
char* out_SQ_GZL_01)
int var_Error = CSRIRDB_OK;
char var_Sqlerrmc[2000];
char var_msg[512]; /* 512 es la longitud máxima del mensaje oracle incluyendo saltos de línea */
size_t var_buf_len, var_msg_len;
/* and the error is beacuse the following assignment */
:out_SQ_GZL_01 := to_char(v_SQ_GZL_01);
/* where v_SQ_GZL_01 is a NUMBER(5) */
I don't know what I'm doing wrong. -
ORA-03106: Fatal Two Task Communication Protocol Error due to multilanguage
1) I have installed oracle 10.2 with multi language support enabled Unicode (AL32UTF8) on windows 2003 Server.
2) Forms 6i installed on same machine but Form close immediately after Database connection.
3) In Net8 Easy Config following error appear "ORA-03106: Fatal Two Task Communication Protocol"
4) If I reinstall database without multi language support, Forms run and connect successfully.Forms 6i does not support multi language support enabled Unicode(UTF-8)
and unicode character has to take a long word size where form6i word's length is less
thats why the message is coming as Two Task Communication Protocol because the same protocol
is used for both database as well as for form6i and database is capable of taking unicode characters
whereas the forms 6i is not able to perform the same. -
ORA-3106 : fatal two-task communication protocol error
We get the following error intermittantly in our server. We are using WebLogic 6.1. Any reason. Here is the log we are getting...
Parsing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6, :7, :8)
; END;
Executing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6, :7, :8
) ; END;
SQLException: SQLState() vendor code(3106)
java.sql.SQLException: ORA-03106: fatal two-task communication protocol error
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:240)
at weblogic.jdbc.oci.Statement.executeUpdate(Statement.java:990)
at weblogic.jdbc.oci.Statement.execute(Statement.java:1430)
at ...ORA-03106
========
Possible reasons for the ORA-03106 errors include:
1. Incompatibilities between the client application and the RDBMS server.
For
example, version incompatibilities, or a client trying to use a feature not
supported by the database kernel.
2. When using database links or gateways.
3. Network or SQL*Net problems.
4. Corruptions.
5. PL/SQL - language related.
RDBMS - Troubleshooting two-task common errors
==============================================
1. Check for NLS incompatibilities between the client and server. This is
a very popular cause of the ORA-03106 error.
2. Check the alert log and RDBMS trace files for any pertinent information /
errors that coincide with receiving the ORA-03106 error.
3. Try to get a testcase and reproduce the problem in-house.
4. If a testcase is not possible, ask for SQL*Net trace files, SQL traces,
and
try setting event 3106 to obtain the error stack.
5. In extreme circumstances, this could indicate that a shared memory
segment
used by Oracle is corrupted. You will have to shut down the database,
possibly using the abort option. Make sure all semaphores have been
released by using the IPCS command on Unix. Oracle uses semaphores to
control concurrency between all of the background processes (pmon, smon,
drwr, lgwr, and oracle shadow processes). Semaphores are also used to
control Two-Task communication between the user process and the shadow
process.
6. Try and narrow down the code that may be causing it. For example it might
have started to happen after increasing the number of parameters in a PL/SQL
block or when using certain values for bind variables, etc.
7. If we still do not make headway, file a bug under RDBMS, but we still may
need some or all of the above information as indicated above
hope it helps!!
"Prasanna" <[email protected]> wrote in message
news:[email protected]...
We get the following error intermittantly in our server. We are usingWebLogic 6.1. Any reason. Here is the log we are getting...
>
Parsing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6,:7, :8)
; END;
Executing: BEGIN gid_msg_fund.fund_get_details (:1, :2, :3, :4, :5, :6,:7, :8
) ; END;
SQLException: SQLState() vendor code(3106)
java.sql.SQLException: ORA-03106: fatal two-task communication protocolerror
at weblogic.db.oci.OciCursor.getCDAException(OciCursor.java:240)
at weblogic.jdbc.oci.Statement.executeUpdate(Statement.java:990)
at weblogic.jdbc.oci.Statement.execute(Statement.java:1430)
at ... -
Fatal two-task communication protocol error (when using db link)
I have created the db link betwen two databases of oracle version 9i 9.0.2
the db link connects to specific user
when i access the table with same name as user then recieve following message
ORA-03106: fatal two-task communication protocol error
when i access the other tables having different name that the user to which the db link connects
that works alright
so what is solution of problem in this particular case?What is your Oracle release? Is it 9.0.1.2 or 9.2.0?
What version of Sql*Plus client are you using? -
Two task communication protocol error
I have a Database Data block. I want to i retrieve the records
with execute query and save the item after changes. when i do
this for the second time connection between ORacle Server and
Forms Runtime is last. Message comming is Two task communication
protocol error. Also the runtime exits.
I need help very urgently as the project is held up because of
this.
SriniI wrote a class for the Oracle 8 OCI calls in php3...I'm not having any problems with php and Oracle...if anyone is interested in the class, email me ([email protected]) and i'll send you the code...it makes traversing a recordset very easy...
$rs = new CData("user","pwd","sid","domain");
$sql = "select col_a, col_b from table";
if ($rs->GetRecordset($sql)) {
while (!$rs->REOF()) {
echo $rs->Val("COL_A")."<br>";
echo $rs->Val("COL_B")."<p>";
$rs->MoveNext();
$rs->MoveFirst();
echo $rs->Val("COL_B");
$rs->MoveNext();
echo $rs->Val("COL_A");
$rs->MovePrevious();
echo $rs->Val("COL_A");
$rs->MoveLast();
echo $rs->Val("COL_B");
echo $rs->RowCount();
echo $CurrentRow();
$sql = "delete from table";
if (!$rs->Execute($sql)) {
echo "Error: ".$rs->err_num.$rs->err_msg;
...you get the picture...
Maybe you are looking for
-
How to parse if input by user is a int or a string.
EDIT: First issue has been fixed, now i'm trying to figure out how to make the program look at the user input. There where the user should input a number (E.G. What is you're first guess line, etc). I want the program to reconize when the input is NO
-
This computer is no longer authorized for purchased items that are on this iPad
Dear all, I already authorize this computer but still pop out this messages. Please help me to solve it, thanks.
-
Sending the enhanced Infotype 0002 outside SAP via an IDOC
Hello Friends, We have added couple of Z fields to the standard 0002 Iinfotype table PA0002. I can see the custom fields in the trans : PA30 screen for infotype 002. Now, we want to send these custom fields value outside SAP via an IDOC. Here are the
-
Exchange : Sycnro Mail - Iphone. No mail account in Itunes.
Hello, I have created an Exchange account on Mail. ( Address Book + iCal OK ) When I plug my iPhone I can't see this account on Itunes, so i can't use the syncro. Any ideas ?
-
Samsung Galaxy 5 touchscreen doesn't work after software update
I updated the new software for my Galaxy 5 today and now have no touchscreen capability. I can't even power it off.