HttpUtils deprecated URGENT (upgradation websphere 4.0 to 5.1)

for this code,
String reqURL= new String(HTTPUtils.getRequestURL(request));
i am getting the following warnigs,
Java compile: the method getRequestURL(HTTPServletRequest) from the type HttpUtils is deprecated.
JavaCompile : The type HttpUtils is deprecated
i also tried replacing HTTPUtils.getRequestURL(request) with HttpServletRequest.getRequestURL(request));
but i getting erroe like,
the method getRequestURL() in the type HTTPServletRequest is not applicabille for the argumnets(HTTPServletRequest)
please help me
thanks and regards
sojanjohn

see reply here:
http://swforum.sun.com/jive/thread.jspa?threadID=45683&tstart=0

Similar Messages

Urgent:Upgrade JRE 1.1.7 to 1.3 for Weblogic 4.5.1

Hi!
I have Weblogic 4.5.1 running on JRE 1.1.7,SPARC Solaris 2.6 platform.I need to upgrade the JRE to 1.3.I am given to understand that there are no issues about this w.r.t Weblogic(see http://www.weblogic.com/platforms/index.html#solaris).But I have conflicting reports that W 4.5.1 will not work with JRE 1.3.Please advise on this as soon as possible.It's urgent and I do not have the time to experiment.You could reply to [email protected]
Best regards,
Venkatesh

Venkatesh,
There should not be any issues with running WLS 4.5.1 with SunSoft SDK
1.3.0. This is a certified configuration.
BEA recommends using this SDK with Sun Microsystems SPARC with Solaris
2.6 and 2.7.
Hope this helps
Raj Alagumalai
Venkatesh B wrote:
Hi!
I have Weblogic 4.5.1 running on JRE 1.1.7,SPARC Solaris 2.6 platform.I need to upgrade the JRE to 1.3.I am given to understand that there are no issues about this w.r.t Weblogic(see http://www.weblogic.com/platforms/index.html#solaris).But I have conflicting reports that W 4.5.1 will not work with JRE 1.3.Please advise on this as soon as possible.It's urgent and I do not have the time to experiment.You could reply to [email protected]
Best regards,
Venkatesh

VERY URGENT:Upgrade To Netweavers From 3.0B version

HI ALL,
We are currently planning to Upgrade TO SAP Netweavers 2004 (BI).Our Current version is 3.0B.Now We are planning about the preupgrade Activities.As far as the upgrade plan is concerned ,Our client is currently only concerned about Technical upgrade and the rest about using the new technology will be planned later while we finish the technical upgrade.I have already gone through various Links in SDN .But ,I have certain Questions ,So i would like to have specific answers from you.Also ,I want to know about the sizing requirements.?
1.1 what space SAP says is required to do Minimize Downtime
1.2) cpu & memory
2) Add requirements such as GUI ---Netweaver GUI???
3)What is the minimum support pack level that should be applied before we upgrade to Sap Netweavers and what is the latest support pack level?
4) what are the plugins that need to be installed?
5) what is meant by database upgrade (Database & SAP Kernel upgrade) and system upgrade and what do we need to do?
6)What is Regression testing?
7)what is meant by SPAU list review?
8) what do u mean by Prepare Run and what are the activities that are done in this phase and what are Pre Prepare Phase Activities?
9)What is external IGS server with v3.0B?
Please take some time out and help me in this regard.Points will be assigned.This is very urgent for me.
I also want to know ,approximately ,what is the time taken to complete the technical upgrade?
Regards,
Samir

can you give me personnel Mail Id..?
Hence i can send the document to you.
Regards
Saravanan.ar
Message was edited by:
Saravanan Raju

Urgently Upgrade Stop In XPRAS_UPG Phase

Hi all,
This is our infrastructure:
Windows 2000
Oracle 9.2.0.7
SAP 4.6B
Kernel Release 46D
We are upgrading our DEV System to R/3 Enterprise 4.7 Ext. 2 Sr1
Our Upgrade Process Stop in the XPRAS_UPG Phase. Basically it gives this error:
WARNING: tp terminated with status 12
R3up> ERROR: tp terminated with error status -1
R3up> ERROR: 2 errors detected during XPRAS_UPG
R3up> ERROR: 1 activities have been aborted in XPRAS_UPG
R3up> ERROR: Operation(s) not completely processed.
 Remaining change request found in buffer TVD.
 Ignoring aborted import steps will cause severe inconsistencies
Logs that we reviewed:
XPRASUPG.ECO and R3up.ECO
the problem is with the RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
 22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17

The conversion of some code pages is not supported.
What happened? 
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
 An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
 'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X u00F0####u00CCu00FF#,").
Please Some help!
We saw this note:
122597 Ignoring errors in the phase XPRAS
So we try with the option "u00CFgnore" + "Repair Severe Errors" but nothing happens, in remains in the same place, Start the Phase a again and Stop at the same point.
676135 Short Dump when you import Support Packages
This notes explain this: (Page 3 Paragraph 3)
If you are still upgrading, import the transport order into the system using 'R3trans -i <data file name>'. Enter the correct path to the data file (possibly DIR_PUT).
But we are scared about to STOP the upgrade here (Like 'cancel' option instead of continue and after restart the upgrade) does somebody apply this note?
This are the logs:
XPRASUPG.ECO
LIST OF ERRORS AND RETURN CODES *******
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
XPRA ERRORS and RETURN CODE in SAPR620ZF1.TVD
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1AETR012XProgram terminated (job: "RDDEXECL", no.: "10593502")
Long text:
 Cause
 Program "&V#&", which was started in the background, was terminated
 abnormally.
 System Response
 The system created a job log for the terminated program.
 What to do
 Proceed as follows:
 Log onto the system in which the program was executed. The system is
 specified at the beginning of the transport log.
 Then call transaction SM37 to display the job log.
 Enter "&V#&" as job name and "DDIC" as user name.
 Restrict the starting date to the starting date specified in the
 transport log.
 For the other selection criteria, select only jobs with the status
 "cancelled". Then press <LS>Execute</>.
 A list of the jobs satisfying the selection criteria is displayed.
 You can display the log by pressing <LS>Job log</>.
 If the list contains several jobs, you can select the job with the ID "
 &V#&" with <LS>Display</> -> <LS>Job details</> or define further
 details for the selection criteria in the initial screen of transaction
 SM37.
 If the ABAP processor reports cancellation, double-clicking on the
 corresponding message in the job log branches to the display of the
 corresponding short dump.
1AEPU320 See job log"RDDEXECL""10593502""TVD"
1 ETP111 exit code : "12"
>>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<
XPRAs are application reports that run at the end of an upgrade.
Most XPRA reports have a report documentation that explains what
the report does and how errors can be corrected.
Call transaction se38 in the SAP system, enter the report name,
select 'Documentation' and click the 'Display' button.
>>> The problematic XPRAs are mentioned in messages of type PU132 above <<<
R3up.ECO:
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15160 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022101802
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 16400 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Deleting file D:\usr\sap\put\tmp\upalert.log
Copying file D:\usr\sap\put\bin\XPRASUPG.TPP to D:\usr\sap\put\bin\AKKU.TMP
Copying file D:\usr\sap\put\buffer\TVD to D:\usr\sap\put\buffer\AFTXPRAS.BUF
Phase XPRAS_UPG:
Deleting file D:\usr\sap\put\log\CONNECT.LOG
R3up> Starting subprocess tp.exe with id 4196 at 20071022105721
EXECUTING D:\usr\sap\TVD\SYS\exe\run\tp.exe pf=D:\usr\sap\put\bin\XPRASUPG.TPP put TVD
Environment: dbs_ora_schema=SAPR3
Environment: dbs_ora_tnsname=TVD
Environment: NLS_LANG=AMERICAN_AMERICA.WE8DEC
Environment: ORACLE_HOME=D:\oracle\TVD\920
Environment: ORACLE_SID=TVD
This is D:\usr\sap\TVD\SYS\exe\run\tp.exe version 340.16.37 (release 640)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter DBCONFPATH is no longer used.
Looking for effective putsteps ... ... ready (looking for putsteps)
STARTSAP continues...
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
D:\usr\sap\TVD\SYS\exe\run\sapevt.exe=>sapparam(1c): No Profile used.
stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
tp returncode summary:
TOOLS: Highest return code of single steps was: 12
WARNS: Highest tp internal warning was: 0118
tp finished with return code: 12
meaning:
A tool used by tp aborted
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
ERROR: stopping on error 12 during EXECUTION OF REPORTS AFTER PUT
Process with ID 15096 terminated with status 12
Deleting file D:\usr\sap\put\log\XPRASUPG.ELG
Moving file D:\usr\sap\put\log\PROT.TMP to D:\usr\sap\put\log\SAPR620ZF1.TVD
Moving file D:\usr\sap\put\log\XPRASUPG.ELG to D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\tmp\MSGIN.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LST
Deleting file D:\usr\sap\put\tmp\MSGOUT.LOG
Deleting file D:\usr\sap\put\tmp\XPRASUPG.ELG
Deleting file D:\usr\sap\put\log\TP.ECO
Deleting file D:\usr\sap\put\bin\TRLIST.DMP
Best Regards,
Desiree Cardenas

Hi Eric,
In fact in the previous post you can see:
the problem is with the
RDDEXECL JOB. Which is in the status CANCELED
When we Check the JOB LOG it gives this:
22.10.2007 10:59:35 Job started
22.10.2007 10:59:35 Step 001 started (program RDDEXECL, variant , user ID DDIC)
22.10.2007 10:59:35 All DB buffers of application server vensapd were synchronized PU
22.10.2007 11:01:17 ABAP/4 processor: CONVT_CODEPAGE_INIT
22.10.2007 11:01:17 Job cancelled 00
When you click on ABAP/4 processor: CONVT_CODEPAGE_INIT you get this:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure "READ_TEXTLINES" "(FORM)".
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the
LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
Sorry for the big amount of information. I will put the complete JOB LOG.
LOG:
Runtime errors CONVT_CODEPAGE_INIT
Exception CX_SY_CODEPAGE_CONVERTER_INIT
Occurred on 22.10.2007 at 11:01:17
The conversion of some code pages is not supported.
What happened?
The conversion of texts in code page '1800' to code page '1100' is not
supported here.
The running ABAP program 'SAPLSTXD' had to be terminated, since conversion
could cause incorrect data to be generated.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that 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.
If the application required you to enter a code page, you may be able to
avoid the error by restarting the application and entering a different
code page.
You can display the available codepages using the transaction SCP. For
more utilities for codepages, use the transaction SNLS.
Error analysis An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_CODEPAGE_CONVERTER_INIT', was neither
caught nor passed along using a RAISING clause, in the procedure
"READ_TEXTLINES" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
One of the two code pages, '1800' or '1100' may be unknown to the system.
It may be that a Unicode code page was specified for a file in the LEGACY MODE. This is not permitted.
It is possible that additional parameters for the code page conversion
(for example, the replacement character) have invalid values. Further
information can be found under "Internal Notes".
If the conversion error occurred while the system was opening, reading,
or writing a file, the name of this file is 'no file'.
(For more information on this file: " X ð####Ìÿ#,").
How to correct the error
The exception must either be prevented, caught within the procedure
"READ_TEXTLINES"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
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:
"CONVT_CODEPAGE_INIT" CX_SY_CODEPAGE_CONVERTER_INITC
"SAPLSTXD" or "LSTXDFDB"
"READ_TEXTLINES"
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
File attributes no file
System environment
SAP Release.............. "620"
Application server....... "vensapd"
Network address.......... "10.55.46.71"
Operating system......... "Windows NT"
Release.................. "5.0"
Hardware type............ "4x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 11
Short dump setting....... "full"
Database server.......... "VENSAPD"
Database type............ "ORACLE"
Database name............ "TVD"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Jun 25 2004 20:55:59"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "OCI_920_SHARE "
Patch level.............. "21"
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"
User, transaction...
Client.............. 000
User................ "DDIC"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTXD"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "SAPLSTXD" in "READ_TEXTLINES".
The main program was "RDDEXECU ".
The termination occurred in line 82 of the source code of the (Include)
program "LSTXDFDB"
of the source code of program "LSTXDFDB" (when calling the editor 820).
The program "SAPLSTXD" was started as a background job.
Processing was terminated because the exception "CX_SY_CODEPAGE_CONVERTER_INIT"
occurred in the
procedure "READ_TEXTLINES" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXD ". Its source code starts in line 75
of the (Include) program "LSTXDFDB ".
Best Regards,
Desiree Cardenas

URGENT:upgrade to 3.0.8 issue Call to WPG_SESSION API Failed.Error-Code:6550

I ran upgrade scripts to 3.0.8 from 3.0.6 and completed with no errors.
csh diag.csh reports no errors.
sqlplus to connect string works fine
DAD connect string is correct.
err text:
Call to WPG_SESSION API Failed.
Error-Code:6550
Error TimeStamp:Tue, 5 Jun 2001 03:36:50 GMT
Database Log In Failed
TNS is unable to connect to destination. Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.
Verify that the TNS name in the connectstring entry of the DAD for this URL is valid and the database listener is running.
DIAG.CSH output
oracle(dba)@ws12:/export/home/upgrade:$csh diag.csh -s portal30 -p portal30 ->
Begining Portal Diagnostics
...portal_schema: portal30
...portal_password: *************
...connect_string: iforce
Loading java class for Portal Diagnostics ...SQL*Plus: Release 8.1.6.0.0 - Production on Mon Jun 4 20:48:59 2001
(c) Copyright 1999 Oracle Corporation. All rights reserved.
Connected to:
Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
SQL> SQL> Creating Table 'wwsec_diagnostic$'
Creating Sequence 'wwsec_diagnostic_seq'
Diagnostics Report v 1.0: Oracle Portal v 3.0.8.9.8
As of 04-Jun-2001 20:49:02 Schema Name: PORTAL30 SSO Schema Name: portal30_sso
PORTAL30.wwsec_enabler_config_info$
Login Server URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30_sso/portal30_sso.wwsso_app_admin.ls_login
DAD : portal30_sso
Host connection : successful.
mod_plsql : working.
JServ : working.
Schema name : portal30_sso
Connect string : iforce
Authentication mode : Single Sign-On
portal30_sso.wwsec_enabler_config_info$
Login Server URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30_sso/portal30_sso.wwsso_app_admin.ls_login
DAD : portal30_sso
Host connection : successful.
mod_plsql : working.
JServ : working.
Schema name : portal30_sso
Connect string : iforce
Authentication mode : Single Sign-On
Partner Application Information
**** Oracle Portal (portal30) ****
Home URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30/portal30.home
Success URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30/portal30.wwsec_app_priv.process_signon
DAD : portal30
Host connection : successful.
mod_plsql : working.
JServ : working.
Schema name : portal30
Connect string : iforce
Authentication mode : Single Sign-On
**** The Login Server (portal30_sso) ****
Home URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30_sso/portal30_sso.home
Success URL : http://ws12.sempi.eng.sun.com:7777/pls/portal30_sso/portal30_sso.wwsso_home.process_signon
DAD : portal30_sso
Host connection : successful.
mod_plsql : working.
JServ : working.
Schema name : portal30_sso
Connect string : iforce
Authentication mode : Single Sign-On
Diagnostics completed successfully!
Disconnected from Oracle8i Enterprise Edition Release 8.1.6.0.0 - Production
With the Partitioning option
JServer Release 8.1.6.0.0 - Production
null

Venu
Have you also upgraded your 9iAS instance to 1.0.2.2? The WPG_SESSION API error commonly appears when you are not using the lastest version of mod_plsql contained in 1.0.2.2.
See: Migration Guide for Oracle9iAS Solaris or NT/2000.

URGENT : Upgradation from 4.6c to ECC6.0.

Hi all sap gurus,
I am getting one problem in upgradation project.
DATA: BEGIN OF pE_CONTROL,
PRINT(1),
CLASE_PRINT(1),
PASE(1) VALUE 'X',
JERAR(1),
TITLES(1) VALUE ' ',
LENG TYPE I VALUE 255,
SEPAR(1),
KTOPL LIKE T001-KTOPL,
index LIKE SY-TABIX,
open(1),
clear(1),
ACO(1),
CLASE(3),
table(30),
field(51),
DATa(520),
TEXTO(1),
ND_change(1),
END OF pE_CONTROL.
DATA: BEGIN OF GT_BUKRS OCCURS 0,
BUKRS LIKE T001-BUKRS,
IMP_VI LIKE BSID-WRBTR,
IMP LIKE BSID-WRBTR,
dollar like bsid-dmbe2,
pesos like bsid-dmbtr,
END OF GT_BUKRS.
gt_bukrs = pe_control-data.
In 4.6c they are using this logic there it is working fine.
whereas in ecc6.0 it showing an error that
ge_bukrs and pe_control-data are not convertable in unicode.
at runtime it is showing the ##### symbols and data moving into fields of structure gt_bukrs is correct in non-unicode system.
what can i do for this in ecc6.0.
please help me in this regard.
points will be rewarded. <= not allowed!!
thanks and regards,
Ravi shankar reddy s
Edited by: Julius Bussche on Jul 15, 2008 1:23 PM

Duplicate post. <= not allowed!!
Edited by: Julius Bussche on Jul 15, 2008 1:24 PM

Urgent - Upgraded Form doesn't works well with values saved by previous ver

Hi all,
Form i m working on has changed many times due to change in requirments.
Everytime i do addition in old form, it doesn't works well be data saved by older versions.
e.g.
Current Version that i have upgraded fetchs the data well from database on query. But when i save it, clear or exit the form and then re-query that data, it doesn't show up instead meassage comes that query caused no records to be fetched.
i checked at database level, data is there.
and when i tried to call data from old form, it also refused to show it (data that was previously entered by itself but then saved by new form).
what could be the problem and i can i resolve it.
plz note that in all of this process, there are no database level changes, only form level changes.
regards,
yasir

sounds like spaces are being padded at the end of the data
check the length of the values you've changed in sqlplus and see if they are indeed right padded

Urgent Upgrade question

I currently use CS 4 regular at home. I could not afford the extended version at the time of original purchase. Now I must get the extended for an upcoming class. But the issue is, when I try and purchase the upgrade it requires the latest version that you are upgrading from and the latest is CS 3 extended and says nothing about CS 4. I don't want to purchase the upgrade and if any issues arrise from the CS 3 to CS 4. Adobe's help has not been forth coming with any info that can be construed as useful. Can anyone help? Please!

The short answer is that there is, as far as I know, no upgrade path from regular to extended. You can upgrade from CS3 to CS4 extended, and if you're a student, you can pay the educational price, but I think that is your only option, as hosed as that is. Good luck.

Urgent :Upgrade issue

Hi All,
Your prompt reply will appreciated .I have been asked to answer following by tomorrow.I am working for an upgrade 4.6c to 6.0 for a US client.Need clarification on:
What do we mean by"Checking whether the code breaks can be replaced by standard functionality in the newer version"?
Does it mean that we need to check if client had some customizations in previous version that became standard functionality in 6.0 version?
we have obtained a list of custom Programs, tables and user exits and I have been asked if there are any potential issues with all the custom programs, tables or user exits.What should I do for this?
Thanks in Advance.
Kriti

Hello Kriti,
You need to ask the person for clarification about these questions. There is always a risk when upgrading that standard functions may have changed between releases. Basically the programs and other components need to be tested to see if they still have the same behavior.
Regards,
Manny

URGENT: Upgrade from Oracle 8.0.4 to Oracle 8.1.7

How do I upgrade Oracle 8.0.4 to Oracle 8.1.7?
Please Help me!!! I have to do this task and I don't know how to start.
Thanks

Hi,
Get the Migration document from oracle for 8.1.7.
Hope that helps.
Thanks,
Lanke

Urgent: Upgrade x client 001

Hi,
I'd be thankfull if someone could help me in this topic.
My client uses client 001 for BW mdt in all environments (dev, qas and prod), and we'll upgrade BW from 3.1 to 7.0.
I've seen that this client is reserved for SAP use in SAP ECC, and that the same should occur with BW. Does anyone if this is true? Does anyone knows SAP note number warning us to this problem? I didn't find anyone.
A copy client changing to another client number before upgrade is sufficient or we should do any other procedure?
Thanks,
Edna.

I have another drive in my G5 (my backup drive used for time machine...) but even that one is shown with a red mark, meaning the system cannot be installed to that drive either (I have no idea why it is not bootable)...
As for VueScan, Mr. Hamrick confirmed me some time ago he had no intention of ever adding compatibility to my scanner (scanner is too rare for the coding time to be profitable, and Mr. Hamrick would not be able to have a test machine anyway). Silverfast also does not support it. And unfortunately, the advent of digital photography has not only seriously wounded film-manufacturing companies, but it also caused high-end scanners to become things of the past, which means that one needs to keep computer systems of the past to run these relics (on another hand, it may be the only reason why these very high quality scanners can now be found for a fraction of their original price)...

URGENT - upgrading ram and hard

Hi there,
I went in to a store to buy a macbook pro 15" with 2.4GHz CPU. I asked if I would be able to upgrade my har drive from 750GB SATA (as comes standard) to a 256 SSD later on. She answered "No, if you want a SSD hard you should get it from the factory and when you received it, you would not be able to upgrade your hard nor your RAM. So if you want a higher RAM you should customize your order now; so you better go with the 8GB RAM and the SSD ordered from Apple".
Now my question is: IS THAT RIGHT??? So does thatt mean becasue now that I've ordered an 8 GB RAM with a 128GB SSD I would not be able to upgrade my ram and Hard drive later???

shahabz wrote:
Thanks for your reply mate
I had a look at this earlier but didn't know if I could upgrade it after I received it or not.
The other thing is the warranty; if I change the RAM and HD, would it void the warranty?
And also, the macsales shows the SSD's as 120 or 240 or 480 as oppose to 128, 256 and 512... any idea? or am I wrong?
The MBP comes with instructions for making those changes so it won't void your warranty unless you break something in the process. The SSD's sizes aren't anything to worry about; it's the price differences that matter most!

Need to urgently upgrade my 9.2.0.1 to 9.2.0.5

Dear Experts
My OS is W2K.
I need to upgrade my db from 9.2.0.1 to 9.2.0.5.
How should I proceed ?
I'm looking for an upgrade to download but perhaps I'm wrong and need to install a brand new db in 9.2.0.5 directly. But I can't find a setup for 9.2.0.5 for W2K on Oracle site.
Any help is greatly appreciated as I've got a demo on Monday..
Best Regards,
Guillaume

You don't need to install database in order to upgrade . You can upgrade existing database running 9.2.0.1 to 9.2.0.5 using patch. Download this patch 3171059.Apply this patch to existing database .
Thanks
GCS

URGENT: upgrade from jdk 1.5 to 1.6 causes OutOfMemoryErrors

I have an application that inserts several million records into a database.
Everything works find under JDK 1.4 and 1.5 and according to JProfiler, no memory leaks exist. the heap usage never exceeds 20MB when running under either of these jvms.
but for some reason, memory consumption under Java 1.6 skyrockets. the problem occurs with various Java 1.6.0_XX versions on Windows as well as on Linux. it also occurs regardless of database (oracle 10g or mysql 5.0.45) which pretty much rules out the jdbc driver causing the problem.
the jvm is launched without any extra parameters (aside from -XX:+PrintGCDetails).
The application uses Spring 1.2 and Hibernate 3.2 (although neither of these appears to be responsible for the massive memory consumption).
i have experimented with both the serial and parallel garbage collectors, tried increasing eden (young) size, tried increasing the jvm heap size (-Xmx; this simply delays the OutOfMemoryError) but nothing seems to solve the problem. i have included snippets of the GC details when running under either JVM.
im pretty much out of theories as to how to solve this. does anyone have any clue?
much appreciated
Benjamin
Here is a sample of the GC details when running under Java 1.5
[GC [DefNew: 704K->63K(704K), 0.0009842 secs][Tenured: 8741K->4819K(8852K), 0.0673614 secs] 9254K->4819K(9556K), 0.0684909 secs]
[GC [DefNew: 640K->64K(704K), 0.0010998 secs] 5459K->4961K(9428K), 0.0013923 secs]
[GC [DefNew: 704K->63K(704K), 0.0008307 secs] 5601K->5128K(9428K), 0.0009015 secs]
[GC [DefNew: 703K->63K(704K), 0.0009454 secs] 5768K->5314K(9428K), 0.0010974 secs]
[GC [DefNew: 703K->64K(704K), 0.0005796 secs] 5954K->5365K(9428K), 0.0006691 secs]
[GC [DefNew: 704K->64K(704K), 0.0005730 secs] 6005K->5452K(9428K), 0.0006394 secs]
[GC [DefNew: 704K->64K(704K), 0.0008441 secs] 6092K->5630K(9428K), 0.0009199 secs]
[GC [DefNew: 704K->63K(704K), 0.0009119 secs] 6270K->5676K(9428K), 0.0011003 secs]
[GC [DefNew: 703K->64K(704K), 0.0008150 secs] 6316K->5761K(9428K), 0.0010778 secs]
[GC [DefNew: 704K->63K(704K), 0.0012583 secs] 6401K->5930K(9428K), 0.0015591 secs]
[GC [DefNew: 703K->63K(704K), 0.0005651 secs] 6570K->5983K(9428K), 0.0006504 secs]
[GC [DefNew: 703K->63K(704K), 0.0006776 secs] 6623K->6063K(9428K), 0.0007520 secs]
[GC [DefNew: 703K->64K(704K), 0.0010686 secs] 6703K->6225K(9428K), 0.0011714 secs]
[GC [DefNew: 704K->63K(704K), 0.0012748 secs] 6865K->6277K(9428K), 0.0015974 secs]
[GC [DefNew: 703K->64K(704K), 0.0006470 secs] 6917K->6355K(9428K), 0.0007239 secs]
[GC [DefNew: 704K->63K(704K), 0.0008335 secs] 6995K->6510K(9428K), 0.0008702 secs]
[GC [DefNew: 703K->63K(704K), 0.0005282 secs] 7150K->6560K(9428K), 0.0005635 secs]
[GC [DefNew: 703K->64K(704K), 0.0005776 secs] 7200K->6634K(9428K), 0.0006132 secs]
[GC [DefNew: 704K->64K(704K), 0.0009024 secs] 7274K->6786K(9428K), 0.0009403 secs]
[GC [DefNew: 704K->64K(704K), 0.0009929 secs] 7426K->6916K(9428K), 0.0010620 secs]
[GC [DefNew: 704K->64K(704K), 0.0007581 secs] 7556K->6993K(9428K), 0.0009915 secs]
[GC [DefNew: 704K->63K(704K), 0.0008686 secs] 7633K->7147K(9428K), 0.0009058 secs]
[GC [DefNew: 703K->64K(704K), 0.0008011 secs] 7787K->7277K(9428K), 0.0008358 secs]
[GC [DefNew: 704K->63K(704K), 0.0005985 secs] 7917K->7351K(9428K), 0.0006325 secs]
[GC [DefNew: 703K->64K(704K), 0.0011532 secs] 7991K->7504K(9428K), 0.0012416 secs]
[GC [DefNew: 704K->63K(704K), 0.0010324 secs] 8144K->7636K(9428K), 0.0011210 secs]
[GC [DefNew: 703K->64K(704K), 0.0006600 secs] 8276K->7707K(9428K), 0.0007347 secs]
[GC [DefNew: 704K->63K(704K), 0.0008733 secs] 8347K->7859K(9428K), 0.0009091 secs]
[GC [DefNew: 683K->64K(704K), 0.0011623 secs] 8479K->8066K(9428K), 0.0012492 secs]
[GC [DefNew: 704K->63K(704K), 0.0006170 secs] 8706K->8129K(9428K), 0.0006887 secs]
[GC [DefNew: 703K->63K(704K), 0.0008206 secs] 8769K->8234K(9428K), 0.0009041 secs]
[GC [DefNew: 703K->63K(704K), 0.0008461 secs] 8874K->8434K(9428K), 0.0008814 secs]
[GC [DefNew: 703K->63K(704K), 0.0005558 secs] 9074K->8489K(9428K), 0.0006446 secs]
[GC [DefNew: 703K->64K(704K), 0.0006280 secs] 9129K->8584K(9428K), 0.0007199 secs]
[GC [DefNew: 697K->64K(704K), 0.0009556 secs] 9217K->8768K(9428K), 0.0010326 secs]
[GC [DefNew: 704K->63K(704K), 0.0005956 secs][Tenured: 8758K->4703K(8852K), 0.0646623 secs] 9408K->4703K(9556K), 0.0654001 secs]
Here is a sample of the GC details when running under Java 1.6
[GC [DefNew: 918K->64K(960K), 0.0020567 secs] 3778K->3020K(5056K), 0.0021595 secs]
[GC [DefNew: 949K->42K(960K), 0.0014172 secs] 3905K->3057K(5056K), 0.0015471 secs]
[GC [DefNew: 927K->35K(960K), 0.0010390 secs] 3942K->3086K(5056K), 0.0011432 secs]
[GC [DefNew: 833K->64K(960K), 0.0015407 secs] 3884K->3374K(5056K), 0.0016432 secs]
[GC [DefNew: 950K->23K(960K), 0.0012706 secs] 4261K->3500K(5056K), 0.0013968 secs]
[GC [DefNew: 919K->36K(960K), 0.0011697 secs] 4396K->3513K(5056K), 0.0012770 secs]
[GC [DefNew: 929K->55K(960K), 0.0012376 secs] 4407K->3551K(5056K), 0.0013605 secs]
[GC [DefNew: 951K->64K(960K), 0.0014868 secs] 4447K->3590K(5056K), 0.0015946 secs]
[GC [DefNew: 960K->64K(960K), 0.0017441 secs] 4486K->3701K(5056K), 0.0018505 secs]
[GC [DefNew: 960K->64K(960K), 0.0020746 secs] 4597K->3796K(5056K), 0.0021760 secs]
[GC [DefNew: 960K->6K(960K), 0.0015848 secs] 4692K->3757K(5056K), 0.0016879 secs]
[GC [DefNew: 898K->38K(960K), 0.0010172 secs] 4649K->3789K(5056K), 0.0011267 secs]
[GC [DefNew: 934K->57K(960K), 0.0010758 secs] 4685K->3852K(5056K), 0.0011904 secs]
[GC [DefNew: 912K->64K(960K), 0.0012502 secs] 4706K->3997K(5056K), 0.0014088 secs]
[GC [DefNew: 927K->46K(960K), 0.0011865 secs] 4860K->3998K(5056K), 0.0013099 secs]
[GC [DefNew: 942K->64K(960K), 0.0012960 secs][Tenured: 4089K->3401K(4096K), 0.0425501 secs] 4894K->3401K(5056K), 0.0441511 secs]
[GC [DefNew: 896K->33K(960K), 0.0011024 secs] 4297K->3435K(6632K), 0.0012661 secs]
[GC [DefNew: 925K->41K(960K), 0.0009093 secs] 4327K->3458K(6632K), 0.0010124 secs]
Processing file: xpressfeed_files\northamerica\f_sec_dprc.1.xml
[GC [DefNew: 937K->62K(960K), 0.0013139 secs] 4354K->3503K(6632K), 0.0014167 secs]
[GC [DefNew: 958K->63K(960K), 0.0016036 secs] 4399K->3571K(6632K), 0.0017231 secs]
[GC [DefNew: 925K->64K(960K), 0.0020497 secs] 4433K->4047K(6632K), 0.0021545 secs]
[GC [DefNew: 960K->63K(960K), 0.0028434 secs] 4943K->4682K(6632K), 0.0029479 secs]
[GC [DefNew: 949K->64K(960K), 0.0034273 secs] 5567K->5432K(6632K), 0.0035356 secs]
[GC [DefNew: 761K->63K(960K), 0.0027110 secs][Tenured: 5760K->3870K(5800K), 0.0521882 secs] 6130K->3870K(6760K), 0.0552171 secs]
[GC [DefNew: 896K->63K(960K), 0.0015790 secs] 4766K->4660K(7412K), 0.0016837 secs]
[GC [DefNew: 959K->64K(960K), 0.0022053 secs] 5556K->5198K(7412K), 0.0023537 secs]
[GC [DefNew: 960K->64K(960K), 0.0047609 secs][Tenured: 6672K->5573K(6708K), 0.0663528 secs] 7134K->5573K(7668K), 0.0714929 secs]
[GC [DefNew: 896K->64K(960K), 0.0013912 secs] 8550K->7829K(10252K), 0.0014999 secs]
[GC [DefNew: 960K->0K(960K), 0.0009803 secs] 8725K->7829K(10252K), 0.0010817 secs]
[GC [DefNew: 658K->0K(960K), 0.0003542 secs][Tenured: 7829K->6726K(9292K), 0.0533249 secs] 8488K->6726K(10252K), 0.0539479 secs]
[GC [DefNew: 896K->0K(960K), 0.0003906 secs] 11782K->10886K(12172K), 0.0005096 secs]
[GC [DefNew: 896K->0K(960K), 0.0003760 secs] 11782K->10886K(12172K), 0.0004794 secs]
[GC [DefNew: 896K->0K(960K), 0.0003961 secs] 11782K->10886K(12172K), 0.0005006 secs]
[GC [DefNew: 550K->0K(960K), 0.0003816 secs][Tenured: 10886K->8806K(11212K), 0.0578118 secs] 11437K->8806K(12172K), 0.0587164 secs]
[GC [DefNew: 1024K->0K(1152K), 0.0006045 secs] 18150K->17126K(24156K), 0.0007713 secs]
[GC [DefNew: 1600K->0K(1792K), 0.0004400 secs] 18726K->17126K(24796K), 0.0005490 secs]
[GC [DefNew: 1600K->0K(1792K), 0.0005157 secs] 18726K->17126K(24796K), 0.0006610 secs]
[GC [DefNew: 1600K->0K(1792K), 0.0003872 secs] 18726K->17126K(24796K), 0.0004886 secs]
[GC [DefNew: 635K->0K(1792K), 0.0004294 secs][Tenured: 17126K->12966K(23004K), 0.0691820 secs] 17761K->12966K(24796K), 0.0697843 secs]
[GC [DefNew: 1600K->0K(1792K), 0.0004238 secs] 31206K->29606K(41440K), 0.0005246 secs]
[GC [DefNew: 1600K->0K(1792K), 0.0004216 secs] 31206K->29606K(41440K), 0.0006283 secs]
[GC [DefNew: 2688K->0K(3008K), 0.0004735 secs] 32294K->29606K(42656K), 0.0005802 secs]
[GC [DefNew: 2688K->0K(3008K), 0.0004411 secs] 32294K->29606K(42656K), 0.0005629 secs]
[GC [DefNew: 2688K->0K(3008K), 0.0005797 secs] 32294K->29606K(42656K), 0.0006856 secs]
[GC [DefNew: 1628K->0K(3008K), 0.0004562 secs][Tenured: 29606K->21253K(39648K), 0.0685190 secs] 31235K->21253K(42656K), 0.0691471 secs]

thanks for showing interest in this problem
i have included the the OOM stack trace below. its the traditional Java Heap Space error...
With JProfiler, the app never goes over 20MB of usage when running under jre 1.5. But then with 1.6, usage skyrockets with the "char[]" class being responsible for some 200 MB of memory (running with -Xms128m -Xmx256m). shortly thereafter the thread crashes.
The application simply parses (very large) XML files using the SAX parser supplied by Sun in the JRE/JDK...in this case its Apache's Xerces implementation.
Here are links to some images taken from JProfiler. If you think any others would be of assistance just tell me and i can post them as well.
http://www.javenue.org/mem_profile_jre1.6.JPG
http://www.javenue.org/object_profile_jre1.6.JPG
http://www.javenue.org/allocated_objects_jre1.6.JPG
OOM StackTrace:
Caused by: java.lang.OutOfMemoryError: Java heap space
     at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.refresh(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.invokeListeners(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.skipChar(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
     at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
     at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     at javax.xml.parsers.SAXParser.parse(Unknown Source)
     ... 6 more

Urgent | Upgrading RAM

I own:
http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03619732
I'm going to add this to my laptop: http://www.amazon.com/Corsair-Vengeance-Laptop-Memory-CMSX16GX3M2A1600C10/dp/B0076W9Q5A/ref=sr_1_1?i...
Will it be compatible?
Note that I am putting 2 8GB RAM sticks. Can my laptop support 16GB? lol
I can't find it written anywhere.
Thanks!

Hi,
Amazon also sells Crucial RAM, pleae use the above information from Crucial to order RAM from Amazon
Hope this makes sense.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

HttpUtils deprecated URGENT (upgradation websphere 4.0 to 5.1)

Similar Messages

Maybe you are looking for